BYOC Cloud overview

AI-generated summary

Genesys Cloud provides interoperability between its voice services and third-party carriers through the BYOC Cloud solution, which enables customers to define SIP trunks between the Genesys Cloud AWS-based Edge and Media Tier and external carriers over the public internet. Customers use the Telephony Admin UI to create SIP trunks connecting Genesys Cloud Media Tier resources in AWS to third-party carriers or devices externally. The external carrier or device can be another cloud service or an on-premises device. BYOC Cloud uses RTP over the internet between Genesys Cloud AWS resources and the third-party trunk endpoint, so consider internet quality and latency. The external carrier/device needs a publicly reachable IP address with appropriate open TCP/IP ports.

The BYOC Cloud solution provides flexibility and interoperability to the Genesys Cloud suite of voice services by allowing you to define SIP trunks between the Genesys Cloud AWS-based Edge and Media Tier and third-party carriers over the public Internet.

To implement BYOC Cloud, you use the Telephony Admin UI to create SIP trunks between the Genesys Cloud Media Tier resources in AWS and third-party carriers or devices over the public Internet. The third-party carrier or device can be another cloud service or a device at the customer’s premises.

For more information, see BYOC Cloud quick start guide.

Notes:

BYOC Cloud involves Real-time Transport Protocol traffic traveling over the Internet between an organization’s regional Genesys Cloud AWS resources and the third-party trunk termination location. Consider your Internet infrastructure quality and latency before implementing BYOC Cloud.
The third-party carrier or device must have a publicly reachable IP address, and the appropriate TCP/IP ports must be open.

[NEXT] Was this article helpful?

Get user feedback about articles.

Loading...

BYOC Cloud overview

[NEXT] Was this article helpful?