Hello there. My SIP to livekit was working fine up...
# telephony
b
Hello there. My SIP to livekit was working fine up but since yesterday livekit no longer answers. What could have changed?
c
Same here ! No change in code. Models are OpenAI realtime and Gemini Live.
b
also using openai realtime. Bot will still answer from a web call but SIP gets no reply
l
I don't see any issues in our SIP status. Do you see the calls on your LK cloud dashboard? Can you provide the call ID of a failed call?
b
@lively-winter-88668 No, nothing reaches the LK cloud dashboard and there is no response to the invite call.
when you say call ID what specifically do you need?
l
Ah, are you using Twilio? Looks like they are experiencing an incident: https://status.twilio.com/
r
If you continue to have problems you can share the PCAP from Twilios side or provide the Twilio CallID
b
No not using Twilio, I have a custom Karmillo instance
r
Can we get a PCAP of the issue?
b
Let me know if this will suffice. thanks
r
The
INVITE
to
field should have your LiveKit SIP URI and not just an IP address.
b
hmm it was working previously though. Perhaps the IP changed?
that did indeed fix it thanks so much
a
@refined-appointment-81829 @lively-winter-88668 I had the exact same issue and the fix worked for me too - thanks! But I'm curious about the root cause: what changed on the LiveKit SIP server side that now requires the full SIP URI in the INVITE To field instead of accepting just the IP address? Our setup was working fine before with just the IP, and we didn't change anything in our configuration. Was there a recent update to the SIP server that made URI validation stricter? Understanding what changed would help us avoid similar issues in the future and ensure our integration stays compatible.
l
I believe that would have been coincidence as we did not change anything. We do not have static IP addresses, so only support the SIP URI. Chris, please weigh in if I'm wrong.
r
Like Darryn was indicating about:
Copy code
...But I'm curious about the root cause: what changed on the LiveKit SIP server side that now requires the full SIP URI in the INVITE To field instead of accepting just the IP address?
LiveKit has not supported IP address in the
TO
or
INVITE
field so the "change" was most likely from something external to LiveKit.