480 Temporarily not available \ 401 Unauthorized connecting ... - HP Support Community

Anonymous · ‎06-27-2012

Hi,

We've recently deployed Multitenant Hosted Lync but we're experiencing problems connecting on the Polycom SoundPoint IP 321 and other models. The CA certificate is installed with-out any issues, and all ports are open from our office to the Lync platform. We have used firmware versions 4.0.1B and 4.0.2B but the results are the same.

We have set the following attribute to no minimum required on all of our server:

Network Security: Minimum session security for NTLM SSP based (including secure RPC) servers

In this example our test user is: test.user@testdomain.co.uk

The pre-Windows 2000 login is: HOSTING\test.user

UPN Suffix: testdomain.co.uk

Authorisation domain: HOSTING.COM

Password: password

Front End Pool: FEPOOL1.hosting.com

Front End Server: FE0101.hosting.com

Our Local IP address: 192.168.1.111

Our WAN IP address: 111.111.111.111

Lync Front End IP address: 111.111.111.222

Can anyone here please offer some assistance?

Please note we have replaced some values in the example here for privacy.

This is what we see in the logs on the Polycom:

0627155049|sip  |5|03|Unknown NTLM element TLS-DSK realm
0627155049|sip  |5|03|Unknown NTLM element sts-uri
0627155049|sip  |5|03|Unknown NTLM element TLS-DSK realm
0627155049|sip  |5|03|Unknown NTLM element sts-uri
0627155049|cfg  |4|03|RT|SIP is settting Login Credentials to invalid
0627155050|app1 |*|03|���ՋP�]研]�o(��P�o`�jp@ is out of range, using 3600
0627155050|app1 |*|03|���ՋP�]研]�o(��P�o`�jp@ is out of range, using 3600
0627155050|sip  |*|03|SipUserRemove 0
0627155050|sip  |4|03|Registration failed User: test.user, Error Code:480 Temporarily not available
0627155054|sip  |*|03|User removed
0627155201|sip  |4|03|SSL_get_error Error code=5
0627155201|sip  |4|03|TLS Listen Thread Exit

Here's a copy of the configuration (XML format):

<?xml version="1.0" encoding="utf-8"?>
<h>
  <registration voIpProt.server.1.address="FEPOOL1.hosting.com" sec.TLS.customCaCert.1="-----BEGIN CERTIFICATE-----<<BLANKED OUT FOR PRIVACY>>-----END CERTIFICATE-----" sec.TLS.profileSelection.SIP="ApplicationProfile1" reg.1.auth.useLoginCredentials="1" voIpProt.SIP.mtls.enable="0" voIpProt.server.1.specialInterop="lync2010" voIpProt.server.1.transport="TLS" voIpProt.SIP.allowTransferOnProceeding="0" dialplan.digitmap="RR+R[2-9]11|0T|RR+R011xxx.T|RR+R[0-1][2-9]xxxxxxxxx|RR+R[2-9]xxxxxxxxx|RR+R[2-9]xxxT." tcpIpApp.sntp.address="111.111.111.222" lcl.ml.lang="English_United_Kingdom" />
  <features feature.presence.enabled="1" feature.messaging.enabled="1" msg.mwi.1.callBackMode="contact" roaming_buddies.reg="1" />
  <media sec.srtp.require="1" sec.srtp.offer="1" sec.srtp.key.lifetime="2^31" sec.srtp.mki.enabled="1" sec.srtp.mki.length="1" sec.srtp.holdWithNewKey="0" sec.srtp.resumeWithNewKey="0" voice.audioProfile.G7221.24kbps.payloadType="112" voice.codecPref.G7221.24kbps="5" voice.codecPref.G7221.32kbps="0" video.iFrame.delay="2"></media>
  <profile reg.1.address="test.user@testdomain.co.uk" reg.1.auth.userId="test.user" reg.1.auth.password="password" msg.mwi.1.callBack="sip:test.user@testdomain.co.uk;opaque=app:voicemail" reg.1.auth.domain="HOSTING" reg.1.label="test.user" />
</h>

Here is a copy of the logs produced on the Lync server:

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.718.00088730 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276232
Instance-Id: 0001A5BD
Direction: incoming
Peer: 111.111.111.111:1042
Message-Type: request
Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>
CSeq: 1 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bK78503580338E6C69
Contact: <sip:test.user@192.168.1.111:49293;transport=tls>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER, BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:68fc811b-4987-5c45-93b0-03b134cfd005>"
User-Agent: PolycomSoundPointIP-SPIP_321-UA/4.0.2.11307
Accept-Language: en-gb,en;q=0.9
Ms-device-info: MAC=00-04-F2-AA-03-C8, vendor=POLYCOM, version=PolycomSoundPointIP-SPIP_321-4.0.2.11307
ms-keep-alive: UAC;hop-hop=yes
Supported: msrtc-event-categories,adhoclist,gruu-10,gruu
Event: registration
Max-Forwards: 70
Expires: 3600
Content-Length: 0
Message-Body: –
$$end_record

TL_INFO(TF_DIAG) [0]0A84.0C5C::06/26/2012-18:15:41.720.00088bfc (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: diagnostic
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 401 Unauthorized
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 1 REGISTER
Peer: 111.111.111.111:1042
Data&colon; destination="Unknown"
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.720.00088c42 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276232
Instance-Id: 0001A5BE
Direction: outgoing;source="local"
Peer: 111.111.111.111:1042
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>;tag=0CCFF96D6EDF9725C7F68E46A0BA6153
CSeq: 1 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
ms-user-logon-data&colon; RemoteUser
Date: Tue, 26 Jun 2012 18:15:41 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="FE0101.HOSTING.com", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="FE0101.HOSTING.com", version=4, sts-uri="https://FEPOOL1.HOSTING.com:443/CertProv/CertProvisioningService.svc"
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bK78503580338E6C69;received=111.111.111.111;ms-received-port=1042;ms-received-cid=3D5D00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.763.00088e66 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276233
Instance-Id: 0001A5BF
Direction: incoming
Peer: 111.111.111.111:1042
Message-Type: request
Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>
CSeq: 2 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bKd7271c5AF5E79FA
Contact: <sip:test.user@192.168.1.111:49293;transport=tls>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER, BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:68fc811b-4987-5c45-93b0-03b134cfd005>"
User-Agent: PolycomSoundPointIP-SPIP_321-UA/4.0.2.11307
Accept-Language: en-gb,en;q=0.9
Ms-device-info: MAC=00-04-F2-AA-03-C8, vendor=POLYCOM, version=PolycomSoundPointIP-SPIP_321-4.0.2.11307
ms-keep-alive: UAC;hop-hop=yes
Supported: msrtc-event-categories,adhoclist,gruu-10,gruu
Event: registration
Authorization: NTLM qop="auth", realm="SIP Communications Service", targetname="FE0101.HOSTING.com", gssapi-data=""
Max-Forwards: 70
Expires: 3600
Content-Length: 0
Message-Body: –
$$end_record

TL_INFO(TF_DIAG) [0]0A84.0C5C::06/26/2012-18:15:41.766.00089351 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: diagnostic
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 401 Unauthorized
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 2 REGISTER
Peer: 111.111.111.111:1042
Data&colon; destination="Unknown"
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.766.00089395 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276233
Instance-Id: 0001A5C0
Direction: outgoing;source="local"
Peer: 111.111.111.111:1042
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>;tag=0CCFF96D6EDF9725C7F68E46A0BA6153
CSeq: 2 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
ms-user-logon-data&colon; RemoteUser
Date: Tue, 26 Jun 2012 18:15:41 GMT
WWW-Authenticate: NTLM opaque="807BFC8F", gssapi-data="TlRMTVNTUAACAAAAAAAAADgAAADzgpji3bJGc/PhwugAAAAAAAAAALYAtgA4AAAABgGxHQAAAA8CABgASQBUAEUAQwAtAEgATwBTAFQASQBOAEcAAQAMAEYARQAwADEAMAAxAAQAIABpAHQAZQBjAC0AaABvAHMAdABpAG4AZwAuAGMAbwBtAAMALgBGAEUAMAAxADAAMQAuAGkAdABlAGMALQBoAG8AcwB0AGkAbgBnAC4AYwBvAG0ABQAgAGkAdABlAGMALQBoAG8AcwB0AGkAbgBnAC4AYwBvAG0ABwAIACVgPrLHU80BAAAAAA==", targetname="FE0101.HOSTING.com", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bKd7271c5AF5E79FA;received=111.111.111.111;ms-received-port=1042;ms-received-cid=3D5D00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.825.000895c5 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276234
Instance-Id: 0001A5C1
Direction: incoming
Peer: 111.111.111.111:1042
Message-Type: request
Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>
CSeq: 3 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bKdb76b5bb84781958
Contact: <sip:test.user@192.168.1.111:49293;transport=tls>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER, BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:68fc811b-4987-5c45-93b0-03b134cfd005>"
User-Agent: PolycomSoundPointIP-SPIP_321-UA/4.0.2.11307
Accept-Language: en-gb,en;q=0.9
Ms-device-info: MAC=00-04-F2-AA-03-C8, vendor=POLYCOM, version=PolycomSoundPointIP-SPIP_321-4.0.2.11307
ms-keep-alive: UAC;hop-hop=yes
Supported: msrtc-event-categories,adhoclist,gruu-10,gruu
Event: registration
Authorization: NTLM qop="auth", opaque="807BFC8F", realm="SIP Communications Service", targetname="FE0101.HOSTING.com", gssapi-data="TlRMTVNTUAADAAAAGAAYAEAAAADiAOIAWAAAACIAIgA6AQAAIgAiAFwBAAAaABoAfgEAABAAEACYAQAAcYKQ4JTA3bzm2MVqGO6LN+0CEJcXh63Oc1EeAF3kGVUwTrqSyD/e5g6oPYcBAQAAAAAAAMdTzQGAamevF4etznNRHgAAAAAAAgAYAEkAVABFAEMALQBIAE8AUwBUAEkATgBHAAEADABGAEUAMAAxADAAMQAEACAAaQB0AGUAYwAtAGgAbwBzAHQAaQBuAGcALgBjAG8AbQADAC4ARgBFADAAMQAwADEALgBpAHQAZQBjAC0AaABvAHMAdABpAG4AZwAuAGMAbwBtAAUAIABpAHQAZQBjAC0AaABvAHMAdABpAG4AZwAuAGMAbwBtAAcACAAlYD6yx1PNAQAAAABpAHQAZQBjAC0AbwBmAGYAaQBjAGUALgBjAG8ALgB1AGsAbwBsAGwAaQBlAC4AYwBsAHUAdAB0AGUAcgBiAHUAYwBrADEAOQAyAC4AMQA2ADgALgAxAC4AMQAxADEA8eMwJNPbMDCqZ2Nxr9S1swAAAAA="
Max-Forwards: 70
Expires: 3600
Content-Length: 0
Message-Body: –
$$end_record

TL_ERROR(TF_SECURITY) [0]0A84.0C5C::06/26/2012-18:15:41.830.00089841 (SIPStack,SIPAdminLog::WriteSecurityEvent:SIPAdminLog.cpp(424))$$begin_record
LogType: security
Text: Failed to validate user credentials
Result-Code: 0x8009030c
SIP-Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 3 REGISTER
Data&colon; gssapi-data="NTLMSSP\x00\x03\x00\x00\x00\x18\x00\x18\x00@\x00\x00\x00\xE2\x00\xE2\x00X\x00\x00\x00"\x00"\x00:\x01\x00\x00"\x00"\x00\\x01\x00\x00\x1A\x00\x1A\x00~\x01\x00\x00\x10\x00\x10\x00\x98\x01\x00\x00q\x82\x90\xE0\x94\xC0\xDD\xBC\xE6\xD8\xC5j\x18\xEE\x8B7\xED\x02\x10\x97\x17\x87\xAD\xCEsQ\x1E\x00]\xE4\x19U0N\xBA\x92\xC8?\xDE\xE6\x0E\xA8=\x87\x01\x01\x00\x00\x00\x00\x00\x00\xC7S\xCD\x01\x80jg\xAF\x17\x87\xAD\xCEsQ\x1E\x00\x00\x00\x00\x00\x02\x00\x18\x00I\x00T\x00E\x00C\x00-\x00H\x00O\x00S\x00T\x00I\x00N\x00G\x00\x01\x00\x0C\x00F\x00E\x000\x001\x000\x001\x00\x04\x00 \x00i\x00t\x00e\x00c\x00-\x00h\x00o\x00s\x00t\x00i\x00n\x00g\x00.\x00c\x00o\x00m\x00\x03\x00.\x00F\x00E\x000\x001\x000\x001\x00.\x00i\x00t\x00e\x00c\x00-\x00h\x00o\x00s\x00t\x00i\x00n\x00g\x00.\x00c\x00o\x00m\x00\x05\x00 \x00i\x00t\x00e\x00c\x00-\x00h\x00o\x00s\x00t\x00i\x00n\x00g\x00.\x00c\x00o\x00m\x00\x07\x00\x08\x00%`>\xB2\xC7S\xCD\x01\x00\x00\x00\x00i\x00t\x00e\x00c\x00-\x00o\x00f\x00f\x00i\x00c\x00e\x00.\x00c\x00o\x00.\x00u\x00"
$$end_record

TL_INFO(TF_DIAG) [0]0A84.0C5C::06/26/2012-18:15:41.831.00089b5e (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: diagnostic
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 401 Unauthorized
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 3 REGISTER
Peer: 111.111.111.111:1042
Data&colon; destination="Unknown"
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.831.00089ba4 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276234
Instance-Id: 0001A5C2
Direction: outgoing;source="local"
Peer: 111.111.111.111:1042
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>;tag=0CCFF96D6EDF9725C7F68E46A0BA6153
CSeq: 3 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
ms-user-logon-data&colon; RemoteUser
Date: Tue, 26 Jun 2012 18:15:41 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="FE0101.HOSTING.com", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="FE0101.HOSTING.com", version=4, sts-uri="https://FEPOOL1.HOSTING.com:443/CertProv/CertProvisioningService.svc"
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bKdb76b5bb84781958;received=111.111.111.111;ms-received-port=1042;ms-received-cid=3D5D00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record

TL_WARN(TF_DIAG) [0]0A84.0C5C::06/26/2012-18:15:41.831.00089bd5 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(145))$$begin_record
LogType: diagnostic
Severity: warning
Text: Routing error occurred; check Result-Code field for more information
Result-Code: 0xc3e93ec3 SIP_E_AUTH_UNAUTHORIZED
SIP-Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 3 REGISTER
Peer: 111.111.111.111:1042
$$end_record

TL_WARN(TF_DIAG) [0]0A84.0C5C::06/26/2012-18:15:41.831.00089be4 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(145))$$begin_record
LogType: diagnostic
Severity: warning
Text: Routing error occured during inbound processing; check Result-Code field for more information
Result-Code: 0xc3e93ec3 SIP_E_AUTH_UNAUTHORIZED
SIP-Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 3 REGISTER
Peer: 111.111.111.111:1042
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.873.00089ddc (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276235
Instance-Id: 0001A5C3
Direction: incoming
Peer: 111.111.111.111:1042
Message-Type: request
Start-Line: REGISTER sip:testdomain.co.uk;transport=tls SIP/2.0
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>
CSeq: 4 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bKe841ede13E92626
Contact: <sip:test.user@192.168.1.111:49293;transport=tls>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER, BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:68fc811b-4987-5c45-93b0-03b134cfd005>"
User-Agent: PolycomSoundPointIP-SPIP_321-UA/4.0.2.11307
Accept-Language: en-gb,en;q=0.9
Ms-device-info: MAC=00-04-F2-AA-03-C8, vendor=POLYCOM, version=PolycomSoundPointIP-SPIP_321-4.0.2.11307
ms-keep-alive: UAC;hop-hop=yes
Supported: msrtc-event-categories,adhoclist,gruu-10,gruu
Event: registration
Authorization: NTLM qop="auth", realm="SIP Communications Service", targetname="FE0101.HOSTING.com", gssapi-data=""
Max-Forwards: 70
Expires: 3600
Content-Length: 0
Message-Body: –
$$end_record

TL_INFO(TF_DIAG) [0]0A84.0C5C::06/26/2012-18:15:41.875.0008a2b3 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: diagnostic
Severity: information
Text: Response successfully routed
SIP-Start-Line: SIP/2.0 401 Unauthorized
SIP-Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
SIP-CSeq: 4 REGISTER
Peer: 111.111.111.111:1042
Data&colon; destination="Unknown"
$$end_record

TL_INFO(TF_PROTOCOL) [0]0A84.0C5C::06/26/2012-18:15:41.875.0008a2f7 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 4033276235
Instance-Id: 0001A5C4
Direction: outgoing;source="local"
Peer: 111.111.111.111:1042
Message-Type: response
Start-Line: SIP/2.0 401 Unauthorized
From: "test.user" <sip:test.user@testdomain.co.uk>;tag=230820E2-B9AE7C03;epid=0004f2aa03c8
To: <sip:test.user@testdomain.co.uk>;tag=0CCFF96D6EDF9725C7F68E46A0BA6153
CSeq: 4 REGISTER
Call-ID: b307d18e-f6a687f-3195248c@192.168.1.111
ms-user-logon-data&colon; RemoteUser
Date: Tue, 26 Jun 2012 18:15:41 GMT
WWW-Authenticate: NTLM opaque="8D77BA94", gssapi-data="TlRMTVNTUAACAAAAAAAAADgAAADzgpji0IilU9+9FkUAAAAAAAAAALYAtgA4AAAABgGxHQAAAA8CABgASQBUAEUAQwAtAEgATwBTAFQASQBOAEcAAQAMAEYARQAwADEAMAAxAAQAIABpAHQAZQBjAC0AaABvAHMAdABpAG4AZwAuAGMAbwBtAAMALgBGAEUAMAAxADAAMQAuAGkAdABlAGMALQBoAG8AcwB0AGkAbgBnAC4AYwBvAG0ABQAgAGkAdABlAGMALQBoAG8AcwB0AGkAbgBnAC4AYwBvAG0ABwAIAPs9T7LHU80BAAAAAA==", targetname="FE0101.HOSTING.com", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.1.111:49293;branch=z9hG4bKe841ede13E92626;received=111.111.111.111;ms-received-port=1042;ms-received-cid=3D5D00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record

SteffenBaierUK · ‎06-27-2012

Hello shaun,

the phone log is pretty clear:

0627155049|sip  |5|03|Unknown NTLM element TLS-DSK realm
0627155049|sip  |5|03|Unknown NTLM element sts-uri
0627155049|sip  |5|03|Unknown NTLM element TLS-DSK realm
0627155049|sip  |5|03|Unknown NTLM element sts-uri

0627155201|sip  |4|03|SSL_get_error Error code=5

I did remove the uninteresting bit.

As far as I am aware we do currently not support NTML on our 4.0.x Releases.

A later release may add this feature but I have not fixed release date for this.

Best Regards

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

Anonymous · ‎06-27-2012

Hi Steffen,

Thanks very much for the prompt reply, I was drawn to the NTLM error and have tried disabling NTLM but wasn't sure I was proceeding down the correct path as we still get errors.

See below for the example IP321 logs with NTLM disabled:

0627202026|sip  |4|03|Registration failed User: test.user, Error Code:401 Unauthorized
0627202117|sip  |4|03|SSL_get_error Error code=5
0627202117|sip  |4|03|TLS Listen Thread Exit
0627202150|sip  |4|03|Registration failed User: test.user, Error Code:480 Temporarily not available
0627202248|sip  |4|03|Registration failed User: test.user, Error Code:401 Unauthorized
0627202326|sip  |4|03|SSL_get_error Error code=5
0627202326|sip  |4|03|TLS Listen Thread Exit
0627202359|sip  |4|03|Registration failed User:test.user, Error Code:480 Temporarily not available
0627202456|sip  |4|03|Registration failed User: test.user, Error Code:401 Unauthorized
0627202545|sip  |4|03|SSL_get_error Error code=5
0627202545|sip  |4|03|TLS Listen Thread Exit

Have you got any more ideas?

Regards, Shaun

SteffenBaierUK · ‎06-28-2012

Hello Shaun,

as a Polycom Employee I am unable to provide you with free support. You should usually work with your Polycom Reseller to bring this to the attention of the Polycom Support.

This official guide => here <= and our Polycom Employee Jeff Schertz Blog => here <= should provide sufficient information on how to setup our phones.

Best regards

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

jschertz · ‎06-28-2012

We do support NTLM v2 for authentication as well as 128-bit. Based on the error it appears the credentials are either invalid or the incorrect format is used.

Are the credentials provided in the .cfg file or via the device's Login Credentials menu? The latter is preferred.

jschertz · ‎06-29-2012

There is a typo in my previous response, that should say NTLM v1 (v2 will be supported in the next release.)

Anonymous · ‎09-23-2014

We are also experiencing this issue using SoundPoint IP 331 phones using UCS software 4.1.1.

Tried both forcing NTLMv2 in the configuration file and lowering NTLM server security settings to "No minimum" to no avail.

Taking a SIP Stack trace on the Lync FE, is shows the phone tries to register twice with the Lync server and gets back a 401 Unauthorized, which is expected based on my experience, but then stops, instead of proceeding with the NLTM challenge/response exchange.

SteffenBaierUK · ‎09-23-2014

Hello Francesco B.,

welcome to the Polycom Community.

Would you be able to try UCS 4.1.0 instead as I believe we currently have an issue to some extend with UCS 4.1.1

It would be good if you could raise a ticket via your reseller with Polycom support so we can troubleshoot this and verify it it matches what we have seen with other customers.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

Anonymous · ‎09-24-2014

Hi Steffen,

thanks for your reply. Just to inform you that we just tried with another SoundPoint IP 331 phone with software version 4.1.0.x and we get the same error.

Thank you

Francesco

SteffenBaierUK · ‎09-24-2014

Hello Francesco B,

the next step is to raise a Ticket with Polycom support via your Polycom reseller.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

480 Temporarily not available \ 401 Unauthorized connecting to Lync using 4.0.1B and 4.0.2B

Create an account on the HP Community to personalize your profile and ask a question