Hi, We're having issues with registering an inbound SIP trunk, outbound seems to connect fine if we uncheck "inbound". I can see previous threads with similar issues, has this been resolved yet? Note: our provider has whitelisted the Vapi IP addresses

Thanks for sharing the details! To help diagnose your inbound SIP trunk issue, could you please specify what error message or behavior you see when trying to register the inbound trunk (e.g., 401 Unauthorized, timeout, or something else)? Source: - [Vapi SIP Trunking Guide](https://docs.vapi.ai/advanced/sip/sip-trunk)

The only error shows is a Toast: https://cdn.discordapp.com/attachments/1435743611076608042/1435745923979542759/image.png?ex=690d1617&is=690bc497&hm=d89c8359845b23afa1c44f799529aa5b4ecd96dd62e5750a7a5696ef14126778&

If you want to create an inbound and outbound trunk, you will have to create one with two gateways; one gateway for inbound and one for outbound. The inboundEnabled gateway needs to have the static IP address of the SIP trunk domain (the domain used for the outbound gateway but in IP format).

Thanks Kyle, i've relayed that to our provider and they've come back with: > For the inbound trunk, we will be sending calls from any IP within the following ranges: > 103.47.234.0/27 > 103.47.235.0/27 > Vapi needs to populate their ACL (Access Control List) to allow inbound traffic from our end. > Can you please check with them if they will allow traffic from multiple IP’s ?

We don't need to allowlist any IPs since its already unrestricted

Thanks Kyle, confirmed we've been able to successfully register an inbound Trunk (+test calls) when registering with an IP address. is there plans to change this so we can register with a hostname? I really don't feel comfortable registering with an IP as we lose redundancy.

There are plans to change our SIP infrastructure but not sure if that includes registering with a hostname. We will have to get back to you on that