NICE inContact uses industry-standard ports and protocols for inbound and outbound phone channels. Specific ports must be opened on client workstations, firewalls, or both to access the correct server IP addresses for your NICE inContact system. The required ports vary depending on your configuration and the geographic location of your business unit.
For clarity in discussing ports, outbound is defined as from the customer initiation point to NICE inContact. Inbound is defined as the NICE inContact initiation point to the customer site.
You cannot run ping/trace route speed tests to the IP addresses listed. When performing ping and trace route tests, use the following:
speedtest-dal.incontact.com = 207.166.92.15
speedtest-lax.incontact.com = 207.166.95.55
If you try to ping or trace route using the IPs listed below, you will not get accurate results. It is normal to show packet loss if you use these IPs.
Outbound and Inbound Ports
NICE inContact uses standard Web (HTTP) and Secure Web (HTTPS) transactions. The default port used for Web (HTTP) transactions is port 80. Secure Web transactions (HTTPS) are handled by port 443. Customers that require inbound FTP (such as the SENDFILE action) or web traffic (such as the GETPAGE script action), must open the following inbound IP addresses and ports as determined by your location.
United States
Outbound Ports
| Server IP Address | Outbound Ports (to NICE inContact) |
|---|---|
| 207.166.85.0/24 | 443 |
| 207.166.86.0/24 | 443 |
| 207.166.91.0/24 | 443 |
| 207.166.94.0/24 | 443 |
| 207.166.95.0/24 | 443 and 21 |
| 207.166.100.0/23 | 443 |
| 207.166.109.0/24 | 443 |
| 199.172.9.0/24 | 443 |
| 199.172.8.0/24 | 443 |
Inbound Ports
| Server IP Address | Inbound Ports (from NICE inContact) |
|---|---|
| 207.166.80.0/24 | 443 |
| 207.166.81.0/24 | 443 |
| 207.166.82.0/24 | 443 |
| 207.166.90.0/24 | 443 |
| 207.166.92.0/24 | 443 |
| 207.166.95.0/24 | 443 |
| 207.166.101.0/24 | 443 |
| 204.176.204.0/24 | 443 |
Europe
Outbound Ports
| Server IP Address | Outbound Ports (to NICE inContact) |
|---|---|
| 216.20.242.0/23 | 443 |
| 216.20.245.0/24 | 443 |
| 216.20.249.0/24 | 443 |
| 216.20.244.0/24 | 443 |
| 216.20.248.0/24 | 443 |
| 216.20.252.0/23 | 443 |
| 199.172.9.0/24 | 443 |
| 199.172.8.0/24 | 443 |
Inbound Ports
| Server IP Address | Inbound Ports (from NICE inContact) |
|---|---|
| 216.20.242.0/23 | 443 |
| 216.20.252.0/23 | 443 |
| 216.20.244.0/24 | 443 |
| 216.20.248.0/24 | 443 |
Email Requests
You should also unblock emails from inContactxxx@incontact.com (such as, passwords@inContact.com or NGAgentEventLog@incontact.com) to avoid important emails being blocked by your spam filter.
Hardphone and CXone Softphone
Configuration
Hardphone such as Polycom (US only) and CXone Softphone configuration must include opening TCP 443. For hardphone only, UDP port 123 must be included.
| Location | IP Block | Service/FQDN | Protocol | Port |
|---|---|---|---|---|
| Dallas | 207.166.92.64/26 | dalxsp.incontact.com | HTTPS | 443 |
| UDP | 123 | |||
| Los Angeles | 207.166.95.128/26 | laxxsp.incontact.com | HTTPS | 443 |
| UDP | 123 | |||
| Frankfurt | 216.20.244.128/27 | fraxsp.incontact.eu | HTTPS | 443 |
| UDP | 123 | |||
| Munich | 216.20.248.128/27 | munxsp.incontact.eu | HTTPS | 443 |
| UDP | 123 |
Licensing and Provisioning for Softphone
Softphone also uses the following licensing and provisioning services:
| Service/FQDN | Protocol | Port | |
|---|---|---|---|
| License Server | secure.counterpath.com | HTTPS | 443 |
| Enterprise Provisioning | ccs3.cloudprovisioning.com | HTTPS | 443 |
IP Voice
VoIP devices use the SIP protocol for call control using port 5060 for non-secure session setup, and port 5061 for secure session setup. For all SIP services, port 5061 must be open for inbound and outbound as all SIP messaging traverses this port. Audio (RTP) ports are dynamically assigned from the available range of UDP ports: 1024 through the end of the range, 65,535.
| Location | IP Block | Service/FQDN | Protocol | Port |
|---|---|---|---|---|
| Dallas | 216.20.235.0/24 | dalsip.incontact.com | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| dalsec.incontact.com | TLS, SRTP | 5061, 1024-65535 | ||
| Los Angeles | 216.20.237.0/24 | laxsip.incontact.com | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| laxsec.incontact.com | TLS, SRTP | 5061, 1024-65535 | ||
| Singapore | 61.14.30.16/28 | sgpsip.incontact.com | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| sgpsec.incontact.com | TLS, SRTP | 5061, 1024-65535 | ||
| Tokyo | 210.57.57.128/28 | tkosip.incontact.com | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| tkosec.incontact.com | TLS, SRTP | 5061, 1024-65535 | ||
| Melbourne | 216.20.247.160/28 | melsip.incontact.com | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| melsec.incontact.com | TLS, SRTP | 5061, 1024-65535 | ||
| Sydney | 207.166.102.160/28 | sydsip.incontact.com | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| sydsec.incontact.com | TLS, SRTP | 5061, 1024-65535 | ||
| Frankfurt | 216.20.254.0/24 | frasip.incontact.eu | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| frasec.incontact.eu | TLS, SRTP | 5061, 1024-65535 | ||
| Munich | 216.20.255.0/24 | munsip.incontact.eu | SIP(UDP or TCP), RTP | 5060, 1024-65535 |
| munsec.incontact.eu | TLS, SRTP | 5061, 1024-65535 |
WebRTC
WebRTC services use the following IP port ranges:
| Location | IP Block | Service/FQDN | Protocol | Port |
|---|---|---|---|---|
| Dallas | 216.20.235.0/24 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| global-wrtc.incontact.com | WebRTC | 443,9080, 1024-65525 | ||
| Los Angeles | 216.20.237.0/24 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| global-wrtc.incontact.com | WebRTC | 443,9080, 1024-65525 | ||
| Frankfurt | 216.20.254.0/24 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| global-wrtc.incontact.com | WebRTC | 443,9080, 1024-65525 | ||
| Munich | 154.48.222.128/25 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| Singapore | 61.14.30.129/27 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| Tokyo | 210.25.25.128/28 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| Sydney | 103.13.81.144/28 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| Melbourne | 103.13.81.128/28 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 | ||
| Sao Paulo | 200.15.3.0/24 | wrtc-pri.niceincontact.com | WebRTC | 443, 1024-65525 |
| wrtc-sec.niceincontact.com | WebRTC | 443, 1024-65525 |
CXone WFM Enterprise
| Service | IP Address | Component | Port Used |
|---|---|---|---|
|
BUX.nicewfm.incontact.com (X will be replaced with number upon assignment) |
207.166.101.51 | RCP | 80 |
| WebStation | 443 | ||
| RTA | 10093,10103,10193,10203,10293,10303 | ||
| 207.166.100.155-156 | RCP | 80 | |
| WebStation | 443 | ||
| RTA | 10093,10103,10193,10203,10293,10303 | ||
| 207.166.100.158-166 | RCP | 80 | |
| WebStation | 443 | ||
| RTA | 10093,10103,10193,10203,10293,10303 | ||
| 207.166.101.85-87 | RCP | 80 | |
| WebStation | 443 | ||
| RTA | 10093,10103,10193,10203,10293,10303 |
CXone QM Enterprise
| Service | IP Address | Ports |
|---|---|---|
| Engage.incontact.com | 207.166.94.65 | 2001, 30006, 30100, 61616, 62000-1, 62020, 62070, 62075-78, 62080-1, 62085, 62121, 62123-4, 62130, 62132, 62137, 62141, 62142, 62145, 62300, 62301, 62333, 62334 |
|
207.166.94.65 207.166.95.107 207.166.95.108 |
62135, 62136, 62515, 62516, 63101 | |
| Screen1.engage.incontact.com Screen2.engage.incontact.com | 207.166.95.51 | 5060 |
|
207.166.95.101 207.166.95.102 207.166.95.111 207.166.95.112 |
38210-38213 | |
|
207.166.95.111 207.166.95.113 207.166.95.115 |
62122 | |
| reporter.engage.incontact.com | 207.166.94.44 | 62083, 62183, 62184 |
Studio
When using Studio with AWS enabled clusters (C29, C30, and C31), the following IP address must be allowed: 52.43.225.203.
