Hi guys, We’re seeing an issue where the initial I...
# telephony
r
Hi guys, We’re seeing an issue where the initial INVITE → 200 OK from LiveKit SIP contains correct SDP with the external IP, but the next SIP message in the same dialog (re-INVITE or the 200 OK to it) is received by our SIP provider without a c= IP line in the SDP. We are using LiveKit SIP with use_external_ip: true . Has anyone encountered LiveKit SIP omitting the SDP connection address in mid-dialog messages? I can share the pcap if required. Thanks
HI @refined-appointment-81829 and livekit team, Any resolution for the above issue? Thanks
r
Do you have a call ID that demonstrates the issue you are having? I would like to see the PCAP
r
Please check the attached, Hope this help understand the issue. Thanks
r
Hmm, I am a little confused by that PCAP. Why are the @IP in the private address space? Is this self-hosted or in LiveKit cloud?
r
This is self-hosted LiveKit, not LiveKit Cloud. The SIP is connected to the telco provider over a private network, so it use private IPs (192.168.x.x). The provider SBC is reachable directly on this private link, which is why those addresses appear in the PCAP.
Hi, Any resolution for this ? we're not able to connect
r
I see. This channel is for LiveKit cloud. If you are self hosting it is best to ask in #C07FVFL1H3P there you and others in the community should help support eachother.