Configure SIP TLS Between CUCM-CUBE/CUBE-SBC With CA Signed Certificates

Publisher

Cisco

URL

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-border-element/215412-configure-sip-tls-between-cucm-cube-cube.html

Published

2020-04-21

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• On CUBE, the dial peer toward Unified CM for SIP TLS uses session transport tcp tls and srtp, with a PKI trustpoint referenced by crypto signaling. in context
• For SIP TLS to CUBE, the Unified CM trunk has SRTP enabled and its destination port changed from 5060 to 5061. in context
• For SIP TLS to CUBE, the CUBE CA certificate or chain is uploaded in Unified CM OS Administration under Security > Certificate Management with the CallManager trust purpose. in context
• Cisco TAC's CUBE SIP TLS technote lists debug crypto pki api, callbacks, messages and transactions, debug ssl openssl errors, msg and states, and debug ip tcp transactions for troubleshooting TLS. in context
• The Cisco technote imports the root and intermediate CA certificates into the CUBE trustpoint before importing the signed CUBE identity certificate. in context
• For a CUCM-to-CUBE SIP TLS trunk, the X.509 subject name in the CUCM SIP trunk security profile must match the peer certificate's subject name, and the trunk destination port changes from 5060 to 5061. in context

Cite this source record

APA

WarmTransfer. (2020, April 21). Configure SIP TLS Between CUCM-CUBE/CUBE-SBC With CA Signed Certificates. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-technote-215412-sip-tls-cucm-cube

BibTeX

@misc{warmtransfer-cisco-technote-215412-sip-tls-cucm-cube,
  title  = {Configure SIP TLS Between CUCM-CUBE/CUBE-SBC With CA Signed Certificates},
  author = {{WarmTransfer}},
  year   = {2020},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-technote-215412-sip-tls-cucm-cube},
  note   = {Cisco, accessed 2026-09-24}
}