locked
Long delay before ringing after adding a separate IP for collocated Mediation Server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I added a NIC and gave it a separate IP for the Mediation Server, and then changed the front-end properties to have a Primary IP and a PSTN IP. The firewall now maps the public IP to the PSTN IP.

    After making this change we're now experiencing a long delay (30-45 seconds) between the UM Auto Attendent transferring the call and it actually ringing. It doesn't matter if you choose a response group or an individual, there's a long delay either way. Outbound calls are not affected at all by this, they ring right away.

    Since the calls eventually go through, I'm guessing this might be an issue with the internal DNS or something. Any ideas?

    Makolyte, Software Developer + System/Network Admin

    Friday, October 4, 2013 2:50 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    This seems to be fixed. In the Exchange Server UM Auto-Attendant settings i changed the IP to point to the Mediation Server's IP (aka the PSTN IP Address in the front-end settings). It previously had the front-end Lync server's FQDN, which on our internal DNS server maps to the front-end server's primary IP address in the Lync settings. There must have been a delay because the UM AA was talking to the front-end, which then had to send it off to the Mediation server. The delay problem seems to be cleared up now after changing that.

    Makolyte, Software Developer + System/Network Admin


    • Edited by Makolyte Tuesday, October 8, 2013 3:32 PM
    • Marked as answer by Kent-Huang Monday, October 21, 2013 12:23 PM
    Tuesday, October 8, 2013 3:29 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Please enable logging tool to reproduce the issue and get trace for troubleshooting.

    http://blog.schertz.name/2011/06/using-the-lync-logging-tool/

    Please also double check the Trunk configuration settings are correctly. You can refer to the following link:

    http://blog.insidelync.com/2013/04/sip-trunking-101-with-lync-server-2013/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Kent Huang
    TechNet Community Support

    Monday, October 7, 2013 5:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This seems to be fixed. In the Exchange Server UM Auto-Attendant settings i changed the IP to point to the Mediation Server's IP (aka the PSTN IP Address in the front-end settings). It previously had the front-end Lync server's FQDN, which on our internal DNS server maps to the front-end server's primary IP address in the Lync settings. There must have been a delay because the UM AA was talking to the front-end, which then had to send it off to the Mediation server. The delay problem seems to be cleared up now after changing that.

    Makolyte, Software Developer + System/Network Admin


    • Edited by Makolyte Tuesday, October 8, 2013 3:32 PM
    • Marked as answer by Kent-Huang Monday, October 21, 2013 12:23 PM
    Tuesday, October 8, 2013 3:29 PM