OpenBSC

openbsc@lists.osmocom.org

12 participants
4278 discussions

[PATCH] ipaccess: relax default behaviour on errors coming from signalling layer
by Pablo Neira Ayuso 16 Oct '12

16 Oct '12

This patch relaxes the behaviour on error coming from the signalling layer. This is probably too strict for recoverable errors. Don't release msgb in this case, as this is controled by the signaling link layer. Thanks to Lennart M�ller <mueller.lennart(a)googlemail.com> for the report. --- src/input/ipaccess.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/input/ipaccess.c b/src/input/ipaccess.c index d63e796..c0c307e 100644 --- a/src/input/ipaccess.c +++ b/src/input/ipaccess.c @@ -450,10 +450,13 @@ static int handle_ts1_read(struct osmo_fd *bfd) goto err_msg; } if (e1i_ts->line->ops->sign_link(msg) < 0) { + /* Don't close the signalling link if the upper layers report + * an error, that's too strict. BTW, the signalling layer is + * resposible for releasing the message. + */ LOGP(DLINP, LOGL_ERROR, "Bad signalling message," "sign_link returned error\n"); ret = -EINVAL; - goto err; } return 0; -- 1.7.10.4 --ibTvN161/egqYuK8--

1 0

[PATCH] Allow setting of Control Channel Description parameters via VTY
by Andreas Eversberg 13 Oct '12

13 Oct '12

--- openbsc/src/libbsc/bsc_init.c | 8 ++-- openbsc/src/libbsc/bsc_vty.c | 59 ++++++++++++++++++++++++++++++++++++++ openbsc/src/libcommon/gsm_data.c | 3 ++ 3 files changed, 66 insertions(+), 4 deletions(-) diff --git a/openbsc/src/libbsc/bsc_init.c b/openbsc/src/libbsc/bsc_init.c index 2533aa7..f5d7969 100644 --- a/openbsc/src/libbsc/bsc_init.c +++ b/openbsc/src/libbsc/bsc_init.c @@ -421,10 +421,7 @@ static int bootstrap_bts(struct gsm_bts *bts) "GSM networks and should only be used in a RF " "shielded environment such as a faraday cage!\n\n"); - /* Control Channel Description */ - bts->si_common.chan_desc.att = 1; - bts->si_common.chan_desc.bs_pa_mfrms = RSL_BS_PA_MFRMS_5; - bts->si_common.chan_desc.bs_ag_blks_res = 1; + /* Control Channel Description is set from vty/config */ /* T3212 is set from vty/config */ @@ -435,6 +432,9 @@ static int bootstrap_bts(struct gsm_bts *bts) switch (n) { case 0: bts->si_common.chan_desc.ccch_conf = RSL_BCCH_CCCH_CONF_1_C; + /* Limit reserved block to 2 on combined channel */ + if (bts->si_common.chan_desc.bs_ag_blks_res > 2) + bts->si_common.chan_desc.bs_ag_blks_res = 2; break; case 1: bts->si_common.chan_desc.ccch_conf = RSL_BCCH_CCCH_CONF_1_NC; diff --git a/openbsc/src/libbsc/bsc_vty.c b/openbsc/src/libbsc/bsc_vty.c index b91304d..61b0911 100644 --- a/openbsc/src/libbsc/bsc_vty.c +++ b/openbsc/src/libbsc/bsc_vty.c @@ -256,6 +256,12 @@ static void bts_dump_vty(struct vty *vty, struct gsm_bts *bts) VTY_NEWLINE); if (bts->si_common.rach_control.cell_bar) vty_out(vty, " CELL IS BARRED%s", VTY_NEWLINE); + vty_out(vty, "Channel Description Attachment: %s%s", + (bts->si_common.chan_desc.att) ? "yes" : "no", VTY_NEWLINE); + vty_out(vty, "Channel Description BS-PA-MFRMS: %u%s", + bts->si_common.chan_desc.bs_pa_mfrms + 2, VTY_NEWLINE); + vty_out(vty, "Channel Description BS-AG_BLKS-RES: %u%s", + bts->si_common.chan_desc.bs_ag_blks_res, VTY_NEWLINE); vty_out(vty, "System Information present: 0x%08x, static: 0x%08x%s", bts->si_valid, bts->si_mode_static, VTY_NEWLINE); if (is_ipaccess_bts(bts)) @@ -496,6 +502,13 @@ static void config_write_bts_single(struct vty *vty, struct gsm_bts *bts) rach_max_trans_raw2val(bts->si_common.rach_control.max_trans), VTY_NEWLINE); + vty_out(vty, " channel-descrption attach %u%s", + bts->si_common.chan_desc.att, VTY_NEWLINE); + vty_out(vty, " channel-descrption bs-pa-mfrms %u%s", + bts->si_common.chan_desc.bs_pa_mfrms + 2, VTY_NEWLINE); + vty_out(vty, " channel-descrption bs-ag-blks-res %u%s", + bts->si_common.chan_desc.bs_ag_blks_res, VTY_NEWLINE); + if (bts->rach_b_thresh != -1) vty_out(vty, " rach nm busy threshold %u%s", bts->rach_b_thresh, VTY_NEWLINE); @@ -1770,6 +1783,49 @@ DEFUN(cfg_bts_rach_max_trans, return CMD_SUCCESS; } +#define CD_STR "Channel Description\n" + +DEFUN(cfg_bts_chan_desc_att, + cfg_bts_chan_desc_att_cmd, + "channel-descrption attach (0|1)", + CD_STR + "Set if attachment is required\n" + "Attachment is NOT required\n" + "Attachment is required (standard)\n") +{ + struct gsm_bts *bts = vty->index; + bts->si_common.chan_desc.att = atoi(argv[0]); + return CMD_SUCCESS; +} + +DEFUN(cfg_bts_chan_desc_bs_pa_mfrms, + cfg_bts_chan_desc_bs_pa_mfrms_cmd, + "channel-descrption bs-pa-mfrms <2-9>", + CD_STR + "Set number of multiframe periods for paging groups\n" + "Number of multiframe periods for paging groups\n") +{ + struct gsm_bts *bts = vty->index; + int bs_pa_mfrms = atoi(argv[0]); + + bts->si_common.chan_desc.bs_pa_mfrms = bs_pa_mfrms - 2; + return CMD_SUCCESS; +} + +DEFUN(cfg_bts_chan_desc_bs_ag_blks_res, + cfg_bts_chan_desc_bs_ag_blks_res_cmd, + "channel-descrption bs-ag-blks-res <0-7>", + CD_STR + "Set number of blocks reserved for access grant\n" + "Number of blocks reserved for access grant\n") +{ + struct gsm_bts *bts = vty->index; + int bs_ag_blks_res = atoi(argv[0]); + + bts->si_common.chan_desc.bs_ag_blks_res = bs_ag_blks_res; + return CMD_SUCCESS; +} + #define NM_STR "Network Management\n" DEFUN(cfg_bts_rach_nm_b_thresh, @@ -2942,6 +2998,9 @@ int bsc_vty_init(const struct log_info *cat) install_element(BTS_NODE, &cfg_bts_challoc_cmd); install_element(BTS_NODE, &cfg_bts_rach_tx_integer_cmd); install_element(BTS_NODE, &cfg_bts_rach_max_trans_cmd); + install_element(BTS_NODE, &cfg_bts_chan_desc_att_cmd); + install_element(BTS_NODE, &cfg_bts_chan_desc_bs_pa_mfrms_cmd); + install_element(BTS_NODE, &cfg_bts_chan_desc_bs_ag_blks_res_cmd); install_element(BTS_NODE, &cfg_bts_rach_nm_b_thresh_cmd); install_element(BTS_NODE, &cfg_bts_rach_nm_ldavg_cmd); install_element(BTS_NODE, &cfg_bts_cell_barred_cmd); diff --git a/openbsc/src/libcommon/gsm_data.c b/openbsc/src/libcommon/gsm_data.c index 8b030e9..352700a 100644 --- a/openbsc/src/libcommon/gsm_data.c +++ b/openbsc/src/libcommon/gsm_data.c @@ -405,6 +405,9 @@ struct gsm_bts *gsm_bts_alloc_register(struct gsm_network *net, enum gsm_bts_typ bts->si_common.rach_control.tx_integer = 9; /* 12 slots spread - 217/115 slots delay */ bts->si_common.rach_control.max_trans = 3; /* 7 retransmissions */ bts->si_common.rach_control.t2 = 4; /* no emergency calls */ + bts->si_common.chan_desc.att = 1; /* attachment required */ + bts->si_common.chan_desc.bs_pa_mfrms = RSL_BS_PA_MFRMS_5; /* paging frames */ + bts->si_common.chan_desc.bs_ag_blks_res = 1; /* reserved AGCH blocks */ llist_add_tail(&bts->list, &net->bts_list); -- 1.7.3.4 --------------090206010508020805000207--

1 0

Analysing the communication between the BSC and the MSC in a sysmoBTS
by Yann R. Moupinda 10 Oct '12

10 Oct '12

Hello everyone, thanks for the ideas you gave me about how i can learn more about the communication between BSC and MSC in my sysmoBTS. Since last week i've been looking at the source codes and it's still difficult for me to follow the exchanged messages betwenn BSC and MSC. I don't have high programming skills. Instead of using sysmoBTS as an autonomous self-contained GSM network (NITB mode), i'd like to configure it in the BSC-only mode running the osmo-bts and osmo-bsc. I read that i will need a MSC that can provide an A-over-IP interface using SCCP-lite. I saw that the "on-waves/bsc-master" branch is implementing such a SCCP and works have been done to create a GSM0808 like API and move the MSC code inside OpenBSC over to use this API. So i was wondering how far this project has been developed yet. Do you already have any interesting results that can help me? If not, it can be also interesting for me to know how you did your tests by implementing the bsc-only mode (osmo-bsc)? Did you connect it to a real MSC or did you have anything else emulating the MSC/HLR/VLR/EIR functions? Best regards Yann

2 1

Oct 3, 8pm / Osmocom Berlin User Group meeting?
by Nico Golde 09 Oct '12

09 Oct '12

Hi all! I *think* Harald is pretty busy and also unlikely to attend prospective meeting tomorrow. Also there is bank holiday tomorrow in Germany and at least I personally will use that to stay away from technology for a bit, so I won't come. Nevertheless, I thought I'd write this email to remind people that in theory there is a meeting tomorrow and discuss if other people attend. I personally would propose to shift the meeting to next week (for purely selfish reasons ;). As far as I know, there is no formal presentation tomorrow. Anyway, will anyone attend tomorrow or is everyone in favor of shifting a week? In case it takes place, for the people who did not attend so far, the usual snippet from Harald's mails: Oct 3, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin 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. Cheers Nico

6 6

Erlang command line interface (OTP-version) available
by M. Josenhans 09 Oct '12

09 Oct '12

Hello, the Erlang command line interface (OTP version) is available on Github: https://github.com/josemic/Erlang-command-line-interface_otp This is a telnet commandline server written in Erlang using OTP libraries. It provides features such as command-completion, command-abbreviation, command-help, reading/writing commands from/to file and modular command-registration. Its behaviour is kept similar to the well known, C-written, OpenBSC telnet command line server. It is intended for future inclusion into Osmocom's Erlang projects. The installation instructions are found in the github wiki. Cheers, Michael

1 0

[PATCH] bsc_init: Forget which SIs are valid for the trx.
by Holger Hans Peter Freyther 09 Oct '12

09 Oct '12

