locked
4 - 6 Beeps before call is connected or ringing RRS feed

  • Question

  • Hi,

    We have a Lync 2010 deployment with 2 front end servers and an edge server.  Everything was working properly until we decided to start migrating our servers to Hyper-V.  We migrated one of our front end servers from VMWare to Hyper-V and everything was still working properly.  Next we migrated our Edge server and Lync SQL server from VMWare to Hyper-V.  This is when we started noticing the delay (4-6 beeps) in making phone calls.  Also, when answering calls from a response group there are 6 beeps before the call is connected.  We still have one front end server on VMWare.  Both VMWare and Hyper-V host servers are the same hardware.  While running the Lync Server Logging Tool it doesn't show any errors. 

    It only shows the following sequence (MediationServer, S4, and SIPStack logged):
    Response successfully routed
    Trying
    Response successfully routed
    Session Progress
    Response successfully routed
    Progress Report
    Trying
    Trying
    Ringing
    Response successfully routed
    Ringing
    Ringing
    Response successfully routed
    Ringing
    Session Progress
    Response successfully routed
    Session Progress
    Routed a request using signed route headers
    PRACK
    SIP OK

    This takes about 5 seconds before a PRACK is sent.  This happens for internal Lync calls as well as external calls through our DMG.  CPU and Memory usage are all low and nothing seems to be overloaded.  Can anyone help me troubleshoot this issue?

    Monday, July 8, 2013 7:47 PM

Answers

  • Check your static routes on the Edge server.

    What do you see when you run route print command?

    Thank you.



    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    The route print command looks normal.  I can ping externally through the External NIC (DMZ VLAN) and to my internal servers through the Internal NIC (Internal VLAN).

    Igor, I think you nailed it on the head.  Although I was able to ping externally and internally, I wasn't able to ping all of our subnets (the ones that the workstations are connected to).  After I added static routes to all of our subnets, phone calls started to instantly ring without any beeps.  I will now test the response groups to see if that helped them as well.  Thanks again.

    A little more info for the root cause:  We already had the static route added for the subnet, but it wasn't working because after the conversion to Hyper-V the interface number changed.  After recreating the static route using the new interface number it started working again.  Thanks again for everyone's help.

    • Edited by PChrist12 Tuesday, July 9, 2013 6:34 PM additional info
    • Marked as answer by PChrist12 Tuesday, July 9, 2013 6:37 PM
    Tuesday, July 9, 2013 5:05 PM
  • Check your static routes on the Edge server.

    What do you see when you run route print command?

    Thank you.



    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    • Marked as answer by PChrist12 Tuesday, July 9, 2013 5:06 PM
    Monday, July 8, 2013 9:40 PM

All replies

  • It looks like the clients have a problem to connect to the edge server, so you get this 4-6 beep.

    regards Holger Technical Specialist UC

    Monday, July 8, 2013 9:14 PM
  • Check your static routes on the Edge server.

    What do you see when you run route print command?

    Thank you.



    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    • Marked as answer by PChrist12 Tuesday, July 9, 2013 5:06 PM
    Monday, July 8, 2013 9:40 PM
  • Hi,

    i have seen the similler symptoms of one of my deployments on Hyper V. can you post what are the hardware spec that you have in Front end and Edge? specially the Processor cores that assigned. remember that when you virtualize, the capacity that can support will reduce in half compared to the Physical deployment. if you have a Monitoring server deployed, you would be able to see what's going on.

    Monday, July 8, 2013 11:47 PM
  • Hi,PChrist12

    Please check your virtual network setting on Edge and FE server to see if anything misconfigured.

    If still no luck,please read through this old case with similar symptom to see if the solution also applys to your issue.

    http://social.technet.microsoft.com/Forums/lync/en-US/1d90eb61-4a00-4e3b-b847-26bbab3f61c8/microsoft-lync-beeps-multiple-times-before-placing-the-call 

    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.

    Tuesday, July 9, 2013 8:53 AM
  • Check your static routes on the Edge server.

    What do you see when you run route print command?

    Thank you.



    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    The route print command looks normal.  I can ping externally through the External NIC (DMZ VLAN) and to my internal servers through the Internal NIC (Internal VLAN).
    Tuesday, July 9, 2013 2:23 PM
  • Hi,

    i have seen the similler symptoms of one of my deployments on Hyper V. can you post what are the hardware spec that you have in Front end and Edge? specially the Processor cores that assigned. remember that when you virtualize, the capacity that can support will reduce in half compared to the Physical deployment. if you have a Monitoring server deployed, you would be able to see what's going on.

    For the virtual Edge server I have 8GB RAM and 4 CPUs.  This was the same on VMWare.  For the Front End server I have 15GB RAM and 4 CPUs.  Again, same as it was on VMWare.

    Also, I do have a monitoring server deployed.  What do I need to look at?
    • Edited by PChrist12 Tuesday, July 9, 2013 2:27 PM Extra comment
    Tuesday, July 9, 2013 2:25 PM
  • Hi,PChrist12

    Please check your virtual network setting on Edge and FE server to see if anything misconfigured.

    If still no luck,please read through this old case with similar symptom to see if the solution also applys to your issue.

    http://social.technet.microsoft.com/Forums/lync/en-US/1d90eb61-4a00-4e3b-b847-26bbab3f61c8/microsoft-lync-beeps-multiple-times-before-placing-the-call 

    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.

    As far as I can tell all of the settings are the same as they were on VMWare.  I have not made any changes to DNS.
    Tuesday, July 9, 2013 2:26 PM
  • check the user activity report, take one of those calls and see if there's any potential connectivity issues in that report.

    Tuesday, July 9, 2013 2:42 PM
  • Check your static routes on the Edge server.

    What do you see when you run route print command?

    Thank you.



    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    The route print command looks normal.  I can ping externally through the External NIC (DMZ VLAN) and to my internal servers through the Internal NIC (Internal VLAN).

    Try to do tracert command to your internal servers.  I had problem once with this.


    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    Tuesday, July 9, 2013 3:50 PM
  • check the user activity report, take one of those calls and see if there's any potential connectivity issues in that report.

    Thanks very much for the help.

    Most of the calls show a green circle next to them.  A few have a yellow circle and these do not have an end time.  They have a response code of 487 and a diagnostic id of 5002.

    We have also received reports that when a user receives a call from a response group, since it takes so many seconds for the call to connect it will roll over to the next person in the queue, and the original user is finally connected but it disconnects the second user that tried to answer it.

    Tuesday, July 9, 2013 4:11 PM
  • Check your static routes on the Edge server.

    What do you see when you run route print command?

    Thank you.



    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

    The route print command looks normal.  I can ping externally through the External NIC (DMZ VLAN) and to my internal servers through the Internal NIC (Internal VLAN).

    Igor, I think you nailed it on the head.  Although I was able to ping externally and internally, I wasn't able to ping all of our subnets (the ones that the workstations are connected to).  After I added static routes to all of our subnets, phone calls started to instantly ring without any beeps.  I will now test the response groups to see if that helped them as well.  Thanks again.

    A little more info for the root cause:  We already had the static route added for the subnet, but it wasn't working because after the conversion to Hyper-V the interface number changed.  After recreating the static route using the new interface number it started working again.  Thanks again for everyone's help.

    • Edited by PChrist12 Tuesday, July 9, 2013 6:34 PM additional info
    • Marked as answer by PChrist12 Tuesday, July 9, 2013 6:37 PM
    Tuesday, July 9, 2013 5:05 PM