Hi All,

Running into this issue, where the first call made from a Lync Client to a federated partner like MSFT fails. The call shows connecting, and then fails citing network issues. In the logs, I can see the error: A federated call failed to establish due to a media connectivity failure where both endpoints are internal". I can see the Local and Remote SITE and MR IP address just fine. 

Also on my edge server the persistent route is already configured with a subnet mask of 255.255.0.0 and a default gateway as well. 

The Edge Server has the latest CU installed, and we are using three different IPs for A/V, Web and SIP. 

I saw blogs online, where everyone pointed to the persistent route being missing, Which is not in my case. Am i missing on something here. I really doubt it to be route issue, because the very next call goes through and the calls after that too. If i wait for say about thirty minutes. the first call fails again with the same error code as mentioned above.. and the rest of the calls work just fine. 

Just to update, when I am logged in Externally and make calls to federated users, it works fine in the first call itself. When logged in Internally it fails the first time and then works the next time. 

HI Eason, the Edge Server internal interface has no Default gateway. The default gateway is only for the External interface. 

I am talking about the persistent route on the Edge Server, 

Here is what my persistent route is:

Network Address 0.0.0.0    Netmask: 0.0.0.0    Gateway Address: 82.X.X.X  Metric Default

Network Address: 10.50.X.X  Netmask: 255.255.0.0  GAteway Address: 10.50.Y.Y  Metric 1.

Is there something that i am missing. 

Also on my edge server the persistent route is already configured with a subnet mask of 255.255.0.0 and a default gateway as well. 

Hi,

From your description above, did you mean you set the default gateway in the internal interface of the Edge Server?

If it is the case, please change the default gateway and set it in the external interface of the Edge Server, for Edge Server internal interface, it is not needed to set default gateway.

Best Regards,

Eason Huang

Hi,

please do route print and check all route added to Your edge server.Then check if network for failing computer is in the list of Your edge server.

This is what my route print looks like. I think its fine. Why just the first call fails and then second call goes through. 

Active Routes:

Network Destination        Netmask          Gateway       Interface  Metric

          0.0.0.0          0.0.0.0   82.199.155.225   82.199.155.227    266

        10.50.0.0      255.255.0.0     10.50.30.129     10.50.30.175     11

     10.50.30.128  255.255.255.192         On-link      10.50.30.175    266

     10.50.30.175  255.255.255.255         On-link      10.50.30.175    266

     10.50.30.191  255.255.255.255         On-link      10.50.30.175    266

   82.199.155.224  255.255.255.224         On-link    82.199.155.227    266

   82.199.155.227  255.255.255.255         On-link    82.199.155.227    266

   82.199.155.228  255.255.255.255         On-link    82.199.155.227    266

   82.199.155.229  255.255.255.255         On-link    82.199.155.227    266

   82.199.155.255  255.255.255.255         On-link    82.199.155.227    266

        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306

        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306

  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306

        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306

        224.0.0.0        240.0.0.0         On-link      10.50.30.175    266

        224.0.0.0        240.0.0.0         On-link    82.199.155.227    266

  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306

  255.255.255.255  255.255.255.255         On-link      10.50.30.175    266

  255.255.255.255  255.255.255.255         On-link    82.199.155.227    266

===========================================================================

Persistent Routes:

  Network Address          Netmask  Gateway Address  Metric

          0.0.0.0          0.0.0.0   82.199.155.225  Default

        10.50.0.0      255.255.0.0     10.50.30.129       1