foreign-sapphire
foreign-sapphire4d ago

Issue with BYO SIP Trunk Provider

Have setup a new SIP trunk provider (Tigo) but outgoing calls aren't connecting. Tigo claims it’s an internal routing issue between IPs 172.31.0.220 and 172.31.9.196, but want to know how I can troubleshoot/verify if this is a problem on the Vapi or Tigo side. Any help would be greatly appreciated.
4 Replies
conscious-sapphire
conscious-sapphire3d ago
@Angus B Tigo is correct - the IP addresses that you mentioned are referred to by IANA as "Private Routing" networks. These include the following ranges:
- 10.0.0.0/8 (or explicitly 10.0.0.0 -> 10.255.255.255)
- 192.168.0.0/24 (or explicitly 192.168.0.0 -> 192.168.255.255)
- 172.16.0.0/12 (or explicitly 172.16.0.0. -> 172.31.255.255)
- 10.0.0.0/8 (or explicitly 10.0.0.0 -> 10.255.255.255)
- 192.168.0.0/24 (or explicitly 192.168.0.0 -> 192.168.255.255)
- 172.16.0.0/12 (or explicitly 172.16.0.0. -> 172.31.255.255)
This is why home network all seem to use the same networks all over the world 🙂 Now, based on what you wrote - I think you are presenting the wrong information to the various systems. Can you show us what Tigo sent you as the trunk information?
foreign-sapphire
foreign-sapphireOP3d ago
Thanks @Nir S (CEO/Founder @Cloudonix) , in the end this occurred because we were not routing requests to <credential_id>.sip.vapi.ai
conscious-sapphire
conscious-sapphire3d ago
Ok, cool
Shubham Bajaj
Shubham Bajaj2d ago
Hey, checking if this is resolved for you?

Did you find this page helpful?