OpenBSC October 2012

openbsc@lists.osmocom.org

30 participants
35 discussions

by Alexander Chemeris

Sorry to those who receive this message twice. I hope Osmocom community finds this small effort interesting as well. ---------- Forwarded message ---------- From: Alexander Chemeris <alexander.chemeris(a)gmail.com> Date: Fri, Oct 19, 2012 at 5:15 PM Subject: Open-source telecom T-shirts To: umtrx <umtrx(a)lists.osmocom.org>, openbts-discuss(a)lists.sourceforge.net Hi all, We're thinking about making T-shirts with open-source telecom. I've posted a call for ideas in my OpenBTS blog - please contribute. Telecom needs more openness and you could help us promote this! http://openbts.chemeris.ru/2012/10/reklama-open-source-telecom/ We plan to give them for free to the first 10-20 UmTRX buyers. Then you'll be able to buy them from our web-shop or from one of our friends and distributors. If you proposal gets printed, you'll get a free T-shirt as well. PS If you know a good online T-shirt printing service in US or Europe - drop me a line. I've never done this in US/Europe before. -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru

12 years, 8 months

[PATCH] libbsc: fix message leaks on several error paths

by pablo＠gnumonks.org

From: Pablo Neira Ayuso <pablo(a)gnumonks.org> This patch fixes several leak of msgbs in uncommon error paths. --- openbsc/src/libbsc/abis_nm.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/openbsc/src/libbsc/abis_nm.c b/openbsc/src/libbsc/abis_nm.c index ee0dd60..2c8b3ee 100644 --- a/openbsc/src/libbsc/abis_nm.c +++ b/openbsc/src/libbsc/abis_nm.c @@ -635,13 +635,16 @@ int abis_nm_rcvmsg(struct msgb *msg) if (oh->placement != ABIS_OM_PLACEMENT_ONLY) { LOGP(DNM, LOGL_ERROR, "ABIS OML placement 0x%x not supported\n", oh->placement); - if (oh->placement != ABIS_OM_PLACEMENT_FIRST) - return -EINVAL; + if (oh->placement != ABIS_OM_PLACEMENT_FIRST) { + rc = -EINVAL; + goto err; + } } if (oh->sequence != 0) { LOGP(DNM, LOGL_ERROR, "ABIS OML sequence 0x%x != 0x00\n", oh->sequence); - return -EINVAL; + rc = -EINVAL; + goto err; } #if 0 unsigned int l2_len = msg->tail - (uint8_t *)msgb_l2(msg); @@ -671,9 +674,9 @@ int abis_nm_rcvmsg(struct msgb *msg) default: LOGP(DNM, LOGL_ERROR, "unknown ABIS OML message discriminator 0x%x\n", oh->mdisc); - return -EINVAL; + rc = -EINVAL; } - +err: msgb_free(msg); return rc; } -- 1.7.10.4

12 years, 8 months

BTS hardware trade.

by Andrew Back

Hello, Is there anyone who has 1800MHz or 900MHz hardware and that would be interested in swapping it for 1900MHz kit? Probably a long shot but worth asking! If so, please contact me off-list. Cheers, Andrew -- Andrew Back http://carrierdetect.com

12 years, 8 months

CSD support for openbsc with the BS-11

by Tobias Engel

Hi, I just pushed a "tobias/csd" branch to both the openbsc and libosmo-abis git. If you check out those branches you should be able to make CSD calls with a BS-11 and the following parameters: V.110, 9.6kbit/s, transparent mode. The AT-Command to activate this mode is AT+CBST=71,0,0. (If you see an ERROR when entering this command, your phone's baseband most likely doesn't support transparent mode. One of the few exceptions seem to be MediaTek and TI.) There is no Interworking Function in the code - the V.110 frames simply get sent from one phone to the other. This should not be a problem as long as both sides use the exact same parameters. The openbsc tobias/csd branch is based on Harald's laforge/csd branch which already adds code for setting CSD channel modes. Many thanks to Dieter Spaar who found out why I was only seeing garbled data on the uplink, and also to GSMK who let me use lots of my time there to figure out this CSD stuff. Next stop would be to implement RLP to also support V.110 non-transparent mode which is supported by almost all GSM basebands. -Tobias

12 years, 8 months

patch to allow setting of various control channel description parameters

by jolly

hi, this patch allows to tune control channel. it can be used to speed up GPRS TBF establishment. regards, andreas

12 years, 8 months

Bad signalling message

by Lennart Müller

Hi, some problems with latest git clone and nanoBTS 165AU... <0002> gsm_04_08.c:412 -> LOCATION UPDATE ACCEPT <0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 05) Sending 0x02 to MS. <0002> gsm_04_08.c:754 -> MM INFO <0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 05) Sending 0x32 to MS. <0002> gsm_subscriber.c:337 Subscriber 262620001000026 ATTACHED LAC=10 <0003> gsm_04_08.c:1158 TX APPLICATION INFO id=0x00, len=4 <0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 06) Sending 0x38 to MS. <0000> abis_rsl.c:1542 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION <0002> gsm_04_08.c:1045 TMSI Reallocation Completed. Subscriber: 262620001000026 <0000> chan_alloc.c:429 (bts=0,trx=0,ts=0,ss=0) starting release sequence <0003> gsm_04_08_utils.c:231 Sending Channel Release: Chan: Number: 0 Type: 1 <0004> abis_rsl.c:618 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD <0004> abis_rsl.c:1017 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive channel <0004> abis_rsl.c:1017 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive channel <0000> abis_rsl.c:1542 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION <0004> bsc_api.c:638 Got data in non active state(RELEASE REQUESTED), discarding. <0019> input/ipaccess.c:454 Bad signalling message,sign_link returned error <0019> input/ipaccess.c:260 Forcing socket shutdown with no signal link set <001b> bsc_init.c:337 Lost some E1 TEI link: 1 0x81e4768 <001b> bsc_init.c:337 Lost some E1 TEI link: 2 0x81e4768 I have no clue if that is a problem of configuration, nanoBTS or abis library. With an old version (Feb 2012), the message... <0019> ipaccess.c:425 Bad signalling message,sign_link returned error. ...appears too, but socket is not being shut down. Thanks, LM

12 years, 8 months

[PATCH] ipaccess: relax default behaviour on errors coming from signalling layer

by Pablo Neira Ayuso

This patch relaxes the behaviour on error coming from the signalling layer. This is probably too strict for recoverable errors. 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..4f81c43 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. + */ LOGP(DLINP, LOGL_ERROR, "Bad signalling message," "sign_link returned error\n"); ret = -EINVAL; - goto err; + msgb_free(msg); } return 0; -- 1.7.10.4 --LZvS9be/3tNcYl/X--

12 years, 8 months

[PATCH] ipaccess: relax default behaviour on errors coming from signalling layer

by Pablo Neira Ayuso

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

12 years, 8 months

[PATCH] Allow setting of Control Channel Description parameters via VTY

by Andreas Eversberg

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

12 years, 8 months

Analysing the communication between the BSC and the MSC in a sysmoBTS

by Yann R. Moupinda

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

12 years, 8 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC October 2012