Trunk Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2015 07:03 AM - edited 03-19-2019 09:43 AM
Hi,
I need some assistance, I have a CUCM 10.0.1. I am trying to setup a trunk to a Microsoft Lync Server. For some reason the trunk status is displaying as down ,Status Reason local=1. Can someone please help me to identify the issue here.
Thanks
Marcel
- Labels:
-
UC Applications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2015 09:38 AM
the SIP Trunk "Status Reason local=1" indicates either the remote peer is Unavailable or Unreachable. Possible reason code for Trunk Status Local=1 is "408 Request Timeout" or "503 Service Unavailable".
check the connectivity between both the nodes, and test if the Lync server can ping the CUCM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2015 01:10 PM
I just checked and the lync server is able to ping the CUCM and vise versa.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2015 06:37 AM
Are you using the same udp/tcp port on both sides?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2015 11:18 AM
Yes I am using 5068 on both sides.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2015 11:21 AM
5068 is on the default SIP port, did you adjust it on the SIP security profile used by the SIP trunk?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2015 03:19 PM
Chris I did check and both the security profile and the SIP trunk the port is set to 5068. What other option do you think I could explore.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2015 06:49 AM
When we built our trunk between Callmanager and Lync, the Lync side didn't have all the ports turned up that they told us. We used nmap against the Lync ip address to prove that the ports weren't listening. They made some configuration changes and then it worked. Not sure if that helps any but thought I'd mention it.
