[SR-Users] SEMS license with kamailio and rtpengine

[Alex Balashov]

> On Feb 9, 2022, at 7:34 AM, Henning Westerholt <hw at gilawa.com> wrote:
> 
> have a look to the FAQ link I quoted earlier, they give some examples there.

Well, they do hint at some of the considerations…

1) "We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged).”

2) "If the modules are included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.”

3) "By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.”

But this doesn’t seem conclusive in the case of Kamailio, at least to my mind. How does “run together in a shared address space” apply to a core that intentionally loads specific symbols from ELF modules (i.e. via dlsym() & friends) vs. dynamic linking at compile time? Or is that firmly established?

The only real definitive answer seems to be: 

"What constitutes combining two parts into one program? This is a legal question, which ultimately judges will decide.”

:-)

— 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/