No. not at all. It's me who's sorry to bother you.
It is indeed the right configuration files. I've worked directly with several polycom vendors on this and it does work. When the files load they generate no errors as can be seen in the boot and app logs. Sip is only partially depreciated. You are still suppose to put extra variables in there and you'll notice my sip file is significantly less than i was in previous releases.
Ok no worries. It surprising because all the Polycom
documentation for UCS 3.3.x and 4.0.x says:
It is no longer necessary to load the default sip.cfg and phone1.cfg files to ensure proper operation. This saves approximately 200 KB from being downloaded from the provisioning server for every phone, and will result in
improved boot speed, particularly in ‘power failure recovery’ scenarios. Now,you only have to manage non-default parameters.
Implication: To take advantage of this change, you need to remove the sip.cfg and phone1.cfg templates from the 000000000000.cfg or <MAC Address>.cfg
files. For administrators that have created their own custom configuration files (for example, by combining sip.cfg and phone1.cfg), all parameters that are set to default values need to be removed.
Change is mandatory: Since the sip.cfg and phone1.cfg files are no longer distributed with the release, this change will need to be made.
I seriously doubt your polycom is running anything higher than 3.3 which the system is designed for.
I don't know why you seriously doubt me. In EPM configuration MGR, if I click Install Firmware, it downloads 4.0.1 and when I provision the phone, that's what get's loaded. I know because I had to use a special downgrade boot loader to get it back to 3.3.3.
Actually it's designed for 4.0.
Ok good to know. I couldn't find any documentation about this anywhere.
And its been tested on on about 500 ish polycoms. Please look at my files more closely and you will see this for yourself
Like I mentioned, the phone (IP670) does work when provisioned thru EPM on 4.0.1. On the phone's diags it logs about 22 errors on a stock config with just a single line registration provisioned. Nothing fancy. I always do a 'format file system' before provisioning to make sure nothing carries over.
In any case, now that I know that you've optimized the configs for 4.0.1 I have something to work towards.
Because Polycom's documentation is based on the premise that sip.cfg & phone-1.cfg are deprecated, it makes customizing configs via EPM non standard. Which file should I be adding and fine tuning features?
Send me your app and boot logs to my email and I can help you figure out why your phones won't work
Thanks man, you're always great about offering to help. I just need some guidance on which files I modify to fine tune features and if you have any idea why I cannot reboot the phone after a change from EPM using any firmware. I've tried 3.3.2, 3.3.3 & 4.0.1 all with clean formats in between. If you can help with those 2 things, that should keep me busy for a while!