Handbook

Genesys Cloud telephony: the handbook for Voice, BYOC Cloud and BYOC Premises

A detailed handbook for the people who choose, build and run Genesys Cloud telephony. It compares Genesys Cloud Voice, BYOC Cloud and BYOC Premises, then covers the new voice platform, the hardware deprecation, hybrid media, sites and number plans, trunks, porting, emergency calls, fraud controls, call quality and continuity. Checked against Genesys sources on 15 November 2026.

By Dave Tidwell, Managing Director34 min read

In short

  • The telephony choice decides carrier, billing, media location and survivability, not routing or most platform features.
  • In the UK, check non-geographic numbers, address rules and port verification before choosing Genesys Cloud Voice.
  • New BYOC Cloud trunks use the Dynamic Cloud Voice Platform; migrate existing trunks in their own change window.
  • Genesys hardware Edges lose support on 1 December 2026 and stop on 1 June 2027; hybrid media is the route out.
  • Set the default site, verify emergency calling with real calls, check the Block List, and accept against 150 ms round-trip.

01

What you are choosing, and the three options

This handbook is for the people who choose, build and run Genesys Cloud telephony: solution architects, telephony engineers, network leads and the programme managers who own the cutover. Every capability, limit, date and behaviour comes from Genesys's own documentation, listed in the sources and checked on 15 November 2026. Telephony is moving quickly: Genesys's own hardware Edges reach end of support on 1 December 2026, new BYOC Cloud trunks moved to a new platform in August 2026, and outbound defaults changed in June 2026. Where something is our own delivery practice rather than a Genesys statement, it is labelled QVCCS practice.

1.1 What is, and is not, being decided

Genesys Cloud offers three telephony connection options. The question is often asked too narrowly, so be clear about its scope before comparing them.

What you are choosing: where calls enter and leave Genesys Cloud; who holds the carrier contract; whether voice minutes appear on the Genesys bill or the telecoms bill; where media is processed; whether a site keeps calling when its internet fails; and how numbers are bought, moved and assigned.

What you are not choosing: routing, queues, IVR flows, analytics or most platform features. All three options deliver calls to the same platform. Genesys describes the voice service as providing public telephony access to whatever Genesys Cloud services you subscribe to, and a queue behaves the same whichever trunk the audio arrived on. The important exception, a premises-only organisation, is covered in 1.4.

The options can be combined. Genesys says so directly, and hybrid media is how (part 5). But making an organisation hybrid media capable cannot be undone, so keep later decisions reversible by not converting anything you do not need to.

1.2 The three options compared

Genesys's own comparison covers the two cloud options; BYOC Premises is described separately because it puts hardware in your building.

Genesys Cloud telephony connection options
Genesys Cloud VoiceBYOC CloudBYOC Premises
What it isA fully cloud-based service with Genesys Telecom as the phone companyYour carrier's SIP trunks terminate over the internet on Genesys Cloud media resources in AWSYour carrier's trunks connect to an Edge device on your premises, which connects to Genesys Cloud
Voice providerGenesys Telecom (varies by country)Your third-party carrierYour third-party carrier
Carrier contract neededNoYesYes
EquipmentNoneNone, though some premises equipment may need an SBC to reach GenesysA premises Edge, from the Customer Hardware Solution
Media processing (IVR, recording, conferencing)In the cloudIn the cloudOn the Edge
Scaling and redundancyAutomatic, across three or more AWS Availability ZonesAutomatic, across three or more AWS Availability ZonesYour design: Edge capacity, Edge groups and sites

1.3 The same choice in plain terms

Ask where the phone company plugs in. With Genesys Cloud Voice, Genesys is the carrier: one contract, one bill, and numbers bought or ported in the admin console. With BYOC Cloud, your carrier's network reaches Genesys's cloud across the public internet: your contract, your minutes, no hardware. With BYOC Premises, your carrier plugs into a device in your building and that device connects to Genesys: your contract, and calls can keep working locally if the internet drops.

The consequence for a UK buyer is that only the third option gives local survivability, and the Genesys-supplied hardware for it is being retired (part 4). That collision is why this decision needs more attention now than it used to.

1.4 What a premises-only organisation cannot do

Genesys lists features that do not work in a premises-only configuration: Virtual Agent, Agentic Virtual Agent, Agent Copilot, Agent Assist Voice, Agent Feedback, AudioHook, Audio Connector and real-time sentiment analysis. Transcription works but runs after the call, and both transcription and recording uploads can be delayed by several hours. Genesys recommends hybrid media to reach the full feature set.

So the telephony option does constrain the platform in one direction. If a site needs premises media for survivability or regulation, design it as part of a hybrid media organisation from the start rather than as a standalone premises estate.

02

Genesys Cloud Voice

Genesys Cloud Voice is a voice over IP telephony service you activate for your organisation. It runs on Genesys Telecom, which Genesys describes as a second-generation, multi-carrier VoIP provider subject to all local telecom regulation. Its services are local, long distance and international calling, emergency services, toll-free services, number purchasing and number porting.

2.1 How it is charged, and what to compare

Genesys states that Genesys Cloud Voice pricing is based on phone numbers and usage per minute. The cost model therefore has two variables, and an estimate that includes only the per-number line has not priced telephony. QVCCS sells no licences or minutes and quotes no rates; prices come from Genesys or your reseller.

Moving to Genesys Cloud Voice moves voice spend onto Genesys's per-minute rates, which may or may not beat a mature enterprise carrier contract. Compare on your real call mix, including international minutes, before deciding.

2.2 Where it fits

The attractions are one vendor and one bill, quick deployment, no equipment to buy or maintain, and buying numbers in the console. Genesys Cloud Voice also brings outbound fraud controls that a self-managed SIP trunk does not (part 10). For a new contact centre with no carrier contract worth keeping, it is normally where we start, subject to the coverage checks below.

2.3 Coverage is not uniform

Genesys publishes coverage requirements and restrictions for every supported country, plus AWS region-specific availability. Read the country page itself, not the summary, for every country where you need numbers. The examples below show how much the rules vary.

