<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
as I understood, the issue was that when pua_reginfo received a
notify and inserted a record in location table, usrloc executed a
callback in pua_reginfo to send notify, which can result in endless
cross notifications between nodes.<br>
<br>
If yes, I pushed a patch in master branch, can you test and see if
it works? If all ok, it will be considered for backport in stable
branches.<br>
<br>
On the other hand, I am not sure it works when the topology is like
a linear (circular) list, thus it might need to be wrapped as config
option -- this just came in my mind, not analysis for it, maybe this
is not feasible at all anyhow.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 03/11/14 12:50,
<a class="moz-txt-link-abbreviated" href="mailto:lejarreta.e@sarenet.es">lejarreta.e@sarenet.es</a> wrote:<br>
</div>
<blockquote cite="mid:25bf0115ad69677b3e42394f41255fa8@sarenet.es"
type="cite">Good morning.
<br>
<br>
We've got a problem with location memory and database replication
between "n" kamailios as REGISTRAR servers.
<br>
<br>
1.- WHAT WE WANNA DO:
<br>
<br>
- To have "n" Kamailios with their DB and memory "user location"
replicated.
<br>
- Each Kamailio owns its own DB.(It could be also with a common
DB).
<br>
- Each kamailio has a PUA_REGINFO, PRESENCE, and REGISTRAR roles.
<br>
- USRLOC Module with db_mode = 2 (Write-Back scheme).
<br>
<br>
2.- WHAT WE DON'T WANNA DO:
<br>
<br>
- USRLOC Module with db_mode != 2 (Write-Back scheme).
<br>
<br>
3.- BACKGROUND:
<br>
<br>
- RFC3265
<br>
- RFC3680
<br>
- RFC3903
<br>
- I attach a small architecture graph.
<br>
<br>
4.- PROBLEMS:
<br>
<br>
4.1 Deadlock:
<br>
<br>
Each REGISTER involves a NOTIFY to the other side.
<br>
Each NOTIFY involves another NOTIFY to the other side.
<br>
<br>
There should be a mechanism to avoid PUBLISH
reginfo_handle_notify() function calls but to PUBLISH save() calls
on pua_reginfo module.
<br>
<br>
Any idea would be appreciated (also to workaround our problem).
<br>
<br>
4.2 PUA_REGINFO module notify.c
<br>
<br>
Just FYI.
<br>
<br>
We think It doesn't comply to RFC3680. It should observe
"unkown-param" object to aid "Contact" header params such as
"Path", "Received", "User_agent" and so on.
<br>
<br>
We've changed code but for a fast startup we've also avoided
"unkown-param" and now we're able to see replicated "Path",
"Received ... params on each DB.
<br>
<br>
Thanks and best regards.
<br>
<br>
Eduardo Lejarreta.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Nov 24-27, Berlin - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a></pre>
</body>
</html>