They are Soundpoint 450s.
The files I'm using should definitely be supported. I have used these
exact zip files on 4 other systems, so I don't see how that could be it.
I have tried this combination:
spip_ssip_BootROM_4_2_1_release_sig.zip
spip_ssip_vvx_3_1_3RevC_release_sig_split.zip
and this combination:
spip_ssip_BootROM_4_2_2_release_sig.zip
spip_ssip_vvx_3_2_3_release_sig_split.zip
The first one is running at my corporate office on 200 phones and 1
small satellite office.
The second is running at 2 small satellite offices.
The xferlog contents are below if that gives any info.
Tue Aug 17 20:20:21 2010 1 10.81.4.249 29200 /2345-12450-001.sip.ld b _
o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:20:26 2010 1 10.81.4.249 0 /0004f22704b2-boot.log b _ i r
PlcmSpIp ftp 0 * i
Tue Aug 17 20:20:35 2010 1 10.81.4.249 23360 /2345-12450-001.bootrom.ld
b _ o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:20:41 2010 1 10.81.4.249 3234 /000000000000.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:20:41 2010 1 10.81.4.249 29200 /2345-12450-001.sip.ld b _
o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:20:41 2010 1 10.81.4.249 23501 /polycom_phone1.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:20:42 2010 1 10.81.4.249 198273 /polycom_sip.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:21:25 2010 1 10.81.4.249 29200 /2345-12450-001.bootrom.ld
b _ o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:21:26 2010 1 10.81.4.249 3234 /000000000000.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:21:26 2010 1 10.81.4.249 23360 /2345-12450-001.sip.ld b _
o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:21:31 2010 1 10.81.4.249 0 /0004f22704b2-boot.log b _ i r
PlcmSpIp ftp 0 * i
Tue Aug 17 20:21:41 2010 1 10.81.4.249 29200 /2345-12450-001.bootrom.ld
b _ o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:21:46 2010 1 10.81.4.249 3234 /000000000000.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:21:47 2010 1 10.81.4.249 29200 /2345-12450-001.sip.ld b _
o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:21:47 2010 1 10.81.4.249 23501 /polycom_phone1.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:21:48 2010 1 10.81.4.249 198273 /polycom_sip.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:22:30 2010 1 10.81.4.249 29200 /2345-12450-001.bootrom.ld
b _ o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:22:31 2010 1 10.81.4.249 3234 /000000000000.cfg b _ o r
PlcmSpIp ftp 0 * c
Tue Aug 17 20:22:31 2010 1 10.81.4.249 29200 /2345-12450-001.sip.ld b _
o r PlcmSpIp ftp 0 * i
Tue Aug 17 20:22:36 2010 1 10.81.4.249 0 /0004f22704b2-boot.log b _ i r
PlcmSpIp ftp 0 * i
Tue Aug 17 20:22:45 2010 1 10.81.4.249 29200 /2345-12450-001.bootrom.ld
b _ o r PlcmSpIp ftp 0 *
On 8/17/2010 3:16 PM, Tony Graziano wrote:
It usually means the bootrom or firmware that sipx is trying to load
on the phone is not supported on that model.
You left out an important detail. Phone model.
On Tue, Aug 17, 2010 at 4:13 PM, Matthew Kitchin (public/usenet)
<[email protected] <mailto:[email protected]>> wrote:
Wow. I think Mr. Murphy and his laws have taken up residence in my
office today.
Fresh (3rd time today) install of 4.2.1 on CentOS 5.5 64 Bit.
Everything, including DNS and DHCP are running on the server.
Any Polycom 450 handset I try gets stuck in a reboot loop. It always
ends up on:
config file error
error is 0x0
I have searched for this error, and I can't find anything that even
remotely seems to apply to me.
I get one warning on the diagnostic test. I can't find a great deal of
info on this.
DHCP (Option 120) Test 8/17/10 2:41 PM Warning
Unknown test result: 1
* Hide details
Starting DHCP server test.
Socket Bind Exception: Address already in use
DHCPACK responce received.
Message Type: DHCPACK
Server Identifier: 10.81.4.5
Subnet Mask: 255.255.255.0
Router: 10.81.4.1
Domain Name: bartlett.voip
DNS Server: 10.81.4.5, 127.0.0.1, 10.85.0.10
TFTP Server: 10.81.4.5
SIP Server: sipx.bartlett.voip
NTP Server: 207.171.7.152, 66.7.96.1, 149.20.54.20
Starting SIP servers test.
Testing connectivity to SIP Server: sipx.bartlett.voip
My DHCP conf file looks the same as it does on my working servers.
[r...@sipx tmp]# cat /etc/dhcpd.conf
authoritative;
ddns-update-style none;
option sip-servers-name code 120 = text;
subnet 10.81.4.0 netmask 255.255.255.0 {
range 10.81.4.10 10.81.4.250;
default-lease-time 43200;
max-lease-time 43200;
option routers 10.81.4.1;
option subnet-mask 255.255.255.0;
option domain-name "bartlett.voip";
option tftp-server-name "10.81.4.5";
option sip-servers-name
"sipx.bartlett.voip:12000/cmcprov/login";
option domain-name-servers 10.81.4.5,10.85.0.10;
option ntp-servers sipx.bartlett.voip;
I have tried using both 3.2.3 and 3.1.3. I have both of these
working on
other setups. It does take whichever firmware I activate, but gets the
same error.
I will be glad to provide any more info, but I'm not sure where to
start. Any ideas?
_______________________________________________
sipx-users mailing list
[email protected] <mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
<mailto:[email protected]>
Fax: 434.984.8431
Email: [email protected] <mailto:[email protected]>
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
<mailto:[email protected]>
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
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/