Introduction
The following are the minimum recommended hardware requirements for an IVR server for the Capacity Management Suite® solution. System performance will vary based on data volume, network, and server capacity.
Third Party Hardware Requirements
IVR Server Requirements
Dedicated Servers Required
1
Architecture
Intel® 64-bit or equivalent AMD processor is supported.
Server Operating System
Windows Server® 2016
Windows Server® 2019
Note: The Capacity Management Suite® solution installed on Windows Server 2019 cannot reliably be integrated with the Rauland staff assignment system. Integrations with other staff assignment systems, such as Hill-Rom® and Kronos®, may also be affected.
CPU
Intel® Xeon® processor, 2.0GHz, 133MHz FSB, or equivalent AMD CPU.
RAM
For details on socket and core requirements, see Server Requirements per Hospital Size.
Disk Architecture
RAID 5
Free Internal Disk Space
80 GB for the application partition
80 GB for a separate operating system partition
Fault Tolerance
RAID
High Availability
Yes. Active/Passive.
Note: TeleTracking allows failover clustering within Microsoft Clustering Services but does not set up or support this environment. This is the responsibility of the client’s server administrator (or equivalent role).
Network Interface
Ethernet 100/1000 Mbps
Performance may vary based on bandwidth. NIC teaming is supported.
Backup Device/Method
Customer-provided
Backup must have open file capability. File locking must be disabled.
Proprietary Hardware
Not required.
Application is CPU Intensive
No
Paging File Size
Use the recommended Microsoft® Windows setting.
Microsoft® Windows PowerShell™
Minimum Version: 5.1
Execution Policy: Cannot be set to Restricted, AllSigned, or RemoteSigned
Load Balancing
Supported on the web tier only
Only supported with Microsoft® Network Load Balancing
TeleTracking will not set up or support this environment. Responsibility falls to the client’s server administrator.
Recommended: Use Source IP persistence with a persistence time equal to the average shift length (8 hours).
Web Server and Third Party Software Components
Microsoft® Internet Information Services (IIS)
Version 10 for Windows® 10 and Windows Server® 2016/2019
Microsoft® Visual C++ 2015 - 2017 Redistributable (x64)
Installed by TeleTracking installation program:
Microsoft® .NET Framework 4.8 or later (must be manually installed before updating to Capacity Management Suite® solution v2021.12 or later)
Microsoft® Web Service Extension 3.0
Microsoft® Visual C++ 2015 - 2017 Redistributable (x64)
RabbitMQ Server
Erlang OTP
Microsoft® ODBC Driver 17 for SQL Server
Microsoft® OLE DB Driver for SQL Server
Third-Party Software
SQL Client Tools
Virtualized Servers
Supported if the virtual machine meets all specified requirements and only supports a network-based configuration
Must comply with network paging requirements. TeleTracking does not support or set up virtual environments.
VM environments may increase RAM and CPU requirements. Performance may vary based on hardware, configuration, and utilization. All systems should follow Microsoft’s Best Practices.
Microsoft® Active Directory
Required for Capacity Management Suite® solution v2022.03 and later
Clients must supply a valid SSL certificate (trusted self-signed or third-party like Verisign; test certificates not valid)
Supported deployment options:
LDAPS supported
On-Premise, Not TeleTracking IQ® Enabled
Cloud-Hosted, Not TeleTracking IQ® Enabled (with LDAP port open via firewall and site-to-site VPN)
On-Premise, TeleTracking IQ® Enabled (with Azure Connect)
Website Encryption
SSL is optional but strongly recommended for Capacity Management Suite® solution versions 2022.02 and earlier
SSL is required for Capacity Management Suite® solution version 2022.03 and later
Network
Network Protocols | TCP/IP Connectivity between IVR server and database server uses TCP port 1433 by default. |
Requires Name Resolution | Yes |
DHCP Supported | No |
Shared Folders Required | Shared folders are required only for integration to the Census Based Scheduling (CBS) component of the Smart Facility™ (formerly Environmental Services Computer Tools (ESCt)) software. CBS and ESCt are not available when the Capacity Management Suite® solution is deployed in a Cloud-Hosted model. |
Mapped Drives Required | No |
Network Security Model | 2000 |
Internet Access | No |
Voice-Over-Internet Protocol Requirements
TeleTracking will supply the Host Media Processing (HMP) software as follows to support IVR call delivery to the TeleTracking application server via a VoIP/SIP connection.
Third Party Software | TeleTracking will provide the following Host Media Processing (HMP) software:
|
Transport Protocol | UDP (recommended) or TCP |
Architecture | DM3 |
Concurrent Calls | 4-48 – Depends on facility size, actual count will be provided by the TeleTracking project team. |
Call Control | Session Initiation Protocol (SIP) (The H.323 protocol is not supported.) |
Medial Streaming and Control over IP | Real-time transport protocol (RTP) |
Audio Format | G.711 |
Purchased Licenses Needed? | Yes |
Remote Access
HMP Elements Best Practice Settings
The following settings are TeleTracking Best practice for setting up a SIP trunk for HMP Elements.
Recommended Default Settings
Protocol | Configuration |
Session Initiation Protocol (SIP) | RFC3261 Compliant |
SIP and RTP Protocol | UDP |
DTMF Protocol | RFC2833 |
SIP Listen and Transmit Port | 5060 |
RTP Listen and Transmit Port | 49152 and UP |
Standard Codex | G711 Mulaw as the standard codec. G711Alaw is also available with configuration changes. |
Type of calls we accept | We will answer any call that is presented to us |
Does SIP Trunk need to register | We do not need to have anyone register with us. However, if a registration request is received, we will return an OK. |
How should HMP Elements look to SIP RFC3261 Compliant | We prefer to look like a “peer” to the other system since we can handle up to 1000 simultaneous calls |
How do we handle SIP ALG | Ensure that SIP ALG is disabled for any routers that will handle the traffic. |