Source note · Unified CM SIP trunk to CUBE configuration
When the trunk runs on all active nodes, CUBE should trust and target every call-processing subscriber, because any of them may originate calls and trusted-list failures are silently dropped.
inferred · Checked 2026-09-24
- Vendor
- Cisco
- Product
- Unified Communications Manager; Cisco Unified Border Element
- Subsystem
- SIP trunk
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- Cisco Collaboration System 12.x Solution Reference Network Designs (SRND) - Cisco Unified CM Trunks — Cisco · tier 2 current vendor documentation · Run on all Active Unified CM Nodes section, combined with cisco-technote-220380-harden-cube IP Address Trusted List section
Cite this note
APA
WarmTransfer. (2026, September 24). Unified CM SIP trunk to CUBE configuration: source note cucm-config-sip-trunk-to-cube-inf-trust-all-subscribers. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-config-sip-trunk-to-cube-inf-trust-all-subscribers
BibTeX
@misc{warmtransfer-claim-cucm-config-sip-trunk-to-cube-inf-trust-all-subscribers,
title = {Unified CM SIP trunk to CUBE configuration: source note cucm-config-sip-trunk-to-cube-inf-trust-all-subscribers},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-config-sip-trunk-to-cube-inf-trust-all-subscribers},
note = {Source note cucm-config-sip-trunk-to-cube-inf-trust-all-subscribers, checked 2026-09-24}
}