To see SIP error logs and validate connection errors, you can enable detailed logging on your LiveKit SIP instance. According to
LiveKit documentation, you should ensure that both SIP signaling port (5060) and media port range (10000-20000) are accessible from the Internet. Additionally, you can use tools like Wireshark to capture SIP traffic for debugging purposes, as suggested in
this Slack discussion.
If you are using LiveKit Cloud, you might not have direct access to SIP logs, but you can check the Twilio or your SIP provider's logs for any error messages related to the call. If you are self-hosting, ensure that your server logs are set to a verbose level to capture detailed information. You can also check if there are any specific error events being fired, such as
Disconnected
events, which might indicate a failed dial attempt, as mentioned in
this Slack thread.
Would you like more detailed guidance on setting up logging or capturing SIP traffic?
Sources:
-
LiveKit documentation
-
this Slack discussion
-
this Slack thread 👍 0 button 👎 0 button 💡
Hint: Mention @runllm in the thread for followups.