OpenBSC May 2024

openbsc@lists.osmocom.org

11 participants
14 discussions

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 22 Jul '25

22 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

cmd2 update causing pySim-shell to fail
by bryan coxwell 24 Jun '25

24 Jun '25

Hi all, Just wanted to share an issue and a quick workaround I found for it in case anyone else has the same problem. I believe a cmd2 update is causing pySim-shell to fail. After installing it on a fresh install of Ubuntu Server 20.04 and getting the following error when I run "python3 pySim-shell -p0": >Using PC/SC reader interface >Autodetected card type: sysmoUSIM-SJS1 >AIDs on card: > USIM: a0000000871002ffffffff8907090000 >Traceback (most recent call last): > File "pySim-shell.py", line 512, in <module> > app = PysimApp(card, rs, opts.script) > File "pySim-shell.py", line 59, in __init__ > super().__init__(persistent_history_file='~/.pysim_shell_history', allow_cli_args=False, use_ipython=True, auto_load_commands=False, command_sets=basic_commands, >startup_script=script) >TypeError: __init__() got an unexpected keyword argument 'use_ipython' If you run into this you can fix it by uninstalling cmd2 and reinstalling cmd2 with "pip3 install cmd2==1.5". Best, Bryan

5 5

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

E1 to IP with iCE40 E1 USB interface
by Alina Androne 15 Jun '24

15 Jun '24

Hello, How can I utilize the iCE40 E1 USB adapter to transition from E1 to IP in a GSM network, connecting a physical Siemens BSC (which has a BTS connected) to OsmoMSC? Only the BTS and BSC are physical. I already have osmo-e1d installed. Should I use osmo-e1d or dahdi version for this transition? What would be the best approach to begin the process? Regards, Alina

5 10

osmo-smlc / sccp_lb_inst.c
by jheyrendt.ext＠orange.com 05 Jun '24

05 Jun '24

Hi Do you know if the packet osmo-smlc should work with osmo-bsc, osmo-stp last versions? I just tested, saw errors and tried to debug but perhaps I made mistakes (link, as, asp are up between BSC and SMLC via osmo-stp) osmo-smlc 0.2.4 DLSCCP DEBUG <0011> sccp_user.c:176 Delivering N-PCSTATE.indication to SCCP User 'SCCP Management' DLSCCP DEBUG <0011> sccp_scmg.c:298 Ignoring SCCP user primitive N-PCSTATE.indication DLSCCP DEBUG <0011> sccp_user.c:176 Delivering N-PCSTATE.indication to SCCP User 'OsmoSMLC-Lb' DLB ERROR <0002> sccp_lb_inst.c:167 (Lb) sccp_lb_sap_up(N-PCSTATE.indication) unsupported Many thanks in advance Best regards Jean-Marc

2 3

Re: New Defects reported by Coverity Scan for Osmocom
by Neels Hofmeyr 29 May '24

29 May '24

For the record, below DEADCODE warnings are "false" positives -- technically correct, but due to the VTY_NEWLINE macro: #define VTY_NEWLINE ((vty->type == VTY_TERM) ? "\r\n" : "\n") > 906 if (vty->type == VTY_TERM) > >>> CID 368762: Control flow issues (DEADCODE) > >>> Execution cannot reach the expression ""\n"" inside this statement: "vty_out(vty, "%% WARNING: n...". > 907 vty_out(vty, "%% WARNING: nft configuration changes need a restart of osmo-hnbgw%s", VTY_NEWLINE); On Tue, May 28, 2024 at 11:00:54PM +0000, scan-admin(a)coverity.com wrote: > Hi, > > Please find the latest report on new defect(s) introduced to Osmocom found with Coverity Scan. > > 2 new defect(s) introduced to Osmocom found with Coverity Scan. > > > New defect(s) Reported-by: Coverity Scan > Showing 2 of 2 defect(s) > > > ** CID 368762: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 907 in cfg_hnbgw_no_nft_kpi() > > > ________________________________________________________________________________________________________ > *** CID 368762: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 907 in cfg_hnbgw_no_nft_kpi() > 901 > 902 DEFUN(cfg_hnbgw_no_nft_kpi, cfg_hnbgw_no_nft_kpi_cmd, > 903 "no nft-kpi", > 904 NO_STR NFT_KPI_STR) > 905 { > 906 if (vty->type == VTY_TERM) > >>> CID 368762: Control flow issues (DEADCODE) > >>> Execution cannot reach the expression ""\n"" inside this statement: "vty_out(vty, "%% WARNING: n...". > 907 vty_out(vty, "%% WARNING: nft configuration changes need a restart of osmo-hnbgw%s", VTY_NEWLINE); > 908 g_hnbgw->config.nft_kpi.enable = false; > 909 return CMD_SUCCESS; > 910 } > 911 > 912 #if ENABLE_PFCP > > ** CID 368761: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 894 in cfg_hnbgw_nft_kpi() > > > ________________________________________________________________________________________________________ > *** CID 368761: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 894 in cfg_hnbgw_nft_kpi() > 888 { > 889 const char *set_table_name = NULL; > 890 if (argc > 0) > 891 set_table_name = argv[0]; > 892 > 893 if (vty->type == VTY_TERM) > >>> CID 368761: Control flow issues (DEADCODE) > >>> Execution cannot reach the expression ""\n"" inside this statement: "vty_out(vty, "%% WARNING: n...". > 894 vty_out(vty, "%% WARNING: nft configuration changes need a restart of osmo-hnbgw%s", VTY_NEWLINE); > 895 > 896 g_hnbgw->config.nft_kpi.enable = true; > 897 osmo_talloc_replace_string(g_hnbgw, &g_hnbgw->config.nft_kpi.table_name, set_table_name); > 898 > 899 return CMD_SUCCESS; > > > ________________________________________________________________________________________________________ > To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2… > > To manage Coverity Scan email notifications for "nhofmeyr(a)sysmocom.de", click https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2… > -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

Developing GSMTAP version 3
by Shinjo Park 20 May '24

20 May '24

Hi all, After the OsmoDevCon 2024, I have set up a repository containing the GSMTAPv3 WIP version: https://gitea.osmocom.org/peremen/gsmtapv3 There is a Redmine ticket for GSMTAPv3: https://osmocom.org/issues/6445 Currently only the global header structure and types/subtypes are defined, and detailed explanation of what each data type stands for is still WIP. Also, GSMTAPv3 will use T16L16V dynamic metadata instead of fixed metadata structure, and the metadata definition is still in early stage. Having a structure definition is the very begging, which will be followed by additional works to actually use the new GSMTAPv3 format (APIs, Wireshark dissector, ...). Any form of help will be much appreciated. Best, Shinjo

4 7

Question about connecting OSMO-MSC to MME from Open5Gs
by Hennig, Lilly 18 May '24

18 May '24

Hello everybody, I was trying to setup an OSMO-MSC with an Open5Gs-Corenetwork, so I can send SMS to different UEs. Unfortunately the OSMO-MSC does not connect to the MME of the Open5Gs-Core and I do not find any installation guide for this specific setup. For your information: The Open5Gs-Core runs on a Laptop and I build the Software from source (4G and 5G components). The MSC should run on the same Laptop. Therefore I would like to ask you, if you can tell me, which other components besides of the OSMO-MSC I possibly have to install and how I should configure this components and the components of the core. Many thanks in advance! Best regards Lilly Hennig

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC May 2024