While working on setting up a SIP Trunk for Lync 2013, I kept encountering an error in my SIP traces. This was true if Lync was using a gateway (in this case and AudioCodes Mediant 1000B), or was connecting directly to the ITSP.
The error in the trace was “503 Service Unavailable” and the detail showed:
10014;reason=”An internal exception received while processing the incoming request”;component=”MediationServer”;Exception=”An exception has been thrown in processing BeginApplyMediaLines”
Everything with the topology and trunk configuration looked correct and most Lync services were behaving correctly. It’s that “most” that should have been my clue. Application sharing to federated partners wasn’t working either, even though IM and presence were.
The resolution for both turned out to be incredibly simple. The Front End servers could not resolve the name of Edge Pool.
Now, I can understand why that would impact federated application sharing, but outbound calls as well? That was a bit surprising.
So, don’t forget to ensure name resolution and connectivity to/from your Lync Front End and Edge Pools. It’ll make your life easier in the long run.
Shane Skriletz, PEI