Anybody had trouble with the old 550's running 3.2.3 loosing their configs for no apparent reason?
Additionally I am seeing in my Enswitch provisioning field for these phones this strange config-command
I am not sure what this is doing or why it would be in there at all...can anybody explain it?
The only additional provisioning I ever add is the call waiting commands
This is really bugging me. Any Ideals or info?
welcome to the Polycom Community.
The easiest way to find out would be to liaise with your SIP provider enswitch and find out what they are provisioning to the phone.
Looking at the SIP 3.2.2 Admin Guide => here <= on Page C - 16 shows the key with the Null function is the DND Key.
Null in this case means do nothing so the DND key is de-activated.
Please work with your provider to find out what they are doing and why they are doing it.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
I did find out the dnd was being disabled per request by some customers so that would not be affecting the loss of config.
I have had my asterisk vendor look and they do not see anything wrong with the configs or with the operation of the switch.
I have over 800 other phones with 220 offices that are not loosing configs. This is specfic to this one location so there has to be some commonality I can identify.
I will continue to examine the customer side then to see if I can identify any power issues or option 66 injections that might be scrambling the NVRAM chip as that is the only thing that makes sense.
I am still not sure what you mean by loss of config.
What Configuration is lost ? The one provisioned by your server?
What seems to be wiped out are the server menus selections specifying server type and address
and in the Ethernet menu the VLan ID goes from the default blank or 0 to Vlan 2...
What has me wondering if this is specific to the 550 and 3.2.3 is that most of my clients are running 450's new 550's and 650's for desktop stations all running 3.3.2. or newer UC I do have lots of customer legacy equipment running from 2.8.0 to 3.2.3 mainly with the old 331's that do not seem to loose configs. The config loss seems to be contained and localized to only this one customer. running 550's with 3.2.3.
My next step will be to offer to upgrade a couple of them for the customer and see if they stabilize.
This post was originally for informational purposes to see if anyone else had run into this same issue.