Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092022-11-07T23:56:29ZOpen Source Mobile Communications
Redmine osmo-isdntap - Bug #5748 (Resolved): segfault when using 'line'-names that contain "/"https://osmocom.org/issues/57482022-11-07T23:56:29Zroox
<p>The <em>line</em> name is part of the file name of the recording.<br />"/" should be properly filtered to not have issues.</p>
<p>This happens when you use 'TE2/0/1' as the line name:<br /><pre>
osmo-isdntap -c /etc/osmocom/osmo-isdntap.cfg --debug=DITAP:DQ931
<0001> isdntap.c:254 (TE2/0/1) U->N Q.931 message SETUP
<0000> isdntap.c:112 (TE2/0/1) Creating call state record for callref 26
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message SETUP
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message CALL PROCEEDING
<0000> isdntap.c:493 (TE2/0/1:1) Starting B-channel recording 03080805240--20221107-002458
<0000> isdntap.c:475 Error opening file /tmp//isdntap-TE2/0/1-03080805240--20221107-002458-1-tx.raw: No such file or directory
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message CALL PROCEEDING
<0000> isdntap.c:341 (TE2/0/1:1) Cannot open B-channel
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message CONNECT
<0000> isdntap.c:341 (TE2/0/1:1) Cannot open B-channel
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message CONNECT
<0000> isdntap.c:341 (TE2/0/1:1) Cannot open B-channel
<0001> isdntap.c:254 (TE2/0/1) U->N Q.931 message INFORMATION
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message INFORMATION
<0001> isdntap.c:254 (TE2/0/1) U->N Q.931 message CONNECT ACK
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message CONNECT ACK
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message DISCONNECT
<0001> isdntap.c:254 (TE2/0/1) U<-N Q.931 message DISCONNECT
<0001> isdntap.c:254 (TE2/0/1) U->N Q.931 message RELEASE
<0000> isdntap.c:523 (TE2/0/1:1) Stopping B-channel recording
Segmentation fault (core dumped)
</pre></p>
<p>Workaround:<br />create the recording directory manually before the recording happens ...</p>
<pre><code>mkdir -p /tmp//isdntap-TE2/0/</code></pre>
<pre>
<0000> isdntap.c:493 (TE2/0/1:1) Starting B-channel recording 03080805240--20221107-003444
<0000> isdntap.c:479 (TE2/0/1:1) Opened file /tmp//isdntap-TE2/0/1-03080805240--20221107-003444-1-tx.raw
<0000> isdntap.c:479 (TE2/0/1:1) Opened file /tmp//isdntap-TE2/0/1-03080805240--20221107-003444-1-rx.raw
</pre> osmo-isdntap - Bug #5747 (Rejected): Configuration created via the vty is broken (% Invalid log l...https://osmocom.org/issues/57472022-11-07T23:47:23Zroox
<p>'write' in the vty creates a broken config: "% Invalid log level 0 for itap / q931" is inserted in the log section</p>
<p>Used versions:<br />osmo-isdntap (v0~git20221017 - master from 07.11.2022)<br />libosmocore (v1.7.0.63 - master from 05.11.2022)</p>
<p>How to reproduce:</p>
<p>start with an empty configuration</p>
<pre><code>echo "" > /etc/osmocom/osmo-isdntap.cfg</code></pre>
<p>start osmo-isdntap</p>
<pre><code>osmo-isdntap -c /etc/osmocom/osmo-isdntap.cfg</code></pre>
<p>telnet 127.0.0.1 4270</p>
<pre><code>osmo-isdntap> en<br /> osmo-isdntap# conf t<br /> osmo-isdntap(config)# isdntap <br /> osmo-isdntap(config-isdntap)# line XXX dahdi TE2/0/1<br /> osmo-isdntap(config-isdntap-line)# local-role network<br /> osmo-isdntap(config-isdntap-line)# exit<br /> osmo-isdntap(config-isdntap)# gsmtap remote-host 192.168.200.2<br /> osmo-isdntap(config-isdntap)# output-path /tmp/<br /> osmo-isdntap(config)# exit<br /> osmo-isdntap# write</code></pre>
<p>results in a config that erroneously adds</p>
<pre><code>% Invalid log level 0 for itap<br /> % Invalid log level 0 for q931</code></pre> OsmocomBB - Feature #4690 (Resolved): Add snake gamehttps://osmocom.org/issues/46902020-08-01T12:44:52Zroox
<p>In 2013 Marcel "sdrfnord" McKinnon wrote a snake game.<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-May/004244.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-May/004244.html</a><br /><a class="external" href="https://github.com/sdrfnord/osmocom-bb/commits/sdrfnord/ui">https://github.com/sdrfnord/osmocom-bb/commits/sdrfnord/ui</a></p>
<p>It currently only works with on devices with a Sitronix ST7558 display controller! (C115/C117/C123/C121/C118).</p>
<p>It would be nice to have it as part of the osmocom-bb master branch or at least a feature-branch on git.osmocom.org</p> OsmoSGSN - Bug #4116 (Resolved): osmo-sgsn fails to compile on openSUSE Tumbleweed (gcc 9.1 with ...https://osmocom.org/issues/41162019-07-17T22:05:02Zroox
<p>osmo-sgns fails to compile on openSUSE Tumbleweed (gcc 9.1 with LTO enabled)</p>
<p>openSUSE just enabled LTO by default for its packages in Tumbleweed/Factory.<br /><a class="external" href="https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html">https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html</a><br /><a class="external" href="https://gcc.gnu.org/wiki/LinkTimeOptimization">https://gcc.gnu.org/wiki/LinkTimeOptimization</a></p>
<p>This means the distro provided CFLAGS now changed from</p>
<p>without LTO<br /><pre>
CFLAGS='-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g'
</pre></p>
<p>to</p>
<p>with LTO enabled<br /><pre>
CFLAGS="-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess"
</pre></p>
<p>compiling osmo-sgsn master with LTO enabled then triggers the following warnings/errors:<br /><pre>
[ 20s] make[3]: Entering directory '/home/abuild/rpmbuild/BUILD/osmo-sgsn-1.4.0.29/tests/gbproxy'
[ 20s] CC gbproxy_test.o
[ 20s] CCLD gbproxy_test
[ 22s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/gbproxy_test.Vzl0RE.ltrans0.ltrans.o: in function `gbproxy_make_sgsn_tlli':
[ 22s] /home/abuild/rpmbuild/BUILD/osmo-sgsn-1.4.0.29/tests/gbproxy/gb_proxy.c:278: undefined reference to `__wrap_osmo_get_rand_id'
[ 22s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/gbproxy_test.Vzl0RE.ltrans0.ltrans.o: in function `gbprox_process_bssgp_dl.constprop.0':
[ 22s] /home/abuild/rpmbuild/BUILD/osmo-sgsn-1.4.0.29/tests/gbproxy/gb_proxy.c:240: undefined reference to `__wrap_osmo_get_rand_id'
[ 22s] collect2: error: ld returned 1 exit status
[ 22s] make[3]: *** [Makefile:437: gbproxy_test] Error 1
</pre></p>
<p>I have attatched the full buildlog.</p> OsmoMSC - Bug #4115 (Resolved): osmo-msc fails to compile on openSUSE Tumbleweed (gcc 9.1 with LT...https://osmocom.org/issues/41152019-07-17T21:59:58Zroox
<p>openSUSE just enabled LTO by default for its packages in Tumbleweed/Factory.<br /><a class="external" href="https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html">https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html</a><br /><a class="external" href="https://gcc.gnu.org/wiki/LinkTimeOptimization">https://gcc.gnu.org/wiki/LinkTimeOptimization</a></p>
<p>This means the distro provided CFLAGS now changed from</p>
<p>without LTO<br /><pre>
CFLAGS='-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g'
</pre></p>
<p>to</p>
<p>with LTO enabled<br /><pre>
CFLAGS="-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess"
</pre></p>
<p>compiling osmo-msc master then triggers the following warnings/errors:<br /><pre>
[ 22s] msc_vty.c:1077:19: error: potential null pointer dereference [-Werror=null-dereference]
[ 22s] msc_ho.c:80:14: error: potential null pointer dereference [-Werror=null-dereference]
[ 22s] lto-wrapper: fatal error: make returned 2 exit status
[ 22s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: error: lto-wrapper failed
[ 22s] collect2: error: ld returned 1 exit status
[ 22s] error: Bad exit status from /var/tmp/rpm-tmp.co5mLl (%build)
</pre></p>
<p>I have attatched the full buildlog.</p> OsmoGGSN (former OpenGGSN) - Bug #4114 (Resolved): osmo-ggsn fails to compile on openSUSE Tumblew...https://osmocom.org/issues/41142019-07-17T21:57:06Zroox
<p>here's the problematic compiler warning:</p>
<pre>
[ 25s] libtool: link: gcc -O2 -D_GNU_SOURCE -fno-builtin -Wall -DSBINDIR=\"/usr/sbin\" -ggdb -I/usr/include/libosmocore/ -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-s
trong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -o .libs/sgsnemu sgsnemu.o cmdline.o /home/abuild/rpmbuild/BUILD/osmo-ggsn-1.3.0.46/
gtp/.libs/libgtp.so -L../gtp ../lib/libmisc.a -ltalloc -losmocore -Wl,-rpath -Wl,/usr/lib64
[ 26s] In function 'memset',
[ 26s] inlined from 'in46a_from_eua' at in46_addr.c:344:5,
[ 26s] inlined from 'create_pdp_conf' at sgsnemu.c:1405:6,
[ 26s] inlined from 'conf' at sgsnemu.c:1511:10:
[ 26s] /usr/include/bits/string_fortified.h:71:10: warning: '__builtin___memset_chk' writing 16 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
[ 26s] 71 | return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest));
[ 26s] | ^
</pre>
<p>OBS build fails because the above mentioned compiler warning the turns into an error by on of the RPM post build checks:<br /><pre>
[ 31s] I: Statement might potentially overflow a destination buffer, where a size larger
[ 31s] than the actual buffer was specified
[ 31s] E: osmo-ggsn destbufferoverflow /usr/include/bits/string_fortified.h:71, 34
</pre></p>
<p>I have attatched the full buildlog.</p> OsmoBSC - Bug #4113 (Resolved): osmo-bsc fails to compile on openSUSE Tumbleweed (gcc 9.1 with LT...https://osmocom.org/issues/41132019-07-17T21:49:10Zroox
<p>openSUSE just enabled LTO by default for its packages in Tumbleweed/Factory.<br /><a class="external" href="https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html">https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html</a><br /><a class="external" href="https://gcc.gnu.org/wiki/LinkTimeOptimization">https://gcc.gnu.org/wiki/LinkTimeOptimization</a></p>
<p>This means the distro provided CFLAGS now changed from</p>
<p>without LTO<br /><pre>
CFLAGS='-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g'
</pre></p>
<p>to</p>
<p>with LTO enabled<br /><pre>
CFLAGS="-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess"
</pre></p>
<p>compiling osmo-bsc master then triggers the following warnings/errors:<br /><pre>
[ 22s] bsc_init.c:242:16: error: potential null pointer dereference [-Werror=null-dereference]
[ 22s] system_information.c:490:9: error: 'f0' may be used uninitialized in this function [-Werror=maybe-uninitialized]
[ 22s] lto-wrapper: fatal error: make returned 2 exit status
[ 22s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: error: lto-wrapper failed
[ 22s] collect2: error: ld returned 1 exit status
[ 22s] error: Bad exit status from /var/tmp/rpm-tmp.gBd6u2 (%build)
</pre></p>
<p>I have attatched the full buildlog.</p> OpenBSC - Bug #4112 (Resolved): OpenBSC fails to compile on openSUSE Tumbleweed (gcc 9.1 with LTO...https://osmocom.org/issues/41122019-07-17T21:45:13Zroox
<p>openSUSE just enabled LTO by default for its packages in Tumbleweed/Factory.<br /><a class="external" href="https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html">https://lists.opensuse.org/opensuse-factory/2019-07/msg00240.html</a><br /><a class="external" href="https://gcc.gnu.org/wiki/LinkTimeOptimization">https://gcc.gnu.org/wiki/LinkTimeOptimization</a></p>
<p>This means the distro provided CFLAGS now changed from</p>
<p>without LTO<br /><pre>
CFLAGS='-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g'
</pre></p>
<p>to</p>
<p>with LTO enabled<br /><pre>
CFLAGS="-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess"
</pre></p>
<p>compiling openbsc master then triggers the following warnings/errors:<br /><pre>
[ 23s] gsm_04_08.c:1464:2: error: 'mi_type' may be used uninitialized in this function [-Werror=maybe-uninitialized]
[ 23s] ../../include/openbsc/acc_ramp.h:90:32: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:279:22: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:280:30: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:281:35: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:277:16: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] ../../include/openbsc/acc_ramp.h:90:32: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:279:22: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:280:30: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:281:35: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] acc_ramp.c:277:16: error: potential null pointer dereference [-Werror=null-dereference]
[ 23s] lto-wrapper: fatal error: make returned 2 exit status
[ 23s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: error: lto-wrapper failed
[ 23s] collect2: error: ld returned 1 exit status
[ 23s] error: Bad exit status from /var/tmp/rpm-tmp.6yGOJj (%build)
</pre></p>
<p>I have attatched the full buildlog.</p> rtl-sdr - Bug #3946 (Resolved): Nightly builds for windows (rtl-sdr/osmo-fl2k) not beeing updatedhttps://osmocom.org/issues/39462019-04-21T20:22:47Zroox
<p>The binaries at <a class="external" href="http://ftp.osmocom.org/binaries/windows">http://ftp.osmocom.org/binaries/windows</a> were last built in may 2018 !</p>
<p>Currently Jenkins job "Osmocom-OBS_MinGW_nightly_publish" downloads and packages the windows binaries for rtl_sdr and just fine but then fails in the last stage while trying to copy the generated files over to ftp.osmocom.org</p>
<p>Not sure whats causing this - maybe some change in the infrastructure back then ?</p> OsmoSGSN - Bug #3689 (New): Support Cisco GGSN (Cisco 7200 with IOS 12.4.x)https://osmocom.org/issues/36892018-11-12T23:39:11Zroox
<p>I just managed to connect osmo-sgsn (2G) to an old real world GGSN implementation from Cisco (IOS 12.4 on 7200er routers).<br />The cool thing is that you can emulate the MIPS based hardware from these cisco routers via dynamips on commodity intel hardware :-)<br />I had to remove some GTP IEs the osmo-sgsn had sent that prevented the GTP tunnel to properly come up.</p>
This GGSN implementation on the 7200 (at least with the tested IOS Version 12.4(20)T5) seems to support
<ul>
<li>GPRS only via GTPv0 and UMTS via GTPv1</li>
<li>GPRS up to Release 6.0</li>
<li>explicit GPRS Release 4.0 (via: gprs compliance 3gpp ggsn r4.0)</li>
</ul>
<p>Here is some more information about this cisco IOS based GGSN:</p>
<p>Cisco GGSN Release 6.0 Configuration Guide, Cisco IOS Release 12.4(2)XB8<br /><a class="external" href="https://www.cisco.com/c/en/us/td/docs/ios/12_4/12_4x/12_42xb/ggsn6_0/cfg/ggsn60_c/ggsnover.html">https://www.cisco.com/c/en/us/td/docs/ios/12_4/12_4x/12_42xb/ggsn6_0/cfg/ggsn60_c/ggsnover.html</a><br />Cisco GGSN Release 6.0 Command Reference, Cisco IOS Release 12.4(2)XB8<br /><a class="external" href="https://www.cisco.com/c/en/us/td/docs/ios/12_4/12_4x/12_42xb/ggsn6_0/cmd/ggsn60_r.html">https://www.cisco.com/c/en/us/td/docs/ios/12_4/12_4x/12_42xb/ggsn6_0/cmd/ggsn60_r.html</a><br />Release Notes for Cisco GGSN Release 6.0 on the Cisco MWAM, Cisco IOS Software Release 12.4 XB<br /><a class="external" href="https://www.cisco.com/c/en/us/td/docs/ios/12_4/12_4x/release/notes/rnMWAMxb.html#wp268022%0A">https://www.cisco.com/c/en/us/td/docs/ios/12_4/12_4x/release/notes/rnMWAMxb.html#wp268022%0A</a></p>
<p>I've attached a patch with the following GTP IEs patched out that allowed me to connect to the Cisco GGSN.</p>
<p>3GPP 29.060 (GPRS)<br /><a class="external" href="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1595">https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1595</a>#</p>
<pre>
#define GTPIE_RAT_TYPE 151 /* Radio Access Technology Type */ ->> TS 29.060 7.7.50
#define GTPIE_USER_LOC 152 /* User Location Information */ ->> TS 29.060 7.7.51
#define GTPIE_MS_TZ 153 /* MS Time Zone */ ->> TS 29.060 7.7.52
#define GTPIE_IMEI_SV 154 /* IMEI Software Version */ ->> TS 29.060 7.7.53
</pre><br />Up to GPRS release 9 all these IEs are marked as optional.<br />From GPRS Release 10 on the IE for IMEI_SV is marked as conditional the others remain optional.
<p>I've also attached debug logs, pcap traces and the osmo-sgsn.cfg</p>
<p>The IOS debug logs were created with the following debug options enabled<br /><pre>
debug gprs gtp events
debug gprs gtp messages
debug gprs gtp packets
debug gprs gtp parsing
</pre></p>
<p>Dynamips parameters (bridge fa1/0 to eth0 on my host)</p>
<pre><code>sudo dynamips -p 1:PA-FE-TX -s 1:0:gen_eth:eth0 --idle-pc=0x6155a540 c7200-adventerprisek9_mw-mz.124-20.T5.bin</code></pre> OsmoBSC - Bug #3630 (Resolved): Too restrictive channel combination checks for nanoBTShttps://osmocom.org/issues/36302018-10-06T20:11:33Zroox
<p>Today i've played with new cell broadcast support.<br />While it worked out of the box with osmo-bts and osmo-trx-lms I had some issues with a nanoBTS.</p>
<p><a href="http://www.ipaccess.com/uploads/wysiwyg_editor/files/2017/nanoBTS-GSM-Datasheet-v1.0.pdf" class="external">nanoBTS-GSM-Datasheet-v1.0.pdf</a> states that it should be a possible to configure a CBCH on TS0 or TS1.</p>
<p>CCCH+SDCCH4+CBCH on TS0 fails with:<br /><pre>
<0004> abis_nm.c:1893 OC=CHANNEL(03) INST=(00,00,00): Invalid Channel Combination 7 on (bts=0,trx=0,ts=0). Reason: TS0 of TRX0 must carry a BCCH.
</pre></p>
<p>CCCH on TS0 + SDCCH8+CBCH on TS1 seems to work but it feels somewhat unreliable.<br />While a Samsung Galaxy A3 (2016 - SMA310F) seem to work fine a good old Nokia 6300 (RM-217) has issues getting onto the network:</p>
<pre>
<0003> abis_rsl.c:1359 (bts=0) CHAN RQD: reason: Location updating (ra=0x08, neci=0x01, chreq_reason=0x03)
<0010> lchan_fsm.c:76 lchan(0-0-1-SDCCH8_CBCH-1)[0x55736648f310]{WAIT_RLL_RTP_ESTABLISH}: (type=SDCCH) lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Timeout
<0010> lchan_fsm.c:99 lchan(0-0-1-SDCCH8_CBCH-1)[0x55736648f310]{WAIT_RLL_RTP_ESTABLISH}: (type=SDCCH) Tx Immediate Assignment Reject (lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Timeout)
<0010> lchan_fsm.c:76 lchan(0-0-1-SDCCH8_CBCH-3)[0x55736648f7b0]{WAIT_RLL_RTP_ESTABLISH}: (type=SDCCH) lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Timeout
<0010> lchan_fsm.c:99 lchan(0-0-1-SDCCH8_CBCH-3)[0x55736648f7b0]{WAIT_RLL_RTP_ESTABLISH}: (type=SDCCH) Tx Immediate Assignment Reject (lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Timeout)
</pre>
<p>Disabling the cannel config checks in src/osmo-bsc/abis_nm.c finally let me use CCCH+SDCCH4+CBCH on TS0 on the nanoBTS.<br />This also seems to work without any issues so far.</p> OsmoBTS - Bug #2944 (Resolved): OsmoBTS master does not work with CalypsoBTS based transceivershttps://osmocom.org/issues/29442018-02-13T23:16:00Zroox
<p>Starting from revision 8c1d15764377eb6a11aa432661d5afe60c2e8a9c CalypsoBTS-based transceivers (I tested jolly/testing) does not longer work.</p>
<p>osmo-bts-trx fails early with:<br /><pre>
<000b> trx_if.c:488 Response message 'RSP SETSLOT 0 5' does not match command message 'CMD SETSLOT 0 5'
<0001> bts.c:210 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
</pre></p>
<p>I added some log statements to the beginning of the cmd_matches_rsp function and the output from osmo-bts-trx now looks like this:<br /><pre>
...
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD POWEROFF'
<000b> trx_if.c:160 Sending control 'CMD POWEROFF' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP POWEROFF 0'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: POWEROFF***
<000b> trx_if.c:424 ***RSPNAME: POWEROFF***
<000b> trx_if.c:425 ***TCM_PARAMS: ***
<000b> trx_if.c:426 ***PARAMS: ***
<0001> oml.c:1049 ADM state already was Unlocked
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD RXTUNE 1781800'
<000b> trx_if.c:160 Sending control 'CMD RXTUNE 1781800' to phy0.0
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD TXTUNE 1876800'
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD SETBSIC 63'
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD POWERON'
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD SETRXGAIN 1'
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD SETPOWER 20'
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD SETSLOT 0 5'
<000b> trx_if.c:457 Response message: 'RSP RXTUNE 0 1781800'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: RXTUNE***
<000b> trx_if.c:424 ***RSPNAME: RXTUNE***
<000b> trx_if.c:425 ***TCM_PARAMS: 1781800***
<000b> trx_if.c:426 ***PARAMS: 1781800***
<000b> trx_if.c:160 Sending control 'CMD TXTUNE 1876800' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP TXTUNE 0 1876800'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: TXTUNE***
<000b> trx_if.c:424 ***RSPNAME: TXTUNE***
<000b> trx_if.c:425 ***TCM_PARAMS: 1876800***
<000b> trx_if.c:426 ***PARAMS: 1876800***
<000b> trx_if.c:160 Sending control 'CMD SETBSIC 63' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP SETBSIC 0'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: SETBSIC***
<000b> trx_if.c:424 ***RSPNAME: SETBSIC***
<000b> trx_if.c:425 ***TCM_PARAMS: 63***
<000b> trx_if.c:426 ***PARAMS: ***
<000b> trx_if.c:160 Sending control 'CMD POWERON' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP POWERON 0'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: POWERON***
<000b> trx_if.c:424 ***RSPNAME: POWERON***
<000b> trx_if.c:425 ***TCM_PARAMS: ***
<000b> trx_if.c:426 ***PARAMS: ***
<000b> trx_if.c:160 Sending control 'CMD SETRXGAIN 1' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP SETRXGAIN 0 1'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: SETRXGAIN***
<000b> trx_if.c:424 ***RSPNAME: SETRXGAIN***
<000b> trx_if.c:425 ***TCM_PARAMS: 1***
<000b> trx_if.c:426 ***PARAMS: 1***
<000b> trx_if.c:160 Sending control 'CMD SETPOWER 20' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP SETPOWER 0 20'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: SETPOWER***
<000b> trx_if.c:424 ***RSPNAME: SETPOWER***
<000b> trx_if.c:425 ***TCM_PARAMS: 20***
<000b> trx_if.c:426 ***PARAMS: 20***
<000b> trx_if.c:160 Sending control 'CMD SETSLOT 0 5' to phy0.0
<000b> trx_if.c:457 Response message: 'RSP SETSLOT 0 5'
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: SETSLOT***
<000b> trx_if.c:424 ***RSPNAME: SETSLOT***
<000b> trx_if.c:425 ***TCM_PARAMS: 0 5***
<000b> trx_if.c:426 ***PARAMS: 5***
<000b> trx_if.c:422 #############################
<000b> trx_if.c:423 ***TCM_CMD: SETPOWER***
<000b> trx_if.c:424 ***RSPNAME: SETSLOT***
<000b> trx_if.c:425 ***TCM_PARAMS: 20***
<000b> trx_if.c:426 ***PARAMS: 5***
<000b> trx_if.c:489 Response message 'RSP SETSLOT 0 5' does not match command message 'CMD SETSLOT 0 5'
<0001> bts.c:210 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
<000b> trx_if.c:240 Enqueuing TRX control command 'CMD POWEROFF'
<000b> trx_if.c:124 Clock indication: fn=1325341
<000b> trx_if.c:124 Clock indication: fn=1325389
<000b> trx_if.c:124 Clock indication: fn=1325440
...
</pre><br />SETPOWER does not match SETSLOT so cmd_matches_rsp returns false.</p>
<p>Full logs, configs and a pcap trace is attached.</p> GSM Audio Pocket Knife - Bug #2934 (Resolved): GSM EFR decoding result for conv/dec/ti_efr does n...https://osmocom.org/issues/29342018-02-12T19:35:51Zroox
<p>There's a decoding issue for conv/dec/ti_efr (test 22).</p>
<p>The other failures with HR encodings (tests: 6,9,13,14) are known issues.<br />See <a class="external" href="https://osmocom.org/issues/2514">https://osmocom.org/issues/2514</a> for details.</p>
<pre>
Regression tests.
1: procqueue ok
2: io/pq_file ok
3: io/pq_rtp ok
4: conv/enc/amr_efr ok
5: conv/enc/gsm ok
6: conv/enc/racal_hr FAILED (testsuite.at:52)
7: conv/enc/racal_fr ok
8: conv/enc/racal_efr ok
9: conv/enc/ti_hr FAILED (testsuite.at:85)
10: conv/enc/ti_fr ok
11: conv/enc/ti_efr ok
12: conv/enc/rtp_efr ok
13: conv/enc/rtp_hr_etsi FAILED (testsuite.at:129)
14: conv/enc/rtp_hr_ietf FAILED (testsuite.at:140)
15: conv/dec/amr_efr ok
16: conv/dec/gsm ok
17: conv/dec/racal_hr ok
18: conv/dec/racal_fr ok
19: conv/dec/racal_efr ok
20: conv/dec/ti_hr ok
21: conv/dec/ti_fr ok
22: conv/dec/ti_efr FAILED (testsuite.at:228)
23: conv/dec/rtp_efr ok
24: conv/dec/rtp_hr_etsi ok
25: conv/dec/rtp_hr_ietf ok
</pre>
<p>I have attached the full buildlog.</p> GSM Audio Pocket Knife - Bug #2926 (Resolved): GSM HR related tests run even when compiled with -...https://osmocom.org/issues/29262018-02-10T19:49:30Zroox
<p>These tests have to fail since HR support was not build in...</p>
<pre>
...
[ 40s] # -*- compilation -*-
[ 40s] 14. testsuite.at:126: testing conv/enc/rtp_hr_ietf ...
[ 40s] ./testsuite.at:129:
[ 40s] $abs_top_builddir/src/osmo-gapk \
[ 40s] -i $abs_srcdir/ref-files/hhgttg_part1_5.s16 \
[ 40s] -f rawpcm-s16le -g rtp-hr-ietf
[ 40s]ยท
[ 40s] stderr:
[ 40s] <0000> app_osmo_gapk.c:335 Encoding to 'hr' codec is unsupported
...
</pre>
<p>Full buildlog and testsuite.log attached.</p> OsmocomBB - Feature #2913 (New): Add a tool that decodes Cell Broadasts (SMSCB)https://osmocom.org/issues/29132018-02-07T20:34:14Zroox
<p>Add tool to osmocom-bb that can decode SMS-CB and log data.</p>
<p>A good starting point is the work done by Alex Badea in 2010 and 2013:</p>
<ol>
<li>changes to libosmocore (even with unit tests)<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003871.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003871.html</a></li>
<li>changes to cell_log<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003887.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003887.html</a></li>
<li>changes to L1 (already merged in sylvain/testing)<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003835.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003835.html</a><br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003836.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003836.html</a></li>
</ol>
<p>There were reasons a that time to not to include these patches into master.</p>
<p>Time went by and now there's even initial support for SMSCB in OsmoBTS/OsmoBSC.<br /><a class="external" href="https://osmocom.org/projects/cellular-infrastructure/wiki/Cell_Broadcast">https://osmocom.org/projects/cellular-infrastructure/wiki/Cell_Broadcast</a></p>
<p>An interesting use-case for (at least for germans) could be the mapping of older BTS from VIAG-Interkom/O2 that still broadcast their locations in Gauss Krueger coordinates.<br />I've written a perl script that uses the logs from Alex Badeas patched cell_log to generate a KML file with the BTS's coordinates.</p> GSM Audio Pocket Knife - Bug #2907 (Resolved): Paralllel builds are brokenhttps://osmocom.org/issues/29072018-02-01T21:55:49Zroox
<p>Parallel builds are broken in master (since the library integration).</p>
<pre>
...
[ 28s] gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -Wall -I/usr/include/libosmocore/ -I/usr/include/libosmocore/ -I/usr/include/alsa -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -c -o app_osmo_gapk.o app_osmo_gapk.c
[ 28s] make[2]: *** No rule to make target '../src/libosmogapk.la', needed by 'osmo-gapk'. Stop.
[ 28s] make[2]: *** Waiting for unfinished jobs....
[ 28s] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -Wall -I/usr/include/libosmocore/ -I/usr/include/libosmocore/ -I/usr/include/alsa -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -c benchmark.c -fPIC -DPIC -o .libs/benchmark.o
[ 28s] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -Wall -I/usr/include/libosmocore/ -I/usr/include/libosmocore/ -I/usr/include/alsa -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -c common.c -fPIC -DPIC -o .libs/common.o
[ 28s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/gapk-0.4.59/src'
[ 28s] make[1]: *** [Makefile:475: all-recursive] Error 1
[ 28s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/gapk-0.4.59'
[ 28s] make: *** [Makefile:384: all] Error 2
</pre>
<p>Full buildlog attached...</p>