OpenBSC October 2020

openbsc@lists.osmocom.org

17 participants
14 discussions

by Martin Nagy

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 days, 8 hours

Re: Help with sccp library

by mosbah abdelkader

> 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.

1 month, 1 week

dynamic traffic channels

by Neels Hofmeyr

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 months

Problem while running NIB on Open Cellular Base sation

by Brackley Casinga

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

1 year, 6 months

GSUP <> MAP Conversion

by a.valizadeh＠sinacomsys.com

Hi! i'm very interested about GSUP <-> GSM MAP protocol conversion to perform HLR interrogation. Do you suggest a suitable solution for this problem? is there some related activity at OSMOCOM project?

4 years, 9 months

Re: OpenBSC Digest, Vol 72, Issue 18

by Sipos Csaba

Hi Andreas, Fixed the patch. Yes there is a gap in the middle, that is why it is split to two: 1..72 and 132..239 is the correct one and it uses a reverse numbering like the Slovak or Czech networks. This is the reason the NMT phones in Hungary was not compatible with any other country, and the phones country settings were locked to Hungary only. For example in my MCR4800XL the country cannot be set, yet if you read out the EPROM, it contains the country settings for all country, but it is locked down to Hungary only. Regards, Csaba <openbsc-request(a)lists.osmocom.org> ezt írta (időpont: 2020. okt. 28., Sze, 13:00): > Send OpenBSC mailing list submissions to > openbsc(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/openbsc > or, via email, send a message with subject or body 'help' to > openbsc-request(a)lists.osmocom.org > > You can reach the person managing the list at > openbsc-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenBSC digest..." > > > Today's Topics: > > 1. [PATCH] Adds country specific settings for Hungary. (Sipos Csaba) > 2. Re: [PATCH] Adds country specific settings for Hungary. > (Andreas Eversberg) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Oct 2020 19:08:46 +0100 > From: Sipos Csaba <dchardware(a)gmail.com> > To: "openbsc-request(a)lists.osmocom.org" <openbsc(a)lists.osmocom.org> > Subject: [PATCH] Adds country specific settings for Hungary. > Message-ID: > <CALQr=E9WMDr_-KBwWdQAH=UgB88nd= > ph2p1G2dOSG8F_CtY_Jg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > This is the final patch for Hungary specific settings for the > osmocom-analog project. > > Tested against a locked Motorola MCR4800XL, it works on all channels and > TAs. > > Please let me know if any more work needs to be done. > > Regards, > Csaba >

4 years, 9 months

[PATCH] Adds country specific settings for Hungary.

by Sipos Csaba

This is the final patch for Hungary specific settings for the osmocom-analog project. Tested against a locked Motorola MCR4800XL, it works on all channels and TAs. Please let me know if any more work needs to be done. Regards, Csaba

4 years, 9 months

Fwd: NMT-450 - partial success

by Sipos Csaba

Hi, I know it is a bit off topic, but as osmocom-analog has no dedicated mail list and my every attempt to contact Andreas lead to silence, I thought this is the closest one to discuss it. I try to create an NMT-450 network with Motorola MCR4800XL phones, and a LimeSDR-mini. As the phones are locked to "Hungary" using a specific raster and a large gap in the middle, first I needed to dig out the details, find out the country code and create a patch so at least the phone is willing to lock onto the DS signal. I managed to do all that, so now the phone is actually able to decode the network and lock onto the signal. My issue is with the uplink: when the phone tries Traffic Area update (the phone's uplink transmission burts is clearly seen with a spectrum analyzer), the network side is not able to detect the uplink burst at all. Not even as bad, or incorrectly formatted frame. Andreas has a site which describes how to set up the uplink side and do some tests: http://osmocom-analog.eversberg.eu/docs/sdr.html I followed that guide and when the uplink burst from the phone arrives, the RX IQ constellation monitor indicates a correct burst with proper power (the burst is nicely round and in the green area). If I try to set up a call to the phone using the correct country code and phone number, the phone clearly responds to the paging request, as the 3 paging attempt generates 3 uplink bursts. Again, with no reception/decoding on the network side. Tried with two phones of the same type, the effect is the same. I have two questions: 1. Where to send patches for the osmocom-analog project? 2. Does anyone have an idea what can be wrong with my setup? One more thing I noticed: compared to the channel frequency used to set the NMT network up, the uplink is a couple kHz shifted: http://www.imagebam.com/image/d17e881357285965 As it can be seen, the uplink burst appears 3-4kHz left relative to the downlink signal. The network is started with the following command: nmt -k 239 -k 235 -Y HU,1 --limesdr-mini --sdr-rx-gain 20 Any and all help is appreciated. Regards, Csaba

4 years, 9 months

[PATCH 0/1] pysim: make random seed function python3 compatible

by Jeremy Herbert

Currently the random seed function _digits is not python3 compatible as it passes a unicode string to the sha1 function. It generates the following exception: Using PC/SC reader interface Card programming failed with an execption: ---------------------8<--------------------- Traceback (most recent call last): File "./pySim-prog.py", line 718, in <module> rc = process_card(opts, first, card_handler) File "./pySim-prog.py", line 643, in process_card cp = gen_parameters(opts) File "./pySim-prog.py", line 342, in gen_parameters iccid += _digits(opts.secret, 'ccid', ml, opts.num) File "./pySim-prog.py", line 228, in _digits s = hashlib.sha1(secret + usage + '%d' % num) TypeError: Unicode-objects must be encoded before hashing ---------------------8<--------------------- This patch fixes this problem. Jeremy Herbert (1): make random seed function python3 compatible pySim-prog.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- 2.25.1

4 years, 9 months

libosmocore: macOS support?

by Ludovic Rousseau

Hello, I try to build utils/osmo-sim-test.c on macOS. For that I need to build the complete libosmocore project. I already patched/hacked some source code file to make them compile on macOS but now the compiler fails on src/vty/cpu_sched_vty.c because cpu_set_t is Linux-specific. The problem is that src/vty/cpu_sched_vty.c contains *a lot* of use of cpu_set_t usage. I am pretty sure utils/osmo-sim-test.c will not need the functions defined in cpu_sched_vty.c. Is it possible to build utils/osmo-sim-test.c without building the complete libosmocore project? Any interest in macOS support (even partial & unofficial support)? Yes, the easiest option is to use Linux. But my main computer uses macOS. And I like challenges :-) Regards, -- Dr. Ludovic Rousseau

4 years, 10 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC October 2020