Firewall configuration
In this section | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Version history | ||||||
|
| Note | ||
|---|---|---|
| ||
|
We recommend adding the appropriate URLs and IP addresses to any firewall rules that restrict employee access, and we request that you treat Vonage Contact Center as a business-critical application. By this, we mean optimizing and prioritizing IP traffic to Vonage Contact Center over other non-critical traffic. This is to ensure real-time responses to agent requests are processed in a timely and efficient manner (call steering buttons, call transfers, hold requests, and so on).
...
SFTP access to call recordings requires TCP port 2244044.
Inbound
All inbound traffic requires access to destination TCP port 443 (HTTPS) on our servers to establish a connection. Responses are sent to a range of ephemeral ports.
...
Using URL allowlisting (recommended)
Add Depending on whether you will use wildcard or fully qualified domain names, add the following URLs to your allowlist:
- Using wildcard domains:
- *.vonage.com
- *.cc.vonage.com
- *.newvoicemedia.com
- *.api.newvoicemedia.com
- *.contact-world.net
- api.amplitude.com
- bam.nr-data.net
- js-agent.newrelic.com
- *.nexmo.com
Using fully qualified domain names (FQDN):
WalkMe traffic
Insert excerpt _ExcerptWalkMeFirewallConfiguration _ExcerptWalkMeFirewallConfiguration nopanel true Adobe Analytics
Add the URL addresses specified in the following page to any existing firewall permissions: https://experienceleague.adobe.com/docs/analytics/technotes/ip-addresses.html?lang=en
You must also add the IP addresses specified in the following sections to your allowlist:
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
WebRTC traffic
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Webhooks API traffic
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
Using IP allowlisting
If your firewall does not support URL or DNS allowlisting, add the following IP addresses for your region to any existing firewall permissions.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Outbound VCC traffic
| Info | ||
|---|---|---|
| ||
| Outbound IP addresses are used for standard web access, for example, agents and supervisors accessing Vonage Contact Center applications. All customers will need to allow outbound IP addresses. |
If your firewall does not support URL/DNS allowlisting, add the following IP addresses for your region to any existing firewall permissions:
...
35.178.30.136
3.11.193.198
3.126.22.243
3.121.175.40
...
--Amazon Web Services (AWS)
Most of VCC uses Amazon Web Services (AWS).
...
| VCC region | AWS region ID | AWS region name | ||
|---|---|---|---|---|
| EMEA | ||||
| eu-central-1 | Frankfurt | |||
| eu-west-2 | London | |||
| USANAM | ||||
| us-east-1 | North Virginia | |||
| us-west-1 | North California | us-west-2 | Oregon | |
| APAC | ||||
| ap-southeast-1 | Singapore | |||
| ap-southeast-2 | Sydney | |||
...
--
...
Adobe Analytics
Add the IP addresses specified in the following page to any existing firewall permissions: https://experienceleague.adobe.com/docs/analytics/technotes/ip-addresses.html?lang=en
--Amplitude
Add the IP addresses specified in the following page to any existing firewall permissions:
--Cloudfront
Add the IP addresses specified in the following page to any existing firewall permissions:
...
| Note | ||
|---|---|---|
| ||
| The IP addresses are all inbound outbound addresses. |
--NewRelic
Add this range of IP addresses—162.247.240.0/22—to any existing firewall permissions.
| Note | ||
|---|---|---|
| ||
| The IP addresses are all inbound outbound addresses. |
--WebRTC traffic
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
--Webhooks API traffic
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|