[asterisk-ha-clustering] Active/Standby call interruption durring failover
Marcin J. Kowalczyk
marcin.kowalczyk at ccig.pl
Tue Jun 17 13:38:08 CDT 2008
Edgar Guadamuz pisze:
> With Asterisk 1.2 and 1.4 the telephones registered in the failed node
> have to re-register in the other node when the IP is moved to it, and
> that's why the call is lost.
>
It's not a problem on server:
AsteriskHA1*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
106/106 192.168.0.67 D N 5060 OK (6 ms)
sipp 192.168.1.20 N 6000 UNREACHABLE
2 sip peers [Monitored: 1 online, 1 offline Unmonitored: 0 online, 0
offline]
AsteriskHA1*CLI>
on client:
CC106*CLI> sip show registry
Host Username Refresh
State Reg.Time
192.168.0.245:5060 106 585
Registered Tue, 17 Jun 2008 20:29:37
CC106*CLI>
reboot of HA1, HA2 takes 192.168.0.245
AsteriskHA2*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
106/106 192.168.0.67 D N 5060 OK (4 ms)
sipp 192.168.1.20 N 6000 UNREACHABLE
2 sip peers [Monitored: 1 online, 1 offline Unmonitored: 0 online, 0
offline]
AsteriskHA2*CLI>
and on client:
CC106*CLI> sip show registry
Host Username Refresh
State Reg.Time
192.168.0.245:5060 106 585
Registered Tue, 17 Jun 2008 20:29:37
CC106*CLI>
so as we can see registration information is shared. In sip.conf I've
setted up bindaddr=192.168.0.245 (floating IP) to force sip clients
register to floating IP
> Asterisk 1.6 include a framework to share the users status (It could
> be the registration information also, I don't know), and perhaps, no
> registration in the other node will be needed... hopefully...
>
Like I show above problem is not on registration side (registration is
shared with file /var/lib/asterisk/astdb).
More information about the asterisk-ha-clustering
mailing list