baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

Start a nNew thread

Hide extension..
by MArc Richter 30 Dec '11

30 Dec '11

Hey! So is it possibel to to hide the sender extension with SMS ? regards Marc

4 5

Quick Recap of running the 28C3 network
by Holger Hans Peter Freyther 29 Dec '11

29 Dec '11

Hi all, just a quick review of things we saw/learned during the congress * OsmocomBB LAPDm and nanoBTS LAPDm appear to have some communication issues leading to timeouts (nanoBTS resends a message with N(R) not incremented as a response to our I frame with Identity Response (or timeout) but with the old data). We don't have a fix/clear understanding of this yet... looks a bit like a bug in the nanoBTS firmware (but then other phones appear to work just fine) * CHANNEL ACTIVATION NACK on a TS. No idea why (maybe we closed a channel with our auto-timer but the nanoBTS thinks it is open). IIRC the nanoBTS sends us a report about open channels, we should cross-check every n-th report with our view of the channels... on top of that we should block failed channels (configurable, still to do). * Open channels... E.g. with a nanoBTS reboot or "drop bts connection ", there was a bug in libosmo-abis that the e1inp_event was not sent as the link was already taken out of the list of sign links when close is called (fixed in libosmo-abis and sharing code between rsl.c and ipaccess.c) * one OML NACK drops all BTS.. The code is there to deal with a crashed BTS to not have it connected in a bad state... (fixed in zecke/28c3) * subscriber queue, thanks to jolly's SMS setup we increased the amount of SMS and there still appear to be paths in the code that do not properly release the transaction/subscr_put and the queue got stuck. We should start by merging jolly's sms rework.. and see how we can move the queue out of process... * Local End Release for SAPI > 0 should be done in the channel release code, we need to implement T3109... thanks to jolly reading GSM 08.58/04.08 with me and discussing the normal/abnormal case. I have some work in progress (only tested the success case) patches in the zecke/28c3 branch. * I uploaded our scripts but somehow the core dumping does not work correctly (core_pattern appears to be right though) for running the network * Purging subscribers from the VLR, we do it too aggressively (on failed paging), it should take the periodic updating timer into account. * Sometimes i miss dates.. e.g. when was the channel opened probably some more things I forgot now, would be a great opportunity if someone gives a hand in cleaning things up. holger PS: jenkins will be back in january, ZFS crashed, the secret key was on the ZFS, grep didn't find the backup script...

1 0

Re: baseband-devel Digest, Vol 23, Issue 24
by Andres Berroa 20 Dec '11

20 Dec '11

Yes, the SIM works on other phones, even on the same phone with the original firmware, so I suspect it's a driver problem. On Tue, Dec 20, 2011 at 7:00 AM, <baseband-devel-request(a)lists.osmocom.org>wrote: > Send baseband-devel mailing list submissions to > baseband-devel(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/baseband-devel > or, via email, send a message with subject or body 'help' to > baseband-devel-request(a)lists.osmocom.org > > You can reach the person managing the list at > baseband-devel-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of baseband-devel digest..." > > Today's Topics: > > 1. Re: Fwd: SIM_JOB_RUN_GSM_ALGO fails (Sebastien Lorquet) > > > ---------- Forwarded message ---------- > From: Sebastien Lorquet <sebastien(a)lorquet.fr> > To: baseband-devel(a)lists.osmocom.org > Cc: > Date: Mon, 19 Dec 2011 17:01:53 +0100 > Subject: Re: Fwd: SIM_JOB_RUN_GSM_ALGO fails > Hi, > > SW1SW2 = 0000 let me think that the command was not actually sent to the > card, or the card was mute, or the error is very low level. > > is the failing sim OK in a real phone? > > Regards, > Sebastien > > PS: A very minor point, I don't know how the debug function is supposed to > work, but the "data=" field is not the data, but the whole command. > > Le 19/12/2011 16:36, Ethan Brown a écrit : > > Hello, > > The command SIM_JOB_RUN_GSM_ALGO fails on one of my sim cards. Here is > the log from mobile app: > > <0005> gsm48_mm.c:1637 AUTHENTICATION REQUEST (seq > 0) > > <0005> subscriber.c:957 Generating KEY at > SIM > > <000f> sim.c:209 got new job: SIM_JOB_RUN_GSM_ALGO > (handle=00000006) > > <000f> sim.c:539 RUN GSM > ALGORITHM > > <000f> sim.c:187 sending APDU (class 0xa0, ins 0x88, data=a0 88 00 00 10 > 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 01 93 ) > <000f> sim.c:877 received APDU (len=0 sw1=0x00 > sw2=0x00) > > <000f> sim.c:953 command > failed > > <000f> sim.c:151 sending result to callback function > (type=1) > > <0005> subscriber.c:991 key generation on SIM failed (cause 2) > > > And this is the log from L1: > > SIM Request (21): a0 88 00 00 10 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 > 01 93 > Triggering SIM transmission Character underflow!Triggering SIM reception > Max characters received!SIM: ACK does not match request, response[0]=60, > sim_data[1]=88 > SIM Response (2): 00 00 > > > The SIM I used for that test is somewhat different than other SIMs I have > tested and worked before. I attached a picture of two SIMs I used. The > green SIM is the one that fails running SIM_JOB_RUN_GSM_ALGO. The white > one works perfectly. > > > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > >

