jaison
07/13/2026, 11:08 AMBrian @ Testzilla.ai
07/13/2026, 11:31 AMAI Evy
07/13/2026, 11:31 AMAI Evy
07/13/2026, 11:31 AM18.98.16.120/30 (All regions) , 3.42.144.0/23 (All regions) , 143.223.88.0/21 (certain United States traffic) , 161.115.160.0/19 (certain United States traffic) to whitelist traffic to Retell's SIP server [(1) ]() . However, this is for outbound traffic from Retell to your infrastructure, not for whitelisting your SBC's IP for inbound calls.
The 200 OK Issue with LiveKit
There's a known behavior with LiveKit: the 200 OK will not come from the same IP number as the one you sent the INVITE to. If you have a firewall configured, it will block the inbound 200 OK from LiveKit [(2) ]() . This could explain why you're seeing silence after your INVITE reaches 18.98.16.120.
Your Setup Options
Based on the documentation, you have two methods for custom telephony [(1) ]() :
Method 1: Elastic SIP Trunking - This is what you're attempting. For inbound calls with this method, your origination settings in your SIP trunking provider need to be correctly configured to route to sip.retellai.com . The transport methods supported are TCP (Recommended) , UDP, TLS, and mTLS .
Method 2: Dial to SIP URI - If elastic SIP trunking doesn't work with your setup, you would need to use the Register Phone Call API to obtain a call_id, then dial to sip:{call_id}@sip.retellai.com . You must dial the call to the SIP URI within 5 minutes of calling Register Phone Call .
Recommendations
1. Check your firewall rules to ensure the 200 OK response from LiveKitAI Evy
07/13/2026, 11:32 AMAI Evy
07/13/2026, 11:32 AMAI Evy
07/13/2026, 11:32 AM