inbound call is not disconnecting at callers end a...
# ask-ai
r
inbound call is not disconnecting at callers end after room is deleted?
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 sorry you’re seeing the inbound call stay connected after the room is deleted. I’m responding to your report that the caller’s leg does not disconnect when you call
DeleteRoom
. What happens when LiveKit deletes a room • Deleting a room causes LiveKit to send a SIP BYE to all SIP participants to terminate their call legs. • If the caller’s device or SIP provider does not receive or honor that BYE, the caller will still see the call as active. Quick checklist to narrow this down • Confirm the
DeleteRoom
request was processed. I can help you inspect logs—did you run
lk agent logs
around the delete event? • Verify LiveKit sent the BYE. In the logs you should see the DeleteRoom processing and an outbound BYE to the trunk. • Check the SIP trunk behavior. Some SIP providers or PSTN gateways do not honor BYE reliably or may require additional headers or settings. • Confirm trunk configuration for header mappings. If you use
attributes_to_headers
or other mappings (for e.g., Five9 integration), ensure those mappings and the trunk settings aren’t altering or blocking BYE signaling. • Check for timing or network issues. If the caller hangs up first or there’s packet loss, the BYE may not be received. Next diagnostic steps I can guide you through 1. Share the room ID and approximate timestamp (UTC) of the DeleteRoom call so we can look for the specific log entries. 2. If you can, paste the relevant portion of the
lk agent logs
output showing the DeleteRoom processing (redact any sensitive tokens). 3. Tell me your SIP provider / PSTN gateway and whether you use any header mappings like
attributes_to_headers
or special SIP options (for example, integration with Five9). What to expect after these checks • If logs show the BYE was sent but the caller didn’t disconnect, the most likely cause is the SIP provider/gateway not honoring BYE — in that case we’ll review trunk settings or suggest using SIP REFER / other hangup mechanisms if supported by your provider. • If logs show the BYE was not sent or was malformed, we’ll identify why and fix the configuration or server-side behavior. If you prefer, share the room ID and logs now and I’ll help pinpoint whether the BYE was issued and what the next fix should be. Sources: How to do call transfers with Five9 | LiveKit | sip | livekit/livekit_composite | DeepWiki