Problem
You’ve configured a SIP trunk between your Lync Server 2013 and Avaya PBX then proceed to try making a call but it fails. A trace and review of the snooper logs reveal the following messages:
TL_INFO(TF_PROTOCOL) [0]101C.3494::07/02/2013-19:27:24.622.00200ea4 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2387.idx(196))[1942010897] $$begin_recordTrace-Correlation-Id: 1942010897
Instance-Id: 47CF0E
Direction: incoming
Peer: 10.50.1.37:50518
Message-Type: request
INVITE sip: +14413243428@domain.com;user=phone SIP/2.0
Start-Line: INVITE sip:+14413243428@domain.com;user=phone SIP/2.0
From: <sip:tluk@domain.com>;tag=19ff1e0ea0;epid=c3c51f41cf
To: <sip:+14413243428@domain.com;user=phone>
Call-ID: 534e05e8aa1b44708dc434c65085e9bb
CSeq: 1 INVITE
Contact: <sip:tluk@domain.com;opaque=user:epid:aZDoBPYY6F-Y6_eBHuLUJQAA;gruu>
Via: SIP/2.0/TLS 10.50.1.37:50518
Max-Forwards: 70
Content-Length: 3266
Content-Type: multipart/alternative;boundary=”—-=_NextPart_000_0092_01CE7741.08E3A7C0″
Message-Body:
TL_INFO(TF_PROTOCOL) [0]16CC.49F8::07/02/2013-19:27:24.652.00204a6f (S4,SipMessage.DataLoggingHelper:1823.idx(752))[2278930503]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_36A13A7>], 10.1.1.66:5070<-10.1.1.66:54529
INVITE sip:+14413243428@10.3.6.210:5070;user=phone;maddr=svrlyncstd02.domain.internal SIP/2.0
FROM: “Luk, Terence”<sip:tluk@domain.com>;tag=19ff1e0ea0;epid=c3c51f41cf
TO: <sip:+14413243428@domain.com;user=phone>
CSEQ: 1 INVITE
CALL-ID: 534e05e8aa1b44708dc434c65085e9bb
MAX-FORWARDS: 69
VIA: SIP/2.0/TLS 10.1.1.66:54529;branch=z9hG4bK8747CA4E.AB3C8956D2CD766C;branched=TRUE
VIA: SIP/2.0/TLS 10.50.1.37:50518;ms-received-port=50518;ms-received-cid=1250700
RECORD-ROUTE: <sip:SVRLYNCSTD02.domain.internal:5061;transport=tls;opaque=state:T;lr>;tag=510C2D779CC0040DA76277F02F7E55EE
CONTACT: <sip:tluk@domain.com;opaque=user:epid:aZDoBPYY6F-Y6_eBHuLUJQAA;gruu>
CONTENT-LENGTH: 3266
SUPPORTED: ms-dialog-route-set-update
SUPPORTED: timer
SUPPORTED: histinfo
SUPPORTED: ms-safe-transfer
SUPPORTED: ms-sender
SUPPORTED: ms-early-media
SUPPORTED: 100rel
SUPPORTED: replaces
SUPPORTED: ms-conf-invite
USER-AGENT: UCCAPI/15.0.4481.1000 OC/15.0.4481.1000 (Microsoft Lync)
CONTENT-TYPE: multipart/alternative;boundary=”—-=_NextPart_000_0092_01CE7741.08E3A7C0″
ACCEPT-LANGUAGE: en-US
ALLOW: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
P-ASSERTED-IDENTITY: “Luk, Terence”<tel:+14413243445>
ms-application-via: SIP;ms-urc-rs-from;ms-server=SVRLYNCSTD02.domain.internal;ms-pool=svrlyncstd02.domain.internal;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
ms-application-via: ms-udc.cdr%3Dae53fde938cbac02468226ebea4f0a60%3A1%3Barch%3Dae53fde938cbac02468226ebea4f0a60%3A1;ms-pool=svrlyncstd02.domain.internal;ms-application=http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent;ms-server=SVRLYNCSTD02.domain.internal
Ms-Conversation-ID: Ac53QI9wCGXHUXoVQ+mYkXqLrnRsZQAAAmqgAAACNxAAACJckAAGPPNgAAADOQA=
ms-keep-alive: UAC;hop-hop=yes
ms-subnet: 10.50.1.0
ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
ms-routing-phase: from-uri-routing-done
ms-pai: “Luk, Terence”<sip:tluk@domain.com>,<tel:+14413243445>
ms-privacy: id
ms-obr-normalized-uri: <sip:+14413243428@domain.com;user=phone>
ms-from: “Luk, Terence”<sip:+14413243445@domain.com;user=phone>
ms-user-data: ms-publiccloud=TRUE;ms-federation=TRUE
TL_INFO(TF_PROTOCOL) [0]16CC.3F30::07/02/2013-19:27:25.554.002087ff (S4,SipMessage.DataLoggingHelper:1823.idx(774))[2278930503]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_36A13A7>], 10.1.1.66:5070->10.1.1.66:54529
SIP/2.0 488 Not Acceptable Here
FROM: “Luk, Terence”<sip:tluk@domain.com>;tag=19ff1e0ea0;epid=c3c51f41cf
TO: <sip:+14413243428@domain.com;user=phone>;tag=e9ae58741f;epid=7A239EA1A1
CSEQ: 1 INVITE
CALL-ID: 534e05e8aa1b44708dc434c65085e9bb
VIA: SIP/2.0/TLS 10.1.1.66:54529;branch=z9hG4bK8747CA4E.AB3C8956D2CD766C;branched=TRUE,SIP/2.0/TLS 10.50.1.37:50518;ms-received-port=50518;ms-received-cid=1250700
CONTENT-LENGTH: 0
P-ASSERTED-IDENTITY: <sip:+14413243428@domain.com;user=phone>
SERVER: RTCC/5.0.0.0 MediationServer
ms-diagnostics: 10407;source=”SVRLYNCSTD02.domain.internal”;reason=”Gateway responded with 407 Proxy Authentication Required”;component=”MediationServer”;SipResponseText=”Not Acceptable Here”;GatewayFqdn=”10.3.6.210;trunk=10.3.6.210″
ms-diagnostics-public: 10407;reason=”Gateway responded with 407 Proxy Authentication Required”;component=”MediationServer”;SipResponseText=”Not Acceptable Here”
ms-trunking-peer: 10.3.6.210;trunk=10.3.6.210;User-Agent=”AVAYA-SM-6.2.0.0.620120″
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
TL_INFO(TF_PROTOCOL) [0]101C.4008::07/02/2013-19:27:25.556.002089ce (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2387.idx(196))[2869572326] $$begin_record
Trace-Correlation-Id: 2869572326
Instance-Id: 47CF1D
Direction: incoming
Peer: svrlyncstd02.domain.internal:5070
Message-Type: response
Start-Line: SIP/2.0 488 Not Acceptable Here
FROM: “Luk, Terence”<sip:tluk@domain.com>;tag=19ff1e0ea0;epid=c3c51f41cf
TO: <sip:+14413243428@domain.com;user=phone>;tag=e9ae58741f;epid=7A239EA1A1
CALL-ID: 534e05e8aa1b44708dc434c65085e9bb
CSEQ: 1 INVITE
VIA: SIP/2.0/TLS 10.1.1.66:54529;branch=z9hG4bK8747CA4E.AB3C8956D2CD766C;branched=TRUE,SIP/2.0/TLS 10.50.1.37:50518;ms-received-port=50518;ms-received-cid=1250700
CONTENT-LENGTH: 0
ms-diagnostics: 10407;source=”SVRLYNCSTD02.domain.internal”;reason=”Gateway responded with 407 Proxy Authentication Required”;component=”MediationServer”;SipResponseText=”Not Acceptable Here”;GatewayFqdn=”10.3.6.210;trunk=10.3.6.210″
ms-diagnostics-public: 10407;reason=”Gateway responded with 407 Proxy Authentication Required”;component=”MediationServer”;SipResponseText=”Not Acceptable Here”
TL_INFO(TF_PROTOCOL) [0]16CC.4480::07/02/2013-19:27:25.559.002090bb (S4,SipMessage.DataLoggingHelper:1823.idx(774))[3101263875]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_36A13A7>], 10.1.1.66:5070<-10.1.1.66:54529
ACK sip:+14413243428@10.3.6.210:5070;user=phone;maddr=svrlyncstd02.domain.internal SIP/2.0
FROM: “Luk, Terence”<sip:tluk@domain.com>;tag=19ff1e0ea0;epid=c3c51f41cf
TO: <sip:+14413243428@domain.com;user=phone>;tag=e9ae58741f;epid=7A239EA1A1
CSEQ: 1 ACK
CALL-ID: 534e05e8aa1b44708dc434c65085e9bb
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.1.1.66:54529;branch=z9hG4bK8747CA4E.AB3C8956D2CD766C;branched=FALSE
CONTENT-LENGTH: 0
SERVER: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FOutboundRouting
ms-application-via: SIP;ms-urc-rs-from;ms-server=SVRLYNCSTD02.domain.internal;ms-pool=svrlyncstd02.domain.internal;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
ms-application-via: ms-udc.cdr%3Dae53fde938cbac02468226ebea4f0a60%3A1%3Barch%3Dae53fde938cbac02468226ebea4f0a60%3A1;ms-pool=svrlyncstd02.domain.internal;ms-application=http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent;ms-server=SVRLYNCSTD02.domain.internal
ms-routing-phase: from-uri-routing-done
ms-diagnostics-public: 5012;reason=”ACK is being generated on receipt of a failure final response for an INVITE forked by application”;AppUri=”http%3A%2F%2Fwww.microsoft.com%2FLCS%2FOutboundRouting”
One of the error messages that catches your eye is the following:
“Gateway responded with 407 Proxy Authentication Required”;component=”MediationServer”;SipResponseText=”Not Acceptable Here”
Solution
After troubleshooting the issue with the PBX engineer, we noticed that we actually had a port mismatch between what was configured on his end and what was configured on my end. The gateway listening port I had configured on my end was set to 5060:
While his end in the Avaya Aura System Manager 6.2 was set to 5068:
Small mistake which was fixed after I changed my TCP port to 5068:
