Workflow

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.

19 connected guidesLive filterPermission-aware instructions
19 guides
Category

xConnect

Open guide →
Guide

Understand the signed switch-event bridge

Use authenticated voice-switch events as authoritative call-state evidence.

Open guide →
Guide

Configure the event bridge

Provide the protected secret-file location through the CLI deployment workflow.

Open guide →
Guide

Disable the event bridge

Use the CLI-only disable action when rollback or maintenance requires it.

Open guide →
Guide

Review event bridge configuration

Use the CLI-only event-config diagnostic to confirm callback and readiness.

Open guide →
Guide

Use PUT for switch events

Reject non-PUT event submissions.

Open guide →
Guide

Respect the 65,536-byte payload limit

Reject empty or oversized event payloads.

Open guide →
Guide

Send required signature headers

Provide timestamp, nonce and signature headers for every event.

Open guide →
Guide

Validate event timestamps

Reject stale or invalid timestamp evidence.

Open guide →
Guide

Use replay-protected nonces

Reject a reused event nonce.

Open guide →
Guide

Verify the HMAC signature

Validate the raw request body using the configured secret.

Open guide →
Guide

Send valid JSON

Reject payloads that cannot be decoded as an event object.

Open guide →
Guide

Understand idempotent event keys

Avoid creating duplicate evidence when the same valid event is delivered again.

Open guide →
Guide

Match an event to a call

Use call UUID/route evidence to update the correct stored call.

Open guide →
Guide

Ingest ringing events

Update call state when the switch reports ringing.

Open guide →
Guide

Ingest answered events

Record answered time and active state.

Open guide →
Guide

Ingest completed or hangup events

Record final status, duration and cause.

Open guide →
Guide

Ingest failure causes

Store the authoritative failure reason for failed/missed/declined/cancelled outcomes.

Open guide →
Guide

Review last switch event time

Use dashboard/diagnostics to confirm recent event delivery.

Open guide →