Just plain 4.2, right? Not 4.2 rev B or something else? On 1/6/2010 9:53 AM, Tony Graziano wrote: > Look at your polycom compatibility list for bootrom. If all your phones will > take a 4.2 bootrom then deactivate the package in use, delete any bootrom > there and upload the new bootrom zip file and re-activate it. Reboot one > phone and see if it works. Allow 5 or more minutes to erase and reload the > phone. > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: tgrazi...@myitdepartment.net > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: mkitchin.pub...@gmail.com<mkitchin.pub...@gmail.com> > To: sipx-users@list.sipfoundry.org<sipx-users@list.sipfoundry.org> > Cc: Tony Graziano<tgrazi...@myitdepartment.net>; mpic...@cmctechgroup.com > <mpic...@cmctechgroup.com> > Sent: Wed Jan 06 10:44:34 2010 > Subject: Re: [sipx-users] Managing Polycom firmware across multiple models > > I deleted the firmware from Sipx inventory, and added the same file back > in. It was the only one I had ever put in. It worked now. I have no idea > why it broke. Maybe something happened when I backed up and restored to > new hardware? No clue here. > What about bootroms? What does everyone normally do here? Should I stick > with what is on them since it is higher than 4.1, or upgrade to the > newest? I thought I read something somewhere about combinations of > bootroms and fimrware that could cause slow boots because it had to > build/read something at every boot (sorry for my lack of specifics). I > want to do whatever is best practice, but I didn't want to make an > irreversible mistake. Thanks for the help! > > On 1/5/2010 7:49 PM, Tony Graziano wrote: > >> No way I know of except query the phone menu itself. >> ============================ >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> Fax: 434.984.8431 >> >> Email: tgrazi...@myitdepartment.net >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> ----- Original Message ----- >> From: mkitchin.pub...@gmail.com<mkitchin.pub...@gmail.com> >> To: Tony Graziano<tgrazi...@myitdepartment.net> >> Cc: Picher, Michael<mpic...@cmctechgroup.com>; >> sipx-users@list.sipfoundry.org<sipx-users@list.sipfoundry.org> >> Sent: Tue Jan 05 20:45:39 2010 >> Subject: Re: [sipx-users] Managing Polycom firmware across multiple models >> >> I guess I'll have to wait until tomorrow. I'm at home and I was hoping I >> could tell the firmware version from the polycom web interface to see if >> it had upgraded, but I can't find that anywhere. Oh well.... >> >> On 1/5/2010 5:57 PM, Tony Graziano wrote: >> >> >>> Matrix: >>> http://downloads.polycom.com/voice/voip/sip_sw_releases_matrix.html >>> >>> Release Notes: >>> http://downloads.polycom.com/voice/voip/relnotes/spip_ssip_3_1_3RevC_relnotes.pdf >>> >>> As long as you are suing a bootrom 4.1.0 or greater, the 3.1.3RevC >>> split upload should be useable by both model phones. >>> >>> Make sure you have no firmware active and upload the 3.1.3 split, then >>> activate it (upload via the zip file). >>> >>> On Tue, Jan 5, 2010 at 6:54 PM,<mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com>> wrote: >>> >>> Also - that is the firmware polycoms page shows when I follow >>> their menus. I assumed that meant it was supported. I will go >>> through some release notes and see what I can find. >>> >>> Sent via BlackBerry from T-Mobile >>> >>> >>> ------------------------------------------------------------------------ >>> *From: * Tony Graziano<tgrazi...@myitdepartment.net >>> <mailto:tgrazi...@myitdepartment.net>> >>> *Date: *Tue, 5 Jan 2010 18:42:22 -0500 >>> *To: *<mkitchin.pub...@gmail.com<mailto:mkitchin.pub...@gmail.com>> >>> *Cc: *Picher, Michael<mpic...@cmctechgroup.com >>> <mailto:mpic...@cmctechgroup.com>>; >>> <sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org>> >>> *Subject: *Re: [sipx-users] Managing Polycom firmware across >>> multiple models >>> >>> tftp would be available by default, and pushed out via dhcp. >>> >>> so if firmware 3.1.3RevC is supported on the polycom 450, it >>> should automatically detect it at reboot or profile push and down >>> and install it, unless the phone was ona network segment where >>> tftp was blocked from the sipx server... >>> >>> On Tue, Jan 5, 2010 at 6:14 PM,<mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com>> wrote: >>> >>> They set to default, but I will check what that as soon as I >>> get home (kids basketball practice right now). DHCP, DNS, >>> TFTP, everything, etc is running on the sipx server configured >>> by the sipx wizard. >>> Sent via BlackBerry from T-Mobile >>> >>> -----Original Message----- >>> From: "Picher, Michael"<mpic...@cmctechgroup.com >>> <mailto:mpic...@cmctechgroup.com>> >>> Date: Tue, 5 Jan 2010 17:42:10 >>> To:<mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com>>; >>> <sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org>> >>> Subject: RE: [sipx-users] Managing Polycom firmware across >>> multiple models >>> >>> Are phones set for TFTP or are they set for FTP or something >>> else? >>> >>> Try manually setting one for TFTP. Also, are they getting >>> DHCP from the >>> same place? >>> >>> Mike >>> >>> -----Original Message----- >>> From: sipx-users-boun...@list.sipfoundry.org >>> <mailto:sipx-users-boun...@list.sipfoundry.org> >>> [mailto:sipx-users-boun...@list.sipfoundry.org >>> <mailto:sipx-users-boun...@list.sipfoundry.org>] On Behalf Of >>> mkitchin.pub...@gmail.com<mailto:mkitchin.pub...@gmail.com> >>> Sent: Tuesday, January 05, 2010 5:01 PM >>> To: sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org> >>> Subject: Re: [sipx-users] Managing Polycom firmware across >>> multiple >>> models >>> >>> Anyone got any tips on how to troubleshoot? >>> >>> On 1/5/2010 2:31 PM, Tony Graziano wrote: >>> > I believe they should be pulling it. >>> > ============================ >>> > Tony Graziano, Manager >>> > Telephone: 434.984.8430 >>> > Fax: 434.984.8431 >>> > >>> > Email: tgrazi...@myitdepartment.net >>> <mailto:tgrazi...@myitdepartment.net> >>> > >>> > LAN/Telephony/Security and Control Systems Helpdesk: >>> > Telephone: 434.984.8426 >>> > Fax: 434.984.8427 >>> > >>> > Helpdesk Contract Customers: >>> > http://www.myitdepartment.net/gethelp/ >>> > >>> > ----- Original Message ----- >>> > From: mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com><mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com>> >>> > To: Tony Graziano<tgrazi...@myitdepartment.net >>> <mailto:tgrazi...@myitdepartment.net>>; sipx-users >>> > <sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org>> >>> > Sent: Tue Jan 05 15:27:49 2010 >>> > Subject: Re: [sipx-users] Managing Polycom firmware across >>> multiple >>> models >>> > >>> > Thanks. So my 450s should be pulling it? They definitely >>> don't seem to >>> > be. I have deployed 6 handsets today and 12 total. My 450 >>> bootrom is >>> > 4.1.2.0037, so it seems like I should have been ok with this >>> requirement >>> > 'Split download file is recommended, but requires that all >>> phones are >>> > running BootROM 4.0 or newer'. They are definitely pulling >>> config file >>> > updates. >>> > My 550s are running bootrom 4.1.1.0232 if that matters. I >>> see that >>> there >>> > is a newer bootrom available for each. Should I upgrade that >>> is well? >>> I >>> > was a little hesitant to do that because I didn't have any >>> issues that >>> I >>> > knew of and I read that change was typically irreversible. >>> > >>> > Thanks again for all the help and advice! >>> > >>> > On 1/5/2010 2:05 PM, Tony Graziano wrote: >>> > >>> >> All of the phones the 3.1.1revc firmware support were >>> unzipped and >>> >> copied to the tftp root directory when you unloaded it. >>> >> >>> >> The phone knows the filename it is looking for, as each >>> model is a >>> >> uniquely different name. >>> >> >>> >> No magic, just logic provided by Polycom on that one. >>> >> >>> >> When the phones boot, or are sent a new profile, they look >>> to see if >>> >> there is a newer bootrom, then firmware, then config file. >>> Newer >>> >> actually only means different here, meaning one that they >>> don't >>> >> currently have as far as bootrom or firmware. If it is not >>> a match, >>> >> they know to download and use it. >>> >> >>> >> On Tue, Jan 5, 2010 at 2:58 PM, mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com> >>> >> <mailto:mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com>> <mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com> >>> >> <mailto:mkitchin.pub...@gmail.com >>> <mailto:mkitchin.pub...@gmail.com>>> wrote: >>> >> >>> >> I am deploying Soundpoint 450s and 550s. I'm using >>> Sipx 4.0.4. >>> The >>> >> 450s >>> >> worked out of the box. No major changes. Per the posts >>> on here >>> and the >>> >> documentation I found, I had to downgrade the 550s to >>> make them >>> >> work at >>> >> all. I added >>> spip_ssip_vvx_3_1_3RevC_release_sig_split.zip to my >>> Sipx >>> >> server and all is well with the 550s. I double checked >>> to see >>> what >>> >> firmware the 450s are running. Menu, Status, Platform, >>> >> Application, Main >>> >> shows version 3.1.0.0147. I assumed it would be a good >>> idea to >>> get >>> >> these >>> >> up to 3.1.3 as well before my roll out in 2 weeks. Now >>> is where >>> I get >>> >> confused. Polycom shows >>> spip_ssip_vvx_3_1_3RevC_release_sig_split.zip >>> >> (same file as the one for the 550) as the file I need >>> for the >>> 450s. I >>> >> can't check the same file in twice. I honestly don't >>> quite >>> understand >>> >> how Sipx knew the first file was for the 550. I didn't >>> know if >>> it read >>> >> it somewhere within the firmware file. Do I have to >>> tell it >>> somehow it >>> >> is for the 450 too? Am I missing something obvious and >>> simple >>> here? >>> >> >>> >> Thanks a ton! >>> >> >>> >> -Matthew >>> >>_______________________________________________ >>> >> sipx-users mailing list sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org> >>> >> <mailto:sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org>> >>> >> 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/ >>> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> ====================== >>> >> Tony Graziano, Manager >>> >> Telephone: 434.984.8430 >>> >> Fax: 434.984.8431 >>> >> >>> >> Email: >>> tgrazi...@myitdepartment.net >>> >>> <mailto:tgrazi...@myitdepartment.net><mailto:tgrazi...@myitdepartment.net >>> <mailto:tgrazi...@myitdepartment.net>> >>> >> >>> >> LAN/Telephony/Security and Control Systems Helpdesk: >>> >> Telephone: 434.984.8426 >>> >> Fax: 434.984.8427 >>> >> >>> >> Helpdesk Contract Customers: >>> >> http://www.myitdepartment.net/gethelp/ >>> >> >>> >> Why do mathematicians always confuse Halloween and >>> Christmas? >>> >> Because 31 Oct = 25 Dec. >>> >> >>> >> >>> >>> _______________________________________________ >>> sipx-users mailing list sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org> >>> 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/ >>> _______________________________________________ >>> sipx-users mailing list sipx-users@list.sipfoundry.org >>> <mailto:sipx-users@list.sipfoundry.org> >>> 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/ >>> >>> >>> >>> >>> -- >>> ====================== >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> Fax: 434.984.8431 >>> >>> Email: tgrazi...@myitdepartment.net >>> <mailto:tgrazi...@myitdepartment.net> >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> Fax: 434.984.8427 >>> >>> Helpdesk Contract Customers: >>> http://www.myitdepartment.net/gethelp/ >>> >>> Why do mathematicians always confuse Halloween and Christmas? >>> Because 31 Oct = 25 Dec. >>> >>> >>> >>> >>> -- >>> ====================== >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> Fax: 434.984.8431 >>> >>> Email: tgrazi...@myitdepartment.net<mailto:tgrazi...@myitdepartment.net> >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> Fax: 434.984.8427 >>> >>> Helpdesk Contract Customers: >>> http://www.myitdepartment.net/gethelp/ >>> >>> Why do mathematicians always confuse Halloween and Christmas? >>> Because 31 Oct = 25 Dec. >>> >>> >>>
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
