LYNC Federation - Internal Error on Verify Message by Lync PC Client.

Question

Hello all,
Recently I set a static route for SIP  "interdomain" Federation between Lync 2013 and other vendor PBX.
However I'm struggling with the Lync PC Client error message on validating the messages received by Lync FE. Lync Mobile Client or IPAD client don't have the same issue.
In the Lync FE logs I see that the Invite it's received by the FE and forward to the Lync PC Client. However the in the Lync PC Logs we see WARN message that verify message failed what result in abort of the incoming call on the Lync Client.
Lync PC Client Log:
08/05/2014|17:36:21.102 26F8:C4 TRACE ::
verified buffer: <TLS-DSK><D82A1226><26><SIP Communications Service><Lync2013-PC.innodemo.local><[email protected]><11892668><INVITE><sip:[email protected]><1641009297><sip:[email protected]><><><><>-length-220.
signature:1fa6a6801d168888125378d7ff858578f30b6bf2
08/05/2014|17:36:21.102 26F8:C4 WARN  ::
VerifyMessage failed
x6 times
In the FE Logs I see:
TL_INFO(TF_PROTOCOL) [0]12E4.1EEC::08/05/2014-15:32:40.429.000000c6 (InboundRouting,InboundRoutingClientTransaction.SendImpl:inboundroutingcontext.cs(2308))[2344625192]
SendImpl() to sip:172.16.93.12:60561;transport=tls;ms-opaque=0e66ad0711;ms-received-cid=A600
TL_INFO(TF_DIAG) [0]10CC.1314::08/05/2014-15:32:40.430.000000c8 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(778))[2344625192]
$$begin_record
Severity: information
Text: Routed a request on behalf of an application
SIP-Start-Line: INVITE sip:172.16.93.12:60561;transport=tls;ms-opaque=0e66ad0711;ms-received-cid=A600 SIP/2.0
SIP-Call-ID: [email protected]
SIP-CSeq: 11892668 INVITE
Peer: 172.16.93.12:60561
Data: destination="[email protected]";application="http://www.microsoft.com/LCS/DefaultRouting"
$$end_record
TL_INFO(TF_PROTOCOL) [0]10CC.1314::08/05/2014-15:32:40.430.000000c9 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(196))[2344625192]
$$begin_record
Trace-Correlation-Id: 2344625192
Instance-Id: 32C
Direction: outgoing
Peer: 172.16.93.12:60561
Message-Type: request
INVITE sip:172.16.93.12:60561;transport=tls;ms-opaque=0e66ad0711;ms-received-cid=A600 SIP/2.0
Start-Line: INVITE sip:172.16.93.12:60561;transport=tls;ms-opaque=0e66ad0711;ms-received-cid=A600 SIP/2.0
From: <sip:[email protected]>;tag=1641009297
To: <sip:[email protected]>;epid=5acfd7e726
Call-ID: [email protected]
CSeq: 11892668 INVITE
Contact: <sip:[email protected]:5061;transport=TLS>
Via: SIP/2.0/TLS 172.16.93.3:5061;branch=z9hG4bK32626C7B.D608D12EF622D7A8;branched=FALSE;ms-internal-info="ca-uvj7g7cd2YxUxssjsnQep4sdcBc90oFo27_60ZBaigu0QjWk5N33QAA"
Via: SIP/2.0/TLS 172.16.93.11:5061;branch=z9hG4bK-2B43DB32;rport;alias;received=172.16.93.11;ms-received-port=60028;ms-received-cid=AD00
Record-Route: <sip:Lync2013-PC.innodemo.local:5061;transport=tls;opaque=state:F:Ci.Ra600;lr;ms-route-sig=aam67Qa-S2QyV9XEtcYaQRQjPC9PgzSs05BJukjXBgjxMu0QjWLwDDRgAA>;tag=45D3B960B6E2B498388A5465B5BFF35F
Max-Forwards: 58
Content-Length: 427
Content-Type: application/sdp
Message-Body: v=0\no=- 34 1 IN IP4 172.16.93.11\ns=-\nt=0 0\nm=audio 16422 RTP/AVP 18 4 8 0 101 13\nc=IN IP4 172.16.93.19\na=rtpmap:101 telephone-event/8000\na=fmtp:18 annexa=yes\na=fmtp:18 annexb=no\na=fmtp:101 0-15\na=ptime:60\na=silenceSupp:off - - - -\na=sendrecv\na=ice-ufrag:Xgox\na=ice-pwd:v8uT6XAZFNHQeDNrOtUWni\na=candidate:1
1 UDP 2130706431 172.16.93.19 16422 typ host\na=candidate:1 2 UDP 2130706430 172.16.93.19 16423 typ host
$$end_record
TL_INFO(TF_DIAG) [0]10CC.1314::08/05/2014-15:32:40.430.000000ca (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(778))[2344625192]
$$begin_record
Severity: information
Text: Routed a locally generated response
SIP-Start-Line: SIP/2.0 100 Trying
SIP-Call-ID: [email protected]
SIP-CSeq: 11892668 INVITE
Peer: ipva.innodemo.local:60028
$$end_record
ERROR message:
TL_ERROR(TF_COMPONENT) [0]10CC.1644::08/05/2014-15:32:43.159.000000d4 (SIPStack,CSIPRequest::ProcessVia:SIPRequest.cpp(685))
( 00000016ABEDAD40 ) Exit - the via header contains unexpected received-cid attribute. Returned 0xC3E93F04(SIPPROXY_E_REQUEST_NO_CORRECT_VIA)
TL_ERROR(TF_COMPONENT) [0]10CC.1644::08/05/2014-15:32:43.159.000000d5 (SIPStack,CSIPRequest::ValidateInboundHeaders:SIPRequest.cpp(1495))
( 00000016ABEDAD40 ) Exit - failed to ProcessVia(). Returned 0xC3E93F04(SIPPROXY_E_REQUEST_NO_CORRECT_VIA)
TL_WARN(TF_DIAG) [0]10CC.1644::08/05/2014-15:32:43.159.000000d6 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(781))[2344625192]
$$begin_record
Severity: warning
Text: Routing error occurred; check Result-Code field for more information
Result-Code: 0xc3e93f04 SIPPROXY_E_REQUEST_NO_CORRECT_VIA
SIP-Start-Line: ACK sip:[email protected] SIP/2.0
SIP-Call-ID: [email protected]
SIP-CSeq: 11892668 ACK
Peer: ipva.innodemo.local:60028
$$end_record
So they are two different errors here, in the Lync client PC failed to verify the message, and in the FE it fail to validate the ms-received-cid in the via header.
What indeed looks to exist a mismatch between "A600" to "AD00", looks the 6 was replaced by 6.I believe this headers are generated internally by Lync FE, not sure what is going wrong here for this mismatch.
Any expert could give a look and have an hint why this weird behavior of Lync FE.
Thanks in advance,
Regards,
Claudio

Answer 1

Hi,
From your description, it happened after the setting of static route. Please double check the route setting. Then publish Topology again, and run Step 2 Setup or Remove Lync Server Components on Lync Server Deployment Wizard.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support