Because Cisco documents Local=1 only for UDP and lists TCP connect failure as a separate out-of-service trigger, a TCP or TLS trunk whose peer is unreachable is more likely to show Local=2 than Local=1.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- SIP trunk status reason
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- Calls through Session Initiation Protocol (SIP) Trunk Failure — Cisco · tier 2 current vendor documentation · Troubleshoot > Scenarios 1 and 2
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting Unified CM SIP trunks that show No Service: source note cucm-sip-trunk-no-service-troubleshooting-local1-udp-scope. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-local1-udp-scope
BibTeX
@misc{warmtransfer-claim-cucm-sip-trunk-no-service-troubleshooting-local1-udp-scope,
title = {Troubleshooting Unified CM SIP trunks that show No Service: source note cucm-sip-trunk-no-service-troubleshooting-local1-udp-scope},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-local1-udp-scope},
note = {Source note cucm-sip-trunk-no-service-troubleshooting-local1-udp-scope, checked 2026-10-02}
}