Examples of Genesys Cloud Voice country restrictions
CountryExamples from Genesys's country page
JapanNational calling is supported only from Tokyo geographic numbers obtained through Genesys; outbound calls to free-phone, premium, emergency and short code numbers are not supported; no non-geographic numbers other than toll-free.
SingaporeToll-free numbers cannot make outbound calls; emergency services are not supported on national or toll-free numbers; number portability only for geographic numbers.
LatviaGeographic numbers are reachable only from within the EU; emergency services and international calls are not supported on toll-free or national numbers.
New ZealandEmergency call performance may not meet the relevant service standard; reachability issues on some international calls to 07 and 09 area codes.

2.4 The UK rules

The UK page is specific enough to decide the telephony question on its own. Genesys Cloud Voice does not offer non-geographic numbers in the UK, and 030 numbers can be assigned only to public sector bodies or not-for-profit bodies. For an organisation whose published number is an 03 or 08 non-geographic range, that single line can rule Genesys Cloud Voice out for those numbers.

  • Geographic numbers can be assigned only if the enterprise is physically located within the area associated with the number, based on city area codes, and need a corresponding UK address to activate.
  • Domestic toll-free numbers (0800, 0808 and 0500) need no address, but can be called only from within the UK, from landlines and mobiles.
  • Porting numbers in the UK depends on specific carrier agreements and is not guaranteed. Genesys advises submitting the list of numbers to the porting team for verification before requesting a port.
  • Number availability depends on supplier inventory; Number Management shows current availability for each area.

03

BYOC Cloud and the Dynamic Cloud Voice Platform

BYOC Cloud lets you define SIP trunks between Genesys Cloud's AWS-based Edge and Media Tier and third-party carriers over the public internet. It keeps your carrier contract and removes the hardware. In 2026 it also means understanding the Dynamic Cloud Voice Platform, which is now the default for new trunks.

3.1 Two warnings for the risk register

Genesys's BYOC Cloud overview carries two warnings that belong in the programme's risk register, not just the network team's notes. Real-time media (RTP) travels over the internet between your organisation's Genesys Cloud region and the carrier's termination point, so Genesys tells you to consider internet quality and latency before implementing. And the carrier or device must have a publicly reachable IP address, with the right ports open.

A related FAQ adds that trunks connect to media resources in the AWS region your organisation is based in. The media path is anchored to your core region, not to where agents or callers are. A UK organisation in the London region with a carrier terminating in Asia puts real-time media across that distance, unless Global Media Fabric changes it (part 8).

3.2 What the carrier must do

Genesys publishes carrier requirements for BYOC Cloud, and they are the document to send the carrier first. The carrier must comply with the relevant parts of the SIP standard, support UDP, TCP or TLS, use publicly routable addresses or host names, support record-routing, and allow Genesys Cloud's public SIP signalling addresses through its access control lists.

Inbound calls must carry an Inbound SIP Termination Identifier, unique within your organisation's region, so Genesys can associate them with your organisation and trunk. There are four ways to present it: FQDN, TGRP, DNIS replacement, or an inbound SIP termination header. Genesys recommends FQDN or TGRP for most implementations. Agree the method in writing before the carrier builds anything.

3.3 The documented build sequence

Genesys's quick start guide sets out the order. Following it avoids most of the half-configured trunks we are asked to rescue.

  1. Work with your carrier against the carrier requirements.
  2. Create a location. It is needed to enable services and is used for emergency services.
  3. Create a site and assign SIP and media resources.
  4. Create the SIP trunk to your carrier or PBX (BYOC Carrier or BYOC PBX).
  5. Configure an outbound route. Defaults exist, but you must assign a trunk to the route.
  6. Set up a number plan. Genesys says the defaults work for most users.
  7. Set up DID and toll-free numbers.
  8. Assign numbers to users, groups or phones.
  9. Place a test call with the Genesys Cloud call simulator.

3.4 BYOC Cloud alongside Genesys Cloud Voice

The options combine. A Genesys Cloud Voice customer can add a BYOC Cloud trunk to an IP-PBX and use number plans and outbound routes to decide which calls leave by that trunk rather than by Genesys. Cloud carrier for the public network and a BYOC trunk to the switchboard is a pattern we use often in multi-site organisations that keep their PBX (part 7).

3.5 The Dynamic Cloud Voice Platform

Genesys describes the Dynamic Cloud Voice Platform (DCVP) as an evolution of the voice platform for Genesys Cloud and BYOC Cloud SIP trunking, with improved performance, updated network endpoints and more security controls. New customers, and anyone creating new BYOC Cloud trunks, should use it. An announcement of 10 August 2026 confirms that all new BYOC Cloud trunks created after that release use DCVP automatically, that existing trunks stay where they are unless migrated, and that a future release will remove the option to choose the legacy platform when creating a trunk.

Some integrations already require it: Genesys's trunk configuration for Microsoft Teams states that you must be using DCVP. For organisations in Mexico or Singapore, Genesys's TLS specification points to the DCVP requirements only.

3.6 Migrating existing trunks

Genesys's own description of the job is precise: you can move trunks between the two platforms with a simple toggle, but changes to the remote SIP endpoints can be harder. The remote endpoint must use the new ingress IP addresses and egress address ranges, trust the TLS certificate authorities and support the TLS cipher list. The recommended sequence is to review prerequisites, create and test a new trunk, migrate existing trunks with the toggle, then update the carrier or SBC configuration.

04

BYOC Premises and the hardware deprecation

With BYOC Premises, an Edge device on your premises connects your carrier's SIP trunks to Genesys Cloud and provides media processing, SIP and telephony services at the edge of the network. It is the only option that can keep a site calling when its internet connection fails, and the one changing most in 2026 and 2027.

4.1 Three hardware solutions, one future

Genesys has offered three ways to produce a premises Edge. Two are ending or gone.

BYOC Premises hardware solutions and their status
SolutionWhat it isStatus
Genesys Hardware SolutionPreconfigured appliances sold through Genesys's hardware partner Arrow: Edge Standard v1, v2 and v3, Edge Mini v1 and v2, and Edge MicroEnd of support 1 December 2026; end of life 1 June 2027
Customer VM SolutionGenesys Edge software on the customer's virtual machinesNew deployments removed on 20 January 2024; existing deployments stopped working on 10 November 2025
Customer Hardware SolutionGenesys Edge software on customer-supplied hardwareAvailable; Genesys's recommended route where premises media is required

4.2 What end of support means in practice

