Telephony & connectivity
Genesys Cloud Voice, BYOC Cloud & BYOC Premises
Choose the right telephony model for Genesys Cloud CX – Genesys Cloud Voice, BYOC Cloud, BYOC Premises or a hybrid – and have it designed and delivered by certified specialists.
Genesys Cloud Voice, BYOC Cloud and BYOC Premises give you three ways to connect your contact centre to the telephone network, and the right choice shapes cost, resilience, compliance and access to AI. QVCCS helps you choose and design telephony connectivity for Genesys Cloud CX, then builds it: carrier and trunk configuration, number porting, emergency calling, media regions and hybrid media, including moves off Genesys-supplied Edge hardware before its end of life. Certified architects and telecoms engineers from our own bench test every path, then supports the result in line with your Genesys Cloud CX support model, with out-of-hours callout where you contract it.
- Solution Architect
- IT Systems, Telecoms & SIP Engineer
- Project Manager
- Systems Integration Tester
- Support Engineer
- Genesys Certified Specialist
- Genesys as your carrierGenesys Cloud Voice provides phone service through Genesys Telecom, with no carrier contract, no equipment and redundancy across three or more availability zones.
- Bring your own carrierBYOC Cloud brings SIP trunks from your carrier into Genesys Cloud media resources in AWS over the internet.
- Premises and hybrid mediaBYOC Premises meets regulatory or connectivity needs; combined with cloud media as a hybrid, it keeps AI features within reach.
- Numbers, regions and emergenciesNumber porting, emergency calling and regional media planned carefully, so every site and country is covered.
- Genesys Cloud CX licence tiers explained: CX 1 to CX 4, add-ons and modelsGenesys Cloud CX 1 to CX 4 compared: what each tier includes, digital-only options, add-ons, Experience Units and named versus concurrent licensing.Read the guide
- Genesys Cloud CX cost explained: what drives the billGenesys Cloud pricing explained: published list prices for CX 1 to CX 4, named, concurrent and hourly licences, add-ons, AI units, telephony and one-off costs.Read the guide
- Genesys Cloud telephony: the handbook for Voice, BYOC Cloud and BYOC PremisesA detailed handbook to Genesys Cloud telephony: Genesys Cloud Voice, BYOC Cloud, BYOC Premises, hybrid media, trunks, porting, emergency calls and quality.Read the guide
- Genesys Cloud network and firewall requirements: domains, IP ranges and portsGenesys Cloud network requirements in one place: domains by region, media IP ranges, WebRTC and BYOC ports, TLS, bandwidth, latency, QoS and proxy guidance.Read the guide
- Genesys Cloud Edge end of life: moving premises Edges to hybrid and cloud mediaGenesys Edge hardware reaches end of support on 1 December 2026 and end of life on 1 June 2027. How to move premises Edges to hybrid and cloud media, in steps.Read the guide
- Cloud VoiceGenesys Telecom as carrier
- BYOC CloudYour carrier's SIP trunks
- BYOC PremisesCustomer hardware Edges
- Hybrid mediaCloud and premises
- Number portingKeep existing numbers
- Emergency callingLocations and routing
Most enterprises combine options – QVCCS designs the mix that fits each region.
01
Choosing between Genesys Cloud Voice and BYOC
Every Genesys Cloud CX contact centre needs a way to reach the public telephone network, and the choice between Genesys Cloud Voice, BYOC Cloud and BYOC Premises is one of the most consequential early decisions in a programme. It affects commercial arrangements with carriers, the way numbers are managed, where media is processed, how resilience is achieved, and which regulatory obligations you can meet. It can also affect which Genesys Cloud capabilities are available on each call. Making the choice deliberately, with the trade-offs understood, avoids expensive rework later in the programme.
There is rarely a single answer for a whole enterprise. A business might use Genesys Cloud Voice in one country, keep an existing carrier contract through BYOC Cloud in another, and retain premises media in a location with specific regulatory needs. QVCCS starts by understanding your sites, countries, call volumes, carrier contracts, numbering estate and compliance requirements. Our architects then compare the options for each region and recommend a telephony model that balances cost, control, resilience and capability, documented clearly so commercial, technical and compliance stakeholders can agree it.
02
How each telephony option works
With Genesys Cloud Voice, Genesys Telecom provides your phone service. There is no separate carrier contract and no on-premises equipment; media is processed in the cloud, scales automatically and is redundant across three or more AWS availability zones. You can buy DID and toll-free numbers or port existing ones, and controls such as prefix blocking and high-cost destination blocking are built in. BYOC Cloud, short for bring your own carrier, terminates SIP trunks from a cloud carrier or your own premises equipment over the internet into Genesys Cloud media tier resources in AWS. It suits organisations with existing carrier relationships, specialist number ranges or commercial agreements they wish to keep.
BYOC Premises is a premises-based option for regulatory or connectivity needs, and it can be combined with cloud media as hybrid media; organisations created since May 2022 are hybrid-capable by default. Genesys strongly recommends hybrid over premise-only, because premise-only cannot use Virtual Agent, Agentic Virtual Agent, Agent Copilot, Agent Assist Voice, AudioHook, Audio Connector or real-time sentiment analysis, and transcription runs post-call. The Genesys Hardware Solution Edges reached end of support in 2025 and reach end of life on 1 June 2027, after which they stop operating. Genesys recommends moving to cloud media, or to the BYOC Premises Customer Hardware Solution where premises media is unavoidable. QVCCS builds these dates into every telephony roadmap.
Telephony is the front door to your contact centre – choose it for resilience and future capability, not just for this year's price.
03
Designing numbers, emergency calls and media
Telephony design goes well beyond picking an option. Number porting needs careful planning: which ranges move, in what order, how inbound routing is tested before each port, and how the old platform keeps working until cut-over. Emergency calling must be designed for every site and, increasingly, for home workers, with locations and routing that meet local regulations. QVCCS documents numbering plans, porting schedules and emergency calling arrangements, and works with carriers and your compliance team so nothing is left to assumption when the switch happens.
Media placement shapes call quality and resilience. Our architects consider which Genesys Cloud regions serve your users and customers, and whether Global Media Fabric should let your organisation use media regions closer to them. We decide how SIP trunks are routed and protected, how internet connectivity and any session border controllers are configured for BYOC Cloud, and how the design behaves if a carrier, link, site or region fails. New BYOC Cloud trunks now use the Dynamic Cloud Voice Platform, with its own IP addresses and certificates, so we plan for it from the outset. Codecs, capacity, failover and monitoring requirements are defined in the Low-Level Design, with the tests that will prove them.
04
Who delivers your telephony, and the details that bite
Telephony decisions cut across commercial, network, compliance and contact centre teams, so we muster a team from our own bench that can speak to all of them. A Solution Architect leads the options analysis and owns the HLD and LLD. An IT Systems, Telecoms & SIP Engineer runs a remote readiness survey of sites, network and telephony, configures trunks, sites, number plans, outbound routes and emergency settings, and works with your carriers. A Project Manager coordinates porting windows and carrier dependencies through the RAID log, and a Support Engineer prepares the handover into live support. Telephony testing is deliberately destructive: our Systems Integration Tester calls every number range from every site, checks caller identity and emergency procedures, then fails trunks, links and SBCs to prove resilience. Engineers monitor cut-over days remotely from a live bridge until call patterns settle.
A handful of details cause most telephony trouble. Caller identity presentation must follow local rules on valid, dialable numbers, and a number that customers cannot call back damages trust in your outbound calls. Number formats need to be consistent, so outbound routes and data lookups match whether a number arrives with a country code or without one. Porting depends on the losing carrier as much as the gaining one, so dates are agreed in writing and a fallback redirect is ready if a port slips. Failover should be tested in both directions, including the return to normal once a failed trunk recovers. Home workers complicate emergency calling, because their location is not the office address. Finally, toll-free and geographic ranges often have different carriers, contracts and porting rules, so each is planned separately.
05
Running carrier connectivity in live service
Once live, telephony must simply work, all day, every day. QVCCS support follows your consumption model: where Genesys or your provider runs first-line support, we act as the telephony specialist and escalation layer behind it; where you contract support with us, we provide SLA-based cover with alarms that call out an engineer automatically when trunks degrade or calls fail. We manage changes such as new number ranges, additional sites, carrier changes and regulatory updates, and our release readiness reviews track Genesys announcements, such as the Genesys Hardware Solution end of life and the move of new BYOC Cloud trunks to the Dynamic Cloud Voice Platform, for their impact on your design. When the time comes to move from premises media to cloud or hybrid, we plan and deliver that transition with the same care as the original build.
Good telephony operations also depend on visibility. We help you define the measures that matter, such as call failure rates by trunk, answer and abandonment patterns by number range, and quality trends by region, and we build the dashboards and alerts that expose them. QVCCS reviews these with your operations and network teams, so capacity is added before peaks rather than after them, and carrier issues are raised with evidence. That steady, data-led approach keeps your Genesys Cloud Voice or BYOC estate dependable as call volumes, sites and regulatory requirements change over the years.
What you get from QVCCS
- Region-by-region comparison of Genesys Cloud Voice, BYOC Cloud and Premises
- Recommended telephony model with commercial and capability trade-offs explained
- High-level and low-level designs for trunks, media, sites and resilience
- Edge end-of-life plan for any Genesys Hardware Solution devices
- Number porting plan, rehearsed cut-over runbook and rollback arrangements
- Emergency calling design agreed with your compliance team
- Trunk monitoring and alarming, with support aligned to your model
Genesys documentation references
- Telephony connection options overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- About Genesys Cloud Voice – Genesys Cloud Resource Centerhelp.genesys.cloud
- About BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
- About hybrid media – Genesys Cloud Resource Centerhelp.genesys.cloud
- Deprecation: BYOC-Premises – Genesys Hardware Solution (end of life)help.genesys.cloud
- Deprecation: BYOC Premises – Customer VM Solutionhelp.genesys.cloud
- About Global Media Fabric – Genesys Cloud Resource Centerhelp.genesys.cloud
- Dynamic Cloud Voice Platform as the default for new BYOC Cloud trunkshelp.genesys.cloud
Methods & templates
Genesys Cloud Voice, BYOC Cloud & BYOC Premises: quality gates, stage by stage
Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For Genesys Cloud Voice, BYOC Cloud & BYOC Premises, the work concentrates in Discover, Design, Prove and Transition, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.
- 01DiscoverDiscovery sign-off
- 02DefineRequirements baseline
- 03DesignDesign authority review
- 04BuildBuild complete
- 05ProveGo / no-go readiness
- 06TransitionOperational acceptance
- 07Run & evolveService reviews
Site, network and telephony readiness survey
Inventories carriers, number ranges, Edges, sites and regulations so the telephony model starts from facts, not assumptions.
Options analysis and architecture decision records
Compares Genesys Cloud Voice, BYOC Cloud, BYOC Premises and hybrid media per region, including AI feature and end-of-life impacts.
Low-Level Design / build book
Specifies trunks, sites, media regions, number plans, outbound routes, emergency settings, codecs and failover exactly as configured.
Telephony testing (carriers, numbers, failover)
Proves every number range, caller ID, emergency route and failover scenario before any port or cut-over.
Number porting plan and cut-over runbook
Sequences ports and redirects in rehearsed waves with test calls, rollback steps and engineers on hand.
How we deliver
Genesys Cloud Voice, BYOC Cloud & BYOC Premises: your engagement at a glance
- 01AssessRemote readiness survey of sites, network, carriers, numbers, volumes, Edges and regulations across every region.
- 02RecommendCompare Genesys Cloud Voice, BYOC Cloud, BYOC Premises and hybrid media, and agree the model per region.
- 03DesignLow-level designs for trunks, media regions, numbering, emergency calling, security, capacity and failover.
- 04Build & portCertified engineers configure telephony, coordinate carriers and run rehearsed number ports with rollback plans.
- 05OperateCut-over support and hypercare, then telephony support alongside your provider or, where contracted, direct from us.
- Solution Architect
- IT Systems, Telecoms & SIP Engineer
- Project Manager
- Systems Integration Tester
- Support Engineer
- Genesys Certified Specialist
Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →
In practice
Where we have delivered this
A major global airline: premises Edges to hybrid media and five cloud media regions
How QVCCS made a major global airline's Genesys Cloud CX org hybrid, linking 18 premises Edges to five Global Media Fabric regions and carrier trunks worldwide.
- Agents
- More than 400
- Licence
- Genesys Cloud CX
A South African financial services organisation: from Edges to cloud media, on time
How QVCCS moved a South African financial services organisation off end-of-life Genesys Edges to hybrid and cloud media, a new carrier and Operator Connect.
- Agents
- 32
- Licence
- Genesys Cloud CX 1
A US health benefits provider: Avaya to Genesys Cloud CX, with an immense self-service IVR
How QVCCS rebuilt a US health benefits provider's immense IVR on Genesys Cloud CX: 172 users, 88 numbers, voice bots and 17 back-end APIs, off Avaya in 2025.
- Users
- 172
- Licence
- Genesys Cloud CX 1
Tools we use here
From the QVCCS App Suite
- DID Conflict CheckerA read-only Genesys Cloud audit mapping every inbound DID to its Architect flow, flagging stale, orphaned and dual-routed numbers and caller-ID clashes.
- Trunk MonitorReal-time health and call volume for the external SIP trunks of a Genesys Cloud CX organisation, with sub-second up and down alerts and an audited event log.
- SIP Trace AnalyserFind out why Genesys Cloud calls failed: search for SIP failures, read the recorded SIP messages, attribute them to the trunk, and export a trace or PCAP.
Further reading
From QVCCS Innovation
- Innov8r: how QVCCS tests Genesys Cloud CX numbers, IVRs and DTMF from the caller's sideHow QVCCS engineers test every Genesys Cloud CX number, IVR flow and DTMF menu from the caller's side with Innov8r, an in-house SIP softphone the team built.13 October 2026
- Where does every number go? Auditing Genesys Cloud DIDs, flows and caller IDsHow our DID Conflict Checker maps every Genesys Cloud DID to its Architect flow and flags agent profile clashes, dual-routed numbers and caller-ID conflicts.28 May 2026
- Trunk Monitor: sub-second SIP trunk health for Genesys Cloud, with the evidenceSIP trunk monitoring and alerts for Genesys Cloud: a 5-second trunk metrics poll fused with notification topics for sub-second up/down, a log and evidence.19 May 2026
- SIP Trace Analyser: from “why did this call fail?” to the trunk and the response codeHow we joined Genesys Cloud analytics and SIP trace metadata to find failed voice calls, hunt response codes like 503 and attribute each failure to a trunk.29 April 2026
Questions
Genesys Cloud Voice, BYOC Cloud & BYOC Premises: common questions
What is the difference between Genesys Cloud Voice and BYOC Cloud?
With Genesys Cloud Voice, Genesys Telecom is your carrier, so there is no separate carrier contract or on-premises equipment, and numbers can be bought or ported. With BYOC Cloud you keep your own carrier, whose SIP trunks connect over the internet into Genesys Cloud media resources in AWS. Both process media in the cloud.
Should we choose BYOC Premises?
Only where regulation or connectivity demands it. Premise-only cannot use features such as Virtual Agent, Agent Copilot, AudioHook or Audio Connector, so Genesys strongly recommends hybrid media. Genesys Hardware Solution Edges reach end of life on 1 June 2027; the Customer Hardware Solution remains for premises needs.
Can we keep our existing phone numbers on Genesys Cloud?
In most cases numbers can be ported to Genesys Cloud Voice or kept with your carrier through BYOC Cloud. Porting needs careful planning: which ranges move and in what order, how inbound routing is tested before each port, and a fallback redirect ready in case a port date slips, so customers keep reaching you throughout.
Last reviewed