Jump to content
Vodia PBX forum
McFone

Button user portal

Recommended Posts

McFone    0

Hi,

We create button profiles in the domain and map them to the extensions, in the user portal all the buttons are visible under buttons.

We can not save any changes to the buttons type, parameter or label.

We create specific profiles in the domain and we can change in the user portal type,parameter and label

vodia works on the matter or it is a misconfiguration of us

thanks

 

 

Share this post


Link to post
Share on other sites
Support    0

Hi,

 

Yes we are looking into changing the buttons on the user portal and we will update this thread as soon as possible. 

Share this post


Link to post
Share on other sites
McFone    0

Hi,

no provision of keys on any device are possible domain extension -> Buttons and user portal.

We can see under the generated folder, the relation of the button config are not stored correctly, in the config file snom_320_buttons-000413xxxx.xml are missing data.

We use Version Sep 9 2017 05:45:43 Version 58.3

Maybe a configuration problem?

Any idea

thanks

qjb1po

Share this post


Link to post
Share on other sites
McFone    0

Hi,

is a 320 snom, we have generally problems with phones and buttons we have yealink, snom and polycom, polycom for example shows only buttons after a reboot and shows a extension after a reconnect of a phone not registered online BLF status etc.

Would be great if you could watch this live together via remote deskop

thanks

 

Share this post


Link to post
Share on other sites
McFone    0

Hello community,

we have problems with the buttons, the behavior is the following:

This behavior is the same in the user portal or domain

snom:
No transfer of buttons to the phone, a reboot is require after a reboot the buttons are present, a change to buttons also goes only with a reboot.

Polycom:
The same here, only the buttons are displayed after a reboot same for only change / delete of buttons

Yealink:
With the yealinks buttons are transferred to the phone but changes / delete of buttons are not transfer and yealink need a factory reset not only a reboot to take over the buttons

All telephones are connected with TLS to the system and Hosted version 58.3 and we use the redirection service.

We can not figure out that is  wrong with the config or setup , with the behavior is not a roll out to customer possible.

But we do not see our mistakes, every help or tip are welcome

thanks

Share this post


Link to post
Share on other sites
Support    0

Hi,

If the phones are correctly registered using auto-provisioning then on version 58.3, after changing the buttons on the extension level GUI (and not the user portal) the "re-sync" option should sync back the buttons. Polycom reboots by default for these changes as they are default settings on the phone and it's firmware. But yealink has an Auto-provision button on its GUI and it can re-sync the buttons without rebooting. Snom also gets the button changes without a reboot, but which Snom model are you referring to?

Share this post


Link to post
Share on other sites
McFone    0

Hi,

thanks for the answer

All phones are registered via PNP, we have already deleted the directory under generated and created a new directory for the extension.

 

snom:
we use a snom 320
With snom, the phone must be restarted for each action New / Change and Delete.

A sync does not work

Polycom VVX410
The same for polycom all changes to the keys must be sent to the phone via a restart.

Yealink T41
With yealink it is the case that sometimes it is possible and often not, sometimes the keys are sent only after a factory reset.

The yealink must be set to open provisioning again for this purpose

Sometimes changes and deletions of keys can only be done via factory reset, the update of the phone after save the changes has no effect

thanks

Share this post


Link to post
Share on other sites
Support    0

Hi,

 

More often than not, it depends on the handset models and the firmware it's running. Please keep a keen eye on them too, as there are various bugs which arise from the firmwares more than the PBX. For e.g Snom and Yealink come up with various firmwares which aren't acceptable to the end users and they keep re-iterating it. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×