FAQs: BYOC Cloud

BYOC Premises allows you to configure two types of retryable codes: Retryable Reason Codes and Retryable Cause Codes. But, neither BYOC Cloud nor Genesys Cloud Voice have customer configurable retryable codes.

However, both BYOC Cloud and Genesys Cloud Voice have a set of default retry/failover codes. BYOC Cloud and Genesys Cloud Voice will failover on SIP 404 and retry/failover on SIP 408/5xx codes.

BYOC Cloud works with a number of certificate authorities. For more information, see the Certificate authority section of the TLS trunk transport protocol specification article.

Yes. But you need to be aware of the following stipulations:

• Inbound call flow requires use of AWS Direct Connect.
• Outbound call flow requires an on-premises a third-party carrier provided device or a PBX.

The BYOC Cloud public SIP IP addresses article specifies that you must add all four of available public SIP IP addresses for your organizations region to your allowlist. If you only add some of them, you will encounter failed call attempts.

For example, if you only add two of the four IP addresses to your allowlist, roughly half of your call attempts will fail.

Genesys Cloud BYOC Cloud Trunks will connect between the third-party target and the Edge/Media resources in the AWS Region an Org is based out of. Please consider connection quality and potential latency when planning for BYOC Cloud use.

BYOC Cloud supports UDP, TCP, and TLS connections.  

Yes. To do so, you’ll use the hybrid telephony connection features. For more information, see About hybrid media.

Yes. Genesys Cloud BYOC Cloud can be added to existing or new organizations that use Genesys Cloud Voice. For example, a Genesys Cloud Voice customer may want to route certain calls to an IP-PBX. A BYOC Cloud trunk could be created between Genesys Cloud and the IP-PBX and Number Plans, and Outbound Routes could be configured to deliver the appropriate calls to the IP-PBX by the BYOC Cloud Trunk rather than the Genesys Cloud Voice PSTN trunks.

If you are already a Genesys Cloud Voice subscriber, you can easily add BYOC Cloud to your subscription via the Genesys Add Ons feature. For more information, see Add BYOC Cloud or Genesys Cloud Voice to your subscription.

If you are a Genesys Cloud partner or Genesys Cloud customer who does not already have Genesys Cloud Voice subscription, you will need to contact your sales representative.

For information, see BYOC Cloud fair use policy.

Yes. You can use AWS Direct Connect to improve connection quality. Direct Connect does not provide security but allows traffic to stay on the Amazon backbone. For more information, see Set up AWS Direct Connect for use with Genesys Cloud.

No. MPLS connections to Genesys Cloud for BYOC Cloud customers are not supported. BYOC Cloud uses public IP addressing for all voice connectivity. Any traffic between a customer’s environment to Genesys Cloud would traverse a public network and not a private MPLS network for connectivity.

You create a Genesys Cloud BYOC Cloud trunk from the Admin > Trunks UI in Genesys Cloud. For more information, see Create a BYOC Cloud trunk.

Yes. You can create and configure multiple BYOC Cloud Trunks within a single organization. These trunks can connect to any variety of third-party carriers or devices.

A BYOC Cloud trunk can connect to any SIP-compliant carrier or device which can be reached by a public IP address over the Internet. This could be a cloud-based carrier, a cloud based IP-PBX, or a premise device exposed through a firewall.

A Genesys Cloud BYOC Cloud trunk is a customer-defined SIP Trunk between Genesys Cloud AWS-based Edge & Media Tier and a third-party system over the public Internet.

Yes. If BYOC Cloud is configured to use the TLS transport, then it is PCI DSS Compliant.

Genesys Cloud with a Cloud-based carrier may be right for you if any of the following describe your telephony goals: 

1. You want a cloud-only solution.
2. You want to leverage your existing carrier relationship.
3. You want to integrate with a third-party device, such as an IP-PBX.
4. You are part of a multinational company, or you want to enable a global office

BYOC Cloud uses a variety of IP addresses for media. For a list of specific IP addresses, see the Domains and IP Addresses section of the About ports and services for your firewall article.