Polycom 5000s not working after re-IP

[sheldoom]

After a re-IP of the IPO R11.0 there are 2 Polycom IP 5000s that were working and now are not.

We have changed all the settings from the old IP address to the new, double-checked all settings, defaulted (the Polycom) and reprogrammed from scratch and nothing seems to work. I get the traces below continuously, but no 400 messages as to why the phone isn't registering. It's just not registering.

Any ideas?

Thank you,

1800887454mS SIP Misc Rx: phone
SUBSCRIBE sip:500@10.102.56.235:5060 SIP/2.0
Via: SIP/2.0/UDP 10.50.10.100:5060;branch=z9hG4bKc73a64885F97B7F5
From: "Ext 500" <sip:500@10.102.56.235>;tag=37D6494D-69B1C48A
To: <sip:500@10.102.56.235>
CSeq: 1 SUBSCRIBE
Call-ID: 5a7b9b2-6eee06bf-45a78c1c@10.50.10.100
Contact: <sip:500@10.50.10.100:5060>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: message-summary
User-Agent: PolycomSoundStationIP-SSIP_5000-UA/3.3.3.0069
Accept-Language: en
Accept: application/simple-message-summary
Max-Forwards: 70
Expires: 3600
Content-Length: 0

1800887951mS SIP Rx: UDP 10.50.10.100:5060 -> 10.102.56.235:5060
REGISTER sip:10.102.56.235:5060 SIP/2.0
Via: SIP/2.0/UDP 10.50.10.100:5060;branch=z9hG4bK7476317AB3591F4
From: "Ext 500" <sip:500@10.102.56.235>;tag=3CFDA362-DB8DD36F
To: <sip:500@10.102.56.235>
CSeq: 1 REGISTER
Call-ID: f3f90e21-a289e49e-a248726b@10.50.10.100
Contact: <sip:500@10.50.10.100:5060>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"
User-Agent: PolycomSoundStationIP-SSIP_5000-UA/3.3.3.0069
Accept-Language: en
Max-Forwards: 70
Expires: 3600
Content-Length: 0

1800887953mS SIP Reg/Opt Rx: phone
REGISTER sip:10.102.56.235:5060 SIP/2.0
Via: SIP/2.0/UDP 10.50.10.100:5060;branch=z9hG4bK7476317AB3591F4
From: "Ext 500" <sip:500@10.102.56.235>;tag=3CFDA362-DB8DD36F
To: <sip:500@10.102.56.235>
CSeq: 1 REGISTER
Call-ID: f3f90e21-a289e49e-a248726b@10.50.10.100
Contact: <sip:500@10.50.10.100:5060>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"
User-Agent: PolycomSoundStationIP-SSIP_5000-UA/3.3.3.0069
Accept-Language: en
Max-Forwards: 70
Expires: 3600
Content-Length: 0

1800888451mS SIP Rx: UDP 10.50.10.100:5060 -> 10.102.56.235:5060
SUBSCRIBE sip:500@10.102.56.235:5060 SIP/2.0
Via: SIP/2.0/UDP 10.50.10.100:5060;branch=z9hG4bKc73a64885F97B7F5
From: "Ext 500" <sip:500@10.102.56.235>;tag=37D6494D-69B1C48A
To: <sip:500@10.102.56.235>
CSeq: 1 SUBSCRIBE
Call-ID: 5a7b9b2-6eee06bf-45a78c1c@10.50.10.100
Contact: <sip:500@10.50.10.100:5060>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: message-summary
User-Agent: PolycomSoundStationIP-SSIP_5000-UA/3.3.3.0069
Accept-Language: en
Accept: application/simple-message-summary
Max-Forwards: 70
Expires: 3600
Content-Length: 0



"It's all ball bearings these days" Fletch F. Fletch

 

[derfloh]

Ipo doesn't answer. Probably it thinks it is related to a SIP trunk or the SIP registrar is disabled.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[Westi]

also check if the IPO can ping the phones.

It has to either have a default IP route or one that works for the phone network

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019