Thanks — I can help with IPs for carrier whitelisting. To give you a precise and safe set of addresses (or an alternative), I need a few details about your setup and what you need to allow: 1. Are you using LiveKit Cloud (hosted at livekit.cloud) or a self‑hosted LiveKit deployment? 2. If cloud: which region/URL are your clients connecting to? If self‑hosted: what is the public hostname or IP of your LiveKit server(s)? 3. What exactly needs to be whitelisted: signaling (REST/WebSocket), TURN/STUN servers, media (SFU) RTP/RTCP traffic, or SIP trunking? 4. Do you require both IPv4 and IPv6 addresses? 5. Can your carrier/firewall whitelist DNS names instead of fixed IPs? (Hosted service IPs can change—DNS is often safer.) 6. Any carrier or firewall appliance details and port requirements you already know? For example: allowed protocols (UDP/TCP), TURN ports (3478/5349), expected RTP port ranges. Quick notes while you gather answers: • If you’re on LiveKit Cloud, IP addresses can change and DNS-based allowlists are usually recommended. • TURN relays typically require ports 3478 (UDP/TCP) and 5349 (TLS). RTP media uses UDP ports; if you use a fixed range on self‑hosted LiveKit you can provide that range to carriers. • If you share whether you need signaling vs TURN vs media, I can give a minimal list of ports/protocols to request from your carrier. Reply with the answers above and I’ll return the exact IPs/ports or the best alternative for carrier whitelisting. , with interactive elements