Source note · SIP TLS handshake failures on trunks

CUBE's cn-san-validate option takes server (validate the identity of the outbound peer), client (validate the identity of the inbound peer) or bidirectional (both), and CN/SAN validation is not on by default.

Checked 2026-09-25

Vendor: Cisco
Product: Cisco Unified Border Element (IOS XE)
Subsystem: server identity validation
Deployment: on-premises
Region: not restricted
Release range: IOS XE 17.6 onwards
Checked: 2026-09-25

Sources

Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - SIP TLS Support — Cisco · tier 2 current vendor documentation · Configure SIP TLS, cn-san-validate keyword description

Cite this note

APA

WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-cube-cn-san-modes. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-cube-cn-san-modes

BibTeX

@misc{warmtransfer-claim-sip-tls-handshake-failures-cube-cn-san-modes,
  title  = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-cube-cn-san-modes},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-cube-cn-san-modes},
  note   = {Source note sip-tls-handshake-failures-cube-cn-san-modes, checked 2026-09-25}
}

Read in context