Use BuildBindSdk.
Builds the per-session SDK binding that wires the REAL Vonage bindings onto the telephony driver. The SDK
is wrapped so the tracker learns of every call end (releasing the max-duration timer). Outbound calls
enable machine detection per onMachine (default 'hangup').
Cancels every timer and drops tracked state (server shutdown).
Handles a Vonage event-webhook payload. A terminal status (busy, failed, rejected, timeout, cancelled,
unanswered, completed) ends the call's bridge session — an unanswered outbound call never opens a media
socket, so without this the session would linger. A machine status hangs up unless onMachine is
'continue'. Other statuses are ignored.
Admits an INBOUND call: resolves the dialed DID to a pinned agent, registers the call + its media-socket
token, and starts the bridge session in the background. Returns as soon as the call is admitted so the
answer webhook can reply inside Vonage's short budget; the media socket (and any audio the caller speaks)
is buffered until the session is ready. Returns { accepted:false } (never throws) when no agent
identity matches the DID.
Places an OUTBOUND call from a given agent identity to a destination number, after the shared outbound gate (agent permission, destination policy, rate limit) has authorized it.
Starts Vonage bridge sessions. One instance per server, constructed alongside the telephony router and sharing the VonageCallMediaRegistry with the media WSS server.