2 1

Fwd: SIM_JOB_RUN_GSM_ALGO fails
by Ethan Brown 19 Dec '11

19 Dec '11

Hello, The command SIM_JOB_RUN_GSM_ALGO fails on one of my sim cards. Here is the log from mobile app: <0005> gsm48_mm.c:1637 AUTHENTICATION REQUEST (seq 0) <0005> subscriber.c:957 Generating KEY at SIM <000f> sim.c:209 got new job: SIM_JOB_RUN_GSM_ALGO (handle=00000006) <000f> sim.c:539 RUN GSM ALGORITHM <000f> sim.c:187 sending APDU (class 0xa0, ins 0x88, data=a0 88 00 00 10 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 01 93 ) <000f> sim.c:877 received APDU (len=0 sw1=0x00 sw2=0x00) <000f> sim.c:953 command failed <000f> sim.c:151 sending result to callback function (type=1) <0005> subscriber.c:991 key generation on SIM failed (cause 2) And this is the log from L1: SIM Request (21): a0 88 00 00 10 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 01 93 Triggering SIM transmission Character underflow!Triggering SIM reception Max characters received!SIM: ACK does not match request, response[0]=60, sim_data[1]=88 SIM Response (2): 00 00 The SIM I used for that test is somewhat different than other SIMs I have tested and worked before. I attached a picture of two SIMs I used. The green SIM is the one that fails running SIM_JOB_RUN_GSM_ALGO. The white one works perfectly.

2 1

Re: burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

the tables from your conv_tch_afs.c I thought, that I need them to get the voice. ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

Re: burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

...ASF-Tables for the different channel codec modes ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 2

Re: burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

>It should work for the SACCH and SACCH but will _not_ decode the FACCH You mean the counter should work for SACH and FACCH? I know...other channels are decoded differently. Thats why I am asking. I am trying to implement FACH and hopefully ASF. I used your tch_h_1 mframe task to grab the tch. Best regards, Tobias ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

is the burst couter in app_cch_scans local_burst_decode() bid = -1; ... if (bid == -1) return; also working for tch? Im asking, because "if (bid == -1)" is not triggered correctly with my tch samples. Regards, Tobias ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

Please report all known bugs/issues to trac!
by Harald Welte 16 Dec '11

16 Dec '11

Hi all! I would like to ask everyone to report known issues with OsmocomBB to the trac at http://bb.osmocom.org/trac/newticket I think there is a lot of knowledge already somwewhere in the project, but it's not readily available. Especially as there is some movement towards creating an actual usable phone, it would be great to have a collection of all known problems in the existing code. Don't worry too much if you don't know the correct component to which to attach the report, we will figure that out. If you don't have a wiki account for bb.osmocom.org, just send me a mail and I will create it. Thanks for your cooperation! -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RFC: Osmocom developer workshop 2012
by Harald Welte 14 Dec '11

14 Dec '11

<DISCLAIMER> Please follow-up to openbsc(a)lists.osmocom.org </DISCLAIMER> Hi all, this idea has been around for quite some time, and for 2012 I really want to turn it into reality: I'd like to have a Osmocom developer workshop The idea here is to get all the active contributors of the project together for a couple of days (maybe 2-4 days), in order to exchange ideas, get to know each other better and last but not least work together on ironing out some of the more difficult issues. * City: Regarding the location: I think for me it is only possible to organize it if it is to be held in Berlin. I'mn happy if somebody else wants to host it at some other location, but then that person would also have to take care of local organization. Berlin also has good train and flight connections, which is definitely a plus. * Venue: If it is in Berlin, we might consider talking with c-base or Raumfahrtagentur as possible venues. * Date: Regarding a proposed date, I'm completely open for suggestions. Of course there shouldn't be any overlap with other major FOSS or Sescurity related conferences, and it should also not coincide with major public holidays, as that only makes travel + accomodation more expensive. * Funding: As we don't have that many commercial users of Osmocom projects, getting funding for e.g. travel / accomodation is probably going to be difficult. We can ask the "usual suspects" among those commercial users we know,, but I guess it will only be possible in exceptional cases to provide that kind of funding. Any ideas / comments / feedback is much appreciated. If somebody has a particular suggestion. <DISCLAIMER> Please follow-up to openbsc(a)lists.osmocom.org </DISCLAIMER> Cheers, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel