Are the Polycoms doing this on a different network than the Polycoms
not doing this?

On 3/7/06, Douglas Garstang <[EMAIL PROTECTED]> wrote:
> This is a SER/Polycom question, but I hoped we may have some SER guru's 
> here...
>
> 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:[EMAIL PROTECTED]>;tag=2A2425B5-B64A4132.
> To: <sip:[EMAIL PROTECTED]>.
> CSeq: 1 REGISTER.
> Call-ID: [EMAIL PROTECTED]
> Contact: <sip:[EMAIL PROTECTED]>;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:[EMAIL PROTECTED]>;tag=2A2425B5-B64A4132.
> To: <sip:[EMAIL PROTECTED]>;tag=136c3bb27674cf7e44f7b05275ffaecc.0629.
> CSeq: 1 REGISTER.
> Call-ID: [EMAIL PROTECTED]
> 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:[EMAIL PROTECTED]>;tag=2A2425B5-B64A4132.
> To: <sip:[EMAIL PROTECTED]>.
> CSeq: 2 REGISTER.
> Call-ID: [EMAIL PROTECTED]
> Contact: <sip:[EMAIL PROTECTED]>;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:[EMAIL PROTECTED]>;tag=2A2425B5-B64A4132.
> To: <sip:[EMAIL PROTECTED]>;tag=136c3bb27674cf7e44f7b05275ffaecc.32b4.
> CSeq: 2 REGISTER.
> Call-ID: [EMAIL PROTECTED]
> Contact: <sip:[EMAIL PROTECTED]>;expires=3600.
> Server: OpenSer (1.0.0 (i386/linux)).
> Content-Length: 0.
> .
>
>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to