In the VoIP business, downtime means lost revenue and angry customers. A proper VOS3000 disaster recovery plan ensures that your softswitch keeps running even if the primary server fails. Whether you’re serving hundreds or thousands of concurrent calls, a master‑slave high availability (HA) setup is the industry standard for reliability.
In this guide, we’ll walk you through the complete process of configuring VOS3000 disaster recovery, including prerequisites, step‑by‑step setup, testing, and best practices.
VOS3000 stores all critical data – accounts, rates, CDRs – in a MySQL database. If the server crashes, you lose not only current calls but also the ability to route new traffic. A disaster recovery setup provides:
VOS3000 uses a master‑slave replication model:
When the master fails, the slave detects the outage, activates its softswitch services, and assumes the virtual IP. Calls in progress may drop, but new calls are processed immediately.
Before you begin, ensure you have:
On the master server, enable binary logging and set a unique server ID:
# Edit /etc/my.cnf[mysqld]
log-bin=mysql-bin server-id=1 binlog-do-db=vos3000db # your actual database name
Restart MySQL and create a replication user:
CREATE USER 'replica'@'slave_ip' IDENTIFIED BY 'strong_password';
GRANT REPLICATION SLAVE ON *.* TO 'replica'@'slave_ip';
FLUSH PRIVILEGES;
Record the master status:
SHOW MASTER STATUS;
Stop MySQL, copy the master data to slave (using `mysqldump` or `xtrabackup`), then configure slave:
[mysqld]
server-id=2
relay-log=relay-log
Start MySQL and set up replication:
CHANGE MASTER TO
MASTER_HOST='master_ip',
MASTER_USER='replica',
MASTER_PASSWORD='strong_password',
MASTER_LOG_FILE='mysql-bin.xxxxxx',
MASTER_LOG_POS=xxxx;
START SLAVE;
Verify with SHOW SLAVE STATUS\G – both Slave_IO_Running and Slave_SQL_Running should be “Yes”.
Install and configure keepalived on both servers. Example `/etc/keepalived/keepalived.conf` (master):
vrrp_instance VI_1 {
state MASTER
interface eth0
virtual_router_id 51
priority 101
advert_int 1
virtual_ipaddress {
192.168.1.100/24 # your virtual IP
}
}
On slave, change state to BACKUP and priority to 100. Restart keepalived.
On both servers, ensure that VOS3000 listens on the virtual IP (edit network settings or use IP aliasing). In the VOS3000 web interface, set the “Local IP” of gateways and phones to the virtual IP. This way, after failover, devices reconnect automatically.
Simulate a master failure by stopping the master server or the VOS3000 process. Verify that:
VOS3000 provides built‑in tools to monitor HA status:
Access these via the web interface under “Disaster Recovery System”.
Even with replication, you need regular backups:
No, VOS3000 officially supports active‑passive master‑slave replication. Active‑active is not recommended because of potential conflicts in real‑time billing and CDR sequence.
With keepalived and properly tuned services, failover typically completes within 5‑10 seconds. Calls established before failure may drop, but new calls are processed immediately.
If replication is synchronous enough, most CDRs are already on the slave. Any CDRs that were in memory but not yet written to the master’s database may be lost. To minimize loss, set `sync_binlog=1` and `innodb_flush_log_at_trx_commit=1` on master.
Yes, but it’s recommended to use identical hardware to ensure consistent performance during failover. If the slave is weaker, it may struggle to handle full traffic load.
Repair the master, ensure it has caught up with the slave (re‑sync if needed), then manually promote it back using a controlled switchover procedure to avoid split‑brain.
Implementing VOS3000 disaster recovery with master‑slave replication is the best way to protect your VoIP business from unexpected outages. While the setup requires careful planning, the peace of mind and service continuity are well worth the effort.
Need help configuring high availability for your VOS3000? Contact us on WhatsApp for expert assistance: +8801911119966
VOS3000 Caller Number Pool: Powerful CLI Rotation for Outbound Traffic The VOS3000 caller number pool feature solves a critical problem… Read More
VOS3000 Protect Route: Smart Backup Gateway Activation with Timer The VOS3000 protect route feature is one of the most misunderstood… Read More
VOS3000 outbound registration setup guide for carrier SIP trunk connections. Configure VOS3000 to register outbound to carriers, IMS, and ITSP… Read More
This website uses cookies.