OpenBSC November 2024

openbsc@lists.osmocom.org

6 participants
13 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

ip config for osmobts and osmo trx
by Masumeh Sadat Tohidi 24 Nov '24

24 Nov '24

I have installed osmo-bts-trx and osmo-trx-uhd on one machine (IP: 192.168.75.174), and on another machine, I installed osmo-bsc, osmo-msc, and osmo-hlr (IP: 192.168.75.185). How should I set the IP addresses in their configuration files? in osmo-bts-trx: osmotrx ip local ? osmotrx ip remote ? oml remote-ip ? in osmo-trx-uhd bind-ip ? remote-ip ? Also in bsc what config should be change?

2 1

connect osmo-BTS-trx to any other commercial Network
by Masumeh Sadat Tohidi 24 Nov '24

24 Nov '24

Hi. Is It possible to connect osmo-BTS-trx to any other commercial BSC or MSC?

2 1

error on sgs connection
by Masumeh Sadat Tohidi 21 Nov '24

21 Nov '24

Hello. I have installed open5gs v2.6.6 on ubuntu 22.04 (192.168.75.181) with kamailio and volte config as in https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/. It work well. I have installed osmo on 192.168.75.185 and also it work well and call establised. but when I add sgs config in mme, It show this info: [mme] INFO: sgsap client() [192.168.75.185]:29118 (../src/mme/sgsap-sctp.c:55) [mme] INFO: VLR-SGs[192.168.75.185] connection refused!!! (../src/mme/mme-sm.c:717) In osmo-msc.cfg i add: sgs local-port 29118 local-ip 192.168.75.185 vlr-name vlr.msc001.mnc001.mcc001.3gppnetwork.org end and in mme.yaml: sgsap: addr: 192.168.75.185 map: tai: plmn_id: mcc: 001 mnc: 01 tac: 1 lai: plmn_id: mcc: 001 mnc: 01 lac: 1 @ mme.txt <https://github.com/user-attachments/files/17811895/mme.txt> This is the log when run osmomsc smo-msc -c /etc/osmocom/osmo-msc.cfg DMNCC NOTICE MNCC socket at /tmp/msc_mncc (mncc_sock.c:300) DLGLOBAL NOTICE Available via telnet 127.0.0.1 4254 (telnet_interface.c:88) DSMPP NOTICE SMPP at 0.0.0.0 2775 (smpp_smsc.c:989) DLCTRL NOTICE CTRL at 127.0.0.1 4255 (control_if.c:1024) DLGSUP NOTICE GSUP connecting to 127.0.0.1:4222 (gsup_client.c:74) DDB NOTICE Init database connection to 'sms.db' using SQLite3 lib version 3.37.2 (db.c:521) DLMGCP NOTICE MGW(mgw) MGCP client: using endpoint domain '@mgw <https://github.com/mgw>' (mgcp_client.c:932) DMSC NOTICE MGW pool with 1 pool members configured, (ignoring MGW configuration in VTY node 'msc'). (msc_main.c:596) DLSCCP NOTICE OsmoMSC-A-Iu: Using SS7 instance 0, pc:0.23.1 (sccp_user.c:566) DLSCCP NOTICE OsmoMSC-A-Iu: Creating AS instance (sccp_user.c:573) DLSCCP NOTICE OsmoMSC-A-Iu: Using AS instance as-clnt-OsmoMSC-A-Iu (sccp_user.c:584) DLSCCP NOTICE OsmoMSC-A-Iu: Creating default route (sccp_user.c:590) DLSCCP NOTICE OsmoMSC-A-Iu: No unassociated ASP for m3ua, creating new ASP asp-clnt-OsmoMSC-A-Iu (sccp_user.c:629) DLGLOBAL ERROR Trying to dispatch event 17 to non-existent FSM instance! (osmo_ss7_as.c:118) DLGLOBAL ERROR backtrace() returned 9 addresses (backtrace.c:42) DLGLOBAL ERROR /lib/x86_64-linux-gnu/libosmocore.so.22(_osmo_fsm_inst_dispatch+0x486) [0x7f4b057e68d6] (backtrace.c:53) DLGLOBAL ERROR /lib/x86_64-linux-gnu/libosmo-sigtran.so.10(osmo_ss7_as_add_asp+0x15b) [0x7f4b055596ab] (backtrace.c:53) DLGLOBAL ERROR /lib/x86_64-linux-gnu/libosmo-sigtran.so.10(osmo_sccp_simple_client_on_ss7_id+0x97b) [0x7f4b0557381b] (backtrace.c:53) DLGLOBAL ERROR osmo-msc(+0x185ca) [0x55b74b7575ca] (backtrace.c:53) DLGLOBAL ERROR osmo-msc(+0x1780a) [0x55b74b75680a] (backtrace.c:53) DLGLOBAL ERROR /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f4b05167d90] (backtrace.c:53) DLGLOBAL ERROR /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f4b05167e40] (backtrace.c:53) DLGLOBAL ERROR osmo-msc(+0x181c5) [0x55b74b7571c5] (backtrace.c:53) DLSCCP NOTICE OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu (sccp_user.c:699) DLSS7 NOTICE 0: Creating SCCP instance (osmo_ss7.c:408) DSGS NOTICE SGs socket bound to r=NULL<->l=192.168.75.185:29118 (sgs_server.c:186) DMSC NOTICE A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no PC),SSN=BSSAP, cs7-instance 0 ((null)) (msc_main.c:806) DMSC NOTICE Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no PC),SSN=RANAP, cs7-instance 0 ((null)) (msc_main.c:826) DLINP NOTICE 127.0.0.1:4222 connection done (ipa.c:143) DLINP NOTICE received ID_GET for unit ID 0/0/0 (ipaccess.c:897) DLM3UA NOTICE 0: asp-asp-clnt-OsmoMSC-A-Iu: Received NOTIFY Type State Change:AS Inactive () (m3ua.c:622) DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoMSC-A-Iu)[0x55b74ca95a20]{ACTIVE}: Ignoring primitive M-ASP_ACTIVE.confirm (xua_default_lm_fsm.c:400) DLM3UA NOTICE 0: asp-asp-clnt-OsmoMSC-A-Iu: Received NOTIFY Type State Change:AS Active () (m3ua.c:622) DSGS NOTICE r=192.168.75.181:51999<->l=192.168.75.185:29118: Connection lost (sgs_server.c:101) DSGS NOTICE r=192.168.75.181:37170<->l=192.168.75.185:29118: Connection lost (sgs_server.c:101) DSGS NOTICE r=192.168.75.181:42624<->l=192.168.75.185:29118: Connection lost (sgs_server.c:101) DSGS NOTICE r=192.168.75.181:40043<->l=192.168.75.185:29118: Connection lost (sgs_server.c:101) DSGS NOTICE r=192.168.75.181:51479<->l=192.168.75.185:29118: Connection lost (sgs_server.c:101)

2 1

eSIM for private networks
by Sipos Csaba 13 Nov '24

13 Nov '24

Dear Harald, I watched your excellent presentation on eSIMs and I have two questions just to make sure I understand the situation correctly. 1. Both the eSIM profile and the SM-DP+ server's certificate has to be signed by the GSMA in order to be able to provide eSIM services to commercial handsets? 2. If the above is the case, that means we effectively lost control of the SIM infra, as we always have to rely on 3rd party SM-DP+ and eSIM profile providers who can provide the necessary signing for both the eSIM profiles and the SM-DP+ server certs signed by GSMA? Based on what you implied during the OsmoDevCall call about getting certified, I am under the impression that Sysmocom will not be able to provide nor eSIM profiles nor SM-DP+ services that can be used for commercial handsets? If this is the case, can you kindly redirect me to a vendor/provider who you have good experience with in this regard? Much appreciate your help! Regards, Csaba

2 3

connect osmo-BTS-trx to any other commercial Network
by Masumeh Sadat Tohidi 12 Nov '24

12 Nov '24

Hi. Is It possible to connect osmo-BTS-trx to any other commercial BSC and MSC?

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC November 2024