For Local=1 and Local=2, Cisco says to check that the remote side has a SIP trunk whose SIP Trunk Security Profile incoming port matches the destination port configured on the originating trunk.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- SIP trunk troubleshooting
- Deployment
- on-premises
- Region
- not restricted
- Release range
- technote updated 2018-09-26; release not stated
- Checked
- 2026-10-02
Sources
- Calls through Session Initiation Protocol (SIP) Trunk Failure — Cisco · tier 2 current vendor documentation · Troubleshoot > Scenario 1 and Scenario 2 recommended actions
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-fix-port-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-fix-port-match
BibTeX
@misc{warmtransfer-claim-cucm-sip-trunk-no-service-troubleshooting-fix-port-match,
title = {Troubleshooting Unified CM SIP trunks that show No Service: source note cucm-sip-trunk-no-service-troubleshooting-fix-port-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-fix-port-match},
note = {Source note cucm-sip-trunk-no-service-troubleshooting-fix-port-match, checked 2026-10-02}
}