IVG 3.10 system requirements
From internal VHT performance testing the IVG system requirements to support up to 300 concurrent call sessions, are a Virtual Machine (VM) server configured with four cores, and with hyperthreading enabled for the equivalent of eight virtual CPU's (vCPU's).
Virtual machine (VM) | Operating System | Number of VHT Callback licenses | Memory | Disk space | vCPUs |
Linux | Up to 2501, 2 | 8 GB | 60 GB | 4 (2 cores; 2 sockets per core) |
1The port count for IVG increases 20% when the Postgres database is is separate from the IVG VM.
2The 250 port count represents a deployment without TLS/SRTP enabled.
The IVG installation process installs VIS along with IVG.
A remote connection across a Wide Area Network (WAN) between an IVG and the PostgreSQL database is not recommended. If a WAN is used, a latency of 20 ms or greater can lead to a voice platform initialization timeout resulting in an endless loop during IVG startup.
Disk partitioning guidelines
Use the following table to identify the Linux OS disk partitioning sizing guidelines for IVG:
File system | Space requirements | Installation directories |
File system separate from root | A minimum of 15 GB free disk space is recommended. | /usr/local/tomcatversion |
/usr/local/tomcatversion/webapps/ROOT/namefiles | ||
"/export/home" |
A minimum of 40 GB free disk space is recommended. This file system should be mounted on its own dedicated disk partition. | /export/home/holly |
/export/home/postgres/version Note: Partitioning for PostgreSQL is only required on IVG VMs to be deployed with a PostgreSQL database. | ||
"/tmp" | A minimum of 1 GB free space is recommended for temporary storage of fetched audio, documents, and scripts/tmp should be mounted as a tmpfs partition. | NA |
swap | A swap space equal to the amount of memory at a minimum is recommended. |
Codec Support
The following codecs can be used for SIP calls to the voice platform:
- G.711
- G.729
Operating system support
Operating system[1] | App server | Java version | Media server | Database support |
| Tomcat 9.0.4 | Java 8 | Apache HTTP Server 2.4.10 | PostgreSQL 9.6.6.1 |
[1] Package updates can be applied for minor release upgrades per the Red Hat Enterprise Linux Application Compatibility Policy.VHT engineers recommend applying the OS patch update in a lab environment, and verifying functionality with regression testing prior to deploying in a production environment.
IVG ports
The IVG installer process opens the following ports which are used by IVG voice platform:
Process | Port | Description |
browser | 4080 | MONAPI port |
browser | 5080 | Outbound call request port |
callcontrol | 4081 | MONAPI port |
call control | 8040 | HTTP listen port |
callcontrol | 8041 | HTTPS listen port |
callredux | 4095 | Callredux listen port |
configserver | 6399 | Listen port |
ctimgr | 20000 | ICM listen port |
foreman | 8333 | Trap port |
foreman | 8400 | Supervise port |
hinge | 7399 | Listen port |
hlm | 9333 | Listen port |
hlm | 9400 | Supervise port |
hmspageserver | 2080 | Listen port |
hmsweb | 2020 | HTTP listen port |
hmsweb | 2021 | HTTPS listen port |
hotts | 4088 | MONAPI port |
hotts | 32330 | TTS interaction port |
hvg | 8050 | HTTP listen port |
hvg | 8051 | HTTPS listen port |
hvg | 8062 | MRCP v2 ASR listen port |
hvg | 9876 | Listen port |
hvg | 9999 | Supervise port |
hvss | 8030 | HTTP listen port |
hvss | 8443 | HTTPS listen port |
logmgr | 7333 | Listen port |
SIP/RTP | 5060 | Primary SIP listen port |
SIP/RTP | 5061 | Secondary SIP listen port |
TLS/SSL | 5070 | Primary TLS port |
TLS/SSL | 5071 | Secondary TLS port |
SIP/RTP | 11000-15000 | RTP ports used for calls |
SIP/RTP | 11000-15000 | RTP ports used for MRCP v2 interaction |
subagent | 8161 | Listen port |
SNMP Agent | 705 | Third-party software |
tts_hum | 8066 | MRCP v2 TTS port |
tts_hum | 32331 | Listen port for TTS (MRCP v2) interaction |
Third party IVG ports
The IVG installer process opens the following ports for third party components in addition to the voice platform ports:
Process | Port | Description |
ICM CTI listen port | 5000 |
Port that runs the ICM CTI worker. Notes:
|
Mountd | 892 | Port used by the NFS client in a multiple IVG environment. |
NFS | 111 | Port used by the NFS server if NFS is enabled. |
20143 | Port used by the NFS client if NFS is enabled. | |
PostgreSQL | 5432 |
PostgreSQL port number. Note: This port number can be designated during IVG installation. |
Tomcat | 8009 | Ports used by Tomcat (VIS and CCIS) |
8005 | ||
8080 |
Performance
While actual performance is dependent on the IVG system, internal VHT acceptance testing achieved the following performance level when all recommended configuration procedures were followed:
Observed performance
|
Projected performance
|
Important:
The observed performance of the G.729 decreases by 60% when compared to the G.711 codec VHT best practices recommend considering this performance when sizing your deployment.
Virtual machine requirements
IVG software has been tested using the following virtualized environment:
- VMWARE ESXi (version 5.5 or higher), 64-bit compatible.