OpenBSC

openbsc@lists.osmocom.org

10 participants
4277 discussions

osmo-nitb / osmo-bsc ms max power dynamic value
by Ron 15 Sep '17

15 Sep '17

Hi All, Is there a way to configure the “ms max power” to a dynamic value depending on the distance of the mobile phone to the base station? For now, the default value is 12. Meaning, the base station is telling the mobile phone to transmit in the power of 12dBm either the phone is besides the base station or on the edge of the base station. If not, is there a roadmap on configuring it with a dynamic or auto value? TIA. Best Regard, Ron Menez ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>

2 1

osmo-ntib and osmo-bts-trx config file error
by mohammad nejati 15 Sep '17

15 Sep '17

Hi , OsmoBTS version 0.6.0.6-ae13 OpenBSC version 0.15.0.885-968a6 I flow the instructions from wiki page and create config files : https://osmocom.org/projects/cellular-infrastructure/wiki/SDR_OsmoTRX_netwo… but when i run : osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM I got this error : There is no such command. Error occurred during reading the below line: timer t3103 0 <0005> ../../../src/libbsc/bsc_init.c:536 Failed to parse the config file: '/home/ashtum/.osmocom/open-bsc.cfg' Reading config failed. Exiting. Similarly when i run : osmo-bts-trx -c ~/.osmocom/osmo-bts.cfg I got : ((*)) | / \ OsmoBTS There is no such command. Error occurred during reading the below line: fn-advance 20 % rtp bind-ip is now deprecated Failed to parse the config file: '/home/ashtum/.osmocom/osmo-bts.cfg'

2 1

Error after installing openbsc.deb
by Anindya Sankar Roy 14 Sep '17

14 Sep '17

Hello, I have installed the open openbsc.deb but when I am trying to run it using the command "osmo-bsc" its giving me the following error <0005> bsc_init.c:536 Failed to parse the config file: 'openbsc.cfg' Bootstrapping the network failed. exiting. full talloc report on 'sccp' (total 1 bytes in 1 blocks) Please help me solve it. Thanks Anindya

3 4

VTY tests still causing build failures
by Harald Welte 14 Sep '17

14 Sep '17

Dear all, for probably about a year (or longer) we have been putting up with VTY tests which cause builds to break under unclear circumstances. I personally believe the probability of a VTY test failing has recently increased again, and this is barely tolerable anymore. Often, rebasing/cherry-picking the given patch one or two times also doesn't work. Yet, the given patch-under-test is not even touching anything related to VTY, like In https://gerrit.osmocom.org/3899 which has failed in https://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/2451/ and https://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/2454/ I know Neels and others have spend already significant time in the past trying to resolve this - unsuccessfully. So I think the situation has reached a point where we should disable the vty tests, or at least the specific part of the vty tests that is known to break most frequently. I definitely want us to have *more* testing, not less. However, when the test itself is not stable yet - particularly after that much time - we cannot have that buggy test delay our development. I would vote for running those tests regularly (daily, every few hours, you name it), but not as part of the mandatory build verification for gerrit V+1. What do others think? -- - 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)

4 5

osmo-gsm-tester modems
by Neels Hofmeyr 11 Sep '17

11 Sep '17

On Mon, Sep 11, 2017 at 11:01:23AM +0200, Pau Espin Pedrol wrote: > today I found the same issue again in prod (/sierra_2 -> /sierra_4). > Interestingly, both /sierra_2 and /sierra_3 seem to be using the same > firmware. dmesg shows again a disconnect from the usb port. We have this idea of giving the same modem a persistent name on ofono, which would solve the symptoms, but it's curious why this happens. I had the watchdog script in place that power cycles the quad modem board and restarts ofono as soon as the modem names mismatch what we expect. But lynxis disabled it. The reasoning is that we won't catch ofono errors. That may be true; my idea was to be able automatically recover ofono without manual intervention. I guess it all depends on how closely you (lynxis) watch the gsm testers for failures? Because my focus is not particularly on ofono, and when I hit a broken situation and need to test things, I will restart ofono and rather not in-depth investigate the failure; in a dismissive way "come on ofono, do what I want now." What do you guys think about this? > I guess only /sierra_2 crashes because it's the first modem in the > resources.conf list and thus it is usually used in all tests (for instance, > tests which require only 1 modem), and probably some of the steps done in > one of those tests is crashing the modem. Something I thought about before: we could implement a kind of random or round robin to not always pick the first matching resources in the list. Advantage is that we would cycle through the hardware and force us to precisely formulate e.g. modem requirements. The disadvantage is that not every test is run exactly the same, adding complexity that may obscure analysis. i.e. to reproduce a run on a particular modem, we would have to somehow clamp that randomness, e.g. log a random seed at the start and allow passing in a random seed on the cmdline. ~N

2 1

OpenBSC and OsmocomBB
by Testphone Test 11 Sep '17

11 Sep '17

Dear List I am trying to run osmocomBB with motorola c118 with openbsc.I tried to get openbsc network on my phone it works well and I am able to register on openbsc network. But when i try to run osmocomBB with openBSC i am not able to get network. Also when i run rssi firmware on c118 phone i get network and its working fine. I am using default configuration file for OpenBSC and using NanoBTS with 1800Mhz support. Is there any configuration change is needed in openBSC ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

Registering problem on osmo-bts
by Sandi Suhendro 09 Sep '17

09 Sep '17

Dear guys, anyone can help me, Im using osmo-gsm-tester osmo-bts.cfg and openbsc.cfg also/ BTS is up and auth policy accept-all is set and even I add subscriber IMSI, but my phone still cannot register on the network. my setup is LimeSDR and using the latest osmo-bts and openbsc with OpenUSRP. do you think its a hardware issue? please help! Thanks -- best regards, DUO

