Difference between revisions of "ATC/RequiredPCDomains"
From Genesys Documentation
(Published) |
(Published) |
||
| Line 3: | Line 3: | ||
|DisplayName=Required Genesys Cloud domains | |DisplayName=Required Genesys Cloud domains | ||
|TocName=Required Genesys Cloud domains | |TocName=Required Genesys Cloud domains | ||
| − | |Context= | + | |Context=For agents to view journey context data from {{MINTYDOCSPRODUCT}}, specific Genesys Cloud domains must be available. |
|ComingSoon=No | |ComingSoon=No | ||
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | ||
| Line 10: | Line 10: | ||
|anchor=RequiredDomains | |anchor=RequiredDomains | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |structuredtext=As a cloud-based product, {{MINTYDOCSPRODUCT}} needs access to various websites in order to work. When you implement {{MINTYDOCSPRODUCT}}, | + | |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] | |
| − | + | *<nowiki>https://dhqbrvplips7x.cloudfront.net/</nowiki> | |
| − | + | *Region-specific Genesys Cloud domains listed in the following sections: | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#USE1 Americas (US East)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#USW2 Americas (US West)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#CAC1 Americas (Canada)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#EUW1 EMEA (Dublin)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#EUC1 EMEA (Frankfurt)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#EUW2 EMEA (London)] | |
| − | + | **{{Link-Standalone|topic=ATC/RequiredPCDomains|anchor=APS1|display text=Asia Pacific (Mumbai)}} | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#APNE2 Asia Pacific (Seoul)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#APSE2 Asia Pacific (Sydney)] | |
| − | + | **[https://all.docs.genesys.com/Draft:ATC/RequiredPCDomains#APNE1 Asia Pacific (Tokyo)] | |
==Notes about the required {{MINTYDOCSPRODUCT}} domains== | ==Notes about the required {{MINTYDOCSPRODUCT}} domains== | ||
Revision as of 18:52, April 27, 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 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 domains listed in the Domains and IP Addresses section
- https://dhqbrvplips7x.cloudfront.net/
- Region-specific Genesys Cloud 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!