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.orghi Max,
On Mon, Apr 15, 2013 at 06:35:23PM +0200, ☎ wrote:
> Could you advice me where to read more about MNCC protocol?
it is not a protocol, but an interface
> openbsc/openbsc/include/openbsc/mncc.h references ETSI TS 100 940 which indeed has a
> lot of variables like MNCC.RECALL.IND in call control diagrams - but where are the
> reference to actual protocol?
there is no protocol. The Spec only defines a set of primitives and
possibly their parameters, but no encoding or no protocol. This is
fairly standard for ETSI/3GPP specs that document internal interfaces
between layers of functional elements where no wire-protocol or vendor
inter-operability is required.
--
- 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)