SBC Manager — Config Apply, Scheduling, and Rollback
Changes to trunks, routes, DIDs, HMR rule sets, and fraud rules are staged in the database and do not affect live Asterisk behavior until you apply them. This lets you batch changes, preview exactly what will change, and apply at a time of your choosing.
Applying Changes
- After making changes, go to Apply
- Review the diff — every added, modified, and removed config element is shown
- Click Apply Now to push immediately, or Schedule Apply for a maintenance window
- The apply agent writes the generated Asterisk config files and reloads Asterisk
- The result (success or failure) is recorded in the apply history
Scheduling an Apply
Click Schedule Apply and choose a future date and time. Scheduled applies are visible in the queue (Operations → Scheduled Apply) and can be cancelled before they run.
Config Versions
Every apply creates a numbered config version. Go to Apply → History to browse past versions, view the full generated config for any version, and compare versions.
Rollback
If a change causes issues, go to Apply → History, find the last known-good version, and click Rollback. The prior config is queued for immediate apply and Asterisk is reloaded to that state.
Approval Workflow
If your role configuration requires approval before applying, a pending apply appears in the queue for an authorized user to review and approve or reject before it executes.
If an Apply Fails
Click the failed apply in Apply → History to view the detailed error. Common causes: Asterisk not running on the target node, a trunk or route referencing a deleted dependency, or a syntax error in the generated config (shown in the apply output).