OpenBSC

openbsc@lists.osmocom.org

13 participants
4278 discussions

Error in making OsmoNITB on Linux
by Abdulghafar Shabaneh 09 Aug '16

09 Aug '16

Hello, I am trying to install Openbsc on the raspberry pi. I get this error (in the attachment ) when I use make. After ./configure) . Is there a problem in ipaccess.nano? Recently. If it is optional . Is it safe to remove it entirely since I am using USRP ? Thanks Abdulghafar

2 1

Development of rtl-sdr driver
by Piotr Krysik 08 Aug '16

08 Aug '16

Hi everyone, The osmocom's version of rtl-sdr driver seems to be the main one. Osmocom's repository is used by distributions to build rtl-sdr packages and it is source of the code for compilation with use of GNU Radio's Pybombs. Is there someone in the Osmocom who is maintaining it? There were some important developments regarding this driver and it would be great to add this patches in the Osmocom's repo. For example one that interests me is turning off dithering so multiple dongles sharing the same clock generate the same LO frequency.Currently there is always little frequency offset that makes coherent of the receivers operation much harder. Such changes of course have to be done carefully so nothing gets broken in the process. In case of turning off dithering it results with worse tuning granularity, so for example turning it off can be made optional. -- Best Regards, Piotr Krysik

2 1

signal quality measurements in osmo-trx
by Max 05 Aug '16

05 Aug '16

Hi. I'm working on http://projects.osmocom.org/issues/1616 and wonder about $subj. In case of sysmobts, osmo-pcu obtain this data directly from DSP: * RSSI (dBm) * burst timing (in quarter of bits) * link quality (in dB) * BER The first and last value seems to be easy from what I see in src/osmo-bts-trx/scheduler_trx.c What about burst timing (necessary to compute TA in the absence of PTCCH) and link quality (measure of C / I where C is carrier and I is interference power) - how can I compute those or some estimator to those values? -- 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

4 5

[PATCH] Add Control Interface port numbers
by msuraev＠sysmocom.de 04 Aug '16

04 Aug '16

From: Max <msuraev(a)sysmocom.de> Related: OS#1646 --- common/chapters/port_numbers.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/common/chapters/port_numbers.adoc b/common/chapters/port_numbers.adoc index 695cc6c..0430b13 100644 --- a/common/chapters/port_numbers.adoc +++ b/common/chapters/port_numbers.adoc @@ -22,6 +22,8 @@ which protocol / interface. |TCP|4246|telnet (VTY)|osmo-gbproxy |TCP|4249|Control Interface|osmo-nitb, osmo-bsc |TCP|4250|Control Interface|osmo-bsc_nat +|TCP|4251|Control Interface|osmo-sgsn +|TCP|4252|Control Interface|openggsn |TCP|5000|A/IP|osmo-bsc, osmo-bsc_nat |UDP|2427|GSMTAP|osmo-pcu, osmo-bts |UDP|23000|GPRS-NS over IP default port|osmo-pcu, osmo-sgsn, osmo-gbproxy -- 2.9.2

1 0

control interface variable naming
by Max 03 Aug '16

03 Aug '16

Hi. It's nitpicking time :) I've noticed that variables exposed over control interface (see osmobsc-usermanual.pdf for example) are named differently - some use _ (e. g. bts_connection_status) others use - (e. g. short-name). Which variant is preferred if any? -- 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

1 0

certificate expiration
by Max 01 Aug '16

01 Aug '16

Hi. A little heads-up - I've noticed that certificate on gerrit server has expired: gerrit.osmocom.org uses an invalid security certificate. The certificate expired on 08/01/2016 12:24 PM. The current time is 08/01/2016 12:33 PM. -- 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

2 1

Re: OsmoNITB + Asterisk
by Anonim Stefan 01 Aug '16

01 Aug '16

Hi, Is there any intention / interest among current community developers to implement the DTMF for osmo sip connector?! Thanks, Stefan On Jul 27, 2016 3:33 PM, "Holger Freyther" <holger(a)freyther.de> wrote: > On 27 Jul 2016, at 20:19, Brian Butterly <bbutterly(a)ernw.de> wrote: > > Hi, Hi! > has anyone recently put together a functional setup with OsmoNITB and > Asterisk (+LCR)? why asterisk? why LCR? The osmo-sip-connector is a "trivial" piece of software that bridges MNCC to SIP (and back) and let's everyone else do the heavy lifting. In contrast to LCR it currently lacks: * Multi-party calls (a bit harder) * DTMF (quite easy but not done) holger

2 1

OsmoNITB + Asterisk
by Brian Butterly 30 Jul '16

30 Jul '16

Hi, has anyone recently put together a functional setup with OsmoNITB and Asterisk (+LCR)? I've got multiple errors while compiling LCR with Asterisk, mainly unknown definitions and a set of missing functions. My setup: -NanoBTS -current OpenBSC (running perfectly) -Ubuntu Xenial, 64Bit, VBox VM -current LCR from Osmocom Repos -Asterisk (build without any issues) --1.8.32.3 from Asterisk Page --1.6.2.24 from Asterisk Page --11.32.0 form Asterisk Page --last 13.x release vie apt I had expected the newer versions to be incompatible, still gave them a shot anyways. I've started fiddling with LCR, but before I go deeper into that, I just wanted to check if there was some defined approach which would get everything up and running. I'd be very thankful for any hint or maybe some information on which versions of what will actually work together. Thanks! Brian

2 2

dyn TS tweaks and fixes
by Neels Hofmeyr 30 Jul '16

30 Jul '16

Hi all, I have some patches that probably fix some corner cases of dynamic pchan switching. However, since I'm technically already in vacation, I will only be able to properly test them in about 10 days' time. If they should become interesting before that, the changes are pushed to branches called neels/dyn_fixes in openbsc and osmo-bts. ~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

1 0

osmo-bts: rach_ind.ra size
by Neels Hofmeyr 27 Jul '16

27 Jul '16

I just came across this compiler warning: l1sap.c: In function 'gsmtap_ph_rach': l1sap.c:291:8: warning: assignment from incompatible pointer type [enabled by default] *data = &l1sap->u.rach_ind.ra; ^ It's a uint16_t ra and used like this in common/l1sap.c: static int gsmtap_ph_rach(struct osmo_phsap_prim *l1sap, uint8_t *chan_type, uint8_t *tn, uint8_t *ss, uint32_t *fn, uint8_t **data, int *len) { [...] *data = &l1sap->u.rach_ind.ra; *len = 1; A cast like this would fix the compiler warning and make sense if data is interpreted to point at a 16 bit data block, probably in host byte order though: *data = (uint8_t*)&l1sap->u.rach_ind.ra; *len = 1; But *len = 1 means that **data is an 8bit value? This is sent to gsmtap. Is *len = 1 something we should fix? ~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

3 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC