Hi LiveKit team! :wave: I'm experiencing two issu...
# telephony
f
Hi LiveKit team! šŸ‘‹ I'm experiencing two issues with SIP outbound calls via Telnyx: Issue 1: Premature active status When I initiate a call and hang up BEFORE the recipient answers, the sip.callStatus attribute still changes to "active". This causes my billing system to incorrectly record the call as "answered". Example from logs: 164622 - participant joined room (call ringing) 164636 - sip.callStatus='active' ← User hung up but this still triggered! 164706 - participant_disconnected (30 seconds later) I hung up the call before line 2, but active was still set. Issue 2: 30-second disconnect delay Even when calls end normally with disconnect_reason=CLIENT_INITIATED, there's always a ~30 second delay between when the call actually ends and when the participant is disconnected from the room. Questions: 1. Is there a known issue with sip.callStatus='active' being set prematurely? (I saw GitHub #3841 mentions similar behavior) 2. Is the 30-second disconnect delay configurable? We need accurate billing and this causes calls to be recorded with inflated durations. Setup: • LiveKit Cloud • Telnyx SIP trunk • Outbound calls via CreateSIPParticipant Thanks!