Source note · Genesys Cloud CX telephony and BYOC
Certificates on a BYOC Cloud TLS trunk endpoint must be signed by a public certificate authority from the list Genesys publishes, and must contain the subject name of the URI the client connected to.
Checked 2026-09-24
- Vendor
- Genesys
- Product
- Genesys Cloud CX BYOC Cloud
- Subsystem
- TLS
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Checked
- 2026-09-24
Sources
- TLS trunk transport protocol specification for BYOC Cloud — Genesys · tier 2 current vendor documentation · certificate requirements section, public certificate authority list
Cite this note
APA
WarmTransfer. (2026, September 24). Genesys Cloud CX telephony and BYOC: source note genesys-cloud-telephony-tls-public-ca. WarmTransfer. https://warmtransfer.net/knowledge/claims/genesys-cloud-telephony-tls-public-ca
BibTeX
@misc{warmtransfer-claim-genesys-cloud-telephony-tls-public-ca,
title = {Genesys Cloud CX telephony and BYOC: source note genesys-cloud-telephony-tls-public-ca},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/genesys-cloud-telephony-tls-public-ca},
note = {Source note genesys-cloud-telephony-tls-public-ca, checked 2026-09-24}
}