Plantronics + Polycom. Now together as Poly Logo

Phone will not re-register

Highlighted
Occasional Contributor

Phone will not re-register

Hi All,

 

We have a problem with a site of phones, if they lose connectivity with the SIP server for a short period of time, the phones will not re register when the connectivity is restored.

 

The way we get the phones back up is to perform a file format on the phones and they will re register straight after this completes (Rebooting the phone or restarting the SIP app doesn't work).

 

Wireshark traces on the SIP server show, once the phones are down, they are not sending any traffic to the SIP server, they don't try to reregister at all.

 

Can I make the phones reregsiter when this scenario occurs, so that when connectivity to the SIP server is restored, the phones come back up with no manual intervention.

 

 

I have included bott/app logs and phone info below.

 

Thanks in advance.

Steve

 

-------------------------------------------------------------------------------------------------------------------------------------------

Phone info

 

Phone Information
Phone Model SoundPoint IP 550
Part Number 2345-12500-001 Rev:Y
MAC Address 00:04:F2:49:39:48
IP Address 10.129.0.119
UC Software Version 4.0.4.2906
BootROM Software Version 4.4.0.0080

 

 

 

 

 

 

 

 

 

-------------------------------------------------------------------------------------------------------------------------------------------

Boot Log

 

000000.315|so |*|00|---------- Initial log entry ----------
000000.315|so |*|00|+++ Note that bootrom log times are in GMT +++
000000.315|copy |*|00|Initial log entry. Current logging level 3
000000.315|utilm|*|00|Initial log entry. Current logging level 4
000000.315|hw |*|00|Initial log entry. Current logging level 4
000000.315|ethf |*|00|Initial log entry. Current logging level 4
000000.315|dns |*|00|Initial log entry. Current logging level 3
000000.315|curl |*|00|Initial log entry. Current logging level 3
000000.315|sec |*|00|Initial log entry. Current logging level 4
000000.475|wdog |*|00|Initial log entry. Current logging level 4
000000.475|lldp |*|00|Initial log entry. Current logging level 3
000000.475|lldp |3|00|LLDP is DISABLED.
000000.475|cdp |*|00|Initial log entry. Current logging level 3
000000.475|cdp |3|00|CDP is DISABLED.
000000.475|key |*|00|Initial log entry. Current logging level 4
000000.490|so |3|00|Platform: Model=SoundPoint IP 550, Assembly=2345-12500-001 Rev=Y Region=
000000.490|so |3|00|Platform: Board=2345-12500-001 1 0
000000.490|so |3|00|Platform: MAC=0004f2493948, IP=Resolving, Subnet Mask=Resolving
000000.490|so |3|00|Platform: BootBlock=3.0.2.0024 (12500-001) 30-Nov-10 15:00
000000.490|so |3|00|Application, main: Label=BOOT, Version=Muscovite 4.4.0.0080 26-Jul-11 13:21
000000.490|so |3|00|Application, main: P/N=3150-11069-440
000000.490|app1 |*|00|Initial log entry. Current logging level 3
000000.500|cfg |*|00|Initial log entry. Current logging level 2
000000.505|cfg |3|00|Current BootBlock revision is '3.0.2 (12500-001).0024'
000000.505|cfg |*|00|Prov|Updating BootBlock
000000.505|cfg |3|00|Checking pre-compiled image 2345-12500-001.bootblock.ld
000000.505|cfg |3|00|New load header information:
000000.505|cfg |3|00|Code length: 0x0000B6A9
000000.505|cfg |3|00|Header check Sum: 0x002A5D32
000000.505|cfg |3|00|Code check Sum: 0x0029A465
000000.505|cfg |3|00|Options: 0x00000020
000000.505|cfg |3|00|Recognized compatible bootBlock
000000.515|cfg |3|00|BootBlock is already present
000000.515|cfg |3|00|Image is already up to date
000000.515|app1 |*|00|BootBlock is already up to date.
000001.475|so |3|00|Link status is Net up Speed 100 full Duplex, PC down.
000012.270|lldp |3|00|LLDP did not receive a response from a switch. Disabling LLDP.
000018.250|cdp |3|00|CDP did not receive a response from a switch. Disabling CDP.
000023.830|app1 |3|00|DNS resolver servers are '172.20.69.1' '172.20.69.2'
000023.830|app1 |3|00|DNS resolver search domain is ''
000023.830|app1 |3|00|Bootline: esw(3,0)bootHost:flash e=10.129.0.119:ffff0000:93a80:15 h=172.20.69.70 g=10.129.0.254 u=**** pw=**** f=0x40 tn=CircaIP
000023.830|app1 |4|00|Could not load time from (0.0.0.0).
000023.835|app1 |3|00|DHCP returned result 0x187 from server 10.129.0.254.
000023.835|app1 |3|00| Phone IP address is 10.129.0.119.
000023.835|app1 |3|00| Subnet mask is 255.255.0.0.
000023.835|app1 |3|00| Gateway address is 10.129.0.254.
000023.835|app1 |3|00| DNS server is 172.20.69.1.
000023.835|app1 |3|00| DNS alternate server is 172.20.69.2.
000024.595|copy |3|00|'ftp://PlcmSpIp:****@172.20.69.70/0004f2493948.cfg' from '172.20.69.70'
000025.605|copy |3|00|Download of '0004f2493948.cfg' succeeded on attempt 1 (addr 1 of 1)
000025.665|cfg |*|00|Prov|Starting to update 2345-12500-001.sip.ld
000025.680|copy |3|00|'ftp://PlcmSpIp:****@172.20.69.70/2345-12500-001.sip.ld' from '172.20.69.70'
000026.570|cfg |3|00|New load header information:
000026.570|cfg |3|00|Code length: 0x0036E80E
000026.570|cfg |3|00|Header check Sum: 0x283AEA46
000026.570|cfg |3|00|Code check Sum: 0x1B553B16
000026.570|cfg |3|00|Options: 0x00000102
000026.570|cfg |3|00|Could not open application file for checking
000026.570|cfg |3|00|Recognized application
000026.695|cfg |*|00|Prov|Updating Application
000026.705|cfg |3|00|Using compatible image 0
000121.000|copy |3|00|Download of '2345-12500-001.sip.ld' succeeded on attempt 1 (addr 1 of 1)
000121.635|sig |*|00|Initial log entry. Current logging level 3
000121.635|sig |3|00|hwSigParseRemove: found key Sig_3.
000122.530|cfg |3|00|Good image signature
000122.670|cfg |3|00|Programming 3598918 bytes into tffs in 4K blocks
000220.425|cfg |*|00|Prov|Succeeded updating file 2345-12500-001.sip.ld
000220.505|cfg |*|00|Prov|Image has been changed
000220.535|cfg |3|00|Prov|Provisioning succeeded
000220.545|app1 |3|00|Application, load: Type=SIP, Version=4.0.4.2906 17-Apr-13 23:08
000232.200|app1 |4|00|Loaded application sip.ld from local system successfully.
000232.200|app1 |6|00|Uploading boot log, time is MON JAN 01 00:02:32 2007
000232.475|copy |3|00|'ftp://PlcmSpIp:****@172.20.69.70/0004f2493948-boot.log' to '172.20.69.70'
000233.085|copy |3|00|Upload of '0004f2493948-boot.log' succeeded on attempt 1 (addr 1 of 1)

 

Message 1 of 1