OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: namezero111111 on May 24, 2019, 12:54:38 pm

Title: MultiWAN failback state flushing / VoiP failover
Post by: namezero111111 on May 24, 2019, 12:54:38 pm
Dear folks,

we are trying to setup an outgoing failover (Tier1/2) gateway group for a registered VoiP line.
So far this works well.

However, when the registration occurs via tier 2, and tier 1 comes back online, the registration stays on tier 2.

This results in the RTP data going out over tier 1 and hence being in a split state, ruining the system.

So I am wondering
1. Is there any way to kill states on tier 2 once tier 1 returns online?
2. Is there a better way to solve this?

Thank you in advance!

EDIT: Something like a "Disable State Killing on Gateway Reconnect" option, or the ability to run a custom script when a gateway comes online?
Title: Re: MultiWAN failback state flushing / VoiP failover
Post by: namezero111111 on May 25, 2019, 08:16:15 am
I had found this link describing the exact issue we're facing: https://forum.netgate.com/topic/58885/sip-trunk-failover-back-on-multi-wan-issues/3

Is there an afterfilterchangeshellcmd equivalent in OPNSense, and under what circumstances will this be executed?

Title: Re: MultiWAN failback state flushing / VoiP failover
Post by: namezero111111 on June 04, 2019, 07:54:14 pm
Mhh we've tried playing with changing filter.inc, but that seems like a bad idea in general.
Has no one ran into this with Voip?

Title: Re: MultiWAN failback state flushing / VoiP failover
Post by: mimugmail on June 05, 2019, 07:14:21 am
Can you open a feature request on github/core following the FR template?

Maybe we need something like:

Dynamic state reset (This option flushes the entire state table on IPv4 address changes in dynamic setups to e.g. allow VoIP servers to re-register.)

... when gateway switches back
Title: Re: MultiWAN failback state flushing / VoiP failover
Post by: namezero111111 on June 05, 2019, 07:48:01 am
Hi mimugmail,

I filed here: https://github.com/opnsense/core/issues/3516

Thanks!