Telephony & connectivity
SIP trunks, carriers & SBCs
Carrier-grade voice for Genesys Cloud CX: SIP trunks, carriers and session border controllers designed, built, tested and supported by certified telephony engineers.
Genesys Cloud SIP trunks are the foundation every customer conversation travels over, and QVCCS engineers them so they never become the weak link. Telecoms engineers from our own bench design Bring Your Own Carrier connections end to end: carrier selection against Genesys carrier requirements, session border controller configuration, codecs, TLS and SRTP encryption, failover, capacity, number plans and DID management. We build and test each trunk against your real call patterns, then manage the cut-over so numbers move with confidence, giving you dependable voice on Genesys Cloud CX with your choice of carrier and resilience designed in from day one.
- Solution Architect
- IT Systems, Telecoms & SIP Engineer
- Project Manager
- Systems Integration Tester
- Support Engineer
- Your carrier, your termsKeep the carrier contracts, rates and number ranges you have negotiated, connected into Genesys Cloud CX through a well-engineered BYOC design.
- Encrypted by designTLS signalling and SRTP media planned from the start, with certificates, ciphers and carrier capabilities agreed before any trunk goes live.
- Failover that is provenRedundant trunks, SBCs and routes, with failover behaviour tested deliberately rather than discovered during an outage.
- Numbers under controlNumber plans, outbound routes and DID inventories documented and mapped to flows, sites and emergency calling requirements.
- 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
- 01PSTN callerDials your DID or freephone
- 02Your carrierSIP trunk, number ranges
- 03SBC or BYOC CloudTLS signalling, SRTP media
- 04Genesys media tierTrunk terminated in AWS
- 05Architect flowDID mapped to call routing
Each hop is a design decision: carrier, SBC, transport security, trunk and routing.
01
Why Genesys Cloud SIP trunks deserve expert design
Genesys Cloud SIP trunks carry every voice interaction your contact centre handles, so their quality is felt by every customer and every agent. One-way audio, clipped greetings, failed transfers and calls that never arrive usually trace back to trunk, codec or SBC decisions made in a hurry. Bring Your Own Carrier gives you the freedom to keep your preferred carrier, your negotiated rates and your existing number ranges, but that freedom brings responsibility for the connection between carrier and platform. QVCCS takes that responsibility seriously. Our certified telephony engineers treat the trunk as a critical system with its own requirements, design, test plan and support model.
For contact centre leaders, a sound trunk design means predictable call quality, enough capacity for peak days and campaign launches, and resilience that holds when a carrier or data centre has a problem. For technical architects, it means clear answers on signalling, media paths, encryption, number formats and monitoring. We bring both perspectives into the same conversation. Our consultants translate service levels, opening hours and business continuity needs into concrete telephony requirements, and our engineers turn those requirements into trunk, SBC and routing configuration that your carrier, your network team and Genesys Cloud CX all agree on.
02
How BYOC trunks connect to Genesys Cloud CX
With BYOC Cloud, SIP trunks are terminated over the internet into Genesys Cloud media tier resources hosted in AWS. Your carrier, or a session border controller you operate, exchanges signalling with the published Genesys Cloud SIP addresses for your region, while media flows to autoscaling services that draw on a large pool of AWS addresses, which matters for firewall design. Carriers must be SIP-compliant with full Record-Routing, support UDP, TCP or TLS, present a publicly routable address and allowlist the Genesys signalling addresses. Inbound calls are matched to your trunk by FQDN, TGRP, DNIS replacement or a custom termination header. New trunks use the Dynamic Cloud Voice Platform, with separate ingress and egress addresses.
Within Genesys Cloud CX, external trunks define how the platform talks to each carrier or SBC: trunk type, transport protocol, codecs such as G.711, G.722, G.729 and Opus, SRTP cipher suites, digest authentication and SIP access control, number formatting and the handling of SIP headers. The transport setting governs calls Genesys Cloud sends, so both ends must be configured to match, and TCP is preferred where large user-to-user data could exceed UDP packet limits. Sites, number plans and outbound routes then decide which trunk carries which call, and DIDs are mapped to Architect inbound flows. Our engineers capture every parameter in the Low-Level Design and align it with the carrier's interconnect specification.
Customers never see your SIP trunks, but they hear every decision made about them – so we design each one as a critical system.
03
Carriers, SBCs, codecs and failover decisions
Carrier selection is about more than price per minute. Coverage in the countries you serve, support for encrypted signalling and media, number porting processes, emergency calling obligations, presentation of caller ID and the quality of the carrier's own support all matter. Where an SBC sits between carrier and Genesys Cloud CX, its configuration determines header manipulation, codec negotiation, topology hiding and how faults are isolated. QVCCS works with your carrier and SBC vendor to agree an interconnect design both sides can support, and we never assume a capability until it has been confirmed and tested on a real call.
Codecs and capacity need equal care. We agree codec preferences that balance audio quality, bandwidth and compatibility with recording, transcription and speech analytics, and we size concurrent call capacity from your forecast peaks plus headroom for growth and outbound campaigns. Resilience is designed as a set of explicit scenarios: what happens if a trunk, an SBC, a carrier point of presence or a Genesys Cloud region becomes unavailable. For each scenario we define the expected behaviour, configure redundant trunks and routes to deliver it, and prove it by deliberately taking components out of service during testing.
Encryption and number management complete the picture. TLS protects signalling and SRTP protects media, but both depend on certificates, cipher suites and carrier support being aligned on every leg. On the Dynamic Cloud Voice Platform, Genesys presents certificates issued under Amazon Trust Services roots, so your SBC must trust Amazon Root CA 1 and 2, and mutual TLS is not supported. We plan certificate trust, ownership and renewal so an expired or untrusted certificate never takes your contact centre offline. On the numbering side, we build an inventory of every DID, freephone and geographic number, recording which flow, site and outbound route each uses, and agree formats for inbound and outbound presentation.
04
How QVCCS delivers your SIP trunk project
Trunk projects sit between your carrier, your network team, your SBC vendor and the contact centre, so QVCCS musters a team from its own bench led by telecoms engineering and takes collective responsibility for the result. A Solution Architect leads discovery, owns the high-level topology and chairs design authority. An IT Systems, Telecoms & SIP Engineer runs the site, network and telephony readiness survey, writes the Low-Level Design covering every trunk parameter, SBC rule, codec and route, and leads the technical conversations with carriers. Where a carrier or SBC vendor needs a formal interconnect document, we write the Interface Control Document. A Project Manager coordinates dependencies through the RAID log, and the Senior Platform Practice Lead peer-reviews the design before build begins.
Testing and cut-over are where trunk projects earn their reputation. Our Systems Integration Tester runs a telephony test pack, traced to the requirements, covering inbound and outbound calls, caller ID presentation, DTMF, transfers, conferencing, recording, encryption, emergency numbers and every failover scenario in the design. Negative testing deliberately removes trunks, SBCs and links and presents malformed or unexpected signalling. Number porting and DID cut-overs follow a porting plan and a rehearsed cut-over runbook, in controlled waves with rollback steps and test calls after each change, run from a remote bridge with your carrier and network team. Porting windows are agreed with the losing carrier early, so every wave has a fixed, rehearsed slot.
05
Monitoring and supporting carrier connectivity
Trunks change over time. Carriers migrate platforms, certificates expire, number ranges grow and traffic patterns shift with every new product or campaign. Where you contract support with QVCCS, we provide SLA-based support and maintenance for Genesys Cloud SIP trunks and the configuration around them, up to 24x7x365, with monitoring and alarming that watch trunk health and call quality and raise automated engineer callouts when something degrades. Where Genesys or another provider runs first-line support, our telecoms engineers work inside that model as the specialist escalation and change layer. Release readiness reviews track Genesys changes such as the move of new BYOC Cloud trunks to the Dynamic Cloud Voice Platform, and we review capacity against demand, plan certificate renewals ahead of expiry, and manage new carriers, countries or DIDs with the same design discipline used at go-live.
What you get from QVCCS
- BYOC topology assessment against Genesys carrier requirements
- Low-level trunk, codec, encryption and routing design
- Interface control documents agreed with your carrier and SBC vendor
- DID inventory mapped to sites, flows and outbound routes
- Telephony test pack including deliberate failover testing
- Porting plan and cut-over runbook with rollback steps
- Monitoring, alarming and engineer callout where you contract support with us
Genesys documentation references
- Carrier requirements for BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
- Dynamic Cloud Voice platform overview and migration guidehelp.genesys.cloud
- Choose a trunk transport protocol – Genesys Cloud Resource Centerhelp.genesys.cloud
- External trunk settings – Genesys Cloud Resource Centerhelp.genesys.cloud
- About BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
- Telephony connection options overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Cloud and generic SIP trunk using Mediant SBC – AudioCodes configuration noteaudiocodes.com
Methods & templates
SIP trunks, carriers & SBCs: how quality is built in
Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For SIP trunks, carriers & SBCs, 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
Checks carriers, SBCs, firewalls, number ranges and capacity against Genesys BYOC Cloud carrier and network requirements.
Low-Level Design / build book
Records every external trunk setting, SBC rule, codec, cipher suite, number plan and outbound route as it will be built.
Interface Control Document (ICD)
Sets out the interconnect agreed with your carrier and SBC vendor: addressing, inbound routing method, transport, certificates and headers.
Telephony testing (carriers, numbers, failover)
Proves call paths, caller ID, DTMF, encryption, emergency numbers and each failover scenario on real calls.
Number porting plan and cut-over runbook
Moves DIDs and freephone numbers in controlled waves with test calls, rollback steps and engineers standing by remotely.
How we deliver
SIP trunks, carriers & SBCs: one accountable team, start to finish
- 01AssessReadiness survey of carriers, number ranges, volumes, sites, SBCs and network against Genesys carrier requirements.
- 02DesignHigh-level topology and low-level trunk, SBC, codec, encryption and number plan design, signed off before build.
- 03BuildCertified engineers configure external trunks, sites, outbound routes and DIDs alongside your carrier and SBC teams.
- 04Test & cut overCall scenario, encryption and failover testing, then porting and cut-over in controlled waves with rollback ready.
- 05SupportSupport aligned to your model – direct from us or via your provider – plus certificate management and capacity reviews as traffic grows.
- Solution Architect
- IT Systems, Telecoms & SIP Engineer
- Project Manager
- Systems Integration Tester
- Support Engineer
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 global industrial technology group: two always-open internal desks from NiCE CXone
How QVCCS moved a global technology group's always-open IT service desk and physical security desk from NiCE CXone to Genesys Cloud CX in a managed service.
- Users
- About 65
- Licence
- Genesys Cloud CX 3
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 major US resort and casino: Genesys Cloud CX beside its hotel PBX, with secure payments
How QVCCS put 125 agents of a major US resort and casino on Genesys Cloud CX beside its Avaya PBX, with secure card payments in the call path.
- Agents
- 125 concurrent
- Licence
- Genesys Cloud CX 3
Tools we use here
From the QVCCS App Suite
- 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.
- IP RangesUser guide to the QVCCS IP Ranges app: filter Genesys Cloud's published IP ranges by region, purpose and direction, and export them for firewall changes.
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
- 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
- Genesys Cloud IP addresses and ranges for firewall allow lists, by region and purposeGenesys Cloud IP addresses and ranges for your firewall allow list, by region from London to Zurich: explore, filter and export them on this page.08 April 2026
Questions
SIP trunks, carriers & SBCs: common questions
What is BYOC Cloud in Genesys Cloud CX?
BYOC Cloud is the Bring Your Own Carrier option in which SIP trunks are terminated over the internet into Genesys Cloud media tier resources in AWS. Your carrier must meet Genesys requirements for SIP compliance, transport and addressing. New trunks use the Dynamic Cloud Voice Platform.
Do I need a session border controller for Genesys Cloud?
Not always. Many carriers connect directly to BYOC Cloud, and Genesys notes that an SBC may be needed where premises equipment must communicate with the media tier. SBCs also help with header manipulation, topology hiding and interworking, and vendors publish configuration notes for Genesys Cloud. Our engineers assess your carrier, network and security requirements and recommend whether an SBC adds value.
Can Genesys Cloud SIP trunks use TLS and SRTP encryption?
Yes. Trunks can use TLS signalling and SRTP media, provided your carrier or SBC supports them. On the Dynamic Cloud Voice Platform your SBC must trust the Amazon Trust Services root certificates, and mutual TLS is not supported. We agree certificates, cipher suites and renewal with every party, then test encryption on real calls before go-live.
How do you move our numbers to Genesys Cloud without disruption?
We build a full inventory of your numbers, map each one to its target flow and route, and port or redirect them in planned waves. Every wave has test calls, a rollback plan and engineers on a remote bridge with your carrier, so issues are caught in minutes rather than reported by customers.
Last reviewed