OpenBSC April 2011

openbsc@lists.osmocom.org

22 participants
37 discussions

by Konrad Meier

Hi all, I was just reading the wiki page about the nanoBTS multi-TRX setup. Two things are not clear to me. 1. What is the purpose of the "RF cable"? Is the TX port of the master BTS looped through the second BTS? Or hase every nanoBTS his own TRX/RX? I am asking because I would like to use a nanoBTS-Booster with the multi-TRX setup and therefore require a combined RF signal. 2. The example example "openbsc.cfg" configures the trx 1 as follows: timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 Is this really needed? My first idea was to configure the second trx to TCH/F only. Best regards Konrad Meier

14 years, 2 months

Any plan to fork OpenBTS and/or merge with Osmocom code?

by Fabio Pietrosanti (naif)

Hi all, this email don't want to be a provocative email but just an opinion related to the creation of value for GSM TLC stack into the opensource environment. As we know currently there are several different projects growing into the GSM (then tetra and in future 3G?) opensource ecosystem. The first "pratical" base has been OpenBTS as a simplified GSM um interface for VoIP. The second major implementations was around the osmocom project that build-up a complete and well designed GSM stack with all the modular interfaces and protocols for communications between BTS and BSC, with MSC, HLR, GGSN, SGSN and major GSM network components. Additionally, if i understood correctly osmocom is much more advanced with broad scope and better design than OpenBTS. It seems to me that OpenBTS it's almost stalled due to the "commercial fork" of the OpenSource project and only fairwaves is contributing to the opensource branch. I personally really dislike the "Commercial fork" approach where the community is used only in the early phase of the project to improve it and from a certain point the community doesn't get almost any added value. I like much more the dual-licensed approach like AGPL/Commercial (like http://pjsip.org) where all the value of the code is publicly released. However, my post was related to a question: - How complex would be, leveraging existing public OpenBTS code, to integrate into the Osmocom project? I mean, having a sort of lightweight BTS component speaking A-Bis over IP to OpenBSC like the cheap nano ip.access BTS does. For what i read now Osmocom have 2 software BTS (Osmo-BTS and Soft-BTS), communicating with the A-BIS over IP interface to OpenBSC: http://lists.gnumonks.org/pipermail/openbsc/2011-March/002529.html http://lists.gnumonks.org/pipermail/openbsc/2010-April/001508.html I've read that only a lot of time ago (2009) there was a discussion about OpenBTS to OpenBSC integration: http://lists.gnumonks.org/pipermail/openbsc/2009-October/000955.html At the current stage of development (2011), with Osmocom finally getting a Software-BTS part communicating to the Software-BSC side, how really complex it would be to integrate the GSM-um related part of OpenBTS into the project? With that approach the 'GSM-um' interface would be a very simplified module of the overall system and osmocom would completely replace OpenBTS all-in-one project. Am i right? -naif p.s. Sorry for the cross-posting, i just wanted to explain the idea and get the communities feedbacks to understand 'at which point' we are in order to think 'what would be required to be done' to achieve that goal.

14 years, 2 months

