Alarm Capture Commands
The sbn-media alarm capture command tree lists, fetches, and replays alarm call captures — per-call bundles of packet capture (pcap), metadata, and parsed SIP messages recorded on the receiving side by the Alarm Receiver.
Persistent flags
Available on all capture subcommands:
Flag | Short | Description |
|---|---|---|
|
| Diagnose environment to source the server URL and token from |
| API proxy base URL (default: derived from | |
| Admin-Token for the signal-trace route (default: derived from |
When neither --environment nor --server is set, capture prefers a direct local NATS connection to the broker and bypasses the API proxy signal-trace route and admin token entirely. Remote use (for example, from a support workstation) requires a diagnose.environments.<name> configuration entry — see Flow Commands for the configuration shape — since that supplies both the server URL and the admin token.
list
List alarm captures matching the filter.
Flag | Description |
|---|---|
| Filter by SIP From |
| Filter by SIP To |
| Filter by line ID |
| Start time (RFC3339 or unix-ns) |
| End time (RFC3339 or unix-ns) |
| Max rows to return (default |
fetch
Download an alarm capture as a tar bundle (pcap + metadata + sip_messages.json).
Flag | Description |
|---|---|
| Output path (default: |
| Skip server-side SIP+RTP merge; |
The pcap shows whether RTP actually flowed in both directions — the standard next step after flow sip -v confirms SDP and codec negotiation looked correct but audio still didn't work.
replay
Replay a capture through the real in-band tone recognizer and alarm protocol handler.
Availability:replayis only present in diagnostic builds ofsbn-media(built with the test tag). The standard production binary does not include it — it will not appear underalarm capture --helpthere. Request a diagnostic build from Innovative when replay is needed.
Flag | Description |
|---|---|
| Replay from a local tar bundle instead of fetching by trace ID |
| Per-scenario timeout in seconds (default |
Runs the captured RTP through the actual DTMF/tone recognizer and alarm protocol handler used in production, and prints pass/fail per assertion. A decode failure can be reproduced locally from the capture — no need to re-request a live reproduction from the customer.