VoWiFi slow failover when using GW Groups

[Proton]

I have theese GW groups:

I have a statis route for Mullvad GW to exit through starlink:

On both Mullvad GW i have:

The same for DOME GW.

Default Gateway is group :

and the othe rgroup lookes like this:
,

I have also set:

And i have my floating rules like this:

Including QOS settings.

The idea is that when the boat is near land the DOME GW is avtive and is top priority. VoWifi also exit there if possible.
So - when we only have Starlink - i force all VoWiFi traffic through WG GWs to always have VoWiFi work even then starlink has exit node abroad (get norwegian ip = allowed ViWiFi).

So to my question:

When both Dome and starlink is online, i can call using VoWiFi, no issues. But when Dome failes, it takes several minutes (5-6) before the mobile again can call. or get a call.
Why is this?

I know we are using UDP trffic and STATES here and that a cell phone can have a delay before he checks and reestablishes VoWiFi again, but is there something i can do to make the transition to WG GWs through starlink faster?
How can i kill the STATES faster?

I have also tried sloppy states and state timeout set to 25, but with same result.

Suggestions?

THX!

[Joshua236]

@Proton retro bowl said in VoWiFi slow failover when using GW Groups:

I have theese GW groups:

I have a statis route for Mullvad GW to exit through starlink:

On both Mullvad GW i have:

The same for DOME GW.

Default Gateway is group :

and the othe rgroup lookes like this:
,

I have also set:

And i have my floating rules like this:

Including QOS settings.

The idea is that when the boat is near land the DOME GW is avtive and is top priority. VoWifi also exit there if possible.
So - when we only have Starlink - i force all VoWiFi traffic through WG GWs to always have VoWiFi work even then starlink has exit node abroad (get norwegian ip = allowed ViWiFi).

So to my question:

When both Dome and starlink is online, i can call using VoWiFi, no issues. But when Dome failes, it takes several minutes (5-6) before the mobile again can call. or get a call.
Why is this?

I know we are using UDP trffic and STATES here and that a cell phone can have a delay before he checks and reestablishes VoWiFi again, but is there something i can do to make the transition to WG GWs through starlink faster?
How can i kill the STATES faster?

I have also tried sloppy states and state timeout set to 25, but with same result.

Suggestions?

THX!

You can try implementing a script that automatically flushes states when it detects a Gateway change, as this will significantly reduce the switching delay. The problem you are experiencing is that VoWiFi UDP connections still hold the old state, so the device takes time to check and reset. When the state is refreshed immediately, VoWiFi will reconnect faster and avoid the current 5-6 minute wait. Additionally, you can also consider reducing the state timeout value further or enabling the flush states on gateway down feature if your system supports it.