OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Re: IMPORTANT: Building OpenBSC with libosmocore
by Holger Freyther 23 Mar '10

23 Mar '10

On Saturday 06 March 2010 00:58:50 Harald Welte wrote: > > I think OpenBSC has been quite useful and stable for quite some time, it > would be great to make something like an 1.0 release at some point soon. > Maybe zecke and myself can do this in the next couple of weeks. Shall we pick 1.0.0 for both OpenBSC and libosmocore?

1 0

IMPORTANT: Building OpenBSC with libosmocore
by Harald Welte 22 Mar '10

22 Mar '10

Hi All Just to clarify this (since we've had another question on the ML) On Wed, Mar 03, 2010 at 10:15:44AM +0100, Holger Freyther wrote: > You are using the latest version of libosmocore but not the one of OpenBSC. You always need to use latest OpenBSC with latest libosmocore. We really cannot afford to spend more time in supporting any kind of forward/backward compatibility on a commit level. However, what we should do, is to make official releases of both the library and the OpenBSC program. OpenBSC will then require a particular version of libosmocore, and the configure script will notice if it is not available. I think OpenBSC has been quite useful and stable for quite some time, it would be great to make something like an 1.0 release at some point soon. Maybe zecke and myself can do this in the next couple of weeks. > libosmocore is a rather new library and we move stuff from OpenBSC into this > library, which means if you have a new version of libosmocore and a bit older > one of OpenBSC your compiler will see stuff twice. This will probably still be the case for the weeks to come, while even more stuff (e.g. 04.08 call control IE parsing / generation) moves into libosmocore. So please, always do a full cycle of * "git pull" on libosmocore * "git pull" on openbsc * "./configure && make install" on libosmocore * "./configure && make" on openbsc This way you'll get a consistent build. Thanks for your understanding, 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)

2 1

BS-11 multidrop problem
by till 20 Mar '10

20 Mar '10

Hi, i want to operate two BS-11 via one E1-card. And i did it almost like here: http://lists.gnumonks.org/pipermail/openbsc/2009-August/000733.html But i dont know how to configure the bport1 object for multidrop and how to use the hfcmulti module to get two interfaces (for lcr i compiled misdn_l1loop but i think this isnt the right here ;)). So atm i am not able to communicate with the second BS11 :/. Any idea? Thx & Greets Till

1 0

AW: AW: AW: AW: WG: again compilation of lcr
by Andreas.Eversberg 16 Mar '10

16 Mar '10

i thought it is the same (sorry, but i could not yet compile it myself). try changing gsm.h line 79 into: extern char gsm_conf_error[128]; or extern char gsm_conf_error[]; anyway: i hate global return values and i will change it. ________________________________ Von: Ihab el Bakri [mailto:ihab.elbakri@hotmail.com] Gesendet: Dienstag, 16. März 2010 12:33 An: Andreas.Eversberg Cc: openbsc Betreff: RE: AW: AW: AW: WG: again compilation of lcr still getting errors: gsm_conf.c:15: error: conflicting declaration âchar gsm_conf_error [128]â gsm.h:79: error: âgsm_conf_errorâ has a previous declaration as âchar* gsm_conf_errorâ make[1]: *** [gsm_conf.o] Error 1 make[1]: Leaving directory `/usr/src/test2/new/lcr' make: *** [all] Error 2 ________________________________ Hotmail: Trusted email with powerful SPAM protection. Sign up now. <https://signup.live.com/signup.aspx?id=60969>

1 0

AW: AW: AW: WG: again compilation of lcr
by Andreas.Eversberg 16 Mar '10

16 Mar '10

oops, try this: --- diff --git a/gsm_conf.c b/gsm_conf.c index 560d9b3..6daf9b3 100644 --- a/gsm_conf.c +++ b/gsm_conf.c @@ -12,7 +12,7 @@ #include "main.h" -char *gsm_conf_error = (char *)""; +char gsm_conf_error[128] = ""; /* read options * --- i never had an error in the config, so an error message never created.

2 1

AW: AW: WG: again compilation of lcr
by Andreas.Eversberg 15 Mar '10

15 Mar '10

> 000000 DEBUG (in getrulesetbyname() line 1871): ruleset main found. > Segmentation fault can you provide gnu debug? start gdb inside lcr source directory: root@isdn-tester:~# gdb GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-linux-gnu". (gdb) load and run (gdb) file lcr Reading symbols from lcr...done. (gdb) run start after crash type (gdb) where you will get a traceback. it should also say the line in code where the crash happened. (before libc was called)

2 1

AW: WG: again compilation of lcr
by Andreas.Eversberg 15 Mar '10

15 Mar '10

please try the following patch. i cannot test it right now. especially the gsm.cpp change is relevant. i hope that everything is clean now. diff --git a/bchannel.c b/bchannel.c index f49572b..baa8434 100644 --- a/bchannel.c +++ b/bchannel.c @@ -23,7 +23,7 @@ #include <netinet/in.h> #include <netdb.h> #include <sys/socket.h> -#include <mISDNif.h> +#include <mISDN/mISDNif.h> #include <mISDN/mISDNcompat.h> int __af_isdn = MISDN_AF_ISDN; diff --git a/gsm.cpp b/gsm.cpp index b2bdd6b..d8906c4 100644 --- a/gsm.cpp +++ b/gsm.cpp @@ -44,12 +44,9 @@ static struct timer_list db_sync_timer; #include "gsm_audio.h" -#undef AF_ISDN -#undef PF_ISDN -extern int AF_ISDN; -#define PF_ISDN AF_ISDN } +#include <mISDN/mISDNcompat.h> struct lcr_gsm *gsm = NULL; > symbol lookup error: /sbin/lcr: undefined symbol: AF_ISDN

2 1

Bounce action notification
by mailman＠lists.gnumonks.org 15 Mar '10

15 Mar '10

This is a Mailman mailing list bounce action notice: List: OpenBSC Member: sebastian.holter(a)wavelight.com Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.gnumonks.org.

1 0

GSM overview
by Andreas.Eversberg 14 Mar '10

14 Mar '10

hi, i just found some valuable information this weekend at www.informatik.hu-berlin.de/~goeller/isdn/ an introduction into gsm tracing in german http://www.informatik.hu-berlin.de/~goeller/isdn/DieGSMDmKanaele.pdf and the same in english http://www.informatik.hu-berlin.de/~goeller/isdn/GSMDmChannels.pdf it gives a rough history of GSM development, GSM network structure, framing, encryption, coding, and services - in just 100 pages. for me it is usefull to verify my parsing of SYSTEM INFORMATION messages. it describes traces of the most importaint messages. andreas

1 0

OpenBSC unsubscribe notification
by mailman-bounces＠lists.gnumonks.org 14 Mar '10

14 Mar '10

2b00042(a)gmx.com has been removed from OpenBSC.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC