<div dir="ltr"><div>I have some questions on this, e.g. on Kamailio:</div><div><br></div><div>1. The core and some modules is GPL. I packaged that without change, and sell to a customer. and when the customer asks for source, I told him to download from the kamailio website, since I didn't change anything. Is that correct?</div><div><br></div><div>2. I can also host the source on my own website, with some more helper scripts for building and packaging. That should be better?</div><div><br></div><div>3. I write a new module, 100% code wrote from scratch, just follow the module guidelines or example code to expose/add hooks to core, dynamically loaded into kamailio. Do I need to use GPL or can it be any license or even closed source? can I sell the standalone module in binary?</div><div><br></div><div>4. my module still should be GPL since I have to call GPL code in kamailio source, e.g. string functions in core. or maybe it's ok if string functions in kamailio core is BSD?</div><div><br></div><div>5. If my module link to a 3rd party lib (e.g. libclosed-source.so or libclosed-source.a I think there's no difference?) which is not open source (but free to sell), can I sell it w/o the source of libclosed-source ?</div><div><br></div><div>6. If answer to 5 is yes, I can write my own libclosed-source and sell with whatever license?</div><div><br></div><div>7. Regards to KEMI, if I write routing scripts with Lua (compiled with luac) and sell to a customer, should I open source the Lua code? The Lua code calls Kamailio core functions which might be GPL.</div><div><br></div><div>Thanks. I don't mean to violate the GPL, just want to be clear and easier to understand the license.</div><div><br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 9, 2022 at 9:05 PM Henning Westerholt <<a href="mailto:hw@gilawa.com">hw@gilawa.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
(just to add the obvious disclaimer that this is not legal advice, I am not a lawyer).<br>
<br>
> [Would it be ok] if it were [using] a standalone service to which Kamailio interfaced using very narrowly confined and general-purpose communication channels?<br>
<br>
I do not think there is a problem regarding to the GPL in this case. Interfacing over SIP/HTTP/RPC/XMLRPC or other standard mechanism to a dedicated process would not establish a close coupling between Kamailio and the other code.<br>
<br></blockquote><div><br></div><div>I think it's correct. e.g. if you use evapi or http to talk to your service you don't have to open source your service code.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Cheers,<br>
<br>
Henning<br>
<br>
-- <br>
Henning Westerholt – <a href="https://skalatan.de/blog/" rel="noreferrer" target="_blank">https://skalatan.de/blog/</a><br>
Kamailio services – <a href="https://gilawa.com" rel="noreferrer" target="_blank">https://gilawa.com</a><br>
<br>
-----Original Message-----<br>
From: sr-users <<a href="mailto:sr-users-bounces@lists.kamailio.org" target="_blank">sr-users-bounces@lists.kamailio.org</a>> On Behalf Of Alex Balashov<br>
Sent: Wednesday, February 9, 2022 1:50 PM<br>
To: Kamailio (SER) - Users Mailing List <<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] SEMS license with kamailio and rtpengine<br>
<br>
<br>
> On Feb 9, 2022, at 7:46 AM, Henning Westerholt <<a href="mailto:hw@gilawa.com" target="_blank">hw@gilawa.com</a>> wrote:<br>
> <br>
>> If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.”<br>
> <br>
> This is exactly what applies to Kamailio due to the core and module architecture. The core and modules also share common data structures and memory segments.<br>
<br>
I see. So, practically, the only way a custom module could be considered meaningfully separate according to these criteria is if it were a standalone service to which Kamailio interfaced using very narrowly confined and general-purpose communication channels?<br>
<br>
— Alex<br>
<br>
-- <br>
Alex Balashov | Principal | Evariste Systems LLC<br>
<br>
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)<br>
Web: <a href="http://www.evaristesys.com/" rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" rel="noreferrer" target="_blank">http://www.csrpswitch.com/</a><br>
<br>
<br>
__________________________________________________________<br>
Kamailio - Users Mailing List - Non Commercial Discussions<br>
* <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Important: keep the mailing list in the recipients, do not reply only to the sender!<br>
Edit mailing list options or unsubscribe:<br>
* <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
__________________________________________________________<br>
Kamailio - Users Mailing List - Non Commercial Discussions<br>
* <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Important: keep the mailing list in the recipients, do not reply only to the sender!<br>
Edit mailing list options or unsubscribe:<br>
* <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">About: <a href="http://about.me/dujinfang" target="_blank">http://about.me/dujinfang</a><br>Blog: <a href="http://www.dujinfang.com" target="_blank">http://www.dujinfang.com</a><br>Proj: <a href="http://www.freeswitch.org.cn" target="_blank">http://www.freeswitch.org.cn</a></div></div>