Mediation Server Time Out

All replies

• 

  

  0

  Sign in to vote

  Check if your Mediation Server has a correct certificate

  Must be FQDN of Mediation Server and must be trusted by your client

   

  This is the error that you receive:

  The peer actively refused the connection

   

  Might also be a firewall issue

  Tuesday, March 25, 2008 7:33 PM
• 

  

  0

  Sign in to vote

  Can you post a little bit more information on which certificate your use. Does the TLS nego goed right? As described earlier you probably need to update or correct your certificate (make sure the FQDN matches the name of the Mediation Server (FDQN).

   

  Wednesday, March 26, 2008 6:52 PM
• 

  

  0

  Sign in to vote

  I have checked the certificate. The FQDN matches the Certificate.

  I am checking with the security team as there might be firewall blocking the connection.

  But what ports should i request to be allowed for the connection?

   

   

   

   

   

  Tuesday, April 1, 2008 3:50 AM
• 

  

  0

  Sign in to vote

  
  Event Type: Error
  Event Source: OCS Mediation Server
  Event Category: (1030)
  Event ID: 25017
  Date:  3/28/2008
  Time:  8:54:42 PM
  User:  N/A
  Computer: WDSJOCS01
  Description:
  The A/V Authentication Service cannot be contacted. Connections that require Firewall traversal will not be successful.

  Exception: Microsoft.Rtc.Signaling.ConnectionFailureException: Unable to establish a connection. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
     at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
     at Microsoft.Rtc.Internal.Sip.TcpTransport.OnConnected(Object arg)
     --- End of inner exception stack trace ---
     at Microsoft.Rtc.Signaling.SipAsyncResult.ThrowIfFailed()
     at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult asyncResult)
     at Microsoft.Rtc.Signaling.RealTimeEndpoint.EndSendMessage(IAsyncResult asyncResult)
     at Microsoft.RTC.MediationServerCore.MrasCommunicator.SendMessageCallback(IAsyncResult result)

  Cause: Either the A/V Authentication Service or Office Communications Server is not unreachable.
  Resolution:
  Verify that A/V Authentication Service is reachable from the computer running Office Communications Server.

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

   

  Event Type: Error
  Event Source: OCS Mediation Server
  Event Category: (1030)
  Event ID: 25014
  Date:  3/28/2008
  Time:  8:57:03 PM
  User:  N/A
  Computer: WDSJOCS01
  Description:
  The A/V Authentication Service cannot be contacted. Connections that require Firewall traversal will not be successful. Mediation server will keep trying; however additional failures will not be logged.

  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.

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

   

  this is the 2 event id from the mediation server.

  Tuesday, April 1, 2008 4:04 AM
• 

  

  0

  Sign in to vote

  i have check with the security team, according to them there is no firewall between the 2 sites.

  Tuesday, April 1, 2008 4:16 AM
• 

  

  0

  Sign in to vote

  You apparantly have problems contacting your AV EDGE Server

  Can you run validation wizards on your pool and edge servers

   

  Tuesday, April 1, 2008 11:14 AM
• 

  

  0

  Sign in to vote

  Yes, the mediation have problem connecting to the AV Edge server.

  I have removed the AV Edge on the Mediation Configuration but still have the same error on the client.

   

  I have also run validation wizards on the pool and edge. No errors shown.

   

  Will it be the log on service that is causing the problem?

  For all the OCS Servers in MY domain, the services is using MY\RTCComponentService as logon.

  For Mediation server in NCAL domain, the services is using NCAL\RTCComponentService as logon.

  Do I need to use the same logon for the services?

   

  My final solution will be reinstalling the 2nd Mediation and joined it to MY domain. Maybe this will solve the problem.

  Wednesday, April 2, 2008 3:54 AM
• 

  

  0

  Sign in to vote

  Did you run the validation wizard on the Mediation Server?

   

  Wednesday, April 2, 2008 4:04 PM
• 

  

  0

  Sign in to vote

  I can't find any validation wizard for the Mediation server.

  Thursday, April 3, 2008 3:33 AM
• 

  

  0

  Sign in to vote

  Run the validation wizard on the Front-End server

  You should also run the OCS Best practive analyzer

  http://www.microsoft.com/downloads/details.aspx?FamilyId=1B90993C-072A-4C84-B385-B76D23B2F27C&displaylang=en

   

  Friday, April 11, 2008 6:58 PM
• 

  

  0

  Sign in to vote

  There was 2 A records for the Mediation server. Remove the second A records. Able to make calls after that. Thanks for the help.

  Thursday, April 17, 2008 8:41 AM
• 

  

  0

  Sign in to vote

  Hello all

   

  We have experienced the same kind of issue.

   

  Running Nortel IP-PBX CS1000E 5.0

  We have finished the set-up of OCS Proxy which MCM(Provided by Nortel) and FE, Mediation and AD.

  We have downloaded Validation Wizard and tried it.

  Each server says need hotfix will be needed.

  But we have already installed the latest version of hotfix.

  So, Error occured saying "already installed... diffrent version of ...."

   

  The issue is occuring in between MCM to Mediation.

   DNS record cannot be retrieved kind of error message was shown.

   

  We appreciate if anybody could let us know the resolution for this error

   

  Yoshi

   

   

  a=sendrecv-----------------------------------------------------------
  2008/06/26 18:41:38: 3.0.1.77: SIP: Received by MCM:
  -----------------------------------------------------------
   Response: 504 Server time-out
    from: "IP_PHONE1000"<sip:+81354361000;ext=1000@ocslab.local;user=phone>;tag=1e8e0b40-ac8a8c0-13c4-40030-4346-1b038098-4346
    to: <sip:+81354361001;ext=1001@ocslab.local;user=phone>;tag=2AC6BBCE6BE0A459BF18C498C8CCF9FE
    call-id: 1e2bd990-ac8a8c0-13c4-40030-4346-7fd9c052-4346
    cseq: 1 INVITE
    via: SIP/2.0/TCP 192.168.200.10:5060;branch=z9hG4bK-4346-106cc7c-61027741;ms-received-port=2204;ms-received-cid=D00
    ms-diagnostics: 1007;reason="Temporarily cannot route";source="ocsproxy.ocslab.local";ErrorType="Connect Attempt Failure";WinsockFailureDescription="The peer actively refused the connection attempt";WinsockFailureCode="274D(WSAECONNREFUSED)";Peer="ocslab.local"

   

  Thursday, June 26, 2008 10:24 AM
• 

  

  0

  Sign in to vote

   

  Hi Yoshi,

  I have the same problem running Nortel CS1000E .

  Do you have fix it ?

   

  Thanks a lot

   

  Pietro

  Wednesday, October 15, 2008 1:35 PM