OpenBSC September 2015

openbsc@lists.osmocom.org

15 participants
27 discussions

Start a nNew thread

minor patches

by Neels Hofmeyr

Hello OpenBSC, see attached patches: one added configure script requirement and two entirely cosmetic tweaks. ~Neels

9 years, 9 months

[PATCH] Add SMPP support in the debian build, include libsmpp34-dev as a dependency.

by Ciaby

This is the last out-of-tree patch that we're still using to package OpenBSC in Rhizomatica. Adding SMPP support in the Debian packages shouldn't be an issue, right? Cheers Ciaby

9 years, 9 months

[PATCH] msc: Add channel information to the meas_feed, bump version to v1

by Alexander Chemeris

Hi all, Attached is a patch for the openbsc which extends meas_feed with channel information - type and id (bts/trx/ts/ss). This is used by the web incarnation of meas_vis utility we wrote [1]. Originally it was a pure copy of the original meas_vis, but when we deployed it at Rhizomatica, they suggested it would be more useful if the channel information is displayed. It would be great to see this patch merged to master. When/if this is merged, I'll submit a patch with meas_json utility which listens on the meas_feed socket and converts it to JSON format digestible by web tools. This JSON is what meas_web uses as a data feed. [1] https://github.com/fairwaves/meas_web PS Apologies for attaching the patch instead of inlining it. GMail would ruin it. -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co

9 years, 9 months

[PATCH] build: have a disable-static build succeed

by Jan Engelhardt

When using configure --disable-static, no libosmogsm.a will be created, and the tests fail to link because symbols like _a5_3 and _a5_4 are not exported through the only remaining libosmogsm.so. A method to overcome this is an intermediate private non-distributed library, examples of which are present in e.g. libabc, kmod and systemd. With this, disable-static can now be the default and practical compile time be halved. --- This is for libosmocore.git. configure.ac | 2 +- src/gsm/Makefile.am | 8 ++++++-- tests/Makefile.am | 6 ++---- 3 files changed, 9 insertions(+), 7 deletions(-) diff --git a/configure.ac b/configure.ac index c492277..9a744b1 100644 --- a/configure.ac +++ b/configure.ac @@ -13,7 +13,7 @@ AC_PROG_MAKE_SET AC_PROG_MKDIR_P AC_PROG_CC AC_PROG_INSTALL -LT_INIT([pic-only]) +LT_INIT([pic-only disable-static]) AC_CONFIG_MACRO_DIR([m4]) diff --git a/src/gsm/Makefile.am b/src/gsm/Makefile.am index d8aff4a..1878050 100644 --- a/src/gsm/Makefile.am +++ b/src/gsm/Makefile.am @@ -10,9 +10,10 @@ noinst_HEADERS = milenage/aes.h milenage/aes_i.h milenage/aes_wrap.h \ milenage/common.h milenage/crypto.h milenage/includes.h \ milenage/milenage.h +noinst_LTLIBRARIES = libgsmint.la lib_LTLIBRARIES = libosmogsm.la -libosmogsm_la_SOURCES = a5.c rxlev_stat.c tlv_parser.c comp128.c comp128v23.c \ +libgsmint_la_SOURCES = a5.c rxlev_stat.c tlv_parser.c comp128.c comp128v23.c \ gsm_utils.c rsl.c gsm48.c gsm48_ie.c gsm0808.c sysinfo.c \ gprs_cipher_core.c gsm0480.c abis_nm.c gsm0502.c \ gsm0411_utils.c gsm0411_smc.c gsm0411_smr.c \ @@ -21,8 +22,11 @@ libosmogsm_la_SOURCES = a5.c rxlev_stat.c tlv_parser.c comp128.c comp128v23.c \ auth_milenage.c milenage/aes-encblock.c \ milenage/aes-internal.c milenage/aes-internal-enc.c \ milenage/milenage.c gan.c ipa.c gsm0341.c apn.c +libgsmint_la_LDFLAGS = -no-undefined +libgsmint_la_LIBADD = ../libosmocore.la +libosmogsm_la_SOURCES = libosmogsm_la_LDFLAGS = $(LTLDFLAGS_OSMOGSM) -version-info $(LIBVERSION) -no-undefined -libosmogsm_la_LIBADD = $(top_builddir)/src/libosmocore.la +libosmogsm_la_LIBADD = libgsmint.la EXTRA_DIST = libosmogsm.map diff --git a/tests/Makefile.am b/tests/Makefile.am index 8e31f66..cf0977d 100644 --- a/tests/Makefile.am +++ b/tests/Makefile.am @@ -19,12 +19,10 @@ utils_utils_test_SOURCES = utils/utils_test.c utils_utils_test_LDADD = $(top_builddir)/src/libosmocore.la $(top_builddir)/src/gsm/libosmogsm.la a5_a5_test_SOURCES = a5/a5_test.c -a5_a5_test_LDADD = $(top_builddir)/src/libosmocore.la $(top_builddir)/src/gsm/libosmogsm.la -a5_a5_test_LDFLAGS = -static +a5_a5_test_LDADD = $(top_builddir)/src/libosmocore.la $(top_builddir)/src/gsm/libgsmint.la kasumi_kasumi_test_SOURCES = kasumi/kasumi_test.c -kasumi_kasumi_test_LDADD = $(top_builddir)/src/libosmocore.la $(top_builddir)/src/gsm/libosmogsm.la -kasumi_kasumi_test_LDFLAGS = -static +kasumi_kasumi_test_LDADD = $(top_builddir)/src/libosmocore.la $(top_builddir)/src/gsm/libgsmint.la comp128_comp128_test_SOURCES = comp128/comp128_test.c comp128_comp128_test_LDADD = $(top_builddir)/src/libosmocore.la $(top_builddir)/src/gsm/libosmogsm.la -- 2.4.3

