@millions-hair-24956 SIP call flow issue - no ringing phase We're using a Twilio Elastic SIP trunk forwarding calls to our LiveKit SIP URI (sip:example123.sip.livekit.cloud). Calls connect immediately without any ringing phase, creating a poor user experience. Questions: 1. Can LiveKit be configured to send a 180 Ringing response before answering with 200 OK? 2. Is there a parameter to set ringing duration? 3. Are there specific SIP headers from Twilio that LiveKit would recognize to control this behavior? We've tried Twilio's header manipulation without success.

It seems likely that LiveKit can be configured to handle SIP call states, including the ringing phase. According to LiveKit documentation, the

sip.callStatus

attribute can indicate different call states such as

dialing

,

ringing

, and

active

. However, the specific configuration to send a 180 Ringing response before a 200 OK is not explicitly mentioned in the provided data sources. Regarding the ringing duration, the CreateSipParticipantOptions interface includes a

ringingTimeout

parameter, which might be used to control the ringing duration, but this is not explicitly confirmed in the data sources. As for recognizing specific SIP headers from Twilio, the SIP API documentation mentions that custom SIP X-* headers can be used, but it does not specify which headers would control the ringing behavior. Would you like more detailed information on any of these points? Sources: - LiveKit documentation - CreateSipParticipantOptions - SIP API documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.