steep-balloon-41261
09/13/2025, 10:07 AMtall-airline-16756
09/13/2025, 10:08 AMtall-airline-16756
09/13/2025, 10:08 AMringing_timeout
field when creating a SIP participant via API, SDKs, or CLI.
• Max Call Duration: This sets the maximum duration allowed for a SIP call, which defaults to 24 hours. You can customize this using the max_call_duration
field.
When it comes to server-level settings, you can tweak the config.yaml
file with options like:
• `sip_ringing_interval`: Controls how often re-INVITEs are sent during ringing.
• `media_timeout`: Defines the timeout for inactive media streams.
If you'd like, I can provide specific examples or guide you through these configurations step-by-step. Just let me know—I'm here to help!
Sources: pkg/config/config.go | cmd/lk/sip.go | packages/livekit-server-sdk/src/SipClient.ts | livekit-protocol/livekit/protocol/sip.pyi | lib/livekit/proto/livekit_sip_pb.rbprehistoric-printer-73777
09/13/2025, 10:09 AMtall-airline-16756
09/13/2025, 10:10 AMtimeToWaitMs
or similar variables. These are commonly set to 10,000 ms (10 seconds) or 20,000 ms (20 seconds) in files like session-view.tsx
or NoAgentNotification.tsx
.
• Agent Worker Initialization: The LiveKit Agents SDK includes a 10-second timeout for initializing agent processes, which you can control with the initialize_process_timeout
setting in the worker options.
• Platform-Level Timeouts: If you’re deploying on platforms such as Fly.io, keep in mind there might be additional timeouts like kill_timeout
that affect long-running sessions.
If you’d like, I’m here to help you find and adjust these settings in your frontend code. Just let me know how I can assist!
Sources: Sources/LiveKit/Types/Options/ConnectOptions.swift | Infrastructure & Deployment | livekit/livekit_composite | DeepWiki | lib/controllers/app_ctrl.dart | agent-console/components/no-agent-notification.tsx | complex-agents/nutrition-assistant/nutrition-assistant-frontend/components/...