<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">“Kamailio - the leading non-sip and sip server"<div class=""><br class=""></div><div class="">Naahhh. Doesn’t work.</div><div class=""><br class=""></div><div class="">/Kamailio Marketing Dept. ;-)<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 19 Dec 2018, at 13:31, Carsten Bock <<a href="mailto:carsten@ng-voice.com" class="">carsten@ng-voice.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">given the fact, that we do a lot of "non-sip" related stuff with Kamailio (we are using Kamailio as a Diameter HSS, Diameter Charging-Server (OCS), Diameter Routing-Agent (DRA)), I would also vote for number (2):</div><div class=""><br class=""></div><div class=""><span style="color:rgb(80,0,80)" class="">> 2) remove the function export from the core and export one with the same</span><br class=""></div><div class=""><span style="color:rgb(80,0,80)" class="">> name from the corex module</span></div><div class=""><font color="#500050" class=""><br class=""></font></div><div class=""><font color="#500050" class="">Thanks,</font></div><div class=""><font color="#500050" class="">Carsten<br clear="all" class=""></font><div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">--<br class=""><br class="">Carsten Bock<br class="">CEO (Geschäftsführer)<br class=""><br class="">ng-voice GmbH<br class="">Millerntorplatz 1<br class="">20359 Hamburg / Germany<br class=""><br class=""><a href="http://www.ng-voice.com/" target="_blank" class="">http://www.ng-voice.com</a><br class="">mailto:<a href="mailto:carsten@ng-voice.com" target="_blank" class="">carsten@ng-voice.com</a><br class=""><br class="">Office +49 40 5247593-40<br class="">Fax +49 40 5247593-99<br class=""><br class="">Sitz der Gesellschaft: Hamburg<br class="">Registergericht: Amtsgericht Hamburg, HRB 120189<br class="">Geschäftsführer: Carsten Bock<br class="">Ust-ID: DE279344284<br class=""><br class="">Hier finden Sie unsere handelsrechtlichen Pflichtangaben:<br class=""><a href="http://www.ng-voice.com/imprint/" target="_blank" class="">http://www.ng-voice.com/imprint/</a></div></div><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">Am Mi., 19. Dez. 2018 um 12:55 Uhr schrieb YAS0 CANER <<a href="mailto:caner_yaso@hotmail.com" class="">caner_yaso@hotmail.com</a>>:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div style="font-family: EmojiFont, Calibri, Helvetica, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 12pt;" class="">
TmEXIT , kEXIT and corEXIT is failed <span class="">😊</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
</div>
<hr style="display:inline-block;width:98%" class="">
<div id="gmail-m_3511166570168917619divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size:11pt" class=""><b class="">From:</b> sr-users <<a href="mailto:sr-users-bounces@lists.kamailio.org" target="_blank" class="">sr-users-bounces@lists.kamailio.org</a>> on behalf of Olle E. Johansson <<a href="mailto:oej@edvina.net" target="_blank" class="">oej@edvina.net</a>><br class="">
<b class="">Sent:</b> Wednesday, December 19, 2018 2:38 PM<br class="">
<b class="">To:</b> Daniel-Constantin Mierla<br class="">
<b class="">Cc:</b> Kamailio (SER) - Development Mailing List; Kamailio (SER) - Users Mailing List<br class="">
<b class="">Subject:</b> Re: [SR-Users] [sr-dev] RFC: updates to some core functions</font>
<div class=""> </div>
</div>
<div class="gmail-m_3511166570168917619BodyFragment"><font size="2" class=""><span style="font-size:11pt" class="">
<div class="gmail-m_3511166570168917619PlainText"><br class="">
<br class="">
> On 19 Dec 2018, at 12:26, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank" class="">miconda@gmail.com</a>> wrote:<br class="">
> <br class="">
> <br class="">
> On 19.12.18 09:47, Olle E. Johansson wrote:<br class="">
>> <br class="">
>>> On 19 Dec 2018, at 09:41, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank" class="">miconda@gmail.com</a>> wrote:<br class="">
>>> <br class="">
>>> corex module was added to hold the functions that otherwise would be<br class="">
>>> more or less "in the core", like those that were updated to support<br class="">
>>> variables in the parameters, so this is the one to take the place of<br class="">
>>> core in regard to exporting functions.<br class="">
>>> <br class="">
>>> tmx was added because tm module became very big, but also to try to<br class="">
>>> separate a bit between transaction management code and some functions in<br class="">
>>> top of it, in the way that tmx can work only with exported api by tm, so<br class="">
>>> if one adds a function there doesn't get access to all internals of<br class="">
>>> transaction and it is safer not to mess up things there. It is more or<br class="">
>>> less like usrloc and registrar, usrloc does internal management of<br class="">
>>> location records, registrar is the interface to configuration file (but<br class="">
>>> there are other modules on top of usrloc, like pua_usrloc, dmq_usrloc, ...).<br class="">
>>> <br class="">
>>> kex is the one that collected some functions that use to be in kamailio<br class="">
>>> (or better said openser at that time) but not in ser during 2005-2008<br class="">
>>> and can be a module that be analyzed to see if can be merged into other<br class="">
>>> modules. A big chunk of it used to be related to MI commands, but as we<br class="">
>>> got rid of MI, might be easier now to split parts of it and relocate.<br class="">
>>> <br class="">
>> Ok, so removing kex is a good first step for the coming release.<br class="">
>> <br class="">
>> It’s really hard explaining TMX and TM for new Kamailians.<br class="">
> <br class="">
> We can add a note at the top of docs for each of these modules to refer<br class="">
> to the other.<br class="">
> <br class="">
> On the other hand, I do not like to have a huge module. It is not<br class="">
> suitable for small embedded systems. Also, there are other modules using<br class="">
> the tm api, so it is a common approach. The tmx is exporting mostly<br class="">
> functions at higher level of transaction interaction, one can build a<br class="">
> transaction stateful sip routing without it, only using tm.<br class="">
> <br class="">
Damn it. My campaign for exit of the x modules just died. Sad story.<br class="">
<br class="">
Thanks for all the responses!<br class="">
<br class="">
/O<br class="">
> Cheers,<br class="">
> Daniel<br class="">
> <br class="">
>> <br class="">
>> /O :-)<br class="">
>> <br class="">
>>> Cheers,<br class="">
>>> Daniel<br class="">
>>> <br class="">
>>> On 19.12.18 09:25, Olle E. Johansson wrote:<br class="">
>>>> Going back one step, are there any reasons to keep tmx, kex and corex modules at all?<br class="">
>>>> <br class="">
>>>> At this point in the project I think many of the functions should be merged into
<br class="">
>>>> the main modules and core. <br class="">
>>>> <br class="">
>>>> If I remember correctly, they exist because of a multi-brand history that is not<br class="">
>>>> really the case any more.<br class="">
>>>> <br class="">
>>>> /O<br class="">
>>>> “The campaign to remove Kamailio extensions to Kamailio”<br class="">
>>>> <br class="">
>>>> <br class="">
>>>>> On 19 Dec 2018, at 09:11, Henning Westerholt <<a href="mailto:hw@kamailio.org" target="_blank" class="">hw@kamailio.org</a>> wrote:<br class="">
>>>>> <br class="">
>>>>> Am Mittwoch, 19. Dezember 2018, 09:03:26 CET schrieb Sergey Safarov:<br class="">
>>>>>> I prefer second way. Without any duplication.<br class="">
>>>>>> For old configs branches 4.4, 5.0, 5.1 is always available.<br class="">
>>>>> Hello,<br class="">
>>>>> <br class="">
>>>>> I would prefer also the second way, for the same reason: less duplicated <br class="">
>>>>> functions.<br class="">
>>>>> <br class="">
>>>>> Best regards,<br class="">
>>>>> <br class="">
>>>>> Henning<br class="">
>>>>> <br class="">
>>>>> <br class="">
>>>>>> ср, 19 дек. 2018 г. в 10:50, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank" class="">miconda@gmail.com</a>>:<br class="">
>>>>>>> Hello,<br class="">
>>>>>>> <br class="">
>>>>>>> it was brought into discussions several times in the past about core<br class="">
>>>>>>> functions not accepting variables in the parameters. I think it is time<br class="">
>>>>>>> to update them during the 5.3 release development. For few of them, I<br class="">
>>>>>>> added in the past some alternative function in the corex module (e.g.,<br class="">
>>>>>>> force_send_socket() in core and set_send_socket() in corex module).<br class="">
>>>>>>> <br class="">
>>>>>>> So, I see two options:<br class="">
>>>>>>> <br class="">
>>>>>>> 1) add a function with similar name in corex module and same behaviour<br class="">
>>>>>>> like the one from core<br class="">
>>>>>>> <br class="">
>>>>>>> 2) remove the function export from the core and export one with the same<br class="">
>>>>>>> name from the corex module<br class="">
>>>>>>> <br class="">
>>>>>>> First one will ensure that configs using the functions right now keep<br class="">
>>>>>>> working without any update.<br class="">
>>>>>>> <br class="">
>>>>>>> The second one will be better in long term from the point of<br class="">
>>>>>>> documentation (no duplicated docs), but there might be few cases that<br class="">
>>>>>>> would require updates in the config -- iirc, there are some functions<br class="">
>>>>>>> that can get special tokens in the parameters (like forward(uri:host,<br class="">
>>>>>>> uri:port)), they will get an equivalent with variables, but old config<br class="">
>>>>>>> will not be compatible.<br class="">
>>>>>>> <br class="">
>>>>>>> Obviously the reason for this email is to ask the developers and users<br class="">
>>>>>>> what would be the preferred way from own point of view.<br class="">
>>>>>>> <br class="">
>>>>>>> Cheers,<br class="">
>>>>>>> Daniel<br class="">
>>>>> -- <br class="">
>>>>> Henning Westerholt - <a href="https://skalatan.de/blog/" target="_blank" class="">https://skalatan.de/blog/</a><br class="">
>>>>> Kamailio services - <a href="https://skalatan.de/services" target="_blank" class="">https://skalatan.de/services</a><br class="">
>>>>> Kamailio security assessment - <a href="https://skalatan.de/de/assessment" target="_blank" class="">
https://skalatan.de/de/assessment</a><br class="">
>>>>> <br class="">
>>>>> _______________________________________________<br class="">
>>>>> Kamailio (SER) - Development Mailing List<br class="">
>>>>> <a href="mailto:sr-dev@lists.kamailio.org" target="_blank" class="">sr-dev@lists.kamailio.org</a><br class="">
>>>>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br class="">
>>>> _______________________________________________<br class="">
>>>> Kamailio (SER) - Development Mailing List<br class="">
>>>> <a href="mailto:sr-dev@lists.kamailio.org" target="_blank" class="">sr-dev@lists.kamailio.org</a><br class="">
>>>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br class="">
>>> -- <br class="">
>>> Daniel-Constantin Mierla -- <a href="http://www.asipto.com/" target="_blank" class="">www.asipto.com</a><br class="">
>>> <a href="http://www.twitter.com/miconda" target="_blank" class="">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank" class="">
www.linkedin.com/in/miconda</a><br class="">
>>> Kamailio World Conference - May 6-8, 2019 -- <a href="http://www.kamailioworld.com/" target="_blank" class="">
www.kamailioworld.com</a><br class="">
>>> Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA --
<a href="http://www.asipto.com/" target="_blank" class="">www.asipto.com</a><br class="">
>>> <br class="">
> -- <br class="">
> Daniel-Constantin Mierla -- <a href="http://www.asipto.com/" target="_blank" class="">www.asipto.com</a><br class="">
> <a href="http://www.twitter.com/miconda" target="_blank" class="">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank" class="">
www.linkedin.com/in/miconda</a><br class="">
> Kamailio World Conference - May 6-8, 2019 -- <a href="http://www.kamailioworld.com/" target="_blank" class="">
www.kamailioworld.com</a><br class="">
> Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA --
<a href="http://www.asipto.com/" target="_blank" class="">www.asipto.com</a><br class="">
> <br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Kamailio (SER) - Users Mailing List<br class="">
<a href="mailto:sr-users@lists.kamailio.org" target="_blank" class="">sr-users@lists.kamailio.org</a><br class="">
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br class="">
</div>
</span></font></div>
</div>
_______________________________________________<br class="">
Kamailio (SER) - Users Mailing List<br class="">
<a href="mailto:sr-users@lists.kamailio.org" target="_blank" class="">sr-users@lists.kamailio.org</a><br class="">
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br class="">
</blockquote></div>
_______________________________________________<br class="">Kamailio (SER) - Development Mailing List<br class=""><a href="mailto:sr-dev@lists.kamailio.org" class="">sr-dev@lists.kamailio.org</a><br class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev<br class=""></div></blockquote></div><br class=""></div></body></html>