Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 2 days ago
    Edited by Yusuke Ouno 2 days ago

    I would like to confirm the following points regarding the recent notification about the IP address range updates.

    ■ Necessity of This Action
    My understanding is that the following actions are required based on the notification. Could you please confirm whether these actions are mandatory?

    Excerpt from the notification:

    Update the firewall allowlist to include the new IP address ranges.
    Retrieve the latest IP ranges using the GET /api/v2/ipranges endpoint or the Resource Center.
    Complete these updates within six months of the announcement.

    ■ Specific Procedure for the Required Actions
    If these actions are indeed required, could you also provide detailed instructions on the necessary configuration changes and the recommended verification steps?

    ■ Impact if No Action Is Taken
    The notification states the following:
    "If the new IP address ranges are not included in your firewall allowlist, access to the platform or certain services may be interrupted."

    Could you please clarify which specific services or functionalities may be affected if no action is taken?

    Thank you for your time and assistance. I appreciate your support and look forward to your clarification.

    https://help.genesys.cloud/ja/announcements/genesys-cloud/ip-address-range-expansion-and-firewall-requirements-notification/


    #GenesysAnnouncements

    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 2.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 2 days ago

    From my understanding, these updates mainly apply to customers/environments that use firewall or proxy allowlists for Genesys services.

    The action itself appears to mainly involve:

    • retrieving the updated IP ranges (via GET /api/v2/ipranges or the Resource Center)
    • updating the customer-managed firewall/proxy allowlists with the new ranges
    • and validating connectivity afterward.

    I could not find detailed Genesys-side configuration steps beyond updating the relevant network/security allowlists, since the actual changes would typically be handled by the customer network/security team.

    The announcement also mentions that the IP range expansion is intended to help Genesys Cloud continue scaling reliably as platform demand grows and reduce the risk of service limitations caused by exhausted address capacity.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 3.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 2 days ago

    Thank you for your reply. I'll keep it in mind.



    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 4.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements
    Best Answer

    Posted 2 days ago

    Hi Yusuke

    If you are currently allowing any of the existing IP ranges, you will need to allow the new ranges as well - https://help.genesys.cloud/articles/ip-addresses-for-the-firewall-allowlist/

    You can retrieve the latest IP ranges using the following API - https://developer.genesys.cloud/organization/utilities-apis#get-api-v2-ipranges.

    Genesys Cloud is introducing additional public IP address ranges used by platform services. These new IP ranges complement existing ranges and support current and future capacity needs.

    Genesys Cloud has published the updated list of IP address ranges through the public API and the Resource Center.

    Genesys Cloud will start using the updated IP address ranges on the effective date.

    Reason - https://help.genesys.cloud/faqs/why-does-genesys-cloud-require-that-i-have-so-many-open-ports-on-my-firewall/

    All client connections (including BYOC Premises Edges, WebRTC Clients, and hard phones for BYOC Cloud and Genesys Cloud Voice customers) to Genesys Cloud are started as outbound connections to Genesys Cloud cloud services

    Hope this helps.

    Regards



    ------------------------------
    Stephan Taljaard
    EMBEDIT s.r.o
    ------------------------------



  • 5.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 2 days ago

    Thank you for your reply. I'll keep it in mind.



    ------------------------------
    Yusuke Ouno
    ------------------------------