OpenBSC June 2023

openbsc@lists.osmocom.org

4 participants
22 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

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

08 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

libosmocore/BSC/MSC: MO voice calls rejected from Siemens S11E (patch included)
by Lennart Müller 01 Feb '24

01 Feb '24

Hi, I had a problem placing MO GSM calls from a Siemens S11E: The calls were dropped immediately; Osmo-MSC reports "Cannot compose Channel Type from bearer capabilities" After investigating the SETUP request from the S11E, the phone does not use octet 3a (no extension bit set in IE 3). Wireshark decodes the radio channel requirement as "Full rate support only MS/fullrate speech version 1 supported", so I added a condition to the gsm48_ie.c function of libosmocore to include at least GSM FR in the list of available speech_ver in case octet 3 has no extension. Attached to this message are the Abis-IP PCAP traces of MO calls, and the patch for gsm48_ie.c. Regards, Lennart

6 6

Problem while running NIB on Open Cellular Base sation
by Brackley Casinga 31 Jan '24

31 Jan '24

Hi, My name is Brackley Cassinga Form DRC, we run a community network called pamoja net where we offer gsm services using osmocom open source software and OC Base station. Recently I have tried to install another base station as the same installed but I could not find any resource guiding through all the steps to take to run NIB on a base station. I'm currently running Ubuntu and I will appreciate if you could guide me on the installation of BSC,hlr,MSC , in order to run a basic gsm network. Thank you. Regards -- *Ir Brackley heshima Casinga **Pacifique* *CEO and Founder of kwanzatechnologie* KwanzaTechnologies ,GlobalElectronics +243977265291 | +243977265291 | Pcassinga(a)gmail.com/ brackley(a)ensemblepourladifference.org www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> | Skype: Brackley cassinga <https://webapp.wisestamp.com/#> Av Semliki N 43

2 1

code review
by Neels Hofmeyr 04 Jul '23

04 Jul '23

Hi community, I feel a bit frustrated by how code review is going recently at osmocom. Let me compare two larger feature branches: There are weeks of review on 19 patches in osmo-hnbgw/cnpool, and <24h from submit to merge on 14 patches in osmo-msc. That may in some situations be ok and justified, but I feel that it is not: The cnpool patch series for osmo-hnbgw spawned huge discussions and long delays on account of minor issues: log lines, event names and comments. I said so, yet it droned on and even spawned offspring. None of the important features was part of code review: larger design choices of the API, efficiency in handling the actual signalling, correctness of the signalling. Maybe that's because all those were mint perfect and no bugs anywhere, but I doubt that I'm really that good =) And at the same time I was "just now" asked to review some patches for osmo-msc, which changes an API that I have recently added and had ideas and reasons for. Before I get a chance to even glance, I see that all the patches are already merged! It is now basically too late to bring in my feedback, because the patches are in, and why spend more time on it. Suck it up, bygones. This very API that was being changed in osmo-msc in under 24 hours was itself under code review scrutiny for at least three years. Also I have (in my own free time) tried to get an improved logging timestamp into libosmocore. This is tagging along for years and years now, because every time over it is being blocked by minor details that are matters of taste. For years I lose precious moments every time i have to read an 'extended-timestamp' in osmo logging and identify the boundary of hours, minutes and seconds. This I consider important. AFAIR the reasons for blocking the patches were, objectively, all not important. These examples are starkly unbalanced. I'm sure you're aware of the bikeshed phenomenon -- it is a precise description of what is happening. It would be great if we could turn that around a bit? http://www.catb.org/jargon/html/B/bikeshedding.html Let's say, I know from experience that it is hard to give good code review, so count me in on this advice. Let's still give all the code review we can, but let's keep in mind the actual impact the particular code change has. If it goes in the "fringe detail" bucket, let's mention it, but just let it pass if the author disagrees. Hope you understand my frustration and maybe even agree. Thanks, ~N

2 2

Nokia Site (Ultra, Metro)
by Sipos Csaba 30 Jun '23

30 Jun '23

Hi Neels, I checked RF and BB hopping with my MetroSite with my patch added, and they both seem to work, multi-TRX was tested a couple days ago, that also works with 2 TRXes. Obviously I did not tested every possible hopping scenarios, but in both cases the node manager reported the correct hopping states and I also checked with a spectrum analyzer. This means that either my UltraSite still has some issues, or that the config logic for it needs a bit of tuning. The one difference I have noticed is that the MetroSite does starts the RSL LAPD when the TRXes reach a configured state, while the UltraSite needs the BSC to start the RSL LAPD links even after the TRXes reach the same configured state. FYI, I am running exactly the same BTS SW release on both units (latest LTS ever released by the vendor), so they should not behave differently from a pure SW point of view. Anyway, at this point in time I don't see any particular issues that indicates a BSC problem. One feature missing is the ability to configure sectors (Nokia calls a sector a "BTS" while the base station is called "BCF"). My question is, do we have any BTS type that has sector configuration support so I can take a look how this was done (if any) ? Regards, Csaba

3 4

BSC to multiple external MSCs
by Varoon Greedharry 22 Jun '23

22 Jun '23

Hello, I know it's quite a dummy question (Beginner) but I'm actually trying the BSC to two external MSCs but the attempt failed. As per the doc, I did configure the cs7 instance. Is there an example configuration file which I could go through. -- Best Regards, Varoon

2 2

Re: OpenBSC Digest, Vol 104, Issue 1
by Sipos Csaba 21 Jun '23

21 Jun '23

Hi Neels, Sorry for the late response. As there is still a slight chance that the issue on my side is HW related, I digged out my old MetroSite with 4 TRX as that is a little bit smaller and easier to move compared to the Ultra cabinet :-) So I will conduct some tests with it in the next couple days. Lets say the issue is the same: what exactly do you need from me to maybe look into it? I assume E1 pcap and logs. If you have a specific log mask, or you need something else, please let me know. Regards, Csaba

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC June 2023