The SIP trunk is considered in service when at least one node receives a response other than 408 or 503 from at least one destination address.
Checked 2026-10-02
The trunk state is considered to be 'in service' when at least one node receives a response (other than a 408 or 503) from a least one destination address.
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- SIP OPTIONS ping
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 8.5(1) and 8.6(1) design guidance; later releases not verified
- Checked
- 2026-10-02
Sources
- Cisco Unified Communications Manager Trunks (Session Management Edition deployment guide, Release 8.5(1)) — Cisco Systems · tier 2 current vendor documentation · SIP OPTIONS Ping
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-in-service-rule. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-in-service-rule
BibTeX
@misc{warmtransfer-claim-cucm-sip-trunk-no-service-troubleshooting-in-service-rule,
title = {Troubleshooting Unified CM SIP trunks that show No Service: source note cucm-sip-trunk-no-service-troubleshooting-in-service-rule},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-sip-trunk-no-service-troubleshooting-in-service-rule},
note = {Source note cucm-sip-trunk-no-service-troubleshooting-in-service-rule, checked 2026-10-02}
}