baseband-devel September 2017

baseband-devel@lists.osmocom.org

8 participants
13 discussions

Start a nNew thread

Engagetted !
by Sébastien Lorquet 14 Oct '25

14 Oct '25

http://www.engadget.com/2010/12/29/researchers-eavesdrop-on-encrypted-gsm-c… Congrats!

7 7

Calypso BTS
by phreaker1983 16 Nov '19

16 Nov '19

I tried to install CalypsoBTS have libosmocore installed, osmo-bts osmobsc, libosmo-netif, libosmo-abis, ortp, trx, libosmo-dsp everything went without errors, following the instructions I created: touch ~/.osmocom/open-bsc.cfg , then when you run : osmo-nitb -c ~/.osmocom/open-bsc.cfg-l ~/.osmocom/hlr.sqlite3-P-C --debug=DRLL:CC:MM:RR:RSL:NM shows me:<0005> bsc_init.c:498 Failed to parse the config file: '/root/.osmocom/open-bsc.cfg' file tried to create as administrator but without success , pleas help me -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Calypso-BTS-tp4026753.html Sent from the baseband-devel mailing list archive at Nabble.com.

6 13

Fwd: OSMOCOM-BB HandOver
by Muhammad Awais Aslam 12 Jan '19

12 Jan '19

Hi, We have been working on the handover feature in OsmocomBB and have managed to make some progress including SB/BSIC detection in dedicated mode which was not previously being successfully done in firmware. I wanted to share it and seek guidance on the last bit of handover implementation on which we are stuck. I hope someone would be able to help us or make use of our work. We took code related to handover from the osmocom-bb jolly branch by manually adding/deleting stuff in the master branch as updating to the latest copy was giving us issues. We added code from the “Safely change TPU offset on TS change or sync change” commit till the “Use only sel_si for information about the current cell” commit. Using the handover code in the jolly branch and after making the changes explained below we were able to obtain the handover command from the BTS. The synchronized handover case works sometimes though still not every time, however the non-synchronized case doesn't work at all as we are not able to get the physical information command from the new cell. I'll explain the changes/additions we made to achieve this. Firstly, we noted that in dedicated mode SB burst was not being detected. Changes were required at three main places in order to correctly perform FB/SB detection: - It was seen that the results for SB were being read from DSP API location dsp_api.db_r->a_sch which is for the idle mode. The results had to be read from the dsp_api.ndb->a_sch26 location for the dedicated case if TCH_SB_DSP_TASK is used. - After reading the FB we needed to update the quarter-bit offset of the TPU using the TOA of the FB to sync it with the start of frame of the neighbour cell in order to catch the SB (by changing the vaule of l1s.tpu_offset using the TOA of the FB). - Frequency compensation needed to be performed using the afc_correct function before reading the SB. * We actually kind of cheated a bit by adding 3 frames to the original idle frame in order to give us more time to perform FB/SB detection including the synchronizations mentioned above. This was because we weren't that proficient with the code and someone with more understanding could do this better. The call did not get dropped. We used the initial added “idle” frame to perform the quarter-bit and frequency compensation which was reversed in the idle frame with the response function to tune back to the serving cell. These things, when added to the code did the trick and BSIC of the neighbours was obtained. Once the BSICs were decoded the measurement report sent to the BTS became meaningful and the handover command was received. Upon receiving handover command, access bursts needed to be sent on the new channel which again was not currently being implemented properly as in order to tune to the new cell we needed to know its quarter-bit offset for start of frame, frequency compensation and absolute frame number which were not previously being obtained. Now that we were able to detect FB and SB these values were stored for the neighbours following detection of these bursts and were used to tune to a neighbour cell in case of a handover to it before the sending of access bursts. However, here is where we are stuck. We were expecting a physical information message following the access bursts but were not able to receive it due to which the handover failed. If only that could be achieved we believe handover should be successful. Either we are not syncing properly to the new cell or we might not be following GSM protocol properly. We also might not be reading the FACCH properly for physical information message after tuning to the new cell as we couldn't really understand that bit very well. We wanted someone expertise on this matter and were hoping our work could be of use. We were more interested in getting the work done first up. Best Regards, M. Awais Aslam

3 3

OpenBTS OsmocomBB Asterisk
by trixbox.t 14 Jul '18

14 Jul '18

Hello! I Need Help I install these three programs OpenBTS, OsmocomBB, Asterisk Then run them, Everything works well OpenBTS sent an SMS to my phones I answered and he checked me I registered into OpenBTS a second phone I tried to transfer SMS between phones - all good but when I try to call from one to another I did not get Asterisk writes ================================================================ *CLI> Retransmission timeout reached on transmission 755803415(a)127.0.0.1 for seqno 179 (Critical Response) -- See wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32001ms with no response ================================================================ Why? What do I do? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp402… Sent from the baseband-devel mailing list archive at Nabble.com.

6 14

GAPK status update
by Vadim Yanitskiy 03 Dec '17

03 Dec '17

