This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgOn Tue, Sep 29, 2009 at 09:21:41PM +0200, Sylvain Munaut wrote:
> >> It's a pity that there are no free EFR/AMR codec implementation, I
> >> have to use plain old GSM-FR.
> >
> > what do you mean by 'free' ? patent-free: no, certainly not. but free as in
> > 'souce code available': sure, there are!
>
> But I meant 'free' as in I can use/distribute it without having to worry :)
well, if you think that way then you probably should not ever distribute
OpenBSC, as it probably implements dozens of things that are covered by GSM
related patents. This is why we are working on an experimental implementation
for research purpose. As soon as you use that in a commercial context, you will
have to ensure that you have licensed the apropriate patents (GSM Essential IP)
from Siemens and others.
> Yes, having the core running in there is not the most elegant solution :) But
> since all the interaction is done via the MNCC interface, it's probably very
> easy to just export that as a socket. Just need to clean up a little the
> message format (with like type & length field always set properly and such)
> and then only the mncc.h header would be used by external apps ...
yes, though in this case Andreas Eversberg would have to decide on the licensing
of that.
Also, MNCC does not cover everything we might want to expose to applications,
but it is a start.
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)