SDCCH not released if Radio Link Failure / Sending Connection Failure: cause = 0x001 Experienced in osmo-bsc and osmo-bts-trx

historical

Hi Harald,

Below are the URLs of the following bugs opened in the issue tracker:

neels/inter_bsc_ho branch for osmo-bsc 2TRX configured but OSMO-BSC only uses the first TRX configuration:
https://osmocom.org/issues/3475

SDCCH not released if Radio Link Failure / Sending Connection Failure: cause = 0x001 Experienced in osmo-bsc and osmo-bts-trx:
https://osmocom.org/issues/3474

Best Regard,

Ron Menez
ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com>

On Aug 20, 2018, at 8:53 AM, Ron <ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com>> wrote:

Thank you for the respond Harald.

Below are the versions of OSMO-BSC, OSMO-BTS-TRX, OSMO-TRX, and OSMO-MSC.

OsmoBSC# show version
OsmoBSC 1.2.1.91-3ff7 (OsmoBSC).
Copyright (C) 2008-2018 Harald Welte, Holger Freyther
Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt
Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr

License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

===============================================

OsmoBTS# show version
OsmoBTS 0.8.1.35-6575f0 (OsmoBTS).
Copyright (C) 2010, 2011 by Harald Welte, Andreas Eversberg and On-Waves
License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

===============================================

OsmoTRX# show version
OsmoTRX 0.4.0 (OsmoTRX).
Copyright (C) 2007-2014 Free Software Foundation, Inc.
Copyright (C) 2013 Thomas Tsou <tom at tsou.cc<mailto:tom at tsou.cc>>
Copyright (C) 2015 Ettus Research LLC
Copyright (C) 2017-2018 by sysmocom s.f.m.c. GmbH <info at sysmocom.de<mailto:info at sysmocom.de>>
License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

===============================================

OsmoMSC# show version
OsmoMSC 1.2.0.20-2798 (OsmoMSC).
OsmoMSC - Osmocom Circuit-Switched Core Network implementation
Copyright (C) 2016 by sysmocom s.f.m.c. GmbH <info at sysmocom.de<mailto:info at sysmocom.de>>
Based on OsmoNITB:
  (C) 2008-2010 by Harald Welte <laforge at gnumonks.org<mailto:laforge at gnumonks.org>>
  (C) 2009-2012 by Holger Hans Peter Freyther <zecke at selfish.org<mailto:zecke at selfish.org>>
Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt
Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr

License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Noted on the filing of 2 separate cases Harald. We’ll open 2 separate case for this.

We are using UBUNTU 16.04 as OS.

Best Regard,

Ron Menez
ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com>

On Aug 18, 2018, at 11:51 PM, Harald Welte <laforge at gnumonks.org<mailto:laforge at gnumonks.org>> wrote:

Hi Ron,

sorry for the late response.

First of all, thanks for your two bug / experience reports.

One very important bit was missing: Which exact version of the relevant osmocom programs
were you using when observing the two issues, respectively?

There's a lot of development going on, and without pin-pointing the exact versions it's
hard to understand whether or not the related problem might still apply to current 'master',
or whether it is likely a regression, etc.

You can use "show version" on the VTY or call the respective program with "--version" command-line
argument to extract the version information.

If you have the time, it would also be very useful if you could file those two bugs
as two separate issues in the respective issue tracker of the respective program (OsmoBSC
in this case) on osmocom.org<http://osmocom.org/>.

Thanks in advance!
--
- Harald Welte <laforge at gnumonks.org<mailto:laforge at gnumonks.org>>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                 (ETSI EN 300 175-7 Ch. A6)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180820/026ff998/attachment.htm>