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/.
Eric Cathelinaud e.cathelinaud at googlemail.comHello, I give you a screenshot in attached file. May be Andreas know why. This screenshot shows a terminated call procedure. We should have : BTS --> BSC : CHANNEL REQUIRED BSC --> BTS : CHANNEL ACTIVATION BTS --> BSC : CHANNEL ACTIVATION ACK BSC --> BTS : IMMEDIATE ASSIGNMENT COMMAND and so on And on the misdn log we only have : BTS --> BSC : CHANNEL REQUIRED BTS --> BSC : CHANNEL ACTIVATION ACK and so on I can't see any message from BSC to BTS. But I can see : "S, func=RR, N(R)=23" from LAPD format I didn't find what it is exactly. Thanks Eric Cathelinaud 2009/7/28 Harald Welte <laforge at gnumonks.org> > On Tue, Jul 28, 2009 at 12:34:59AM +0200, Eric Cathelinaud wrote: > > Hi, > > > > I still have one question about the log. We can see only messages going > from > > BTS to BSC but not the ones in the other way. Why? > > I would give you answers if I had them. As I indicated before on this > list, > I'm almost constantly travelling and rarely have access to a BS-11, so I > cannot test/verify any of your findings. I did some casual checking of > misdn_log last time, and it _seemed_ to work fine. > -- > - 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/20090728/2efd29cc/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: misdnLog.png Type: image/png Size: 133932 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20090728/2efd29cc/attachment.png>