Hello,
second try to add support to bs11_config for bport0/1 configuration. This
time with enum abis_bs11_line_cfg.
It seems sometimes creating bport1 fails, even LMT shows create obj
greyed out. Don't know why yet.
Regards,
Daniel Willmann
Daniel Willmann (1):
Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config
openbsc/include/openbsc/abis_nm.h | 10 +++++++++-
openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++--
openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++
3 files changed, 64 insertions(+), 3 deletions(-)
I downloaded and built the latest version of openbsc/libosmocore (that's
today's version), but when running, it hangs on this part:
<0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff)
IPACCESS(0xe1): RSL CONNECT ACK IP=10.100.1.22 PORT=3003 STREAM=0x00
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) CHANGE
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG:
OP_STATE=Disabled AVAIL=Off line(03)
<0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Software
Activated Report
<0005> abis_nm.c:1770 Set TRX Attr (bts=0,trx=0)
<0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Sending OPSTART
<0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG:
OP_STATE=Disabled AVAIL=OK(ff) ADM=Unlocked
<0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Sending OPSTART
It stops there and nanoBTS keeps blinking green light.
When running an older version (without libosmocore), it works well.
Is this a familiar behaviour, any idea?
Thnx.
Hallo guys,
just a question. Did some of you can tell me the best way to connect
two different GSM cells (two nanoBTS) and build the communication
between the two of them over my IP network? Which components(Astersik,
LCR, mISDN ....)are requested for that? is it possible at all?
Thanks!!
--
Fabrice Ismael Poundeu Tchouatieu
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Hi all!
As some of you may have noticed, there are some references to GPRS in
the openbsc 'master' branch now. The code in there is sufficient to
configure a nanoBTS via OML and RSL (SI13) to establish contact with an
existing NS-over-IP capable SGSN.
All that needs to be done is to set a couple of parameters at the BTS
level in openbsc.cfg. I've documented them briefly in the wiki (VTY
reference page). Also, at least one of your timeslots have to be of
PDCH pchan type. We don't implement dynamic TCH/PDCH switching yet.
As the changes required to get this initialization/configuration done
are non-invasive, I decided to include them in the master branch right
away.
If you set 'gprs enabled 0' in your openbsc.cfg, all GPRS functionality
should be disabled.
This is of course only the first step.
The much bigger work will be in the grps-sgsn branch, where work will
continue on completing the BSSGP and LLC protocol implementations and
the actual SGSN + GGSN functionality. The goal is of course to
eliminate the need for an external SGSN/GGSN completely.
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)
Hello there,
I was reading throught the openbsc website, and its really a great project i would like to test and particiopate in.
Installed the software, the only problem is that i dont have the hardware to test it !!!
My question :
I am looking for the hardware to test it eg. for one Siemens Bs11 (since the ip.access is a bit too expensive for my pocket :) ), is there a chance to buy such device from any one ?
Who is selling this devices ?
greets
amed
_________________________________________________________________
http://redirect.gimas.net/?n=M1003xWin7Geschenk2_WW
Hol dir das Gratis-Geschenkpaket von Windows 7 für deinen PC ab!
Hi,
I have finally an idea on how to go from varpoware "oh I need to merge that" to
actually merging stuff and started to work on that.
The one goal I have is to create a BSC/MSC split inside our codebase and to
make MSC functionality only communicate via a given BSC API. This move will
allow to do some things transparently to the MSC code, it includes automatic
RLL establishes for SAPI, very early/early assignment will become transparent
and in the future I can roll out my "subscriber task" scheduler to do stuff
like SMS submit during a voice call...
Here is my plan on how to get there...
1.) Create a new structure for the MS Connection. This would happen on a GSM
0808 Complete Layer3 Information message (e.g. CM Service Request, Paging
Response). The name I picked is total rubish but can easily changed later.
I have embedded this connection into the struct gsm_lchan and moved all MSC
attributes into this new structure. So right now we have a 1:1 mapping between
a GSM LCHAN and the Subscriber Connection.
2.) Moved transaction code to work on this new structure instead of the lchan,
I verified MT-SMS, MO-SMS, MT-Call, MO-Call. So the plan is to remove the
occurence of GSM LCHAN from the MSC code paths, this will also mean to remove
direct calls to RSL, RLL, paging.c.
3.) I picked gsm_04_11.c as the first file from the MSC (actually SMSC) code to
go without the lchan. I have removed the direct call to RSL and placed it
behind a new GSM0808 DTAP API. This would be the place where we figure out the
real LCHAN..
This is all working and I can build on top of that until I reach the goal at
which point I can forward port some of my code from the On Waves branch and
instead of playing MSC myself, put it into SCCP...
<- now comes the stuff that I want to complete by the end of next month ->
4.) Currently when compiling you see a "BROKEN" warning, this is more that it
is broken conceptually as the code handles paging and RLL establishment by
itself. So the idea will be to move my "bssap.c" code to master and handle the
RLL establishment and paging inside the new BSC API. This would involve
queuing of messages...
5.) Remove the callback for SMS from abis_rsl.c and create a bsc_api_init with
callbacks for various things (mostly Create Connection, Clear Request, Data).
At this point the gsm_04_11.c will be free of BSC code.
6.) Move it to gsm_04_08. This will involve adding new commands (resembling
the GSM 08.08) message names, sharing some callbacks between SAPI=0 and SAPI=3
and having a dispatch. E.g. later we should have a handler for new connection
which would run authentication and then dispatch the handling of the
connection to a task, on task completion close the channel or give it to the
next task. After this we should magically be able to switch between very
early/early assignment in the BSC code and the MSC will not recognize this,
also TCH/H handling with be mostly transparent.
7.) Remove the 1:1 mapping of of GSM LChan to the new struct. Actually the new
struct should include two lchan's (in case of handover or assignment), I will
have to figure out on how to marry the handover code with that...
8.) I could rebuild my bsc_msc_ip.c on top of the new BSC API and all I need
to do is to handle MSC. We could also create a msc_bsc_ip.c which takes these
SCCP messages and sticks it into the MSC code of ours and we have a MSC.
as usual... any help is more than welcome.
z.
Hi!
I don't exactly remember in which context I was last communicating with
whom of you about the question whether or not the BA of a cell should
include its own BCCH frequency or not.
I think from commercial networks we could see both behaviors, and it was
thus unclear what we should do for OpenBSC.
I've now found a reference for this in the GMS specs: GSM 3.22 Chapter
4.8:
> NOTE: The PLMN operator cannot expect the ME to store the BCCH or
> CPBCCH carrier frequency of the serving cell in the SIM unless the
> BA(BCCH) includes the BCCH or CPBCCH carrier frequency on which it is
> broadcast.
So now we know at least the difference when it comes to those two
options.
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)
Hello Harald,
On Sun, 28 Mar 2010 13:16:36 +0800, "Harald Welte" <laforge(a)gnumonks.org> wrote:
>
> as far as I know, it has to change on every retransmission. Dieter is
> probably the person who knows all RACH aspects in detail, maybe he can
> comment on this.
According to the specification the random value has to change on every
transmission:
a random reference which is drawn randomly from a uniform probability
distribution for every new transmission.
In the TSM30 firmware this is done by having a table with random values
and an index into the table which is initialised to a random value when
the Immediate Assignment Procedure is started and incremented with every
random number taken for a retransmission. The table has 32 values because
the random reference is not larger than 5 bits.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi Andreas,
some comments regarding your issues.txt:
> must random value in chan_request change on every resend or only on
> every RR establishment? (currently it changes on every RR
> establishment only.)
as far as I know, it has to change on every retransmission. Dieter is
probably the person who knows all RACH aspects in detail, maybe he can
comment on this.
> must be expanded: struct osmocom_ms:
no problem here, expand it how you see fit. I just generally prefer
caller-allocated structures to callee-allocated ones, and I'd like to
use static allocation whenever possible. So if there's only one 'struct
rrlayer' per ms, then we should simply include 'struct rrlayer' as
sub-structure of 'struct osmocom_ms', rather than having two structures
and pointers between them.
> OpenBSC: if tx-msg fails during process, the msg must be freed to
> avoid memory leak.
I don't understand, can you please explain this further?
> random acces via RSL?
I think we simply add some new / non-standard primitives, as it does not
have any notion of RACH bursts.
It might also be possible to encode it as UNIT DATA REQUEST for channel
(chan_nr) RACH (CCCH uplink), but then we still cannot specify details
like at which frame number, etc. From what I can see, your
RSL_MT_RAND_ACC_REQ approach looks fine to me. As a minor improvement
we could call it RSLms_MT_RAND_ACC_REQ to indicate that it is our custom
RSLms message and nothing specified in the original RSLms spec.
Cheers,
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)
Hi!
One of the bigger missing parts in libosmocore is the debug support that
we have in OpenBSC, including support for multiple debug categories,
log levels, log targets, filters, context, etc.
I'm currently half-way through splitting/generalizing the core code from
the OpenBSC specific bits (like IMSI context/filter). It's coming along
quite nicely - actually less of a problem than I originally thought.
The purpose of this is (as usual) to enable OsmocomBB to use the same
codebase as OpenBSC for logging/debugging.
So this mail is simply a heads-up that some changes will be visible in
this area, once again requiring you to update + build libosmocore and
OpenBSC after the changes have been committed.
The good news, at least it should fail gracefully now, as the OpenBSC
autotools magic is now requesting a certain libosmocore version during
./configure.
Cheers,
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)
Hi,
i have a problem with bs11_config. When i start it, i get this:
---------------------------------------------------------
# ./bs11_config -p /dev/ttyS0 /path/to/BTSBMC76.SWI
bs11_config (C) 2009 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
Invalid length in hdr: 0
Speicherzugriffsfehler
---------------------------------------------------------
Thanks
Marcus
--
Marcus Specht
open|MVNO
c/o Cyber-Dynamix Gesellschaft für Systemintegration GmbH
Heiner-Stuhlfauth-Str. 28
90480 Nürnberg
Tel.: 0911 / 1809105
Fax.: 0911 / 1809109
Geschäftsführer: Heiko Thierbach, Gerhard Feder
Sitz der Gesellschaft ist Nürnberg
Amtsgericht Nürnberg, HRB 16704
Ust-Id.-Nr. DE204640808
------------------------------------------------------------------------------
Diese Nachricht ist eine nicht öffentliche Mitteilung.
Sollten Sie diese Nachricht versehentlich erhalten haben
und nicht der gewünschte Empfänger sein,
so bitten wir Sie, diese Nachricht zu löschen, keine
Kopien anzufertigen und nicht weiterzuleiten. Bitte
informieren Sie uns per eMail über den Zustellungsfehler
und entschuldigen Sie die Unannehmlichkeit.
Bitte beachten Sie: Unabhängig vom Inhalt stellt diese
Nachricht keinerlei vertragliche Verpflichtung,
Zusicherung, Bestellung, Angebot oder ähnliches dar,
solange keine schriftliche Bestätigung von uns vorliegt.
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?
Hi,
I have downloaded and compiled both libosmocore and OpenBSC. However, when
I try to execute an OpenBSC program (for example ipaccess-find) I see the
following error
~/openbsc/openbsc/src# ./ipaccess-find eth0
./ipaccess-find: error while loading shared libraries: libosmocore.so.0:
cannot open shared object file: No such file or directory
could you help me. Thanks.
Ahmet
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?
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)
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
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>
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.
> 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)
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.
>. /lcr: symbol lookup error: ./lcr: undefined symbol: init_af_isdn
pull lcr again. the mISDNuser header paths have changed. i changed more
stuff.
also try to remove the /usr/include/mISDNuser directory. it is obsolete.
now compat_af_isdn.h can be removed from openbsc also. todo so, replace
the include of this file by:
#include <mISDN/mISDNcompat.h>
int __af_isdn = MISDN_AF_ISDN;
maybe it is better to use "static int", so it will not conflict when
linking to lcr... we will see.
the function call init_af_isdn(); can be removed.
> am still getting this error:
try the patch i added to my last mail. it is not yet committed to GIT.
go into your osmocore GIT directiory, say "patch -p1" and paste the
following. (end with CTRL+d)
----
diff --git a/include/osmocore/gsm48.h b/include/osmocore/gsm48.h
index 6356379..787cdd0 100644
--- a/include/osmocore/gsm48.h
+++ b/include/osmocore/gsm48.h
@@ -6,7 +6,7 @@
extern const struct tlv_definition gsm48_att_tlvdef;
extern const char *cc_state_names[32];
-const char *gsm48_cc_msg_names[0x40];
+extern const char *gsm48_cc_msg_names[0x40];
const char *rr_cause_name(uint8_t cause);
void gsm48_generate_lai(struct gsm48_loc_area_id *lai48, uint16_t mcc,
----
hi,
now after changing code of lcr, it compiles with libosmocom and openbsc.
all packets are the latest (mISDN, mISDNuser, libosmocom, openbsc, lcr)
i have started it without crashing, but i could not test it. please
change to "develop" branch of LCR.
be sure to add links to openbsc and libosmocore to the LCR source
directories:
libosmocore -> ../libosmocore/
openbsc -> ../openbsc/openbsc/
also i found some little problems while compiling osmocore and openbsc:
the 'extern' is missing:
diff --git a/include/osmocore/gsm48.h b/include/osmocore/gsm48.h
index 6356379..787cdd0 100644
--- a/include/osmocore/gsm48.h
+++ b/include/osmocore/gsm48.h
@@ -6,7 +6,7 @@
extern const struct tlv_definition gsm48_att_tlvdef;
extern const char *cc_state_names[32];
-const char *gsm48_cc_msg_names[0x40];
+extern const char *gsm48_cc_msg_names[0x40];
const char *rr_cause_name(uint8_t cause);
void gsm48_generate_lai(struct gsm48_loc_area_id *lai48, uint16_t mcc,
an here is a warning i did not analyse yet:
/usr/lib/gcc/i686-pc-linux-gnu/4.3.4/../../../../i686-pc-linux-gnu/bin/l
d: Warning: size of symbol `rsl_rlm_cause_strs' changed from 8 in
./openbsc/src/libbsc.a(abis_rsl.o) to 120 in
/usr/local/lib/libosmocore.so
regards,
andreas
hi holger,
i still can't see it.
regards,
andreas
>git pull in libosmocore please. We are still moving stuff out of
OpenBSC into
>libosmocore and if you update the one you should update the other. My
>libosmocore contains a mncc.h file.
root@nuedel libosmocore # git pull
Already up-to-date.
root@nuedel libosmocore # ls include/osmocore/ -R
include/osmocore/:
Makefile bitvec.h gsm_utils.h msgb.h rxlev_stat.h
statistics.h tlv.h
Makefile.am comp128.h gsmtap.h protocol select.h talloc.h
utils.h
Makefile.in gsm48.h linuxlist.h rsl.h signal.h timer.h
write_queue.h
include/osmocore/protocol:
Makefile Makefile.am Makefile.in gsm_04_08.h gsm_04_11.h
gsm_04_80.h gsm_08_58.h gsm_12_21.h
hi,
i got some problems with missing mncc.h at osmocore include directory. i
am in the master branch. any idea?
thanx,
andreas
make[2]: Entering directory `/root/gsm/openbsc/openbsc/src'
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -I/usr/local/include/
-g -O2 -MT abis_rsl.o -MD -MP -MF .deps/abis_rsl.Tpo -c -o abis_rsl.o
abis_rsl.c
In file included from ../include/openbsc/gsm_data.h:46,
from abis_rsl.c:31:
../include/openbsc/mncc.h:29:27: error: osmocore/mncc.h: No such file or
directory
In file included from ../include/openbsc/gsm_data.h:46,
from abis_rsl.c:31:
../include/openbsc/mncc.h:122: error: field 'bearer_cap' has incomplete
type
../include/openbsc/mncc.h:123: error: field 'called' has incomplete type
../include/openbsc/mncc.h:124: error: field 'calling' has incomplete
type
../include/openbsc/mncc.h:125: error: field 'redirecting' has incomplete
type
../include/openbsc/mncc.h:126: error: field 'connected' has incomplete
type
../include/openbsc/mncc.h:127: error: field 'cause' has incomplete type
../include/openbsc/mncc.h:128: error: field 'progress' has incomplete
type
../include/openbsc/mncc.h:129: error: field 'useruser' has incomplete
type
../include/openbsc/mncc.h:130: error: field 'facility' has incomplete
type
../include/openbsc/mncc.h:131: error: field 'cccap' has incomplete type
../include/openbsc/mncc.h:132: error: field 'ssversion' has incomplete
type
make[2]: *** [abis_rsl.o] Error 1
make[2]: Leaving directory `/root/gsm/openbsc/openbsc/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/gsm/openbsc/openbsc'
make: *** [all] Error 2
Hello guys,
I installed a newly fresh Debian Lenny, downloaded openbsc project using
git. But when running ./configure after autoreconf -i (which went well), I
get the following message:
./configure: line 3551: syntax error near unexpected token `LIBOSMOCORE,'
./configure: line 3551: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)'
I know the osmocomBB project has a bit of the focus now and that some
sources in openbsc are also used in osmocomBB, hence the libosmocore? But
can someone helping me out to get the openbsc build?
Thank you.
Hi,
I have the OpenBSC up and running with a nanobts at 900MHz.
I would require some help with the following issues.
1) I'm able to view most of the air interface messages on wireshark but not
able to
view the gsm system information blocks. Is there any patches I should add on
wireshark and is it possible
to provide instructions on how to apply the patches ?
2) I'm able to see the rrlp request made to the mobile on wireshark. However
I'm not
see any rrlp response from the mobile on wireshark. I'm sure my mobile
suppot ms-based rrlp request.
Again, what are the patches to wireshark I should apply? Appreciate if
details on how to apply the patches
are provided.
3) I have copied out the gprs branch and am able to run the gprs OpenBSC
codes without any problems.
Just that at this stage, my mobile (i-phone 3Gs) does not seem to be able to
do a gprs attach and have
the OpenBSC allocate it a P-TMSI. Is there any thing I should do to get my
i-phone 3Gs to do a gprs attach on the
OpenBSC? (For my i-phone 3Gs, the settings is gsm mode only)
4) Also in the OpenBSC folder, there's this rrlp-ephemeris folder, if
possible, would like to have further details on
the purpose of the rrlp-ephemeris folder.
Appreciate any kind advise and help.
Thanks so much
Ken
Hello,
I am getting some errors when trying to compile lcr with asterisk and gsm. error:
g++ -DHAVE_CONFIG_H -I. -DWITH_GSM -I./openbsc/include -Wall -I/usr/include/mISDNuser -DCONFIG_DATA="\"/usr/local/lcr\"" -DSHARE_DATA="\"/usr/local/lcr\"" -DLOG_DIR="\"/usr/local/lcr\"" -DEXTENSION_DATA="\"/usr/local/lcr/extensions\"" -g -O2 -MT gsm.o -MD -MP -MF .deps/gsm.Tpo -c -o gsm.o gsm.cpp
gsm.cpp: In member function âvoid Pgsm::bchannel_send(unsigned int, unsigned int, unsigned char*, int)â:
gsm.cpp:228: error: overloaded function with no contextual type information
make[1]: *** [gsm.o] Error 1
make[1]: Leaving directory `/home/bs11/bs11/lcr'
make: *** [all] Error 2
Best regards
Ihab El Bakri
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
https://signup.live.com/signup.aspx?id=60969
On 02-Mar-10 3:12 PM, Bjarni S. Sigurðsson wrote:
> Also, you can check if PKG_CHECK_MODULES is defined in aclocal.m4.
>>> grep PKG_CHECK_MODULES aclocal.m4
>
> Should get a line with "AC_DEFUN([PKG_CHECK_MODULES],". If not then
> there is something "wrong" with the autoconf setup, or you are missing
> the pkg.m4 file which should come with the pkg-config package.
>
> -BSS
Thanks for putting in so much effort for me.
There were multiple problems in my freshly installed "lenny" :)
There was no libosmocore. So downloaded
(git://git.osmocom.org/libosmocore.git) and started compiling. Ran into
problem of some a4 errors and installed gettext with apt-get. Then there
was problem of libtool missing. So installed libtool with apt-get.
Finally compiled and installed libosmocore.
After solving the above issues came back to openbsc -
Now the autoreconf -i is cleanly executed.
The ./configure step is also clean and same as your output.
The make step is *breaking* now with errors as below :-
Making all in src
make[2]: Entering directory `/root/openbsc/openbsc/src'
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -I/usr/local/include/
-g -O2 -MT abis_rsl.o -MD -MP -MF .deps/abis_rsl.Tpo -c -o abis_rsl.o
abis_rsl.c
In file included from ../include/openbsc/gsm_data.h:59,
from abis_rsl.c:31:
/usr/local/include/osmocore/utils.h:8: error: redefinition of âstruct
value_stringâ
make[2]: *** [abis_rsl.o] Error 1
make[2]: Leaving directory `/root/openbsc/openbsc/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/openbsc/openbsc'
make: *** [all] Error 2
Any guesses what else to fix ?
with Regards,
ASHWIN
On 03-Mar-10 5:05 PM, Ihab el Bakri wrote:
> Hello Ashwin,
>
>
> Checkout the attached file.. ./configure && make && make install
>
Hi Ihab,
Extracted the rar file in /root/temp/
The "make" breaks as below.
with Regards
ASHWIN
tiny:~/temp# ./configure
-bash: ./configure: Permission denied
tiny:~/temp# ls -l con
config config.log config.status configure
configure.in convert_to_enum.py
tiny:~/temp# chmod 755 configure
tiny:~/temp# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking for library containing crypt... -lcrypt
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking if gcc supports -fvisibility=hidden... yes
configure: creating ./config.status
config.status: creating openbsc.pc
config.status: creating liblaf0rge1.pc
config.status: creating libsccp.pc
config.status: error: cannot find input file: `include/openbsc/Makefile.in'
tiny:~/temp# make
mkdir -p asn1_gen && \
cd asn1_gen && \
../../../tmp/rrlp/asn1c/asn1c/asn1c -fskeletons-copy
-fnative-types -gen-PER
/bin/sh: line 2: ../../../tmp/rrlp/asn1c/asn1c/asn1c: No such file or
directory
make: *** [libgsm-asn1.a] Error 127
tiny:~/temp#
Hello,
I am looking for a couple of BS-11/nanoBTS Units 10 and more, price is not a problem, so if any body has a BS-11 or an ip.access nanoBTS to sell, please contact me immediately :)
Best regards
Ihab El Bakri
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
Hi,
Tried to compile and got some errors at the ./configure stage.
./configure: line 3551: syntax error near unexpected token `LIBOSMOCORE,'
./configure: line 3551: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)'
Can some one help ?
with Regards,
ASHWIN