Polycom 601 not sending Authorization header

[Anonymous]

Hi,

I have a polycom 601 with firmware 3.1.8. And its not sending Authorization heder in "REGISTER" message:

REGISTER sip:******.com:5060 SIP/2.0..

Via: SIP/2.0/UDP 10.1.10.86:5060;branch=z9hG4bK5e40c0d1B67DABA0..

From: "0622281" <sip:*****@******.com>;tag=1BB89D07-F984DE64..

To: <sip:*****@*****.com>..

CSeq: 1 REGISTER..

Call-ID: fdd4e7d3-a915be65-2e2c995a@192.168.0.100..

Contact: <sip:*****@10.1.10.86:5060>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"..

User-Agent: PolycomSoundPointIP-SPIP_601-UA/2.2.0.0047_0004f205692a.

Max-Forwards: 70..

Expires: 60..

Content-Length: 0....

Please advise.

[SteffenBaierUK]

Hello Nikita,

we do support the Authorization Header in SIP 3.1 for example but to my knowledge only send this as a reply to a 401 challenge.

Your Phone is not using SIP 3.1.8 as stated in your Post. It is using 2.2.0.0047 according to your User Agent.

Usually the first registration attempt is a basic and then followed by a digest authentication.

If you bring your phone to the above mentioned Software Version and still believe the phone is not behaving SIP RFC conform then I suggest you work with your Polycom Reseller.

Please be aware the SoundPoint IP 601 has been discontinued and is no longer available for purchase.

Support for the product will be available until 03/31/2013 but is not free.

Best Regards

Steffen Baier

[Anonymous]

Sorry, this is an old trace. I already upgraded it to 3.1.8 it still act the same:

Phone is sending "REGISTER":

U 2013/03/14 15:06:05.346337 24.11.149.131:5060 -> server.com:5060
REGISTER sip:mypbxadmin.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 10.1.10.86:5060;branch=z9hG4bK88815bd0FF54CCD.
From: "******" <sip:*******@server.com>;tag=7FC3F68E-C7A7F8A1.
To: <sip:0622281@mypbxadmin.com>.
CSeq: 1 REGISTER.
Call-ID: b4bbfffa-fa12d0e4-ef203257@192.168.0.100.
Contact: <sip:*******@10.1.10.86:5060>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER".
User-Agent: PolycomSoundPointIP-SPIP_601-UA/3.1.8.0070_0004f205692a.
Accept-Language: en.
Max-Forwards: 70.
Expires: 30.
Content-Length: 0.
.

Server replies with "401 Unauthorized.":

U 2013/03/14 15:06:05.346672 server.com:5060 -> 24.11.149.131:5060
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP 10.1.10.86:5060;branch=z9hG4bK88815bd0FF54CCD;rport=5060;received=24.11.149.131.
From: "*******" <sip:*******@server.com>;tag=7FC3F68E-C7A7F8A1.
To: <sip:*******@server.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.ab74.
CSeq: 1 REGISTER.
Call-ID: b4bbfffa-fa12d0e4-ef203257@192.168.0.100.
WWW-Authenticate: Digest realm="server.com", nonce="UUIgyFFCH5wDngmR0zYHg7LeseSVCM7B".
Server: Enswitch SIP proxy.
Content-Length: 0.
.

Phone replies with "REGISTER" without  Authorization Header:

U 2013/03/14 15:06:09.349260 24.11.149.131:5060 ->server.com:5060
REGISTER sip:mypbxadmin.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 10.1.10.86:5060;branch=z9hG4bK88815bd0FF54CCD.
From: "*******" <sip:0622281@server.com>;tag=7FC3F68E-C7A7F8A1.
To: <sip:*******@mypbxadmin.com>.
CSeq: 1 REGISTER.
Call-ID: b4bbfffa-fa12d0e4-ef203257@192.168.0.100.
Contact: <sip:******@10.1.10.86:5060>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER".
User-Agent: PolycomSoundPointIP-SPIP_601-UA/3.1.8.0070_0004f205692a.
Accept-Language: en.
Max-Forwards: 70.
Expires: 30.
Content-Length: 0.
.

Please advise.

[SteffenBaierUK]

Hello Nikita,

as already mentioned the official escalation path has be outlined.

The phone, based on the MAC, is nearly 7 years old so you will have to pay the PPI fee in order to speak to our support agents.

Best Regards

Steffen Baier