The deprecation announcement, published on 1 March 2025 with high impact and action required, gives Genesys's reasons: Arrow's stock of preconfigured Edges has run out, and most of these devices are already past hardware end of warranty.

The part people underestimate is what happens after 1 December 2026. Genesys will give only limited support to existing devices, covering configuration and migration assistance, and no new deployments will be allowed. Failing hardware will not be supported or replaced. An organisation that waits is not choosing a delay; it is choosing the day a failed appliance can no longer be replaced. On 20 July 2026 Genesys announced end of life on 1 June 2027, when remaining deployments stop working.

To check whether an organisation is affected, open the Edges list under telephony administration, select each Edge and look at Model in the information panel. If it reads Genesys Hardware Solution, it is affected.

4.3 Where Genesys recommends you go

Genesys recommends moving to cloud media, either BYOC Cloud or Genesys Cloud Voice, using the Hybrid Media Solution built into the platform. The benefits it lists are automatic scaling, built-in resilience, access to its latest AI solutions and lower total cost of ownership. Where premises media is needed for regulatory or connectivity reasons, Genesys recommends the Customer Hardware Solution, which it calls a more practical and economical premises solution.

Our Edge end of life guide covers the migration mechanics and planning, and our case study on moving a financial services estate from Edges to hybrid media shows a real sequence.

4.4 Configuring a premises Edge

Configuration follows a fixed order, the same whichever hardware produced the device: create the external SIP trunk; create a phone trunk (WebRTC or SIP); connect the trunk to an Edge network interface; create sites; associate the Edge with a site and an Edge group and attach the external trunk; add or amend the number plan; add or amend the outbound route; and configure emergency services.

4.5 Edge groups and local site routing

Edge groups have a rule that people get wrong. Genesys states that Edges in one Edge group cannot communicate with Edges in another. For organisations with several locations, manage Edges with sites, not Edge groups, and only create separate groups when you do not want Edges in them to talk to each other.

Edges in a group share resources, including trunks: if one Edge is connected to a long-distance line, the others can use it. A new Edge group cannot work until it has at least one Edge. Each group needs an external SIP trunk to the provider and a SIP or WebRTC phone trunk for the phones: two trunks with two purposes, and confusing them is a classic early configuration error.

Local Site Routing makes Edges site-aware within a group, so calls use Edges at the same site where possible, saving bandwidth and reducing latency. In a multi-site premises estate, per-site trunks plus Local Site Routing are what keep a Manchester call going out on the Manchester line.

05

Hybrid media: combining options

Hybrid media lets one organisation use more than one connection option at once, to take advantage of both cloud and premises features. It is also the route Genesys recommends off its retiring hardware, and the way Genesys Cloud Voice and BYOC Premises users reach Global Media Fabric.

5.1 Two facts before anything else

Organisations created after 11 May 2022 are hybrid media capable automatically. Older organisations become capable by adding a second connection option from AppFoundry. Genesys warns that the conversion takes between 45 minutes and four hours, may affect active calls and should be done off-peak, and that once an organisation is hybrid media capable there is no way to reverse it. Nothing in this part is a reversible experiment.

5.2 The phases in each direction

Two features make hybrid media work: Hybrid Media Edge Groups and Site Links. Site Interconnects let Edges at different sites communicate, and Site Links connect core sites using specified Edge interfaces.

Phases of a hybrid media conversion
DirectionPhases
Premises to hybrid (adding BYOC Cloud or Genesys Cloud Voice)1. Make the organisation hybrid media capable. 2. Move Edges into the Genesys Cloud Hybrid Media Group. 3. Configure Edge interfaces to use Site Interconnects. 4. Enable and configure Site Links.
Cloud to hybrid (adding BYOC Premises)1. Make the organisation hybrid media capable. 2. Pair the new premises Edges with Genesys Cloud. 3. Move Edges into the Hybrid Media Edge Group. 4. Configure Site Interconnects. 5. Enable and configure Site Links.

5.3 What changes, and what does not, after phase one

Phase one surprises people because nothing visible changes: until the later phases are complete, a premises organisation that has become hybrid media capable carries on working as a standard BYOC Premises organisation. In the hybrid model, PureCloud Voice – AWS is the single cloud media core site, and the Hybrid Media Group replaces the separate Edge groups used before.

In a hybrid media organisation you cannot make a premises site the default site; the default must be a cloud site (part 6).

5.4 The cutover capacity warning

Genesys gives a specific threshold for cutover planning: if moving to cloud media will put more than 400 concurrent calls onto cloud media within ten minutes, consider opening a care case to pre-scale resources, because a step that size may drop calls until autoscaling catches up. Autoscaling handles steady growth, not a step change you create deliberately.

06

Sites, number plans and outbound routes

This is the routing model for calls entering and leaving Genesys Cloud, and the vocabulary is the same across all three options. Genesys defines a site as the entity you use to set rules for routing calls: the number plan associates types of numbers with classifications, and the outbound route associates classifications with external trunks.

6.1 How an outbound call finds its trunk

A call is placed from something associated with a site. Genesys identifies the site and classifies the dialled number using the site's number plan, which Genesys calls a master routing table for inbound and outbound routing. The outbound route for that classification chooses the trunk, and the call leaves on it. Outbound routes and classifications across the sites in an Edge group make up the dial plan, based on where a call comes from and where it is going.

The first site setting, the media model, is fixed by your connection option: Cloud for BYOC Cloud and Genesys Cloud Voice, Premises for BYOC Premises.

6.2 Core, branch and default sites

These designations carry more weight than their names suggest, so check each one.

  • A site with an Edge assigned is a core site; a site without one is a branch site.
  • With BYOC Cloud or Genesys Cloud Voice, Genesys creates and maintains the core site, and any site you create is a branch site. With BYOC Premises, designating core and branch sites is your job.
  • One site must be the Default site. Genesys says it generally handles inbound calls, and IVR-initiated transfers where it is unclear which site to use.
  • With the cloud options, the Genesys-managed core site starts as the default, but it is not accessible to anyone outside Genesys and has only the most basic configuration. When you create your first site, make it the default and configure its number plan.
  • In a hybrid media organisation, the default site must be a cloud site.
  • You can change the Default site at any time.

6.3 Inbound calls on the wrong site, and Number Plan Site

