[asterisk-ha-clustering] Active/Standby call interruption durring failover

[C. Mylonas (Mr VoIP)]

FYI,
Siemens Hipath8000 stays out of the media path, that's why the call doesn't
drop.

Cheers
Chris

On Wed, Jun 18, 2008 at 4:38 AM, Marcin J. Kowalczyk
<marcin.kowalczyk at ccig.pl> wrote:

> 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).
>
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-ha-clustering mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering
>



-- 
Kind Regards,
Chris Mylonas
Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-ha-clustering/attachments/20080619/9a4b9355/attachment.htm