locked
Lync 2010 & Lync 2013 Coexistance - Audio Call not working from External Users RRS feed

  • Question

  • Hi,

    I have Lycn 2013 & Lync 2010 Coexistance , everthing thing is working from but Lycn 2010/2013 Users are not able to make audio call to external 2013 users , same external 2013 users are not able to make call to lycn 2010 and lync 2010 users. While external 2013 users can call to external 2013 users without any problem.

    EDGE 2010 is being used with Lync 2013 , Call are showing connecting status and then disconnect. any idea from where i should start troubleshooting

    Regards

    Usman Ghani


    Usman Ghani - MCITP Exchange 2010

    Friday, September 12, 2014 7:59 PM

Answers

  • Is there a 2013 Edge in the environment currently?  If everything is configured to flow through the 2010 Edge (which is forwards compatible and should work just fine with 2013), I'd check the firewall ports and routes to make sure that traffic can flow between the edge and the 2013 front end pool as seen in http://technet.microsoft.com/en-us/library/gg425891(v=ocs.14).aspx and ensure that the 2013 front end pool can resolve the FQDN of the Lync 2010 edge pool (because it's not a domain member, it's not always in DNS).

    I'm assuming the policies are the same on both sides, and internal to internal communicates work as well as the external to external communications as you've noted.  Can you confirm that Lync 2010 users externally can audio chat with both internal 2010 and 2013 users.

    In the topology builder, is the same edge pool for media set for the new 2013 pool as the old? 


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications



    • Edited by Anthony CaragolMVP Friday, September 12, 2014 9:11 PM
    • Proposed as answer by Eason Huang Monday, September 15, 2014 6:57 AM
    • Marked as answer by Eason Huang Monday, September 22, 2014 2:23 AM
    Friday, September 12, 2014 9:00 PM
  • Thanks every one , issue has been fixed by restarting EDGE Server.

    Usman Ghani - MCITP Exchange 2010

    • Marked as answer by Eason Huang Monday, September 22, 2014 2:23 AM
    Monday, September 15, 2014 10:11 AM

All replies

  • Is there a 2013 Edge in the environment currently?  If everything is configured to flow through the 2010 Edge (which is forwards compatible and should work just fine with 2013), I'd check the firewall ports and routes to make sure that traffic can flow between the edge and the 2013 front end pool as seen in http://technet.microsoft.com/en-us/library/gg425891(v=ocs.14).aspx and ensure that the 2013 front end pool can resolve the FQDN of the Lync 2010 edge pool (because it's not a domain member, it's not always in DNS).

    I'm assuming the policies are the same on both sides, and internal to internal communicates work as well as the external to external communications as you've noted.  Can you confirm that Lync 2010 users externally can audio chat with both internal 2010 and 2013 users.

    In the topology builder, is the same edge pool for media set for the new 2013 pool as the old? 


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications



    • Edited by Anthony CaragolMVP Friday, September 12, 2014 9:11 PM
    • Proposed as answer by Eason Huang Monday, September 15, 2014 6:57 AM
    • Marked as answer by Eason Huang Monday, September 22, 2014 2:23 AM
    Friday, September 12, 2014 9:00 PM
  • For Audio call would do peer to peer. Audio call between internal-external is that the external user will hit TCP 5061 to the Access Edge Server and will be provided with either UDP 3478 or TCP 443 for the Audio/Video Edge, and the internal user will contact to the A/V Edge Server’s Internal NIC over UDP 3478 or TCP 443 as well for the first scenario.

    Therefore, you can try to double check the port for edge servers. You can do a netstat -an to see your server listening on UDP 3478 and utilize netcat which can attempt telnet to UDP by using netcat -u host 3478.

    Here is a great blog how to test the listening port for edge:

    http://blog.schertz.name/2012/07/understanding-lync-edge-server-ports/


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer" Mai Ali | My blog: Technical | Twitter: Mai Ali

    • Proposed as answer by Eason Huang Monday, September 15, 2014 6:52 AM
    Saturday, September 13, 2014 12:08 PM
  • Hi,

    From your description, did you mean internal Lync 2010/2013 users couldn’t make call to external Lync 2013 users, and external Lync 2013 users couldn’t make calls to internal Lync 2010 users?

    If it is the case, please also double check if IM could work normally in the situation above?

    If IM works, it may be the issue of Edge Server ports.

    You can refer to the link about Lync Server 2010 Port Ranges and Audio/Media Negotiation, in it there are A/V connectivity scenarios such as Two Users Internal to the Network, Two Users on the Internet, A/V through the Web Conferencing Server:

    http://www.shudnow.net/2010/12/06/lync-server-2010-port-ranges-and-audiomedia-negotiation/

    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.

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    Monday, September 15, 2014 6:58 AM
  • Thanks every one , issue has been fixed by restarting EDGE Server.

    Usman Ghani - MCITP Exchange 2010

    • Marked as answer by Eason Huang Monday, September 22, 2014 2:23 AM
    Monday, September 15, 2014 10:11 AM