OpenBSC

openbsc@lists.osmocom.org

3 participants
4155 discussions

[PATCH] sms: introduce new command to trigger the sending process for specific subscribers only

by Nico Golde

--- 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--

14 years, 4 months

AW: fix of chan_lcr / new socket interface for openbsc

by Andreas.Eversberg

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

14 years, 4 months

fix of chan_lcr / new socket interface for openbsc

by Andreas.Eversberg

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

14 years, 4 months

New utility for drawing protocol ladder diagrams

by Harald Welte

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)

14 years, 4 months

Possible error in libosmocore

by Daniel Willmann

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

14 years, 4 months

Legal usage without a carrier-licence?

by Jay R. Worthington

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

14 years, 4 months

Re:How to run openbsc on nanoBTS

by Ravi Shankar

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

14 years, 4 months

Proposed OpenBSC application interface

by Harald Welte

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)

14 years, 4 months

"Dial up networking" config

by Chris Rankine

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

14 years, 4 months

Ericsson RBS2308 support / Status on LAPD

by Harald Welte

Hi all, Some people have been working together in order to finally start with support of the Ericsson RBS2308 (and similar models) in OpenBSC. The biggest issue so far is bringing up the actualy LAPD on the E1/T1 link. It seems Ericsson is using some dynamic timeslot configuration between BSC and BTS, so unlike e.g. Siemens, you cannot explicitly configure the OML E1 timeslot on the BTS using local configuration tools. The current working assumption is: Somehow the BSC produces bit-patterns on the E1 link and uses them to let the BTS know where to start LAPD for OML. One contributor was friendly enough to do raw bit-traces of a Racal 6113 connected to the Ericsson RBS, and they look like this: Racal to BTS Initialization openbsc:/etc/dahdi# cat /dev/dahdi/1 | hexdump 0000000 aaaa aaaa aaaa aaaa aaaa aaaa aaaa aaaa * 00092e0 aaaa aaaa aaaa aaaa aaaa aaaa aaaa 55aa 00092f0 ffff ffff ffff ffff ffff ffff ffff ffff * 0009600 ffff ffff ffff ffff ffff ffff ffff 7e7e 0009610 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e * 00096b0 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 5f7e 00096c0 3e5f 49ce cfef cfcf cfcf cfcf cfcf cfcf 00096d0 cfcf cfcf cfcf cfcf cfcf cfcf cfcf cfcf * I've written a small C program to do soft-hdlc decode. * a pattern of alternating bits (0xaa) * a pattern of all-1 bits(0xff) * a sequence of FLAG symbols (01111110) * a HDLC message FA 7D 7F 4E F2, which is a TEI=62/SAPI=62 SABME (SAPI 62 / TEI62 is configured for OML on the BTS) The interesting part is: 1) this is a SABME from BSC to BTS, whereas GSM 08.56 specifically says the BTS is the TE and the BSC the NT 2) we have not seen any TEI manager related messages(L2ML) Keep alives afterwards, about every 8 seconds 001d5e0 cfcf cfcf cfcf ebcb 04e4 a805 f323 f3f3 001d5f0 f3f3 f3f3 f3f3 f3f3 f3f3 f3f3 f3f3 f3f3 * 0031630 f3f3 f2f3 f9fa 0101 086a fcfc fcfc fcfc 0031640 fcfc fcfc fcfc fcfc fcfc fcfc fcfc fcfc * 0045680 fcfc fcfc fcfc fcfc fcfc fcfc bebe 4040 0045690 825a 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f 00456a0 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f * 00596e0 3f3f 2f3f 90af 1610 8fa0 cfcf cfcf cfcf 00596f0 cfcf cfcf cfcf cfcf cfcf cfcf cfcf cfcf * 006d730 cfcf cfcf cfcf cfcf cbcf e4eb 0504 23a8 006d740 f3f3 f3f3 f3f3 f3f3 f3f3 f3f3 f3f3 f3f3 * 0081790 faf2 01f9 6a01 fc08 fcfc fcfc fcfc fcfc 00817a0 fcfc fcfc fcfc fcfc fcfc fcfc fcfc fcfc * 00957e0 fcfc fcfc fcfc befc 40be 5a40 3f82 3f3f 00957f0 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f 3f3f If you decode this, you get FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 21 AC (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) If we look at the BTS to Racal 6113 side: Initialization openbsc:/etc/dahdi# cat /dev/dahdi/1 | hexdump 0000000 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 * 000fe00 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e5e7 f3f5 000fe10 1039 f971 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 000fe20 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 * Keep Alives, every 8 seconds 0023e40 f9f9 f9f9 f9f9 f9f9 f9f9 7c7d 8080 04b5 0023e50 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e * 0037ea0 5f5f 2020 412d 9f1f 9f9f 9f9f 9f9f 9f9f 0037eb0 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f * 004bef0 9f9f 9f9f 9f9f 9f9f 979f c8d7 0b08 4750 004bf00 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 * 005ff40 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 f5e5 005ff50 02f2 d402 f911 f9f9 f9f9 f9f9 f9f9 f9f9 005ff60 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 f9f9 * 0073fa0 f9f9 f9f9 f9f9 7c7d 8080 04b5 7e7e 7e7e 0073fb0 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e * 0087ff0 7e7e 7e7e 7e7e 7e7e 7e7e 7e7e 5f7e 205f 0088000 2d20 1f41 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f 0088010 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f 9f9f * 009c050 9f9f 9f9f 979f c8d7 0b08 4750 e7e7 e7e7 009c060 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 e7e7 * Decoded, we get: FA 7D 73 60 3A (LAPD UA) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 25 25 AD 20 (LAPD unknown??) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) FA 7D 01 01 AD 20 (LAPD RR) So as a summary, it seems that 1) the BSC applies some magic pattern (0xaa / 0xff) 2) the BSC establishes the LAPD session for OML TEI/SAPI 3) there is no L2ML, contrary to lots of Ericsson Abis documentation that you can find online. We'll continue our attempts and see if we can get the OML up... -- - 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)

14 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC