OpenBSC June 2016

openbsc@lists.osmocom.org

18 participants
82 discussions

by Max

Hi. So far release process for new versions of osmocom components was rather quiet (unless I'm looking at the wrong place). This is different from many other open source projects some of which do announcements in ML, some use blogposts etc. Is there any interest/value in the release announcements for osmocom projects? Or maybe partially (applications but not libraries for example)? Or only major but not minor? Or not at all? To me personally the value is twofold: a) we generate some news which might be good thing to attract attention of potential contributors (if we won't overdo it :) and b) it makes it clear when some feature is "officially shipped" so we have to start paying attention to things like backward compatibility. Of course writing such announcements is boring regardless of a medium so if we follow this road we should automate the process as much as possible. What do you guys think? -- 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

9 years, 3 months

gerrit and branches

by Neels Hofmeyr

Today I've taken another close look at branches and gerrit, and have written down my conclusions here: http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit#Submitting-… In summary: * Branch re-submission needs the workaround of tweaking the first commit. It would be nice to fix gerrit to not need this, but for the time being the effort of cosmetically changing the first commit log is acceptable. * It *is* possible to have private branches in the gerrit repos and still be able to submit them to master, with the proper project config. I have thus switched all our gerrit projects' configs to rebase-if-necessary with the flags as described on the wiki page. (Except for osmo-pcap, where we still disallow content merges.) I will now go back to pushing my "private" developments to the public repository (gerrit) under the neels/ or sysmocom/ namespaces. ~Neels -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

9 years, 3 months

testing gerrit, might be down shortly

by Neels Hofmeyr

I'm testing things related to our gerrit bug report, if it's not working for you right now it may be because I'm restarting gerrit to test with/out our fix. I'll repost when I'm done. ~Neels -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

9 years, 3 months

osmo-trx repo

by Max

Hi. Repository over git.osmocom.org/osmo-trx is not (yet?) converted to gerrit. Can I get commit access so I can push (not to master of course) some branches for review/testing if necessary? -- 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

9 years, 3 months

RE: Regression in osmo-pcu with UHD trx ?

by Saurabh Sharan

> Date: Fri, 27 May 2016 18:02:28 +0200 > From: Pierre Baudry <pierre.baudry(a)diateam.net> > I noticed that since several weeks that osmo-pcu did not work as good as > previously. Yes we have also seen similar failures for GPRS calls in the osmo-pcu. Our setup uses NuRAN hardware with osmo-bts-sysmo > The latest "good" revision I am aware of is commit > d87e1d6ab747423d3668c74d16201a5d967accf0 (2015/12/14) This is a useful information for us that the above mentioned commit works for GPRS. > Can somebody confirm or reproduce this attitude ? The PCU log that we have during failure matches with the one you have reported. We have tried a workaround for this GPRS call failure by forcing two-phase-access in osmo-pcu.cfg. Based on our analysis done till now it seems One phase access of GPRS is broken. > I will try to provide more logs and a pcap capture as soon as I get > hands back on the hardware. It will be quite useful to narrow down the issue, so please share the relevant logs collected Regards Saurabh

9 years, 3 months

gerrit on all repos?

by Neels Hofmeyr

On Wed, Jun 15, 2016 at 07:11:06PM +0200, Max wrote: > Repository over git.osmocom.org/osmo-trx is not (yet?) converted to gerrit. I believe that we could move all repositories to gerrit now. Are there reasons to keep some of the repositories out of gerrit? Almost all of my problems with gerrit have been resolved, and the last one is solved by not pushing private branches to gerrit. Instead, I have my own bare git clones on our sysmocom-office machine to sync my home and office work. It would be nice to be able to publicly push private branches again, and indeed I think the fix for gerrit wouldn't be too difficult, but for now I'm fine. I would like to switch all projects to 'rebase-if-necessary', but first want to verify the differences to the cherry-pick strategy. IIRC cherry-pick is no good for commits that depend on each other, but only 80% sure about that... ~Neels -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

9 years, 3 months

osmo-trx issues

by Max