The recent commit to improve the SI generation lead to setting the BCCH SIs for all TRX in a multi-trx setup. This is because we create the SIs globally but si_valid appears to be limited to the 'current' trx. Warn if we attempt to set SIs for the BCCH on a trx that does not have a BCCH. --- openbsc/src/libbsc/bsc_init.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/openbsc/src/libbsc/bsc_init.c b/openbsc/src/libbsc/bsc_init.c index e05aec7..7a60e04 100644 --- a/openbsc/src/libbsc/bsc_init.c +++ b/openbsc/src/libbsc/bsc_init.c @@ -129,6 +129,11 @@ static int rsl_si(struct gsm_bts_trx *trx, enum osmo_sysinfo_type i, int si_len) GSM_BTS_SI(bts, i), si_len); break; default: + if (bts->c0 != trx) + LOGP(DRR, LOGL_ERROR, + "Attempting to set BCCH SI%s on wrong BTS/TRX (%d/%d)\n", + get_value_string(osmo_sitype_strs, i), + bts->nr, trx->nr); rc = rsl_bcch_info(trx, osmo_sitype2rsl(i), GSM_BTS_SI(bts, i), si_len); break; @@ -149,6 +154,9 @@ static int set_system_infos(struct gsm_bts_trx *trx) ms_pwr_ctl_lvl(bts->band, bts->ms_max_power); bts->si_common.cell_sel_par.neci = bts->network->neci; + /* Zero, forget the state of the SIs */ + bts->si_valid = 0; + /* First, we determine which of the SI messages we actually need */ if (trx == bts->c0) { -- 1.7.10.4

1 0

Analysing the communication between the BSC and the MSC in a sysmoBTS
by Yann R. Moupinda 04 Oct '12

04 Oct '12

Hello everybody First of all, let me introduce myself. My name is Yann Moupinda and I'm a student doing his Master thesis in the field of GSM technology. For my thesis, the company for which i'm working now, bought a sysmoBTS from sysmocom. The sysmoBTS is configured as a stand alone GSM network in a box (NITB) running the osmo-nitb and the osmo-bts programs. An important part of my thesis is to understand how the sysmoBTS works and therefore I did some measurements with wireshark to analyse the data flow between the BTS,BSC and MSC/HLR/VLR/EIR. This is also to see the main differences between a sysmoBTS and a conventional GSM Network. I used the " tcpdump " - command on the loopback interface lo0 to capture the data flow between the GSM components and then, the analysis with wireshark shows me only the data flow between BTS and BSC. It's possible to see such messages like LOCATION UPDATING REQUEST and IDENTITY REQUEST wich are normally, transparently exchanged between Mobile Station (MS) and the Network subsystem (MSC/HLR/VLR/EIR). All these messages are always addressed to, or from the same BSC TCP-port 3003. So i can not see what happens behind this port (behind BSC). In order to get the communication between BSC and MSC, i decided to have a deeper look on the logging messages of the sysmoBTS. Even there, i cannot recognize how the data transmission between BSC and MSC works. Does anyone know how to get this information? Any guidance would be appreciated. I have included one .pcap file and a text file of the logging messages taken while i powered on the mobile phone. Best regards, Yann.

3 2

OpenBSC and 3G
by John Otten 02 Oct '12

02 Oct '12

Hello Everyone, I now have OpenBSC (including GPRS) up and running with a fair amount of stability, using an IP.Access 2G BTS. Now I am looking towards the next stage - getting a 3G system operating. I have the use of an IP.Access NodeB that I would like get running with OpenBSC. In performing my due diligence, I found Harald's 3G road map from December 2010 or so. I am wondering what the current state of development is. I see that IP.Access' URSL protocol was an issue back then, because it is proprietary. Has anyone managed to get far enough in their development that they have implemented the protocol? I also see from Dieter Spaar's blog that he is making some progress, but he states his code is not ready for public release. Since I don't see much about 3G on the OpenBSC wiki, I am assuming that no one has any code that they would want to share at this point. I imagine I may have to forge ahead on my own. I am fairly new to GSM development, and I haven't really delved into the OpenBSC source yet (other than to discern what might have caused some problems I encountered), so if anyone has any suggestions on where to begin, or has some issues where I might be able to assist in order to move development further down the road, please let me know. Thanks! John

1 0

Bounce action notification
by mailman＠lists.osmocom.org 01 Oct '12

01 Oct '12

This is a Mailman mailing list bounce action notice: List: OpenBSC Member: jledet07(a)student.aau.dk 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.

1 0

BS-11 to sell
by Harald Welte 01 Oct '12

01 Oct '12

Hi! In case anyone on this list is interested in owning a BS-11, I have decided to sell off one more of the units that I still had here for my personal use. I'm also able to sell a compatible HFC-E1 or DAHDI/Digium card along with it. Price is up to negotiation. I don't intend to give it away for free, unless it is somebody with a known track record of osmocom.org contributions. 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)

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC