Difference between revisions of "ATC/RequiredPCDomains"
From Genesys Documentation
(Published) |
m (Text replacement - "Genesys Cloud" to "Genesys Cloud CX") |
||
Line 1: | Line 1: | ||
{{Article | {{Article | ||
|Standalone=Yes | |Standalone=Yes | ||
− | |DisplayName=Required Genesys Cloud domains | + | |DisplayName=Required Genesys Cloud CX domains |
− | |TocName=Required Genesys Cloud domains | + | |TocName=Required Genesys Cloud CX domains |
− | |Context=For agents to view journey context data from {{MINTYDOCSPRODUCT}}, specific Genesys Cloud domains must be available. | + | |Context=For agents to view journey context data from {{MINTYDOCSPRODUCT}}, specific Genesys Cloud CX domains must be available. |
|ComingSoon=No | |ComingSoon=No | ||
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | ||
Line 12: | Line 12: | ||
|structuredtext=As a cloud-based product, {{MINTYDOCSPRODUCT}} needs access to various websites in order to work. When you implement {{MINTYDOCSPRODUCT}}, ensure that your network configuration allows access to the following domains: | |structuredtext=As a cloud-based product, {{MINTYDOCSPRODUCT}} needs access to various websites in order to work. When you implement {{MINTYDOCSPRODUCT}}, ensure that your network configuration allows access to the following domains: | ||
− | *All Genesys Cloud domains listed in the [https://help.mypurecloud.com/articles/?p=25911 Domains and IP Addresses section] | + | *All Genesys Cloud CX domains listed in the [https://help.mypurecloud.com/articles/?p=25911 Domains and IP Addresses section] |
*<nowiki>https://dhqbrvplips7x.cloudfront.net/</nowiki> | *<nowiki>https://dhqbrvplips7x.cloudfront.net/</nowiki> | ||
− | *Region-specific Genesys Cloud domains listed in the following sections: | + | *Region-specific Genesys Cloud CX domains listed in the following sections: |
**{{Link-Standalone|topic=ATC/RequiredPCDomains|display text=Americas (US East)|anchor=USE1}} | **{{Link-Standalone|topic=ATC/RequiredPCDomains|display text=Americas (US East)|anchor=USE1}} | ||
**{{Link-Standalone|topic=ATC/RequiredPCDomains|display text=Americas (US West)|anchor=USW2}} | **{{Link-Standalone|topic=ATC/RequiredPCDomains|display text=Americas (US West)|anchor=USW2}} |
Revision as of 21:28, November 9, 2021
Contents
- 1 Required domains for all implementations
- 2 Notes about the required Genesys Predictive Engagement domains
- 3 Americas (US East)
- 4 Americas (US West)
- 5 Americas (Canada)
- 6 EMEA (Dublin)
- 7 EMEA (Frankfurt)
- 8 EMEA (London)
- 9 Asia Pacific (Mumbai)
- 10 Asia Pacific (Seoul)
- 11 Asia Pacific (Sydney)
- 12 Asia Pacific (Tokyo)
For agents to view journey context data from Genesys Predictive Engagement, specific Genesys Cloud CX domains must be available.
Required domains for all implementations
As a cloud-based product, Genesys Predictive Engagement needs access to various websites in order to work. When you implement Genesys Predictive Engagement, ensure that your network configuration allows access to the following domains:
- All Genesys Cloud CX domains listed in the Domains and IP Addresses section
- https://dhqbrvplips7x.cloudfront.net/
- Region-specific Genesys Cloud CX domains listed in the following sections:
Notes about the required Genesys Predictive Engagement domains
Domain | Used for |
---|---|
https://api.mypurecloud | API resources |
https://apps.mypurecloud | Non-cached static assets |
https://journey-websockets.mypurecloud | Real-time events |
https://dhqbrvplips7x.cloudfront.net/ | Cached static assets |
https://login.mypurecloud/ | Logging in users |
Note:
Americas (US East)
- API domain: https://api.mypurecloud.com
- Apps domain: https://apps.mypurecloud.com
- Websocket domain: https://journey-websockets.mypurecloud.com
Americas (US West)
- https://api.usw2.pure.cloud
- https://apps.usw2.pure.cloud
- https://journey-websockets.usw2.pure.cloud
Americas (Canada)
- https://api.cac1.pure.cloud
- https://apps.cac1.pure.cloud
- https://journey-websockets.cac1.pure.cloud
EMEA (Dublin)
- https://api.mypurecloud.ie
- https://apps.mypurecloud.ie
- https://journey-websockets.mypurecloud.ie
EMEA (Frankfurt)
- https://api.mypurecloud.de
- https://apps.mypurecloud.de
- https://journey-websockets.mypurecloud.de
EMEA (London)
- https://api.euw2.pure.cloud
- https://apps.euw2.pure.cloud
- https://journey-websockets.euw2.pure.cloud
Asia Pacific (Mumbai)
- https://api.aps1.pure.cloud
- https://apps.aps1.pure.cloud
- https://journey-websockets.aps1.pure.cloud
Asia Pacific (Seoul)
- https://api.apne2.pure.cloud
- https://apps.apne2.pure.cloud
- https://journey-websockets.apne2.pure.cloud
Asia Pacific (Sydney)
- https://api.mypurecloud.com.au/
- https://apps.mypurecloud.com.au/
- https://journey-websockets.mypurecloud.com.au/
Asia Pacific (Tokyo)
- https://api.mypurecloud.jp/
- https://apps.mypurecloud.jp/
- https://journey-websockets.mypurecloud.jp/
Comments or questions about this documentation? Contact us for support!