[PATCH 0/7] openbsc: cleanups for ipaccess tools (3/*)

by pablo＠gnumonks.org

From: Pablo Neira Ayuso <pablo(a)gnumonks.org> This patchset is the third in the series to cleanup code in ipaccess tools and drivers. They have been tested by bootstraping the nanoBTS successfully in a small setup with two laptops, one acting as proxy and another with osmo-nitb. They are available in the pablo/cleanups branch in openbsc git tree. BTW: I'm going to stop a bit with cleanups to add a VTY interface for ipaccess-proxy, as Harald suggested. Please, merge it! Thanks. Pablo Neira Ayuso (7): libabis: ipaccess: more robust ipaccess_idtag_name() src: more robust ipaccess_idtag_parse() libabis: ipaccess: use log instead of debug under errors in ipaccess_send() ipaccess-find: get rid of ipac_idtag_name() ipaccess-proxy: more robust option parsing and checking ipaccess-proxy: remove leftover option `--udp' ipaccess-proxy: get rid of make_gprs_sock() openbsc/include/openbsc/ipaccess.h | 2 +- openbsc/src/ipaccess/Makefile.am | 6 +++ openbsc/src/ipaccess/ipaccess-find.c | 22 +------------ openbsc/src/ipaccess/ipaccess-proxy.c | 56 +++++++++++++-------------------- openbsc/src/libabis/input/ipaccess.c | 18 ++++++---- openbsc/src/osmo-bsc_nat/bsc_nat.c | 8 ++++- openbsc/src/osmo-bsc_nat/bsc_ussd.c | 8 ++++- 7 files changed, 55 insertions(+), 65 deletions(-) -- 1.7.2.3

14 years, 2 months

wireshark: update of RSL dissector

by pablo＠gnumonks.org

From: Pablo Neira Ayuso <pablo(a)gnumonks.org> This patch includes some updates for the wireshark RSL dissector. See patch for details. This changes are available in the pablo/wireshark-rsl branch of openBSC. Please, merge it. Pablo Neira Ayuso (1): wireshark: update extension of RSL dissector with ip.access nanoBTS support wireshark/0004-rsl-ipaccess.patch | 228 ++++++++++++++++++++++--------------- 1 files changed, 134 insertions(+), 94 deletions(-) -- 1.7.2.3

14 years, 2 months

OpenBSC unsubscribe notification

by mailman-bounces＠lists.osmocom.org

so29(a)onlinehome.de has been removed from OpenBSC.

14 years, 2 months

GSM equipment auction

by Guy Taylor

Hi all Just to let everyone know about an auction that people may like to look into. Online Auction Closes 3pm* on Tuesday 19th April 2011 Extensive Electronic Test and Measurment Equipment to include Agilent /HP Telecom test, Spectrum Analysers, Frequency generators, Optical Test, Oscilloscopes, Programmable Power Supplies, Inspection Scopes, 19in Test rack syetems Equipment Transport, IT equipment and more. http://www.sweeney-kincaid.com/Sales/SaleDescription.aspx?SaleId=1640 guy

14 years, 2 months

ipaccess-config perforning tests is broken

by Holger Hans Peter Freyther

Hi Harald, I bisected this and I end at the commit that moves bsc_init.c code around and moves things to signals. Out of your head would you know if ipaccess-config needs to call some other init function or do something special? If not I will dig a bit more and come back with more details. holger

14 years, 2 months

handover errormessage

by Thomas Ansorg

hello, one abis_rsl-massage is: CONNECTION FAIL: RELEASE CAUSE=0x18(Siemens: T_MSRFPCI Expired) 01 and handover always ends in a segfault error what does that mean and how can i fix it? T.

14 years, 2 months

[PATCH 0/6] openbsc: cleanups for ipaccess tools (2/*)

by pablo＠gnumonks.org

From: Pablo Neira Ayuso <pablo(a)gnumonks.org> This patchset is the second in the series to cleanup redundant code in ipaccess tools. They have been tested by bootstraping the nanoBTS successfully in a small setup with two laptops, one acting as proxy and another with osmo-nitb. They are available in the pablo/cleanups branch in openbsc git tree. Please, merge it! Thanks. Pablo Neira Ayuso (6): ipaccess-proxy: get rid of make_listen_sock() and use make_sock() instead libabis: ipaccess: conclude new ipaccess_send_*() functions and use them libabis: ipaccess: export ipaccess_idtag_name() ipaccess-proxy: get rid of ipac_idtag_parse() libabis: ipaccess: export ipaccess_parse_unitid ipaccess-proxy: remove hardcoded IP for options `-l' and `-b' openbsc/include/openbsc/ipaccess.h | 3 + openbsc/src/ipaccess/Makefile.am | 7 +- openbsc/src/ipaccess/ipaccess-proxy.c | 188 ++++++--------------------------- openbsc/src/libabis/input/ipaccess.c | 75 +++++++++---- 4 files changed, 94 insertions(+), 179 deletions(-) -- 1.7.2.3

14 years, 2 months

[PATCH] ipaccess-proxy: remove hardcoded IP for options `-l' and `-b'

by Pablo Neira Ayuso

This patch removes the hardcoded IP addresses for options `-l' and `-b'. --- openbsc/src/ipaccess/ipaccess-proxy.c | 23 +++++++++++++++++++---- 1 files changed, 19 insertions(+), 4 deletions(-) diff --git a/openbsc/src/ipaccess/ipaccess-proxy.c b/openbsc/src/ipaccess/ipaccess-proxy.c index b6dcad1..55658cf 100644 --- a/openbsc/src/ipaccess/ipaccess-proxy.c +++ b/openbsc/src/ipaccess/ipaccess-proxy.c @@ -1120,11 +1120,19 @@ static void print_help() static void print_usage() { - printf("Usage: ipaccess-proxy\n"); + printf("Usage: ipaccess-proxy [options]\n"); } +enum { + IPA_PROXY_OPT_LISTEN_NONE = 0, + IPA_PROXY_OPT_LISTEN_IP = (1 << 0), + IPA_PROXY_OPT_BSC_IP = (1 << 1), +}; + static void handle_options(int argc, char** argv) { + int options_mask = 0; + while (1) { int option_index = 0, c; static struct option long_options[] = { @@ -1150,9 +1158,11 @@ static void handle_options(int argc, char** argv) exit(0); case 'l': listen_ipaddr = optarg; + options_mask |= IPA_PROXY_OPT_LISTEN_IP; break; case 'b': bsc_ipaddr = optarg; + options_mask |= IPA_PROXY_OPT_BSC_IP; break; case 'g': gprs_ns_ipaddr = optarg; @@ -1171,15 +1181,20 @@ static void handle_options(int argc, char** argv) break; } } + if ((options_mask & (IPA_PROXY_OPT_LISTEN_IP | IPA_PROXY_OPT_BSC_IP)) + != (IPA_PROXY_OPT_LISTEN_IP | IPA_PROXY_OPT_BSC_IP)) { + printf("ERROR: You have to specify `--listen' and `--bsc' " + "options at least.\n"); + print_usage(); + print_help(); + exit(EXIT_FAILURE); + } } int main(int argc, char **argv) { int rc; - listen_ipaddr = "192.168.100.11"; - bsc_ipaddr = "192.168.100.239"; - tall_bsc_ctx = talloc_named_const(NULL, 1, "ipaccess-proxy"); log_init(&log_info); -- 1.7.2.3 --------------020905060808020403000801--

14 years, 2 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC April 2011