OpenBSC June 2018

openbsc@lists.osmocom.org

11 participants
16 discussions

question!
by Cattalina Maria 15 Jun '18

15 Jun '18

Hello. I have some problems.I want to create a GSM network for my final diploma project for University.I'm using USRP2 and I haven't find any specific configuration files for this type of USRP.Do you have any configuration files for USRP2? I'm running Kali Linux (amd64). I've attached the config files that I've used from osmocom.org and some printscreens.Sorry for my English.I'm looking forward for your response.Thank you!

3 2

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

Regarding Programming SIM cards
by Ferdaus, Farah 13 Jun '18

13 Jun '18

Hi there, I have built and installed the requirements for OpenBTS and my USRP (Ettus N210) is responding but now I am stuck at SIM card stage. I am trying to program a Super SIM 16-in-1 using the Insten_USB_SIM_Card_Writer<https://www.amazon.com/Insten-Reader-Writer-Backup-Phone/dp/B0188GHIP2/ref=…> and following the steps mentioned here<http://openbts.org/w/index.php?title=ProgrammingSIMcards> and here<http://osmocom.org/projects/pysim/wiki> but unable to write the sim card. Every time I run the pcsc_scan command it stops working. Below is the output. "wslopenbts@wslopenbts-desktop:~$ pcsc_scan PC/SC device scanner V 1.4.25 (c) 2001-2011, Ludovic Rousseau <ludovic.rousseau(a)free.fr> Compiled with PC/SC lite version: 1.8.14 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...^C" The problem seems that the PC is not getting the SIM card reader. But the SIM card reader was plugged into the PC while running the command and the LED turned red which indicate it was getting the power from the PC. Do you think, buying another new SIM card reader can resolve the issue? I can test by buying another SIM and SIM card reader; Do any of you have any suggestion for the SIM and SIM card reader, particularly which one will be good? Finally, any guideline for me regarding programming the SIM card. I will be very grateful if you help me by giving suggestions to resolve my issue. Can anyone please help me regarding this issue. Thanks in advance Best Regards, Farah

3 3

osmo-trx-lms
by Antony Lemmens 05 Jun '18

05 Jun '18

Hello folks, I had trouble with the osmo-trx-uhd and LimeSDR (like in Bug #2723), so I tried the branch "laforge/lime". The result is that the LimeSDR apparently transmit successfully data (my MS display correctly the MCC/MNC and the spectro shows the correct frequency) but it seems that the LimeSDR/driver/not-sure-what does not receive any signal in return. I know that my complete hardware and software setup (cables, tem cell, spectro) is OK because it works fine with the Fairwaves UmTRX board. The LimeSuiteGUI shows some problems with the RX calibration, but if I do a full reset to default settings from the GUI, it works fine (so I suppose that the problem does not come from the LimeSDR board itself). If I restart osmo-trx-lms, it cause the problem again. Is there some specific settings to do in osmo-trx.cfg to make it work? I know that it is a work in progress, and if you need some feedback or tests, do not hesitate to ask. Have a nice day, Antony

2 1

ABIS over IuB SCTP
by Borjan Jovanovski 03 Jun '18

03 Jun '18

Hi everyone, i would like to know if it is possible to connect a bts which uses abis over sctp to OpenBSC and if so i would kindly ask for an explenation on how to do that. Kind thanks.

3 9

nanoBTS constantly restarting
by Michael Spahn 01 Jun '18

01 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC June 2018