https://osmocom.org/https://osmocom.org/favicon.ico?16647414092021-02-20T02:04:25ZOpen Source Mobile CommunicationsOsmoBSC - Bug #5037: rbs2000 Remote Transcoder Failure https://osmocom.org/issues/5037?journal_id=213652021-02-20T02:04:25Zkeith
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/21365/diff?detail_id=35604">diff</a>)</li></ul> OsmoBSC - Bug #5037: rbs2000 Remote Transcoder Failure https://osmocom.org/issues/5037?journal_id=213662021-02-20T03:11:22Zkeith
<ul></ul><p>On the old machine that worked;</p>
<p>I started upgrading packages one by one, restarting osmo-bsc, osmo-msc and osmo-mgw each time.</p>
<p>I did that for the following individually, and calls kept working.</p>
<p>apt install osmo-mgw</p>
<p>same apt install for:<br />osmo-msc<br />osmo-bsc<br />libosmo-sigtran5<br />osmo-stp<br />libosmocore16<br />libosmoabis9<br />libosmotrau2</p>
<p>Then unfortunately I let frustration get the better of my patience, and just went ahead with apt upgrade.<br />This system is now also giving:</p>
<pre>
20210219210208350 DCHAN ERROR lchan(0-0-7-TCH_F-0)[0x5568baed4740]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Transcoder Failure [ 28 ]) (abis_rsl.c:982)
</pre>
<p>At least it's confirmed that something in the upgrade broke it:</p>
<pre>
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-image-4.19.0-14-amd64
The following packages will be upgraded:
base-files bind9-host ca-certificates dnsmasq dnsmasq-base file grub-common grub-pc grub-pc-bin grub2-common iproute2 libapache2-mod-php7.3 libasn1c1 libbind9-161
libcairo2 libdns-export1104 libdns1104 libfdt1 libgnutls-dane0 libgnutls-openssl27 libgnutls28-dev libgnutls30 libgnutlsxx28 libisc-export1100 libisc1100 libisccc161
libisccfg163 libldap-2.4-2 libldap-common liblwres161 libmagic-mgc libmagic1 libnode-dev libnode64 libnss-systemd libosmo-e1d-dev libosmo-e1d0 libosmo-gsup-client0
libosmo-mslookup0 libosmo-netif-dev libosmo-ranap3 libosmo-sccp-dev libosmocore-dev libosmocore-utils libosmonetif8 libosmotrau2 libp11-kit-dev libp11-kit0 libpam-systemd
libpq5 libsmpp1 libssl-dev libssl1.1 libsystemd0 libudev1 libzstd1 linux-compiler-gcc-8-x86 linux-headers-amd64 linux-image-amd64 linux-kbuild-4.19 linux-libc-dev
node-ini node-y18n nodejs nodejs-doc openssl osmo-e1d osmo-hlr osmo-sip-connector php7.3 php7.3-cli php7.3-common php7.3-curl php7.3-gd php7.3-intl php7.3-json
php7.3-mbstring php7.3-opcache php7.3-pgsql php7.3-readline php7.3-xml postgresql-9.6 postgresql-client-9.6 postgresql-client-common postgresql-common
postgresql-contrib-9.6 python-apt-common python3-apt sudo systemd systemd-sysv tzdata udev unzip
94 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 107 MB of archives.
</pre> OsmoBSC - Bug #5037: rbs2000 Remote Transcoder Failure https://osmocom.org/issues/5037?journal_id=213672021-02-20T14:39:42Zlaforge
<ul></ul><p>remote transcoder failure is something the BTS sends if it cannot establish the TRAU<br />link over Abis to osmo-mgw.</p>
<p>So either osmo-mgw is not running, not configured correctly, or osmo-mgw or libosmo-abis<br />somehow have a regression.</p>
<p>libosmo-abis didn't have many commits recently, neither did osmo-mgw. I would<br />guess you could try reverting those:</p>
<ul>
<li><a class="external" href="http://git.osmocom.org/libosmo-abis/commit/?id=949b8a22b05b55135a47f0eabf3bfb8dffa6b7d0">http://git.osmocom.org/libosmo-abis/commit/?id=949b8a22b05b55135a47f0eabf3bfb8dffa6b7d0</a></li>
<li><a class="external" href="http://git.osmocom.org/libosmo-abis/commit/?id=b3952c60f12fd2d2b2496a47ecb34dd5b966e0d8">http://git.osmocom.org/libosmo-abis/commit/?id=b3952c60f12fd2d2b2496a47ecb34dd5b966e0d8</a></li>
</ul>
<p>Regards,<br /> Harald</p> OsmoBSC - Bug #5037: rbs2000 Remote Transcoder Failure https://osmocom.org/issues/5037?journal_id=213742021-02-22T01:38:37Zkeith
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>keith</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul><p>I'm a bit at a loss to explain this.</p>
<p>No config files changed, but I uninstalled all packages and built everything from source, which worked, then I reinstalled all packages and that also works.</p>
<p>I notice there is still a: CONNECTION FAIL (cause=Remote Transcoder Failure [ 28 ])</p>
<p>error in the osmo-bsc log when every call ends, I must have been mis-interpreting this immediate call termination (caused by something else) as being related to this error in the log. Or maybe something else changed in the last 24 hours..</p>
<p>I still have one broken system - I might go back and check what is happening there, but I will probably just close this as invalid.</p> OsmoBSC - Bug #5037: rbs2000 Remote Transcoder Failure https://osmocom.org/issues/5037?journal_id=213782021-02-22T11:00:11Zlaforge
<ul></ul><p>On Mon, Feb 22, 2021 at 01:38:43AM +0000, keith [REDMINE] wrote:</p>
<blockquote>
<p>I notice there is still a: CONNECTION FAIL (cause=Remote Transcoder Failure [ 28 ])<br />error in the osmo-bsc log when every call ends,</p>
</blockquote>
<p>I would guess this is likely just an artefact during shutdown, as we<br />probably shut down the MGW side slightly before shutting down the<br />channel on the BTS side. If the call works fine before the message, I<br />would simply ignore it.</p> OsmoBSC - Bug #5037: rbs2000 Remote Transcoder Failure https://osmocom.org/issues/5037?journal_id=226422021-10-05T21:04:38Zkeith
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul><p>Closing, this hasn't been reproduced.</p>