I have some questions on this, e.g. on Kamailio:
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?
2. I can also host the source on my own website, with some more helper scripts for building and packaging. That should be better?
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?
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?
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 ?
6. If answer to 5 is yes, I can write my own libclosed-source and sell with whatever license?
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.
Thanks. I don't mean to violate the GPL, just want to be clear and easier to understand the license.
On Wed, Feb 9, 2022 at 9:05 PM Henning Westerholt <
hw@gilawa.com> wrote:
Hello,
(just to add the obvious disclaimer that this is not legal advice, I am not a lawyer).
> [Would it be ok] if it were [using] a standalone service to which Kamailio interfaced using very narrowly confined and general-purpose communication channels?
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.
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.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-----Original Message-----
From: sr-users <sr-users-bounces@lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Wednesday, February 9, 2022 1:50 PM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] SEMS license with kamailio and rtpengine
> On Feb 9, 2022, at 7:46 AM, Henning Westerholt <hw@gilawa.com> wrote:
>
>> If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.”
>
> 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.
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?
— Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--