Plantronics + Polycom. Now together as Poly Logo

IP 331/335 config not saved


IP 331/335 config not saved

1. Phones are provisioned via DHCP option 160.
2. Phones download their configuration via HTTP
3. Phone registers with the PBX and everything is good.
Problem: If the system providing DHCP option 160 is removed from the network, then after restart the phones revert to an old config from a previous provider (Fonality). This indicates that the config downloaded via HTTP is never saved.
The issue is not unique to one phone but occurs, I believe, on all the 100+ phones with the affected customer.
Why is the config not saved? / How do we force saving it?
Kind Regards,
Message 1 of 4
Polycom Employee & Community Manager

Re: IP 331/335 config not saved

Hello @sub0 ,


welcome to the Polycom Community.

Both the community's Must Read First and the community's FAQ reference the basic minimum information a new or follow up post should contain.

This ensures the questions having to be asked are limited and any new or follow up post contains the right amount of details to ensure any voluntary participant within the community does not spend additional time chasing basic information.

As a reminder the basic information asked for:


  • Provide the exact Software Version of your Phone
  • Provide the Phone Model
  • Provide the Call Platform (aka openSIP,Skype for Business Online, Skype for Business on Premise, Lync)
  • Additional Polycom Infrastructure (RPRM,PDMS or BToE)
  • If applicable provide a backup of the phone in question

UC Software 4.0.0 or later via the Web Interface Utilities > Phone Backup & Restore > Phone Backup > Phone Backup. Please rename into .TXT or Zip the file to attach.
Since UC Software 5.9.0 simply provide this via the Web Interface Diagnostics > Download Support Information Package

  • If possible provide a Log and either attach them or use the Code Tag.Consult the Troubleshooting Section found within the FAQ if applicable
  • If possible provide the MAC Address or Serial of the device
  • Provide details for example if the issue is a day 1 issue or only happened after an upgrade or any other relevant details
  • For questions around Support please check here


Whilst providing some of these details may not directly impact any possible answer the community can provide, it does enable Polycom to have an overview of the current software used. In addition providing all details at the same time allow us to check logs or look up a potential support partners if an issue needs to come into support. It also enables us to verify the entitlement for using features.


Please ensure you always check the FAQ's and/or utilize the community search before posting any new topics or follow up post’s.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.


Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 4
Occasional Advisor

Re: IP 331/335 config not saved

This seems counter intuitive, but you need to assert provisioning from provisioning, instead of relying on option 160. What I have chosen to do with our provisioning is force the DHCP boot server option to static and specifically SET the provisioning server data from provisioning. This ensures that once the phone has talked to my provisioning it will not listen to erroneous option 66/160 handed out by some misconfigured gateways.


See these options:


<device device.set="1"
Message 3 of 4

Re: IP 331/335 config not saved

Thanks a bunch!


Will set the provisioning server data from provisioning, and report back with results.





Message 4 of 4