Navigate to the Templates Section:
Check for VoIPmonitor Template:
Installing VoIPmonitor Template:
Navigate to the VPS Menu:
Select VoIPmonitor Template:
Important: Since VoIPmonitor can utilize significant resources due to traffic monitoring and analytics, place this VPS on a separate processing host to ensure optimal performance.
Set VPS Password:
Configure Resources:
Important: Allocate enough resources for VoIPmonitor based on expected traffic and monitoring tasks. Ensure that IOPS and bandwidth are optimized for high throughput as VoIPmonitor can generate heavy load during monitoring.
Select Network Interface and Assign IP:
Note: VoIPmonitor can monitor live VoIP traffic, so ensure proper network segmentation and security for monitored traffic.
Create the VPS:
Wait for VPS Creation:
Start the VPS:
Access VPS CLI using In-house TTY:
Get the MySQL Password from Configuration
Inside the VoIPmonitor VPS, the MySQL database is already created with the username voipmonitor and a random password. We will need to use this password for the VoIPmonitor GUI installation.
Use the in-house TTY or SSH to connect to the VPS’s CLI.
Once connected, retrieve the VoIPmonitor database password with the following command:
cat /etc/voipmonitor.conf | grep mysqlpassword
Note the value of mysqlpassword=<auto_generated_pass>, as this will be required during the web-based installation.
Complete VoIPmonitor Web Installation
Open a web browser and enter the VPS’s IP address to launch the VoIPmonitor installation page.
When prompted, enter the following database details:
Register and License VoIPmonitor:
Configure VoIPmonitor and Sensor:
nano /etc/voipmonitor.conf
# Change the id_sensor value to a unique number for each sensor you configure to avoid conflicts. The "id_sensor = 1" is reserved for the sensor on the VoIPmonitor server so in this example we will leave it at defaul value.
id_sensor = 1
# MySQL Server Details
mysqlhost = localhost
mysqlport = 3306
mysqlusername= voipmonitor
mysqlpassword= <auto_generated_pass>
mysqldb = voipmonitor
Set the interface to eth0, which is commonly used for LAN traffic inside containers.
If your server or container has multiple network interfaces, make sure to replace eth0 with the appropriate interface name for the network you want to monitor.
# Network Interface
interface=eth0
# Server-side settings
server_bind = 0.0.0.0
server_bind_port = 60024
# Password for server's sensor authentication
server_password = YourSensorPassword
Save and exit the file.
Start Sensor Service:
service voipmonitor start
Install VoIPmonitor Sensor:
wget http://www.voipmonitor.org/current-stable-sniffer-static-64bit.tar.gz -O vm-sniffer.tar.gz
tar xzf vm-sniffer.tar.gz
cd voipmonitor*
./install-script.sh --no-user-input
Configure VoIPmonitor and Sensor:
nano /etc/voipmonitor.conf
Update the following parameters to ensure proper communication with the VoIPmonitor server:
# Change the id_sensor value to a unique number for each sensor you configure to avoid conflicts. The "id_sensor = 1" is reserved for the sensor on the VoIPmonitor server:
id_sensor = 5
Set the interface to eth0, which is commonly used for LAN traffic inside containers.
If your server or container has multiple network interfaces, make sure to replace eth0 with the appropriate interface name for the network you want to monitor.
# Network Interface
interface=eth0
# Client-side settings
server_destination = < VoIPmonitor Server IP>
server_destination_port = 60024
# Password for client's sensor authentication
server_password = YourSensorPassword
Save and exit the file.
Start Sensor Service:
service voipmonitor start
http://<VoIPmonitor_IP>
Replace <VoIPmonitor_IP> with the actual IP address of your VoIPmonitor Server.