Genesys documents a nasty inbound problem. Normally, inbound BYOC Cloud calls are tagged with the site of the trunk that has the outbound route, and that site's number plan is applied to them. A call can therefore be associated with the wrong site, its dialled number normalised by the wrong number plan entry, and then fail to match any assigned DID. When that happens, Genesys Cloud sends a SIP 404 to the carrier and the caller hears an out-of-service message.

The fix is the Number Plan Site setting on the external trunk, which pins which site's number plan is used, both for transforms on inbound calls and for later outbound transfers of calls that never pass through another site. If callers hear a not-recognised message on some numbers but not others, look here first. The same setting stops a multi-country estate normalising a UK number with another country's plan.

07

Trunks, transport and PBX passthrough

A trunk that is built correctly on the Genesys side and incorrectly on the carrier side does nothing, and the console will not always tell you why. This part covers trunk types, the three transport protocols, TLS requirements, and PBX passthrough for organisations keeping a switchboard.

7.1 Trunk types

BYOC Cloud has two main trunk types: BYOC Carrier, to a carrier, and BYOC PBX, to a private branch exchange. Trunks must be set to In-Service, and some subtypes have their own settings; a Verizon trunk requires custom SIP headers, and a WhatsApp Business Calling trunk fills in its allowed addresses for you. Genesys selects the recommended transport protocol for each trunk type by default, and says that in most situations it is the best one.

7.2 UDP, TCP or TLS

BYOC Cloud trunk transport protocols
ProtocolWhen Genesys says to use it
UDPThe standard protocol: fast, low-latency connections using a continuous packet stream without acknowledgements.
TCPWhen you put large amounts of user-to-user information (UUI) or custom data in headers, to avoid failures when packets exceed the UDP maximum transmission unit (MTU).
TLSWhen the connection must be secure, using TLS over TCP.
  • Both ends of the trunk must use the same protocol, or the trunk may not work. This is the commonest reason a new trunk does nothing.
  • The setting only controls the protocol Genesys uses to send calls on the trunk; it is not enforced on calls received. Configure the carrier or PBX to use the protocol you want.
  • The usual firewall ports are 5061 for TLS and 5060 for UDP and TCP.

7.3 TLS and SRTP requirements

For secure trunks, the carrier must support SIP over TLS over TCP and SRTP, protecting both signalling and audio. BYOC Cloud supports TLS 1.2, with listeners on port 5061, and one-way (server-side) TLS; mutual TLS is not supported, and nor is IPsec. Where FIPS compliance is required, Genesys tells you to configure remote endpoints to allow only the cipher suites it marks as NIST-preferred.

That is a security architecture requirement to give the carrier before they quote, not a discovery at cutover.

7.4 PBX passthrough

PBX passthrough makes Genesys Cloud the public network connection for a retained switchboard. Enabled on a BYOC PBX trunk or an external SIP trunk, it lets the PBX pass calls intended for the public network directly through Genesys Cloud, which Genesys says removes the need for a separate public network connection just for PBX calls. Genesys Cloud uses the site's number plan and outbound routes when the destination is not a Genesys Cloud user, station or IVR flow, and sends the call out on a BYOC Carrier, external SIP or Genesys Cloud Voice trunk.

7.5 Passthrough consequences to design for

  • Two call legs, two normalisations and two charge events. Genesys states that each leg is normalised separately and each is subject to the usage fees for its trunk type. Model cost per leg, and when a caller ID looks wrong, check which leg normalised it.
  • Either the inbound or the outbound trunk must be a PBX trunk; passthrough between two carrier trunks is not the pattern.
  • Genesys's warning: do not enable PBX passthrough on external trunks that connect to carriers, because doing so leaves you at risk of toll fraud.

08

Global Media Fabric

Global Media Fabric answers a question multinational organisations ask after go-live: can media stop travelling through the core region? Genesys's answer is that you can configure an organisation to use any Genesys Cloud media region in the world for real-time media to and from clients and carriers, associating any group of users and any trunks with any media region.

8.1 The limits are explicit

  • It applies only to BYOC Cloud trunks. Genesys Cloud Voice and BYOC Premises trunking work differently and cannot use it at present.
  • US-East 2 (Ohio) is designated for FedRAMP and isolated from all other regions.
  • For the European Sovereign Region it is in limited availability; Genesys asks you to contact your account team.
  • Configurations must comply with local telecommunications regulations.
  • Clients can use WebRTC or managed SIP phones, with BYOC Carrier or BYOC PBX trunks.
  • Genesys states the aim as balancing audio latency against call setup time, recommends testing different configurations, and warns that results vary with carrier location, agent location and internet quality.

8.2 Regions and configuration

Genesys lists media regions across the Americas (Oregon, North Virginia, Ohio, Canada Central, São Paulo and Mexico Central), Europe (Frankfurt, Dublin, London, Zurich, Paris and the sovereign region in Brandenburg), the Middle East (UAE), Africa (Cape Town) and Asia Pacific (including Sydney, Tokyo, Seoul, Mumbai, Osaka, Singapore, Hong Kong and Jakarta).

Configuration is two steps from Sites and Trunks in telephony administration: first add media regions to a site, then configure the trunk to use that site.

For the two options it does not serve, Genesys names the route: organisations using Genesys Cloud Voice or BYOC Premises can extend through hybrid media. That makes Global Media Fabric a real argument for hybrid media in a distributed estate, not only a survivability feature.

09

Numbers and porting

Numbers are the part of a telephony programme with external dependencies and no room to negotiate, so they need the earliest dates in the plan. With Genesys Cloud Voice, administrators buy DID and toll-free numbers from Genesys's inventory in Number Management, or port existing numbers in. With BYOC, numbers stay with your carrier and are registered in Genesys Cloud, then assigned to users, groups or phones.

9.1 Porting DIDs into Genesys Cloud Voice

Genesys explains that it can take up to ten days to learn the exact date your carrier will release your numbers, so it recommends submitting a port request two to three weeks in advance. The automated procedure handles up to 500 DID numbers per request; larger volumes use Genesys's batch porting processes. That self-service article covers the US and Canada and points elsewhere for other countries.

9.2 Porting in EMEA and Latin America

In EMEA and Latin America, porting is manual and email-based. You email support to request the Genesys Cloud Voice number porting form and a letter of authorisation for your country, then return them completed. The request creates a support ticket handled during normal business hours, which Genesys gives as Monday to Friday, 8 am to 5 pm US Eastern time. Requests are processed within 24 hours of receipt, but confirming an exact port date can take up to ten days.

