Health Checks & Validation

1. Trunk Health Check

The SBC Dashboard displays real-time health status for all trunks.

Status	Description
UP	OPTIONS probe successful
DOWN	Consecutive failures exceeded threshold
UNKNOWN	Health check not configured

Configure in the trunk’s SBC metadata:

{
  "sbc": {
    "health_check": {
      "enabled": true,
      "interval_secs": 30,
      "timeout_secs": 5,
      "max_failures": 3
    }
  }
}

SBC → Dashboard displays:

SBC → Validation: Runs configuration consistency checks, detecting:

Check	Description
Trunk Reachability	Whether the dest address is valid
Route Integrity	Whether routes reference existing trunks
Codec Intersection	Whether trunk codecs intersect with global codecs
ACL Conflicts	Whether IP allow/block lists overlap
JSON-RPC Rules	Template syntax, upstream URL reachability

GET /api/sbc/validation/run

Returns a list of validation results, each containing:

SBC → Routes → Route Simulation:

Input:

Output:

SBC → Routes → JSON-RPC Simulation:

Enter match conditions to simulate JSON-RPC rule matching and upstream API calls (can be set to dry-run to avoid sending actual requests).

SBC provides independent reload operations:

Operation	Endpoint	Description
Reload Trunks	`POST /api/sbc/trunks/reload`	Re-read trunks from config files
Reload Routes	`POST /api/sbc/routes/reload`	Re-read routes from config files
Reload JSON-RPC	`POST /api/sbc/jsonrpc/config`	Update JSON-RPC configuration

Reloading does not affect active calls.