locked
Call terminated on media connectivity failure RRS feed

  • Question

  • Hi

    I have a problem when trying to make calls from Communicator to external phones.

    When I make a call it connects fine and I can hear my phone ringing, but if I answer nothing happens. Communicator still says connecting call even if I answer and then disconnects after 10 seconds.

    If I don’t answer it’s the same thing. Communicator says connecting and then it disconnects after 10 seconds.

    All I find in the log is this : Call terminated on media connectivity failure

     

    And in the eventviewer I have this error

    Event Type:    Error

    Event Source: OCS Mediation Server

    Event Category:                    (1030)

    Event ID:        25015

    Date:                                    3/28/2007

    Time:                                    11:44:15 PM

    User:                                    N/A

    Computer:      MEDIATION

    Description:

    The A/V Authentication Service returned invalid response. Connections that require Firewall traversal will not be successful.

     

    Response Code: 504

    Response Text: Server time-out

     

    Cause: Either the A/V Authentication Service is not running or unreachable.

    Resolution:

    Verify that A/V Authentication Service is reachable from the computer running Office Communications Server. The response text may also indicate a configuration issue.

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Tuesday, April 10, 2007 2:42 PM

Answers

  •  

    ops... I had a firewall between my client and the mediation server.

    So when opening the ports it works fine

    Thursday, April 12, 2007 5:53 PM

All replies

  •  

    ops... I had a firewall between my client and the mediation server.

    So when opening the ports it works fine

    Thursday, April 12, 2007 5:53 PM
  •  

    Hi Tommy,

     

    Do you know what ports you have opened on your firewall? We have the same problem when calling with federated users via our Edge.

     

    Calling with domain users work fine.

     

    /Thomas

    Tuesday, October 2, 2007 6:39 AM
  • Hi Thomas,

     

    We are seeing the same issue. Did you have yours resolved in some way?

     

    Thanks

    Alex

     

    Monday, November 17, 2008 4:33 PM
  • Yep. Make sure that you have configured your external interfaces of the Audio/Video Edge Servers to use a public IP.

    I would suggest to read the following document and follow the best practises:

    http://www.microsoft.com/downloads/details.aspx?familyid=e4a8d703-e41a-47d9-b9dd-2799f894af92&displaylang=en

    /thomas
    Monday, November 17, 2008 5:32 PM
  • Hi Thomas,

     

    We have our infrastructure implemented using best practices with public IP addresses for all edge server roles. However our internal networking setup has a lot complexity to it (not from OCS side). From OCS perspective it all goes via CSM load balancing as there are two machines per roles.

    I was wondering if going from internal to external IP address has fixed your issue. If so I am a little surprised you were able to make it work for your company user working remotely. From my understanding traffic will be routed in a same way as when you talk to federated user.

    Can you please elaborate a bit more on your solution.

     

    Thanks

    Alex

     

    Monday, November 17, 2008 5:43 PM
  • Hi Alex,

     

    Just a few thoughts:

     

    1/ In our case we were not able to use Audio/video at all connecting with external users. Reconfiguring the A/V Edge Servers solved that problem

     

    2/ Check your mediation server properties > see if the internal interface of the A/V edge server is correctly configured (in our case on port 5062). Check if you can ping from your mediation server to the internal Edge server. The internal A/V Edge server can be configured in the Global Pool Level settings of your OCS server (Edge Server tab).

     

    3/ Trace the network traffic on your firewall/gateway to check if routing is correct and if any A/V media traffic from the mediation server is blocked from your ISA server: You might have to add another rule allowing traffic from the mediation server.

     

    4) Try to run the logging tool on the mediation- and (av) edge server and analyse the sip stack log for any conncetivity errors.

     

    Cheers,

     

    Thomas

     

    Tuesday, November 18, 2008 9:42 AM