Thanks Michael.
In my testing the phones reregistered quite quickly actually e.g. a couple of
seconds. The arping would have sorted out the ARP table on the phone.
I actually don't want auto failover at this time. Lots of testing required as
it could actually break a working system e.g. duplicate Virtual IP Address
Regards
Michael Knill
On 21/7/18, 9:15 pm, "Michael Keuter" <li...@mksolutions.info> wrote:
> Am 21.07.2018 um 03:11 schrieb Michael Knill
<michael.kn...@ipcsolutions.com.au>:
>
> Hi Group
>
> I have won a reasonable size customer (90 extensions) and Im currently
testing Astlinux hot standby.
> This is what I am planning to do:
> • The Astlinux HS is in parallel to the primary Astlinux server with
different IP Addresses on the internal and external interface but same subnet.
Its likely that these systems will be behind a firewall using NAT. The SIP
Trunk will be registered and not IP Address based.
> • The primary server periodically synchronises its config and database
to the HS server. I can basically use my standard backup and restore script to
do this
> • Both servers are remotely accessible
>
> In the event that the primary server fails, the following is performed to
failover to the HS server:
> • Add primary server IP as virtual IP on HS server e.g. ifconfig
eth1.100:1 172.30.30.1 netmask 255.255.255.0
> • Update ARP table e.g. arping -q -U -c 3 -I eth1.100 172.30.30.1
> • Register the SIP Trunk on the HS server
>
> My initial testing seems to work well and I cant find any issues.
>
> Obviously there are some caveats:
> • Don't sync gui.network.conf and Asterisk SIP Trunk config files as
they are different on the HS server
> • The virtual IP is not permanent. If the outage is long term, the HS
server should be converted into the primary (only a couple of files are
different)
> • Unless converted into the primary, any config changes (including
dynamic ones) will need to be synced to the primary server when failed back
> • Devstate will not be maintained
>
> Although this solution is not perfect, the ability to run up a new server
in minutes remotely is certainly a big plus.
>
> What do you think? Can you see any other issues?
>
> Regards
> Michael Knill
Hi Michael,
some thoughts:
* It could take some time until all IP-phones re-register on the
Real/Virtual server IP (depending on their config up to 10 minutes).
* If you have a central PoE-switch you could simply reboot that switch to
reboot all phones at once to re-register.
* Think about that the provisioning then also switches.
* Some phones (e.g. Yealink) also have the ability to register to a 2nd
SIP-server and do a failover on their own…
For automatic switching of the "Virtual IP" there are existing solutions
(not in AstLinux yet):
* ucarp (domain "ucarp.org" seems to be gone) =>
https://github.com/jedisct1/UCarp/commits/master (not very up to date :-( )
* keepalived (an older version is in Buildroot) => http://www.keepalived.org
https://blog.itanddevelopment.com/simple-automatic-failover-for-asterisk-and-freepbx/
http://blog.unicsolution.com/2015/01/kamailio-high-availability-with.html
Only my 2 ct.
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
