locked
Lync Slow call setup with edge RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have an issue where the call setup takes a long time when edge is enabled for the site. When user makes a Lync  to Lync call the client beebs 2 times, when clients makes an external call throught the PSTN the client beebs 6 times. When we disable the association with the edge server there are no time out and call setup works very quick.

    Can some one tell why it takes such a long time for the client call setup is complete when edge is enabled? Is it possible to enable the association but prefend the client to check the edge server before making a call?

    Monday, July 2, 2012 8:04 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have typically seen this issue when the Edge server is misconfigured or firewall is blocking some of the call set-up ports for ICE.  Can you elaborate on your Edge configuration?:

    • NIC configuration with subnet information
    • Default gateway configuration
    • static routes configured
    • Number of Edge servers deployed
    • If multiple Edge servers, how are they load balanced (HLB or DNS)

    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    • Proposed as answer by mmcgille Monday, July 2, 2012 8:31 PM
    • Marked as answer by Robster_1 Tuesday, July 3, 2012 6:27 AM
    Monday, July 2, 2012 2:02 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have typically seen this issue when the Edge server is misconfigured or firewall is blocking some of the call set-up ports for ICE.  Can you elaborate on your Edge configuration?:

    • NIC configuration with subnet information
    • Default gateway configuration
    • static routes configured
    • Number of Edge servers deployed
    • If multiple Edge servers, how are they load balanced (HLB or DNS)

    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    • Proposed as answer by mmcgille Monday, July 2, 2012 8:31 PM
    • Marked as answer by Robster_1 Tuesday, July 3, 2012 6:27 AM
    Monday, July 2, 2012 2:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tim

    The firewall config at customer side was the problem indeed. We found out that network support of the customer closed some ports. Thanks for thinking with me!!!

    Monday, July 2, 2012 6:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    So the issue has been fixed now?

    Regards,

    Kent Huang

    TechNet Community Support ************************************************************************************************************************

    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.


    • Edited by Kent-Huang Tuesday, July 3, 2012 2:58 AM
    Tuesday, July 3, 2012 2:57 AM