Firewall configuration

In this section

Version history




  • You must read this entire section to ensure that you configure your firewall correctly.
  • Inbound and outbound traffic terminology:
    • Inbound describes traffic from VCC.
    • Outbound describes traffic to VCC.

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).

You should also review any IP packet inspection or local caching policies to optimize the user experience.

Ports

Outbound

All outbound traffic requires TCP port 443 (HTTPS). Responses are sent to a range of ephemeral ports. This requirement applies to:

SFTP access to call recordings requires TCP port 44044.

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.

Virtual private network (VPN)

We recommend using a split tunnel configuration to ensure that traffic—especially voice traffic—to Vonage services is routed directly from the end user to our platform and not through a VPN. We do not recommend tunneling voice connectivity through a VPN tunnel due to the potential adverse effect on voice quality.


Using URL allowlisting (recommended)

Depending on whether you will use wildcard or fully qualified domain names, add the following URLs to your allowlist:

You must also add the IP addresses specified in the following sections to your allowlist:

WebRTC traffic

Webhooks API traffic

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.

Outbound VCC traffic

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:

--Amazon Web Services (AWS)

Most of VCC uses Amazon Web Services (AWS).

Add the IP addresses for your region as described in the following page: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html.

This list of addresses is subject to change.

There might be multiple AWS regions associated with your VCC region:

VCC regionAWS region IDAWS region name
EMEA

eu-central-1Frankfurt

eu-west-2London
NAM

us-east-1North Virginia

us-west-2Oregon
APAC

ap-southeast-1Singapore

ap-southeast-2Sydney


--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:

The IP addresses are all outbound addresses.

--NewRelic

Add this range of IP addresses—162.247.240.0/22—to any existing firewall permissions.

The IP addresses are all outbound addresses.

--WebRTC traffic

--Webhooks API traffic