OpenBSC August 2021

openbsc@lists.osmocom.org

9 participants
12 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

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

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

Connect cell phone to real GSM network through OpenBTS
by Mario Lucas 28 Aug '21

28 Aug '21

Dear Osmocom society, I am trying to connect a cell phone (lets call it phone #1) through OpenBTS to real GSM network… To do so i have to introduce a osmocomBB phone which will be connected to my linux machine which runs OpenBTS So kind of it will be a following structure: Phone #1 → OpenBTS → OsmocomBB phone → real GSM netwok. No my goal is to have OpenBTS and OsmocomBB phone to talk to each other… for example authentication parameters which to be exchanged between phone #1 and real network to happen through the chain described above …. Has this case been or something like this done before ? Or are you aware of any cases when OpenBTS and OsmocomBB phone exchange data? Thank you very much -- Mario Lucas

1 0

Announcement of "OsmoDevCall" on August 27, 2021
by Harald Welte 24 Aug '21

24 Aug '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 27, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "osmo-remsim in practice" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

rsl_rx_bs_pwr_ctrl()
by Neels Hofmeyr 13 Aug '21

13 Aug '21

Hey Vadim, Just now I came across this code, with an early return in case of BCCH. But right below that, BCCH is still mentioned in the comment, and there are more IEs being parsed. So I get the impression the early return may prevent that OSMO_MIN limiting for BCCH, and that may not be intended? /* Osmocom specific extension for BCCH carrier power reduction */ if (dch->chan_nr == RSL_CHAN_BCCH) { int rc = bts_set_c0_pwr_red(trx->bts, new); if (rc != 0) { const uint8_t cause = (rc == -ENOTSUP) ? RSL_ERR_SERV_OPT_UNIMPL : RSL_ERR_IE_CONTENT; return rsl_tx_error_report(trx, cause, &dch->chan_nr, NULL, msg); } return 0; } /* BS power reduction is generally not allowed on BCCH/CCCH carrier. * However, we allow it in the BCCH carrier power reduction operation. * Constrain BS power value by the maximum reduction for this timeslot. */ if (trx->bts->c0 == trx) new = OSMO_MIN(new, lchan->ts->c0_power_red_db); /* 9.3.32 (TLV) BS Power Parameters IE (vendor specific) */ if ((ie = TLVP_GET(&tp, RSL_IE_BS_POWER_PARAM)) != NULL) { https://git.osmocom.org/osmo-bts/tree/src/common/rsl.c?id=6611e7f3059d26794…

2 2

Announcement of "OsmoDevCall" on August 13, 2021
by Harald Welte 12 Aug '21

12 Aug '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 13, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "GSM-R and its differences to GSM" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

HR / AMR Lab Testing Using OSMO-NITB
by Sonny Lafuente 10 Aug '21

10 Aug '21

Hello Community! Would like to as if anyone here have experience testing Half rate /AMR in osmo-nitb and Freeswitch. Basically we are testing it in our lab with our devices Samsung Note 9 and iPhone and we are having issue / errors as observed during testing. Below are the details of the NITB we using: OpenBSC# show version OpenBSC 1.1.0.76-0bbb9 (OpenBSC). Copyright (C) 2008-2016 Harald Welte, Holger Freyther Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. OpenBSC# Osmo running-config: stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive network network country code 10 mobile network code 1 short name testnetwork long name testnetwork auth policy closed authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3113 60 timer t3103 1 timer t3101 10 timer t3109 1 timer t3122 10 timer t3105 1 dyn_ts_allow_tch_f 0 subscriber-keep-in-ram 1 bts 0 type sysmobts band GSM900 cell_identity 1 location_area_code 1 base_station_id_code 63 ms max power 23 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator descending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1000 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr hr efr amr amr tch-h modes 0 amr tch-h start-mode auto trx 0 rf_locked 0 arfcn 122 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 hopping enabled 0 timeslot 2 phys_chan_config SDCCH8 hopping enabled 0 timeslot 3 phys_chan_config TCH/H hopping enabled 0 timeslot 4 phys_chan_config TCH/H hopping enabled 0 timeslot 5 phys_chan_config TCH/H hopping enabled 0 timeslot 6 phys_chan_config TCH/H hopping enabled 0 timeslot 7 phys_chan_config TCH/H hopping enabled 0 trx 1 rf_locked 0 arfcn 42 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/H hopping enabled 0 timeslot 2 phys_chan_config TCH/H hopping enabled 0 timeslot 3 phys_chan_config TCH/H hopping enabled 0 timeslot 4 phys_chan_config TCH/H hopping enabled 0 timeslot 5 phys_chan_config TCH/H hopping enabled 0 timeslot 6 phys_chan_config TCH/H hopping enabled 0 timeslot 7 phys_chan_config TCH/H hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h amr nitb subscriber-create-on-demand subscriber-create-on-demand random 100000 199999 no assign-tmsi smpp local-tcp-ip 127.0.0.1 2776 system-id password policy closed smpp-first esme admin password password default-route NITB Logs: Not Working: Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02) Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=7,ss=0) Activating ARFCN(73) SS(0) lctype TCH_H r=CALL ra=0x49 ta=0 Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=7,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=7,ss=0) CHANNEL ACTIVATE ACK Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state ACTIVATION REQUESTED -> ACTIVE Tue Aug 10 17:08:41 2021 <000a> bsc_api.c:415 Sending (bts=0,trx=1,ts=7,ss=0) ChanModify for speech: SPEECH_AMR on channel TCH_H Tue Aug 10 17:08:41 2021 <0003> gsm_04_08_utils.c:517 -> CHANNEL MODE MODIFY mode=0x41 <—————————————————————————————————————— This is what we observed, no Channel Modify Ack Tue Aug 10 17:08:47 2021 <000a> bsc_api.c:139 Assignment T10 timeout on 0x15b4350 Tue Aug 10 17:08:47 2021 <0003> osmo_msc.c:82 MSC assign failure (do nothing). Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02) Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=7,ss=1) Activating ARFCN(73) SS(1) lctype TCH_H r=CALL ra=0x49 ta=0 Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=7,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=1) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=7,ss=1) CHANNEL ACTIVATE ACK Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=1) state ACTIVATION REQUESTED -> ACTIVE Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:746 [entropy] smpp_pdu_rx(00 00 00 10 00 00 00 15 00 00 00 00 00 00 00 24 ) Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:595 [entropy] Rx Enquire Link Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:599 [entropy] Tx Enquire Link Response Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x47, neci=0x01, chreq_reason=0x02) Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=6,ss=0) Activating ARFCN(73) SS(0) lctype TCH_H r=CALL ra=0x47 ta=0 Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=6,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=6,ss=0) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=6,ss=0) CHANNEL ACTIVATE ACK Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=6,ss=0) state ACTIVATION REQUESTED -> ACTIVE Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:1358 (bts=0,trx=1,ts=7,ss=0) CONNECTION FAIL: RELEASING state ACTIVE CAUSE=0x01(Radio Link Failure) Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:867 (bts=0,trx=1,ts=7,ss=0) RF Channel Release due to error: 1 Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:777 (bts=0,trx=1,ts=7,ss=0) DEACTivate SACCH CMD Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state ACTIVE -> RELEASE DUE ERROR Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:939 (bts=0,trx=1,ts=7,ss=0) RF CHANNEL RELEASE ACK Tue Aug 10 17:09:17 2021 <0004> abis_rsl.c:826 (bts=0,trx=1,ts=7,ss=0) is back in operation. Tue Aug 10 17:09:17 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state RELEASE DUE ERROR -> NONE Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: Location updating (ra=0x07, neci=0x01, chreq_reason=0x03) Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1924 (bts=0,trx=0,ts=1,ss=0) Activating ARFCN(8) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x07 ta=0 Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:595 (bts=0,trx=0,ts=1,pchan=SDCCH8) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1231 (bts=0,trx=0,ts=1,ss=0) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1603 (bts=0,trx=0,ts=1,ss=0) CHANNEL ACTIVATE ACK Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1231 (bts=0,trx=0,ts=1,ss=0) state ACTIVATION REQUESTED -> ACTIVE Osmo-sip-connector Logs: <0000> sip.c:330 sip_release_call(): Release with MNCC cause(NORM_CALL_CLEAR) <0000> sip.c:302 cause2status(): Mapping cause(NORM_CALL_CLEAR) to status(200) <0000> sip.c:353 Ending leg(0x8dc700) in con <0000> sip.c:223 SIP event(33) status(200) phrase(OK) 0x8dc700 <0000> sip.c:257 leg(0x8dc700) got resp to bye <0000> sip.c:223 SIP event(9) status(200) phrase(Session Terminated) 0x8d7150 <0000> sip.c:265 leg(0x8d7150) got bye, releasing. <0000> sip.c:223 SIP event(7) status(0) phrase(INVITE sent) 0x8d7150 <0000> sip.c:223 SIP event(1) status(100) phrase(Trying) (nil) <0000> sip.c:89 Incoming call handle(0x8d96a0) <0000> sip.c:223 SIP event(7) status(100) phrase(Trying) 0x8dc700 <0000> sip.c:330 sip_release_call(): Release with MNCC cause(RESOURCE_UNAVAIL) <0000> sip.c:302 cause2status(): Mapping cause(RESOURCE_UNAVAIL) to status(503) <0000> sip.c:341 Canceling leg(0x8dc700) in cnfd state <0000> sip.c:223 SIP event(31) status(503) phrase(Service Unavailable) 0x8d7150 <0000> sip.c:242 leg(0x8d7150) unknown SIP status(503), releasing. <0000> sip.c:248 Releasing other leg (0x8d6f30) with status(503) <0001> mncc.c:54 cmd(0x204) never arrived for leg(2147483656) <—————————————————————————————————————— Basically it didn’t arrived in B Leg. <0001> mncc.c:495 call(2147483656) can not be found Very well appreciated your help on this. Best Regards, Sonny

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC August 2021