Possibility to use INET socket for external MNCC

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.org
Mon Mar 31 14:54:13 UTC 2014


On Fri, Mar 21, 2014 at 04:09:03PM +0100, Luca Valtulina wrote:
> wouldn't be useful to have the possibility to choose (at least) between
> UNIX and INET socket to be used for connecting to an external MNCC?

There are several problems with this:

1) the MNCC interface carries both voice and signalling.  For signalling
   you would like something that resembles TCP/SCTP/DCCP, but for the
   voice you would only like UDP semantics.  Choosing either a reliable
   protocol for voice frames or an unrealiable protocol for signalling
   is calling for lots of trouble and will not happen.  So it would have
   to  be multiple sockets.

2) I don't think the current protocol is endian/alignment safe.  By
   runnign it over a unix domain socket we basically enforce that both
   programs on the MNCC side will run on the same architectuer and not
   cause any problems.  If you run it over a network, making that
   assumption is false.

So yes, it could be possible to run MNCC over IP/INET sockets, but it
would require considerable effort of addressing the issues described
above.  Will you be working on implementing this?

Regards,
	Harald

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




More information about the OpenBSC mailing list