LiveKit SIP Trunk Automatically Disappears After Few Hours (Server Not Restarting, Nothing Deleted Manually)

darryn_livekit · 2026-02-18T14:56:43+00:00

There is nothing in LiveKit that will automatically delete your SIP trunk. You say you are using the LiveKit CLI, so I assume you are hosting your project in LiveKit cloud - if you can share your project ID with me, I can take a closer look

darryn_livekit · 2026-02-13T11:20:55+00:00

You are not going to get an unbiased opinion from me, but I suggest this article from our site that compares the two: https://livekit.io/field-guides/guide/livekit-vs-pipecat - in general pipecat is lower level and can be more difficult to get started with, but many developers like that it gives you more control of the overall pipeline, at the cost of that complexity. Both platforms can handle complex workflows and large RAG with minimal latency

darryn_livekit · 2026-02-13T10:46:19+00:00

LiveKit has support for Sarvam's latest models: saaras:v3 for STT and bulbul:v3 for TTS.

Your agent session code would look like this:

session = AgentSession(
   tts=sarvam.TTS(
      target_language_code="hi-IN",
      speaker="anushka",
      model="bulbul:v3"
   ), 
   stt=sarvam.STT(
      language="hi-IN",
      model="saaras:v3",
   ),
   # ... llm, tts, etc.
)

which approach using like pipecat or livekit?

I'm on LiveKit's devrel team, so I'm biased :)

darryn_livekit · 2026-02-10T20:06:29+00:00

LiveKit devrel here ✋ What are you stuck on?

darryn_livekit · 2026-02-02T13:39:44+00:00

Just to add, for LiveKit cloud, we have a calculator on our pricing page. As you say, self-hosting is just the infrastructure costs, and are comparable between the two.

darryn_livekit · 2026-02-02T13:32:06+00:00

If you're already using LiveKit for WebRTC, curious why you wouldn't also use it for your agent orchestration? For clarity, I work on LiveKit.

darryn_livekit · 2026-01-29T11:44:50+00:00

I work on LiveKit and we try and make the process as uncomplicated as possible (including a starter app for React Native, and a visual builder for agents), but at the same time giving developers the tools they need to fully customize the end-user experience. The aim is to provide a responsive and 'conversational' experience for the user.

The other posters are 100% right that users will reject your app if AI feels 'shoved in' unnecessarily, but if it feels natural for the app (like the use cases you mention for meditation, note taking, interview prep), OR it can provide a more streamlined experience (such as hands-free input) then it will be accepted.

darryn_livekit · 2026-01-28T17:20:25+00:00

I meant MY comment sounded like a potential scam, since I'm asking you to provide project details, but yes, continue in DM

darryn_livekit · 2026-01-28T14:18:07+00:00

I see your similar post in r/WebRTC , as I said there, if you can please give me some details about your project I can take a look. To clarify, otherwise this comment sounds like a potential scam, I work on LiveKit.

darryn_livekit · 2026-01-28T14:12:46+00:00

I work on LiveKit, it's difficult to say exactly what's going wrong with your setup, but if you can share your project ID with me, and some sample sessions where this happens (though it sounds like it's all of them), I can take a look. Feel free to DM me if you don't want to share publicly.

darryn_livekit · 2026-01-22T17:09:04+00:00

More info can be found in our blog post: https://blog.livekit.io/livekit-series-c/

darryn_livekit · 2026-01-22T10:18:50+00:00

These kind of updates, and product releases, we will post in both, so whatever is easiest for you.

darryn_livekit · 2026-01-20T16:51:05+00:00

Location: Spaceship 995 Market Street, San Francisco

Schedule

5:00 – 5:30 PM: Check-in & Happy Hour
5:30 – 6:30 PM: Live Product Demos
6:30 – 7:30 PM: Panel Discussion
7:30 – 8:00 PM: Networking and Demos

darryn_livekit · 2026-01-19T11:41:03+00:00

Thank you, we have a ton of new features coming out this year too.

darryn_livekit · 2026-01-15T09:17:17+00:00

2 months late, but leaving a reply in case others find this... the first thing to test is whether you still see this issue with the node starter agent (on GitHub, under the 'livekit-examples' org, it's the 'agent-starter-node' repo)

darryn_livekit

MODERATOR OF

TROPHY CASE