For a UK programme, that means porting paperwork moves on US Eastern time. Do not raise a port request on the Friday of a go-live week.

9.3 Toll-free ports move on the industry's clock

Genesys does not submit toll-free port requests to the losing carrier until two weeks before the requested date, which it describes as an industry standard to prevent premature disconnection. You can submit a request up to 30 days ahead, but the port is not confirmed until the losing carrier approves it. Bulk toll-free ports use a downloadable template and a separate procedure.

9.4 The SMS trap

This one catches omnichannel programmes. Genesys states that its number porting process is designed for voice numbers: SMS services on ported numbers are not transferred automatically, and are likely to be disrupted by the port. To move SMS as well, reply to the port confirmation email asking for SMS to be ported; to leave SMS with the old carrier, ask them to reconnect it after the voice port.

Decide this per number before the port. A number carrying a two-factor authentication service or a marketing short code is not just a phone line.

9.5 Interim forwarding

Genesys documents an optional bridge for EMEA and Latin American ports that we treat as standard: after provisioning the new Genesys Cloud Voice numbers, ask your carrier to forward the old numbers to them, and once the port completes, ask the carrier to remove the forwarding. Calls keep flowing during the gap.

9.6 Porting out of Genesys Cloud Voice

If numbers leave Genesys Cloud Voice, the person signing the letter of authorisation must hold the Genesys Cloud Voice Admin role. If the new carrier asks for a billing telephone number, any number on the list will do, and a screenshot of Number Management serves as proof of ownership. Where a carrier needs your organisation ID but will not accept letters, use the last eight digits of the Genesys Cloud organisation ID, excluding letters. After the port, remove the numbers from Number Management: usage charges stop, but Genesys charges a prorated share of the monthly recurring charge for the current billing cycle.

10

Emergency services and outbound restrictions

Read this part even if everything else is familiar. Emergency calling and outbound restrictions both have defaults that are wrong for at least one real organisation, and both fail silently: the first time anyone notices is when a call does not connect.

10.1 Emergency services with BYOC

With BYOC Cloud or BYOC Premises you can call emergency services on your normal numbers, but Genesys is clear that you must set up emergency services with your carrier first, then configure the matching settings in Genesys Cloud. Three documented facts belong in every telephony decision paper.

  1. Genesys is not responsible for emergency services if emergency calls are routed to BYOC trunks. Liability and configuration sit with the customer and the carrier.
  2. Emergency information does not cross between services. If you add BYOC Cloud to an organisation already using Genesys Cloud Voice, the emergency information set up for Genesys Cloud Voice is not provided to the BYOC carrier, and failing to provide it could stop emergency services locating the caller.
  3. Under BYOC Cloud and some BYOC Premises configurations, emergency dialling is internet-based, so it could be limited or unavailable during a power cut or broadband failure. Genesys Cloud Voice requires warning labels on all connected equipment for the same reason.

10.2 Configuring emergency numbers

Emergency numbers are configured in the number plan and outbound routes of each site: select the emergency number plan, enter the emergency number, then choose the trunk and classification. Genesys attaches a precondition that is easy to skip: do not assign an emergency number plan to a BYOC trunk unless you have verified that your carrier provides emergency services and holds the correct location for the numbers in use. Location objects are required to enable services and are used for emergency services in BYOC Cloud; the ANI sent on emergency calls is configurable.

Country rules apply to Genesys Cloud Voice too, as part 2 showed: emergency calling is unsupported on some number types in several countries, and in New Zealand performance may not meet the national service standard.

10.3 Prefix Blocking, and the June 2026 default

Prefix Blocking is available only in Genesys Cloud Voice, not in BYOC Cloud. It gives administrators an Allow List and a Block List: block or allow a whole country by its prefix, part of a country by adding an area code, or a single number. Its purpose is to stop unauthorised outbound calls to high-cost international destinations.

Since 8 June 2026, outbound calling to all countries is blocked by default for new Genesys Cloud Voice customers: every country prefix starts in the Block List, and administrators allow the countries they need. The change does not apply to existing organisations, to avoid disrupting service. The practical consequence is that a new organisation can go live with international outbound silently blocked, and the symptom is a failed call rather than an obvious configuration error. Check the Block List before blaming the carrier.

10.4 High-cost countries and premium numbers

Genesys Cloud Voice also restricts outbound calls to high-cost country destinations automatically, based on its analysis of call traffic patterns, for all customers in all regions. Customers cannot change the list themselves: activating or deactivating the restriction needs a support case, it is not possible to disable a single country code, and Genesys reserves the right to add or remove countries without advance notice. For an organisation with legitimate calling into an affected country, that is a business risk to record, and the support route needs an owner.

Since 12 January 2026, Genesys Cloud Voice also restricts calls to certain premium-rate and shared-cost numbers and to some abbreviated dialling codes, typically three to five digits, used for subscriptions, voting, competitions, directory services and donations. Toll-free numbers and emergency services are not affected.

10.5 With BYOC, fraud controls are yours

Because Prefix Blocking does not exist on BYOC trunks, outbound restrictions there are a matter for your carrier and your contract. That belongs in the comparison: Genesys Cloud Voice ships fraud controls that a self-managed SIP trunk does not. Read it together with the PBX passthrough warning in part 7, which is the other common route to toll fraud.

11

Phones, network readiness and call quality

Telephony is where network quality becomes a failure users can hear, so measure it before arguing about it. This part covers the two families of endpoint, the settings Genesys prescribes for them, and how to test the network they depend on.

11.1 The WebRTC phone

The browser softphone is configured in Phone Management: create base settings with Genesys Cloud WebRTC Phone as the make and model, then create phones from them. Settings fall into four sections: General, Media, Network and Custom. Each phone inherits from its base settings, and Genesys notes you can customise an individual phone without changing the base settings. Get the base settings right once and keep exceptions on individual phones, rather than creating a second base settings object for every team.

One browser behaviour generates support tickets: in Firefox, unless the agent ticks Remember this decision and allows microphone access, Firefox keeps prompting and the agent cannot pick up incoming calls. Put it in agent onboarding.

11.2 Managed SIP phones under BYOC Cloud

