Environmental Requirements
Port Information for Hosted inContact WFO
To minimize the number of ports that must be opened in your firewall, inContact WFO uses a service called Connection Pooling on the PREMISES server. This service requires:
| Port | Transport | Description |
|---|---|---|
| 2010 | HTTP(S) | Open on server and firewall for communication between the PREMISES server and the cloud. Either HTTP or HTTPS can be used. HTTPS is used by default. Talk to your team if you have questions about secure transport configuration. |
In addition, the following ports must be open at your location to allow for proper communication between inContact WFO components:
| Port | Transport | Description |
|---|---|---|
| 4510 | TCP | Connections from Silverlight client players |
| 2020 | HTTP | inContact WFO Web Portal connections using the HTML5 Interaction Player |
| 5650 | HTTP | Token requests for the HTML5 Interaction Player |
| 443 | HTTPS | HTTP services on the client PCs for inContact WFO Web Portal |
| 943 |
TCP |
Silverlight cross-domain policy listener |
| 5638 | TCP | Logging communications between client PCs and the PREMISES server |
| 5672 | TCP | Used by the messaging interface for various inContact WFO services |
If you use inContact Screen Recording, you will additionally need:
| Port | Transport | Description |
|---|---|---|
| 5633 | TCP | Open on client PCs for communication between the PC and the PREMISES server. Secure communication between the PREMISES server and the clients is dependent on the security of your LAN. |
If you use inContact Desktop Analytics, you will additionally need:
| Port | Transport | Description |
|---|---|---|
| 5634 | TCP | Open on client PCs for communication between the PC and the PREMISES server. These communications can be secured using HTTPS and SSL. For more information, talk to inContact Support or see |
Antivirus Software
Antivirus exclusions should be configured in any system where antivirus scanning is installed. The guidelines below are provided to assist with ensuring the reliability and performance of your inContact WFO system, while still providing for a secure environment. A lack of exclusions can cause system performance issues and possibly contribute to service outages.
These guidelines apply to both memory resident and on-demand scanning.
General Considerations
These exclusion guidelines are product-specific. For applications not specifically listed, it is often necessary to determine exclusions on a case-by-case basis. This section provides guidance in this area.
Files should typically be excluded based on the following criteria:
- Locked Files — The files are permanently locked open by a legitimate server process. Examples of these are databases such as DHCP and SQL Server, as well as files such as the Windows Pagefile.
- Large Files — The files are manipulated often by a legitimate server process and are typically large in size. Examples of these are copying CD/DVD images (.iso) and Virtual Machine Files (.vhd). In addition, operations may include offline maintenance on Virtual Machine Files and Exchange Server databases.
- Temporary Files — A large number of temporary files are written to disk by a legitimate server process.
Exclusion Guidelines
The following should be excluded from anti-virus scanning on the PREMISE Server:
- The cc_screencapserver.exe process
- Files with the *.vid extension
- The default folder associated with inContact Screen Recording, C:\temp\
- The cc_loggerservice.exe process
- Files with the *.log extension
- The default folder associated with inContact WFO logging, C:\Program Files\CallCopy\Logs\