I have some questions:
1) When I start bsc_hack bsc_init.c first establishes OML link and
initializes the bts then it establishes RSL link and bts starts
broadcasting. However, it takes so much time to start the bts. Instead of
this I want to do the following: it establishes OML link at the beginning
and only once, then when i want to start broadcasting it establishes just
the RSL link and bts will start faster since i don't have to wait for OML
link. What should be done for this?
2) If i send one or two word messages from telnet interface it is okay. But
if i send a longer message the phone could't receive the end of the message
correctly(last words may be incomplete). Did any one encounter with this
problem? What is wrong with me?
3) Could I send SMS in which extension of the sender is text not integer.
For example, i want to send an information SMS that this is a test network.
For this purpose i want to send an SMS from 'OpenBSC'. I set the extension
of the first subscriber in database as text and tried to send the SMS but
SMS wasn't delivered. What should i do?
4) Can i add SMS externally to SMS table of database?
Thanks.
Jason
Hi Peter and others,
it seems like the situation regarding the GSM network at the Camp is
starting to become clearer every day.
I am still arguing that two relatively large BTS with circular antennas
are a good idea. Therefore, I have now applied for a test license with
the regulatory authority with the following parameters:
* six GSM 1800 ARFCN
* two antennas, circular, 18 meters above ground
* 5W output power on each ARFCN. I know one of my customers in Germany
has once managed to get a license for 5W, so I thought it is a good
bet we should get the same. It should be more than sufficient to
cover the camp.
* from August 2nd through August 15th, i.e. we have time for build-up
and can also run it one more day during shutdown of the camp
I should be receiving "Motorola Horizon Macro" BTSs with 3 to 6 TRX each
soon. They are able to drive something like >= 20W output power, way
more than we need. The only problem with those BTS is: We will need to
add the Motorola A-bis dialect to OpenBSC before the Camp, which could
be a tough task depending on how far they are off the standard A-bis
as specified in 08.58 and 12.21.
If we cannot make those BTS work, our options are somewhat limited.
1) nanoBTS based
The nanoBTS are 200mW only, so we would need a booster. Those cost
about 1000 EUR for 6W downlink power + 18dB uplink LNA. Who is going
to fund that? Also, we would need a combiner/splitter to run
something like a 3-TRX setup.
2) Ericsson RBS
I should have two RBS 2308 (4TRX each) soon, but both of them are GSM
1900. It is unlikely that we ge a license, and a lot of phones probably
don't support it. So unless they can somehow be converted to 1800
MHz units, they are not a good fit either :/
3) Siemens BS-11
All of them are GSM 900. No way to get a license in Germany, sorry.
So we basically _have to_ make the Motorola Horizon work...
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)
> I've committed some changes a couple of minutes ago (to libosmocore +
> openbsc) that make lcr compile again.
> The problem is: The query is always false, so no messages are sent to OpenBSC.
> If I comment out the if-query, everything works as expected: Calls can be made mobile originated and mobile terminated.
> However, I don't think the if-query is there without a reason.
Since there is only one (gsm-)network instance, the "gsm->network" pointer must be set to something != NULL. Then it should work
Thanx, applied both fixes. (blindly) Please try if it works.
Hi Sylvain,
do we need such a hack on top of the 27c3 branch for the upcoming camp? I will
try to create a proper patch before the start of the camp.
holger
Good morning,
I would like to use two directional antennas with a nanoBTS DCS1800.
As far as I know, first I need a duplexer to use one antenna both for RX and TX
- does anybody know a cheap model? I found only one for 500 Euros.
Second, to connect two antennas to the duplexer, I need a power splitter.
Can somebody suggest one for duplex usage?
Third, to improve indoor signal level, there are plenty offers of duplex
repeaters, but the legal situation is unclear because one might produce
distortion on ARFCNs different from his own. Again, anyone with experience?
Maybe a suggestion for a model with a fixed ARFCN setting?
Thanks,
Lennart
Hello
Our goal was to send status sms via the vty interface. But all of our
sms were cropped. In contrast sms from one MS to another MS are
displayed correctly (despite the fact, that the text at the database
contains several '@' at the end / the user_data contains several
zero-octets). Therefore i have inspect the code and found several bugs.
The main problem is that the "user_data_len" is not correctly used. As
per GSM 03.40, 9.2.3.16 TP‑User‑Data‑Length (TP‑UDL):
"If the TP‑User‑Data is coded using the GSM 7 bit default alphabet, the
TP‑User‑Data‑Length field gives an integer representation of the number
of septets within the TP‑User‑Data field to follow."
Currently the "user_data_len" contains the number of octets (returned
from gsm_7bit_encode(...) at gsm_utils.c (libosmocore)).
The big problem here is that this information is not unique, e.g.:
1.) 46 non-extension characters + 1 extension character => (46 * 7 bit +
(1 * (2 * 7 bit))) / 8 bit = 42 octets
2.) 47 non-extension characters => (47 * 7 bit) / 8 bit = 41,125 = 42 octets
3.) 48 non-extension characters => (48 * 7 bit) / 8 bit = 42 octects
But the MS has to know the correct "user_data_len" to decode the correct
number of characters.
For this reason i updated the gsm_7bit_encode() function to return the
correct number of septets. However sometimes it is needed to know the
correct number of octets (e.g. at gsm_04_11.c: gsm340_gen_tpdu(...)) =>
i added a function to gsm_utils.c named:
uint8_t get_octet_len(const uint8_t sept_len)
I have also fixed the problem, that the sms are wrongly stored /
displayed on the database. But the solution on the function
*sms_from_result(...) (at db.c) is not really "beautiful". This is
because there exists no "user_data_len" field at the database. To store
the right value for "user_data_len" (which is further needed) i have to
get the length from the "text" field. Unfortunately this is not enough.
If the text contains extension characters like {[]} etc. then the
"user_data_len" has to be bigger because these characters needs two
septets. Therefore i use a switch statement so search for these
characters. A better solution for that is to store the right
"user_data_len" to the database (on the encoding / decoding procedure).
But i don't know if this is a suitable solution for all of you (because
you have to change your database structure etc.).
Best Regards
Dennis Wehrle
Forgot the list >.<
Barnaby J Astles
---------- Forwarded message ----------
From: Barnaby Astles <bjastles(a)gmail.com>
Date: Sun, Jul 24, 2011 at 11:16
Subject: Re: Radios
To: Harald Welte <laforge(a)gnumonks.org>
Yes Think you are right ... I am just horrified at the cost of the
ip.access. I would like to get in to the project but the cost of entry is
just so enormous.
All I can do is research and hope to land on some sort of deal. Then I would
try to get a low powered temp licence and the make the case for a low
powered non-interference license to Industry Canada to deploy low cost
building/campus zones. I am kind of sick to see all the spectrum get eaten
up by the large corps and leave nothing for small companies.
Barnaby J Astles
On Sun, Jul 24, 2011 at 02:52, Harald Welte <laforge(a)gnumonks.org> wrote:
> Hi Barnaby,
>
> On Sat, Jul 23, 2011 at 01:15:49PM -0400, Barnaby Astles wrote:
> > Has any one looked at airspan radios ?
>
> I am not aware of anyone in our community having had access to those
> devices.
>
> > http://www.airspan.com/products/airharmony/
>
> it's hard to judge how easily they would integrate with OpenBSC based on
> the marketing speech says ;)
>
> I would guess that it should be fairly simple to integrate the GSM part,
> if it reuses the Abis related components from ip.access.
>
> However, they could just use some completely different parts of the
> ip.access software stack, and have something custom over the back-haul
> link.
>
> If you have an interest in OpenBSC interoperability with those units,
> I'm sure we could find a way to make it happen. My guess is that
> they would be pretty expensive, as the nanoBTS alone (without any LTE)
> is already horribly expensive.
>
> 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,
since some days I'm using an old version of OpenBSC and LCR (as suggested by
University of Freiburg) to interconnect our GSM and PSTN. We are using
Debian squeeze and a nanoBTS.
However, I would like to upgrade to a newer version of OpenBSC.
Unfortunately, no current LCR version compiles without errors such as
missing declarations etc., for example:
g++ -DHAVE_CONFIG_H -I. -DWITH_GSM_BS -I./openbsc/include
-I./libosmocore/include -I./openbsc -Wall
-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
In file included from ./openbsc/include/openbsc/rest_octets.h:4,
from ./openbsc/include/openbsc/gsm_data.h:9,
from gsm_bs.h:2,
from main.h:157,
from gsm.cpp:12:
./openbsc/include/openbsc/gsm_04_08.h:33: error: use of enum ‘gsm_chan_t’
without previous declaration
./openbsc/include/openbsc/gsm_04_08.h:33: error: invalid type in declaration
before ‘;’ token
./openbsc/include/openbsc/gsm_04_08.h:34: error: use of enum
‘gsm_chreq_reason_t’ without previous declaration
./openbsc/include/openbsc/gsm_04_08.h:34: error: invalid type in declaration
before ‘;’ token
In file included from ./openbsc/include/openbsc/gsm_data_shared.h:11,
from ./openbsc/include/openbsc/gsm_data.h:154,
from gsm_bs.h:2,
from main.h:157,
from gsm.cpp:12:
./libosmocore/include/osmocom/gsm/gsm_utils.h:62: error: expected identifier
before ‘)’ token
./libosmocore/include/osmocom/gsm/gsm_utils.h:62: error: two or more data
types in declaration of ‘parameter’
gsm.cpp: In function ‘gsm_mncc* create_mncc(int, unsigned int)’:
gsm.cpp:195: error: invalid application of ‘sizeof’ to incomplete type
‘gsm_mncc’
etc. etc.
If I manually include some header files from libosmocore and OpenBSC to LCR
and declare missing ENUMs (dirty hacks), LCR starts without a problem.
Starting osmo-nitb with -P and -m parameters, LCR can connect to MNCC
socket. But any try to start voice traffic either from or to a mobile
station results into these continuous messages:
<0006> gsm_04_08.c:2954 receive message GSM_TCH_FRAME
<0006> gsm_04_08.c:2986 TCH frame to lchan without RTP connection
<0006> gsm_04_08.c:2954 receive message GSM_TCH_FRAME
<0006> gsm_04_08.c:2986 TCH frame to lchan without RTP connection
<0006> gsm_04_08.c:2954 receive message GSM_TCH_FRAME
<0006> gsm_04_08.c:2986 TCH frame to lchan without RTP connection
.....
Furthermore, either OpenBSC ignores LCR messages or LCR does not send
messages to OpenBSC, because calls from mobile stations are signalled
through LCR to asterisk; calls from asterisk to a mobile station are
indicated by LCR but not by OpenBSC.
All configuration files of the running setup (openbsc.cfg, LCR files) are
used.
Commits...
- LCR: 39a36cb99a6dba1441a7a4b51914e0dadf3a7ae8
- libosmocore: 95f7eb288c4b8b69d61fa8d68957fb21f09e11e5
- OpenBSC: fe2d9b2fab2ae36a12411435f910efc9697d7b18 (debian branch, but same
problem with master)
Is there really no possibility at the moment to run LCR with a current
OpenBSC?
Many thanks in advance,
Lennart
This is a Mailman mailing list bounce action notice:
List: OpenBSC
Member: christoph_schueler(a)web.de
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.osmocom.org.
Hi,
this series of patches makes sure that the logs generated by
osmo_pcap_server are cleaned up. I wasn't able to use logrotate since we
wanted to keep the timestamped filenames and logrotate would treat every
log as independent.
The script now sorts the pcap logs per-client and deletes all but the
newest N files. The oldest M remaining files will be compressed with
gzip.
Some small fixes for problems I encountered are included. I hope the
requirement for libosmocore 0.3.2 is okay.
Regards,
Daniel Willmann (4):
server: Fix memory leak and error handling in restart_pcap
server: Register signal handler to reopen logfiles on SIGHUP
Catch up with API change in osmo_sock_init
contrib: Add a script to clean up in regular intervals
Makefile.am | 2 +-
configure.ac | 3 +-
contrib/Makefile.am | 1 +
contrib/clean_old | 46 ++++++++++++++++++++++++++++++++++
include/osmo-pcap/osmo_pcap_server.h | 2 +
src/osmo_client_network.c | 2 +-
src/osmo_server_main.c | 4 +++
src/osmo_server_network.c | 31 +++++++++++++++++++++-
8 files changed, 86 insertions(+), 5 deletions(-)
create mode 100644 contrib/Makefile.am
create mode 100755 contrib/clean_old
--
1.7.5.3
Hello,
here an updated version of the script that handles whitespace in filennames
properly. Thanks Holger for pointing out that such things do exist. :-)
Regards,
Daniel Willmann (1):
contrib: Add a script to clean up in regular intervals
Makefile.am | 2 +-
configure.ac | 1 +
contrib/Makefile.am | 1 +
contrib/osmo_pcap_clean_old | 47 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 50 insertions(+), 1 deletions(-)
create mode 100644 contrib/Makefile.am
create mode 100755 contrib/osmo_pcap_clean_old
--
1.7.5.3
Hi all,
I wonder what is the easiest way to make our database code async. Looking at
our tables and code we do not seem to have a very complicated use.
Problem:
libdbi makes queries to SQLite that kills performance (e.g. every
SELECT sends out pragma queries for every column to be queried). We
have a hacked up libdbi from the last congress.
We have some issues inserting new data into the database (e.g. the db
being locked). In one way or another we have some issues there
(either nitb will block, or the external process will...)
When moving to postgres and a database on a different system we will
have to deal with latencies and round trip time, but our code is sync.
Goal:
Most of our setting is 'set and forget'. We don't have complicate
transactions (e.g. we don't have two nitb's setting the LAC of a
subscriber, or wouldn't really care).
When updating the in-memory representation, we don't mind how long it
will take until it hits the disk on the remote system.
Proposal:
Also setting/storing will can remain like they are, the return value
does only mean that a request has been sent.
Only loading the subscriber, SMS, need to be asynchronous.
M1:
Change the gsm_subscriber code to load a subscriber asynchronously,
this will mostly touch the gsm48 code and the VTY area. On load one
can specify a callback.
M2:
Change the SMS code to load a SMS asynchronously, this will mostly
change the SMS queue, some parts of the SMS submit (e.g. to check if
there are still SMS to be sent) and the submit in the VTY
M3:
Probably create our own DB abstraction and provide a SQLite3 and
Postgres backend using the native API of both of them (and getting rid
of the libdbi and gdb issue)
biggest problem:
What do we do with the DB queries done from VTY that are
asynchronous, e.g to confirm a SMS has been stored? Do we care about
it? Do we turn this to a 'notification'?
comments
holger
Hi List,
i just tried to build openbsc latest checkout.
libosmocore compiles fine (checkout is also from today)
i got this error:
make[3]: Betrete Verzeichnis '/home/demo/openbsc/openbsc/src/libcommon'
CC common_vty.o
In file included from common_vty.c:26:
../../include/openbsc/vty.h:32: error: redeclaration of enumerator
‘E1INP_NODE’
/usr/local/include/osmocom/vty/command.h:77: note: previous definition
of ‘E1INP_NODE’ was here
In file included from common_vty.c:28:
../../include/openbsc/debug.h:16: error: expected identifier before ‘-’
token
In file included from ../../include/openbsc/bsc_nat.h:24,
from common_vty.c:30:
../../include/openbsc/mgcp.h: In function ‘mgcp_timeslot_to_endpoint’:
../../include/openbsc/mgcp.h:180: error: ‘DMGCP’ undeclared (first use
in this function)
../../include/openbsc/mgcp.h:180: error: (Each undeclared identifier is
reported only once
../../include/openbsc/mgcp.h:180: error: for each function it appears in.)
make[3]: *** [common_vty.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/demo/openbsc/openbsc/src/libcommon'
make[2]: *** [all-recursive] Fehler 1
make[2]: Verlasse Verzeichnis '/home/demo/openbsc/openbsc/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlasse Verzeichnis '/home/demo/openbsc/openbsc'
so libcommon failes.
is there a fix available or it is a unknown problem
thanks.
Regards axel
Hi all,
I have seen a strange OML NACK loop in OpenBSC with the ipaccess BTS. When I
restart the osmo-nitb it is working again, so I suspect somehow our state of
the BTS is corrupted.
any ideas
holger
Reset the BTS MO State on BTS bootstrap. This way we will always
test the BTS disconnect/reconnect case of the BTS.
Do not reset the administrative state of objects. The BSC might
have set these and wants to maintain them across disconnect/
reconnect. Right now this is true for the TRX state.
---
openbsc/src/libbsc/bsc_init.c | 3 +++
openbsc/src/libcommon/gsm_data_shared.c | 1 -
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/openbsc/src/libbsc/bsc_init.c b/openbsc/src/libbsc/bsc_init.c
index 1be8cb7..02a3adf 100644
--- a/openbsc/src/libbsc/bsc_init.c
+++ b/openbsc/src/libbsc/bsc_init.c
@@ -406,6 +406,9 @@ static int bootstrap_bts(struct gsm_bts *bts)
bts->si_common.ncc_permitted = 0xff;
+ /* Initialize the BTS state */
+ gsm_bts_mo_reset(bts);
+
return 0;
}
diff --git a/openbsc/src/libcommon/gsm_data_shared.c b/openbsc/src/libcommon/gsm_data_shared.c
index 58e3bed..b52d58a 100644
--- a/openbsc/src/libcommon/gsm_data_shared.c
+++ b/openbsc/src/libcommon/gsm_data_shared.c
@@ -36,7 +36,6 @@
void gsm_abis_mo_reset(struct gsm_abis_mo *mo)
{
- mo->nm_state.administrative = NM_STATE_NULL;
mo->nm_state.operational = NM_OPSTATE_NULL;
mo->nm_state.availability = NM_AVSTATE_POWER_OFF;
}
--
1.7.4.1
--------------050709080504010702000704--
I see that pretty much every vendor in GSM industry uses their own dialect in their core network products, I wonder why. What do they achieve from it while killing compatibility with other products from other companies?
Hi!
I've started to play a bit with Smatch (http://smatch.sourceforge.net/)
and fixed a number of bugs in libosmocore.
When applying it to openbsc, I get:
CC ipaccess.o
/home/laforge/projects/git/openbsc/openbsc/src/libabis/input/ipaccess.c +455 ipaccess_drop(28) info: loop could be replaced with if statement.
/home/laforge/projects/git/openbsc/openbsc/src/libabis/input/ipaccess.c +451 ipaccess_drop(24) info: ignoring unreachable code.
The point herer is: we loop over a list, but we return from the first
iteration of the loop. Zecke?
CC abis_nm.o
/home/laforge/projects/git/openbsc/openbsc/src/libbsc/abis_nm.c +810 sw_load_segment(38) warn: unsigned 'len' is never less than zero.
'len' has to be signed, I fixed that one.
CC paging.o
/home/laforge/projects/git/openbsc/openbsc/src/libbsc/paging.c +134 can_send_pag_req(25) info: ignoring unreachable code.
We have a goto statement in each possible caes (including defualt) above
it. So the return 0 will never be hit. That's ok and not a bug. But I
think the code is too convoluted this way. I think we should have one
function that just returns (sdcch/tch) based on the rsl_type and
net->pag_any_tch, and then a second function that has a simple if/else.
I'm not against goto - but I think this time it really can be avoided
easily.
CC bsc_vty.o
/home/laforge/projects/git/openbsc/openbsc/src/libbsc/bsc_vty.c +1062 show_e1ts(25) warn: variable dereferenced before check 'line'
/home/laforge/projects/git/openbsc/openbsc/src/libbsc/bsc_vty.c +1075 show_e1ts(38) warn: buffer overflow 'line->ts' 32 <= 32
/home/laforge/projects/git/openbsc/openbsc/src/libbsc/bsc_vty.c +1080 show_e1ts(43) error: potential null derefence 'line'.
fixed two of them, the third is bogus
CC db.o
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/db.c +254 db_fini(6) info: redundant null check on db_dirname calling free()
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/db.c +256 db_fini(8) info: redundant null check on db_basename calling free()
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/db.c +280 db_create_subscriber(20) warn: variable dereferenced before check 'subscr'
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/db.c +1062 sms_from_result(36) warn: 256 is more than 255 (max 'sms->user_data_len' can be) so this is always false.
fixed the first 3, the last remains as a safeguard
CC gsm_04_08.o
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/gsm_04_08.c +550 mm_rx_loc_upd_req(46) error: we previously assumed 'conn->loc_operation' could be null.
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/gsm_04_08.c +1891 gsm48_cc_rx_setup(68) error: we previously assumed 'trans->subscr' could be null.
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/gsm_04_08.c +2193 gsm48_cc_rx_connect(40) error: we previously assumed 'trans->subscr' could be null.
The first is bogus, the others need to be investigated
CC gsm_04_11.o
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/gsm_04_11.c +599 gsm340_rx_tpdu(46) error: sms_alphabet is never equal to 4294967295 (wrong type 0 - 255).
I fixed that one!
CC ussd.o
/home/laforge/projects/git/openbsc/openbsc/src/libmsc/ussd.c +54 handle_rcv_ussd(9) error: req.text[0] is never equal to 255 (wrong type -128 - 127).
CC bsc_ussd.o
/home/laforge/projects/git/openbsc/openbsc/src/osmo-bsc_nat/bsc_ussd.c +385 bsc_check_ussd(62) error: req.text[0] is never equal to 255 (wrong type -128 - 127).
This is due to 'struct ussd_request.text' being 'char', I changed it to
uint8_t.
CC bs11_config.o
/home/laforge/projects/git/openbsc/openbsc/src/utils/bs11_config.c +223 linkstate_name(5) error: buffer overflow 'bs11_link_state' 3 <= 3
/home/laforge/projects/git/openbsc/openbsc/src/utils/bs11_config.c +240 mbccu_load_name(5) error: buffer overflow 'mbccu_load' 6 <= 6
/home/laforge/projects/git/openbsc/openbsc/src/utils/bs11_config.c +905 main(34) info: ignoring unreachable code.
fixed.
CC ipaccess-firmware.o
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-firmware.c +64 ipaccess_analyze_file(26) warn: buffer overflow 'firmware_header->more_magic' 2 <= 2
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-firmware.c +64 ipaccess_analyze_file(26) warn: buffer overflow 'firmware_header->more_magic' 2 <= 3
zecke?
CC ipaccess-proxy.o
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-proxy.c +173 store_idtags(14) error: buffer overflow 'ipbc->id_tags' 255 <= 255
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-proxy.c +173 store_idtags(14) error: buffer overflow 'ipbc->id_tags' 255 <= 255
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-proxy.c +175 store_idtags(16) error: buffer overflow 'ipbc->id_tags' 255 <= 255
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-proxy.c +178 store_idtags(19) error: buffer overflow 'ipbc->id_tags' 255 <= 255
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-proxy.c +500 ipaccess_rcvmsg(66) error: buffer overflow 'ipbc->rsl_conn' 4 <= 4
/home/laforge/projects/git/openbsc/openbsc/src/ipaccess/ipaccess-proxy.c +504 ipaccess_rcvmsg(70) error: buffer overflow 'ipbc->bsc_rsl_conn' 4 <= 4
fixed
CC gprs_bssgp_util.o
/home/laforge/projects/git/openbsc/openbsc/src/libgb/gprs_bssgp_util.c +114 bssgp_tx_status(17) warn: variable dereferenced before check 'orig_msg'
fixed.
CC gb_proxy_main.o
/home/laforge/projects/git/openbsc/openbsc/src/gprs/gb_proxy_main.c +284 main(81) info: ignoring unreachable code.
bogus, sa it's jus an exit(0)
CC gprs_gmm.o
/home/laforge/projects/git/openbsc/openbsc/src/gprs/gprs_gmm.c +757 gsm48_rx_gmm_att_req(133) warn: variable dereferenced before check 'ctx'
fixed
CC gprs_sndcp.o
/home/laforge/projects/git/openbsc/openbsc/src/gprs/gprs_sndcp.c +478 sndcp_unitdata_req(37) info: ignoring unreachable code.
comment in the code says it is not reached
CC sgsn_main.o
/home/laforge/projects/git/openbsc/openbsc/src/gprs/sgsn_main.c +284 main(83) info: ignoring unreachable code.
comment in the code says it is not reached
CC sgsn_libgtp.o
/home/laforge/projects/git/openbsc/openbsc/src/gprs/sgsn_libgtp.c +504 sgsn_rx_sndcp_ud_ind(32) info: ignoring unreachable code.
fixed
CC bsc_nat.o
/home/laforge/projects/git/openbsc/openbsc/src/osmo-bsc_nat/bsc_nat.c +1553 get_next_free_bsc_id(20) info: ignoring unreachable code.
zecke?
--
- 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 Harald
Thanks for the options. I will need to look into it in a bit more detail. Which part of the code base do I need to concentrate on to get the Fr over E1 functionality?
Naveen
Hi!
After many delays on my side (it kept falling off my TODO list), I have
finally merged the daniel/controlif branch earlier today.
For those who haven't heard about it so far: It is code that allows us
to remotely get and/or set attributes of the BSC. Furthermore, it
supports traps (similar to SNMP traps).
The idea of it is to allow us to have centralized management of networks
with many OpenBSC installations, offering SNMP-like feel but without
adding the complexity of SNMP (asn.1, etc.) to OpenBSC itself.
We might at some point have an independent gateway process that exports
the attributes through real SNMP, but that mostly depensd on whether any
production networks have such a requirement or not.
The control interface is implemented either stand-alone (for osmo-nitb)
or via the regular A and A-bis/IP as an additional ip.access stream
identifier.
Thanks to Daniel for writing the code, to On-Waves for funding the
development and once again my apologies for the delays.
btw: I have done a couple of cosmetic clean up commits in addition to
Daniels branch, hopefully I didn't break anything while doign that...
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)
Hi all,
so far we do not have any statement about the licensing of the content on
our wiki. This means the default copyright rules apply: All the content is
copyrighted, and nobody has any rgiht to reproduce it at all.
I would like to propose an official license for the content in the wiki:
Create Commons CC-BY-SA. The alternative would be to go for CC-BY-NC-SA,
disallowing commercial use of the content.
I'm not certain if NC is really what we want. After all, even somebody
using OpenBSC in a commercial environment should be able to make copies
of the reference documentation we have available - as long as he will
releas the result again (which the SA part already covers).
If the major contributors to the wiki would agree to a license, I would
update the wiki accordingly.
Thanks,
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)
Is there any other way to reset a NanoBTS without building a reset dongle?
My NanoBTS is acting strangely after a segfault of OpenBSC.
I can connect and beacon my network with the BTS but it won't enable data
for some reason. It was working fine before.
Now it says something like this
<000d> input/ipaccess.c:696 accept()ed new OML link from 192.168.1.139
SET ATTR NACK CAUSE=Message cannot be performed
<000d> input/ipaccess.c:758 accept()ed new RSL link from 192.168.1.139
The NanoBTS doesn't even make a connection to the SGSN when this happens.
Thank you
I want to kno if there is a way to reset the nanobts without making the
reset dongle? ./ipaccess-config works at the moment.
I am trying to validate some functionality of a BSC that we have. The BSC will be connected via Gb interface(over E1) to an SGSN. What kind of hardware(processor/E1 card) would I need to support the SGSN ? I am mainly interested in testing ns/bssgp functionality. Thanks in advance.
Naveen
>> Can you provide some details about the BSC?
Hans if you mean what brand this is a custom BSC that our company(Hughes) developed for a customer. This BSC is connected to a customer provided SGSN via 2 E1 links.
Naveen
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
Hi!
With these patches, libosmocore, libosmo-sccp, openbsc and osmo-tetra
does not use anymore our own copy of talloc and they rely on the
standalone library that is provided by major distributors.
The osmocom-bb part is still missing, my idea is to include a copy
of libtalloc in the tree in the shared/ directory via rsync. This
patch will follow later since we can still rely on the outdated
copy of libosmocore.
Please, apply.
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
Hi Harald!
These are the two patches that I'm using to support signalling
and logging in the libraries.
The patch that adds the logging support reworks your previous
contribution so we only keep the logging subsystem in libosmocore,
instead of the full definition of the logging subsystem.
See patches descriptions for further details.
Let me know if you're OK with these changes.
Pablo Neira Ayuso (2):
signal: reserve signal subsystems >= 64 for libraries
logging: rework definition of logging subsystems for libraries
include/osmocom/core/logging.h | 22 ++++++--
include/osmocom/core/signal.h | 23 +++++++++
include/osmocom/gsm/gsm.h | 6 ++
src/gsm/Makefile.am | 2 +-
src/gsm/init.c | 22 ++++++++
src/logging.c | 107 ++++++++++++++++++++++-----------------
6 files changed, 129 insertions(+), 53 deletions(-)
create mode 100644 include/osmocom/gsm/gsm.h
create mode 100644 src/gsm/init.c
--
1.7.2.5
Hi all,
I have been working on a project involved using osmo-nitb and trying to read / send SMS by doing SQL queries directly hlr.sqlite3 in a perl program, but I cannot figure out the encode/decode process on the "user_data" field.
From "sms_from_text" function in libmsc/gsm_04_11.c, it appears to me that the content of user_data is a gsm_7bit_encode-ed of text if the SMS is sent with VTY interface. I then tried to port gsm_7bit_decode to perl and the implementation successfully decoded two test strings in libosmocore/tests/sms/sms_test.c. However it does not successfully decode any SMS user_data record in hlr.sqlite3 to the original text. The result looks like just a piece of garbled text, not even close to any human-readable text at all.
I also tried briefly to include gsm0338 decoding process, or some other perl-based implementation from CPAN, no success at all. I am currently out of ideas to try.
It will be really appreciated if anyone with similar experience can offer insight to my issue here.