Hi All,
I'm setting up a new Exchange 2013 server using SP1 (CU5) as the baseline. I'm trying to get Lync 2013 integration for IM working, but I seem to getting a different error message from everyone else. While the first line is the same for people who have certificate errors, the third line is very different.
2014-07-24T13:32:40.522Z,6,1,,,,0,ERROR:InstantMessageOCSProvider.ResetPresence. SelfDataSession not established.,
2014-07-24T13:32:40.631Z,141,5,,,,0,"DEBUG:InstantMessageOCSProvider.SignInCallback. Context: User=amazinguser@geosoft.com, Sip address=sip:amazing.user@geosoft.com, Lyncserver=lync2013.geosoft.com",
2014-07-24T13:32:40.647Z,141,1,,,,0,"ERROR:UCWEB Failure: Code=OcsRegisterFailure, SubCode=Undefined, Reason=None\r\nMicrosoft.Rtc.Internal.UCWeb.Utilities.UCWException: The endpoint was unable to register. See the ErrorCode for specific reason. --->
Microsoft.Rtc.Signaling.RegisterException: The endpoint was unable to register. See the ErrorCode for specific reason.\r\n at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()\r\n at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object
owner, IAsyncResult result)\r\n at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.OotyUserEndpointEstablish_callback(IAsyncResult asyncResult)\r\n --- End of inner exception stack trace ---\r\n at Microsoft.Rtc.Internal.UCWeb.Utilities.AsyncHelper.EndAsyncCall[T](IAsyncResult
asyncResult, String methodName, T ucwScopeInstance)\r\n at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.EndSignIn(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.Clients.Owa2.Server.Core.InstantMessageOCSProvider.<>c__DisplayClass33.<SignInCallback>b__32(RequestDetailsLogger
logger)",
So, I did the trace and it appears things are getting malformed when sending data? This is what the Exchange server is attempting to send.
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_369013E>], 192.168.0.x:11535->192.168.0.y:5061REGISTER sip:geosoft.com SIP/2.0
FROM: <sip:amazing.user@geosoft.com>;epid=AFEB7BEF65;tag=e284bb12fb
TO: <sip:amazing.user@geosoft.com>
CSEQ: 1 REGISTER
CALL-ID: 0506b0822fa640c1a2975f8ebcb60c3b
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 192.168.0.x:11535;branch=z9hG4bK40a2e4b3
CONTACT: <sip:exch2013.geosoft.com:5075;transport=Tls;ms-opaque=91a37e8f3d315774>;methods="Service,Notify,Benotify,Message,Info,Options,Invite";+sip.instance="<urn:uuid:494c7ee5-e77e-52a8-86dc-a8a029d396c8>";text;audio;video;image
CONTENT-LENGTH: 0
EVENT: Registration
EXPIRES: 1800
SUPPORTED: gruu-10
SUPPORTED: ms-forking
SUPPORTED: msrtc-event-categories
SUPPORTED: ms-userservices-state-notification
SUPPORTED: ms-cluster-failover
USER-AGENT: RTCC/5.0.0.0 OWA/15.00.0913.021
This is the error it's getting back:
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_369013E>], 192.168.0.x:11535<-192.168.0.y:5061SIP/2.0 400 Invalid Contact information
FROM: <sip:amazing.user@geosoft.com>;epid=AFEB7BEF65;tag=e284bb12fb
TO: <sip:amazing.user@geosoft.com>;tag=37D128C333B73F1A9B13488593AFDD4D
CSEQ: 1 REGISTER
CALL-ID: 0506b0822fa640c1a2975f8ebcb60c3b
VIA: SIP/2.0/TLS 192.168.0.x:11535;branch=z9hG4bK40a2e4b3;ms-received-port=11535;ms-received-cid=5B37800
CONTENT-LENGTH: 0
SERVER: RTC/5.0
ms-diagnostics: 1018;reason="Parsing failure";source="lync2013.geosoft.com"
Is this a bug? I've been at this for 3 days replacing certificates and resetting Lync user accounts, but now I'm having doubts.