OpenBSC

openbsc@lists.osmocom.org

20 participants
4286 discussions

Patch: EPC capability flag support
by Tomáš Morvay 17 Sep '15

17 Sep '15

Hi, as a part of our project at university, we implemented extraction of EPC Capability flag. This flag is a bit sent by mobile phone to indicate support of EPC (or LTE). This bit is extracted during processing of Attach request to log this information. An function to check the the of this flag for given sgsn context is also created to make it reusable. For the extraction of the EPC Capability field we used the location described in TS 24.008 v10.15.0 section 10.5.5.12. This can be interesting information for any developers experimenting with devices supporting 4G, so I think I would be a good idea to make it available in the original repository. The patch for this change is in the attachment. Best regards, Tomas Movay

1 0

DAHDi support broken (with DAHDI 2.7.0 onwards)
by Sipos Csaba 16 Sep '15

16 Sep '15

Dear Harald, This is probably no the best moment, but as the original implementer of DAHDI support in OpenBSC, maybe you can fix this. It seems that DAHDI 2.7.0 breaks the compatibility with OpenBSC. I think the only thing they changed is the way you need to refer to the E1 device in /dev and because of that, OpenBSC will not going to find the DAHDI device and give an error in that regard. The last time I checked (around version 2.9) this was the only problem, otherwise OpenBSC compiles fine with DAHDI. Anyway, the use of DAHDI 2.6.3 (the latest which works with OpenBSC) forces us to use very old kernels (and OSes), and I am quite sure we are not the only ones still using OpenBSC with E1. :-) I hope you will have some time and take a quick look into this. If you dont have any E1 based hardware anymore, I am more than happy to help you and test the fix on our (Nokia InSite, MetroSite, Ultrasite based) system. Thank you! Regards, Csaba

1 3

minor patches
by Neels Hofmeyr 16 Sep '15

16 Sep '15

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

2 1

[PATCH] Add SMPP support in the debian build, include libsmpp34-dev as a dependency.
by Ciaby 15 Sep '15

15 Sep '15

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

2 2

[PATCH] msc: Add channel information to the meas_feed, bump version to v1
by Alexander Chemeris 14 Sep '15

14 Sep '15

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

3 4

[PATCH] build: have a disable-static build succeed
by Jan Engelhardt 11 Sep '15

11 Sep '15

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

1 0

Osmocom Berlin User Group revival?
by Harald Welte 08 Sep '15

08 Sep '15

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)

3 3

[Help needed] Testing OpenBSC without hardware BTS
by Kornschnok 03 Sep '15

03 Sep '15

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

1 0

[PATCH] openbsc: unhardwire MGCP endpoint id
by Mike McTernan (wavemobile) 01 Sep '15

01 Sep '15

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

2 4

dvnixload error: Entry point not found
by Diego Fernandez Alonso 24 Aug '15

24 Aug '15

Hello. I have a problem with my sysmoBTS. When I start the bts I receive a BOOTME message. So after identify in the SysmoBTS Manual the problem like broken UBL, I tried to follow the manual using the dvnixload utility. I installed the binutils-multiarch package and others neccesary for the execution of the divnixload, but during the proccess I get an error: root@ubun-osmo:/home/osmo-user/Documentos# ./dvnixload -p /dev/ttyUSB0 ubl-sysmobts-v2.elf u-boot-sysmobts-v2.elf dvnixload info: Using cross compiler "" dvnixload info: Expecting messages: [BOOTME] [BOOTPSP] [I_ME] dvnixload info: [BOOTME] received dvnixload error: Entry point not found dvnixload error: Entry point not found Do someone know why I get an "Entry point not found" message and how I can fix it? Thank you so much!!

2 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC