breezy-notebook-42090
11/09/2025, 3:23 PMcuddly-photographer-93072
11/09/2025, 3:46 PMbreezy-notebook-42090
11/10/2025, 6:29 AMlively-winter-88668
11/10/2025, 12:03 PMbreezy-notebook-42090
11/10/2025, 12:51 PMbreezy-notebook-42090
11/10/2025, 12:51 PMlively-winter-88668
11/10/2025, 2:08 PMrefined-appointment-81829
11/10/2025, 2:15 PMbreezy-notebook-42090
11/10/2025, 2:50 PMrefined-appointment-81829
11/10/2025, 3:41 PMbreezy-notebook-42090
11/10/2025, 4:00 PMrefined-appointment-81829
11/10/2025, 6:22 PMINVITE to field should have your LiveKit SIP URI and not just an IP address.breezy-notebook-42090
11/11/2025, 7:51 AMbreezy-notebook-42090
11/11/2025, 11:07 AMaverage-fireman-39457
11/12/2025, 2:56 AMlively-winter-88668
11/12/2025, 8:54 AMrefined-appointment-81829
11/12/2025, 3:21 PM...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.