OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Re: How to download firmware and configure NanoBTS the first time...
by Ravi Shankar 23 Feb '11

23 Feb '11

Nothing required actually. The firmware is preloaded.Just configure the Nanobts using the installation CD given. Some jar file is there for configuring part. > https://lists.osmocom.org/mailman/listinfo/openbsc > or, via email, send a message with subject or body 'help' to > openbsc-request(a)lists.osmocom.org > > You can reach the person managing the list at > openbsc-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenBSC digest..." > > > Today's Topics: > > 1. Re: How to download firmware and configure NanoBTS the first > time... (Harald Welte) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 16 Feb 2011 22:52:33 +0100 > From: Harald Welte <laforge(a)gnumonks.org> > Subject: Re: How to download firmware and configure NanoBTS the first > time... > To: Omar Atia <omar.atia(a)its.ws> > Cc: 'Peter Hasse' <peter.hasse(a)fokus.fraunhofer.de>, > openbsc(a)lists.osmocom.org > Message-ID: <20110216215233.GO25856(a)prithivi.gnumonks.org> > Content-Type: text/plain; charset=us-ascii > > Omar, > > how should we know in what you get your particular nanoBTS units delivered? > > You have to talk to your supplier about that. > > For all I know, it is customary for the nanoBTS to ship with pre-installed > firmware. Based on your support contract with ip.access you may receive > firmware updates from time to time, which you can then apply either using > tools from ip.access or using our ipaccess-config. Our tool is of course > not officially recognized/authorized/recommended/endorsed for this purpose. > > 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) > > > > ------------------------------ > > _______________________________________________ > OpenBSC mailing list > OpenBSC(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/openbsc > > > End of OpenBSC Digest, Vol 26, Issue 15 > *************************************** >

1 0

[PATCH] sms: introduce new command to trigger the sending process for specific subscribers only
by Nico Golde 22 Feb '11

22 Feb '11

--- openbsc/src/vty_interface_layer3.c | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-) diff --git a/openbsc/src/vty_interface_layer3.c b/openbsc/src/vty_interface_layer3.c index a575274..6cb9cbf 100644 --- a/openbsc/src/vty_interface_layer3.c +++ b/openbsc/src/vty_interface_layer3.c @@ -206,6 +206,24 @@ DEFUN(show_subscr, return CMD_SUCCESS; } +DEFUN(subscriber_send_pending_sms, + subscriber_send_pending_sms_cmd, + "subscriber " SUBSCR_TYPES " ID sms pending send", + SUBSCR_HELP "SMS Operations\n" "Send pending SMS\n") +{ + struct gsm_network *gsmnet = gsmnet_from_vty(vty); + struct gsm_subscriber *subscr = get_subscr_by_argv(gsmnet, argv[0], argv[1]); + struct gsm_sms *sms; + + sms = db_sms_get_unsent_by_subscr(gsmnet, subscr->id, UINT_MAX); + if(sms) + gsm411_send_sms_subscr(sms->receiver, sms); + + subscr_put(subscr); + + return CMD_SUCCESS; +} + DEFUN(subscriber_send_sms, subscriber_send_sms_cmd, "subscriber " SUBSCR_TYPES " ID sms send .LINE", @@ -766,6 +784,7 @@ int bsc_vty_init_extra(void) install_element(ENABLE_NODE, &smsqueue_max_cmd); install_element(ENABLE_NODE, &smsqueue_clear_cmd); install_element(ENABLE_NODE, &smsqueue_fail_cmd); + install_element(ENABLE_NODE, &subscriber_send_pending_sms_cmd); return 0; } -- 1.7.4.1 --fdj2RfSjLxBAspz7--

1 0

AW: fix of chan_lcr / new socket interface for openbsc
by Andreas.Eversberg 22 Feb '11

22 Feb '11

