Lync 2013 Outgoing Sip / Voice issues

Hi,

I am having an issue when setting up a SIP trunk in to Lync.

1. Mediation pool is set as TLS 5067-5067 and TCP is 5060-5060

2. PSTN gateway has 88.215.61.201 as signalling gateway and 88.215.61.202 as alternative media. with Lycn set to use all avalibe IP address.

3. Trunk is set to listen on port 5060 protocol TCP and associated mediaserver port as 5060.

Now all incoming calls are working and I can use both Conferencing and direct dial to an assigned number. However all out bound alls are failing with a "call not connected or ended" error

A snoop trace shows

TL_INFO(TF_PROTOCOL) [1]1E2C.2748::02/06/2014-09:21:30.560.001052d2 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(196))[726616948] $$begin_record
Trace-Correlation-Id: 726616948
Instance-Id: 11E84
Direction: incoming
Peer: IAH-Lync.iah.ac.uk:5070
Message-Type: response
Start-Line: SIP/2.0 503 Service Unavailable
FROM: "aaron street"<sip:aaron.street@pirbright.ac.uk>;tag=5a9f3b82e7;epid=521eb7198e
TO: <sip:+441483123456@pirbright.ac.uk;user=phone>;epid=9C1E94F7FC;tag=fb892a5522
CALL-ID: d9c1a37ce7674d0e98762551d31d759c
CSEQ: 1 INVITE
VIA: SIP/2.0/TLS 149.155.28.4:56648;branch=z9hG4bK6BF9FA4C.62EFEC7A3F6DE50A;branched=FALSE,SIP/2.0/TLS 149.155.25.25:60178;ms-received-port=60178;ms-received-cid=6DC00
CONTENT-LENGTH: 0
ms-diagnostics: 10001;source="IAH-Lync.iah.ac.uk";reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
ms-diagnostics-public: 10001;reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
$$end_record

The Line that confuses me is

Peer: IAH-Lync.iah.ac.uk:5070

why is it looking to port 5070? why not 5060 as it is configured to?

In another log entry I see

ACK sip: +441483123456@88.215.61.201:5070;user=phone;maddr=IAH-Lync.iah.ac.uk SIP/2.0
Start-Line: ACK sip:+441483123456@88.215.61.201:5070;user=phone;maddr=IAH-Lync.iah.ac.uk SIP/2.0

Open in new window


again why port 5070 and not 5060 ?

I am sure this is causing the issue but I can see were in the config it is picking up this port number.

Also saw this error

"27591525Incoming session is rejected because Mediation Server thinks its network interface is down.NULL"

One thing I have done is change the IP address of the frountend/media server. every thing else is fine but not sure if there is any thing I need to do in the topology to clear out the old IP record or if this might be affecting it.

Thanks for any help.
LVL 16
Aaron StreetInfrastructure ManagerAsked:
Who is Participating?
 
Aaron StreetInfrastructure ManagerAuthor Commented:
Resolved.

Had to go on to the front end server and disable and re-enable the mediator server publishing and re running the setup program each time. After that it is fine
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.