Hi

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

When self hosting how do I connect or how do I know my sip server uri? Is it just the public IP of the instance with port? So in dockerfoles do I use localhost or the public IP?

When you're self-hosting LiveKit, it's really important to use the public IP address of the machine running the SIP server, followed by the SIP port (default: 5060). Using

localhost

or an internal Docker IP might seem convenient, but it will make the SIP server unreachable from external SIP peers, and we definitely want to avoid that! Let me walk you through the key steps to get this set up smoothly: • SIP URI Format: Make sure to use

<public-ip-address>:5060

. • Configuration: In your

config.yaml

, set

use_external_ip: true

. This helps the SIP server detect and use the public IP via STUN, which is especially important if you're running in a cloud or behind NAT. • Docker Networking: Run your container with

--network host

mode to properly expose the UDP ports and allow access through the public IP. Also, please double-check that ports 5060 (for SIP signaling) and 10000–20000 (for RTP media) are open and accessible from the internet by adjusting your firewall and network settings. This step is key to making sure everything communicates smoothly. Sources: pkg/sip/types.go | Self-hosted SIP server | LiveKit Docs