FAQs: BYOC

No, while you use Genesys Bot Connector, you only incur BYOT charges. Genesys does not add additional fair use allocation charges.

Yes. BYOC Premises and BYOC Cloud are both PCI DSS Compliant.

Genesys Cloud Edge and Media Tier route calls as specified in your organization’s number plan and outbound routes configurations. For example, you can create three BYOC trunks:

• One trunk connects to a premises IP-PBX.
• One trunk connects to an international carrier.
• One trunk connects to a local carrier.

To ensure that dial strings are matched against patterns, be sure to properly configure your number plan and outbound routes. When properly configured, Genesys Cloud Edge and Media Tier select the appropriate trunk for each call. For more information, see Create an outbound route, and Add a number plan. 

BYOC allows customers to define multiple trunks, potentially to more than one carrier. Should a carrier or trunk experience an outage, calls inbound on these trunks would fail. The remaining trunks would continue to route calls in to Genesys Cloud.

However, many carriers support carrier-level failover, which you can leverage to redirect calls to alternate trunks.

A Genesys Cloud BYOC trunk allows for multiple destination SIP servers or proxies, which provides failover within an individual trunk. Also, when you create an outbound route, you can add multiple usable trunks, which provide trunk-to-trunk failover. For more information, see Create an outbound route.

BYOC, which is an acronym for Bring Your Own Carrier, allows you to define SIP Trunks between Genesys Cloud and third-party carrier devices or carrier services. BYOC is available in two distinct offerings, named according to where the connection terminates against Genesys Cloud:

• BYOC Premises: You can define SIP Trunks between premises-based Edge hardware devices and third-party systems.
• BYOC Cloud: You can define SIP Trunks between Genesys Cloud Media Tier resources in AWS and third-party systems over the public Internet.