Signed switch events and authoritative call state
Configure the event bridge, verify timestamp/nonce/signature evidence, ingest idempotent events and reconcile authoritative call status and duration.
Guides in this workflow
Follow the guide that matches the exact action, filter, menu change or issue.
Understand the signed switch-event bridge
Use authenticated voice-switch events as authoritative call-state evidence.
Configure the event bridge
Provide the protected secret-file location through the CLI deployment workflow.
Disable the event bridge
Use the CLI-only disable action when rollback or maintenance requires it.
Review event bridge configuration
Use the CLI-only event-config diagnostic to confirm callback and readiness.
Use PUT for switch events
Reject non-PUT event submissions.
Respect the 65,536-byte payload limit
Reject empty or oversized event payloads.
Send required signature headers
Provide timestamp, nonce and signature headers for every event.
Validate event timestamps
Reject stale or invalid timestamp evidence.
Use replay-protected nonces
Reject a reused event nonce.
Verify the HMAC signature
Validate the raw request body using the configured secret.
Send valid JSON
Reject payloads that cannot be decoded as an event object.
Understand idempotent event keys
Avoid creating duplicate evidence when the same valid event is delivered again.
Match an event to a call
Use call UUID/route evidence to update the correct stored call.
Ingest ringing events
Update call state when the switch reports ringing.
Ingest answered events
Record answered time and active state.
Ingest completed or hangup events
Record final status, duration and cause.
Ingest failure causes
Store the authoritative failure reason for failed/missed/declined/cancelled outcomes.
Review last switch event time
Use dashboard/diagnostics to confirm recent event delivery.