Plantronics + Polycom. Now together as Poly Logo

IP7000 SIP/2.0 401 Unauthorized (no credential for 10011@xxxx.com

Occasional Advisor

IP7000 SIP/2.0 401 Unauthorized (no credential for 10011@xxxx.com

 Having trouble getting an IP7000 authorized/registered to an Avaya Session Manager.  I have verified the authorization/password settings many times, and have checked authorization settings with some registered Avaya SIP sets so I am pretty confident I have them set correctly but obviously I have something wrong. Last I tried to set it up via  Quick Tip 44011 (Registering Standalone Polycom Soundstation IP) attached.  The BootROM is 4.3.0.026 and the SIP application is 3.3.1.0933.

 

Perhaps some here is good at reading SIP traces?  These are from the SM.

 

 

15:1|REGISTER sip:xxxx.com SIP/2.0                                         |
15:1|Route: <sip:132.189.0.50:15060;lr>                                    |ci.c
15:1|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bK6ef53e705EC50A3F-AP;|
15:1|ft=132.189.0.51~13c4                                                  |o cr
15:1|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bK6ef53e705EC50A3F           |  St
15:1|From: "10011" <sip:10011@xxxx.com>;tag=4A2271F6-5E0B56FD              |  st
15:1|To: <sip:10011@xxxx.com>                                              |nspo
15:1|CSeq: 1 REGISTER                                                      |  En
15:1|Call-ID: 893dd11a-3123d571-df46a874@10.43.55.15                       |  En
15:1|Contact: <sip:10011@10.43.55.15>;methods="INVITE, ACK, BYE, CANCEL, OP|.22;
15:1|TIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"        |
15:1|User-Agent: PolycomSoundStationIP-SSIP_7000-UA/3.3.1.0933             |
15:1|Accept-Language: en                                                   |> Ex
15:1|P-Av-Transport: AP;fe=10.43.55.15:5060;ne=132.189.0.51:5060;tt=UDP    |
15:1|Max-Forwards: 69                                                      |ci.c
15:1|Expires: 3600                                                         |
15:1|Content-Length: 0                                                     |> Ex

 

 

15:1|SIP/2.0 401 Unauthorized                                              |ci.c
15:1|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bK6ef53e705EC50A3F-AP;|
15:1|ft=132.189.0.51~13c4                                                  |o cr
15:1|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bK6ef53e705EC50A3F           |  St
15:1|To: <sip:10011@xxxx.com>;tag=1435358323*1*016asm-callprocessing.sar838|  st
15:1|843524~1358370698961~1839104859~1                                     |nspo
15:1|From: "10011" <sip:10011@xxxx.com>;tag=4A2271F6-5E0B56FD              |  En
15:1|Call-ID: 893dd11a-3123d571-df46a874@10.43.55.15                       |  En
15:1|CSeq: 1 REGISTER                                                      |.22;
15:1|WWW-Authenticate: Digest realm="xxxx.com", qop="auth", opaque="1234567|
15:1|890abcedef", nonce="13c4533f6d3cd85a3628db25637fc1df7855ee9f8ff", algo|
15:1|rithm=MD5, stale=false                                                |> Ex
15:1|Server:  AVAYA-SM-6.1.6.0.616008                                      |
15:1|Content-Length: 0                                                     |ci.c

 

 

15:1|REGISTER sip:xxxx.com SIP/2.0                                         |
15:1|Route: <sip:132.189.0.50:15060;lr>                                    |ci.c
15:1|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bK170b69136C70CEFE-AP;|
15:1|ft=132.189.0.51~13c4                                                  |o cr
15:1|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bK170b69136C70CEFE           |  St
15:1|From: "10011" <sip:10011@xxxx.com>;tag=4A2271F6-5E0B56FD              |  st
15:1|To: <sip:10011@xxxx.com>                                              |nspo
15:1|CSeq: 2 REGISTER                                                      |  En
15:1|Call-ID: 893dd11a-3123d571-df46a874@10.43.55.15                       |  En
15:1|Contact: <sip:10011@10.43.55.15>;methods="INVITE, ACK, BYE, CANCEL, OP|.22;
15:1|TIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"        |
15:1|User-Agent: PolycomSoundStationIP-SSIP_7000-UA/3.3.1.0933             |
15:1|Accept-Language: en                                                   |> Ex
15:1|Authorization: Digest username="10011@xxxx.com", realm="xxxx.com", non|
15:1|ce="13c4533f6d3cd85a3628db25637fc1df7855ee9f8ff", qop=auth, cnonce="XM|ci.c
15:1|ogWj5iOlBKpUq", nc=00000001, opaque="1234567890abcedef", uri="sip:xxxx|
15:1|.com", response="3f7f885e913ea45e9fb9d1d2a9b153e2", algorithm=MD5     |> Ex
15:1|P-Av-Transport: AP;fe=10.43.55.15:5060;ne=132.189.0.51:5060;tt=UDP    |
15:1|Max-Forwards: 69                                                      |ci.c
15:1|Expires: 3600                                                         |
15:1|Content-Length: 0


15:1|SIP/2.0 401 Unauthorized (no credential for 10011@xxxx.com@xxxx.com)  |nspo
15:1|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bK170b69136C70CEFE-AP;|  En
15:1|ft=132.189.0.51~13c4                                                  |  En
15:1|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bK170b69136C70CEFE           |.22;
15:1|To: <sip:10011@xxxx.com>;tag=1435358323*1*016asm-callprocessing.sar838|
15:1|843524~1358370698966~1839104861~1                                     |
15:1|From: "10011" <sip:10011@xxxx.com>;tag=4A2271F6-5E0B56FD              |> Ex
15:1|Call-ID: 893dd11a-3123d571-df46a874@10.43.55.15                       |
15:1|CSeq: 2 REGISTER                                                      |ci.c
15:1|Server:  AVAYA-SM-6.1.6.0.616008                                      |
15:1|Content-Length: 0                                                     |> Ex

2 REPLIES 2
Occasional Advisor

Re: IP7000 SIP/2.0 401 Unauthorized (no credential for 10011@xxxx.com

I realized we were seeing 10011@xxxx.com@xxxx.com in the 401 Unauthorized (no credential for 10011@xxxx.com message so I removed xxxx.com in the authentication field on the IP7000. Looks better but get the same 401 error.

 

07:3|SIP/2.0 401 Unauthorized                                              |rans
07:3|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bK316a8e8bA135595E-AP;|ntit
07:3|ft=132.189.0.51~13c4                                                  |
07:3|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bK316a8e8bA135595E           |true
07:3|To: <sip:10011@132.189.0.51>;tag=1435358323*1*016asm-callprocessing.sa|ntit
07:3|r838843524~1358429495673~1839120009~1                                 |2.23
07:3|From: "10011" <sip:10011@132.189.0.51>;tag=6B9C9039-659F98E4          |
07:3|Call-ID: b680cf4d-3bfdcf08-c68416ff@10.43.55.15                       |
07:3|CSeq: 1 REGISTER                                                      |0.51
07:3|WWW-Authenticate: Digest realm="xxxx.com", qop="auth", opaque="1234567|
07:3|890abcedef", nonce="13c48b5217b922ddf6d2a17b23e8ec0e6ce51780cca", algo|ci.c
07:3|rithm=MD5, stale=false                                                |
07:3|Server:  AVAYA-SM-6.1.6.0.616008                                      |0.51
07:3|Content-Length: 0                                                     |

07:3|REGISTER sip:132.189.0.51:5060 SIP/2.0                                |tatu
07:3|Route: <sip:132.189.0.50:15060;lr>                                    |LS
07:3|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bKfca00862D2B84621-AP;|rans
07:3|ft=132.189.0.51~13c4                                                  |ntit
07:3|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bKfca00862D2B84621           |
07:3|From: "10011" <sip:10011@132.189.0.51>;tag=6B9C9039-659F98E4          |true
07:3|To: <sip:10011@132.189.0.51>                                          |ntit
07:3|CSeq: 2 REGISTER                                                      |2.23
07:3|Call-ID: b680cf4d-3bfdcf08-c68416ff@10.43.55.15                       |
07:3|Contact: <sip:10011@10.43.55.15>;methods="INVITE, ACK, BYE, CANCEL, OP|
07:3|TIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"        |0.51
07:3|User-Agent: PolycomSoundStationIP-SSIP_7000-UA/3.3.1.0933             |
07:3|Accept-Language: en                                                   |ci.c
07:3|Authorization: Digest username="10011", realm="xxxx.com", nonce="13c48|
07:3|b5217b922ddf6d2a17b23e8ec0e6ce51780cca", qop=auth, cnonce="iF2vySOzLVR|0.51
07:3|wytX", nc=00000001, opaque="1234567890abcedef", uri="sip:132.189.0.51:|
07:3|5060", response="b97a6278e7aac1cf119bf7d65162c436", algorithm=MD5     |ci.c
07:3|P-Av-Transport: AP;fe=10.43.55.15:5060;ne=132.189.0.51:5060;tt=UDP    |0.51
07:3|Max-Forwards: 69                                                      |
07:3|Expires: 3600                                                         |ci.c
07:3|Content-Length: 0       

07:3|SIP/2.0 401 Unauthorized (no credential for 10011@xxxx.com)           |ntit
07:3|Via: SIP/2.0/UDP 132.189.0.51;rport;branch=z9hG4bKfca00862D2B84621-AP;|
07:3|ft=132.189.0.51~13c4                                                  |true
07:3|Via: SIP/2.0/UDP 10.43.55.15;branch=z9hG4bKfca00862D2B84621           |ntit
07:3|To: <sip:10011@132.189.0.51>;tag=1435358323*1*016asm-callprocessing.sa|2.23
07:3|r838843524~1358429495679~1839120011~1                                 |
07:3|From: "10011" <sip:10011@132.189.0.51>;tag=6B9C9039-659F98E4          |
07:3|Call-ID: b680cf4d-3bfdcf08-c68416ff@10.43.55.15                       |0.51
07:3|CSeq: 2 REGISTER                                                      |
07:3|Server:  AVAYA-SM-6.1.6.0.616008                                      |ci.c
07:3|Content-Length: 0             

 

Message 2 of 3
Highlighted
Polycom Employee & Community Manager

Re: IP7000 SIP/2.0 401 Unauthorized (no credential for 10011@xxxx.com

Hello Sptitze,

 

all you need to setup is explained => here <=

 

Address= the Extension/DDI/Username assigned to the Phone’s Account on the SIP Switch

 

From the  UCS 3.3.0 Admin Guide:

 

The user part or the user and the host part of the phone’s SIP URI or the H.323 ID/extension.
For example (SIP):
reg.x.address=”1002” from
1002@polycom.com or
reg.x.address=”1002@polycom.com”.
For example (H.323):
reg.x.address=”23456”

 

Auth User ID= the Extension/DDI/Username assigned to the Phone’s Account on the SIP Switch

 

From the UCS 3.3.0 Admin Guide:

 

User ID to be used for authentication challenges for this registration. If non-Null, will override the “Reg User x” parameter entered into the Authentication submenu off of the Settings menu on the phone.

 

Auth Password= the Password assigned to the Phone’s Account on the SIP Switch

 

From the UCS 3.3.0 Admin Guide:

 

Password to be used for authentication challenges for this registration. If non-Null, will override the “Reg Password x” parameter entered into the Authentication submenu off of the Settings menu on the phone.

 

 

Optional 

 

Label = can be used to show the Phones DDI or Name when idle

 

 

Above should be sufficient to register the SSIP7000 to your switch.

 

If this does not work or if you continue to have issues I would suggest to liaise with Avaya and or your Polycom reseller to bring this to the attention of Polycom support.

 

Best Regards

 

Steffen Baier




<======== Signature / Disclaimer ========>
Please be aware:For questions about the type of support to expect please check here

Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

The title Polycom Employee & Community Manager is an automatic setting within the community and any forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Poly employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and maybe answered on weekends, bank holidays or personal holidays.
Message 3 of 3