Below is a list of IP addresses and ranges that should be approved on your network. If you are having issues, please forward these to your IT department:
IP addresses you may need to permit in order to receive web-hooks and/or allow API access to your CRM
Authorize these two IP addresses to allow API calls FROM phoneBurner to reach your CRM platform as well as allow call-done API hooks TO your CRM and/or call-done destination URL. This applies to Zoho CRM, SalesForce, Zapier, etc. if you have an allow-list of IP addresses.
| Role | IP Address | Notes |
|---|---|---|
| NAT Gateway us-west-1 Zone A | 13.57.114.30 | API and Call-Done events originate from these IPs |
| NAT Gateway us-west-1 Zone B | 52.53.118.44 | API and Call-Done events originate from these IPs |
SoftPhone (browser-based Voice over IP)
The SoftPhone is an in-browser VOIP implementation. This must be authorized if the web-browser is used to make phone calls into your dial-session. If you dial into a specific phone number using other VOIP software, a landline, or a cellular device this section does NOT apply to you.
| Role | IP | Notes |
|---|---|---|
| WebRTC Media | 52.9.232.194 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 13.52.133.85 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 13.56.166.249 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 13.57.111.161 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 13.57.80.189 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 52.52.161.55 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.151.26.231 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.183.2.216 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.193.201.124 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.193.228.79 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.193.77.72 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.215.60.255 | Permit TCP,UDP 10,000 - 40,000 |
| WebRTC Media | 54.215.80.234 | Permit TCP,UDP 10,000 - 40,000 |
| SIP over HTTP(s) Signalling | 54.241.31.181 | Permit TCP 80,443 |
| SIP over HTTP(s) Signalling | 50.18.132.124 | Permit TCP 80,443 |
Other IP addresses
| Role | IP Address | Notes |
|---|---|---|
| In-browser realtime notifications (scheduled for deprecation in 2024) | 52.52.231.116 | Permit TCP(80,443,5223, 5229,5269,7071,7443). |
Dialer HTTP Server-Sent-Events
| US - In-browser realtime notifications | 54.236.3.168/29 | Permit TCP 80,443 |
| US - In-browser realtime notifications | 54.175.191.192/26 | Permit TCP 80,443 |
| US - In-browser realtime notifications | 54.241.191.232/29 | Permit TCP 80,443 |
| US - In-browser realtime notifications | 52.9.63.128/26 | Permit TCP 80,443 |
| US - In-browser realtime notifications | 34.223.51.128/27 | Permit TCP 80,443 |
| EU - In-browser realtime notifications | 54.93.254.232/29 | Permit TCP 80,443 |
| EU - In-browser realtime notifications | 35.157.63.192/26 | Permit TCP 80,443 |
| Asia - In-browser realtime notifications | 54.250.252.48/29 | Permit TCP 80,443 |
| Asia - In-browser realtime notifications | 54.249.82.168/31 | Permit TCP 80,443 |
| Asia - In-browser realtime notifications | 18.179.18.128/25 | Permit TCP 80,443 |
| India - In-browser realtime notifications | 13.232.67.192/27 | Permit TCP 80,443 |
We also have other IP addresses that are pulled from the AWS public IP pool for certain load-balancers for the web-application; however, access to those is typically over TCP 443 (TLS / SSL) which is not typically restricted by most organizations for outbound access.
Comments
0 comments
Please sign in to leave a comment.