Cisco recommends checking network connectivity to the remote peer from the originating Unified CM with the CLI command utils network ping followed by the remote peer address.
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 > Scenarios 1 to 3 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-cli-ping. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-fix-cli-ping
BibTeX
@misc{warmtransfer-claim-cucm-sip-trunk-no-service-troubleshooting-fix-cli-ping,
title = {Troubleshooting Unified CM SIP trunks that show No Service: source note cucm-sip-trunk-no-service-troubleshooting-fix-cli-ping},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-fix-cli-ping},
note = {Source note cucm-sip-trunk-no-service-troubleshooting-fix-cli-ping, checked 2026-10-02}
}