Hi everyone, we’re debugging an outbound SIP calling issue and would appreciate help. Our setup: - We are using a self-hosted LiveKit server. - We are also using a self-hosted SIP server. - The SIP trunk is configured to call a Twilio PSTN number. What works: - The same SIP trunk credentials work correctly in the LiveKit cloud SIP server. - In our self-hosted setup, the LiveKit room and SIP participant are created successfully. - Media negotiation also starts, so the RTC side appears healthy. What happens in our self-hosted setup: - When we trigger a call, the mobile number rings. - In some cases, the phone receives multiple incoming call attempts. - Each attempt ends automatically after a short time. - The logs show Twilio returning a 407 auth challenge. - After that, the SIP invite fails and LiveKit eventually returns request timed out / 408. What we observed in logs: - SIP participant creation starts successfully. - Twilio sends 407 during the SIP invite flow. - The invite is then canceled / fails. - LiveKit reports the SIP participant request timed out. What we have already checked: - The trunk username is configured correctly. - The same trunk credentials work with the cloud SIP server. - So the issue seems specific to our self-hosted SIP server or its auth flow. Question: - Is there anything special we need to configure in the self-hosted SIP server to handle Twilio’s 407 challenge correctly? - Could the self-hosted SIP server be failing to send the correct password or digest auth response? - Why would the call be retried multiple times and create multiple ring attempts on the mobile? If anyone has seen this behavior with self-hosted LiveKit SIP + Twilio, any pointers would be appreciated.

Hi, may I know how you're importing the number? Also, could you please share the error logs? I’ll review them and we can discuss further.