Telnyx Conference Status

The caller hung up while on hold.

This is the ONLY way a Telnyx window can end early, because unlike Telegram and WhatsApp there is no second handset of the owner's that could have picked the call up. Resolving here is what makes the takeover task stand down (it loses the claim) and what clears the banner for an invite with no agent behind it.

Signed, like every other Telnyx endpoint in this file. An earlier version argued the guarded UPDATE made verification unnecessary — but idempotence only defends against REPLAY, and invite_id is a sequential integer in a query string. A forged POST could close a stranger's live window: the agent would then stand down (its claim is gone) while nobody hangs up the caller, who stays parked on hold music with no one coming.

The invite names its own account, so unlike /voice/status there is no need to try every key in the workspace — there is exactly one right key here. An unknown invite answers 204 rather than 404, so this cannot be used to probe which invite ids exist.