For physical desk phones provisioned by Genesys Cloud under BYOC Cloud, Genesys documents exact base settings. Treat them as fixed values rather than suggestions.

Base settings for managed phones under BYOC Cloud
SettingValue
Preferred codec listaudio/opus, then audio/PCMU, in that order
Provision sourceThe Genesys Cloud provisioning service
TCP keep-aliveSend keep-alive every 30 seconds
ProtocolTLS
Listen port8061
Registration period600
  • The matching ports are TCP 8061 (SIPS) for managed phones and TCP 5061 for unmanaged phones, TCP 80 and 443 for provisioning, and UDP 16384 to 65535 for RTP and SRTP media.
  • The wide media range is what firewalls and proxies most often get wrong; open it before testing a phone, not after.
  • Our network and firewall requirements guide covers domains, ranges and ports in full, and our IP ranges tool lists the addresses by region.

11.3 Bandwidth planning

Genesys's customer network readiness article gives the planning figures. The adaptive Opus codec, used by WebRTC phones and some managed phones, needs between 32 and 128 kbps in each direction per concurrent call; phones that do not use Opus need a fixed amount set by their codec. Allow a further 5% of voice bandwidth for SIP signalling, and 150 to 250 kbps per monitor for screen recording. The same article lists questions to ask a SIP provider, including whether it preserves QoS markings, its maximum calls per second and concurrent calls per trunk, and its SIP header requirements.

11.4 Measuring call quality

The Genesys Cloud WebRTC Diagnostics app runs a phone test (streaming connection, WebRTC station, call connected and call quality) and a network test that checks DNS and access to Genesys media servers. It reports four quality measures.

WebRTC diagnostics measures and Genesys's targets
MeasureWhat it isTarget
Mean Opinion Score (MOS)Voice quality from 1 (unacceptable) to 5 (excellent)Higher is better
Packet lossLost packets, which seriously affect call qualityLess than 1%
Average round-trip time (RTT)Latency between your location and your Genesys Cloud regionBelow 300 ms on the standalone app's page; below 150 ms on the built-in app's page
JitterVariation between when packets are sent and receivedLess than 30 ms

11.5 Two official RTT figures

Genesys's two diagnostics pages give different round-trip targets for the same measure. The standalone app's page says round-trip average should be below 300 ms (150 ms one-way); the built-in app's page says below 150 ms. Both are current. Design and accept against the stricter figure and record in the project documents which one you used and why.

MOS is also Genesys's answer to quality-of-service questions for softphones: Genesys Cloud does not natively provide QoS for WebRTC phones, and instead gives MOS values, visible in the Interactions view. A network team may still mark softphone traffic on its own network for its own reasons, but Genesys Cloud does not consume those markings for WebRTC.

12

Monitoring, capacity and continuity

You cannot run what you cannot see, and what telephony administrators can see changed in 2026. This part covers the metrics available, the move to capacity-based monitoring for cloud media, and what continuity options exist today.

12.1 Premises Edge metrics

For premises Edges, Genesys provides telephony metrics per Edge: bandwidth, call counts, CPU, memory, storage and QoS mismatches, the last counted over a 24-hour sliding window. Watch them at known peaks, and before the hardware deadlines in part 4, so that capacity for the replacement is sized from evidence.

12.2 The Edges list is now premises-only

From the release of 19 January 2026 (first released in limited availability on 17 November 2025), the Edges list shows only BYOC Premises Edges; cloud media instances no longer appear, and the change adds visibility of each organisation's concurrent call capacity and calls-per-second limits. A related announcement confirms the page is renamed Premises Edges and that cloud media capacity is summarised through call capacity metrics rather than instance counts.

For a cloud media organisation, you lose instance-level detail and gain capacity metrics. That is a reasonable trade, because Genesys autoscales cloud media and instances are not yours to manage, but it changes what a support conversation looks like. Update runbooks and screenshots so nobody is told to look for something that is no longer there.

12.3 Cloud media and trunk metrics

Under BYOC Cloud or Genesys Cloud Voice, the cloud media monitoring view shows gauges including usage toward the autoscaling threshold and usage of on-demand capacity, plus real-time session and call counts. Record your concurrent call and calls-per-second limits and watch these gauges at peaks; the 400-calls-in-ten-minutes warning in part 5 is a clue to how autoscaling behaves under a sudden step.

Trunk metrics are changing too. A Genesys announcement describes revised BYOC trunk metrics to support the new call session service architecture, adding trunk metrics and removing QoS as a reported metric. Check which metrics your alerting relies on before that change reaches your organisation.

12.4 Continuity for Genesys Cloud Voice

Genesys Cloud Voice organisation linking lets an administrator set a destination organisation in a different region to receive Genesys Cloud Voice traffic during an outage or organisation-wide maintenance, choosing which numbers reroute, and return routing once service is restored. It is currently available only in the US East 1, US West 2 and Canada Central 1 regions. There is no equivalent for UK and European organisations today, so say so plainly in any UK continuity design rather than implying cloud voice has regional failover.

Genesys is careful not to oversell it: the feature supports number continuity but does not replace full disaster recovery. Its own checklist is a good one wherever you are: prepare the destination organisation with flows, queues and roles in advance; replicate configuration manually or programmatically; add DID ranges for failover numbers; make sure agents or automation can handle the calls; and test regularly.

12.5 Site-level continuity

For a specific site that must keep working, the options are BYOC Premises survivability, in a hybrid media organisation, or diverse internet paths. Genesys's network readiness guidance calls for reliable, fully diverse last-mile paths to carrier networks. Ask the facilities lead two questions: what happens to this building's calls if its internet fails, and what happens if the building closes. The answers decide which of these you need. Our European Sovereign Region guide covers the related residency question.

13

How to decide

The framework in this part is ours; every capability inside it rests on the Genesys sources in earlier parts. It is a starting position for a conversation, not a substitute for reading the country pages and the carrier's own terms.

13.1 Three questions, in this order

  1. Is there a carrier contract worth defending? A competitive multi-year contract usually favours BYOC Cloud. An expensive, expiring or unwanted contract favours Genesys Cloud Voice, which removes a vendor and a bill.
  2. Does any site need to make and receive calls when its internet fails? If so, that site needs BYOC Premises with the Customer Hardware Solution, or a retained PBX. No cloud option gives local survivability.
  3. Can the published numbers be obtained in each country? Check the country page first, because a UK non-geographic 03 or 08 number, or a geographic number without a matching address, can rule Genesys Cloud Voice out.

