SBC

SBC Manager — High Availability Operations

SipLive SBC Manager supports an active/active dual-node HA model. Both SBC nodes share a replicated database and operate independently — each manages its own Asterisk instance and apply agent.

   SBC Node 1              SBC Node 2
   (Asterisk + GUI)        (Asterisk + GUI)
          \                     /
           \                   /
            [ shared / replicated MariaDB ]

The dashboard shows the health, heartbeat, and apply state of both nodes simultaneously. HA features are available on licensed tiers — pair nodes via account linking on the Settings → Activation page.

Managing HA Nodes

Go to Settings → Sync Settings (HA / Replication) to view and manage cluster nodes. From this page you can:

Register a new node in the cluster
View each node's connection status and last heartbeat
Put a node into maintenance mode before upgrades or reboots
Remove a decommissioned node

Monitor → HA Nodes shows live node status.

Maintenance Mode

When a node is in maintenance mode its apply agent is paused and the dashboard shows it as intentionally offline. Other nodes continue serving calls normally. Clear maintenance mode when the node is ready to return to service.

Failover Behavior

If one SBC node becomes unreachable, the other continues serving calls using its last-applied Asterisk configuration. No manual intervention is required — PJSIP endpoints on both nodes are symmetric.

Firewall Symmetry

Web, SSH, and SIP firewall allowlists are mirrored to the peer node automatically, so both nodes stay reachable by the same management and carrier addresses after failover.

SBC Manager — Activation and Licensing SBC Manager — API Tokens and Audit Log SBC Manager — Backups, Restore, and Remote Storage SBC Manager — Bulk Operations, Capacity, and Maintenance SBC Manager — Carrier Templates and the New Endpoint Wizard