cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1847
Views
9
Helpful
8
Replies

SIP trunk between UC 8.5 and MS Lync 2010

Jeff Bankston
Level 1
Level 1

Are there any docs out there that would assist in creating a SIP trunk to a MS Lync 2010 server? I think I have it done, but calls get a fast busy so that could be anything.

Which RTMT function would be best used to check the SIP trunk for issues, watch the call flow, etc.?

Thanks, Jeff

8 Replies 8

norbert.putz
Level 1
Level 1

Hi Jeff,

I used the Microsoft documentation:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26800

That paper worked excellent in my environment.

Regards,

Norbert

That was very helpful, but in the event it still fails ( and it does ) what is a good mechanism in RTMT to see what is failing?

Thanks, Jeff

I suggest to use the "Lync Server Logging Tool", which is installed automatically on your Lync server. Run the tool, select "SIP" as the only component and set the "Level" to "All"

Use the "Analyze Log Files" button after you've logged some of your sip traffic. It requires you to install the Lync Server 2010 Resource Kit Tools but will provide a great logging tool.

Regards,

Norbert

As it turns out, I had the SIP trunk configured correctly, but the problem was that the Lync end wasn't. The problem was that MS needed to add in all IP addresses of all Call Mgrs, Pub and Subs, and the trunk came up.

In troubleshooting this with them, the Lync system has only a log file to see what's going on, no debug tools, no visual indicators of whats happening, but I had RTMT on my end.

Thanks, Jeff

Hello Jeff.  Could you give me some more detail on what you did to make this work?  I have followed the same guide and it's not working for me.  I suspect I have the same issue as you with the SIP trunk not being up.  Thanks much, Mike.

Make sure in the sip profile you use same ports used by the lync such as tcp or udp in and put directions

Also what is not working signaling or RTP media or both ?

They are using the same ports.  I would say both aren't working because I don't think the trunk is up.

My issue was that the Lync Mediation Server was not installed.  Once I installed that it all worked, although I think the MS whitepaper may have had an error or two in the ports being used, but I haven't confirmed that on my end yet.