BYOC Cloud public SIP IP addresses
When you configure BYOC Cloud, you must inform your carrier of the Genesys Cloud IP addresses. The Genesys Cloud IP addresses are listed in the Regional Public SIP Signaling Resources tables in this article.
Use the IP addresses that correspond to the AWS region in which the Organization is based.
For example, if the Organization is based in the us-east-1 region, then you would inform the carrier to use the Genesys Cloud IP addresses listed in that table.
There are four IP addresses in each region. You must add all four IP addresses to your allowlist in order for calls from Genesys Cloud to your carrier to work properly. Furthermore, you must work with your carrier to load balance all incoming calls using those four IP addresses. Genesys Cloud load balances all outgoing calls among those same four IP addresses. This load balancing scheme allows Genesys Cloud to keep traffic balanced across our entire customer base.
For more information, see About ports and services for your firewall.
Notes:
- Call signaling and media are handled by separate services for resiliency and scaling purposes. The media IP addresses provided by the Session Description Protocol will be different than the signaling IP addresses. For more information, see Why does the Session Description Protocol provide media IP addresses which are different from the signaling IP addresses?
- The IP addresses listed in this article do not respond to ICMP Ping commands.
US East (Northern Virginia) / use1
DNS SRV – byoc.use1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
52.203.12.137 | lb01.voice.use1.pure.cloud |
54.82.241.192 | lb02.voice.use1.pure.cloud |
54.82.241.68 | lb03.voice.use1.pure.cloud |
54.82.188.43 | lb04.voice.use1.pure.cloud |
US East (Ohio) / use2.us.gov
DNS SRV – byoc.use2.us-gov-pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
3.129.185.96 | lb01.voice.use2.us-gov-pure.cloud |
3.136.43.147 | lb02.voice.use2.us-gov-pure.cloud |
3.141.75.31 | lb03.voice.use2.us-gov-pure.cloud |
3.140.225.227 | lb04.voice.use2.us-gov-pure.cloud |
US West (Oregon) / usw2
DNS SRV – byoc.usw2.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
34.211.206.63 | lb01.voice.usw2.pure.cloud |
54.244.22.120 | lb02.voice.usw2.pure.cloud |
52.32.193.99 | lb03.voice.usw2.pure.cloud |
52.33.193.56 | lb04.voice.usw2.pure.cloud |
Canada (Central) / cac1
DNS SRV – byoc.cac1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
99.79.151.210 | lb01.voice.cac1.pure.cloud |
35.182.29.150 | lb02.voice.cac1.pure.cloud |
52.60.140.216 | lb03.voice.cac1.pure.cloud |
35.182.138.230 | lb04.voice.cac1.pure.cloud |
South America (São Paulo) / sae1
DNS SRV – byoc.sae1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
18.229.62.233 | lb01.voice.sae1.pure.cloud |
177.71.170.155 | lb02.voice.sae1.pure.cloud |
18.229.17.171 | lb03.voice.sae1.pure.cloud |
54.207.115.206 | lb04.voice.sae1.pure.cloud |
Europe (Ireland) / euw1
DNS SRV – byoc.euw1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
52.212.65.21 | lb01.voice.euw1.pure.cloud |
52.212.66.56 | lb02.voice.euw1.pure.cloud |
52.212.61.62 | lb03.voice.euw1.pure.cloud |
52.212.54.249 | lb04.voice.euw1.pure.cloud |
Europe (London) / euw2
DNS SRV byoc.euw2.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
3.11.204.103 | lb01.voice.euw2.pure.cloud |
3.11.208.50 | lb02.voice.euw2.pure.cloud |
3.11.83.136 | lb03.voice.euw2.pure.cloud |
3.11.48.81 | lb04.voice.euw2.pure.cloud |
Europe (Frankfurt) / euc1
DNS SRV – byoc.euc1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
18.197.177.95 | lb01.voice.euc1.pure.cloud |
52.28.196.118 | lb02.voice.euc1.pure.cloud |
18.197.58.44 | lb03.voice.euc1.pure.cloud |
18.184.11.49 | lb04.voice.euc1.pure.cloud |
Europe (Zurich) / euc2
DNS SRV – byoc.euc2.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
167.234.50.224 | lb01.voice.euc2.pure.cloud |
167.234.50.225 | lb02.voice.euc2.pure.cloud |
167.234.50.226 | lb03.voice.euc2.pure.cloud |
167.234.50.227 | lb04.voice.euc2.pure.cloud |
Middle East (UAE) / mec1
DNS SRV – byoc.mec1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
167.234.48.224 | lb01.voice.mec1.pure.cloud |
167.234.48.225 | lb02.voice.mec1.pure.cloud |
167.234.48.226 | lb03.voice.mec1.pure.cloud |
167.234.48.227 | lb04.voice.mec1.pure.cloud |
Asia Pacific (Mumbai) / aps1
DNS SRV – byoc.aps1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
3.6.231.246 | lb01.voice.aps1.pure.cloud |
65.1.45.119 | lb02.voice.aps1.pure.cloud |
35.154.180.222 | lb03.voice.aps1.pure.cloud |
15.207.180.196 | lb04.voice.aps1.pure.cloud |
Asia Pacific (Sydney) / apse2
DNS SRV – byoc.apse2.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
13.54.135.179 | lb01.voice.apse2.pure.cloud |
13.55.102.9 | lb02.voice.apse2.pure.cloud |
13.55.146.155 | lb03.voice.apse2.pure.cloud |
13.55.130.108 | lb04.voice.apse2.pure.cloud |
Asia Pacific (Tokyo) / apne1
DNS SRV – byoc.apne1.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
13.115.13.21 | lb01.voice.apne1.pure.cloud |
54.199.104.0 | lb02.voice.apne1.pure.cloud |
13.112.90.55 | lb03.voice.apne1.pure.cloud |
13.231.7.149 | lb04.voice.apne1.pure.cloud |
Asia Pacific (Seoul) / apne2
DNS SRV – byoc.apne2.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
52.79.48.237 | lb01.voice.apne2.pure.cloud |
52.79.67.164 | lb02.voice.apne2.pure.cloud |
52.78.39.100 | lb03.voice.apne2.pure.cloud |
15.165.109.145 | lb04.voice.apne2.pure.cloud |
Asia Pacific (Osaka) / apne3
DNS SRV – byoc.apne3.pure.cloud
IP Addresses | Load Balancer DNS Names |
---|---|
167.234.49.224 | lb01.voice.apne3.pure.cloud |
167.234.49.225 | lb02.voice.apne3.pure.cloud |
167.234.49.226 | lb03.voice.apne3.pure.cloud |
167.234.49.227 | lb04.voice.apne3.pure.cloud |
Modified date (YYYY-MM-DD) |
Revision | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2023-11-08 | Added load balancing addresses for new regions: Asia Pacific (Osaka) / apne3, Europe (Zurich) / euc2, and Middle East (UAE) / mec1. |
||||||||||||
2023-07-05 | Updated the load balancing addresses that were using legacy domain names. No impact to functionality as both the legacy and new domain names work. The following domain names were updated:
|