VoIP Innovations
VoIP Innovations authenticates by IP address rather than SIP registration, and publishes several geo-redundant endpoints. The Exovo template knows this and can provision the whole recommended setup — three IP-authenticated trunks, a failover outbound rule, and the inbound IP allow-list — in a single step.
Before you start: register your PBX IP
Because authentication is IP-based, VoIP Innovations must know your system's public IP before any call will work. In the VI BackOffice, add your PBX's public IP address as an endpoint on your account, and point your DIDs at it. Your public IP is shown on Admin → Dashboard under System Information.
Provision the recommended setup
Admin → Trunks → Add trunk, choose United States → VoIP Innovations, and accept the recommended configuration. Exovo creates:
- Three outbound trunks — primary (conversational) plus secondary and tertiary geo-redundant endpoints, all IP-authenticated (no registration).
- One failover outbound rule that tries the trunks in order, so an unreachable endpoint just means the call goes out the next one.
- The inbound allow-list entries — VoIP Innovations' six sending IPs are added to the trunk IP allow-list.
Since these trunks don't register, the trunk list shows IP auth rather than a registration state — that's normal.
Inbound DIDs
Add your DIDs to the primary trunk's DID Numbers tab in international format (+1XXXXXXXXXX)
and build inbound rules for them as usual.
Enabling the inbound allow-list
Provisioning adds VI's IPs to the trunk allow-list but doesn't turn enforcement on — an allow-list that's missing one of your other carriers would silently drop their calls. When every trunk on your system is from a known-IP carrier, enable Restrict inbound to trunk IPs on Admin → Advanced → IP Blacklist for a meaningful security upgrade: SIP traffic from anywhere other than your carriers is rejected outright. See IP blacklist and allow-list.
Testing
- Outbound: dial your mobile from any extension — the call should leave via the primary trunk (check Admin → Reports or the dashboard's active-call tile).
- Failover: the outbound rule's trunk chain shows 1°/2°/3° order on Admin → Outbound Rules; no test needed, but this is where to look if the primary endpoint ever degrades.
- Inbound: call one of your DIDs — it should follow your inbound rule, or the trunk's default route if you haven't built rules yet.