hi harald, i would also suggest to combine mncc.h of openbsc and osmocom-bb first, and move it to libosmocore. this way the LCR (or other mncc_socket client) does not depend on any files of openbsc and osmocom-bb, just on libosmocore. because i like to use the same socket interface for osmocom-bb, i would suggest to to put mncc_sock.c into libosmocore too, so it must not be implemented twice. then i would make lcr to be able to connect to both osmocom-bb and openbsc sockets. finally there is no more polling of file descriptor required at lcr. if you agree, can you move the code to libosmocore? i will work on the socket configuration and see what i can do with the versioning. andreas -----Ursprüngliche Nachricht----- Von: Harald Welte [mailto:laforge@gnumonks.org] Gesendet: Dienstag, 22. Februar 2011 13:22 An: Andreas.Eversberg Cc: openbsc(a)lists.gnumonks.org Betreff: Re: fix of chan_lcr / new socket interface for openbsc Andreas, thanks for integrating the mncc socket patch into lcr. I would personally like to see the following improvements: * add some (preferrable automatically computed) version to the mncc, to make sure you cannot run lcr + bsc_hack built from a different mncc.h file. We could do something like a md5sum over the header at compilation time, stored in both openbsc and lcr. Once they connect the mncc socket, they request the remote side md5-value and compare it with the local-side value. If they don't match, print an error message and exit the program. * make the socket path configurable, which is required for running multiple instances of openbsc+lcr on the same machine. If you (or anyone else on this list) happens to have some time to work on that, it would be greatly appreciated. Regards, Harald

2 1

fix of chan_lcr / new socket interface for openbsc
by Andreas.Eversberg 22 Feb '11

22 Feb '11

hi, the broken chan_lcr is now fixed in the "develop" branch of lcr git. i have tested it with asterisk 1.8.1. the locking seems to be improved in this asterisk version. i could not run it in a deadlock, as i could with asterisk 1.6. i would suggest to try this out, but please keep your current asterisk and lcr sources. if all works fine, i would like to merge the "develop" branch into the "master" branch soon. for the gsm users: the second change in the "develop" branch is the socket interface between openbsc and lcr. thanks to harald welte for providing this patch. instead of linking openbsc to lcr, openbsc runs it's own process. (using bsc_hack as usual) lcr connects to a socket of openbsc. with it, the gsm.conf became obsolte and has been removed from lcr. in order to run lcr with openbsc ("master" branch of openbsc) : bsc_hack -P -m -l <sqlite-database> -c <openbsc-config> -P is required to enable rtp proxy for use with ipaccess bts. -m is required to allow call control via socket interface to get lcr from "develop" branch, do: git-clone git://git.misdn.org/git/lcr.git/ cd lcr sh checkout-branch.sh develop regards, andreas

2 1

New utility for drawing protocol ladder diagrams
by Harald Welte 21 Feb '11

21 Feb '11

Hi! With the help of graphviz, I have written a small perl-based tool that allows you to generate ladder diagrams. It can be found at git://git.osmocom.org/gen_ladder.git For your reference, I'm attaching a sample input and output file. The bent/curved arrows are a result of graphviz trying to indicate that the message is between e.g. MS and MSC and 'bypasses' BTS and BSC. I'm still waiting for somebody with more graphviz skills to make this an option. Hope this is useful for some of you... -- - 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

Possible error in libosmocore
by Daniel Willmann 20 Feb '11

20 Feb '11

Hello, I just stumbled over the following change in libosmocore diff --git a/src/vty/Makefile.am b/src/vty/Makefile.am index 7353ab8..8d730c3 100644 --- a/src/vty/Makefile.am +++ b/src/vty/Makefile.am @@ -10,5 +10,5 @@ lib_LTLIBRARIES = libosmovty.la libosmovty_la_SOURCES = buffer.c command.c vty.c vector.c utils.c \ telnet_interface.c logging_vty.c -libosmovty_la_LIBADD = $(top_builddir)/src/libosmocore.la +libosmovty_la_LIBADD = -losmocore $(top_builddir)/src/libosmocore.la endif from commit 2822296d The -losmocore seems wrong as it is the library we're building here and it's not necessarily already installed. If I remove that part libosmocore builds for me again. Regards, Daniel Willmann

3 2

Legal usage without a carrier-licence?
by Jay R. Worthington 17 Feb '11

17 Feb '11

Hi, as probably for most of us an official (testing) licence is out of reach, is there a "workaround" for this problem? - Is there some part of the official gsm bands that overlaps with local ISM or other not-so-tightly-regulated frequencies? (i.e, GSM1900 seems to have a small part that's not used by DECT...) - Are there any "standard" gsm handsets that could be modified (preferably in software) to work at 2,4GHz? - Is UMA/GAN (http://en.wikipedia.org/wiki/Generic_Access_Network) something that could be used with OpenBSC? As far as i understand the specification, UMA is GSM Layer 3 over an GPRS/IPSEC tunnel to the BSC, so all the GSM-Goodies should be there. I realize the first two options would not exactly make it legal, but i'd prefer the wrath of my neighbors over the suicide-squad from a carrier or regulatory agency ;). Any comments? Regards, Jay

