AsteriskNow and Lync2013

General discussions about AsteriskNOW.

Moderators: Moderator, Support

AsteriskNow and Lync2013

Postby rebootln » Mon Jul 15, 2013 12:24 pm

Hi all,


i have been banging my had on this for 2 days now

all guides online point that integrating the two is simple - create sip trunk / add a peer in asterisk - a few dial rules and that's it

however i seem to have an authentication issue ... here is the error


Reliably Transmitting (no NAT) to 192.168.0.65:5060:
OPTIONS sip:192.168.0.65 SIP/2.0
Via: SIP/2.0/TCP 192.168.0.60:5060;branch=z9hG4bK499542c1
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.0.60>;tag=as7d82ea8b
To: <sip:192.168.0.65>
Contact: <sip:asterisk@192.168.0.60:5060;transport=TCP>
Call-ID: 212ff5d77f74f27b648966507a16bd1c@192.168.0.60:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 11.4.0
Date: Mon, 15 Jul 2013 18:20:17 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- SIP read from TCP:192.168.0.65:5060 --->
SIP/2.0 401 Unauthorized
Date: Mon, 15 Jul 2013 18:20:17 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="server.domain.local", version=4
WWW-Authenticate: Kerberos realm="SIP Communications Service", targetname="sip/server.domain.local", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="server.domain.local", version=4, sts-uri="https://server.domain.local:443/CertProv/CertProvisioningService.svc"
From: "asterisk" <sip:asterisk@192.168.0.60>;tag=as7d82ea8b
To: <sip:192.168.0.65>;tag=1A864FD71D24EA3126ED01414941B743
Call-ID: 212ff5d77f74f27b648966507a16bd1c@192.168.0.60:5060
CSeq: 102 OPTIONS
Via: SIP/2.0/TCP 192.168.0.60:5060;branch=z9hG4bK499542c1;ms-received-port=35858;ms-received-cid=24D300
Server: RTC/5.0
Content-Length: 0

<------------->
--- (12 headers 0 lines) ---



any ideas as to why i am getting 401 / 403
rebootln
Oldsterisk
 
Posts: 126
Joined: Mon Apr 29, 2013 12:50 pm

Re: AsteriskNow and Lync2013

Postby david55 » Wed Jul 17, 2013 3:46 am

Failed options are not normally critical. Even failures to respond at all can be worked round with qualify=no.

Getting 401 is normal The problem is that I don't think that Asterisk supports any of the NTLM, Kerberos or TLS-DSK authentication methods, so would be unable to reply with the relevant credentials.
david55
Moves Like Spencer
 
Posts: 12570
Joined: Fri Sep 26, 2008 5:03 am


Return to AsteriskNOW General

Who is online

Users browsing this forum: No registered users and 1 guest