Server Requirements
The specific hardware and system software required for your implementation is determined by inContact WFO Sales Engineering during the discovery and system design process. No system hardware or software should be purchased or requisitioned until the final system design document is complete.
Hardware Requirements
inContact WFMv2 can be deployed as part of an inContact WFO system, or as a standalone system without any other inContact WFO modules. If you are using inContact WFMv2 with an integration to the inContact Cloud Contact Center, all functionality is in the cloud and no server hardware is needed at your site.
If your inContact WFMv2 system integrates with a third-party ACD (such as Avaya or Cisco), a server is required at your site for deployment of the integration components.
In general, inContact recommends a server with at least 4 GB of RAM and a quad-core processor. The server can be physical or virtual, and must have a public-facing IP address. This server is referred to as the PREMISES server.
In a scenario where the integration is to a third-party ACD, and you are deploying inContact WFMv2 along with inContact WFO (which also requires a PREMISES server), a single PREMISES server, meeting the inContact WFO specifications, may be shared.
Software Requirements
The following software environments have been tested with and are supported for system servers:
- Operating System: inContact WFMv2 — Windows 2012 R2
- Protocols — IPv4
Licensing
inContact WFO Sales Engineering explains licensing requirements during the sales process. If SSL is used in the network, a certificate file must be purchased from a third-party vendor (such as VeriSign).