ahennis@voicespring.net Posted December 17, 2015 Report Share Posted December 17, 2015 I am running Vodia server 5.2.5 and Snom 720 phones running 8.7.5.35 and 8.7.3.25. I have configure an agent group and have configured a button on the phone to allow that agent to log in and log out. When I press the button it will log the agent in and if I press it again it will log the agent out but the button never lights up when the agent is logged in. Is there any other configuration that needs to be done to make this work. Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted December 17, 2015 Author Report Share Posted December 17, 2015 Here is one of the document I referenced to config this. https://www.vodia.com/documentation/agentgroups Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted December 17, 2015 Author Report Share Posted December 17, 2015 Did additional testing. Agent was not logged in Pressed button to log agent in. Agent did get logged in but button did not light up Selected extension in PBX and re-synced the selected account. The button lit up. Pressed the button to log agent out. Agent did get logged out but button did not go off. Selected extension in PBX and re-synced the selected account. The button lit up. Quote Link to comment Share on other sites More sharing options...
Vodia Telephone System Posted December 18, 2015 Report Share Posted December 18, 2015 We will look into it. In the mean time, can you please manually select a button profile for that extension, instead of choosing automatic. Just choose the phone's button profile from the drop down and save it. Thanks. Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted December 18, 2015 Author Report Share Posted December 18, 2015 Thank you for looking into my request. I am not using the automatic button template. Each phone has its' own button template. I guess it is possible that this is a Snom problem. I should probable engage them too. Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted January 5, 2016 Author Report Share Posted January 5, 2016 Any update on this. I tried Vodia PBX 5.3.0 and have the same issue. Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted January 5, 2016 Author Report Share Posted January 5, 2016 I have also tried a D715 on 8.7.5.13 and have the same problem. Quote Link to comment Share on other sites More sharing options...
Vodia Telephone System Posted January 5, 2016 Report Share Posted January 5, 2016 Hmmm without the automatic selection it works here for me. We will try to test further with the version you mentioned for the phone in case that has a difference. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted January 7, 2016 Report Share Posted January 7, 2016 Check this video on how to create an extension ,ACD, buttons and provisioning a snom 760 phone. Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted March 25, 2016 Author Report Share Posted March 25, 2016 I have since upgraded to Vodia PBX 5.4.0 and this is still not working. I even tried a Snom 760 as was used in the video. Still does not work. Any suggestions as how to troubleshoot this issue would be appreciated. Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted March 25, 2016 Author Report Share Posted March 25, 2016 Figured it out. I was using global button profile that could be assigned to multiple phones and not an extension specific profile. I usually use a global profile because I like the ability to switch to a text-based editing window for buttons. The extension specific profile does not have the ability to switch to a text-based editing window for buttons. It would be nice to be able to switch to a text-based editing window for buttons for extension specific profiles. Perhaps this can be added in a future version. Is the requirement to use an extension specific profile vs. a global profile for the agent login/logout status indicator to function by design or is it a bug in the system? Quote Link to comment Share on other sites More sharing options...
chrispopp Posted June 5, 2017 Report Share Posted June 5, 2017 I am having the same issue. Even with extension specific doesn't work. Tried multiple firmware versions and getting the same result. Using extension specific profile only lasts a day or so. Testing with a Snom D745 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.