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.comHi! Working fine thanks. But there is something I don't understand : the source is always the user and the destination always the network. I would like to ask another question. I can see on which time slot the burst is sent but i can't see the frame and the multiframe number. Is it available somewhere? Thanks Eric 2009/7/22 Andreas.Eversberg <Andreas.Eversberg at versatel.de> > > can you comment on the status of mISDNdebugtool? As it seems, Eric is > having > > some problems using it. Also, in current mISDNuser.git (socket > branch), > > it doesn't compile since mISDNdebugtool.h is missing. > > hi, > > sorry for the late answer. > > i don't exactly know what this was for. i think it was used to debug the > driver itself. to actually log frames from isdn interface and write a > pcap file you need misdn_log. > > for logging first card use "misdn_log" or "misdn_log -c0". for writing > pcap file use "misdn_log -c0 -w <file>" > this connects to given isdn interface and shows transmitted data also. > it must be started AFTER the application or it will set the mode to > TE-mode. so first run bsc_hack, then start misdn_log. > > andreas > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20090723/ba0dd550/attachment.htm>