Source record · tier 2 current vendor documentation
Carrier requirements for BYOC Cloud
- Publisher
- Genesys
- URL
- https://help.genesys.cloud/articles/carrier-requirements-byoc-cloud/
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Genesys proprietary documentation; no-redistribution; short excerpts and locators only
Source notes citing this source
- 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. in context
- On Legacy Cloud Voice, a party connecting to BYOC Cloud needs full Record-Route support as RFC 3261 requires. in context
- On Dynamic Cloud Voice, a party connecting to BYOC Cloud must fully support RFC 3261 section 8.2.6.2 and return the Via header in responses exactly as Genesys Cloud sent it. in context
- With the FQDN routing method, the inbound Request-URI puts the dialled number in the user part and the trunk's identifier-based FQDN in the host part, for example sip:+13172222222@myuniqueidentifier.byoc.use1.genesys.cloud. in context
- Setting the Genesys-facing CUBE dial-peer's session target to dns:<identifier>.byoc.<region>.genesys.cloud should put the FQDN-method host into the Request-URI that Genesys expects. inferred in context
- BYOC Cloud carriers must support UDP, TCP or TLS transport, FQDN routing and Record-Routing as RFC 3261 requires, and must return the Via header untouched in responses. in context
- BYOC Cloud identifies the trunk for an inbound call by TGRP, FQDN, custom header or DNIS replacement, evaluated in that order of precedence. in context
- The carrier must add the Genesys Cloud public SIP IP addresses for the region to its carrier-side ACL allowlist, and send inbound calls to the public SIP load balancer DNS names or the trunk FQDN. in context
- A BYOC Cloud carrier must be SIP-compliant including RFC 3261 sections 8.2.6.2, 19.1.1 and 19.1.5, and must fully support Record-Route. in context
Cite this source record
APA
WarmTransfer. (2026, September 24). Carrier requirements for BYOC Cloud. WarmTransfer. https://warmtransfer.net/knowledge/sources/genesys-help-carrier-requirements-byoc-cloud
BibTeX
@misc{warmtransfer-genesys-help-carrier-requirements-byoc-cloud,
title = {Carrier requirements for BYOC Cloud},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/genesys-help-carrier-requirements-byoc-cloud},
note = {Genesys, accessed 2026-09-24}
}