Source note · Connecting Unified CM to Genesys Cloud CX
Genesys Cloud requires a unique Inbound SIP Termination Identifier in each inbound INVITE to associate the call with the organisation. The identifier must be unique within the organisation's region.
Checked 2026-09-25
- Vendor
- Genesys
- Product
- Genesys Cloud CX
- Subsystem
- inbound SIP routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Configure SIP routing for a BYOC Cloud trunk — Genesys · tier 2 current vendor documentation · identifier uniqueness requirement
Cite this note
APA
WarmTransfer. (2026, September 25). Connecting Unified CM to Genesys Cloud CX: source note cucm-with-genesys-cloud-termination-id-unique. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-with-genesys-cloud-termination-id-unique
BibTeX
@misc{warmtransfer-claim-cucm-with-genesys-cloud-termination-id-unique,
title = {Connecting Unified CM to Genesys Cloud CX: source note cucm-with-genesys-cloud-termination-id-unique},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-with-genesys-cloud-termination-id-unique},
note = {Source note cucm-with-genesys-cloud-termination-id-unique, checked 2026-09-25}
}