Support for Indian Server IPs and Whitelisting for TeleCMI Integration

Support Help
1

I am writing to inquire about your infrastructure’s compatibility with regional server requirements for an integration we are currently configuring.

We are integrating a Retell AI agent with TeleCMI, a custom telephony provider from India, and we need to clarify the following regarding IP addresses and hosting:

  1. Indian Server IP Support: Does your current infrastructure support or utilize Indian server IPs for outbound/inbound media streaming and signaling?

  2. IP Whitelisting: If you do support Indian server IPs, could you provide the specific IP ranges or static IPs used by your service? We need to whitelist these within the TeleCMI dashboard to ensure a secure and stable connection.

  3. Self-Hosting Options: If Indian server IPs are not natively supported, do you offer a self-hosted setup (BYO infrastructure) within a domestic Indian region (e.g., AWS ap-south-1) that we could implement?

Please let us know if there is specific documentation we should refer to regarding regional deployments or firewall configurations.

2

Indian Server IP Support & IP Whitelisting

Retell AI’s infrastructure uses specific IP blocks for SIP traffic.(1) For whitelisting in your TeleCMI dashboard, you need to configure these IP ranges:(1)

All regions:

  • 18.98.16.120/30(1)

United States traffic (certain):

  • 143.223.88.0/21(1)
  • 161.115.160.0/19(1)

The documentation notes that some non-US traffic might originate from IPs not listed above, but this traffic was scheduled to be migrated to the first IP block by December 3, 2025.(2)

Retell SIP server URI: sip:sip.retellai.com(1)

For transport methods, you can configure:(1)

  • TCP: sip:sip.retellai.com;transport=tcp(1)
  • UDP: sip:sip.retellai.com;transport=udp(1)
  • TLS: sip:sip.retellai.com;transport=tls(1)

Regional Infrastructure

I don’t have information in the available sources about India-specific server IPs or self-hosted deployment options in Indian regions like AWS ap-south-1. The documentation covers elastic SIP trunking integration with custom telephony providers(1)(3) but doesn’t specify regional server locations or self-hosting capabilities for specific geographic regions.

For detailed information about regional deployments, Indian infrastructure support, or self-hosting options, I’d recommend:

Check out these potentially useful sources:

You can also:

Would you like a general answer based on my knowledge about typical cloud infrastructure patterns instead?