# Genesys Cloud CX telephony and BYOC Canonical: https://warmtransfer.net/knowledge/genesys-cloud-telephony Last verified: 2026-09-24 Genesys Cloud offers 3 telephony connection options: Genesys Cloud Voice, BYOC Cloud, and BYOC Premises[^50]. These options govern where media is processed, how trunks connect to public networks, and which platform features can run on voice interactions[^28][^43]. ## Connection models Genesys Cloud Voice is a VoIP telephony service provided directly by Genesys that an organization activates to secure public telephony and assign numbers to users, IVRs, phones, or campaigns[^26]. It processes media in the cloud, requires no customer carrier contract, and eliminates premises equipment[^28]. Emergency services are included with every purchased number, with addresses validated by Genesys Cloud, though callers should know their location because some emergency call centers cannot receive address data[^27]. The Genesys Local Number Porting team completes most port requests in 5 business days, activating service on the confirmed FOC date[^29]. Genesys Cloud Voice billing comprises 1-time charges (purchases, setup, port requests), monthly recurring charges for DID and toll-free numbers, and usage charges for inbound and outbound calls[^23]. BYOC Cloud establishes SIP trunks between third-party carriers and the Genesys Cloud AWS-based Edge and Media Tier over the public internet[^2]. It requires a customer-managed carrier contract, processes media in the cloud, and requires a customer SBC only when connecting premises equipment[^1]. Fair use under BYOC Cloud is measured in minutes starting when a call is answered by a person or an automated system until disconnect[^20]. Both Genesys Cloud Voice and BYOC Cloud scale automatically and provide redundancy across 3 or more availability zones[^12]. BYOC Premises terminates third-party carrier SIP trunks to an on-premises Edge device and processes media locally on premises[^5]. Trunks on a BYOC Premises Edge can terminate either to on-premises equipment such as an SBC or SIP gateway, or to a cloud-based carrier device[^6]. | Connection option | Media processing | Carrier contract | Premises hardware | | --- | --- | --- | --- | | Genesys Cloud Voice | Cloud[^28] | None required[^28] | None required[^28] | | BYOC Cloud | Cloud[^1] | Third-party customer-managed[^1] | SBC only if connecting premises gear[^1] | | BYOC Premises | On premises[^5] | Third-party carrier[^5] | On-premises Edge device[^5] | ## BYOC Cloud network and transport requirements Carriers or devices terminating a BYOC Cloud trunk must possess a publicly reachable IP address or host name with the required ports open[^4]. Because RTP media traverses the internet between regional Genesys Cloud AWS resources and the trunk termination, Genesys advises testing internet quality and latency prior to rollout[^3]. Carrier endpoints must comply with SIP standards including RFC 3261 sections 8.2.6.2, 19.1.1, and 19.1.5, and must provide full support for Record-Route[^8]. Carriers must allowlist Genesys Cloud public SIP IP addresses for their region in carrier-side ACLs and send inbound traffic to the trunk FQDN or public SIP load balancer DNS names[^7]. Published BYOC Cloud SIP addresses do not reply to ICMP ping, and signaling and media run over distinct addresses and services[^47]. BYOC Cloud supports UDP, TCP, and TLS over TCP[^56]. SIP signaling listens on port 5060 for UDP and TCP, and port 5061 for TLS[^57]. Both ends of the trunk must configure identical transport protocols or the trunk may fail[^55]. The transport protocol setting controls only how Genesys Cloud transmits calls; it is not enforced on inbound calls received on the trunk[^58]. Genesys recommends TCP over UDP when SIP headers include large amounts of UUI or custom data, because UDP packets that exceed the MTU can cause call failures[^59]. Secure trunks require SIP over TLS over TCP paired with SRTP for media[^53]. IPsec is not supported for BYOC Cloud trunks[^41]. BYOC Cloud TLS relies on 1-way server-side TLS and does not support mutual TLS (mTLS)[^42]. Endpoints must run TLS version 1.2 on port 5061[^54]. Trunk certificates must be issued by a public CA on the Genesys published list and match the subject name of the URI contacted[^51]. On 2025-03-24, Genesys announced that a future release will drop the TLS ciphers TLS_RSA_WITH_AES_256_CBC_SHA256 and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384[^11]. ## Dynamic Cloud Voice vs Legacy Cloud Voice Genesys directs new customers and new BYOC Cloud trunks to use the Dynamic Cloud Voice platform[^13]. On the Legacy Cloud Voice platform, each region assigns 4 public SIP signaling IP addresses (lb01 through lb04 under `voice..pure.cloud`), all of which require carrier allowlisting[^46]. Legacy endpoints present DigiCert TLS certificates and support only the secp384r1 (P-384) elliptic curve[^52][^16]. The Dynamic Cloud Voice platform separates public SIP IP addresses between ingress (traffic sent to Genesys Cloud) and egress (traffic originating from Genesys Cloud)[^15]. Inbound request URIs on Dynamic Cloud Voice adopt the `genesys.cloud` DNS suffix with a single `byoc` subdomain, removing the legacy separate `voice` and `byoc` subdomains[^14]. Dynamic Cloud Voice presents certificates chained to Amazon Trust Services roots (Amazon Root CA 1 and 2) and supports both secp256r1 (P-256) and secp384r1 (P-384) elliptic curves[^52][^16]. ## BYOC Premises hardware, lifecycle, and survivability In BYOC Premises – Customer Hardware Solution deployments, customers procure Genesys-recommended HPE hardware from a vendor of their choice in Large or Small configurations[^9]. Putting a customer hardware Edge into service initiates a monthly hardware usage charge under the organization's Genesys Cloud contract[^10]. Edges should follow an N+1 redundancy design, where N represents the Edge count required for peak concurrent calls[^18]. Redundant sites must use hardware of comparable capacity: Customer Hardware Large pairs with Genesys Hardware Standard, Customer Hardware Small pairs with Genesys Hardware Mini, and Edge Micro mixes only with Edge Micro[^17]. Phones register to a randomized primary and secondary Edge, failing over to the secondary almost immediately if the primary fails, though the UI can lag up to 15 seconds during Edge-to-cloud heartbeat restoration[^19]. Multiple premises Edge models and capabilities have reached end-of-life or deprecation milestones: - BYOC Premises – Customer VM Solution reached end of support on 2024-01-20 and end of life on 2025-11-10 because of its reliance on Windows Server 2012 R2[^60]. - Edge Remote Survivability (offline ACD routing and cached IVR execution during WAN outages) was deprecated on 2025-06-30, though BYOC Premises itself remains supported[^49]. - BYOC Premises – Genesys Hardware Solution enters end of support on 2026-12-01[^31]. This applies to Edge Standard v1, v2, and v3, Edge Micro, and Edge Mini v1 and v2[^30]. Genesys scheduled this deprecation because pre-configured hardware inventory at Arrow has depleted and most units have passed hardware warranty[^34]. Following EOS, Genesys limits support to configuration and migration assistance, blocks new deployments, and will not replace failed hardware[^33]. Migration paths include Genesys Cloud Voice, BYOC Cloud, or the Customer Hardware Solution for deployments constrained by local connectivity or regulatory mandates[^32]. ## Hybrid media and feature limitations A premise-only BYOC Premises architecture lacks cloud media streaming capabilities, making Virtual Agent, Agentic Virtual Agent, Agent Copilot, Agent Assist Voice, Agent Feedback, AudioHook, Audio Connector, and real-time sentiment analysis unavailable[^43]. In addition, transcription runs post-call with potential delays reaching several hours[^44]. WarmTransfer's reading of the sources is that adopting AudioHook, Agent Copilot, or real-time transcription in a BYOC Premises environment requires adding a cloud telephony option via hybrid media and routing voice interactions through cloud media[^40]. Hybrid media allows an organization to mix BYOC Premises, BYOC Cloud, and Genesys Cloud Voice within a single tenant[^36]. Organizations created after 2022-05-11 are hybrid-media capable automatically, whereas older organizations require conversion[^35]. Converting a BYOC Cloud organization uses the same process as converting a Genesys Cloud Voice organization[^38]. The conversion procedure must follow this order: create a location, create a premises core site, pair the BYOC Premises Edges, add the Edges to the hybrid media group 1 at a time, configure site interconnects, put Edges in service, enable site links to the cloud site, configure trunks, routes, and number plans, and transfer phones[^37][^39]. ## See also - See also [Genesys Cloud CX routing and Architect flows](https://warmtransfer.net/knowledge/genesys-cloud-routing). - See also [UCaaS and CCaaS procurement and RFP evaluation](https://warmtransfer.net/knowledge/ucaas-ccaas-procurement). ## Applicability Applies to: Genesys Cloud CX, Genesys Cloud Voice, Genesys Cloud CX BYOC Cloud, Genesys Cloud CX BYOC Premises, Genesys Cloud CX BYOC Premises – Genesys Hardware Solution, Genesys Cloud CX BYOC Premises – Customer VM Solution, and Genesys Cloud CX BYOC Premises – Customer Hardware Solution. Deployments: hybrid, multi-tenant, and on-premises-edge. Sources checked 2026-09-24. Organizations created after 2022-05-11 are hybrid-media capable automatically, while older tenants require manual conversion[^35]. BYOC Premises Edge Remote Survivability was deprecated effective 2025-06-30[^49]. The BYOC Premises Customer VM Solution reached end of support on 2024-01-20 and end of life on 2025-11-10[^60]. End of support for the Genesys Hardware Solution takes effect 2026-12-01[^31]. Deprecation of the BYOC Cloud TLS ciphers TLS_RSA_WITH_AES_256_CBC_SHA256 and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 was announced on 2025-03-24 without a stated removal release[^11]. ## What remains uncertain The specific Genesys Cloud release that will remove the deprecated TLS ciphers TLS_RSA_WITH_AES_256_CBC_SHA256 and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 is not covered by the sources below. ## Sources [^1]: BYOC Cloud requires a customer-managed contract with a third-party carrier, processes media in the cloud, and may need a customer SBC only where premises equipment is connected. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), comparison table, BYOC Cloud column. Checked 2026-09-24. [^2]: BYOC Cloud defines SIP trunks between the Genesys Cloud AWS-based Edge and Media Tier and third-party carriers over the public internet. Source: [About BYOC Cloud](https://help.genesys.cloud/articles/about-byoc-cloud/), opening paragraph. Checked 2026-09-24. [^3]: Genesys advises evaluating internet infrastructure quality and latency before implementing BYOC Cloud, because RTP media crosses the internet between regional Genesys Cloud AWS resources and the trunk termination. Source: [BYOC Cloud overview](https://help.genesys.cloud/articles/byoc-cloud-overview/), important considerations section. Checked 2026-09-24. [^4]: A carrier or device terminating a BYOC Cloud trunk must have a publicly reachable IP address or host name with the required ports open. Source: [BYOC Cloud overview](https://help.genesys.cloud/articles/byoc-cloud-overview/), overview section, requirements for external carriers or devices. Checked 2026-09-24. [^5]: BYOC Premises uses a premises-based Edge device to connect third-party carrier SIP trunks to Genesys Cloud and processes media on premises. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), comparison table, BYOC Premises column. Checked 2026-09-24. [^6]: A BYOC Premises SIP trunk can connect the on-premises Edge either to an on-premises carrier device such as an SBC or SIP gateway, or to a carrier device in the cloud. Source: [BYOC Premises trunk connection overview](https://help.genesys.cloud/articles/byoc-premises-solutions/), premises-based carrier device and cloud-based carrier device sections. Checked 2026-09-24. [^7]: The carrier must add the Genesys Cloud public SIP IP addresses for the region to its carrier-side ACL allowlist, and send inbound calls to the public SIP load balancer DNS names or the trunk FQDN. Source: [Carrier requirements for BYOC Cloud](https://help.genesys.cloud/articles/carrier-requirements-byoc-cloud/), network infrastructure and inbound call routing bullets. Checked 2026-09-24. [^8]: A BYOC Cloud carrier must be SIP-compliant including RFC 3261 sections 8.2.6.2, 19.1.1 and 19.1.5, and must fully support Record-Route. Source: [Carrier requirements for BYOC Cloud](https://help.genesys.cloud/articles/carrier-requirements-byoc-cloud/), general requirements, SIP compliance bullets. Checked 2026-09-24. [^9]: With BYOC Premises – Customer Hardware Solution the customer builds the Edge from Genesys-recommended HPE hardware bought from a vendor of their choice, in Large or Small configurations. Source: [About BYOC Premises - Customer Hardware Solution](https://help.genesys.cloud/articles/about-byoc-premises-customer-hardware-solution/), opening section and configuration options. Checked 2026-09-24. [^10]: Putting a BYOC Premises Edge in service starts the monthly hardware usage charge specified in the Genesys Cloud contract. Source: [About BYOC Premises - Customer Hardware Solution](https://help.genesys.cloud/articles/about-byoc-premises-customer-hardware-solution/), associated costs note. Checked 2026-09-24. [^11]: On 2025-03-24 Genesys announced that a future release would drop the BYOC Cloud TLS ciphers TLS_RSA_WITH_AES_256_CBC_SHA256 and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384. Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), cipher deprecation notice. Checked 2026-09-24. [^12]: Genesys Cloud Voice and BYOC Cloud both scale automatically and are made redundant across three or more availability zones. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), comparison table, scaling and redundancy rows. Checked 2026-09-24. [^13]: Genesys says new customers and customers creating new BYOC Cloud SIP trunks should use the Dynamic Cloud Voice platform. Source: [Dynamic Cloud Voice platform overview and migration guide](https://help.genesys.cloud/articles/dynamic-cloud-voice-platform-overview/), who should use the platform section. Checked 2026-09-24. [^14]: Dynamic Cloud Voice inbound request URIs use the genesys.cloud DNS suffix with a single byoc subdomain, replacing the separate voice and byoc subdomains of the legacy platform. Source: [Dynamic Cloud Voice platform overview and migration guide](https://help.genesys.cloud/articles/dynamic-cloud-voice-platform-overview/), domain naming section. Checked 2026-09-24. [^15]: The Dynamic Cloud Voice platform uses distinct public SIP IP addresses for ingress (requests to Genesys Cloud) and egress (requests from Genesys Cloud). Source: [Dynamic Cloud Voice platform overview and migration guide](https://help.genesys.cloud/articles/dynamic-cloud-voice-platform-overview/), IP address section. Checked 2026-09-24. [^16]: The Dynamic Cloud Voice platform supports the secp256r1 (P-256) elliptic curve in addition to secp384r1 (P-384), which was the only curve on the legacy platform. Source: [Dynamic Cloud Voice platform overview and migration guide](https://help.genesys.cloud/articles/dynamic-cloud-voice-platform-overview/), elliptical curves section. Checked 2026-09-24. [^17]: Edges in one redundant site must have similar capacity: Customer Hardware Large mixes with Genesys Hardware Standard, Customer Hardware Small with Genesys Hardware Mini, and Edge Micro only with other Edge Micros. Source: [BYOC Premises Edge redundancy](https://help.genesys.cloud/articles/edge-redundancy/), compatibility constraints section. Checked 2026-09-24. [^18]: Genesys recommends deploying BYOC Premises Edges as N+1, where N is the number of Edges needed for the expected peak concurrent call load. Source: [BYOC Premises Edge redundancy](https://help.genesys.cloud/articles/edge-redundancy/), redundancy configuration section. Checked 2026-09-24. [^19]: Phones on a BYOC Premises site register to a randomized primary and secondary Edge; if the primary fails the phone switches to the secondary almost immediately, though the UI may lag up to about 15 seconds while Edge-to-cloud heartbeats resume. Source: [BYOC Premises Edge redundancy](https://help.genesys.cloud/articles/edge-redundancy/), phone registration and failure response sections. Checked 2026-09-24. [^20]: BYOC Cloud usage for fair use is measured in minutes from when the call is answered (by a person or an automated system) until it disconnects. Source: [Genesys Cloud fair use policy](https://help.genesys.cloud/articles/genesys-cloud-fair-use-policy/), BYOC Cloud fair use policy overview. Checked 2026-09-24. [^21]: The BYOC Cloud fair use allowance is 5,000 minutes per month for each named Genesys Cloud CX 1 to 4 user, and allowances pool across the organization's users each month with no rollover. Source: [Genesys Cloud fair use policy](https://help.genesys.cloud/articles/genesys-cloud-fair-use-policy/), Fair use policy by license type table (named users); BYOC Cloud fair use allocation section. Checked 2026-09-24. [^22]: BYOC Cloud minutes beyond the fair use allocation are listed at USD 0.00120 per minute per call, billed in six-second increments rounded up. Source: [Genesys Cloud fair use policy](https://help.genesys.cloud/articles/genesys-cloud-fair-use-policy/), Overage charges section. Checked 2026-09-24. [^23]: Genesys Cloud Voice is billed as one-time charges (purchases, setup, port requests), monthly recurring charges for DID and toll-free numbers, and usage charges for inbound and outbound calls. Source: [Genesys Cloud Voice overview](https://help.genesys.cloud/articles/genesys-cloud-voice-service/), billing section. Checked 2026-09-24. [^24]: The Genesys Cloud Voice global coverage page lists availability in APAC (for example Australia, Japan, Singapore) and Latin America (for example Brazil, Mexico, Colombia) as well as the United States, Canada and EMEA (disputed). Source: [Genesys Cloud Voice global coverage requirements and restrictions](https://help.genesys.cloud/articles/genesys-cloud-voice-global-coverage-2/), APAC and Latin America headings. Checked 2026-09-24. [^25]: The Genesys Cloud Voice overview describes service availability as the United States, Canada and EMEA regions (disputed). Source: [Genesys Cloud Voice overview](https://help.genesys.cloud/articles/genesys-cloud-voice-service/), geographic coverage / DID numbers section. Checked 2026-09-24. [^26]: Genesys Cloud Voice is a VoIP telephony service, provided by Genesys, that an organization activates to get public telephony and assign phone numbers to users, IVR, phones or campaigns. Source: [Genesys Cloud Voice overview](https://help.genesys.cloud/articles/genesys-cloud-voice-service/), opening section. Checked 2026-09-24. [^27]: Genesys Cloud includes emergency services with every Genesys Cloud Voice number purchase and validates addresses, but some emergency call centers cannot receive address data, so callers should know their location. Source: [Genesys Cloud Voice overview](https://help.genesys.cloud/articles/genesys-cloud-voice-service/), emergency calling section. Checked 2026-09-24. [^28]: With Genesys Cloud Voice no customer carrier contract and no premises equipment are required, and media is processed in the cloud. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), comparison table, Genesys Cloud Voice column (equipment, media processing, carrier contract rows). Checked 2026-09-24. [^29]: For Genesys Cloud Voice, the Genesys Local Number Porting team completes most ports in five business days, and service activates on the confirmed FOC date. Source: [Genesys Cloud Voice overview](https://help.genesys.cloud/articles/genesys-cloud-voice-service/), porting section. Checked 2026-09-24. [^30]: The Genesys Hardware Solution EOS covers Edge Standard v1, v2 and v3, Edge Micro, and Edge Mini v1 and v2. Source: [Deprecation: BYOC-Premises – Genesys Hardware Solution](https://help.genesys.cloud/announcements/deprecation-byoc-premises-genesys-hardware-solution/), affected Edge devices list. Checked 2026-09-24. [^31]: On 2025-03-01 Genesys announced end of support for BYOC Premises – Genesys Hardware Solution effective 2026-12-01. Source: [Deprecation: BYOC-Premises – Genesys Hardware Solution](https://help.genesys.cloud/announcements/deprecation-byoc-premises-genesys-hardware-solution/), announcement header and summary. Checked 2026-09-24. [^32]: Genesys names three migration paths off the Genesys Hardware Solution: Genesys Cloud Voice, BYOC Cloud, or BYOC Premises – Customer Hardware Solution for organizations whose regulatory or connectivity needs require premises media. Source: [Deprecation: BYOC-Premises – Genesys Hardware Solution](https://help.genesys.cloud/announcements/deprecation-byoc-premises-genesys-hardware-solution/), recommended migration paths section. Checked 2026-09-24. [^33]: After the Genesys Hardware Solution EOS, Genesys gives only limited support (configuration and migration help) to existing Edges, allows no new deployments, and will not support or replace failing hardware. Source: [Deprecation: BYOC-Premises – Genesys Hardware Solution](https://help.genesys.cloud/announcements/deprecation-byoc-premises-genesys-hardware-solution/), support after EOS section. Checked 2026-09-24. [^34]: Genesys gives two reasons for the Genesys Hardware Solution EOS: Arrow's stock of pre-configured Edges has run out, and most of these Edges have reached hardware end of warranty. Source: [Deprecation: BYOC-Premises – Genesys Hardware Solution](https://help.genesys.cloud/announcements/deprecation-byoc-premises-genesys-hardware-solution/), reason section; Arrow inventory note dated 2023-08-30. Checked 2026-09-24. [^35]: Genesys Cloud organizations created after 2022-05-11 are hybrid-media capable automatically; older organizations must be converted. Source: [About hybrid media](https://help.genesys.cloud/articles/about-hybrid-media/), requirements section. Checked 2026-09-24. [^36]: Hybrid media lets an organization combine any or all of the three telephony connection options (BYOC Premises, BYOC Cloud, Genesys Cloud Voice) in one organization. Source: [About hybrid media](https://help.genesys.cloud/articles/about-hybrid-media/), opening section. Checked 2026-09-24. [^37]: The conversion to hybrid media runs in order: create a location, create a premises core site, pair the BYOC Premises Edges, add them to the hybrid media group, configure site interconnects, put the Edges in service, enable site links to the cloud site, then build trunks, routes and number plans and finally move phones. Source: [Convert BYOC Cloud/Genesys Cloud Voice to hybrid media](https://help.genesys.cloud/articles/convert-byoc-cloud-genesys-cloud-voice-to-hybrid-media/), numbered procedure steps 1 to 9. Checked 2026-09-24. [^38]: Converting a BYOC Cloud organization and converting a Genesys Cloud Voice organization to hybrid media follow the same process. Source: [Convert BYOC Cloud/Genesys Cloud Voice to hybrid media](https://help.genesys.cloud/articles/convert-byoc-cloud-genesys-cloud-voice-to-hybrid-media/), page introduction. Checked 2026-09-24. [^39]: When building a hybrid media group, premises Edges can only be added to the group one at a time. Source: [Convert BYOC Cloud/Genesys Cloud Voice to hybrid media](https://help.genesys.cloud/articles/convert-byoc-cloud-genesys-cloud-voice-to-hybrid-media/), step: add Edges to the hybrid media group. Checked 2026-09-24. [^40]: A BYOC Premises organization that wants AudioHook, Agent Copilot or real-time transcription must add a cloud telephony option through hybrid media and route those calls through cloud media (inferred). Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), BYOC Premises feature gaps and hybrid media rows. Checked 2026-09-24. [^41]: BYOC Cloud does not support IPsec for secure trunks. Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), Requirements section. Checked 2026-09-24. [^42]: BYOC Cloud TLS connections use one-way (server-side) TLS; mutual TLS is not supported. Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), certificate requirements section. Checked 2026-09-24. [^43]: In a premise-only BYOC Premises deployment Virtual Agent, Agentic Virtual Agent, Agent Copilot, Agent Assist Voice, Agent Feedback, AudioHook, Audio Connector and real-time sentiment analysis are unavailable. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), BYOC Premises column, features not available in a premise-only solution. Checked 2026-09-24. [^44]: In a premise-only deployment transcription happens after the call, with a potential delay of several hours. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), BYOC Premises column, transcription row. Checked 2026-09-24. [^45]: On the Dynamic Cloud Voice platform each region has three ingress SIP addresses (lb01 to lb03 under byoc..genesys.cloud) and one egress /30 CIDR range. Source: [BYOC Cloud public SIP IP addresses](https://help.genesys.cloud/articles/byoc-cloud-public-sip-ip-addresses/), Dynamic Cloud Voice platform table (example row US East use1). Checked 2026-09-24. [^46]: On the Legacy Cloud Voice platform each Genesys Cloud region has four public SIP signaling addresses, named lb01 to lb04 under voice..pure.cloud, and all four must be allowlisted. Source: [BYOC Cloud public SIP IP addresses](https://help.genesys.cloud/articles/byoc-cloud-public-sip-ip-addresses/), Legacy Cloud Voice platform table and allowlisting note. Checked 2026-09-24. [^47]: The published BYOC Cloud public SIP addresses do not respond to ICMP ping, and call signaling and media are handled by separate services on different addresses. Source: [BYOC Cloud public SIP IP addresses](https://help.genesys.cloud/articles/byoc-cloud-public-sip-ip-addresses/), important notes section. Checked 2026-09-24. [^48]: The BYOC Cloud public SIP address list covers regions including US East (use1, use2), US West (usw2), Canada Central, Mexico Central, Sao Paulo, Ireland, London, Frankfurt, Zurich, UAE, Mumbai, Singapore, Sydney, Tokyo, Seoul and Osaka. Source: [BYOC Cloud public SIP IP addresses](https://help.genesys.cloud/articles/byoc-cloud-public-sip-ip-addresses/), regional table headings. Checked 2026-09-24. [^49]: BYOC Premises Edge Remote Survivability (cached IVR flows and ACD routing during internet loss) was deprecated effective 2025-06-30, while the BYOC Premises connection option itself remains supported. Source: [Deprecation: BYOC Premises Edge Remote Survivability](https://help.genesys.cloud/announcements/deprecation-byoc-premises-edge-remote-survivability/), announcement summary and important note. Checked 2026-09-24. [^50]: Genesys Cloud offers three telephony connection options: Genesys Cloud Voice, BYOC Cloud and BYOC Premises. Source: [Telephony connection options overview](https://help.genesys.cloud/articles/telephony-connection-options/), page introduction and comparison table columns. Checked 2026-09-24. [^51]: Certificates on a BYOC Cloud TLS trunk endpoint must be signed by a public certificate authority from the list Genesys publishes, and must contain the subject name of the URI the client connected to. Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), certificate requirements section, public certificate authority list. Checked 2026-09-24. [^52]: Genesys Cloud BYOC endpoints on the Legacy Cloud Voice platform present DigiCert certificates, while the Dynamic Cloud Voice platform uses Amazon Trust Services roots (Amazon Root CA 1 and 2). Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), root certificate authority tables for Legacy and Dynamic Cloud Voice. Checked 2026-09-24. [^53]: For secure BYOC Cloud trunks, carriers must support SIP over TLS over TCP together with SRTP for media. Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), Requirements section. Checked 2026-09-24. [^54]: BYOC Cloud supports TLS endpoints using TLS version 1.2, with TLS listeners on port 5061. Source: [TLS trunk transport protocol specification for BYOC Cloud](https://help.genesys.cloud/articles/tls-trunk-transport-protocol-specification/), TLS version and port section. Checked 2026-09-24. [^55]: Both ends of a BYOC Cloud trunk must be configured with the same transport protocol, or the trunk may not work. Source: [Choose a trunk transport protocol](https://help.genesys.cloud/articles/choose-a-trunk-transport-protocol/), configuration requirement note. Checked 2026-09-24. [^56]: BYOC Cloud trunks support three transport protocols: UDP, TCP and TLS over TCP. Source: [Choose a trunk transport protocol](https://help.genesys.cloud/articles/choose-a-trunk-transport-protocol/), supported protocols section. Checked 2026-09-24. [^57]: BYOC Cloud SIP uses port 5060 for UDP and TCP and port 5061 for TLS. Source: [Choose a trunk transport protocol](https://help.genesys.cloud/articles/choose-a-trunk-transport-protocol/), firewall ports section. Checked 2026-09-24. [^58]: The trunk transport protocol setting only controls how Genesys Cloud sends calls on the trunk; it is not enforced on calls received on the trunk. Source: [Choose a trunk transport protocol](https://help.genesys.cloud/articles/choose-a-trunk-transport-protocol/), important note on protocol selection. Checked 2026-09-24. [^59]: Genesys recommends TCP rather than UDP when SIP headers carry large amounts of UUI or custom data, because UDP messages that exceed the MTU can cause call failures. Source: [Choose a trunk transport protocol](https://help.genesys.cloud/articles/choose-a-trunk-transport-protocol/), UDP and TCP protocol descriptions. Checked 2026-09-24. [^60]: BYOC Premises – Customer VM Solution reached end of support on 2024-01-20 and end of life on 2025-11-10, because it was built only for Windows Server 2012 R2. Source: [Deprecation: BYOC Premises - Customer VM Solution](https://help.genesys.cloud/announcements/deprecation-byoc-premises-customer-vm-solution/), announcement summary and reason section. Checked 2026-09-24.