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

Genesys Cloud BYOC Premises: Edge, carrier and hardware-lifecycle boundaries

Connect a third-party carrier through a premises Edge while keeping the external SIP trunk, Edge ownership, interface binding, site routing, capacity, emergency service and the December 1, 2026 Genesys-hardware support boundary separate.

Reviewed 2026-10-10Current first-party Genesys Cloud BYOC Premises architecture, Edge, external-trunk, interface, site, status, capacity, emergency-service and hardware-lifecycle documentation reviewed October 10, 2026; Genesys states that support for its BYOC Premises Genesys Hardware Solution ends December 1, 2026, while the Customer Hardware Solution is a separate provisioning path; no Genesys Cloud organization, license, Edge, customer server, carrier order, trunk, interface, site, Edge group, phone, number plan, route, peer, registration, address, certificate, firewall, call, media stream, emergency workflow, price, capacity, availability, compatibility, migration or support response was inspected or testedAdvancedDocumentation based · not lab tested

Classify where the SIP connection terminates

BYOC Premises terminates the third-party carrier or device connection on a premises-based Genesys Cloud Edge. The Edge supplies media-server, SIP registrar, SIP proxy and call-routing functions as a cloud-managed appliance. That is different from BYOC Cloud, where the SIP trunk terminates on Genesys Cloud AWS-based media resources.

Record the organization, region, Premises media-model site, Edge and Edge group, bound network interface, External SIP trunk, carrier or gateway, numbers, emergency owner and support contacts. A carrier service, an Edge and the Genesys Cloud application are separate ordered and operated boundaries.

Treat the December 1, 2026 deadline as hardware-path specific

Genesys says support for the BYOC Premises – Genesys Hardware Solution ends December 1, 2026 and that its hardware partner no longer sells those Edge devices. The announcement does not say that every BYOC Premises deployment or External SIP trunk ends on that date. Genesys separately documents a Customer Hardware Solution Edge provisioning path.

Inventory the actual Edge model and ownership before choosing a response. For a Genesys-supplied appliance, retain the contract, support status, replacement or migration decision, change window, rollback and emergency-calling continuity. Do not describe customer hardware as an in-place firmware conversion or claim continued support without an approved migration record.

Bind the carrier handoff to the exact External SIP trunk

Genesys directs administrators to obtain the carrier's provisioning answers and then match the External SIP trunk configuration. The Premises External SIP type has its own listen port, prioritized outbound SIP servers or proxies, optional registration and availability behavior, source-address access control and advanced settings.

Preserve protocol and port, peer order, address or CIDR controls, authentication or registration behavior, caller identity, codecs, DTMF, fax and security from the selected order. The base guide leaves digest authentication, registration and availability disabled; that default is not evidence that every carrier uses IP authentication or no health mechanism.

Follow the Edge, interface, site and group chain

An External SIP trunk must be joined to the intended Edge network interface, and a BYOC Premises site uses the Premises media model. Edge groups let premises Edges share trunks, while phone trunks connect phones or WebRTC endpoints. These objects do different jobs.

Retain the physical or virtual Edge identity, software and installer versions, cloud connectivity, interface address, selected external trunk, Edge-group membership, phone-trunk inheritance, site, number plan and outbound route. A green trunk on one interface does not prove the call selected that Edge, site or route.

Read status and capacity without turning them into call proof

Genesys exposes Edge cloud connectivity, external-trunk status, software and hardware details in the Edge information panel. Trunk indicators distinguish operational, partial, down, disabled, unknown and provider-managed states. Registration can update availability when the peer supports it, but an in-service or registered state is not a completed call.

Premises Max Calls is per trunk, and zero means unlimited at the trunk setting rather than unlimited Edge capacity. Keep external-trunk limit, call-start rate, Edge-model capacity, current calls and carrier sessions separate. Accept signaling, answer, two-way media, DTMF, fax and failover with bounded calls rather than from configuration values alone.

Close emergency, migration and commercial evidence separately

Genesys says not to assign an emergency number plan to a BYOC trunk until the carrier's emergency service and the location for the numbers are verified. Retain physical location, emergency number plan, outbound route, trunk, ANI, carrier dispatch record, callback, notifications, outage behavior and an approved validation method.

A migration from expiring Genesys hardware can change Edge identity, interfaces, capacity, routing and failure modes even if the public numbers and carrier remain. Reaccept representative inbound, outbound, transfer, media, failover and emergency workflows after the selected change. No organization, Edge, carrier path, call, migration or emergency workflow was validated 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

Provider research · Current 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 tested

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.

Read guide →
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 →
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 →