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 at gmail.comHi Holger, Thnx for your offer, there is nothing to look at it than just an initialization process on the OML layer. It decodes some OML messages but not all, the RSL messages are decoded well I think, can't completely confirm that. For me it's important to follow the procedure of the nanobts up and running before handling RSL messages. Harald posted me some traces for scanning neighbouring cells, which I think is important to fill the BA List. But according to Harald these were ip.access specific messages, so how am I suppose to interpret that? I mean which bytes indicates a neighbouring cell, or how am I suppose to understand the meaning of certain bytes i.e. dBm level of a certain neigbouring cell and which ARFCN? It's like reading a piece of Frenche text without having a dictionarry (well, I understand a little bit french :-) ). I don't know how you, Harald and others interpretted the messages during reverse-engineering. Cause I assume you don't have any technical documents about ip.access specific messages, except the GSM specs and some own experience? Kind regards, Nordin. -------------- next part -------------- A non-text attachment was scrubbed... Name: abis2.pcap Type: application/octet-stream Size: 21147 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20090730/65ff43b2/attachment.obj>