<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 01/27/2011 04:15 PM, Danny Dias wrote:
<blockquote
cite="mid:AANLkTiksDxkfUjU9WVAUuVD5J6LOEu+90-hNKk6Ww0fo@mail.gmail.com"
type="cite">Thanks Alex...<br>
<br>
<div class="gmail_quote">2011/1/27 Alex Hermann <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:alex@speakup.nl">alex@speakup.nl</a>></span><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thursday 27 January 2011, Klaus Darilion wrote:<br>
> Am 27.01.2011 11:21, schrieb Danny Dias:<br>
</div>
<div class="im">> > I've read some difficulty in the
synchronisation of registrations because<br>
> > Kamailio works best when it stores registrations in memory and<br>
> > registrations are constantly changing - they expire and are
renewed, as<br>
> > well as new ones joining and old ones leaving. To make the
failover<br>
> > solution function seamlessly, it is necessary to synchronise
the<br>
> > in-memory registrations between the primary and the backup
server . This<br>
> > can be done by forking a copy of the registration request to
the backup<br>
> > server, but there are some practical problems in doing this,
has anyone<br>
> > do something with this?<br>
<br>
</div>
What problems are you referring to? I use this for some years now
without any<br>
problems.<br>
<div class="im"><br>
<br>
</div>
</blockquote>
<div><br>
</div>
<div>I checked for some problems here:</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://www.smartvox.co.uk/astfaq_ha_failover_ideas.htm">http://www.smartvox.co.uk/astfaq_ha_failover_ideas.htm</a></div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> Yes - the problem with SIP based replication
is that both proxies must<br>
> be running. This is a problem as Kamailio binds to the virtual IP
at<br>
> start up - thus adding the virtual IP address to the backup server
does<br>
> not make Backup-Kamailio listening to the new IP address - you
would<br>
> have to restart the backup Kamailio.<br>
<br>
</div>
Just bind kamailio to the HA IP on both servers and do REGISTER
replication<br>
between the two (on SIP level). Then if the IP migrates to the other
server,<br>
it will take over the rgistrar function with no loss of records. No
restart<br>
needed.<br>
</blockquote>
<div><br>
</div>
<div>Do you mean that both Kamailio-1 and Kamailio-2 will be as
primary server? and the clients will register in the 2 machines? and
also they will bind to the ip of the HA? sorry my friend but i do not
understand very well, i'm quite new with redundant systems, could you
please explain a little?</div>
<div> </div>
</div>
</blockquote>
<br>
Hello<br>
<br>
This week, I have added the p_usrloc module to K master branch, that
allows partitioned user location service for Kamailio. This has the
benefits of redundancy, failover and load balancing to user location
service for K. Along with Henning Westerholt, we will also present some
strategies for partioned user location to the upcoming FOSDEM meeting
in Brussels.(more info here
<a class="moz-txt-link-freetext" href="http://www.fosdem.org/2011/schedule/event/kamailiolocationservices">http://www.fosdem.org/2011/schedule/event/kamailiolocationservices</a>)<br>
<br>
You can check the README of the module (master branch
modules_k/p_usrloc) for some strategies for partitioned user location.<br>
<br>
Marius<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:AANLkTiksDxkfUjU9WVAUuVD5J6LOEu+90-hNKk6Ww0fo@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
<br>
> I think most people either have a database (which is
highly-available by<br>
> itself) which is used by both proxies, or every proxy has a local<br>
> database and the synchronization is on DB level (e.g. master-slave<br>
> replication, btw: does somebody know if usrloc DB queries are
suitable<br>
> for master-master replication?)<br>
<br>
</div>
Last time i tried, they are not, at least not in writeback mode. One
proxy is<br>
expiring records from the DB which the other proxy is trying to update.
Maybe<br>
DB-only mode will work, but that has some practical (performcance)
problems.<br>
--<br>
Greetings,<br>
<br>
Alex Hermann<br>
<br>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Ing. Danny Dias<br>
<a moz-do-not-send="true" href="http://www.DannTEL.net"
target="_blank">www.DannTEL.net</a><br>
</blockquote>
<br>
</body>
</html>