Jump to content


Photo

Phone buttons do not sync on D745 after restart

Solved

  • Please log in to reply
4 replies to this topic

#1 chrispopp

chrispopp

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts

Posted 05 June 2017 - 03:41 PM

I'm having a tough time with getting the Snom D745 to work correctly with the latest Vodia 57, and the firmware is 8.9.3.60.

 

I have 3 agent groups. In this case 315, 254, 255.

 

Create a custom button list for user 207, the phone is provisioned via based provisioning MAC.

 


domain1.png
 
Upon reboot of the phone the buttons do not get synced.
 

domain2.jpg
 
The buttons do not work. Nothing lights up for BLFs nor Agent Groups. After I go back to the extension button list and click on "Save as Custom" the buttons refresh and start working again for a while. 
 

domain3.jpg
 
 
The big problem is that it sometimes loses the buttons even without the reboot. I have tried a lot of different firmware and I'm getting the same issue.


#2 chrispopp

chrispopp

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts

Posted 05 June 2017 - 03:47 PM

Attached in this is also the log from the phone set to Debug2 if it helps. This is just after the reboot. The buttons in this are not syncing.

Attached Files



#3 Support

Support

    Vodia Support

  • Administrators
  • PipPipPip
  • 45 posts
  • Gender:Male

Posted 06 June 2017 - 08:38 AM

Hi,

 

Try to add this line as it is to the XML file snom_745_phone.xml before the line </phone-settings> and save it:-

<user_proxy_require idx="1" perm="RW">buttons</user_proxy_require>

And then reboot the phone (while it is still being AUTO-PROVISIONED).

 

We have added this change in our latest and upcoming version which wont require the above changes to be done manually anymore. The latest build shall be available for all OS shortly.



#4 Vodia PBX

Vodia PBX

    Advanced Member

  • Administrators
  • PipPipPip
  • 8,974 posts
  • Gender:Male

Posted 06 June 2017 - 08:55 AM

There was a problem with snom button in the versions made in the past few weeks. It has been fixed, if you can, try to upgrade to 57.4 or higher where the problem is fixed.



#5 chrispopp

chrispopp

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts

Posted 06 June 2017 - 03:30 PM

It works now. Thanks







Also tagged with one or more of these keywords: Solved

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users