Not yet configured, but exotel has asked for "*The...
# ask-aib
billions-grass-55145
12/19/2025, 10:01 AMNot yet configured, but exotel has asked for "*The Fully Qualified Domain Name (FQDN) and the destination protocol if you are utilizing dynamic IP addresses".*
Exotel supports only static-IP whitelisting, (no username/password).
t
tall-airline-16756
12/19/2025, 10:01 AMThanks for reaching out, Latish. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
12/19/2025, 10:01 AMThanks — I see Exotel needs the FQDN and destination protocol for whitelist-based SIP trunking and that Exotel only accepts static-IP whitelisting (no username/password). I don't have a predefined FQDN or protocol for Exotel in our docs.
A couple quick questions so I can give an exact answer or the right values to share with Exotel:
1. Are you planning to terminate SIP traffic to a LiveKit-hosted component (our cloud) or to your self-hosted LiveKit server?
2. If self-hosted, can you share the public hostname (FQDN) or the public/static IP you plan to use for SIP termination?
3. If LiveKit-hosted, do you need me to check which public-facing SIP gateway FQDN and protocol we can provide for Exotel to whitelist?
If you want the destination protocol recommended now: tell me whether Exotel expects SIP over UDP, TCP, or TLS (or if they accept all), and I’ll confirm which protocol LiveKit (or your deployment) supports for SIP trunking.