OpenBSC May 2018

openbsc@lists.osmocom.org

21 participants
32 discussions

Re: Help with sccp library
by mosbah abdelkader 08 Jul '25

08 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

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

Save the Date: OsmoCon 2018 on October 18-19, 2018
by Harald Welte 19 Oct '18

19 Oct '18

== OsmoCon 2018 == OsmoCon (Osmocom Conference) 2018 is the technical conference for Osmocom users, operators and developers! We are happy to announce the date of OsmoCon 2018. It has been scheduled on October 18 + 19, 2018 and will happen in Berlin, Germany. For the second time, the Osmocom Conference brings together users, operators and developers of the Osmocom Open Source cellular infrastructure projects, such as OsmoBTS, OsmoBSC, OsmoSGSN, OpenGGSN and others. Join us for two days of presentations and discussions with the main developers behind Open Source Mobile Communications, as well as commercial and non-profit users of the Osmocom cellular infrastructure software. You can find some initial information in our wiki at http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018 which will be updated as more information becomes available. == Call for Participation == We're also at the same time announcing the Call for Participation and call on everyone with experiences to share around the Osmocom member projects to submit talks, workshops, discussions or other proposals. You can find the CfP at https://pretalx.sysmocom.de/osmocon2018/cfp We are particularly looking for contributions about: * updates on features/functionality/status of individual Osmocom projects * success stories on how Osmocom projects are deployed in practice * migration from OsmoNITB to the post-NITB architecture * tutorials / workshops on how to setup / analyze Osmocom projects * statistics, reporting, operations aspects of Osmocom projects * third-party open source utilities to be used with Osmocom projects Looking forward to meeting many existing and new Osmocom users at OsmCon this October! Regards, Harald Welte -- - 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)

3 4

Osmo-bts "shutdown timer expired"
by Георгий Прайзендорф 15 Jun '18

15 Jun '18

Hi, sorry for my English. I installed osmocombb on Kali rolling. When i'm trying to start my own bts, it works for 4 seconds, then i can see message "Shutdown timer expired". Bellow you can see my config files. 1 screenshot - 2 trx firmware on motorola c115. 2 screenshot, left - follow the commercial BTS timer, right - starting MSC, SMS, HLR. 3 screenshot - starting osmo-bts. 4 screen - my problem. I can connect with telnet to BSC and BTS, but BTS - only for this 4 seconds, when it's up. I didn't replaced filters on motorola, is it my problem? Or i just need to install smth more? Also, if i write to the wrong mail list, tell me please where should i write with my problem?

2 1

nanoBTS constantly restarting
by Michael Spahn 02 Jun '18

02 Jun '18

Hello all, I have recently tried migrating an OsmoNITB setup to the new standard using mostly this guide right here: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I… <https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…> However, while my nanoBTS works perfectly fine in the old setup, it just doesn not work at all in the new one. When I start osmo-bsc the LED on the BTS starts flashing green after a few seconds and then stops flashing and just stays green all the time, which is the expected behaviour. Unfortunately though, after another couple of seconds, the LED starts flashing green again and then turns red. This is what the log shows: BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=l2_bch.c:1154 **** ** l2_bch.c#1154:BCHbcchSItypeValid( prim_p->infoType ) ** IPA_SW_FATAL_ERROR ** In task "TRX Proc:L2_BCH" @ (1063). **** 　 . BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=TRX Proc:L2_BCH:l2_bch.c#1154 (1063). BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#255:TRX has logged the error: 　 . BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#256:TRX Proc:L2_BCH:l2_bch.c#1154 (1063) . BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=BCHbcchSItypeValid( prim_p->infoType ). BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#260:BCHbcchSItypeValid( prim_p->infoType ) 　 20180328072641280 DLINP <0013> input/ipaccess.c:247 Sign link vanished, dead socket 20180328072641281 DLINP <0013> input/ipaccess.c:71 Forcing socket shutdown with no signal link set 20180328072641282 DCTRL <000e> osmo_bsc_ctrl.c:160 No more BTS connected, sending TRAP. 　 Now I'm not claiming that my config is already 100% correct but I feel like this isn't a configuration issue. I'm using the most recent nightly builds of the entire osmocom library. Does anyone know what could be at fault here? Kind regards, Michael Spahn

4 9

React to IMSI Attach but not PERIODIC
by Keith Whyte 31 May '18

31 May '18

Hi All, I have a use case where I'd like to react to MS connecting to the network, that is on initial IMSI ATTACH. We already have the SMPP alert notification mechanism which can be used, but unfortunately in SMPP the ms_availability_status only has 3 posible values in the spec: 0: Available 1: Denied 2: Unavailable. So currently if I react to status 0, this would also happen on periodic LURs I could keep state separately but that sounds prone to errors. The external process reacting to the alert notification could try somehow to get the previous status from HLR or database, but that sounds like a race condition. One possibility might be to extend this with a further custom value 3: Available (Initial Attach) or some such? Any thoughts?

4 9

UICC with ISIM application
by Tomcsányi, Domonkos 30 May '18

30 May '18

Hello All, Sorry if this is an off-topic question, but I was wondering: does anyone know of any carrier that actually uses a UICC ('SIM card') with the ISIM application installed? So far all cards I saw have only USIM, maybe CSIM on them. I'd like to extend Benoit's card library with ISIM support, but there is no way to test my code right now, so I'm thinking about buying maybe a card. Thanks. Domi

3 3

Writing FPLMS to SIM
by Keith Whyte 28 May '18

28 May '18

Hi all Somebody mentioned recently (at osmodevcon was it?) about writing to the FPLMNS list to avoid service loss due to LUR reject cause 11 (I think?) I notice we don't seem to have this an a option in pySim-prog.py, so I am wondering what tool was used? Thanks! (I noted the commented FIXME section for HPLMN in pySim.read.py and from there was able to modify read address and read and decipher the FPLMN list, although i did not get a nice readable output format yet.)

3 3

Re: Compiler Error OsmocomTRX
by Babar Ali 28 May '18

28 May '18

I received following error while compling osmo-trx on rasbian, i have already build libosmocore-0-11-0 from source and installed but despite this still unable to compile osmo-trx, any one can help to resolve the issue! configure: error: Package requirements (libosmocore >= 0.11.0) were not met: Requested ‘libosmocore >= 0.11.0’ but version of Osmocom Core Library is UNKNOWN Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.” I have already build following components on Rasbian from source successfully LimeSuite SoapySDR SoapyUHD libosmocore-0.11.0/ libosmocore-0.96.0 RegardsBabar

5 15

osmo-trx and osmo-bts-trx ip address with LimeSDR
by Sandi Suhendro 26 May '18

26 May '18

Dear list, I have question about osmo-trx config with osmo-bts-trx. if in osmo-bts-trx osmotrx ip local 192.168.100.73 osmotrx ip remote 192.168.100.100 then what ip address fill on osmo-trx for limesdr.cfg? bind-ip 192.168.100.73 remote-ip 192.168.100.100 Please correct me, cause I confuse osmo-trx won't running if not using same ip as 127.0.0.1 well, Does 127.0.0.1 is fine for only sms/call network in new split? please advise. Thanks. -- Best Regards, DUO

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC May 2018