Polycom SIP version and BootROM

the most current versions available on the website (3.1.2?) is what you should be running. Try to phase out the 501s if you can, there were a lot of early 501's using 500 boards and identify themselves as 500s which froze at 2.1.2.

I have held off updating my Polycom firmware until I have more time to deal with any problems that are caused by the update. I'm not sure where most of my phones are now, but I have upgraded couple, and the latest version seems to do ok. Has anyone had a problem with a phone after an upgrade? Should I just throw the new firmware out in my config directory and let the phones pick it up as they boot?

We always deploy the latest firmware on our own phones first - to catch any mishaps before going "live". The config is checked and corrected to take advantage of any new settings/changed directives. Next steps are:

- Customers which would benefit from any bugfixes

- New customers

- Selected customers - those that give good feedback

- All the rest - at once or in chunks depending on how the previous steps went.

No serious problems so far (only cosmetic). Make sure that you use the sip.cfg that comes with the firmware. We use both sip.cfg and phone1.cfg unedited from the firmware archive. We add our own customizations in a separate config.

/Ole

thats exactly how I constructed and intended the phone provisioning templates in pbx manager to work. Always always use the vanilla sip.cfg and phone1.cfg and override them with changes. After experiencing a no-audio call problem with an IP301 going from sip1.65 to sip2.0 I always use new vanilla files with each version.

If you leave teh phone1.cfg and sip.cfg as default what file do you use to make global changes to all the phones for changes like time and message button?

Thanks

polycom_local.cfg in your provisioning folder.