Source note · Connecting Unified CM to Genesys Cloud CX
On Dynamic Cloud Voice, a party connecting to BYOC Cloud must support the FQDN method of SIP routing recommended in RFC 3261 section 19.1.1. It must also return unknown Contact URI parameters in later requests, per section 19.1.5.
Checked 2026-09-25
- Vendor
- Genesys
- Product
- Genesys Cloud CX
- Subsystem
- carrier requirements
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Carrier requirements for BYOC Cloud — Genesys · tier 2 current vendor documentation · RFC 3261 compliance (Dynamic Cloud Voice)
Cite this note
APA
WarmTransfer. (2026, September 25). Connecting Unified CM to Genesys Cloud CX: source note cucm-with-genesys-cloud-carrier-fqdn-routing. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-with-genesys-cloud-carrier-fqdn-routing
BibTeX
@misc{warmtransfer-claim-cucm-with-genesys-cloud-carrier-fqdn-routing,
title = {Connecting Unified CM to Genesys Cloud CX: source note cucm-with-genesys-cloud-carrier-fqdn-routing},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-with-genesys-cloud-carrier-fqdn-routing},
note = {Source note cucm-with-genesys-cloud-carrier-fqdn-routing, checked 2026-09-25}
}