Sticky connections

[kapara]

I am hoping I understand this correctly.

I use voip with Dual wan and on the pfSense I had a lot of problems that required hiring someone to create a custom program to run on the pfsense box to resolve the problem.

Scenario:  Voip with Dual WAN

When using VOIP with dual wan and the primary connection goes down the phones successfully reconnect on the failover WAN.

When the primary comes back up the phones make a connection on the primary WAN but since the secondary never went down the phones still keep a open connection on the backup and then the phones do not work until they are disconnected or power cycled at which time they connect only on the primary.

Most people I would think keep the voip phones on there own subnet or vlan.  This is what I did.  So the script would then verify the status of both wan connections and if the primary was up it would kill all the states related to the vlan subnet.

I want to switch over to OPNsense but not having this will cause major problems.  IT is a similar problem I face with most firewalls.

So will this resolve that issue or do I need to do a script again?  Is there any plan to implement such a feature?  Would be fantastic!

[kapara]

Anyone?

[muchacha_grande]

I think that this problem could be resolved killing every state involving phones IP addresses.
I face a similar problem but in my case with only one WAN, the public IP suddanly changes and my PBX losses registration with every trunk I have configured.
I already asked the developers having possibility to kill states with a schedule option, but with no luck.
Franco asked me to test an option that already exists that kills the states on IP change, but my ISP doesn't allow me to use the modem on bridge mode, so the WAN ip is internal for me and never detect an IP change.