Source record · tier 2 current vendor documentation
Calls through Session Initiation Protocol (SIP) Trunk Failure
- Publisher
- Cisco
- URL
- https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/213718-calls-through-session-initiation-protoco.html
- Published
- 2018-09-26
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only
Source notes citing this source
- A No Service trunk status reason of local=1 means no OPTIONS responses after all retries over UDP, local=2 means Unified CM could not open a socket to the peer, and local=3 means DNS could not resolve the hostname or SRV. in context
- The SIP trunk status is shown on the Device > Trunk page in Cisco Unified CM Administration. in context
- Trunk status reason Local=1 means no response came back to OPTIONS after all retries over UDP; check that the remote CallManager service is running, that the remote trunk's incoming port matches, and basic reachability. in context
- Trunk status reason Local=2 means Unified CM could not open a socket connection to the remote peer. in context
- Trunk status reason Local=3 means the DNS server is unreachable or DNS cannot resolve the trunk's hostname or SRV record. in context
- A Unified CM trunk Status Reason of local=1 means no response was received to OPTIONS after retries over UDP. in context
- A Unified CM trunk Status Reason of local=2 means Unified CM could not create a socket connection to the remote peer. in context
- A Unified CM trunk Status Reason of local=3 means DNS resolution failed (DNS server unreachable or DNS misconfigured). in context
- When all remote peers of a Unified CM SIP trunk are out of service, RTMT raises UC_CALLMANAGER-3-SIPTrunkOOS and the trunk page shows the status as No service. in context
- When every remote peer of a SIP trunk is out of service, Unified CM reports that all remote peers are out of service and cannot handle calls for the trunk, and the trunk shows No Service. in context
- Cisco's SIP trunk failure tech note lists out-of-service reason codes: Local=1 means no responses to OPTIONS after all retries over UDP, Local=2 means Unified CM could not open a socket to the remote peer, and Local=3 means DNS could not resolve the hostname or SRV record. in context
Cite this source record
APA
WarmTransfer. (2018, September 26). Calls through Session Initiation Protocol (SIP) Trunk Failure. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-technote-213718-sip-trunk-failure
BibTeX
@misc{warmtransfer-cisco-technote-213718-sip-trunk-failure,
title = {Calls through Session Initiation Protocol (SIP) Trunk Failure},
author = {{WarmTransfer}},
year = {2018},
url = {https://warmtransfer.net/knowledge/sources/cisco-technote-213718-sip-trunk-failure},
note = {Cisco, accessed 2026-09-24}
}