13.2 Where we start

Starting positions by situation (QVCCS framework)
SituationWhere we start
New UK contact centre, no carrier contract worth keepingGenesys Cloud Voice, unless non-geographic numbers or port certainty rule it out
Carrier contract worth keeping, no survivability requirementBYOC Cloud on the Dynamic Cloud Voice Platform
Regulated environment, trunk crossing the public internetBYOC Cloud with TLS and SRTP, TLS 1.2 and the cipher list agreed with the carrier in advance
Switchboard or PBX retainedA BYOC PBX trunk with passthrough onto a carrier trunk; never passthrough on a carrier-facing trunk
A site must survive internet lossBYOC Premises with the Customer Hardware Solution, in a hybrid media organisation
Existing Genesys-supplied Edge appliancesHybrid media, then cloud media, planned now: end of support 1 December 2026, end of life 1 June 2027
Global estate with users and carriers far from the core regionBYOC Cloud with Global Media Fabric, regions chosen by measurement

13.3 Three checks before committing

  • Read the country page for every country with numbers, not the summary.
  • Get the port list verified early, especially in the UK, where Genesys says porting depends on carrier agreements and is not guaranteed.
  • Decide emergency services, Prefix Blocking and the toll fraud position explicitly, and write the decisions down.

14

Ten things that go wrong, and what fixes them

Our own pattern list from building and rescuing Genesys Cloud telephony, with each entry resting on the documented behaviour in the part named beside it.

14.1 Symptoms, causes and fixes

Common Genesys Cloud telephony failures
SymptomLikely causeFix
A new trunk does nothingThe two ends use different transport protocolsConfigure both ends the same; check the carrier's side, not just Genesys's (part 7)
Some numbers get a not-recognised message; the carrier sees SIP 404The wrong site's number plan normalised the dialled numberSet Number Plan Site on the trunk (part 6)
International calls fail on a new organisationSince June 2026, all country prefixes start in the Block ListAllow the countries needed in Prefix Blocking (part 10)
Calls fail when header data is largeUUI or custom headers exceed the UDP MTUMove the trunk to TCP (part 7)
Calls fail after a platform or SBC changeTrunk and remote endpoint are on different platforms or settingsConfigure ingress addresses, egress ranges, certificate authorities and ciphers, then migrate with the toggle (part 3)
A desk phone will not registerWrong port, protocol or codec orderTCP 8061 for managed phones, TLS, Opus then PCMU, keep-alive 30, registration 600 (part 11)
No audio, or one-way audioMedia port range closed, or a proxy inspecting RTPOpen UDP 16384 to 65535 to the right regional ranges and bypass inspection for media (part 11)
Calls drop during a hybrid cutoverMore than 400 concurrent calls moved to cloud media within ten minutesSplit the waves or raise a care case to pre-scale (part 5)
Inbound calls reach the wrong flow, or nothingYour site was never made the Default siteMake your site the default and configure its number plan (part 6)
Doubled records or charges for one PBX callPassthrough creates two legs, each normalised and chargedModel cost per leg and check normalisation on both (part 7)

Questions

Common questions

What is the difference between Genesys Cloud Voice and BYOC Cloud?

With Genesys Cloud Voice, Genesys is your carrier: one contract and one bill, with numbers bought or ported in the console and charges per number and per minute. With BYOC Cloud, your own carrier's SIP trunks terminate over the internet on Genesys Cloud media in AWS, so you keep your carrier contract and minutes. Both process media in the cloud and scale automatically.

Can a UK organisation use non-geographic numbers with Genesys Cloud Voice?

Genesys states that Genesys Cloud Voice does not offer non-geographic numbers in the UK, and 030 numbers can be assigned only to public sector and not-for-profit bodies. Geographic numbers need a matching UK address in the number's area, and UK porting depends on carrier agreements and is not guaranteed. Organisations relying on 03 or 08 numbers often keep them with a carrier on BYOC Cloud.

What happens to Genesys hardware Edges in 2026 and 2027?

The BYOC Premises Genesys Hardware Solution reaches end of support on 1 December 2026: no new deployments, only limited configuration and migration help, and failing hardware will not be replaced. End of life follows on 1 June 2027. Genesys recommends moving to cloud media through hybrid media, or to the Customer Hardware Solution where premises media is required.

Is hybrid media reversible?

No. Genesys warns that once an organisation is hybrid media capable there is no way to reverse it. Organisations created after 11 May 2022 are already capable; older ones convert by adding a second connection option from AppFoundry, which takes 45 minutes to four hours, may affect active calls and should be done off-peak.

Why are outbound international calls failing on a new Genesys Cloud Voice organisation?

Since 8 June 2026, new Genesys Cloud Voice customers start with every country prefix in the Prefix Blocking Block List, so international calls are blocked until an administrator allows the countries needed. Existing organisations were not changed. Genesys also blocks some high-cost countries and premium-rate numbers automatically, and those lists cannot be edited by customers.

What latency should a Genesys Cloud voice network meet?

Genesys's diagnostics pages give two round-trip targets for the same measure: below 300 ms (150 ms one-way) on the standalone app's page and below 150 ms on the built-in app's page. Both call for packet loss under 1% and jitter under 30 ms. Designing to 150 ms round-trip satisfies both pages.

