Home > Lync > Lync 2013 Trunks and EnableFastFailover

Lync 2013 Trunks and EnableFastFailover

This post was inspired by a troubleshooting session that happened just before the long Memorial Day Weekend here in the states. We had just moved our pilot users over to our Lync 2013 pool a day before when they started reporting issues calling certain numbers. What was interesting was not all calls were failing. Only international calls and a few mobiles were failing. National calls were working fine. Nothing changed call flow-wise so it had me a bit stumped.

To properly set the background, our calls were going from Lync to a Cisco voice gateway and then out an E1 to the carrier.  We tested a call from Lync 2010 and the call would succeed:


You can see at about 14 seconds into the call we get back our first 200 Ok. Next, here is a call from Lync 2013. User has all of the same voice policies, dial plan, routes, etc.


We dug our heels in and got the Cisco guy on the line and he watched what was being sent to the carrier and he didn’t see anything wrong but kept seeing Lync send a Cancel so the call would fail. What you don’t see in the above image is that we would start trying to hit the backup voice gateway which only becomes active if the first doesn’t work.

Well, it took longer than I would like to admit before we all noticed the call was failing at exactly 10 seconds everytime. Consistency like this is never coincidence. I started looking at the trunk configuration settings in Lync 2013 and lo and behold, I found this:

EnableFastFailoverTimer Optional Boolean When set to True, outbound calls that are not answered by the gateway within 10 seconds will be routed to the next available trunk; if there are no additional trunks then the call will automatically be dropped. In an organization with slow networks and gateway responses, that could potentially result in calls being dropped unnecessarily.

The default value is True.

We set the EnableFastFailoverTimer to False and our calls started to go through. It appears that this particular carrier was just taking a long time to setup International calls along with certain mobiles.

So, how did we set it? We used:

Set-CsTrunkConfiguration -Identity "our site specific trunk" -EnableFastFailoverTimer $false"

We could have also done it via the Lync Management Console by unchecking Enable outbound routing failover timer check box in the Trunk Configuration:




Categories: Lync Tags:
  1. soder
    June 5, 2014 at 5:13 am

    For me, this failover timer caused more connectivity problem, than it solved. So as a generic rule I disable this feature for all deployments.

  2. June 5, 2014 at 10:27 am

    Just found the same issue today, but disabling fast Failover has a drawback on my case.
    I have multiple sip trunks for the Mediation Server to try. If you disable this Setting, the call attempt will stay indefinetly on the first Gateway and will never be retried to the next Gateway if there’s a Problem with the first.
    On this case the solution is to increase the timeout value for the Mediation servers

  3. Markus
    June 9, 2014 at 1:50 am

    @Luis Can you please clarify what you mean by ” increase the timeout value for the Mediation servers”

  4. Rogers
    February 4, 2015 at 7:43 am

    I just hit this today. Your article sorted out my issue but i wish there was a way to adjust the timers instead of disabling the feature

    • Jeff
      February 12, 2016 at 7:03 am

      There is OutboundRouting.exe.config in
      C:\Program Files\Microsoft Lync Server 2013\Server\Core

      You want to adjust
      It’s 10 seconds by default.

      I haven’t messed with this setting, my concern with changing it was that future updates may change / reset back to 10000.

  1. No trackbacks yet.

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 )

Google photo

You are commenting using your Google 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 )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: