locked
Intermittent Outbound Calling RRS feed

  • Question

  • We have an issue with newly deployed stand-alone Mediation servers and an AudioCodes Mediant 1000 where the Front End (a Standard Edition for testing) logs the following events when attempting an outbound call:

    A PBX gateway has been marked as down.

    Gateway name: lync-mediation.domain.company.loc.

    Cause: A gateway failed to respond to a request within allotted time or was unable to route the request due to some error.

    Resolution:

    Verify that the gateway is up and can respond to calls.

    A call to a PSTN number failed due to non availability of gateways.

    Closely followed by:

    Called Number: +12345678910

    Phone Usage: Default Usage

    Route: LocalRoute

    CallId: 2d19blah252d44d59d9blah96ba92b53

    Cause: All gateways available for this call are marked as down.

    Resolution:

    Verify that these gateways are up and can respond to calls.

    However, every once in a while the Front End will suddenly see the gateway as being available and outbound calls will work.  Inbound calls to Lync and calls to UM through that same gateway work fine.

    This is a Lync RTM environment (no CU yet), Windows 2008 SP2, AudioCodes Mediant 1000 software version 6.20A.022.003.  Windows Firewall is off on all Lync servers except the Edge.  We do have a hardware load balanced Mediation server pool but even bypassing that this happens.

    Any help is appreciated.  Thanks.


    Friday, May 13, 2011 2:05 PM

Answers

  • The problem was a misconfiguration in the f5.  The right ports were open but the monitors on those ports were configured incorrectly.  I worked with that group to straighten that out and it has been fine.  Thanks.
    • Marked as answer by MacGeever Thursday, July 14, 2011 4:52 PM
    Thursday, July 14, 2011 4:52 PM

All replies

  •  

    What would be most helpful is to capture a packet trace of this happening and see the messages between the mediation and the Audiocodes.  Preferably from both sides.  The Audiocodes has a message trace tool in the Web admin console, as does Lync.  You'll be able to see what the exact error is, or see that the Call attempt indeed isn't making it to the Audiocodes.

     


    Thomas Kisner, MCITP -- http://thelync.net
    • Proposed as answer by Sharon.Shen Wednesday, May 18, 2011 8:08 AM
    Friday, May 13, 2011 3:22 PM
  • Hi,

    Do you configure 2 virtual gateways interacting with the multiple Media Servers?To solve multiple Mediation Servers interacting with the same gateway peer entity, you need to configure multiple virtual gateways. Each gateway would be associated with a different FQDN, which DNS would resolve to the same IP address.And the same policy should be associated with all virtual gateways.

    More information please check: http://technet.microsoft.com/en-us/library/gg398971.aspx

    Hope this useful!

    Regards,

    Sharon

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Sharon.Shen Friday, May 20, 2011 12:37 PM
    Wednesday, May 18, 2011 8:08 AM
  • Hi,MacGeever,

    Any updates on this issue?

    We will really appreciate if you kindly sharing the solution or something about it.

    Regards,

    Sharon


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, May 20, 2011 12:40 PM
  • We do not have multiple gateways.  We have two Mediation servers behind an F5 load balancer and a singled AudioCodes Mediant 1000.  If I change the hosts file on the Front End to talk to a single Mediation server calls work.  I have determined the intermittent performance is when the F5 is involved.  All ports appear to be opened properly.  Given the two errors above I am wondering what ports it might be using to check the gateway or how that is done to make sure we didn't miss something.
    Monday, May 23, 2011 6:03 PM
  • The problem was a misconfiguration in the f5.  The right ports were open but the monitors on those ports were configured incorrectly.  I worked with that group to straighten that out and it has been fine.  Thanks.
    • Marked as answer by MacGeever Thursday, July 14, 2011 4:52 PM
    Thursday, July 14, 2011 4:52 PM