SBC Manager — Routing Policies and Route Simulation
How the SBC Routes Calls
- Inbound (from a carrier): the call is matched by its dialed number — per-DID trunk assignment (see DID Management) — normalization and security policies are applied, and the call is delivered to the assigned PBX-side trunk, with automatic failover to the DID's backup trunk.
- Outbound (from the PBX): the dialed number is matched against priority-ordered prefix policies, the winning policy selects the carrier trunk, HMR transforms are applied, and the call is sent. Lower-priority policies with the same prefix provide automatic carrier failover.
Routing policies control how calls are matched and where they are sent. Go to Routes to manage them.
Policy Types
| Type | Description |
|---|---|
| Destination | Matches the dialed number by prefix and routes to a specified trunk |
| Source | Matches the calling number by prefix |
Priority
Multiple policies can match the same call. The policy with the lowest priority number wins. Leave gaps between priority values (e.g., 100, 200, 300) so future policies can be inserted without renumbering.
Failover
If the primary trunk on the winning policy is unavailable, the next matching policy is tried automatically — built-in call failover with no extra configuration.
Example: NANPA Outbound with Backup
| Priority | Policy Name | Prefix | Trunk |
|---|---|---|---|
| 10 | Emergency — 911 | 911 | carrier-primary |
| 10 | Emergency — 988 | 988 | carrier-primary |
| 100 | Outbound NANPA — Primary | 1 | carrier-primary |
| 200 | Outbound NANPA — Backup | 1 | carrier-backup |
911/988 always go to the primary carrier at highest priority. All other NANPA calls try the primary carrier first, then fall back to the backup automatically.
Time Windows
Policy → Time Windows lets you define named schedules (business hours, after hours, holidays) that routing policies can reference, so calls route differently by time of day.
Route Simulation
Go to Routes → Simulate to test routing decisions without placing a real call. Enter a source and destination number to see which policy wins, which trunk is selected, and which transforms are applied. A batch simulation API (/api/v1/route-simulate/batch) can test up to 200 calls in one request.