I have a series of Polycom phones that are tying to register with OpenSER. The phone sends a REGISTER message, and OpenSER replies with Unauthorised (all normal). The phone re-sends the REGISTER with the credentials, and OpenSER sends Ok.
Here's where it goes downhill. The polycom's appearance display does not change from an unregistered to a registered state, ie it does not change from an empty phone to a filled in one. It doesn't think it's registered eventhought it's gotten an OK. Then, a regular intervals it keeps trying to register again, because it still thinks it wasn't successful.
I have some other Polycom phones that are not doing this. All have the same SIP software version, and all essentially have the same xml config files, with minor variations. Happening with OpenSER 1.0.0 and 1.0.1
I have pasted ngrep output of one of these below. Anyone got any ideas?
# U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Max-Forwards: 70. Expires: 3600. Content-Length: 0. .
# U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com;tag=136c3bb27674cf7e44f7b05275ffaecc.0629. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. WWW-Authenticate: Digest realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d". Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .
# U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Authorization: Digest username="2944029", realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d", uri="sip:ipt.oneeighty.com", response="9d8b4708296f3fb88d5cfd453121860d", algorithm=MD5. Max-Forwards: 70. Expires: 3600. Content-Length: 0. .
# U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com;tag=136c3bb27674cf7e44f7b05275ffaecc.32b4. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;expires=3600. Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .
First..Never send logs with Public IP's in Mailing List.
Is polycom reacting same with SER also. If yes, then Polycom issue only.
From: "Douglas Garstang" dgarstang@oneeighty.com CC: users@openser.org Subject: [Users] Registration Weirdness Date: Tue, 7 Mar 2006 20:01:26 -0700
I have a series of Polycom phones that are tying to register with OpenSER. The phone sends a REGISTER message, and OpenSER replies with Unauthorised (all normal). The phone re-sends the REGISTER with the credentials, and OpenSER sends Ok.
Here's where it goes downhill. The polycom's appearance display does not change from an unregistered to a registered state, ie it does not change from an empty phone to a filled in one. It doesn't think it's registered eventhought it's gotten an OK. Then, a regular intervals it keeps trying to register again, because it still thinks it wasn't successful.
I have some other Polycom phones that are not doing this. All have the same SIP software version, and all essentially have the same xml config files, with minor variations. Happening with OpenSER 1.0.0 and 1.0.1
I have pasted ngrep output of one of these below. Anyone got any ideas?
# U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Max-Forwards: 70. Expires: 3600. Content-Length: 0. .
# U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com;tag=136c3bb27674cf7e44f7b05275ffaecc.0629. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. WWW-Authenticate: Digest realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d". Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .
# U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Authorization: Digest username="2944029", realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d", uri="sip:ipt.oneeighty.com", response="9d8b4708296f3fb88d5cfd453121860d", algorithm=MD5. Max-Forwards: 70. Expires: 3600. Content-Length: 0. .
# U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com;tag=136c3bb27674cf7e44f7b05275ffaecc.32b4. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;expires=3600. Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
_________________________________________________________________ Sexy, sultry, sensuous. - see why Bipasha Basu is all that and more. Try MSN Search http://server1.msn.co.in/Profile/bipashabasu.asp
On 03/08/06 05:01, Douglas Garstang wrote:
I have a series of Polycom phones that are tying to register with OpenSER. The phone sends a REGISTER message, and OpenSER replies with Unauthorised (all normal). The phone re-sends the REGISTER with the credentials, and OpenSER sends Ok.
Here's where it goes downhill. The polycom's appearance display does not change from an unregistered to a registered state, ie it does not change from an empty phone to a filled in one. It doesn't think it's registered eventhought it's gotten an OK. Then, a regular intervals it keeps trying to register again, because it still thinks it wasn't successful.
I have some other Polycom phones that are not doing this. All have the same SIP software version, and all essentially have the same xml config files, with minor variations. Happening with OpenSER 1.0.0 and 1.0.1
I have pasted ngrep output of one of these below. Anyone got any ideas?
everything seems to be ok with the reply for the REGISTER. Does the polycom have some debugging feature? Could you see some logs from the phone. Maybe it will give some hints.
Also, maybe making a comparison with the messages sent/received by the phones which accept the 200ok would reveal some differences.
Cheers, Daniel
# U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Max-Forwards: 70. Expires: 3600. Content-Length: 0. .
# U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com;tag=136c3bb27674cf7e44f7b05275ffaecc.0629. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. WWW-Authenticate: Digest realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d". Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .
# U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Authorization: Digest username="2944029", realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d", uri="sip:ipt.oneeighty.com", response="9d8b4708296f3fb88d5cfd453121860d", algorithm=MD5. Max-Forwards: 70. Expires: 3600. Content-Length: 0. .
# U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" sip:2944029@ipt.oneeighty.com;tag=2A2425B5-B64A4132. To: sip:2944029@ipt.oneeighty.com;tag=136c3bb27674cf7e44f7b05275ffaecc.32b4. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c@216.187.128.72. Contact: sip:2944029@216.187.128.72;expires=3600. Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Daniel-Constantin Mierla -
Douglas Garstang -
Kapil Dhawan