OpenBSC October 2024

openbsc@lists.osmocom.org

1 participants
16 discussions

ip.access nano 3G S8 Configuration
by John Thewlis - Meath Broadband 18 Nov '25

18 Nov '25

We are trying to setup this AP as part of the 3.5G Osmocom project. We have the software stack operational and are now preparing the nano for testing. When we try to login via telnet at port 8090 we are getting a constant refusal to connect:- root@osm/openbsc/openbsc/src/ipaccess# telnet 192.168.192.30 8090 Trying 192.168.192.30... telnet: Unable to connect to remote host: Connection refused The device seems to be locked as indicated by the leds on the front panel. We have tried resetting the nano to see if this would help but to no avail. Any ideas as to how to access the device for initial configuration?. Thanks John

4 4

Pysim error: SW match failed
by Martin Nagy 16 Aug '25

16 Aug '25

Hi all, After buying a super Sim Kit (16 in 1) from China, I tried the reader (green PCB inside a blue transparent plastic case with a blue LED) and SIM (identified as a fakesupersim) with pysim tool. However i am getting the following error: /pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z 1234 -j 1 -t auto Insert card now (or CTRL-C to cancel) Autodetected card type fakemagicsim Generated card parameters : > Name : 26C3 > SMSP : e1ffffffffffffffffffffffff058100945555ffffffffffff000000 > ICCID : 8949262427518313026 > MCC/MNC : 262/42 > IMSI : 262422461512085 > Ki : 7b74741a1ee14337ec23f9ab92a13648 > OPC : ccd867d60797d8d45354a51b3ef568ff Programming ... Traceback (most recent call last): File "./pySim-prog.py", line 530, in <module> card.program(cp) File "/home/nadicek/pysim/pysim/pySim/cards.py", line 231, in program self._scc.update_binary('6f30', hplmn + 'ff' * (tl-3)) File "/home/nadicek/pysim/pysim/pySim/commands.py", line 53, in update_binary return self._tp.send_apdu_checksw(pdu) File "/home/nadicek/pysim/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1])) RuntimeError: SW match failed ! Expected 9000 and got 9804. I checked mailing lists and haven’t found anybody who had similar problem with pysim. Also I have tried forcing different models of SIM, but nothing is working. Obviously I can remove this check from the script file (__init__.py in /pySim/transport), however somebody had a reason to put such condition there. I would like to ask if it is safe to remove that line of code and the purpose of that line of code. Thanks a lot and best regards Martin

3 3

pycrate repo update
by benoit michau 21 Jul '25

21 Jul '25

Dear osmocom developpers, This is just to let you know that the Python library pycrate has a new home : https://github.com/pycrate-org/pycrate. The packages on Pypi are now feeded from there. This library can be used in many cases dealing with mobile signalling. I wanted to let you know, as even if I am not aware of any osmocom projects depending on it, some of you may use the library from time to time, or could have local applications depending on it. Best Regards Benoit

2 1

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

dynamic traffic channels
by Neels Hofmeyr 20 May '25

20 May '25

On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote: > [translated from german] > is it certain that we switch a channel to PDCH only when > gprs mode != none? A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we send a PDCH ACT message. We send a PDCH ACT message - during init (CHANNEL OML's state changed to enabled -> send PDCH ACT), - and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH. So the question is, when we receive a channel release ack, could that be the PDCH release and we switch PDCH right back on by accident? No, because we only receive a chan rel ack when the *TCH/F* is being released. That is because the PDCH release is initiated "internally" from the PDCH DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches on, which existed before dyn PDCH: if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) { LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n", gsm_lchan_name(lchan)); return 0; } In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but not in the rsl_rx_dyn_pdch(). This is analogous to the ip.access way -- the ip.access nanobts replies to a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel release ack. Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH for clarity? (But we shouldn't actually send a release ack, to stay compatible.) Even though it works as-is, we should indeed add another flag check: - We do check the flags that no ACT/DEACT is already pending; - And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE; - But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE. This should never happen, but it would make sense to ensure that. ~Neels

3 5

BladeRF or LimeSDR for running osmo-bts-trx
by Mychaela Falconia 28 Oct '24

28 Oct '24

Hello Osmocom community, (Cc'ing Eric per instructions from Harald) I am looking to acquire an SDR device for the purpose of running osmo-bts-trx. My initial goal is to get to the bottom of some mysteries observed in OS#6579; because it is CSD, getting a non-virtual test setup requires an SDR-based BTS rather than the otherwise wonderful sysmoBTS. And of course there will likely be other fixes and improvements that can be made in osmo-bts-trx. :) Harald recommended that I get a BladeRF 2.0 xA4 for this purpose, plus a Leo Bodnar GPSDO. However, before I commit to buying that hw with an aggregate cost of around $800, I wanted to get some community input to make sure it is the right choice for the job at hand. (There is also the possibility that Sysmocom will sponsor this hw for me, which is wonderful - but still, I don't want to waste money even if it's someone else's!) Harald told me that Eric has worked on BladeRF, and instructed me to ask both Eric and the wider community. My basic question is: how stable and reliable is this BladeRF 2.0 in the BTS application? I presume I will need to run osmo-trx-bladerf, but I find it alarming that there is absolutely no documentation for this variant: the wiki and the user manual cover osmo-trx-uhd and osmo-trx-lms, but not one mention of BladeRF. It is my understanding that BladeRF always runs on 38.4 MHz clock; if the external clock frequency is some other, the PLL inside BladeRF will discipline the local 38.4 MHz VCXO to "follow" the external reference, but the SDR will still run at 38.4 MHz. Thus I see no way to avoid fractional resampling, i.e., configuring the external GPSDO to put out 26 MHz or 52 MHz won't do anything to eliminate that fractional resampling need. Hence the question: does this fractional resampling constitute a real problem, or is it a sufficiently minor defect such that one can live with it in a lab environment? Will there be any gotchas to be aware of, such as MS struggling to connect to the test network? Finally, how does this BladeRF compare to various LimeSDR options? It seems like LimeSDR has always been the popular choice in the "cheap" department, whereas for BladeRF I see not one mention anywhere as I already noted. How do these two options compare? I recall hearing that while LimeSDR was once very popular, people were also having problems with it. Is BladeRF now better in terms of stability, or not really? And if BladeRF really is a better choice than LimeSDR for the purpose of running an SDR BTS on something cheaper than Ettus hw, then how did we get into the peculiar situation of having documentation that covers LimeSDR but not BladeRF? Please help this SDR-ignorant gal figure out which hardware I should buy. Whether I cover the cost on my own or take up Harald's offer of cost reimbursement, either way I need to be sure I buy the right thing... Oh, one more detail: whichever USB-interfaced SDR I get, I plan on using a Raspberry Pi 5 to drive it, running stock Raspbian. Does anyone have any experience with using RPi devices to drive SDRs for use as BTS? Is RPi5 powerful enough to run all of the computationally demanding parts, including that fractional resampling? Is stock Raspbian good enough in terms of sw dependencies? TIA, Mychaela

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC October 2024