[Kamailio-Users] Redundancy and fault-tolerance

Uriel Rozenbaum uriel.rozenbaum at gmail.com
Wed Mar 4 18:30:08 CET 2009


Guys, let's go a step backwards.

I'm now trying HeartBeat and succeded making one node starting when the
other is down, that is fine.

Now we have the following scenario:

2 Floating IPs: 192.168.200.80 and .82

Kam1: Fixed IP 192.168.200.81, master for .80 and backup for .82
Kam2: Fixed IP 192.168.200.83, master for .82 and backup for .80

Then I'll have both servers up, load-sharing 50% of the load each.

When any of them has an issue I need the other to take the load but without
restarting Kamailio (as i don't want to refresh cache). If I use
'listen=0.0.0.0' I'll have record_route to write wrong things on the SIP
Header:

*Record-Route: <sip:0.0.0.0;ftag=as24719265;lr=on>*
*Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bKf5c5.04e5a224.0*
Via: SIP/2.0/UDP 192.168.200.11:5060;branch=z9hG4bK41474ecd;rport=5060
From: "541160911100"
<sip:541160911100 at 192.168.200.81<sip%3A541160911100 at 192.168.200.81>
>;tag=as24719265
To: <sip:1054111556446967 at 192.168.200.81<sip%3A1054111556446967 at 192.168.200.81>
>
Contact: <sip:541160911100 at 192.168.200.11<sip%3A541160911100 at 192.168.200.11>
>
Call-ID: 68dd3a3971ec68ab08b3086c59ac276d at 192.168.200.81
CSeq: 102 INVITE
User-Agent: Metrotel
Max-Forwards: 69
Remote-Party-ID: "541160911100"
<sip:541160911100 at 192.168.200.81<sip%3A541160911100 at 192.168.200.81>
>;privacy=off;screen=no
Date: Mon, 02 Mar 2009 18:23:25 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 320

If I use 'listen=eth0' then I'll have to restart Kamailio when an event
occurs.

Is there any workaround you may know to solve this? Any module or trick to
check the received address in order to use it with listen=0.0.0.0?

Thanks!
Uriel

On Tue, Mar 3, 2009 at 7:56 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:

> El Martes, 3 de Marzo de 2009, Juha Heinanen escribió:
> > Iñaki Baz Castillo writes:
> >  > I mean in the DRB replication process.
> >
> > there are provisions in the protocol to detect data corruption when data
> > is copied to disk of the secondary.
>
> Yes, I know it, I've used DBRD :)
> But I didn't know how reliable that protocol is.
>
> Thanks.
>
>
> --
> Iñaki Baz Castillo
>
> _______________________________________________
> Kamailio (OpenSER) - Users mailing list
> Users at lists.kamailio.org
> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20090304/e2003c3b/attachment.htm>


More information about the sr-users mailing list