great-tiger-31125
12/19/2025, 4:43 PMtransfer_request = TransferSIPParticipantRequest(
participant_identity=participant_identity,
room_name=room_name,
transfer_to=transfer_to,
play_dialtone=False
#ringing_timeout # default ms from livekit?
)
await livekit_api.sip.transfer_sip_participant(transfer_request)
the default ringing_timeout duration from livekit side is how much milliseconds?tall-airline-16756
12/19/2025, 4:43 PMgreat-tiger-31125
12/19/2025, 4:43 PMtall-airline-16756
12/19/2025, 4:44 PMringing_timeout for transfer_sip_participant.
I don’t have the default value on hand. Could you tell me which LiveKit release or API/sdk version you’re using (SDK language and version or server/release tag)? If you don’t know the version, tell me whether you’re on self-hosted LiveKit or LiveKit Cloud. With that I can give the exact default or the correct config location to override it.great-tiger-31125
12/19/2025, 4:48 PMtall-airline-16756
12/19/2025, 4:49 PMringing_timeout value for that release in my sources.
Quick clarifying question: are you running LiveKit Cloud or a self-hosted LiveKit server with the default configuration? Also — are you calling the API via the livekit-agents library only, or do you have any custom SIP config/overrides on the server?
With that info I can either:
• look up the exact default for 1.3.2, or
• show how to read/override the timeout in your config so you get a deterministic value.great-tiger-31125
12/19/2025, 5:12 PMtall-airline-16756
12/19/2025, 5:13 PMringing_timeout for livekit-agents 1.3.2 and how it affects a Twilio SIP call.
I do not have a verified default ringing_timeout for 1.3.2. I can’t confirm defaults or server caps from here. What I can confirm and help with:
• You can pass ringing_timeout on TransferSIPParticipantRequest as milliseconds.
• Increasing the value makes LiveKit wait longer for the SIP leg to answer before treating the transfer as timed out; that’s the practical effect.
• With Twilio SIP, the likely result of increasing the timeout is simply a longer ringing period before the transfer fails. I cannot guarantee Twilio’s exact behavior here — please run a quick test to confirm how Twilio behaves for 45s/60s in your setup.
Next steps I can take for you (pick one):
• I can show the exact code snippet to set ringing_timeout in your livekit-agents call (45,000 or 60,000 ms).
• I can check the livekit-agents 1.3.2 source or your server config to confirm the default and whether any server-side maximum caps the value (I’ll need access to the repo or your server config).
• I can suggest a simple test procedure to verify behavior with Twilio in your environment.
Which of the above would you like me to do?