OpenBSC

openbsc@lists.osmocom.org

12 participants
4278 discussions

Help needed with CSD/V.110 decoding
by Tobias Engel 28 Sep '12

28 Sep '12

Hi, I have been trying to implement some basic CSD functionality into openbsc. V.110 transparent mode, to be specific, since this should be the most simple to implement. At first I tried with a nanobts, but that didn't seem to work at all. Now I am using a bs-11. The two phones I use establish a connection, but they cannot exchange data and what I see on the Abis link also doesn't really make sense to me. (Needless to say everything works as expected when using the same phones on a production network.) I attached a pcap of a CSD call I made via the bs-11. The second attachment is the raw dump of the traffic frames I received from the BS-11 for _one_ of the phones. (It looks pretty much the same for the other phone.) The first idle data frames received look ok: 00000000 00 00 c5 ff ff ff ff ff fd ff ff ff ff ff ff ff 00000010 ff fd ff ff ff ff ff ff ff ff fd ff ff ff ff ff 00000020 ff ff ff fd ff ff ff ff C bits (Uplink data), D bits (all set to "1" == idle) and E bits (9.6 kbit/s) are all set as expected. But after the synchronisation phase, things start to get strange. The idle frames suddenly look like this: 00000460 00 00 8a ff ff fe fe fe fa fe fe fe fe fe fe fe 00000470 fe fa ff fe fe fe fe fe fe fe fa ff fe fe fe fe 00000480 fe fe fe fa ff fe fe fe The BTS "forgets" to set the first bit of every octet to "1" on most (but not all) octets. Also, the C bits now state that this is a 14.5kbit/s data frame. The E bits say the user rate now is 7.2 kbit/s. There are only four frames with actual payload data in the dump. These frames are at the positions I expect them to be (40600, 60520, 80440, 100400 - they were sent in intervals of 10 seconds). They look like this: 00009e90 00 00 8a ff 2b a2 fa aa 00009ea0 fa 86 02 22 22 6e fe 1a 26 fa d7 4e d6 52 36 56 00009eb0 4e d6 fa 53 36 56 4e d6 52 36 56 fa 4f d6 52 36 What has been sent by the phone is an eight byte timestamp followed by 22 bytes of 0xaa. But I only get one data frame for each of these transmissions (30 bytes of payload don't fit into one data frame), and if I parse it as V.110 data, I get these 20 bytes: 00000000 15 7d 0d 10 d5 ff 33 fb ae f5 ff ae ba ef fd ba 00000010 ef ae ba ff So no 0xaa bytes there... Does anybody have any idea what I might be doing wrong here? Thanks, -Tobias

2 2

OpenBSC unsubscribe notification
by mailman-bounces＠lists.osmocom.org 26 Sep '12

26 Sep '12

akwonghk(a)gmail.com has been removed from OpenBSC.

1 0

Re: OpenBSC Digest, Vol 45, Issue 15
by TAUFIQ WAHYUDI 25 Sep '12

25 Sep '12

@peter i have already installed libosmocore,libosmo-aabis,and openBsc,and have been clone and integrated all the items into eclipse via egit. i am a newbie in telco, does anyone in this forum know how to start up openBSC ? i do want to know how does the Box work, and really confuse how to start from.Would you guys send me a technical startup document globally, so then i have an understanding regarding this stuff Best Regards On 9/24/12, openbsc-request(a)lists.osmocom.org <openbsc-request(a)lists.osmocom.org> wrote: > Send OpenBSC mailing list submissions to > openbsc(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > 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. new comer (TAUFIQ WAHYUDI) > 2. Re: new comer (Peter Stuge) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 23 Sep 2012 21:36:30 -0700 > From: TAUFIQ WAHYUDI <taufiq.wahyudi.12(a)gmail.com> > To: openbsc(a)lists.osmocom.org > Subject: new comer > Message-ID: > <CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > hi all, > > i am new comer in this group, i already have installed openbsc until to > this step, i have problems would you mind all giving me a hand in the > future? > > thank you very much > > Best Regards >

1 1

GPRS and PDP Context
by John Otten 25 Sep '12

25 Sep '12

Good Day, I have been working with OpenBSC for the past few weeks and I am able to make voice calls and send SMS messages within the private network without issues. I am now attempting to add GPRS to the mix, and have been having less success. I have been able to make it to the internet from my phones occasionally, but in general, there appears to be an issue between osmo-sgsn and OpenGSN. My hope is that it is a simple configuration issue. However, I suspect it may be due to an issue in the code, or perhaps something mentioned last May (I have been scouring the mail archive) regarding foreign vs local TLLIs. My current setup is: One Linux workstation which runs all three pertinent executables: osmo-nitb, osmo-sgsn and ggsn. A nanoBTS 165BU (PCS1900) Two Nokia 6013b phones I am working in an RF chamber. I have some T-Mobile SIMs so, I have the network set to T-Mobile rather than the test network. I had previously been able to connect to the internet perhaps 1 in 10 times, presumably because the PDP contexts were not being created (the ggsn output would not state that it was creating a context when I tried to connect from the phone). I modified gprs_llc.c to handle the issue that Frank Maas mentioned in May, regarding llme_alloc not localizing the TLLI. Now, I can usually connect with a phone more consistently (but not always) on a fresh restart of the three executables. However, after connecting to the internet via the phone, if I cycle the power on the phone, I am usually not able to connect to the internet again. Sometimes the ggsn states that it "Received create PDP context request," and sometimes it doesn't state it when the sgsn (apparently) makes a request. At times, the ggsn reports "Received packet with no destination!!!" During these times, when I check the PDP contexts in osmo-sgsn, I get: OsmoSGSN> show pdp-context all PDP Context IMSI: 310260XXXXXXXXX, SAPI: 3, NSAPI: 5 APN: epc.tmobile.com PDP Address: IPv4 192.168.100.3 SGSN PDP Context Statistics: User Data Messages ( In): 0 (0/s 0/m 0/h 0/d) User Data Messages (Out): 0 (0/s 0/m 0/h 0/d) User Data Bytes ( In): 0 (0/s 0/m 0/h 0/d) User Data Bytes (Out): 0 (0/s 0/m 0/h 0/d) The times when the ggsn does not state that it received a create PDP context request, the "show pdp-context all" command shows nothing. My newbie guess is that osmo-sgsn is saving the state of the phone's connection (based on the IMSI?), and is not releasing or clearing it when the phone is powered off. When the phone is powered back on, it will have different connection parameters, but it will use the original parameters after retrieving them based on the IMSI. I have started to look through the code in the src/gprs directory to see if this is the case. I am wondering if anyone might have some insight into why the connection is not fully restored. Or perhaps they can offer guidance where I might begin to look in the code. I can send logs and pcap files of a typical session if anyone is interested. Thanks! John

8 20

new comer
by TAUFIQ WAHYUDI 24 Sep '12

24 Sep '12

hi all, i am new comer in this group, i already have installed openbsc until to this step, i have problems would you mind all giving me a hand in the future? thank you very much Best Regards

2 1

[PATCH] fix segfault during show running-config
by Max 22 Sep '12

22 Sep '12

--- src/vty/logging_vty.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vty/logging_vty.c b/src/vty/logging_vty.c index 6166f1f..71d926d 100644 --- a/src/vty/logging_vty.c +++ b/src/vty/logging_vty.c @@ -547,7 +547,7 @@ static int config_write_log_single(struct vty *vty, struct log_target *tgt) for (i = 0; i < osmo_log_info->num_cat; i++) { const struct log_category *cat = &tgt->categories[i]; char cat_lower[32]; - + if (!osmo_log_info->cat[i].name) continue; /* stupid old osmo logging API uses uppercase strings... */ osmo_str2lower(cat_lower, osmo_log_info->cat[i].name+1); osmo_str2lower(level_lower, log_level_str(cat->loglevel)); -- 1.7.9.5 --------------080000000307010502010601--

1 0

[PATCH] logging.c: log_parse_category_mask(), skip log category name right away if name is NULL to prevent passing a NULL ptr to strlen
by Nico Golde 22 Sep '12

22 Sep '12

--- src/logging.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/logging.c b/src/logging.c index 0816570..f368bea 100644 --- a/src/logging.c +++ b/src/logging.c @@ -167,6 +167,7 @@ void log_parse_category_mask(struct log_target* target, const char *_mask) int i = 0; char *mask = strdup(_mask); char *category_token = NULL; + size_t length, cat_length; /* Disable everything to enable it afterwards */ for (i = 0; i < osmo_log_info->num_cat; ++i) @@ -176,16 +177,17 @@ void log_parse_category_mask(struct log_target* target, const char *_mask) do { for (i = 0; i < osmo_log_info->num_cat; ++i) { char* colon = strstr(category_token, ","); - int length = strlen(category_token); - int cat_length = strlen(osmo_log_info->cat[i].name); + + if (!osmo_log_info->cat[i].name) + continue; + + length = strlen(category_token); + cat_length = strlen(osmo_log_info->cat[i].name); /* Use longest length not to match subocurrences. */ if (cat_length > length) length = cat_length; - if (!osmo_log_info->cat[i].name) - continue; - if (colon) length = colon - category_token; -- 1.7.10.4 --sdtB3X0nJg68CQEu--

1 0

Enabling keep-alive for sockets in libosmo-abis
by Holger Hans Peter Freyther 21 Sep '12

21 Sep '12

Dear Pablo, Daniel was adding keepalive support to the socket used to talk to the bts. This was done in commit 8c2591d95e17eb6fa868e4d886a63ac62f3ca8af of OpenBSC and somehow needs to find its way to master of OpenBSC or libosmo-abis. I think it belongs into libosmo-abis but I am not sure where exactly. Is the keepalive setting something that belongs into the e1inp_line and configuration? Do you have an idea where I should add it? thanks holger

2 1

Sept 19, 8pm / Osmocom Berlin User Group meeting
by Harald Welte 20 Sep '12

20 Sep '12

Hi all! This is the announcement for the next Osmocom Berlin meeting. Sept 19, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. 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)

2 1

ask protocol gsm
by anak galer 17 Sep '12

17 Sep '12

Hi I want asking about protocol GSM header like this. ex : /* A-bis Interface Management Messages */ NM_MT_ESTABLISH_TEI = 0x21, where it came from 0x21, explain please. anyone have more reference Thank You

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC