VoIP.infoThe independent guide to business communications.
VoIP.info Provider research

Genesys Cloud BYOC Cloud: carrier, trunk and Voice-platform boundaries

Connect a third-party carrier or PBX to Genesys Cloud while keeping Voice platform, region, inbound organization identity, site routing, media, emergency service and carrier ownership separate.

Reviewed 2026-10-09Current first-party Genesys Cloud BYOC Cloud architecture, carrier, trunk, routing, transport, TLS, Dynamic Cloud Voice migration, site, emergency-service, fair-use and configuration-checklist documentation reviewed October 9, 2026; the Dynamic Cloud Voice default announcement has no effective date in the reviewed record and existing trunks retain their current platform unless deliberately migrated; no Genesys Cloud organization, license, carrier order, trunk, site, location, number plan, route, peer, address, certificate, firewall, call, media stream, fax, emergency workflow, message, usage record, price, availability, compatibility or support response was inspected or testedAdvancedDocumentation based · not lab tested

Classify the BYOC Cloud boundary before selecting settings

BYOC Cloud defines SIP trunks between the Genesys Cloud AWS-based Edge and Media Tier and a third-party carrier service or device over the public Internet. The external trunk can be BYOC Carrier or BYOC PBX. That is different from BYOC Premises, where the connection terminates on a premises Edge.

Record the Genesys organization and region, site and location, cloud media model, trunk type and subtype, carrier or PBX owner, numbers, emergency owner and support contacts. A Genesys feature or AWS region does not establish carrier coverage, number availability or interoperability for the selected path.

Documented service facts

Reviewed 2026-10-09. Compare SIP trunk services →

SIP authentication

Documented

BYOC Cloud uses an external trunk to a third-party carrier service or device. Source addresses, the region-specific inbound termination identifier and, for TLS, public-CA certificate trust are separate controls. The reviewed material does not establish one universal digest username, realm or secret for every carrier. Preserve the exact trunk type, Voice platform, peer list, access-control policy and certificate behavior rather than copying another organization or region.

SIP registration

Not verified

The reviewed BYOC Cloud workflow describes provisioned BYOC Carrier or BYOC PBX trunks, outbound SIP destinations, source controls and inbound identifiers rather than a universal REGISTER workflow. Do not invent a registrar, Contact expiry or registration lamp. Confirm the selected carrier's current handoff, OPTIONS behavior, accepted transaction and call outcome separately.

Inbound delivery

Documented

An inbound INVITE needs a regionally unique Inbound SIP Termination Identifier so Genesys Cloud can associate the call with the correct organization. Genesys documents FQDN, TGRP and DNIS methods, with a custom header only when standard methods are unavailable. Identification, Number Plan Site transformation, destination routing, number ownership and final answer remain distinct checkpoints.

Routing and failover

Documented

The carrier questionnaire calls for SIP OPTIONS, 503 handling and sequential failover, while Genesys publishes regional proxy and media addresses. Those are interface and planning requirements, not proof of the selected carrier's target order, health thresholds, timer, capacity, geographic diversity, restoration sequence or established-call survival. Record and test only the approved new-call failure cases.

Number and regional availability

Not verified

BYOC Cloud connects Genesys Cloud to a separately chosen third-party carrier or device over the public Internet. Genesys regions and media locations do not establish carrier serviceability, number inventory, portability, regulatory eligibility or emergency support at an address. Bind every site and number to current Genesys and carrier qualification records.

Audio codecs and DTMF

Documented

Genesys' provider questionnaire recommends G.711 and requires out-of-band DTMF support, early media and hold behavior. This is an interconnect requirement, not proof of one trunk's complete codec list, packetization, telephone-event payload, offer and answer, transcoding or audio quality. Preserve both SDP directions and observed packets for the selected carrier path.

T.38 fax

Not verified

The questionnaire asks the provider to support fax pass-through, but the reviewed BYOC Cloud records do not establish a universal T.38 profile, G.711 fallback, switchover sequence, redundancy method, device compatibility or completed-page result. Qualify the exact carrier, number, gateway, document set and direction independently.

Signaling and media encryption

Documented

BYOC Cloud can use TLS over TCP and SRTP, but certificate roots, URI suffixes, ingress and egress ranges and cipher behavior vary between the legacy and Dynamic Cloud Voice platforms. The Dynamic platform guide says BYOC does not support client authentication or mutual TLS. Also, the configured transport controls outbound calls and is not enforced on received calls. Prove the actual platform, TLS role, certificate chain, SIP transport and SDP protection on both directions.

Concurrent calls and call starts

Not verified

The fair-use policy measures BYOC Cloud usage minutes for billing; it is not a simultaneous-call or calls-per-second entitlement. The reviewed sources do not publish one universal carrier capacity, burst rate or emergency reserve. Size Genesys telephony limits, carrier channels and rate limits, SBC sessions where present, access, firewall state and media resources separately.

Emergency calling

Documented

Genesys directs BYOC customers to establish the physical location with the carrier and then configure emergency dialing in the site's Number Plan and Outbound Routes. A location record, emergency ANI, number classification, selected trunk, carrier dispatch record, callback path, internal notification, outage behavior and provider-approved validation method remain separate evidence.

Pricing model

Not verified

Genesys documents monthly fair-use allocations and overage treatment for BYOC Cloud usage, but the reviewed public pages do not establish the selected organization's current total. Obtain dated Genesys licensing and usage terms plus carrier numbers, channels or usage, access, equipment, emergency service, implementation, support, tax, renewal and termination terms.

Administration and support

Documented

Administrators create a cloud-media site, BYOC Carrier or BYOC PBX trunk, inbound identifier, destinations, Number Plan Site and outbound routes while coordinating carrier allowlists. Existing and Dynamic Cloud Voice trunks can have different addresses, certificate roots and URI suffixes. Maintain platform, region, organization, site, carrier, network, certificate, number, emergency, monitoring, escalation and rollback owners.

SMS and MMS

Not verified

The reviewed generic BYOC Cloud voice-trunk pages do not establish SMS or MMS eligibility, sender registration, throughput, retention or price for a carrier-provided number. A specialized WhatsApp Business Calling trunk subtype also does not prove generic text messaging on BYOC numbers. Qualify every messaging channel, number, country and commercial order separately.

Preserve legacy and Dynamic Cloud Voice platform evidence

Genesys' August 10, 2026 announcement says the Dynamic Cloud Voice platform will become the default for new BYOC Cloud trunks, but the reviewed announcement has no effective date. Existing trunks retain their current platform unless deliberately migrated. Do not infer a trunk's platform from the current create screen or from its age alone.

The Dynamic platform uses different ingress and egress ranges, a genesys.cloud request-URI suffix and Amazon Trust Services roots; legacy endpoints use different addresses, suffixes and DigiCert roots. Genesys recommends a new test trunk before migrating traffic. Preserve the current platform, UI reference values, DNS, address policy, certificate roots, approved test and rollback.

Route inbound calls with organization and site identity

Each inbound call needs the regionally unique Inbound SIP Termination Identifier so Genesys can select the correct organization. FQDN and TGRP are the standard methods; DNIS replacement and a custom header are bounded alternatives. This identity is separate from the public called number.

The selected Number Plan Site controls inbound transforms and later outbound transfers for calls that have not passed through another site. Trace carrier Request-URI and headers, organization identifier, selected site, normalized digits, Architect or user destination and final outcome without rewriting every field at once.

Treat transport configuration as directional

BYOC Cloud can send calls using UDP, TCP or TLS. Genesys warns that both ends must use the same transport, but the trunk setting controls the protocol used to send calls and is not enforced on received calls. Therefore a successful inbound call does not prove that the configured outbound transport or destination is correct.

For TLS, preserve the actual Voice platform, role, certificate chain, supported root and negotiated session. The Dynamic guide says BYOC does not support client authentication or mutual TLS. Keep source-address controls and the region-specific inbound identifier as independent authorization layers.

Separate provider requirements from accepted media

Genesys asks providers to support SIP OPTIONS, out-of-band DTMF, early media, hold, 503 and sequential failover, and recommends G.711 for the carrier interconnect. Those requirements help qualify a provider but do not establish one call's selected codec, digits, media addresses, SRTP state or quality.

Retain the actual offer and answer and observed media in both directions. Fax pass-through in the questionnaire is not universal proof of T.38 or completed pages. Size and failover must likewise use the selected carrier order and Genesys limits rather than the BYOC fair-use billing allowance.

Close emergency, commercial and operational records separately

Genesys requires BYOC emergency service to be established with the carrier and then configured through the site's Number Plan and Outbound Routes. Record the physical location, emergency ANI, route, carrier dispatch record, callback, notification, outage behavior and approved validation method.

Fair-use minutes describe billing rather than capacity. Preserve current Genesys licensing and usage terms, carrier charges, numbers, access, equipment and support separately. Generic BYOC voice documentation does not establish SMS or MMS on a carrier number. No organization, trunk, call, emergency workflow, message, capacity, price, availability or compatibility was tested for this guide.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Hub · Provider records reviewed individually on their listed dates; account-specific terms and availability require direct confirmation

SIP trunk provider research

Compare the connection model, call routing, media support and cost structure of documented SIP trunk services.

Explore topic →
Guide

SIP trunk IP authentication

Understand source-address trust and the consequences of a WAN address change.

Read guide →
Guide

SIP trunk failover and redundant calling paths

Design alternate routing without assuming active calls will survive.

Read guide →
Protocol reference · RFC 3261 SIP, RFC 3711 SRTP, RFC 4568 SDP Security Descriptions, RFCs 5763 and 5764 DTLS-SRTP, and current Asterisk PJSIP documentation reviewed October 6, 2026; deployed endpoints, intermediaries, certificates and calls require direct verification

SIP TLS and SRTP: what each protects

Distinguish adjacent-hop signaling protection, SRTP media protection, SDES and DTLS-SRTP keying, and the actual termination points on every call leg.

Read guide →
Guide

Planning emergency calling for a VoIP deployment

Assign responsibility for location, routing and outage procedures before rollout.

Read guide →
Troubleshooting · Current first-party Genesys Cloud BYOC Cloud and BYOC Premises architecture, carrier, Edge, trunk, routing, transport, TLS, Dynamic Cloud Voice migration, site, status, capacity, emergency-service and hardware-lifecycle documentation reviewed October 10, 2026; the Dynamic Cloud Voice default announcement has no effective date in the reviewed record and existing Cloud trunks retain their current platform unless deliberately migrated; Genesys states support for the BYOC Premises Genesys Hardware Solution ends December 1, 2026; no Genesys Cloud organization, license, carrier order, Edge, trunk, interface, site, location, number plan, route, peer, registration, address, certificate, firewall, call, media stream, fax, emergency workflow, message, usage record, price, capacity, availability, compatibility, migration or support response was inspected or tested

Genesys Cloud BYOC trunk is down or calls fail

First separate BYOC Cloud from BYOC Premises, then trace one failed call through the selected cloud Voice platform or premises Edge, trunk state, site routing, carrier response and media before changing firewall or routing policy.

Read guide →
Interactive tool

Concurrent call planning calculator

Turn an explicit simultaneous-use assumption into a rounded-up external-call scenario.

Open tool →