OpenBSC

openbsc@lists.osmocom.org

4315 discussions

OpenBSC running on an Odroid-XU
by John Baker 18 Sep '14

18 Sep '14

Hi, I have an Odroid-XU I have setup with Debian Wheezy and a USRP B200. After building the UHD drivers from source, I followed the "network from scratch" page. I also configured and built osmo-trx with the --with-neon-vfpv4 option. Things are running OK, a whole lot better than my attempt with OpenBTS actually. I"m able to connect to the network with my Samsung S4 phone, but after an hour or so of the BTS running, I get a UHD recieved time out error (see below). I wonder what could be causing this? I have the B200 plugged into the USB 3.0 port, along with external power. Thanks in advance for any help. root@odroid-wheezy:~# osmo-trx linux; GNU C++ version 4.6.3; Boost_104900; UHD_003.007.002-94-ge56809a0 Config Settings Log Level............... NOTICE Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 Channels................ 1 Samples-per-Symbol...... 1 External Reference...... Disabled C0 Filler Table......... Disabled Diversity............... Disabled Tuning offset........... 0 -- Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex... done -- Loading FPGA image: /usr/local/share/uhd/images/usrp_b200_fpga.bin... done -- Operating over USB 3. -- Detecting internal GPSDO.... No GPSDO found -- not found -- Initialize CODEC control... -- Initialize Radio control... -- Performing register loopback test... pass -- Performing CODEC loopback test... pass -- Asking for clock rate 32.000000 MHz -- Actually got clock rate 32.000000 MHz -- Performing timer loopback test... pass -- Asking for clock rate 26.000000 MHz -- Actually got clock rate 26.000000 MHz -- Performing timer loopback test... pass -- Setting B200 1 SPS -- Transceiver active with 1 channel(s) ALERT 3030074464 23:06:10.4 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:10.5 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:10.6 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:10.7 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:10.8 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:10.9 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.0 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.1 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.2 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.3 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.4 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.5 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.6 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.7 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:11.9 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.0 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.1 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.2 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.3 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.4 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.5 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.6 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.7 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.8 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:12.9 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.0 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.1 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.2 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.3 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.4 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.5 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.6 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.7 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.8 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:13.9 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:14.0 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:14.1 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out ALERT 3030074464 23:06:14.2 UHDDevice.cpp:832:check_rx_md_err: UHD: Receive timed out terminate called after throwing an instance of 'uhd::assertion_error' what(): AssertionError: accum_timeout < _timeout in uint64_t radio_ctrl_core_3000_impl::wait_for_ack(bool) at /root/uhd/host/lib/usrp/cores/radio_ctrl_core_3000.cpp:232

2 1

TIP: Working with nanoBTS behind NAT
by admin＠manateeshome.com 15 Sep '14

15 Sep '14

I wrote a short post about using nanoBTS behind NAT and getting proper connection. http://manatails.net/blog/2014/09/setting-arbitary-destination-ip-for-rtp-p… As OpenBSC does not natively support NAT like Asterisk does, One needs to use a simple hack to manually tell the BSC about the connection information. Regards, Pierre

1 0

osmo-sgsn crash report
by admin＠manateeshome.com 15 Sep '14

15 Sep '14

Hello, I've been working with my nanoBTS units again. But I've noticed some crashes while using GPRS data. I am currently using the newest git repo for everything. And a nanoBTS 1900 and an iPhone. Attached is the log of the crash. Please let me know if you need more information. Regards, Pierre

2 2

RRlp protocol implementation
by Snehasish Kar (Vehere) 15 Sep '14

15 Sep '14

Dear Sir I am trying to use the RRLP protocol implemented in openbsc, till now i am able to send the rrlp request and activate the phone gps(ms-based mode) but i am not getting any reply from the phone's side neither any location error or any location. So please suggest me what to do in this case. Thanks & Regards Snehasish

2 1

What branch to use with B200?
by Sipos Csaba 14 Sep '14

14 Sep '14

Dear list, It seems that after the last 2-3 weeks massive committing storm, I lost the ability to compile an interworking version of OpenBSC/Osmo-BTS/Osmo-PCU because the Osmo-PCU and the Osmo-BTS cannot connect anymore. According to the wiki, I need to use "jolly/multi-trx" for Osmo-Abis and "jolly/trx" for Osmo-BTS, and "jolly/testing" with OpenBSC. Previously this setup was working, but now Osmo-BTS tells the PCU socket is not connected, while the PCU is running with the correct config on the same PC. I also wanted to try "201409-trx" branch (moved back to master with osmo-abis and openbsc for this one, otherwise I got errors during the configuration phase), but I got compilation errors with Osmo-BTS at RSL.c If someone can point me in the right direction which branches should I use to get an interworking copy with a B200, that would be awesome. I am also happy to try the new branch "201409-trx" if someone can tell me which branches to use for that too. Thanks! Csaba

1 0

