How to determine Polycom firmware version
Do the same command on a sip.ld file. The firmware and bootrom are two different files. -bash-3.00$ strings 2345-12600-001.sip.ld | head B5(!b Application 08-Sep-08 14:46 3.1.0 Iter=C;BuildID=0084;AppType=1;Config=15;Cpu=8;Dsp=32;Flash=41352;Gpio=296960;Key=384;Lcd=33792;PhoneType=3801088;Phy=272;TargetFlash =6;FlashWidth=1;Checksum=0x00008f03;SigMax=3;Sig_3=8a1d05e3144e710ce0a2be32c66e4131c087da7076cf92d5b9b675a2a1eb178d9cb18f99ecae30f6c ae65c96e5489aed1420205d0aaa34c1501c26050ffac620b91cb3a47b2a880609b520582c6a57b3673473c5e018b10c57b5938d71b7252382490feed0839a4f8dcb3 308f1b708cb0cb64f79d6f154c29d5247c3df91473c; Copyright (c) 2000-2008 Polycom, Inc. I also always rename the file to include the version number so they're a bit easier to track, even if in different directories. Such as: -bash-3.00$ strings sip_316.ld | head Application 01-Dec-09 12:35 3.1.6 Iter=A;BuildID=0017;AppType=1;Config=15;Cpu=1;Dsp=2;Flash=40;Gpio=4;Key=1;Lcd=9;PhoneType=8;Phy=2;TargetFlash=2;FlashWidth=1;Checksum=0x00008ba7;SigMax=3;Sig_3=5e20e0e7a5d9ca55d7ea518de53430e06b7b77d35a98cb0ba0b942540d0b8620797f4fdecddec8b850b47ea615fd6fb133a3e8242127f3321f79bd810d977e79e9908f9eb00ce8ccc46226c74340db76cc37f9c295a1da4f494ae5033e2d018747e0fe77de7eb490ee22b8bd688511f31719f240d802c47dad7a49cab5c250d0; Copyright (c) 2000-2009 Polycom, Inc. --- Brandon Buckner Switching Technician / VoIP Admin Iowa Network Services brandonb at netins.com<mailto:brandonb at netins.com> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of PE Sent: Tuesday, June 28, 2011 11:52 AM To: voiceops at voiceops.org Subject: [VoiceOps] How to determine Polycom firmware version If I have multiple copies of polycom firmware on a server (in different directories, of course), is there any way to know what version it is? The phones seem to be able to tell by downloading the 4k, but I don't see a firmware version.There appears to be header info in the file but nothing that tells me explicitly that this is, for example, v3.3.1. Even the phone type is cryptic (8388608 = 450?) # strings /tmp/2345-12450-001.bootrom.ld | more %r;0 BootRom 04-Jun-10 17:08 4.3.0 Iter=A;BuildID=0246;SigKey=8;Config=11;Cpu=8;Dsp=32;Flash=41344;Gpio=1048576;Key=1056768;Lcd=262144;PhoneType=8388608;Phy=16;TargetF lash=4;FlashWidth=1;Checksum=0x00008fa7;SigMax=3;Sig_3=268574598ea909fa3d673c4e4f85328e3a2a37ce0da6a5e51930d6d89621919bdcae01e680fa9 1a330cf2e280849825c31dbfa253a97f78ae2d8f34819e9f0e053d76cbf4eae57629307c50b267ceea2222b2ec8435be83cc68cdb060cb28ed4c8990f6b8900e0aee 8f9fa57987bd925f476f7e0f56f83376491fbedffe3f17c; Copyright (c) 2000-2010 Polycom, Inc. #### A BUNCH OF UNREADABLE BINARY STUFF FOLLOWS Anyone have an easy way to tell the version (without having to boot a phone from it)? Thanks
I'm an idiot. I thought I had done it on a sip file and that it was telling me it wanted Bootrom 4.3.0. Oops. Thanks Brandon. On Tue, Jun 28, 2011 at 1:18 PM, Brandon Buckner <BrandonB at netins.com>wrote:
Do the same command on a sip.ld file. The firmware and bootrom are two different files. ****
** **
-bash-3.00$ strings 2345-12600-001.sip.ld | head****
B5(!b****
Application****
08-Sep-08 14:46****
3.1.0****
Iter=C;BuildID=0084;AppType=1;Config=15;Cpu=8;Dsp=32;Flash=41352;Gpio=296960;Key=384;Lcd=33792;PhoneType=3801088;Phy=272;TargetFlash ****
=6;FlashWidth=1;Checksum=0x00008f03;SigMax=3;Sig_3=8a1d05e3144e710ce0a2be32c66e4131c087da7076cf92d5b9b675a2a1eb178d9cb18f99ecae30f6c ****
ae65c96e5489aed1420205d0aaa34c1501c26050ffac620b91cb3a47b2a880609b520582c6a57b3673473c5e018b10c57b5938d71b7252382490feed0839a4f8dcb3 ****
308f1b708cb0cb64f79d6f154c29d5247c3df91473c;****
Copyright (c) 2000-2008 Polycom, Inc.****
** **
I also always rename the file to include the version number so they?re a bit easier to track, even if in different directories. Such as:****
** **
-bash-3.00$ strings sip_316.ld | head****
Application****
01-Dec-09 12:35****
3.1.6****
Iter=A;BuildID=0017;AppType=1;Config=15;Cpu=1;Dsp=2;Flash=40;Gpio=4;Key=1;Lcd=9;PhoneType=8;Phy=2;TargetFlash=2;FlashWidth=1;Checksum=0x00008ba7;SigMax=3;Sig_3=5e20e0e7a5d9ca55d7ea518de53430e06b7b77d35a98cb0ba0b942540d0b8620797f4fdecddec8b850b47ea615fd6fb133a3e8242127f3321f79bd810d977e79e9908f9eb00ce8ccc46226c74340db76cc37f9c295a1da4f494ae5033e2d018747e0fe77de7eb490ee22b8bd688511f31719f240d802c47dad7a49cab5c250d0; ****
Copyright (c) 2000-2009 Polycom, Inc.****
** **
** **
*---*
*Brandon Buckner*
*Switching Technician / VoIP Admin***
*Iowa Network Services*
*brandonb at netins.com*
** **
** **
*From:* voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] *On Behalf Of *PE *Sent:* Tuesday, June 28, 2011 11:52 AM *To:* voiceops at voiceops.org *Subject:* [VoiceOps] How to determine Polycom firmware version****
** **
If I have multiple copies of polycom firmware on a server (in different directories, of course), is there any way to know what version it is? The phones seem to be able to tell by downloading the 4k, but I don't see a firmware version.There appears to be header info in the file but nothing that tells me explicitly that this is, for example, v3.3.1. Even the phone type is cryptic (8388608 = 450?)****
** **
** **
# strings /tmp/2345-12450-001.bootrom.ld | more****
%r;0****
BootRom****
04-Jun-10 17:08****
4.3.0****
Iter=A;BuildID=0246;SigKey=8;Config=11;Cpu=8;Dsp=32;Flash=41344;Gpio=1048576;Key=1056768;Lcd=262144;PhoneType=8388608;Phy=16;TargetF ****
lash=4;FlashWidth=1;Checksum=0x00008fa7;SigMax=3;Sig_3=268574598ea909fa3d673c4e4f85328e3a2a37ce0da6a5e51930d6d89621919bdcae01e680fa9 ****
1a330cf2e280849825c31dbfa253a97f78ae2d8f34819e9f0e053d76cbf4eae57629307c50b267ceea2222b2ec8435be83cc68cdb060cb28ed4c8990f6b8900e0aee ****
8f9fa57987bd925f476f7e0f56f83376491fbedffe3f17c;****
Copyright (c) 2000-2010 Polycom, Inc.****
** **
#### A BUNCH OF UNREADABLE BINARY STUFF FOLLOWS****
** **
** **
Anyone have an easy way to tell the version (without having to boot a phone from it)?****
** **
Thanks****
participants (2)
-
BrandonB＠netins.com -
peeip989＠gmail.com