A place to ask questions, connect with others, and stay in the know
Hi @Phil Whitener,Hoping I can tag onto the end of this discussion :)We are newly onboarding to Genesys Cloud (which will be well after the 24 Feb) and currently in the process of evaluating the required firewall rules to allow communications with Genesys Cloud.Can I assume that for the 'Genesys Cloud services' listed (including BYOC Cloud edge devices, managed phones and WebRTC) that we would only need a destination of 126.96.36.199/20 and won't need to add all the AWS IP's for cloud media services?Is there a way to confirm that after 24 Feb that our instance will only use the 188.8.131.52/20 range (or force it to)? Will new connections after 24 February only use the new range if successful and stop using the existing AWS shared ranges - or be a mixture until migration is complete?Having a single range for the cloud media services will be great - which means I don't have to convince our firewall team to add all the AWS IP's for cloud media services.Cheers,Jeff
Every year, Genesys® delivers more than 70 billion remarkable customer experiences for organizations in over 100 countries. Through the power of the cloud and AI, our technology connects every customer moment across marketing, sales and service on any channel, while also improving employee experiences. Genesys pioneered Experience as a ServiceSM so organizations of any size can provide true personalization at scale, interact with empathy, and foster customer trust and loyalty. This is enabled by Genesys Cloud™, an all-in-one solution and the world's leading public cloud contact center platform, designed for rapid innovation, scalability and flexibility. Visit www.genesys.com.