flaky-beard-91685
08/05/2025, 7:49 AMtall-airline-16756
08/05/2025, 7:49 AMtall-airline-16756
08/05/2025, 7:49 AMsip:<your-subdomain>.sip.livekit.cloud.
3. The FQDN for whitelisting is typically your SIP endpoint. For example: <your-subdomain>.sip.livekit.cloud.
4. If you are using region-based endpoints, the FQDN will include your region (e.g., us, eu, etc.): <your-subdomain>.<region>.sip.livekit.cloud.
Ensure you whitelist all relevant region-based endpoints if you are using multiple regions. Let me know if you need further assistance!flaky-beard-91685
08/05/2025, 7:51 AMtall-airline-16756
08/05/2025, 7:51 AMoutbound_address field in the SIP trunk settings—that’s where the IP address for sending SIP traffic is specified.
2. Check out the transport field too, since it tells you which transport protocol (like UDP, TCP, or TLS) is being used for SIP communication.
If you want to dive deeper, the LiveKit SIP API documentation has lots of helpful info. And of course, feel free to reach out if you have any questions—I’m here to help!
Sources: SIP APIs | LiveKit Docsflaky-beard-91685
08/05/2025, 7:53 AMtall-airline-16756
08/05/2025, 7:53 AMuse_external_ip setting is super handy—it uses STUN servers to figure out the external IP on the fly and shares it with your clients.
• LiveKit is pretty flexible and supports multiple network interfaces and NAT mappings, so it works well even when IPs change.
• By default, there’s no need to set a static IP—the system smartly adjusts based on your network setup.
If you want me to walk you through anything or help with the setup, just give me a shout!