Media connectivity failure when both endpoints are internal


An interesting issue I had recently when trying to connect an audio call to a federated partner.

IM and Presence were working but no audio or video. The attempt states connecting and then fails. A quick trip to the monitoring server, looking at the BYE for the call in questions the Diagnostic header 25 is found

Reason= “A federated call failed to establish due to media connectivity failure when both endpoints are internal” & ICEWarn=0x40003a0

ice01

Certainly a strange error since I am trying the call from the LAN at company A to a Lync user on the LAN at Company B, certainly not both internal.

Grabbing the Lync Logs from the Lync client I was keen to seen the candidate negotiation and more importantly the selected candidate pair as this would reveal the path that was selected for the audio. Perhaps that would help me understand why the error reports both users as internal

Using snooper to open the logs I start a search for a=remote-candidate (that’s the marker for the selected candidate)

The last OK message for the call in question should show the selected candidate.

Just after the a=crypto there should be an a=remote-candidate…BUT its missing!

ice02

Right, so what reasons could cause ALL the candidates to fail?

  1. Perhaps there are ports blocked
  2. Could be routing
  3. Maybe a topology error

My vote goes to routing as the error states that both endpoints are intenal and that sounds like some funky routing getting the candidate logic all confused.

So, what does the Edge Server consider internal and external?

Checking the Edge server I found the following:-

Internal facing interface

IP 10.20.30.10   Subnet 255.255.255.0   Default Gateway None

External facing Interface

IP 10.20.20.10/11/12   Subnet 255.255.255.0   Default Gateway 10.20.20.1

No problems there, so checking the persistent static route I find the following:-

2015

Notice how in this instance the Netmask defined as a Class B actually includes the Internal and External facing IP’s of the Edge Server and thus the confusion in the error messages.

Once this was corrected the traffic flow was no longer an issue

 

Advertisements

About Paul B

My name is Paul Bloem and I am employed at Lexel Systems in New Zealand as a Principal Consultant for Unified Communications. I have been working on enterprise voice solutions for over 20 years. My first 10 years were spent working for a Telco in South Africa (Telcom SA). This is where all the groundwork happened as I was exposed to just about every aspect of telecommunication you could imagine. I develop an interest in PBX technologies and eventually became the go-to guy. Next, I had a 10 year run at Siemens South Africa, most of my time there was as a Technical Trainer. During this time VoIP hit the world stage, I had the privilege of introducing VoIP both as H.323 and later SIP across the Siemens HiPath 4000 solution stack. In 2008 I immigrated to New Zealand with my newly attained MCSE, I was ready to go where no PBX Techie had gone before. I was employed to explore OCS 2007 and that was pretty much the beginning of the end for me. I have been working on OCS and Lync ever since. My current role focuses exclusively on Lync and associated technologies.. That includes pre-sales, consulting, architecture and design, training and support. I even get to play in the development space from time to time - focus on play ;-) I was nominated as a Microsoft VTSP for Lync early in 2013 and also awarded Microsoft's MVP award for Lync in 2014.
This entry was posted in Uncategorized and tagged . Bookmark the permalink.

One Response to Media connectivity failure when both endpoints are internal

  1. Pingback: ms-client-diagnostics: 25; reason=”A federated call failed to establish due to a media connectivity failure where both endpoints are internal | UC Sorted

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