locked
Lync Peer to Peer audio RRS feed

  • Question

  • Hi all

    I have a question regarding Lync peer to peer audio that I cannot find the answer to.

    In a scenario whereby one user is external and the other is internal and both are using the
    Lync client does the internal user need to access the edge server’s external av port in
    order for audio to work?

    Thanks in advance

    Alan


     


    Wednesday, November 7, 2012 2:49 PM

Answers

  • Hi,

    When one user is internal and one user is external , they will attempt peer to peer. 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. UDP 3478 is preferred even if the connection test for TCP 443 and UDP 3478 were successful in testing. Because this is technically peer to peer, the internal user will NOT connect to the MCU on the Front End but will instead connect directly to the A/V Edge Server’s Internal NIC over UDP 3478 or TCP 443 as well.  The Front End A/V MCU will not be used in this scenario.  When you add a 3rd person to the conversation, the external user will connect to the Front End Server’s A/V MCU in which the A/V Edge will proxy this data for the user, and the internal users will connect to the Front End A/V MCU instead of the Internal Edge NIC.


    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.

    • Proposed as answer by Kent-Huang Tuesday, November 20, 2012 10:07 AM
    • Marked as answer by Alan McBurney Monday, November 26, 2012 11:02 PM
    Thursday, November 8, 2012 3:22 AM

All replies

  • The internal user does NOT need to access the edge servers external AV port. The internal user will communicate with the Edge via the Edge internal interface.
    Wednesday, November 7, 2012 3:07 PM
  • Alan thanks for the response

    So why does some documentation refer to publishing av.domain.com in internal DNS with the Edge Servers Public AV IP? 

    Wednesday, November 7, 2012 7:01 PM
  • I don't believe the documentation should say that. Can you share the document or a link? This actually used to be the case prior to Lync because the AV service on the Edge server need to be able to resolve the FQDN with which it was associated but because of how Lync relies on the topology builder this is no longer the case.

    Wednesday, November 7, 2012 7:05 PM
  • Hi,

    When one user is internal and one user is external , they will attempt peer to peer. 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. UDP 3478 is preferred even if the connection test for TCP 443 and UDP 3478 were successful in testing. Because this is technically peer to peer, the internal user will NOT connect to the MCU on the Front End but will instead connect directly to the A/V Edge Server’s Internal NIC over UDP 3478 or TCP 443 as well.  The Front End A/V MCU will not be used in this scenario.  When you add a 3rd person to the conversation, the external user will connect to the Front End Server’s A/V MCU in which the A/V Edge will proxy this data for the user, and the internal users will connect to the Front End A/V MCU instead of the Internal Edge NIC.


    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.

    • Proposed as answer by Kent-Huang Tuesday, November 20, 2012 10:07 AM
    • Marked as answer by Alan McBurney Monday, November 26, 2012 11:02 PM
    Thursday, November 8, 2012 3:22 AM