libosmo{core,vty,codec,ctrl,vty} GPL v2 vs v3
by Harald Welte 12 Sep '14

12 Sep '14

Hi Steve and Max, sorry for catching up that late. It is only now in my holidays that I finally am able to find some time to read through the osmocom mailing lists again. On Wed, Mar 26, 2014 at 08:17:58PM +0100, Steve Markgraf wrote: > On 26.03.2014 18:26, Max.Suraev(a)fairwaves.co wrote: > > I've just noticed (yepp, I'm very observant :) that COPYING in > > libosmocore is GPLv2. Is there any particular reason we still do > > not use GPLv3? libosmocore was started as a GPLv2+ project, in order to ensure maximum compatibility to a variety of applications. Some free software applications out there are still GPLv2, and we want them to be able to use libosmocore. * libosmocodec is pure GPLv2+ * libosmoctrl is pure GPLv2+ * libosmovty is pure GPLv2+ > Good point, git grep "either version 3" actually shows that there are > quite some files that are GPLv3+, so the compiled and linked binaries > already make use of the "or any later version" of the other GPLv2+ > licensed files. This is actually a problem, and one that needs fixing. 1) libosmogb Most of the hits are in libosmogb, as the libosmogb code was first developed as part of (AGPLv3+) OpenBSC/OsmoSGSN and then migrated to libosmocore.git reporitory to be also used from osmo-pcu, not just from the SGSN side. The majority of the osmo-pcu codebase appears to be GPLv2+, so linking with a GPLv3+ libosmogb is fine. However, an AGPL libosmogb would not be suitable. I've reviewed the copyright ownership /authorship situation of libosmogb and see if we can make sure that all authors agree to a GPLv3+ licensing of it. Based on the review, we have the following copyright holders: * Harald Welte * Holger Freyther * sysmocom (Jacob, Holger?) * Andreas Eversberg Holger/Andreas: * Would you agree to license libosmogb under GPLv2+ or GPLv3+? * Do you have any preference regarding v2+ or v3+? 2) libosmocore: strrb.c / loggingrb.c These are the only two files of libosmocore, which claim to be GPLv3+. I would personally consider this a mistake at the time, but I've included Katerina in the Cc. Holger/Katerina: * Do you remember how and why this code states it is GPLv3+ instead of the usual GPLv2+ in libosmocore? * Was this intentional or a mistake? * Irrespective of the past, would you agree to license strrb/loggingrb under GPLv2+? If yes, I will commit the related code change 3) libosmogsm: gsm0411_smc.c und gsm0411_smr.c This is due to jolly first writing them as part of osmoocomBB and then later moving them to libosmocore. Jolly: Can you please confirm if you are willing to license them under GPLv2+ instead of GPLv3+ as indicated in the source code? 4) libosmogsm: the imported milenage code. it is GPLv2 or BSD, so we have to use it under BSD license. This should be indicated somewhere explicitly. > So replacing COPYING with GPLv3 definitely would make sense imho. See above, the devil is in the details, it's not that simple. Regards, 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 2

Re: GPRS core network simulation
by Calogero Cannizzaro 11 Sep '14

11 Sep '14

Hi mister Harald, thank you very much for your answer. I am an engineering student and I have started to work on my thesis. I would like to perform a GPRS core network completely using virtual machine (virtual box based) and use it to prove that an operator can manage M2M traffic just using standard hardware, virtual machine and open source components (osmocom project ). At this moment i deployed 4 virtual machine, one for each osmo component (osmoNITB, openGGSN, osmoSGSN) on the fourth VM I want to run the fakeBTS because I don't have a bts. I would like to simulate it as if there are some M2M devices generate request(attach, pdp context for example). When I try the communication between NITB and fakeBTS there are some error Messages related to RSL. Then there isn't communication between NITB-fakeBTS and SGSN-GGSN. Do you detect any configuration error? Thank you. Best regard Calo -------- Original message -------- Subject: Re: GPRS core network simulation From: Harald Welte <laforge(a)gnumonks.org> To: calogero cannizzaro <can_ni(a)hotmail.it> CC: "openbsc(a)lists.osmocom.org" <openbsc(a)lists.osmocom.org> Hi Calogero, * what is the goal / use case of your simulation? * what exactly do you need to simulate? * what is the input/output of the simulation? In general, the vaious Osmo-* implementations are not designed for simulation buy for actual network operation. So you will likely need to implement quite a lot in order to use it in a simulation context. The most important question is, that you need code that will behave as actual handsets on a network, and code to manage all those virtual handsets, tell them what they should be doing, etc. -- - 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 2

[PATCH] gprs: Fix bssgp_rcvmsg to handle signalling msgs with BVCI IE
by Jacob Erlbeck 10 Sep '14

10 Sep '14

