Maybe this should be a new Load Balancing Algorithm called Failover instead of a option under Priority. The Failover option will failover and stay until manualy failed back.
Here is another example of why I requested it.
We have a VoIP ALG device that sits behind the Peplink. The VoIP ALG device does MOS scores and other VoIP specific tasks that the Peplink can not do. So we need this device for our hosted VoIP system.
The VoIP ALG device created a session with the PBX on the internet. This sesion never times out becuase it has a 5 second heartbeat. The VoIP phones only have sessions when calls are made and they do expire. Here is the issue we have with Priority and the reason I am requesting Failover and stay.
WAN1 is up. The VoIP ALG has a session to the Internet PBX. Phones are using WAN1. WAN1 goes down. All calls are terminated. We have 2 options moving to WAN2 I will describe how they impact the users.
Option 1. Prority with “Terminate Session on recovery” turned OFF.
The VoIP ALG starts a session on WAN2. The phones start using WAN2. When WAN1 comes back on line. The Phones who’s sessions expire will start to use WAN1. However the VoIP ALG devices session does not expire so it stays on WAN2. Now we have part of our phone system on WAN1 and the other part on WAN2. The Internet PBX does not like this can all inbound calls do not work. If we had my failover and stay feature. The entire phone system would stay on WAN2 and inbound calls would work. After hours we could manualy switch them back to WAN1 so they would not loose any calls.
Option 2. Prority with “Terminate Session on recovery” turned ON.
This sounds like a good solution because it forces all traffic back to WAN1. The problem is that when WAN1 comes back on line it terminates all the sessions on WAN2. This is fine for computer Intetnet sessions but very bad for VoIP. With VoIP all the current calls will be disconnected. So the users get disconnected calls twice, the first time when WAN1 fails. This is understandable and acceptable. But then they get their calls disconnected again when WAN1 comes back on line. This second outage is not acceptable. We wanted to use the Peplink device for redundancy and to limit the outages they have. If we had a Failover and stay option we would not have that second VoIP outage.