locked
Cannot make peer-to-peer call between two internal endpoints RRS feed

  • Question

  • Hi all, I can't make peer-to-peer call between two internal endpoints, and get the below failure information from Report. May I know how to troubleshoot this problem, is that related to port issue? Thank you.

    Request:
    BYE
    Response:
    200
    Diagnostic ID:
    22
    Category:
    Unexpected
    Component:
    Common
    Reason:
     
    Call failed to establish due to a media connectivity failure when both endpoints are internal
    Description:
     
    The call failed to connect because a media path could not be established between the two internal endpoints. This can be caused by network performance issues affecting the endpoints. Correlation of such failures with individual networks or endpoints can indicate potential deployment issues.

     

    Report time:
    12/20/2011 6:11:35 PM
         
     
    Response code:
    200
    Diagnostic ID:
    22
     
     
    Request type:
    BYE
    Content type:
       
     
    Source:
     
    Application:
       
     
    From user URI:
    To user URI:
     
     
    From user agent:
    UCCAPI/4.0.7577.314 OC/4.0.7577.314 (Microsoft Lync 2010)
     
     
    Diagnostic header:
    22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal"; CallerMediaDebug="application-sharing:ICEWarn=0x80020,LocalSite=192.168.57.20:50048,RemoteSite=10.2.13.103:50043,RemoteMR=x.x.x.x<real IP address>:50911,PortRange=50040:50049,RemoteMRTCPPort=50911,LocalLocation=2,RemoteLocation=2,FederationType=0"

     

    Tuesday, December 20, 2011 10:27 AM

Answers

  • Do the two lync client calls access via VPN?

    If you use Hardware load balancer for Lync FE pool, please make sure the necessary ports are opend on it.

    Run get-CsconferencingPolicy to check the AudioBitRateKb value is 200. If not, please change it to 200.


    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.


    • Edited by Sean_Xiao Thursday, December 22, 2011 9:31 AM
    • Proposed as answer by Sean_Xiao Tuesday, December 27, 2011 1:42 AM
    • Marked as answer by Sean_Xiao Wednesday, December 28, 2011 4:44 AM
    Thursday, December 22, 2011 9:30 AM

All replies

  • Hi Aiya,

    Can you check all required ports are allowed in internal firewall ?

    Have a look at client port range . http://technet.microsoft.com/en-us/library/gg398833.aspx

    Thanks

    Tuesday, December 20, 2011 11:42 AM
  • Aiya,

    The clients will try to make a point to point (direct) connection for this so, you should have seen attempts from .20 to 103 on the port range specified.  Check wireshark to verify, then contact your firewall/network team.

     

    ICEWarn=0x80020,LocalSite=192.168.57.20:50048,RemoteSite=10.2.13.103:50043,RemoteMR=x.x.x.x<real IP address>:50911,PortRange=50040:50049,RemoteMRTCPPort=50911

     


    BBB
    Tuesday, December 20, 2011 11:53 PM
  • Do the two lync client calls access via VPN?

    If you use Hardware load balancer for Lync FE pool, please make sure the necessary ports are opend on it.

    Run get-CsconferencingPolicy to check the AudioBitRateKb value is 200. If not, please change it to 200.


    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.


    • Edited by Sean_Xiao Thursday, December 22, 2011 9:31 AM
    • Proposed as answer by Sean_Xiao Tuesday, December 27, 2011 1:42 AM
    • Marked as answer by Sean_Xiao Wednesday, December 28, 2011 4:44 AM
    Thursday, December 22, 2011 9:30 AM