Source note · Unified CM SIP trunk to CUBE configuration
When multiple non-secure SIP trunks with different listening ports point to the same destination, they may use the wrong port in a mid-call INVITE and the call drops.
Checked 2026-09-24
they may incorrectly use the port in the mid call INVITE. Hence, the call drops
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- SIP trunk
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Release 15 and SUs
- Checked
- 2026-09-24
Sources
- System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Trunks — Cisco · tier 2 current vendor documentation · SIP Trunk Interactions and Restrictions
Cite this note
APA
WarmTransfer. (2026, September 24). Unified CM SIP trunk to CUBE configuration: source note cucm-config-sip-trunk-to-cube-ucm-nonsecure-port-drop. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-config-sip-trunk-to-cube-ucm-nonsecure-port-drop
BibTeX
@misc{warmtransfer-claim-cucm-config-sip-trunk-to-cube-ucm-nonsecure-port-drop,
title = {Unified CM SIP trunk to CUBE configuration: source note cucm-config-sip-trunk-to-cube-ucm-nonsecure-port-drop},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-config-sip-trunk-to-cube-ucm-nonsecure-port-drop},
note = {Source note cucm-config-sip-trunk-to-cube-ucm-nonsecure-port-drop, checked 2026-09-24}
}