Sources

  1. Deprecation: BYOC Premises - Customer VM Solution – Genesys Cloud Resource Centerhelp.genesys.cloud
  2. Deprecation: BYOC-Premises - Genesys Hardware Solution – Genesys Cloud Resource Centerhelp.genesys.cloud
  3. Disaster recovery routing for Genesys Cloud Voice traffic – Genesys Cloud Resource Centerhelp.genesys.cloud
  4. Dynamic Cloud Voice Platform as the default for new BYOC Cloud trunks – Genesys Cloud Resource Centerhelp.genesys.cloud
  5. Revised BYOC trunk metrics to support call session service – Genesys Cloud Resource Centerhelp.genesys.cloud
  6. Telephony Admin UI: Cloud media visibility update – Genesys Cloud Resource Centerhelp.genesys.cloud
  7. About BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  8. About BYOC Premises – Genesys Hardware Solution – Genesys Cloud Resource Centerhelp.genesys.cloud
  9. About BYOC Premises – Genesys Cloud Resource Centerhelp.genesys.cloud
  10. About Genesys Cloud Voice – Genesys Cloud Resource Centerhelp.genesys.cloud
  11. About hybrid media – Genesys Cloud Resource Centerhelp.genesys.cloud
  12. About telephony – Genesys Cloud Resource Centerhelp.genesys.cloud
  13. Addresses for premises-based carrier devices/services under BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  14. BYOC Cloud configuration checklist – Genesys Cloud Resource Centerhelp.genesys.cloud
  15. BYOC Cloud quick start guide – Genesys Cloud Resource Centerhelp.genesys.cloud
  16. BYOC Cloud overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  17. BYOC Premises trunk connection overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  18. Carrier requirements for BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  19. Choose a trunk transport protocol – Genesys Cloud Resource Centerhelp.genesys.cloud
  20. Cloud to hybrid media overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  21. Configure 911 or other emergency numbers – Genesys Cloud Resource Centerhelp.genesys.cloud
  22. Configure a trunk for Microsoft Teams integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  23. Configure base settings for phones under BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  24. Configure PBX passthrough for a BYOC or External SIP trunk – Genesys Cloud Resource Centerhelp.genesys.cloud
  25. Configure the Genesys Cloud WebRTC phone – Genesys Cloud Resource Centerhelp.genesys.cloud
  26. Create a trunk under BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  27. Customer network readiness – Genesys Cloud Resource Centerhelp.genesys.cloud
  28. Dynamic Cloud Voice platform overview and migration guide – Genesys Cloud Resource Centerhelp.genesys.cloud
  29. BYOC Premises Edge group configuration overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  30. External trunk settings – Genesys Cloud Resource Centerhelp.genesys.cloud
  31. Genesys Cloud Voice AWS region-specific availability and restrictions – Genesys Cloud Resource Centerhelp.genesys.cloud
  32. Genesys Cloud Voice global coverage requirements and restrictions – Genesys Cloud Resource Centerhelp.genesys.cloud
  33. Genesys Cloud Voice high-cost country outbound call blocking – Genesys Cloud Resource Centerhelp.genesys.cloud
  34. Genesys Cloud Voice organization linking overview  – Genesys Cloud Resource Centerhelp.genesys.cloud
  35. Genesys Cloud Voice activation requirements and service restrictions for United Kingdom – Genesys Cloud Resource Centerhelp.genesys.cloud
  36. Genesys Cloud Voice overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  37. Global Media Fabric overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  38. High-cost premium-rate numbers – Genesys Cloud Resource Centerhelp.genesys.cloud
  39. Hybrid media overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  40. Improve inbound call handling with the Number Plan Site feature – Genesys Cloud Resource Centerhelp.genesys.cloud
  41. Monitor cloud media resources – Genesys Cloud Resource Centerhelp.genesys.cloud
  42. Port numbers in EMEA and LATAM – Genesys Cloud Resource Centerhelp.genesys.cloud
  43. Port DID numbers – Genesys Cloud Resource Centerhelp.genesys.cloud
  44. Port numbers out of Genesys Cloud Voice – Genesys Cloud Resource Centerhelp.genesys.cloud
  45. Port toll-free numbers – Genesys Cloud Resource Centerhelp.genesys.cloud
  46. Ports and services for VoIP phones under BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  47. Premises to hybrid media overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  48. Run the built-in Genesys Cloud WebRTC Diagnostics app – Genesys Cloud Resource Centerhelp.genesys.cloud
  49. Run the standalone Genesys Cloud WebRTC Diagnostics app – Genesys Cloud Resource Centerhelp.genesys.cloud
  50. Select a phone – Genesys Cloud Resource Centerhelp.genesys.cloud
  51. Set up a Customer Hardware Solution Edge – Genesys Cloud Resource Centerhelp.genesys.cloud
  52. Set up emergency services with BYOC – Genesys Cloud Resource Centerhelp.genesys.cloud
  53. Sites overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  54. Telephony connection options overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  55. TLS trunk transport protocol specification for BYOC Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
  56. Use the Genesys Cloud Voice Prefix Blocking feature to block and allow outbound dialing prefixes – Genesys Cloud Resource Centerhelp.genesys.cloud
  57. View telephony metrics – Genesys Cloud Resource Centerhelp.genesys.cloud
  58. Can I use BYOC Cloud with Genesys Cloud Voice? – Genesys Cloud Resource Centerhelp.genesys.cloud
  59. Does Genesys Cloud support QoS for WebRTC phones? – Genesys Cloud Resource Centerhelp.genesys.cloud
  60. What are the limitations to BYOC Cloud trunks  – Genesys Cloud Resource Centerhelp.genesys.cloud
  61. What is BYOC? – Genesys Cloud Resource Centerhelp.genesys.cloud
  62. Why are my inbound BYOC Cloud calls being associated with the wrong site? – Genesys Cloud Resource Centerhelp.genesys.cloud
  63. Bring Your Own Carrier (BYOC) – Genesys Cloud Resource Centerhelp.genesys.cloud
  64. Edge – Genesys Cloud Resource Centerhelp.genesys.cloud
  65. number plan – Genesys Cloud Resource Centerhelp.genesys.cloud
  66. outbound route – Genesys Cloud Resource Centerhelp.genesys.cloud
  67. January 12, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  68. January 19, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  69. June 8, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  70. November 17, 2025 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  71. Genesys Voice Services – Genesys Cloud Resource Centerhelp.genesys.cloud
  72. Make your organization hybrid media capable – Genesys Cloud Resource Centerhelp.genesys.cloud
  73. Genesys Cloud Voice activation requirements and service restrictions for Singapore – Genesys Cloud Resource Centerhelp.genesys.cloud
  74. Genesys Cloud Voice activation requirements and service restrictions for Japan – Genesys Cloud Resource Centerhelp.genesys.cloud
  75. Genesys Cloud Voice activation requirements and service restrictions for New Zealand – Genesys Cloud Resource Centerhelp.genesys.cloud
  76. Genesys Cloud Voice activation requirements and service restrictions for Latvia – Genesys Cloud Resource Centerhelp.genesys.cloud

Last reviewed

We work by introduction

Clients, partners and people introduced to us can reach the right specialist directly.

Who to contact