9 Feb
2022
9 Feb
'22
8:02 a.m.
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.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Wednesday, February 9, 2022 1:50 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] SEMS license with kamailio and rtpengine
On Feb 9, 2022, at 7:46 AM, Henning Westerholt
<hw(a)gilawa.com> wrote:
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(a)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
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.