If you are using the voipinnovations (Metered SIP trunking) module for trunking, how can you failover your outbound calls to a different IP address? The module creates the 2 outbound and 4 inbound trunks for you.
The issue is that VI is having a service issue the last couple days with their primary outbound termination server, but neither of the two outbound trunks that get created are pointing to the secondary or tertiary IP address
Same problem, I have an outgoing route with 4 trunks in cascade.
For some tests I disabled the first trunk, and even with the setting to continue if busy, the call did not start. The outgoing route always tried to use the first trunk (disabled) this happens on freepbx 17
So there’s definitely some confusion here. The issue isn’t necessarily how to failover anymore, it’s more confusion regarding the trunks that the VI module is actually creating.
It creates 6 trunks - 2 with the naming convention voipInn-X-randomid, then 4 more like voipinn-X-randomid-inbound. This naming makes me thing that the first two are outbound trunks, while the next four are used for inbound. I could be wrong, I’m just going based off the name.
But then, you look at the IP addresses that each trunk uses. This wiki article has VI IPs listed, and what their roles are.
The first “outbound” trunk uses the IP that is designated for Primary Termination. That’s fine. The second “outbound” trunk uses the IP that is designated for Primary Origination. That confuses me.
The next four trunks, labeled “inbound” use the IPs (in order) for secondary termination, tertiary termination, tertiary origination, and quaternary origination. This is also confusing.
@kgupta can you provide some clarification? Should I just ignore the naming convention of them and start to use them based on the IP addresses?