locked
Lync - Voice Not working in external Network - Strange issue RRS feed

  • Question

  • Hi

    We have installed Lync in a Windows 2008 R2 Server in a VM. We dont have a edge server or a reverse proxy. We have added a NIC card in the server. We have mapped to an external Public  IP address. Everything is working fine. The problem is that the voice calls are working as long as the people who are communciating are within our office network. Once a partner goes out of office network the voice calls are failing, even desktop sharing is failing indicating "calls are failing due to network issues"

    Strangely if both the partners are outside office network (both at home), voice calls are working fine. This is where the issue is pretty confusing. Any help or suggestions please?

    Regards

    Sriniraj

    Sunday, July 1, 2012 12:57 PM

Answers

  • This is an unsupported configuration so first don't expect to get it working consistently or even at all. Frankly from a security perspective even if you could get it to work you should not be doing this. With that said the reason that internal only calls or external only calls work is because they must be Peer to Peer and the users are communicating directly with each other. The question as to why internal to external is not working is entirely due to how you have configured the VM to use NAT. Lync must not be able to establish viable TURN/STUN candidates in order to relay through the "public" IP/NIC.

    • Proposed as answer by Sean_Xiao Tuesday, July 3, 2012 6:25 AM
    • Marked as answer by Sean_Xiao Monday, July 9, 2012 2:10 AM
    Sunday, July 1, 2012 2:03 PM
  • You will Need a Edgeserver in your Network for communication from internal to external. Two Client external communicate as a peer to peer call, so there is no network issue with the media stream, only from internal to external

    regards Holger Technical Specialist UC


    Sunday, July 1, 2012 5:01 PM
  • Hi,

    It is not a supported scenario. A edge server is needed for external remote users. Please deploy a edge server in your current lync infrastructure.

    About more Edge server deployment, please refer this document:http://technet.microsoft.com/en-us/library/gg398918


    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.

    • Marked as answer by Sean_Xiao Monday, July 9, 2012 2:10 AM
    Friday, July 6, 2012 7:39 AM
  • of course it will not work, it's  not supported scenario that you have,

    why not working? i'll try to explain

    when you have call from lync client to lync client its peer t peer connection or it routes using edge server.

    when your lync client is in external network and he is trying to connect in internal client with voice or app sharing, you have not peer to peer connection and you have not edge , if you would have edge your traffic will routed using edge.

    Saturday, July 7, 2012 11:11 AM

All replies

  • This is an unsupported configuration so first don't expect to get it working consistently or even at all. Frankly from a security perspective even if you could get it to work you should not be doing this. With that said the reason that internal only calls or external only calls work is because they must be Peer to Peer and the users are communicating directly with each other. The question as to why internal to external is not working is entirely due to how you have configured the VM to use NAT. Lync must not be able to establish viable TURN/STUN candidates in order to relay through the "public" IP/NIC.

    • Proposed as answer by Sean_Xiao Tuesday, July 3, 2012 6:25 AM
    • Marked as answer by Sean_Xiao Monday, July 9, 2012 2:10 AM
    Sunday, July 1, 2012 2:03 PM
  • You will Need a Edgeserver in your Network for communication from internal to external. Two Client external communicate as a peer to peer call, so there is no network issue with the media stream, only from internal to external

    regards Holger Technical Specialist UC


    Sunday, July 1, 2012 5:01 PM
  • Thanks Alanmad
    Monday, July 2, 2012 6:21 AM
  • Thanks much Holger
    Monday, July 2, 2012 6:21 AM
  • Hi,

    It is not a supported scenario. A edge server is needed for external remote users. Please deploy a edge server in your current lync infrastructure.

    About more Edge server deployment, please refer this document:http://technet.microsoft.com/en-us/library/gg398918


    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.

    • Marked as answer by Sean_Xiao Monday, July 9, 2012 2:10 AM
    Friday, July 6, 2012 7:39 AM
  • of course it will not work, it's  not supported scenario that you have,

    why not working? i'll try to explain

    when you have call from lync client to lync client its peer t peer connection or it routes using edge server.

    when your lync client is in external network and he is trying to connect in internal client with voice or app sharing, you have not peer to peer connection and you have not edge , if you would have edge your traffic will routed using edge.

    Saturday, July 7, 2012 11:11 AM
  • Hi

    As per the suggestions in the forum, we have a added an Edge server VM and added two NIC 's. One configured to the public IP and the other one to the internal ip, still the voice calls from internal to external is not working, what are we doing wrong here, any suggestions please.

    Thursday, July 12, 2012 4:31 AM
  • Have you check your Firewall for the Edge Server ports?

    Also did you configure your external DNS for the Edge Server?

    Here is a good link for the installation

    http://ocsguy.com/2010/11/21/deploying-an-edge-server-with-lync/


    regards Holger Technical Specialist UC

    Thursday, July 12, 2012 5:32 AM