do live emits webhooks on sip trunk used ?
# ask-ai
r
do live emits webhooks on sip trunk used ?
t
Thanks for reaching out, Saurabh. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m responding to your question about whether LiveKit emits webhooks when a SIP trunk is used. Yes. LiveKit sends webhook events for SIP call lifecycle activity. Common webhook events you’ll receive when a SIP trunk is used include: •
participant_joined
— when a SIP caller joins a room via the trunk •
participant_left
— when the SIP caller disconnects •
room_started
/
room_finished
— when a room begins or ends due to SIP activity •
track_published
/
track_unpublished
— when audio from the SIP participant becomes available or stops •
egress_started
/
egress_ended
— if recording/egress is configured for the SIP call Webhooks are delivered as HTTP POSTs to your configured endpoint and include participant metadata that identifies the SIP connection so your backend can react in real time. If you want, I can: • show a sample webhook payload for a SIP participant, • explain how to distinguish SIP participants from normal WebRTC participants in the payload, or • help you troubleshoot missing webhooks (what endpoint to check, common failure reasons). Which would be most helpful? Sources: sip | livekit/livekit_composite | DeepWiki
r
for call events ?
t
Thanks — you’re asking specifically about webhooks for call events (SIP call lifecycle). Do you mean general call lifecycle events (rings, answered, hung up), or are you looking for specific events like call progress (ringing), answered, failed, or transfer events? I can do one of the following—please pick which you want: • Provide a list of call-related webhook events LiveKit emits for SIP trunks (answered, ended, etc.) and example payloads. • Explain how to detect call state transitions from the standard webhook events (e.g., using
participant_joined
+
track_published
to infer answered). • Help troubleshoot missing call webhooks (what to check on your webhook endpoint and common causes). Which option should I expand on, or tell me the specific call events you need (e.g., ringing, answered, busy, failed, transfer).