SOLUTION: Presence works but cannot send message to federated partner.

SOLUTION: Presence works but cannot send  messages to federated partner.

Applies to Lync 2010 and OCS 2007

Problem:

You configured federation between Lync 2010 and OCS 2007 organization. You can see presence information between organizations but cannot send instant messaging to each other.

Symptoms:

When you enable logging on Lync 2010 Client you got the following errors in Application log on the client.

Event Type:      Warning
Event Source:   Communicator
Event Category:           None
Event ID:          11
Date:                20.06.2013
Time:                11:21:07
User:                N/A
Computer:        PC43
Description:

A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f8). More information is contained in the following technical data:

RequestUri:   sip:Deniz@contoso.com;opaque=user:epid:y3bYeKGGoFCWtQzA3V3NigAA;gruu
From:         sip:defne@fabrikam.com;tag=41a0891e15
To:           sip:Deniz@contoso.com;tag=c82aba59be
Call-ID:      ed286ec1ea634ddc8c9a570fff3c932c
Content-type: application/sdp;call-type=im
v=0
o=- 0 0 IN IP4 10.10.10.15
s=session
c=IN IP4 10.10.10.15
t=0 0
m=message 5060 sip null
a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite
Response Data:
504  Server time-out
ms-diagnostics:  1011;reason=”Ms-Diagnostics header not provided by previous hop“;source=”ae.fabrikam.com”;Domain=”contoso.com”;PeerServer=”ae.contoso.com”;OriginalPresenceState=”3000″;CurrentPresenceState=”3000″;MeInsideUser=”Yes”;ConversationInitiatedBy=”2″;SourceNetwork=”3″;RemotePartyCanDoIM=”Yes”

Resolution:

If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

Event Type:      Warning
Event Source:   Communicator
Event Category:           None
Event ID:          11
Date:                20.06.2013
Time:                11:20:39
User:                N/A
Computer:        PC43
Description:
A SIP request made by Communicator failed in an unexpected manner (status code 0). More information is contained in the following technical data:

RequestUri:   sip:Deniz@contoso.com;opaque=user:epid:y3bYeKGGoFCWtQzA3V3NigAA;gruu
From:         sip:defne@fabrikam.com;tag=d69933e551
To:           sip:Deniz@contoso.com;tag=688bb6e3bb
Call-ID:      7526197203504fa791e3fe248290d674
Content-type: application/sdp;call-type=im
v=0
o=- 0 0 IN IP4 10.10.10.15
s=session
c=IN IP4 10.10.10.15
t=0 0
m=message 5060 sip null
a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite
Response Data:

504  Server time-out
ms-diagnostics:  1011;reason=”Ms-Diagnostics header not provided by previous hop”;source=”ae.fabrikam.com”;Domain=”contoso.com”;PeerServer=”ae.contoso.com”

504  Server time-out
ms-diagnostics:  1011;reason=”Ms-Diagnostics header not provided by previous hop”;source=”ae.fabrikam.com”;Domain=”contoso.com”;PeerServer=”ae.contoso.com”
0  (null)
(null):  52112;reason=”Callee did not receive an ACK for the 200 OK“;OriginalPresenceState=”3000″;CurrentPresenceState=”3000″;MeInsideUser=”Yes”;ConversationInitiatedBy=”2″;SourceNetwork=”3″;RemotePartyCanDoIM=”Yes”;RetriedInvite=”true”
Resolution:

If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

On the Contoso Lync 2010 Edge server If you run Lync Server 2010 Logging Tool and analyze it with snooper (from Lync 2010 Resource Kit) you got the following:

TL_INFO(TF_PROTOCOL) [0]0EB0.112C::06/20/2013-08:49:33.646.00005ae6 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 3719720148
Instance-Id: 00001A2E
Direction: incoming;source=”external edge”;destination=”internal edge”
Peer: ae.fabrikam.com.tr:4119
Message-Type: request
Start-Line: SUBSCRIBE sip:pool.contoso.com:5061;transport=tls;ms-fe=lyncFE.internal.contoso.com SIP/2.0
From: <sip:defne@fabrikam.com>;tag=1d97ae5dcd;epid=9583b63822
To: <sip:deniz@contoso.com>;tag=C4660080
CSeq: 2 SUBSCRIBE
Call-ID: f8c521944c2b4bd5a0904e2626b25063
Record-Route: <sip:ae.fabrikam.com.tr:5061;transport=tls;epid=9583b63822;lr>;tag=1B2706C3AFF51F910409EE0048C358D7
Via: SIP/2.0/TLS

TL_WARN(TF_DIAG) [0]0EB0.10AC::06/20/2013-08:49:35.680.00008082 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(145))$$begin_record
LogType: diagnostic
Severity: warning
Text: Host name resolution failure
SIP-Start-Line: ACK sip:Deniz@contoso.com;opaque=user:epid:y3bYeKGGoFCWtQzA3V3NigAA;gruu SIP/2.0
SIP-Call-ID: 6f97738d7d12410d9a96e6f5ce5c50ed
SIP-CSeq: 1 ACK
Data: fqdn=”lynFE.internal.contoso.com”
$$end_record
So it is clear that contoso Edge server cannot resolve IP address of the Lync 2010 Front End Server lynFE.internal.contoso.com. Since it can resolve IP address of the pool fqdn pool.contoso.com only presence information works but instant messaging does not.

Resolution:

Add IP adress of lynFE.internal.contoso.com to host file of Contoso edge server so that it can resolve contoso Lyne 2010 Front End Server. As you can see the snooper logs, resolving pool name is not enough for IM.  SIP messages also contain FE server which  the destination user has been registered.

Advertisements
Gallery | This entry was posted in Lync 2010 and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s