Port, Domain, Voice, and IP Address Requirements

This page provides details for all applications that require specific ports and IP addresses. These requirements are necessary for your contact center to work properly.

The selection list on the right side of this page will give you the details for setting up your specific contact center. If you don't know the cluster or phone number you use, talk to your account manager.

  1. Ports and Protocols: Select the applications that your contact center uses.
    • Example: Admin, Email, MAX, Studio
  2. Domain Names and IP Addresses: Select the cluster where your tenant is housed.
    • Example: C32
  3. IP Voice: Select the phone number option matching your IP voice infrastructure.
    • Example: 700-212-0

After making your selections, the page displays only the information that applies to your CXone implementation. You may need to scroll down to view all requirements.

To ensure that you have a secure, encrypted connection, NICE CXone requires at least TLS 1.2 compliance and the following ciphers as noted.

Inbound Traffic (from your servers to CXone)

You must support at least one of these ciphers from any source that communicates with CXone such as browsers and back-end integrations. It is recommended that you support both of these ciphers if possible.

  • 0xC02F, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • 0xC030, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

Outbound Traffic (from CXone to your servers)

You must support at least one of the following ciphers on servers that CXone communicates with such as IVR scripts or other integrations. It is recommended that you support multiples of these ciphers if possible. If you are trying to integrate with other service providers, you are responsible for ensuring that those providers also meet these requirements.

  • 0x009E, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
  • 0xC013, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • 0xC02B, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  • 0xC02C, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

For clarity in discussing ports, outbound is defined as from the customer initiation point to NICE CXone. Inbound is defined as the NICE CXone initiation point to the customer site.

Ports and Protocols by Application

View information regarding your selected content here.

Domain Names and IP Addresses by Cluster

Rather than provide an exhaustive list of all fully qualified domain names (FQDN), we use templates based on some variables. If you are unsure how these variables apply to your tenant, contact your account manager for clarification.

The following variables are used:

  • {cluster} refers to the assigned cluster for a customer.
  • {custom} corresponds to a custom hostname requested by a customer. The custom variable can be assigned through several different CXone product features.
  • {num} corresponds to a Engage QM Integrated host assignment.

NICE CXone uses platform-as-a-service (PaaS) cloud services for these clusters. Because of this, the IP address list we specify is not comprehensive and only shows addresses with fixed assignments. We recommend you configure your firewall rules for filtering using hostnames in order not to block valid traffic. Also note that AWS/cloudfront IP addresses are subject to change without notice. Take precautions to ensure reach-ability of said FQDNs.

United States

North America FedRAMP

Canada

Europe (EU)

Great Britain

Australia

Japan

IP Voice by Phone Number

These phone numbers correspond to data centers maintained either by NICE CXone or partners like AWS. These data centers exist globally and typically are paired to support failover. Customers must allow communication with the appropriate ranges, or risk a network outage during fail-over events.

View information regarding your selected content here.