In a Hybrid migration environment with Exchange On-Prem / Lync On-Prem and Office 365, I encountered two errors that actually come from misconfiguring the client’s Lync On-prem environment when setting up unified messaging on Office 365.
My post below will explain how to solve its mistakes and I hope it will help some people.
To ensure that your Lync and Office365 environment is properly configured, follow the guide below:
Migration date: April 01, 2015
Migration Type: Cutover Exchange 2010 + Lync Server 2010
TL_INFO(TF_PROTOCOL) [0]06EC.0338::03/23/2015-13:52:42.936.00004043 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 2296834163
Instance-Id: 00007BA3
Direction: incoming;source=”internal edge”;destination=”external edge”
Peer: CONTOSOLYNCFE01.contoso.com:62157
Message-Type: request
Start-Line: BYE sip:uminternal.um.prod.outlook.com:5066;ms-fe=BN3PR11MB0258.namprd11.prod.outlook.com;transport=Tls SIP/2.0
From: <sip:5145551234;phone-context=CONTOSO_Global@contoso.com;user=phone>;epid=243D1C1F9C;tag=f2c0fa14b
To: <sip:+5145554321@contoso.com;user=phone>;epid=B0DAFC866A;tag=2fba11c27
CSeq: 4188 BYE
Call-ID: 7de706e8-f352-4432-87db-c8cded3ea3c9
Via: SIP/2.0/TLS 192.168.1.21:62157;branch=z9hG4bK1D42DA88.0FE7333822E35C4E;branched=FALSE
Max-Forwards: 69
Via: SIP/2.0/TLS 192.168.1.21:62509;branch=z9hG4bK5829a05a;ms-received-port=62509;ms-received-cid=283800
Route: <sip:CONTOSOLYNCEDGE01.contoso.com:5061;transport=tls;opaque=state:Si;lr>,<sip:exap.um.outlook.com:5061;transport=tls;epid=B0DAFC866A;lr;ms-key-info=AAEAAWNkNZ52Q7PLZmXQATfPdNPzVASi5184zpoBaEerlIbtXy0Vl9catHmQazIWLWXvmCou-dQLXwsatbCV3r4e-9gv9UM-vd-mDRN9ZSvZy4X5fx88lSk57Ibs5S9neSb3FZ_YbTx-9DEGs4PUBLO9daUCz0wwcEorpbfRU-L4Oropjg4GjOLMsKL2bbrvdD_vorEAjqKQCoidxYytO2IH6ZWBiiBvRda8vfk2JAkm4sMckrP3LHNxGtCsK4Hxu8-AAgKBhLcJNh6yE6M2u_qFWEQ0n0m0PkG9aNL4Y6p6SsCYUhzUIPKpme0IWVMdjwBoE3hqNytQe5FMl3_7DIYF6UEswvKQ8CSKIpLkxrhnoW5YBz0HXKYeAqli9OAW39Jng8oN66LBvj9E1bAq0IuSTeHHafXXRuUVL9FQi3IF-mRVyZs1NA3dyiK4rdcm5zVGBlchsgvwRIZcGtGrum45CXZmU_-5aHzDVKg8IMQcriAP3PuZN58yohnnJMPGWj6yueksFvVmLFuZLdirtVl8rmay3PPZZJ2TUUo8rYbBaJEL4VRx65f5B0gHqz9HJ6zC2SmfaNajMEbaBGxsMb4e3iItlB9wStm6SK0ibU9YB8mejF_h7JKu3DU2ITgDAJ-REdD3zC8cvRCAp_Vwvg7bs6xVZm-jF17hq985SSv3bon2QJgmIn8Lo2Q3es_a;ms-route-sig=eeCF5CeEZksvPfPo2DdcvvbnTwgBlFIE8dAfGt7defsuy08iqnJJcXOgAA>
CONTACT: <sip:CONTOSOLYNCFE01.contoso.com@contoso.com;gruu;opaque=srvr:MediationServer:A9DaPGztc1SvALSwWMd8XAAA;grid=c55432bfc80f4633b1d10cb93050f8e2>;isGateway
CONTENT-LENGTH: 0
SUPPORTED: ms-dialog-route-set-update
SUPPORTED: gruu-10
USER-AGENT: RTCC/4.0.0.0 MediationServer
P-ASSERTED-IDENTITY: “JOHN DELETRE”<sip:5145551234;phone-context=CONTOSO_Global@contoso.com;user=phone>
ms-diagnostics: 22;source=”CONTOSOLYNCFE01.contoso.com”;reason=“Call failed to establish due to a media connectivity failure when both endpoints are internal”;component=”MediationServer”;Exception=”Proxy side ICE connectivity check failed.”;ICEWarningFlags=”ICEWarn=0x80120,LocalSite=192.168.1.21:50362,RemoteSite=10.8.148.7:3257,RemoteMR=65.55.127.81:50670,PortRange=49152:57500,RemoteMRTCPPort=50670,LocalLocation=2,RemoteLocation=2,FederationType=0″
ms-diagnostics-public: 22;reason=”Call failed to establish due to a media connectivity failure when both endpoints are internal”;component=”MediationServer”;Exception=”Proxy side ICE connectivity check failed.”
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
Message-Body: –
$$end_record
Cause: After various tests and a little research on the internet, it turns out that this error occurs when your Front End Mediation service is not associated with your Edge server. You can check this by running Get-CsService -MediationServer:
Identity : MediationServer:CONTOSOLYNCFE01.contoso.com
Registrar : Registrar:CONTOSOLYNCFE01.contoso.com
EdgeServer: EdgeServer:CONTOSOLYNCEDGE01.contoso.com
SipServerPort : 5070
SipClientTcpPort : 5060
SipClientTlsPort : 5067
AudioPortStart : 49152
AudioPortCount : 8348
DependentServiceList : {PstnGateway:206.83.256.001}
ServiceId: 1-MediationServer-3
SiteId : Site:CONTOSO
PoolFqdn: CONTOSOLYNCFE01.contoso.com
Version: 5
Role : MediationServer
Resolution: In my case, the EdgeServer line was empty. To associate your Edge server with your Mediation service, execute the following command:
Set-CsMediationServer -identity “MediationServer:CONTOSOLYNCFE01.contoso.com” -EdgeServer CONTOSOLYNCEDGE01.contoso.com
Date of migration: April 17, 2015
Migration Type: Hybrid Exchange 2010 + Lync Server 2010
Cause: After various tests and a little research on the internet, it turns out that this error occurs when the DNS entry of type SRV _sipfederationtls._tcp.contoso.com is not configured in the local DNS.
Resolution: If you are in the same situation, simply add the local DNS entry making sure to put it in the default SIP domain.
