baseband-devel November 2020

baseband-devel@lists.osmocom.org

5 participants
6 discussions

Start a nNew thread

Engagetted !

by Sébastien Lorquet

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

6 months, 1 week

"Bad signalling message, sign_link returned error: Operation not permitted" - during voice call

by Mario Lucas

Dear team, I did set up GSM network with SDR (LimeSDRmini). SMS are ok. However when try to make voice call got following message on osmo-bsc terminal: <0003> abis_rsl.c:1372 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x41, neci=0x01, chreq_reason=0x02) <0007> osmo_bsc_sigtran.c:305 Initializing resources for new SIGTRAN connection to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:351 Opening new SIGTRAN connection (id=31) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0003> abis_rsl.c:1372 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9b, neci=0x01, chreq_reason=0x01) <0007> osmo_bsc_sigtran.c:305 Initializing resources for new SIGTRAN connection to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:351 Opening new SIGTRAN connection (id=32) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0004> abis_nm.c:344 BTS 0 reported connected PCU version 0.8.0 <0016> input/ipaccess.c:411 Bad signalling message, sign_link returned error: Operation not permitted. <0016> input/ipaccess.c:411 Bad signalling message, sign_link returned error: Operation not permitted. WHat is this bad signalling message operation not permitted? -- Mario Lucas

3 years, 4 months

Osmocom C files syntax understanding

by Mario Lucas

Dear baseband-developers team, Would you be so kind to advise me on the following: I desire (dramatically want very much) to learn / understand Osmocom projects. I am a beginner in programming and i try to understand / learn C files that the project is build of. As an example i tried to learn / understand for example an Osmocom message buffer — msgb.h file. But immediately faced some syntax difficulties: This is the extract of msgb.h file: struct msgb { struct llist_head list; /*!< \brief linked list header */ /* Part of which TRX logical channel we were received / transmitted */ /* FIXME: move them into the control buffer */ union { void *dst; /*!< \brief reference of origin/destination */ struct gsm_bts_trx *trx; }; As it can be seen a structure «msgb» has as one of its components another structure — «gsm_bts_trx» But in whole Osmocom BB project files i could not find definition / description of struct «gsm_bts_trx». Would you kindly advise me please how to see which components / constituents / elements are in this gsm_bts_trx structure? From which components is struct gsm_bts_trx build of? Thank you so much for your kind advise. -- Mario Lucas

3 years, 5 months

Dropped packets by HW.... Dumping Stale bursts

by Mario Lucas

Dear all, I am using LimeSDRmini to run osmo-bts… During operation from time-to time (and sometimes quite frequently) following messages pop-up in terminal: «Dropped packets by HW!» and «Dumping Stale bursts...» I guess my LimeSDRmini is dropping some packets. LimeSDRmini configuration is: Firmware 6, Hardware 3, Protocol1, Gateware 1.3. Would you advise — may be there is more or less stable firmware version that to some extent is stable while working with Osmo-bts ? Thanks -- Mario Lucas

3 years, 5 months

PCU socket not connected, dropping message

by Mario Lucas

Dear baseband developers team, I built home gsm network with Osmo-stp-msc-hlr-bsc-bts, osmo-trx limeSDR. I managed and registered phones. I did send sms between each other. However when i decided to make a call — i noticed following message in terminal: «PCU socket not connected, dropping message». I searched on Osmocom web site and it is said that pcu socket is involved in GPRS things (i.e. in internet). Therefore why does such message appears when i try to make simple call between two mobiles — it has nothing to do with GPRS… And what would you advise me how to resolve this ? P.S. initially when i was about to start osmo-bts-trx i got message «PCU L1 socket failed» and i just renamed the pcu_bts file to some other name and osmo-bts-trx started. Thank you so much for your kind reply. Best regards -- Mario Lucas

3 years, 5 months

fixeria trx.highram.bin stuck

by Mario Lucas

Dear all, Pls help me with the following issue: I want to run a transceiver having motorola c115… i follow the procedure described in CalypsoBTS page : http://osmocom.org/projects/baseband/wiki/CalypsoBTS without chainloader i get: /home/ubuntu# /home/ubuntu/trx/src/host/osmocon/./osmocon -m c123xor -p /dev/ttyUSB0 /home/ubuntu/trx/src/target/firmware/board/compal_e88/trx.highram.bin got 7 bytes from modem, data looks like: 66 74 6d 74 6f 6f 6c ftmtool Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: c1 . got 1 bytes from modem, data looks like: 66 f and with chainloader i get: /home/ubuntu# /home/ubuntu/trx/src/host/osmocon/./osmocon -m c123xor -p /dev/ttyUSB0 -c /home/ubuntu/trx/src/target/firmware/board/compal_e88/trx.highram.bin got 2 bytes from modem, data looks like: 04 81 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(chainloader): file_size=32, hdr_len=4, dnload_len=39 got 1 bytes from modem, data looks like: 00 . it seems with chainloader it is trying to do more but still stuck…. pls help…. Mario -- Mario Lucas

3 years, 5 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel November 2020