Genesys Cloud requires a unique identifier in the inbound INVITE to associate a call with the right organization's BYOC Cloud trunk, configured as a regionally unique Inbound SIP Termination Identifier.
Checked 2026-09-30
- Vendor
- Genesys
- Product
- Genesys Cloud CX
- Subsystem
- BYOC Cloud SIP routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Configure SIP routing for a BYOC Cloud trunk — Genesys · tier 2 current vendor documentation · Configure SIP routing for a BYOC Cloud trunk, Inbound
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-inbound-identifier. WarmTransfer. https://warmtransfer.net/knowledge/claims/genesys-cloud-byoc-setup-inbound-identifier
BibTeX
@misc{warmtransfer-claim-genesys-cloud-byoc-setup-inbound-identifier,
title = {Setting up Genesys Cloud BYOC Cloud with a carrier or SBC: source note genesys-cloud-byoc-setup-inbound-identifier},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/genesys-cloud-byoc-setup-inbound-identifier},
note = {Source note genesys-cloud-byoc-setup-inbound-identifier, checked 2026-09-30}
}