locked
A/V calls fail for all remote users (via Lync 2010 Edge). RRS feed

  • Question

  • We have just deployed a single Lync 2010 edge server. Enterprise Voice functionality is deployed internally and is fully functional (PSTN access, RSG etc). All core functionality (IM, Presence, desktop sharing, file transfer) works fine for remote users.

    However any A/V communications from a remote user (via the edge) fails when the call is answered. This is for all A/V calls from a remote user to internal users, PSTN numbers and the audio test service.

    In every case the call is initiated but when answered there is a delay then the client reports 'call failed due to network issues'. Lync logging (sipstack), network traces etc don't give much indication whats wrong with the edge av service.

    Diagnostics report the following:

    Report time: 13/08/2012 10:53:53 a.m.      
      Response code: 200 Diagnostic ID: 23  
      Request type: BYE Content type:    
      Source:   Application:    
     
      From user agent: UCCAPI/4.0.7577.4103 OC/4.0.7577.4103 (Microsoft Lync 2010)  
      Diagnostic header: 23; reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote"; CallerMediaDebug="audio:ICEWarn=0x80120,LocalSite=192.168.55.17:6052,RemoteSite=172.x.x.54:55210,RemoteMR=202.x.x.54:59017,PortRange=1025:65000,RemoteMRTCPPort=59017,LocalLocation=1,RemoteLocation=2,FederationType=0"

    Wednesday, August 15, 2012 1:51 AM

Answers

  • Thanks for your reply's.

    We don't have a collocated mediation server but the cmdlet above provided the answer to our issue.

    We have several SBA's on remote sites and the cmdlet above made it obvious we hadn't defined the edge server for these SBA's. Once the edge was defined in topology builder the A/V all worked.

    • Marked as answer by gg-10 Thursday, August 16, 2012 11:02 PM
    Thursday, August 16, 2012 11:02 PM

All replies

  • Looks like you are having ICE negotiation problems.  From the ICEWarn error code, you have the following issues below:

    0x20

    Local connectivity failed. (local UDP for audio/video and local TCP for application sharing and file transfer).

    This flag can occur if the direct connection between clients isn’t possible due to NAT/firewalls. This may result in an ICE protocol failure.

    0x100

    TCP NAT connectivity failed.

    This flag is expected. If local-to-local connectivity succeeded, the TCP NAT connectivity check may not have been tried. Or there is no direct TCP connection possible. TCP NAT connectivity failing may result in an ICE protocol failure.

    0x80000

    No TURN server configured.

    This flag is indicating that there was no TURN server configured or there is a Domain Name System (DNS) resolution failure, resulting in a communication issue between the client and the TURN server. This may result in a protocol ICE failure.


    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    Wednesday, August 15, 2012 1:57 AM
  • Hi,

    Is Medation server collocated with front end?

    Please run Get-CsService -MediationServer to check if Edge server of Mediation server has been set.

    If you are using NATing, please check if you specified the IP address of the AV interface for the public IP address.


    Regards,

    Kent Huang

    TechNet Community Support ************************************************************************************************************************ 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.


    • Edited by Kent-Huang Thursday, August 16, 2012 3:06 AM
    Thursday, August 16, 2012 3:05 AM
  • Thanks for your reply's.

    We don't have a collocated mediation server but the cmdlet above provided the answer to our issue.

    We have several SBA's on remote sites and the cmdlet above made it obvious we hadn't defined the edge server for these SBA's. Once the edge was defined in topology builder the A/V all worked.

    • Marked as answer by gg-10 Thursday, August 16, 2012 11:02 PM
    Thursday, August 16, 2012 11:02 PM
  • Does your edge have a static route pointing back to each network that might be running the lync client?

    The Lync Client and Edge need to be able to resolve each other internally.


    Thanks!

    Wednesday, August 22, 2012 6:11 PM