https://livekit.io logo
Join Slack
Powered by
We are getting following issue when we connect to ...
# ask-ai
s
We are getting following issue when we connect to SIP provide -- PCAP which was shared to you indicates that the call INVITE was successfully sent to LiveKit IP. We kindly request you to check at your end why the 200 OK SIP negotiation response was not received in these cases.
t
Thanks for reaching out, Mohan. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
I'm here to help you with the issue of the missing 200 OK SIP negotiation response. This can sometimes happen due to configuration or authentication hiccups, but don’t worry—we can work through it together! Here are some friendly steps to guide you: • Verify SIP Trunk Credentials: Double-check that the username and password you’ve set up in your LiveKit SIP trunk match exactly what your SIP provider expects. Authentication mismatches are a common reason calls don’t connect properly. • Check SIP Provider Configuration: It’s a good idea to reach out to your SIP provider and confirm that their service is set up to send or expect a 200 OK response. Sometimes a quick confirmation can clear things up. • Review Logs and Telemetry: Take a look at both LiveKit’s logs and your SIP provider’s telemetry for the call in question. Look specifically for the SIP INVITE request, any provisional responses like 100 Trying or 180 Ringing, and any error messages that pop up instead of the 200 OK. • Confirm SIP Trunk and Dispatch Rule Existence: Make sure the SIP trunk is properly created and that there’s a dispatch rule in place to handle incoming calls smoothly. If you’d like, feel free to share more details such as specific logs or error messages you’re seeing during the call setup. I’m here to help you every step of the way! Sources: pkg/siptest/client.go | SIP troubleshooting guide | LiveKit Docs
s
How to review Logs & Telemetry ? I am using Livekit cloud
t
I'd be happy to guide you through reviewing logs and telemetry in LiveKit Cloud. Here’s how you can get started: • Access Logs via LiveKit CLI: You can use the command 
lk agent logs
to stream runtime logs in real-time. If you’re looking for build logs, try 
lk agent logs --log-type=build
. Just a quick note: runtime logs aren’t stored by LiveKit Cloud, so you’ll want to forward them externally if you need to keep them long-term. • Forward Logs to External Services: For more detailed analysis and storage, you can forward your logs to platforms like Datadog, CloudWatch, or Sentry. For example, to send logs to Datadog, simply add your client token using 
lk agent update-secrets --secrets "DATADOG_TOKEN=your-client-token"
. This helps keep everything organized and accessible. • Use the LiveKit Cloud Dashboard: The dashboard is a great place to see real-time analytics and telemetry for your media sessions. You’ll find session-level metrics, participant insights, and track-level statistics right there. Plus, if your project uses SIP, you can check out SIP call logs as well. • Enable OpenTelemetry: If you want even deeper observability, configuring your agent with OpenTelemetry support is a fantastic option. It lets you track session execution flows and pinpoint any performance bottlenecks. If you’d like, I’m here to help with any specific setup or integration you’re working on—just let me know! Sources: Log collection | LiveKit Docs | Log collection | LiveKit Docs | Say hello to improved Cloud analytics | Announcing LiveKit Cloud | Logs, metrics, and telemetry | LiveKit Docs
Open in Slack
PreviousNext
Powered by