Source note · Troubleshooting Genesys Cloud BYOC trunks
The customer endpoint certificate's common name or subject alternative name must match the value used as the trunk's SIP Servers or Proxies setting; the BYOC endpoint validates by host name, and an IP address is not acceptable.
Checked 2026-09-25
- Vendor
- Genesys
- Product
- Genesys Cloud BYOC Cloud
- Subsystem
- TLS certificates
- 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 · certificate requirements section
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Genesys Cloud BYOC trunks: source note genesys-byoc-troubleshooting-cert-name-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/genesys-byoc-troubleshooting-cert-name-match
BibTeX
@misc{warmtransfer-claim-genesys-byoc-troubleshooting-cert-name-match,
title = {Troubleshooting Genesys Cloud BYOC trunks: source note genesys-byoc-troubleshooting-cert-name-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/genesys-byoc-troubleshooting-cert-name-match},
note = {Source note genesys-byoc-troubleshooting-cert-name-match, checked 2026-09-25}
}