9 years, 9 months

Osmocom Berlin User Group revival?

by Harald Welte

Dear all, After two years of intermission, I'm currently pondering to revive the Osmocom Berlin User Group and would like to understand a) who would be interested in attending? b) which day(s) of the week would be preferred / not preferred? Instad of "just" hanging out, chatting about Osmocom related topics etc. I am interested in having actual topics for each of the meetings. There is no need for a formal presentation or anything like that, but at least let's try to stay focussed on the topic for the first hour or so, and then conclude with a more general chat towards the end. Some of the topics that I would like to start with ASAP: * sharing of knowledge regarding 3G and 4G protocol stacks (I'm looking a lot at this recently, and it is a good time to talk about what I've learned) * completing the work towards splitting osmo-nitb into osmo-bsc and osmo-mss - as a first stept towards adding RANAP/Iu to osmo-mss * attempting to decode/analyze BVG bus/tram radio (TETRAPOL) using tetrapol-kit from http://brmlab.cz/git/tetrapol-kit.git * are berlin S-Bahn trains actually still broadcasting their GPS position in MPT1327? * moving ahead with AT91SAM3S based SIMtrace2 with MITM support Let me know who is interested in joining. In terms of venue I would suggest to again use the CCCB, unless somebody objects. We could of course also ask our friends at IN-Berlin or C-Base. In terms of schedule, I would actually want to go for bi-weekly again. Happy hacking, Harald -- - 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)

9 years, 9 months

[Help needed] Testing OpenBSC without hardware BTS

by Kornschnok

Hello, I just started on OpenBSC. I would really like to test it without a hardware BTS. I'm aware that there's a smalltalk "FakeBTS" program for testing it but I did not manage to run it due to a runtime problem with libgnu-smalltalk version 3.2.91 which was listed as a requirement to run FakeBTS. As lower stable version of libgnu-smalltalk wouldn't work there's nothing I could do. I include the error message below just in case. ------------------- openbts@ubuntuopenbts:~$ gst "Global garbage collection... done" "Global garbage collection... done" /usr/share/gnu-smalltalk/kernel/SysDict.st:37: Aborted /usr/share/gnu-smalltalk/kernel/SysDict.st:37: Error occurred while not in byte code interpreter!! /usr/lib/libgst.so.7 (+0x67cef) [0xb7748cef] [0xb77af400] [0xb77af424] ... Aborted -------------------- Anyway, what I want to achieve as a start is to emulate some phone calls and trace how calls are routed through the different entities. (It's for demonstration purpose and personal interest) Would that be possible with maybe some coding? I would appreciate any suggestion on how to start. Thanks in advance! Kornschnok

9 years, 9 months

[PATCH] openbsc: unhardwire MGCP endpoint id

by Mike McTernan (wavemobile)

Hi Folks, At present endpoint IDs are assumed to end with @mgw when trying to find/match non-e1 endpoint ids. Unless the MGCP peer supports compatible configuration, DNS or a hosts file may need to be setup to meet the hardwired host name requirement in the openBsc MGCP, and then we can still only run one BSC. The attached patch makes a simple change to use either the configured local_ip or source_addr, matching logic used in SDP responses. It also improves the error message when an endpoint can't be found. Please consider for inclusion to mainline. Kind Regards, Mike

9 years, 9 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC September 2015