February 2011 - OpenBSC - lists.osmocom.org

GPRS - local and foreign TLLIs
by Luca Melette 04 Feb '26

04 Feb '26

Hello everybody, after setting up a nanoBTS with OpenBSC/SGSN/GGSN, I had some troubles trying to connect my smartphone to the GPRS cell. Investigating the BTS-to-SGSN traffic, I saw that the frames sent by the SGSN were all marked with the same N(U) value (at LLC layer), the value was 0. With some debug, I found that the there was a mismatch in the TLLI storage, used to keep the status of attached terminals. The mentioned code is contained in gprs_llc.c, involving LL Entity functions and gprs_llc_tx_ui(). /* look-up or create the LL Entity for this (TLLI, SAPI) tuple */ lle = lle_by_tlli_sapi(msgb_tlli(msg), sapi); if (!lle) { struct gprs_llc_llme *llme; LOGP(DLLC, LOGL_ERROR, "LLC TX: unknown TLLI 0x%08x, " "creating LLME on the fly\n", msgb_tlli(msg)); llme = llme_alloc(msgb_tlli(msg)); lle = &llme->lle[sapi]; } The TX function uses the previously received TLLI to lookup for the LLE. The lle_by_tlli_sapi() performs the search, but preliminary it applies a foreign2local TLLI conversion to ensure to have a local one. Since no valid entry for the searched TLLI is found, a new one is created. And the problem is here. The new entry has the foreign TLLI. Next time the lookup fails again, and a new entry is created. This way, the counter N(U) is always reset, and the mobile do not recognize the message sequence and no attach is possible. My question is about foreign and local TLLIs. I patched the lookup, avoiding the conversion, so that the LLE is found and everything works fine... but... What is the sense of the conversion? Should the TLLI be always stored as a local one? Can this problem be solved with another foreign2local while allocating new entries? Actually, my problem has been solved with that workaround. But I'm curious to know what is the right way. Hope somebody can answer :) Thanks. Cheers, LM

5 6

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

Several questions
by jason mercury 06 Dec '12

06 Dec '12

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

4 3

spec download
by Joe Eggleston 03 Mar '11

03 Mar '11

Hi all, Maybe I'm missing something, but I haven't found an easy way to download pdf versions of all the 3gpp specs. Why would you want to do that? Well, dealing with MS-Word format is a pain. And, there's no online full-text search of all the specs. So, I threw together a quick web scraper to pull down the latest version of all the 3GPP specs from the ETSI web site in pdf format. Thought it might be useful to others - http://monkey.org/~joe/files/fetch_3gpp.py Feel free to contact me if you have any trouble using it. -Joe

2 1

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

24 Feb '11

Hi, I'm not sure how useful this patch is for others, I found it quite useful during my sms testing. See attached patch file. Cheers Nico

2 4

Timing Advance
by Nordin 24 Feb '11

24 Feb '11

Hello guys, I haven't been busy with openbsc for a while, however, I was following the mailing-list. I have the following question, is timing advance also implemented for the nanoBTS? Cause I don't really know where to look in the sources, thank you.

6 7

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