i am having a issue in my sip and livekit server that my age LiveKit Community #ask-ai

i am having a issue in my sip and livekit server t...

astonishing-smartphone-66046

04/20/2026, 9:30 AM

i am having a issue in my sip and livekit server that my agent when deployed on myown livekit server makes 3 concurrent calls with some auth error at first then 408 and 407 error i belive 1) Primary failure (root cause)

Copy code

SIP.CreateSIPParticipant → request timed out (15s)
status: 408 deadline_exceeded
error: request timed out

This means: LiveKit sent an outbound SIP INVITE via your trunk (

ST_HQ2Nc49ua4d7

) The upstream provider (

<http://livekit-server-dev.pstn.twilio.com|livekit-server-dev.pstn.twilio.com>

) did not respond in time • So the call never got established 👉 This is the main failure.

tall-airline-16756

04/20/2026, 9:30 AM

Thanks for reaching out, ali. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

tall-airline-16756

04/20/2026, 9:30 AM

Thanks — I’m responding to the SIP 408/407 failures you reported (LiveKit sending an INVITE that times out, and prior 407 auth errors). I can help troubleshoot—please share a few details so I can narrow the root cause. Please provide: • Your SIP outbound trunk config (hide passwords if you prefer; at minimum share

host

port

transport

(UDP/TCP/TLS), and

auth_username

). • The exact sequence/timestamps of the errors from your LiveKit logs (the 407 entries and the 408 timeout). • Whether the SIP provider requires Proxy-Authorization or Digest auth, and if you’ve confirmed the credentials with the provider. • Whether you can reach the provider from the LiveKit host (results of

telnet <host> <port>

nc -vz <host> <port>

), and whether any NAT/firewall sits between LiveKit and the provider. • If you’re using TLS: confirm the certificate/trust setup and that SNI is correct. • Whether the agent makes 3 concurrent calls always, and whether they succeed against a different/trusted SIP endpoint. What I’ll check once you send those: • Authentication mismatch signs in the logs (407 challenges and how LiveKit responds). • Transport/connectivity timeouts causing the 408 deadline_exceeded. • Any misconfigured caller ID or trunk settings that the provider might reject. If you’d rather not paste config here, share the log excerpts for the 407 and subsequent 408 (redact secrets). Sources: LiveKit Phone Numbers | Connect voice agents to phone lines | LiveKit | Agents telephony integration | LiveKit Documentation | sip | livekit/livekit_composite | DeepWiki | Preserving Caller ID During SIP Transfers in LiveKit Agents, with interactive elements

7 Views

Open in Slack

Previous Next