Answered by:
Mediation service not starting

Question
-
Hello all, I deployed Lync 2010 Std front end and I intend to use ent voice.
Instant messaging is working well, but I can't start mediation service. I want to use mediation with an Audiocodes mediant 1000.
Can someone help me with this configs? That's my 1st deploy with ent voice.
Thanks!
Friday, August 3, 2012 2:56 PM
Answers
-
fixed! I don't know why the listening ports on my mediant were different from Lync, I had set the correct ports...and change my config to "all configured addresses"...thanks for your help.
- Proposed as answer by Lisa.zheng Friday, August 10, 2012 6:12 AM
- Marked as answer by Sharon.Shen Tuesday, August 21, 2012 11:40 AM
Wednesday, August 8, 2012 1:33 PM
All replies
-
Have you configured everything in the Topology for the Mediationserver.
Which error did you get in the eventlog.
Check that the used port is available for the Mediation Server.
regards Holger Technical Specialist UC
Friday, August 3, 2012 3:45 PM -
Guess I have many issues:
1:Log Name: Lync Server
Source: LS Mediation Server
Date: 8/3/2012 1:42:47 PM
Event ID: 25004
Task Category: (1030)
Level: Error
Keywords: Classic
User: N/A
Computer: lyncfe.solutionesp.com.br
Description:
Mediation Server service could not be started.
Exception: System.Exception: MediationServer Core Initialize Error. ---> System.Exception: The connection manager was unable to listen using the address and port supplied.
at Microsoft.RTC.MediationServerCore.ProxyGatewayListener.CreateProxyGatewayListener(Configuration config, MediationCallCollection mediationCallCollection, RtpPlatform platform)
at Microsoft.RTC.MediationServerCore.Core.Initialize()
--- End of inner exception stack trace ---
at Microsoft.RTC.MediationServerCore.Core.Initialize()
at Microsoft.RTC.MediationServerCore.Server.OnStart()
Cause: Internal error or a previous failure.
Resolution:
Examine the details of this event log entry and any other previous failures to determine the potential cause.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Mediation Server" />
<EventID Qualifiers="50182">25004</EventID>
<Level>2</Level>
<Task>1030</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-03T16:42:47.000000000Z" />
<EventRecordID>11448</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>lyncfe.solutionesp.com.br</Computer>
<Security />
</System>
<EventData>
<Data>System.Exception: MediationServer Core Initialize Error. ---> System.Exception: The connection manager was unable to listen using the address and port supplied.
at Microsoft.RTC.MediationServerCore.ProxyGatewayListener.CreateProxyGatewayListener(Configuration config, MediationCallCollection mediationCallCollection, RtpPlatform platform)
at Microsoft.RTC.MediationServerCore.Core.Initialize()
--- End of inner exception stack trace ---
at Microsoft.RTC.MediationServerCore.Core.Initialize()
at Microsoft.RTC.MediationServerCore.Server.OnStart()</Data>
</EventData>
</Event>2:
Log Name: Lync Server
Source: LS Mediation Server
Date: 8/3/2012 1:42:47 PM
Event ID: 25057
Task Category: (1030)
Level: Error
Keywords: Classic
User: N/A
Computer: lyncfe.solutionesp.com.br
Description:
The Mediation Server service has encountered a major problem with its configurations.
Cause: Check the following MOM alerts for more details. MEDIATIONSERVER_E_SETTING_INVALID_VALUE (Event ID: 25008), MEDIATIONSERVER_E_SETTING_INVALID_CERTIFICATE (Event ID: 25013), MEDIATIONSERVER_E_SETTING_CERTIFICATE_INVALID_SUBJECT (Event ID: 25037), MEDIATIONSERVER_E_SETTING_INVALID_LISTENING_ADDRESS_DATA (Event ID: 25012), MEDIATIONSERVER_WRN_SETTINGS_NOT_DYNAMIC (Event ID: 25031)
Resolution:
Modify the above specified configurations to clear the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Mediation Server" />
<EventID Qualifiers="50182">25057</EventID>
<Level>2</Level>
<Task>1030</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-03T16:42:47.000000000Z" />
<EventRecordID>11447</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>lyncfe.solutionesp.com.br</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>3:
Log Name: Lync Server
Source: LS Mediation Server
Date: 8/3/2012 1:42:47 PM
Event ID: 25012
Task Category: (1030)
Level: Error
Keywords: Classic
User: N/A
Computer: lyncfe.solutionesp.com.br
Description:
Invalid Mediation Server listening address/port.
Listening Address: 192.168.168.18
Listening Port: 5060
Cause: Settings configured incorrectly. Either the IP address does not belong to this machine or the port specified is invalid or already in use.
Resolution:
Configure the Mediation Server settings. Make sure that Mediation Server has a static IP and does not lose the IP address.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Mediation Server" />
<EventID Qualifiers="50182">25012</EventID>
<Level>2</Level>
<Task>1030</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-03T16:42:47.000000000Z" />
<EventRecordID>11446</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>lyncfe.solutionesp.com.br</Computer>
<Security />
</System>
<EventData>
<Data>192.168.168.18</Data>
<Data>5060</Data>
</EventData>
</Event>Friday, August 3, 2012 4:50 PM -
Can you verify that the IP 192.168.168.18 and port 5060 can be used on the Server where the mediationserver is installed. It Looks loke a IP or port problem
Normal 5067 will be used for TLS and 5068 for TCP
regards Holger Technical Specialist UC
- Edited by Holger Bunkradt Saturday, August 4, 2012 7:12 AM
- Proposed as answer by Lisa.zheng Tuesday, August 7, 2012 3:13 AM
Saturday, August 4, 2012 7:11 AM -
Have you checked the IP and the port?
How about changing the port 5060 to 5067, will it work?
Regards,
Lisa
Tuesday, August 7, 2012 3:13 AM -
Yes I did it, but I got the same error:
I'm trying to use TCP.Log Name: Lync Server
Source: LS Mediation Server
Date: 8/7/2012 9:44:29 AM
Event ID: 25012
Task Category: (1030)
Level: Error
Keywords: Classic
User: N/A
Computer: lyncfe.solutionesp.com.br
Description:
Invalid Mediation Server listening address/port.
Listening Address: 192.168.168.18
Listening Port: 5068
Cause: Settings configured incorrectly. Either the IP address does not belong to this machine or the port specified is invalid or already in use.
Resolution:
Configure the Mediation Server settings. Make sure that Mediation Server has a static IP and does not lose the IP address.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Mediation Server" />
<EventID Qualifiers="50182">25012</EventID>
<Level>2</Level>
<Task>1030</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-07T12:44:29.000000000Z" />
<EventRecordID>12621</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>lyncfe.solutionesp.com.br</Computer>
<Security />
</System>
<EventData>
<Data>192.168.168.18</Data>
<Data>5068</Data>
</EventData>
</Event>Tuesday, August 7, 2012 12:45 PM -
It is the same error, did you double check that the Ipaddress is correct on the networkcard and the FQDN is also correct?
regards Holger Technical Specialist UC
Tuesday, August 7, 2012 5:13 PM -
Man I don't know, IP .18 is configured on the media gateway (mediant 1000), and I set it in my config as pstn gateway using this IP, not FQDN, is that correct?Tuesday, August 7, 2012 5:32 PM
-
Hm, but why I can see on your image, that the mediationserver pstn is assigned to the .18, if it is the IP address of the GW?
regards Holger Technical Specialist UC
Wednesday, August 8, 2012 8:03 AM -
yeas, .18 is the IP configured in the GW...is that right?Wednesday, August 8, 2012 1:11 PM
-
fixed! I don't know why the listening ports on my mediant were different from Lync, I had set the correct ports...and change my config to "all configured addresses"...thanks for your help.
- Proposed as answer by Lisa.zheng Friday, August 10, 2012 6:12 AM
- Marked as answer by Sharon.Shen Tuesday, August 21, 2012 11:40 AM
Wednesday, August 8, 2012 1:33 PM