stopDialOut() or the REST API, the remote party hung up, or the callee never answered.
With the default "signalwire" provider an unanswered dial-out (busy, declined, unreachable) ends with this event and the payload carries the callee’s SIP status; with "daily" the same outcome is reported as dialout.error instead. See unanswered dial-outs by provider.
Common fields
Represents the version of the event. Uses semantic versioning to inform a consumer if the payload has introduced any breaking changes.
Documenting when the webhook itself was sent. This timestamp is different than the time of the event the webhook describes.
Payload
The
callerId passed when starting the dial-out, if one was supplied: the ID of a purchased phone number.The SIP provider handling the dial-out:
"signalwire" or "daily". See SIP providers.The call ID of the dial-out call leg, if available. On the Daily SIP provider this is the SIP
Call-ID; on SignalWire it is SignalWire’s SID for the SIP leg between Daily and SignalWire."signalwire" provider only. The SIP status code with which the callee ended the call before
answering, e.g. 486 (busy), 603 (declined), 404 (not found). Absent when the callee answered
and later hung up, when the session was stopped through the API, and after a call transfer.
Best-effort: it can also be absent for an unanswered call when SignalWire’s call record is not
available in time, so a missing code does not mean the callee answered.The standard reason phrase for
sip_status_code (RFC 3261), e.g. "Busy Here". It is derived
from the code, not the phrase the callee sent. Present only with sip_status_code.