Currently BSSGP messages with an NS BVCI of 0 (signalling) are discarded if they aren't RESET messages. Thus valid signalling messages (e.g. BLOCK) are not handled properly, because the BVCI IE is ignored if it present. Instead a STATUS message referring to BVCI 0 (instead of the BVCI used in the BLOCK message) is returned. This patch changes the implementation to use the BVCI contained in the BVCI IE if that is present in a signalling message. It fixes BSSGP BLOCK/UNBLOCK for the osmo-sgsn. Note that signalling messages without an BVCI IE (e.g. SUSPEND/RESUME) are still rejected. Ticket: OW#1205 Sponsored-by: On-Waves ehf --- src/gb/gprs_bssgp.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/src/gb/gprs_bssgp.c b/src/gb/gprs_bssgp.c index b8c6c74..0e9fd38 100644 --- a/src/gb/gprs_bssgp.c +++ b/src/gb/gprs_bssgp.c @@ -976,6 +976,7 @@ int bssgp_rcvmsg(struct msgb *msg) struct bssgp_bvc_ctx *bctx; uint8_t pdu_type = bgph->pdu_type; uint16_t ns_bvci = msgb_bvci(msg); + uint16_t bvci = ns_bvci; int data_len; int rc = 0; @@ -991,14 +992,17 @@ int bssgp_rcvmsg(struct msgb *msg) rc = bssgp_tlv_parse(&tp, budh->data, data_len); } + if (bvci == BVCI_SIGNALLING && TLVP_PRESENT(&tp, BSSGP_IE_BVCI)) + bvci = ntohs(*(uint16_t *)TLVP_VAL(&tp, BSSGP_IE_BVCI)); + /* look-up or create the BTS context for this BVC */ - bctx = btsctx_by_bvci_nsei(ns_bvci, msgb_nsei(msg)); + bctx = btsctx_by_bvci_nsei(bvci, msgb_nsei(msg)); /* Only a RESET PDU can create a new BVC context */ if (!bctx && pdu_type != BSSGP_PDUT_BVC_RESET) { LOGP(DBSSGP, LOGL_NOTICE, "NSEI=%u/BVCI=%u Rejecting PDU " - "type %u for unknown BVCI\n", msgb_nsei(msg), ns_bvci, + "type %u for unknown BVCI\n", msgb_nsei(msg), bvci, pdu_type); - return bssgp_tx_status(BSSGP_CAUSE_UNKNOWN_BVCI, &ns_bvci, msg); + return bssgp_tx_status(BSSGP_CAUSE_UNKNOWN_BVCI, &bvci, msg); } if (bctx) { -- 1.9.1

1 0

Training sequences of ARFCNs different than C0
by Perper 08 Sep '14

08 Sep '14

Hi All, I've started implementing reception of multiple channels of a BTS as part of my gr-gsm project and I encountered little problem. C0 channel (most probably) uses different training sequence than the rest of ARFCNs from Cell Allocation. I'm not sure that this is the case. But if I compute cross correlation I always get the strongest peak for a different training sequence. The training seqence number used on C0 is usually equal to BCC (BTS Color Code) that is transmitted in SCH bursts (I've never seen different situation in the wild). I can also find training sequence code of C0 transmitted on BCCH inside of Channel Description in System Information Type 4 messages. Where BTSes transmit training sequence (/sequences) of ARFCNs other than C0? Best Regards, Piotr Krysik

2 2

[openbsc 1/2] gprs_sgsn.h: Add two macros to log details of MM/PDP contexts
by Daniel Willmann 08 Sep '14

08 Sep '14

--- openbsc/include/openbsc/gprs_sgsn.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/openbsc/include/openbsc/gprs_sgsn.h b/openbsc/include/openbsc/gprs_sgsn.h index 6e7c677..6a02637 100644 --- a/openbsc/include/openbsc/gprs_sgsn.h +++ b/openbsc/include/openbsc/gprs_sgsn.h @@ -113,6 +113,9 @@ struct sgsn_mm_ctx { uint8_t t3370_id_type; }; +#define LOGMMCTXP(level, mm, fmt, args...) \ + LOGP(DMM, level, "MM(imsi=%s p-tmsi=0x%08x tlli=0x%08x) " fmt, (mm)->imsi, (mm)->p_tmsi, (mm)->tlli, ## args) + /* look-up a SGSN MM context based on TLLI + RAI */ struct sgsn_mm_ctx *sgsn_mm_ctx_by_tlli(uint32_t tlli, const struct gprs_ra_id *raid); @@ -176,6 +179,8 @@ struct sgsn_pdp_ctx { unsigned int num_T_exp; /* number of consecutive T expirations */ }; +#define LOGPDPCTXP(level, pdp, fmt, args...) \ + LOGP(DGPRS, level, "PDP(imsi=%s ti=%u) " fmt, (pdp)->mm->imsi, (pdp)->ti, ## args) /* look up PDP context by MM context and NSAPI */ struct sgsn_pdp_ctx *sgsn_pdp_ctx_by_nsapi(const struct sgsn_mm_ctx *mm, -- 1.8.4.2

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC