Hey when i try to use twilio ws connector with self hosted livekit server i got 404 error
but when i try with livekit cloud then it works
any suggestion to make it work with self hosted livekit server
@Sakthivel_Maruthamuthu that 404 looks expected rather than misconfiguration on your side.
The self-hosted server registers five Twirp services in pkg/service/server.go: room, agent dispatch, egress, ingress and SIP. There is no connector service among them, and anything unmatched falls through to defaultHandler, which returns http.NotFound for any path other than /. So a call to livekit.Connector/ConnectTwilioCall has nothing to answer it and you get a 404. ConnectTwilioCall is defined in livekit/protocol, but the only implementation in livekit/livekit is cmd/test-server/handlers.go, which is a mock for testing Twirp calls.
The connector docs (Twilio Connector | LiveKit Documentation) do list “Either LiveKit Cloud or a self-hosted LiveKit server” under requirements though, so either there is a component I have not found or that line needs a caveat. Worth someone from LiveKit confirming which.
If you need something running now, the same page calls Elastic SIP Trunking the recommended approach, and livekit/sip is open source so that path does work self-hosted.
Thank you both for raising this, and the analysis.
The docs are incorrect and we will get that fixed. Twilio connector requires LiveKit cloud.
The nuance is that LiveKit Agents can be either self-hosted, or hosted in LiveKit cloud, but the SFU itself can’t be self-hosted.