Source note · Enabling mixed mode and encrypted calling in Unified CM
For a CUCM-to-CUBE TLS trunk the CUBE certificate is uploaded to Unified CM as CallManager-Trust, the X.509 Subject Name matches the CUBE certificate CN, the trunk destination port changes from 5060 to 5061 and SRTP Allowed is checked.
Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager; Cisco Unified Border Element
- Subsystem
- SIP trunk
- Deployment
- on-premises
- Region
- not restricted
- Release range
- as written (2017)
- Checked
- 2026-09-30
Sources
- Configure SIP TLS between CUCM-CUBE/CUBE-SBC — Cisco Systems · tier 2 current vendor documentation · Configure > Steps 4, 9 and 10
Cite this note
APA
WarmTransfer. (2026, September 30). Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-cube-cert-trust. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-cube-cert-trust
BibTeX
@misc{warmtransfer-claim-cucm-secure-calling-setup-cube-cert-trust,
title = {Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-cube-cert-trust},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-cube-cert-trust},
note = {Source note cucm-secure-calling-setup-cube-cert-trust, checked 2026-09-30}
}