Hi. While running osmo-trx with B200 I've noticed following log messages repeated multiple times: 1) WARNING 3011271488 16:59:00.1 Transceiver.cpp:674:pullRadioVector: Clipping detected on received RACH or Normal Burst 2) ERR 3011304256 16:58:12.9 UHDDevice.cpp:1512:write: Skipping buffer data: timestamp=210353475 time_end=202360063 How bad is that: are those break everything completely or can be sometimes ignored? What could be causing it and what can be done to try to fix it (hw/sw)? Note, I run it as follows: sudo chrt 20 ./Transceiver52M/osmo-trx -- 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

9 years, 3 months

OpenBSC

by sms makhof

Hi all I am installing OpenBSC.I just following http://openbsc.osmocom.org/trac/wiki/Building_OpenBSC (I am just Building libosmocore, Building libosmo-abis, Building libosmo-netif, Building OpenBSC and install library.) But when I tried to run OpenBSC,I encounter with this error(problem). user12@ubuntu:~$ cd '/home/user12/openbsc/openbsc/src/osmo-nitb' user12@ubuntu:~/openbsc/openbsc/src/osmo-nitb$ sudo ./osmo-nitb <0005> bsc_init.c:492 Failed to parse the config file: 'openbsc.cfg' Or how do I run the software(OpenBSC)! Or do I have to install something missing? Note: My Linux is version 12.04 . Please help me. thank you.

9 years, 4 months

RRLP encoding related

by mike sbor

Hello, I am trying to generate ephemeris data (that I get from a ublox receiver) in RRLP format. I have came across the following discussing n openbsc mailing list. http://openbsc.osmocom.narkive.com/8rLcJRc2/rrlp-ephemeris-data#post9 at the end of the discussion, Dieter Spaar wrote that he found a bug fix for a problem. Can you please guide me about where to look for this feature in the git repository? In the discussion, Slyvian has attached a project but I am not sure whether this bug fix is there or not I am planning to buy/manufacture the board that Slyvian has designed for ublox lea 6 and try producing assisted gps data in rrlp format http://openbsc.osmocom.org/trac/wiki/osmo-lea6t-gps Thanks a lot for your help rifo

9 years, 4 months

osmo-bts - branch:laforge/virt_phy - questions on virtual layer implementation

by Sebastian Stumpf

Hi, as a part of my master thesis I am currently trying to complete the implementation of the virtual physical layer in the laforge/virt-bts branch in osmo-bts.git. I already set up the projects and analyzed/debugged some of the code. Now I have a few things to ask or be confirmed by the pros :). 1. The sent messages on the virtual physical layer will be wrapped in a GSM_TAP header. I would like to analyze and implement the Uplink (MS->BTS) on the BTS side first, by sending dummy messages a small program and then processing them in the BTS. Unfortunately I don't have these dummy messages. Can anyone of you provide me with some examples for the msgs coming from the MS side (Access Burst on RACH, Uplink Burst on TCH, RSSI on SACCH, Location Update Request on SDCCH, Authentication Response on SDCCH) or tell me how else I can get my fingers on them? 2. Did I correctly understand that the virt_um_rcv_cb() method in l1_id.c will unwrap incoming GSM_TAP messages and distribute/forward them to layer2? Is the correct l2 interface to use l1sap.c from the common part? E.g. l1sap_ph_rach_ind(..) for incoming RACH msg from MS. 3. Does any logic to unwrap and forward GSM_TAP messages already exist or was that solely used for logging via wireshark by now. 4. I added some comments to the code, mostly to document my own unterstandings. But as I am no expert yet, they might contain some logical errors. Can I keep these in the code when commiting or better remove them? 5. Should I create a new branch for my work (e.g. stumpf/virt_phy) or commit to the existing? Not so important Questions: 6. I had a compilation error caused by 2 missing methods in the main.c.I added empty method bodies for bts_model_phy_link_set_defaults(..) and bts_model_phy_instance_set_defaults(..) and everything seems okay so far. Can I do that or did I miss something here? 7. To check if I receive incoming messages from the registered virtual UM multicast socket I periodically wrote a dummy text to it with a small program. As the registered callback method virt_um_rcvcb(..) wasn't called I checked the initialization of the multicast socket (virtual_um.c->virt_um_init(..)). After some research it seems that mcast sockets do not support a call of connect() after a bind(). Removing the call that connects the socket to the multicast group and port, seems to work. Is that okay or are there any problems I could run into by not connecting to the mcast socket? I think connect() is usally used on tcp sockets. Thank you very much in advance for your answers! Kind Regards, Sebastian Stumpf

9 years, 4 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC June 2016