5 5

Re:How to run openbsc on nanoBTS
by Ravi Shankar 16 Feb '11

16 Feb '11

Dear sir I am new to openbsc.I have two NanoBTS(165cu).I'm facing some difficulty which I'm summarizing below I'm using Ubuntu10.04 1) Can we proceed with one nanobts.? 2)I've configured bts ip,unit id, oml ip of one bts.But not able to get the firmware. How to get it and configure for NanoBTS?? 3)how to run openbsc ?? Please suggest the procedure to run the openbsc. Thanks

4 4

Proposed OpenBSC application interface
by Harald Welte 15 Feb '11

15 Feb '11

Hi! Collin Mulliner, Tobias Engel and myself have been meeting yesterday to discuss a generic application interface for OpenBSC. They are both doing security analysis and want to achieve a clean way how an external application can get access to a more or less transparent communication channel to the phone. The purpose of this is to be able to send intentionally malformed packets to the mobile phone GSM stack at various different levels within the stack. As of now, they have both hacked some custom code into openbsc that gets them half way where they want to be - but not quite all the way. The requirements can be summarized as follows: 1) Ability to establish a SDCCH or TCH channel by paging the phone As of now, the 'silent call' feature from the VTY already does this. 2) Ability to send arbitrary layer3 protocol messages to the phone Adding this is relatively easy (use rsl_sendmsg on the lchan from the silent call) 3) Ability to receive responses from the phone, as well as error conditions such as 'readio link failure'. We don't have a solution for this yet, and we also have no clean way to identify what might be a response from the phone to the external app, and what might be a message from the phone to the normal network code in OpenBSC 4) Ability to selectively disable partial protocol handling in OpenBSC. Let's say you want to play with the mobile phone call control implementation. In this case, you want to make sure all CC related messages go from/to the external program and not from the regular OpenBSC network code. So what I've been thinking of as a solution to the problem: * store a bypass_flags bitmask related to the subscriber structure, where we indicate values such as BYPASS_RR, BYPASS_MM, BYPASS_CC, BYPASS_SAPI3. * if we process an incoming message from the MS in gsm0408_rcvmsg(), we check if a bypass flag matching the message is found. If yes, forward the message to the external program * if we want to send a message from our own protocol stack to the MS, we check if a bypass flag matching the message is found. If yes, we drop the message that we were about to send. * any messages received from the application will be forwarded to the MS The application interface protocol will likely have a close resemblance to RSL RLL. We need to exchange the following primitives with the application, like: * ESTABLISH REQUEST -- app requests a channel be established to MS (by IMSI) * ESTABLISH CONFIRM -- network confirms a channel has been established * ESTABLISH INDICATION -- network tells app connection was made by MS * [UNIT] DATA REQUEST -- app requests data to be sent to MS * [UNIT] DATA INDICATION -- network indicates data was received from MS * ERROR INDICATION -- network tells app something went wrong * RELEASE REQUEST -- app asks network to release channel * RELEASE CONFIRM -- net tells app that channel was released (as rqd) * RELEASE INDICATION -- net tells app that channel was released (by MS) The channel_number of RSL (indicating on-air timeslot) doesn't make much sense in this context, of course. The link_identifier on the other hand is great as it allows the app to indicate SDCCH/FACCH or SACCH as well as the SAPI. The actual RSL-like protocol would be encapsulated by UDP and available on a socket of the MSC. What do you think? 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 9

"Dial up networking" config
by Chris Rankine 15 Feb '11

15 Feb '11

For our ongoing experiment, we are hoping to tether some laptops onto the EDGE connection, either through a USB style dongle or a USB cord into a phone that allows it to be treated like a modem (And for some old school phones, maybe even a Serial port connection). These situations require a number to be dialed, what I believe is a USSD code, and sometimes a username and password to be entered. I am not talking about newer smart phones where the connection is sometimes shared using advanced drivers. Has anyone been able to do this with OpenBSC? Chris Rankine

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC