OpenBSC, nanoBTS and Asterisk integration

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

Sylvain Munaut 246tnt at gmail.com
Tue Sep 29 19:21:41 UTC 2009


>> 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!

Yes, there is the openmoko & android (using opencore) too. But I meant
'free' as in I can use/distribute it without having to worry :)
Here I'm not sure it would be accepted to be merged into asterisk ...

> As I indicated
> before, I really don't like the 'daemon in library' approach that we're using
> right now, where the entire OpenBSC 'daemon' runs inside a library that is
> linked to some other executable.
>
> I suppose at some point we actually want to offer some kind of IPC based API
> for external programs, where OpenBSC runs in one process and the other
> application in another.  Once that happens, I might consider licensing the
> library on the other side of the IPC under a different license.

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 ...

    Sylvain




More information about the OpenBSC mailing list