Problem with new tb 2.0 iso and Polycom bootrom
The new trixbox 2.0 pro se iso that is available for download right now is including the polycom 4.0.0.0423 bootrom that is not compatible with trixbox. An oversight i assume. I'm sure of this, here's what i did:
1) Downloaded the new 2.0 iso from the trixbox website marked:
Version: trixboxPro-2.0.0.iso
Date Published:4/16/2008
Language: English
Download Size: 621 MB
MD5 checksum:6532460d1b1ef57e0bdaaa7be5c31b5d
2) Installed it on my server, authenticated, it's up and running 119311.
3) plugged in my polycom 501. It went through updating the bootrom twice, both times formatting the file system. Then after the second reset the phone is totally unable to connect to the boot server.
I thought at first that the server was then having a problem with the boot server so I found a TFTP program on sourceforge.org: http://sourceforge.net/projects/tftputil/ setup my workstation as a TFTP server. I downloaded bootrom 3.2.3B and soundstation sip software 2.1.3 from the polycom website. Loaded all the files in my 'dummy' TFTP server, renamed the 000......cfg file to the proper macaddress.cfg file. The phone connected and updated back to the proper firmware.
Then just to be sure I set the phone to connect back to the trixbox server and it did it again, updated the bootrom to the 4.0.0.023.
you have access to the command line correct?
so then for the 2.2.2 version firmware you would type in:
wget http://downloads.polycom.com/voice/voip/sp_ss_sip/spip_ssip_2_2_2...
you would then see the file being downloaded to your server. after its done, type
unzip spip_ssip_2_2_2_release_sig.zip
and it will unzip all those files for you
Dang, i'm right on the edge of being there. The phone is up and running, kinda. It's not auto provisioning now. when i installed the software did i copy over the file that does the auto provisioning? If so how do i restore that file, or edit the existing one, or how do i get it back up and running? grr.
it shouldnt have overwritten it - that file name is based on the MAC ID of the phone
i really cannot tell you where on your system the file is located
i'd advise doing a search for it
(if you wanted to find a file called file1.txt):
find -name file1.txt
and it will then show you the path where that file is located
(ex. /home/tftp/file1.txt)
then once you navigate to that directory (using my example)
cd /home/tftp
you can open the file for viewing/editing with:
vi file1.txt
(you may want to read up a little bit on using vi before you open the file though - if you type "man vi" into the command line then it will show you a user manual for it.)
side note: typing man (whatever command you want to learn about here) will bring up the manual for that command
ex. man vi
man cd
man grep
the list just goes on and on
wget http://yum.trixbox.org/centos/5/RPMS/firmware-polycom-3.0.1-2.noa...
rpm -i --force firmware-polycom-3.0.1-2.noarch.rpm
reboot your phone
press setup and enter the password
Now select the "Server Menu" ?? Maybe named something else
Make sure to set the server type to "Trivial FTP"
change "Server Address" to the ip address of your TFTP server
press exit twice and select "Save & reboot"
Your phone well reboot a few times to load the Boot ROM and firmware.
When it's done go into the endpoint manager and search for new phones.
Select your phone and pick an extension from the list.
reboot your phone and start making calls!
Hmm. This comes in a .txt file with the spip_ssip_bootrom_3_0_1.zip file from the polycom webiste:
***** Polycom BootROM 3.0.x Upgrade Warning *****
Once you have upgraded to the BootROM 3.0.x image, you will ONLY be able to run signed versions of our applications and BootROMs. You will NOT be able to downgrade to unsigned versions of the BootROM and you will NOT be able to use applications that are unsigned.
The 3.0.x BootROM release was designed to improve the security of your Polycom IP phone, with the introduction of HTTP/HTTPS provisioning (SIP only) and the addition of "digital signatures" to the BootROM and applications.
Upgrading to the 3.0.x BootROM is recommended ONLY if you intend to use these security features in the SIP 1.5.x application.
For all other customers, we recommend that you continue to use the 2.6.2 version of the BootROM. You will still be able to use all the functionality of our latest SIP and MGCP releases, without being restricted to using signed images.
Might this be my problem somehow?
Not sure what your problem is Ricki. You can download many versions of Polycom software at Polycom's site;
http://www.polycom.com/usa/en/support/voice/soundpoint_ip/soundpo...

Member Since:
2008-04-14