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/.
Nordin Bouchtaoui bouchtaoui at gmail.comSorry Harald, Should read the info on the wiki better. And also the debugging output reveals some info. Anyway thanks. 2009/7/29 Harald Welte <laforge at gnumonks.org> > On Wed, Jul 29, 2009 at 05:31:03PM +0200, Nordin wrote: > > Hello Harald, > > > > Should the plugin you added for Wireshark decode almost all messages > > or not? Cause on the OML layer a lot of OML messages are not > > decoded, is this behaviour normal? > > there is a oml decoder plugin, I've posted it to this list, it is in our > git > tree and it is mentioned in the wiki, so it should be pretty easy to find. > > > I now try to follow the communication flow, but can't seem to > > understand the multiple OML messages. It starts with 0x00, than a > > datalen and than protocol (0xFF) and than it starts with 0x80, > > 0x80,.... But I can't find 0x80 (messagetype) in OpenBSC source. > > I've checked ipaccess.h and ipaccess.c, but nothing...maybe I lokked > > at the wrong place. > > oml is implemented in abis_nm.c > > -- > - 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) > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20090729/52bc537c/attachment.htm>