3 4

OsmoBTS after NITB split
by Max 09 Sep '17

09 Sep '17

Hi. The OsmoBTS build depends (unfortunately) on OpenBSC because it uses gsm_data_shared.h header. ATM this file is available in osmo-bsc and osmo-msc (maybe other split repos as well). Which is the "canonical" one from OsmoBTS point of view? Also, when would be the right time to move OsmoBTS' jenkins job to use one of the split repos instead of old OpenBSC? -- Max Suraev <msuraev(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

3 3

jenkins slave setup and artifact re-use
by Neels Hofmeyr 09 Sep '17

09 Sep '17

Hi Blobb, I'd like to probe your opinion on a discussion we had today about our jenkins. So far our setup was manual, and we would like to (somewhat) automate the process of providing build dependencies on slaves. One solution that was discussed longer than others would be to use docker. Each of our repositories that need a build would have their own docker file, containing the complete setup of dependencies. The idea is that anyone can easily setup an identical build on any new jenkins build slave or even at home; no complex config of the jenkins build slave is needed. The point being, if we adopt docker in such a way, it would be logical to make use of the docker cache to save unnecessary rebuilds. It is a generic solution instead our artifact store. I feel a bit bad for accepting your contributions, doing review and keeping you busy, just to then talk about docker to solve the problem instead; I appreciate your presence and would like to keep you involved. Interestingly enough, we are experimenting with the artifact store on that one build job that has already been using docker for quite some time... (It was for the separate network space, not really for artifacts.) In any case, I would like to include you in the discussion, and maybe you would also like to be involved in maturing the idea? Until now it is still wild and no-one has taken actual steps. An example to follow would be laforge's recently added https://git.osmocom.org/docker-playground/tree/ One interesting bit is that it has a method to check whether a given git branch has changed, and rebuilds the docker image only if it has: https://git.osmocom.org/docker-playground/tree/osmo-ggsn-master/Dockerfile#… ADD http://git.osmocom.org/openggsn/patch/?h=laforge/osmo-ggsn /tmp/commit This line fetches the given URL (in this case the latest patch on that branch) and considers the docker image as unchanged if that URL shows the same as last time. As soon as a new patch shows, things are rebuilt. In this sense we could have docker images cascading on top of each other, adding individual dependencies and reusing identical states auto-detected by docker. All build steps would be in the Dockerfile. For builds that aren't used by other builds (like the "final" programs, osmo-msc, osmo-sgsn, osmo-bsc,...) we don't need to store the result, so don't need to include the program's build in the Dockerfile: on a docker image with all dependencies, run the final build step by invoking 'docker run', like we currently do for the OpenBSC-gerrit job, and then just discard the changes. Remotely related: we have the osmo-gsm-tester that is running binaries produced by jenkins to do automated tests on real GSM hardware. Currently we compile and tar the binaries, copy them over, extract, set LD_LIBRARY_PATH and run: a bit tedious and problematic e.g. for mismatching debian versions. This could be simplified by docker by guaranteeing a fixed operating system around the binary, actually using hub.docker.com (or maybe one day a private docker hub) instead of copying over binary tars manually, sharing across any number of build slaves, and with the added bonus of having the resulting binaries run in a separate network space. As I said, on the one hand I appreciate our work on the artifact store, on the other hand the docker way undeniably makes for a good overall solution to simplify things in general, with artifact re-use coming "for free"... One advantage of the artifact store though is that the artifacts we manage are not entire debian installations but just a few libs and executables in a tiny tar. What is your opinion? ~N

3 9

virtphy and MT SMS
by Keith Whyte 08 Sep '17

08 Sep '17

Hi all! I just installed and configured osmo-bts-virtual and osmocom-bb with virtphy. Let me say - this is brilliant! It's so easy to do such things as trigger IMSI Attach and Detach - so much easier than entering and exiting airplane mode or power off/on. Also, MO sms is a breeze.. I have a script to inject SMS regularly, so I don't have to turn to the mobile and press buttons with each code change in my SMS handler, I just make the change and wait for the next SMS to hit it! So thanks so much to those responsible for making this happen! Now, one thing that is failing badly for me right "out-of-the-box" is MT SMS. As I am totally new to the osmocom-bb code, I guess the best would be a ticket with some pcaps, but I thought I would ask first if it is a known issue? Basically, BSC is doing this: DLSMS <0024> gsm_04_11.c:127 GSM4.11 TX [HEX of msg redacted] DLSMS <0024> gsm0411_smc.c:247 SMC(954) TC1* timeout, retrying... while on the mobile side: <0005> gsm48_mm.c:3909 (ms 1) Received 'RR_EST_IND' from RR in state MM idle (sapi 0) <0005> gsm48_mm.c:912 new state MM IDLE, normal service -> wait for network command Then this repeats: <0001> gsm48_rr.c:4775 Indicated ta 0 (actual ta 0) <0001> gsm48_rr.c:4777 Indicated tx_power 19 <0001> gsm48_rr.c:4799 ACCH message type 0x00 unknown. <0001> gsm48_rr.c:664 MON: f=56 lev=>=-47 snr= 0 ber= 63 LAI=262 42 0001 ID=0000 TA=0 pwr=19 TS=1/1 <0001> gsm48_rr.c:2866 MEAS REP: pwr=19 TA=0 meas-invalid=0 rxlev-full=-47 rxlev-sub=-47 rxqual-full=0 rxqual-sub=0 dtx 0 ba 0 no-ncell-n 7 <0001> gsm48_rr.c:2161 PAGING ignored, we are not camping.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC