OpenBSC August 2019

openbsc@lists.osmocom.org

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

1 month

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.

2 months, 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, 4 weeks

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, 7 months

Sample configs for reproducing osmo-nitb behaviour with the split stack

by Rafael Diniz

Hi all, Today I'm working on updating my NuRAN unit with the new osmo stack in order to try to reproduce the same behavior of old osmo-nitb we use in production in Rhizomatica (with subscriber_create_on_demand feature on). I'm writing just in case someone already put online a set of config files with the parameters needed by such behavior set? ; ) ps: I have the new splip stack working fine here, I just need to modify my setup with new features to support subscriber_create_on_demand. Best regards, Rafael Diniz

6 years

osmo-hlr VTY tests failing on master

by Harald Welte

FYI. I don't see any commit until the last one from Pau on August 13. It could of course also be a change in libosmocore? -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

6 years

Diameter to GSUP translator

by Harald Welte

Hi all, as some of you know, I've been working on a small diameteer to GSUP translator, which allows us to connect a MME like nextepc-mme against osmo-hlr. The code is still a big ugly hack and needs cleanup, but today I finally got it to work for authentication and location update. In case anyone is curious how this looks like, I've attached a pcap file that includes the S1AP, DIAMETER, GSUP and GTPv2C traffic of an initial LTE registration happening on a setup running the following programs: * nextepc MME, SGW, PGW, PCRF * osmo_diameter2gsup * osmo-hlr The point of this is to enable networks to run a shared subscriber database for 2G, 3G and 4G, which is a very typical use case if you have existing Osmocom based network and want to extend it with LTE. We will test this translator extensively at the upcoming CCC Camp, where all three (2G, 3G and 4G) networks will be running. The sad part is that we don't yet have a common GGSN and P-GW, which means that the PDP/PDN context including the IP address will not persist when moving between 2G+3G on the one hand side and 4G on the other hand side. I expect to get the commit history cleaned up and plan to push the [Erlang] code to git.osmocom.org tomorrow. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

6 years, 1 month

3G handover (+ 35C3 experience)

by Mykola Shchetinin

Hello, dear Community, Has anybody tested how cell handover works in 3G with Osmocom software? 3G network was set up for 35C3: I would like to ask whether anybody noticed if a cell was reselected "smoothly" by the phone when the user was moving or it was like a drop of a connection and reconnection to a different cell afterwards? So, basically, the question is: Does the handover work in 3G Osmocom? (single HNBGW and MSC/SGSN) Thanks. Kind regards, Mykola

6 years, 1 month

201908 Osmocom CNI Release

by Pau Espin Pedrol

Hi, I have been releasing new tagged versions of Osmocom CNI (Osmocom Cellular Network Infrastructure) related projects over last days this week. New released versions: libosmocore 1.2.0 libosmo-abis 0.7.0 libosmo-netif 0.6.0 libusrp 3.4.4 libgtpnl 1.2.1 osmo-trx 1.1.1 osmo-pcu 0.7.0 osmo-ggsn 1.4.0 osmo-pcap 0.1.1 libasn1c 0.9.32 libsmpp34 1.14.0 osmo-bts 1.1.0 osmo-hlr 1.1.0 libosmo-sccp 1.1.0 osmo-mgw 1.6.0 osmo-iuh 0.5.0 osmo-bsc 1.5.0 osmo-msc 1.5.0 osmo-sgsn 1.5.0 openbsc 1.3.1 osmo-sip-connector 1.3.0 Some patch releases may come tomorrow in the event some unexpected error shows up during repository build process. Please, to get the latest tags applied, remember to fetch them and clean up the .version related files. Something like this will do the job (be careful, git clean may remove some of your changes in the git repo): $ git fetch --tags; git clean -fxd Updated tags in OE meta-telephony 201705 will come during current ot next week. Regards, -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

6 years, 1 month

Failure to activate sigtran stack when using IPA on osmo-bsc

by Roch-Alexandre Nominé

Hi, I’m trying to configure osmo-bsc to connect to an IPA based MSC and get a failure when activating the sigtran stack. Here’s the log: root@sysmobts-v2:/etc/osmocom# osmo-bsc -c /etc/osmocom/osmo-bsc.cfg <001d> ../../git/src/osmo_ss7.c:1269 0: ASP Restart for server not implemented yet! % Ignoring deprecated logging level everything % Ignoring deprecated logging level everything % dyn_ts_allow_tch_f is deprecated, rather use msc/codec-list to pick codecs <0011> ../../../git/src/vty/telnet_interface.c:104 telnet at 0.0.0.0 4242 <0013> ../../git/src/input/ipaccess.c:853 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports <0018> ../../../git/src/ctrl/control_if.c:866 CTRL at 0.0.0.0 4249 <0008> ../../../git/src/osmo-bsc/osmo_bsc_sigtran.c:427 Initializing SCCP connection to MSC msc-0 <0008> ../../../git/src/osmo-bsc/osmo_bsc_sigtran.c:437 CS7 Instance identifier, A-Interface: 0 <001e> ../../git/src/sccp_user.c:397 msc-0: Using SS7 instance 0, pc:0.23.3 <001e> ../../git/src/sccp_user.c:411 msc-0: Creating AS instance <0005> ../../../git/src/osmo-bsc/osmo_bsc_main.c:504 Failed to initalize sigtran backhaul. I used the configuration posted by Harald part of ticker https://osmocom.org/issues/2544 https://osmocom.org/attachments/3154/osmo-bsc.cfg.ipa and get the same result. How can I troubleshoot further in order to know what’s happening? Best regards Roch.

6 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC August 2019