Hi,
I run a smallish VoIP/internet network using Mikrotik to wirelessly move the traffic.
So far everythings great except that if I need to use another route for voip (ie between primary and backup backhaul, equipment can fail,freeze etc), I have to reboot both the CPE and voip gateway simulataneously at the client. (remotely of course)
Just changing the route works for internet traffic but voip doesnt work, call doesnt go through, still stays registered on client device though.
Im looking for an automatic way for using another route to occur with minimum downtime for the client. The voip is natted.
Clients generally get an 192.168.1.0/24 range for the Mikrotik device ether1, the wlan1 side is routed using bgp.
(I am about make a software that monitors each device (voip gateway and CPE) at the terminal level per client , which would then handle the rebooting of both devices simultaneously but imo there just got to be a better way)
Any help or insights would be appreciated. (or even pointing out blatant idiocy on my part 
)
imho voip traffic follows same route rules as any other data stream if the voip data is treated same as the rest.
But what happens when the voip gateway isn’t reachable on the new route?
When a route changes the connection basically breaks. Normal browsing etc. is not so much effected by it but any real time data stream is. So, if a connection between server and client is broken in voip it might take some time before both ends are actually aware of this and esthabished the new connection?
Just my guesses…
Hi,
Your quite right, in this case its 15 mins with no intervention by anyone (with some voip gateway adjustments). However by the time 15 mins has gone by the customer is phoning to complain (usually), I’m looking for something faster. Maybe 2-3 mins.
Also sip extension expiration isnt as fast as it could be with delays on the server that make it hard to offer prompt registration recovery (on remote/adsl deployments).
A software solution is great except it has dependancy on the network being up where its deployed, with deployment per HS to address the issue.
However I must thank you for your answer, its relevant in that worst case scenario is 15 min downtime at the client.
Guess I’ll have to start coding 
(after a bit more checking Ive managed to get re registration down to near instant reliably via mikrotik only , thanks again)