Source note · Connecting Unified CM to Genesys Cloud CX
For TLS, the customer endpoint needs a certificate from a public CA that Genesys trusts, with a common name or subject alternative name that matches a hostname in the trunk's SIP Servers or Proxies. IP addresses are not accepted for this match.
Checked 2026-09-25
- Vendor
- Genesys
- Product
- Genesys Cloud CX
- Subsystem
- TLS trunk
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- TLS trunk transport protocol specification for BYOC Cloud — Genesys · tier 2 current vendor documentation · validation requirements: subject name validation
Cite this note
APA
WarmTransfer. (2026, September 25). Connecting Unified CM to Genesys Cloud CX: source note cucm-with-genesys-cloud-tls-cn-san-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-with-genesys-cloud-tls-cn-san-match
BibTeX
@misc{warmtransfer-claim-cucm-with-genesys-cloud-tls-cn-san-match,
title = {Connecting Unified CM to Genesys Cloud CX: source note cucm-with-genesys-cloud-tls-cn-san-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-with-genesys-cloud-tls-cn-san-match},
note = {Source note cucm-with-genesys-cloud-tls-cn-san-match, checked 2026-09-25}
}