Because certificate names are matched against SIP Servers or Proxies by host name, a TLS trunk's SIP Servers or Proxies entries should be host names that appear in the carrier certificate, not IP addresses.
inferred · Checked 2026-09-30
- Vendor
- Genesys
- Product
- Genesys Cloud CX
- Subsystem
- BYOC Cloud TLS
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Status
- inferred
- Checked
- 2026-09-30
Sources
- TLS trunk transport protocol specification for BYOC Cloud — Genesys · tier 2 current vendor documentation · TLS trunk transport protocol specification for BYOC Cloud, subject name validation
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up Genesys Cloud BYOC Cloud with a carrier or SBC: source note genesys-cloud-byoc-setup-tls-hostname-inference. WarmTransfer. https://warmtransfer.net/knowledge/claims/genesys-cloud-byoc-setup-tls-hostname-inference
BibTeX
@misc{warmtransfer-claim-genesys-cloud-byoc-setup-tls-hostname-inference,
title = {Setting up Genesys Cloud BYOC Cloud with a carrier or SBC: source note genesys-cloud-byoc-setup-tls-hostname-inference},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/genesys-cloud-byoc-setup-tls-hostname-inference},
note = {Source note genesys-cloud-byoc-setup-tls-hostname-inference, checked 2026-09-30}
}