<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
font-size:10.0pt;
font-family:"Courier New";}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:"Courier New";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Thanks you so much for these helpful guidelines.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR">David<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="mso-fareast-language:FR">From:</span></b><span style="mso-fareast-language:FR"> Daniel-Constantin Mierla <miconda@gmail.com>
<br>
<b>Sent:</b> Monday, October 12, 2020 4:56 PM<br>
<b>To:</b> David VILLAUME <david.villaume@sewan.fr>; Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org><br>
<b>Subject:</b> Re: [SR-Users] Local cache registration<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hello,<o:p></o:p></p>
<p>somehow I haven't approached un-registrations in the previous email ... but it doesn't add that much.<o:p></o:p></p>
<p>If the expires is 0 (variable $expires(...) can be useful here) in REGISTER and comes from a trusted security token, you can call save() with the flag for no-reply and forward to the main registrar (or do it on reply with unregister). I would also lower
the expires for htable item using $shtex(...) with same key (security token) to a few seconds to cope with retransmissions, rather than just deleting it.<o:p></o:p></p>
<p>However, if it expires because the user didn't sent any new registration, then you have to handle that when traffic (INVITE, etc.) comes from main registrar and return 404, 408 or 484. While there are event callbacks for both htable and usrloc records expiration,
triggering a register towards main registrar is useless if main registrar asks for authentication (as it should do in most of the cases), because I understood you want to cover the case when kamailio doesn't know (cannot access) the user password. It would
be a similar case like when the user is suddenly disconnected, before doing unregister (e.g., no more internet access, power off, ...) If kamailio has access to user password, the uac module becomes also an alternative.<o:p></o:p></p>
<p>Cheers,<br>
Daniel<o:p></o:p></p>
<div>
<p class="MsoNormal">On 12.10.20 16:11, David VILLAUME wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hello Daniel,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Thanks for your clear and complete answer knowing I’ts nor part of a module your approach seems totally comprehensible to me .</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">I imagine I can add a second htable with the A-leg expiration interval and a trigger on expire to perform an uac request to unregister on the B-leg.
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Thanks again for all your work and quick answers.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR">Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR">David</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="mso-fareast-language:FR">From:</span></b><span style="mso-fareast-language:FR"> Daniel-Constantin Mierla
<a href="mailto:miconda@gmail.com"><miconda@gmail.com></a> <br>
<b>Sent:</b> Monday, October 12, 2020 3:59 PM<br>
<b>To:</b> David VILLAUME <a href="mailto:david.villaume@sewan.fr"><david.villaume@sewan.fr></a>; Kamailio (SER) - Users Mailing List
<a href="mailto:sr-users@lists.kamailio.org"><sr-users@lists.kamailio.org></a><br>
<b>Subject:</b> Re: [SR-Users] Local cache registration</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p>Hello,<o:p></o:p></p>
<p>if you just want to accept intermediate every 5-min registrations based on source ip and port of a successful registration done every hour, that's quite simple to do in kamailio without any new module, actually not using uac module at all (see next details).
The uac module is more flexible in some aspects, by allowing local subscribers to be mapped to subscribers on a remote server with complete different usernames and passwords, as well as having same username and password towards another sip system on the same
provider, ...<o:p></o:p></p>
<p>Anyhow, back to what I think you are looking for, here is the logic:<o:p></o:p></p>
<p> - when a registration comes, store userid, source ip and port in an avp/xavp (e.g., "$fU/$si/$sp")<o:p></o:p></p>
<p> - update expires to a an higher value as you want (e.g., 3600) and forward the registration to main registrar<o:p></o:p></p>
<p> - if 200ok is received by kamailio, then call save() so contact details are stored in the local database, then adjust back the expires (there are functions in textopsx module that allow you setting header parameters)<o:p></o:p></p>
<p> - store in an htable the userid, source ip and port (these being taken from the xavp/avp created on REGISTER)<o:p></o:p></p>
<p> - when follow up registrations come, check first if "$fU/$si/$sp" is matching any key in htable, if yes, just send 200ok after you add the contact headers from register with append_to_reply(). If no key match in the htable, then do the steps above<o:p></o:p></p>
<p> - htable has to be defined with expires a bit lower than 3600secs (or what is that higher expire value you want), so at some point the item with the key "$fU/$si/$sp" is deleted, forcing you to do the steps 1-4 again<o:p></o:p></p>
<p>As a bonus, if main register supports Path and sends the OPTIONS keepalive, you skip using registrar/usrloc module (so no more save()) and you just play with headers updates (ie., change expires) and storing/checking "security" token "$fU/$si/$sp" in the
htable.<o:p></o:p></p>
<p>Cheers,<br>
Daniel<o:p></o:p></p>
<div>
<p class="MsoNormal">On 12.10.20 15:32, David VILLAUME wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Hello,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">I just try to reproduce what we actually have on Oracle or what is done in opensips mid_registrar module and trust the A leg user as long as it come from the same IP/port couple that have successfully registered.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">I paste the process description of the mechanism described on opensips module page.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">But I can understand your choice to not go that way.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US" style="font-size:13.5pt;mso-fareast-language:FR">Contact throttling</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="mso-fareast-language:FR">In "contact throttling" mode, the mid-registrar can significantly reduce the registration rate on the main registrar side (between
mid-registrar and main registrar), while coping with a high registration rate on the end-user side (between end-user and mid-registrar). This is useful in scenarios were the end-users are very dynamic and short-lived (like on mobile devices), but the main
registrar cannot cope with large traffic. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="mso-fareast-language:FR">Traffic conversion is done in a
<i>"per-device"</i> manner, according to each unique SIP Contact header field value. It is achieved by increasing the "expires" parameter value of each contact, when relaying registrations to the main registrar. Once such a registration is completed, subsequent
registrations for the same SIP Contact header field value will be continuously absorbed by the mid-registrar until, eventually, the lifetime of the remote registration will have decreased enough that a refresh (i.e. simply forwarding the next REGISTER request)
is mandatory. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="mso-fareast-language:FR">A common occurence is for some SIP User Agents to lose their network connection (especially when dealing with mobile devices),
hence they do not properly de-register from the mid-registrar. In this case, in order to avoid stale registrations on the main registrar (which contains SIP contacts with greatly extended lifetimes!), the mid-registrar will appropriately generate De-REGISTER
requests and remove these contacts from the main registrar's location service as soon as it considers them to have expired.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="mso-fareast-language:FR">The main practical use for this mode is registration traffic conversion. By minimizing the strain of processing registrations
on the main registrar, we allow it to dedicate more system resources to critical areas of the platform, such as advanced SIP calling features and/or media handling.
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://opensips.org/html/docs/modules/2.3.x/mid_registrar.html">https://opensips.org/html/docs/modules/2.3.x/mid_registrar.html</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR">Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR">David</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:FR">From:</span></b><span lang="EN-US" style="mso-fareast-language:FR"> Daniel-Constantin Mierla
<a href="mailto:miconda@gmail.com"><miconda@gmail.com></a> <br>
<b>Sent:</b> Monday, October 12, 2020 3:20 PM<br>
<b>To:</b> Kamailio (SER) - Users Mailing List <a href="mailto:sr-users@lists.kamailio.org">
<sr-users@lists.kamailio.org></a>; David VILLAUME <a href="mailto:david.villaume@sewan.fr">
<david.villaume@sewan.fr></a><br>
<b>Subject:</b> Re: [SR-Users] Local cache registration</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p><span lang="EN-US">If you do not have access to credentials on Kamailio, how do you want to authenticate registrations coming every 5min? If you want to reuse the auth headers from the 1-hour based registration, then you create a big security problem, normally
nonce is valid very short time to avoid reply and offline brute force attacks.</span><o:p></o:p></p>
<p><span lang="EN-US">Note that Kamailio can connect to other databases+tables to fetch username and password, it doesn't have to be "subscriber" style. You can customize table name and column names. For example, it can connect to asterisk realtime database
to fetch the password from "secret" column.</span><o:p></o:p></p>
<p><span lang="EN-US">Cheers,<br>
Daniel</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On 12.10.20 15:02, David VILLAUME wrote:</span><o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span lang="EN-US">I read again the uac doc and didn’t find a way to perform this using the functions that seems to require credentials that I don’t have on the kamailio host.</span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US">Is the uac module really designed to perform this operation is that way ?</span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US">Regards,</span><o:p></o:p></pre>
<pre><span lang="EN-US">David</span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US">El Sun, 11 Oct 2020 20:07:58 +0000</span><o:p></o:p></pre>
<pre><span lang="EN-US">David VILLAUME <</span><a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"><span lang="EN-US">david.villaume at sewan.fr</span></a><span lang="EN-US">> escribió:</span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> Hello,</i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> </i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> I try to perform a registration caching in order to have a short interval</i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> registration on phone <> Kamailio (5 minutes) and a longest interval on the</i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> leg Kamailio <> registrar(1h).</i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> </i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> I’m not so sure about the best way to proceed, does one of you have a working</i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> sample or some hints about the way to have it working ?</i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> </i></span><o:p></o:p></pre>
<pre><span lang="EN-US">><i> </i></span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<pre><span lang="EN-US">the uac module does that. You can handle upstream registrations in different</span><o:p></o:p></pre>
<pre><span lang="EN-US">intervals than the ones you receive.</span><o:p></o:p></pre>
<pre><span lang="EN-US"> </span><o:p></o:p></pre>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:FR"><br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<pre><span lang="EN-US">_______________________________________________</span><o:p></o:p></pre>
<pre><span lang="EN-US">Kamailio (SER) - Users Mailing List</span><o:p></o:p></pre>
<pre><a href="mailto:sr-users@lists.kamailio.org"><span lang="EN-US">sr-users@lists.kamailio.org</span></a><o:p></o:p></pre>
<pre><a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"><span lang="EN-US">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</span></a><o:p></o:p></pre>
</blockquote>
<pre><span lang="EN-US">-- </span><o:p></o:p></pre>
<pre><span lang="EN-US">Daniel-Constantin Mierla -- </span><a href="http://www.asipto.com"><span lang="EN-US">www.asipto.com</span></a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/miconda"><span lang="EN-US">www.twitter.com/miconda</span></a><span lang="EN-US"> -- </span><a href="http://www.linkedin.com/in/miconda"><span lang="EN-US">www.linkedin.com/in/miconda</span></a><o:p></o:p></pre>
<pre><span lang="EN-US">Funding: </span><a href="https://www.paypal.me/dcmierla"><span lang="EN-US">https://www.paypal.me/dcmierla</span></a><o:p></o:p></pre>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Daniel-Constantin Mierla -- <a href="http://www.asipto.com">www.asipto.com</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a><o:p></o:p></pre>
<pre>Funding: <a href="https://www.paypal.me/dcmierla">https://www.paypal.me/dcmierla</a><o:p></o:p></pre>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Daniel-Constantin Mierla -- <a href="http://www.asipto.com">www.asipto.com</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a><o:p></o:p></pre>
<pre>Funding: <a href="https://www.paypal.me/dcmierla">https://www.paypal.me/dcmierla</a><o:p></o:p></pre>
</div>
</body>
</html>