Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-09-17T11:16:59ZOpen Source Mobile Communications
Redmine Cellular Network Infrastructure - Bug #3559 (Closed): CBCH on timeslot 0 not workinghttps://osmocom.org/issues/35592018-09-17T11:16:59Zduo_kali
<p>Tested with CCCH+SDCCH4+CBCH on timeslot 0 and phone doesnt camp and there is no any indication at all in the trace to debug, it seems look BTS transmit the wrong channel or something. (test with asus and blackberry phone)</p>
<p>Then second test, I delete CBCH on timeslot 0 then put SDCCH8+CBCH on timeslot 1, its working.</p>
<p>The PCAP attached.</p> osmo-sip-connector - Support #3550 (Closed): No voice when using osmo-sip in new splits with aste...https://osmocom.org/issues/35502018-09-13T08:17:42Zduo_kali
<p>Is this a codec matter in osmo-mgw cause I saw this "can not patch PT because no suitable egress codec was found".</p>
<p>the PCAP attached.</p>
<p>and here is the log :</p>
<p>osmo-msc : <a class="external" href="https://pastebin.com/Lkf3er3Y">https://pastebin.com/Lkf3er3Y</a><br />osmo-bsc : <a class="external" href="https://pastebin.com/ktLHU3iw">https://pastebin.com/ktLHU3iw</a><br />osmo-mgw : <a class="external" href="https://pastebin.com/tY4w7HrQ">https://pastebin.com/tY4w7HrQ</a><br />osmo-sip : <a class="external" href="https://pastebin.com/uThEskgH">https://pastebin.com/uThEskgH</a></p>
<p>Note: Voice is working normal without osmo-sip-connector.</p>
<p>Thanks.</p> OsmoTRX - Support #3547 (Closed): LimeSDR-USB experience with osmo-trxhttps://osmocom.org/issues/35472018-09-11T08:27:08Zduo_kali
<p>Testing with all LimeSDR-USB firmware,I found the firmware/gateware version: <strong>LimeSDR-USB_HW_1.3_r3.0.img and LimeSDR-USB_HW_1.4_r2.9.rbf</strong> from LimeSuite V.17.09.0 seems the most stable and having the best performance any other releases or latest firmware.</p>
<p>Check with osmo-trx-lms also fine (after switched back from latest firmware to the version I mention) but compare to the osmo-trx legacy i had, the performance is better using the osmo-trx old one.</p>
<p>btw,<br />The old osmo-trx I have is more stable with the firmware I mention when using openbsc/osmo-nitb.</p>
<p>I hope this one can be fix and maybe can look from the old osmo-trx version that I attached and why this one perform better.</p>
<p>This version also I get voice working sometimes with the new splits, but seems sdr failure with not the right firmware could be the problem?</p>
<p>Please check the firmware I mention and hope can make the osmo-trx-lms can build and support with oldest LimeSuite version.</p>
<p>Thanks.</p> OsmoMGW - Bug #3539 (Resolved): osmo-mgw data from wrong address: 127.0.0.1, expected: 0.0.0.0https://osmocom.org/issues/35392018-09-09T18:54:32Zduo_kali
<p>osmo-mgw log showing the error : data from wrong address: 127.0.0.1, expected: 0.0.0.0</p>
<p>this is the log file <a class="external" href="https://pastebin.com/6N00ZCGj">https://pastebin.com/6N00ZCGj</a></p> Cellular Network Infrastructure - Bug #3538 (Rejected): osmo-mgw data from wrong address: 127.0.0...https://osmocom.org/issues/35382018-09-09T18:21:54Zduo_kali
<p>osmo-mgw log showing the error : data from wrong address: 127.0.0.1, expected: 0.0.0.0</p>
<p>this is the log file <a class="external" href="https://pastebin.com/6N00ZCGj">https://pastebin.com/6N00ZCGj</a></p> OsmoTRX - Bug #2816 (Closed): osmo-trx-uhd: bug with limesdr send timed outhttps://osmocom.org/issues/28162018-01-02T06:41:32Zduo_kali
<p>osmo-trx became not more stable in the new master and sometime doesnt want connect at all. (im using limesdr)<br />pcaps attached.</p>
<p>its probably also affect by osmo-bts-trx which looks has problem since new updated with new libosmocore.</p>
<pre>
ce
NOTICE 139651202938624 12:46:07.9 Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP interface
NOTICE 139651202938624 12:46:07.9 Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP interface
NOTICE 139651202938624 12:46:07.9 Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP interface
NOTICE 139651202938624 12:46:07.9 Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP interface
NOTICE 139651202938624 12:46:08.0 Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP interface
NOTICE 139651202938624 12:46:08.0 Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP interface
INFO 139651202905856 12:46:08.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2093830
INFO 139651202905856 12:46:09.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2094047
WARNING 139650995844864 12:46:09.8 UHDDevice.cpp:338:uhd_msg_handler: L
WARNING 139650995844864 12:46:10.3 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:10.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2094264
WARNING 139650995844864 12:46:11.4 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:11.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2094481
INFO 139651202905856 12:46:12.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2094697
WARNING 139650995844864 12:46:13.4 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:13.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2094914
WARNING 139650995844864 12:46:14.4 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:14.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2095130
INFO 139651202905856 12:46:15.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2095347
WARNING 139650995844864 12:46:15.6 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:16.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2095564
WARNING 139650995844864 12:46:16.5 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:17.5 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2095781
WARNING 139650995844864 12:46:17.5 UHDDevice.cpp:338:uhd_msg_handler: L
WARNING 139650995844864 12:46:17.6 UHDDevice.cpp:338:uhd_msg_handler: L
INFO 139651202905856 12:46:18.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2096040
INFO 139651202905856 12:46:19.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2096257
INFO 139651202905856 12:46:20.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2096474
INFO 139651202905856 12:46:21.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2096691
INFO 139651202905856 12:46:22.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2096908
INFO 139651202905856 12:46:23.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2097125
INFO 139651202905856 12:46:24.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2097341
INFO 139651202905856 12:46:25.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2097558
INFO 139651202905856 12:46:26.7 Transceiver.cpp:1002:writeClockInterface: ClockInterface: sending IND CLOCK 2097775
ALERT 139651202938624 12:46:27.3 UHDDevice.cpp:1022:writeSamples: UHD: Device send timed out
ALERT 139651202938624 12:46:27.3 UHDDevice.cpp:1022:writeSamples: UHD: Device send timed out
<pre></pre> osmo-sip-connector - Bug #2786 (Closed): osmo-sip-connector segfault with kali rolling https://osmocom.org/issues/27862017-12-28T13:13:08Zduo_kali
<p>Tried with ubuntu was fine then this happen with kali rolling.</p>
<p>the segmentation fault here:<br /><a class="external" href="https://pastebin.com/crS8bkdn">https://pastebin.com/crS8bkdn</a></p>
<p>It showing sourceport nameserver is connect to wlan0 like this :<br /><0004> telnet_interface.c:104 telnet at 127.0.0.1 4256<br /><0001> mncc.c:879 Scheduling MNCC connect<br />su_source_port_create() returns 0x5555557bf4a0<br />sres: nameserver fe80::1%wlan0: invalid address<br /><0001> mncc.c:786 Reconnected to /tmp/bsc_mncc<br /><0001> mncc.c:699 Got hello message version 5</p>
<p>in ubuntu is fine and has create good sourceport.</p>
<p>Thanks.</p>