OpenBSC March 2020

openbsc@lists.osmocom.org

5 participants
7 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

OsmoSTP connection

by Igor Kim

Hello dears! I try to connect 2 STPs to each other via Sigtran M3UA protocol. But I don't understand, why my connection is fault. Could you please check my configuration? STP1 STP2 point-code 0.12.4 point-code 0.12.4 port 2905 port 2906 IP 172.18.141.1 IP 172.18.142.2 Me configuration is: STP1 cs7 instance 1 network-indicator reserved point-code 0.12.4 asp stp2 2906 2905 m3ua local-ip 172.18.141.1 remote-ip 172.18.142.2 role asp sctp-role client as stp2 m3ua asp stp2 traffic-mode override routing-key 0 0.25.0 route-table system STP2 cs7 instance 1 network-indicator reserved point-code 0.25.0 asp stp1 2905 2906 m3ua local-ip 172.18.142.2 remote-ip 172.18.141.1 role sg as stp1 m3ua asp stp1 traffic-mode override routing-key 0 0.12.4 route-table system listen m3ua 2906 accept-asp-connections dynamic-permitted Thanks in advance!

5 years, 5 months

New Mobile Phone Models - Latching Issue using OSMO-NITB - Connection Drops approx after 3 Minutes

by Ron

Hi Community, Does anyone experiences, in newer phone models, that after a successful latched to OSMO-NITB, it will dropped its connection in a few minutes? We have experienced this issue to the following mobile phone models: 1. iPhone X - Software Version - 13.3 (Connection drops approximately after 3 minutes) 2. Samsung S10 (Connection drops after 1 - 3 minutes) 3. Samsung Note 9 Best Regards, Ron Menez

5 years, 5 months

Use of anytype in Osmocom TTCN-3 tests / TITAN

by Harald Welte

Hi Vadim, 22:22 < fixeria> LaF0rge: oh, we already have 'template anytype' in pcu/PCUIF_RAW_Components.ttcn 22:23 < fixeria> ... and that's my code :P 22:26 < fixeria> yay, it even compiles 22:39 < fixeria> but does not work as expected: "error: Type mismatch: a value or template of type `(a)Osmocom_Types.anytype' was expected instead of `integer'" 22:41 < fixeria> I am testing against uint8_t which is defined exactly in Osmocom_Types :/ 22:52 < fixeria> LaF0rge: pespin_: https://pastebin.com/EL9JUqq9 Please see https://www.eclipse.org/forums/index.php?t=msg&th=1074288&goto=1721710&#msg… for how to use anytype in TITAN So if I modify the last line of Osmocom_Types.ttcn with your patch from https://pastebin.com/EL9JUqq9 attached to this: } with { encode "RAW"; variant "FIELDORDER(msb)" extension "anytype OCT1" } The errors about the non-existant OCT1 field in anytype are gone. This is of course not nice, but maybe a work-around to explicitly list those types at the end for now? Regards, Harald -- - 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)

5 years, 6 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2020