Dear Osmocom community, I have been working on GAPK (GSM Audio Packet Knife) for some time, and now I would like to share some achievements. Previously GAPK was represented as a single binary that could be called with some command line arguments in order to perform required operations. This is only handy for humans, but not for other programs, which may also need to perform some format / codec conversations or audio capture / playback. One of such programs is the mobile from OsmocomBB project. Currently, when you're making a voice call, both audio capture and playback are only possible on the L1 side, i.e. on a Calypso based phone. Of course, the audio stream can be redirected via MNCC socket, but this is not what a regular OsmocomBB user would like to do. Moreover, there is a lack of AMR codec support. Also, there is another GNURadio based project named GR-GSM. In short, this is a set of blocks for GSM signal reception, demodulation and further processing. At the moment, one has TCH Full Rate decoding capabilities only. Audio playback is not supported yet. Having these projects in my mind, I have got an idea of creating a shared library from the GAPK source code. And, a few days ago I was managed to get the audio playback working in OsmocomBB. I hope, this library will be also usable for other projects. Brief list of changes were made: - Composed a shared library named libosmogapk - All exposed symbols have got an 'osmo_gapk' prefix - Added a pkg-config manifest and a symbol export map - Integrated the Osmocom logging framework - Benchmarking is now disabled by default - Processing queue now based on the linuxlist - Fixed program exit due to ALSA buffer underrun - Fixed ALSA audio playback from file - Old gapk application was renamed to 'osmo-gapk' and linked against the library - Adjusted verbosity level (normal / debug) - Fixed I/O combinations (ALSA, RTP, file...) check All changes could be found at the fixeria/lib branch of GAPK. I hope to see them merged, and open for discussions ;) With best regards, Vadim Yanitskiy.

2 4

Re: OpenBSC and OsmocomBB
by Vadim Yanitskiy 11 Sep '17

11 Sep '17

Hi, Probably, the problem is related to https://osmocom.org/issues/1458 In short, a phone is unable to sync a strong BTS due to the ADC input overload. As a quick solution, you can use the 'stick ARFCN' option in 'mobile.cfg'. This helped me when a phone was pretty close to my BTS. With best regards, Vadim Yanitskiy.

2 1

OpenBSC and OsmocomBB
by Testphone Test 11 Sep '17

11 Sep '17

Dear List I am trying to run osmocomBB with motorola c118 with openbsc.I tried to get openbsc network on my phone it works well and I am able to register on openbsc network. But when i try to run osmocomBB with openBSC i am not able to get network. Also when i run rssi firmware on c118 phone i get network and its working fine. I am using default configuration file for OpenBSC and using NanoBTS with 1800Mhz support. Is there any configuration change is needed in openBSC ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

help me osmocomBB
by Олег Суворов 10 Sep '17

10 Sep '17

Can you help me? -------- Пересылаемое сообщение -------- От кого: Олег Суворов <olegtsss(a)mail.ru> Кому: baseband-devel <baseband-devel(a)lists.osmocom.org> Дата: Пятница, 1 сентября 2017, 18:28 +06:00 Тема: help me Hello, I am from Russia, can you help me with Filter Replacement! I have to mobile, Motorolla C115 and C118. I was bye all elements to make filter replacement. Motorolla C115 look like your instruction and I was done filter replacement. Motorolla C115 nice work after it. But Motorolla C118 don`t look like in your instruction. I read: "Different circuit Sometimes the input (at the bottom of the balun) is not with caps in series and a resistor in parallel. Instead it might be without the resistors in parallel and resistors in series. Remove the resistors and place 2x the appropriate cap in series (22 pF for GSM90, 15 pF for DCS1800". But I don`t understand what I must do. I do like my picture (С118_2.jpg), but after it Motorolla don`t work: No signal from Network. Can you help me? With Best Regards, Oleg Syvorov ---------------------------------------------------------------------- ----------------------------------------------------------------------

1 0

Osmocombb on Ubuntu 16.04
by ty 07 Sep '17

07 Sep '17

Hi. My name is tyrus and I have been working with OsmocomBB since 2014 but had given it a break. I decided to go back to the project only that this time I am running a machine on Ubuntu 16.04 LTS. I get the following error during the make stage of the installation: libmobile.a(gsm48_rr.o): In function `gsm48_rr_enc_cm3': */home/tyrus/osmocom-bb/src/host/layer23/src/mobile/gsm48_rr.c:1210: undefined reference to `bitvec_fill'* *libmobile.a(vty_interface.o): In function `cfg_ms_rename':* */home/tyrus/osmocom-bb/src/host/layer23/src/mobile/vty_interface.c:1283: undefined reference to `osmo_talloc_replace_string'* collect2: error: ld returned 1 exit status Makefile:377: recipe for target 'mobile' failed make[3]: *** [mobile] Error 1 make[3]: Leaving directory '/home/tyrus/osmocom-bb/src/host/layer23/src/mobile' Makefile:322: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/tyrus/osmocom-bb/src/host/layer23/src' Makefile:348: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/tyrus/osmocom-bb/src/host/layer23' Makefile:84: recipe for target 'host/layer23/layer23' failed make: *** [host/layer23/layer23] Error 2 Anyone else experienced this? I have *gcc-arm-none-eabi* toolchain installed Much appreciated. -ty

5 10

Re: SDR_PHY question
by Vadim Yanitskiy 07 Sep '17

07 Sep '17

Hi, > I believe I need to keep focusing on osmo-trx support > as the gr-gsm app does not seem to support TX (please > correct me if I'm wrong though). You are right, currently it doesn't. But we together with Piotr Krysik are working on TX support for GR-GSM... > I will keep investigating this and I will provide you > some patches for osmo-trx which enable power > measurement and synchronization. Great! Having both OsmoTRX and GR-GSM TRX support would be good. I am currently busy with TCH implementation for trxcon, so as soon as I finish, I'll put my development power on this too. With best regards, Vadim Yanitskiy.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel September 2017