>>> On 9/11/2009 at 1:31 PM, in message >>> <!&!aaaaaaaaaaayaaaaaaaaaoxibeah36bflhdziwzzo3rcgaaaeaaaacyw+qkvlqflk8ao7lwvgjybaaaaa...@warrentek.com>, >>> "Warren Wiemer" <[email protected]> wrote:
Tony, Thanks for the insight regarding the BootROM and firmware, so I will do as you have suggested and post the results. As far as the process for removal of the others and upload of the new, what location are these files stored in so they can be purged? Or is that automatically taken care of by virtue of creating a new Device File entry and uploading the new files that you mentioned? Regards, Warren Wiemer [email protected] From: Tony Graziano [mailto:[email protected]] Sent: Friday, September 11, 2009 1:24 PM To: [email protected]; [email protected] Subject: Re: [sipx-users] Using new Polycom SoundPoint IP 550 phones -Freezing and Corruption >>> On 9/11/2009 at 1:00 PM, in message >>> <!&!aaaaaaaaaaayaaaaaaaaaoxibeah36bflhdziwzzo3rcgaaaeaaaabmlihj3b6fog+mzmxjqe+0baaaaa...@warrentek.com>, >>> "Warren Wiemer" <[email protected]> wrote: I am trying to configure several new Polycom SoundPoint IP 550 phones to work with a newly created SIPXecs server (4.0.1-015823 2009-06-19T07:16:14 ecs-centos5). This system was a default install and operating fine with (6) older Polycom 501 devices and (4) Bria Communicator 2.5 devices. After having received these new Polycom 550 phones yesterday, I tried to configure one of them with our SIPXecs server and encountered several issues along the way. The first issue was that after adding it as a new Phone Device, and associating a User/Line with it, I generated the profiles and sent them to the server. However the device would boot up and load what appears to be a default app whereas line 1 is labeled as "SoundPoint IP" and the date and time flash off/on continuously. These Polycom 550 devices are running firmware version 3.0.4, so upon researching this online I came across information stating that I needed to download the matching firmware files from Polycom and add to the SIPXecs system by creating a new Device File entry. I performed those actions, and then found that the phone now reboot but hang on the screen which displays the IP address info and etc following the messages that a new application was loaded and checked. When the devices freeze, they actually drop their network connection as well. Then to make things worse, after adding the new file from Polycom for firmware 3.0.4 (spip_ssip_3_0_4_release_sig.zip), I was asked if I would like to use those files as the defaults and I accepted. Since that happened now the original Polycom 501 and Bria 2.5 extensions are no longer working and display errors about the SIP URL on the Polycom 501s and the Bria clients just state that the services are unavailable. So at that point things were not looking too well, so I decided to go to the backup (Config) from the previous day and do a restore. That process completed successfully, but after the reboot I discovered the my issues with the registration of the original Polycom 501 and Bria extension was not any better and that I had also lost some of the custom DNS zone entries and etc. At this point I have no phones registering with my SIPXecs server, appear to have the incorrect firmware/config files for the original Polycom 501 and Bria extensions and still am unable to successfully configure and register one of the new Polycom SoundPoint 550 devices that we have purchased. Short of completely rebuilding the server and starting from scratch, is there information that can be offered to help me with these issues. Regards, Warren Wiemer [email protected] You should have proper bootrom and firmware. I think you are confusing bootrom versions as actually firmware. http://downloads.polycom.com/voice/voip/relnotes/spip_ssip_3_1_3RevC_relnotes.pdf Look at PAGE 5. You need Bootrom 4.1 or greater. The latest shipping version firmware (3.2) is not tested yet, so I would stick with 3.1.3C (split) and firware 4.1. Remove those others and upload this and let the phone update before doing anything else. Post back your success/failure.. Thanks. Bingo. Delete the ones in sipxconfig and upload the new ones, then reboot the phone after the new files are there and activated. The phone should automatically start upgrading BOOTROM first, then FIRMWARE. There will be several reboots and a 15-20 minute process.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
