Bug #4198
closedIgnoring TX data, transceiver offline.
Added by emersonjr over 4 years ago. Updated about 3 years ago.
0%
Description
I'm running 0smo-TRX + Osmo-BTS-TRX with USRP B100 on a Debian 8 using an Intel(R) Atom(TM) CPU N2800 1.86GHz, which remotely connects to an OsmoNITB station on the same network, Debian 8 Intel(R) Core(TM) i5-7600 CPU 3.50GHz. Network is generated and mobile stations can join correctly, however no voice is deployed upon making calls. What sounds weird is that we use exactly the same setup on OsmoNITB station altogether and there is voice as expected.
Upon running Osmo-BTS-TRX after Osmo-TRX, some error messages show up, regarding unsupported messaging format on the logs of both softwares.
I'm attaching links to pastebin of logs at the bottom.
Does anyone have any idea?
Osmo-BTS-TRX
https://pastebin.com/zKCHEzRk
Osmo-TRX
https://pastebin.com/2FwRuHFb
Files
| osmo-trx.cfg | osmo-trx.cfg | 355 Bytes | emersonjr, 09/13/2019 05:46 PM | ||
| osmo-bts-trx.cfg | osmo-bts-trx.cfg | 600 Bytes | emersonjr, 09/13/2019 05:46 PM |
Updated by emersonjr over 4 years ago
emersonjr wrote:
I'm running 0smo-TRX + Osmo-BTS-TRX with USRP B100 on a Debian 8 using an Intel(R) Atom(TM) CPU N2800
1.86GHz, which remotely connects to an OsmoNITB station on the same network, Debian 8 Intel(R) Core(TM) i5-7600 CPU3.50GHz. Network is generated and mobile stations can join correctly, however no voice is deployed upon making calls. What sounds weird is that we use exactly the same setup on OsmoNITB station altogether and there is voice as expected.Upon running Osmo-BTS-TRX after Osmo-TRX, some error messages show up, regarding unsupported messaging format on the logs of both softwares.
I'm attaching links to pastebin of logs at the bottom.
Does anyone have any idea?
Osmo-BTS-TRX
https://pastebin.com/zKCHEzRkOsmo-TRX
https://pastebin.com/2FwRuHFb
emersonjr wrote:
I'm running 0smo-TRX + Osmo-BTS-TRX with USRP B100 on a Debian 8 using an Intel(R) Atom(TM) CPU N2800
1.86GHz, which remotely connects to an OsmoNITB station on the same network, Debian 8 Intel(R) Core(TM) i5-7600 CPU3.50GHz. Network is generated and mobile stations can join correctly, however no voice is deployed upon making calls. What sounds weird is that we use exactly the same setup on OsmoNITB station altogether and there is voice as expected.Upon running Osmo-BTS-TRX after Osmo-TRX, some error messages show up, regarding unsupported messaging format on the logs of both softwares.
I'm attaching links to pastebin of logs at the bottom.
Does anyone have any idea?
Osmo-BTS-TRX
https://pastebin.com/zKCHEzRkOsmo-TRX
https://pastebin.com/2FwRuHFb
Updating
I managed to solve the error messages from both softwares, but calls still hook without voice
Updated by laforge over 4 years ago
- Priority changed from High to Low
OsmoNITB is completely unmaintained and not supported for several years now.
I'm worried you might be running an equally ancient version of OsmoTRX / OsmoBTS. Can yo please post the version information ("show version" on the respective VTY, or use the respective command line argument to make it print the version).
Also, please don't post links to pastebin. If somebody looks at this issue in 3 years from now, can you guarantee that the content is still there? Please include it here using the "< pre >" and "< /pre >" tags
Updated by laforge over 4 years ago
Sidenote: please also note that Debian 8 is unmaintained at this point. Security updates have been discontinued since june 2018, more than a a year ago: https://www.debian.org/releases/jessie/
Updated by emersonjr over 4 years ago
- File osmo-trx.cfg osmo-trx.cfg added
- File osmo-bts-trx.cfg osmo-bts-trx.cfg added
That's right, I'm including the error messages below:
Osmo-BTS
((*)) | / \ OsmoBTS <0017> control_if.c:911 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:104 Available via telnet 127.0.0.1 4241 <0012> input/ipaccess.c:897 enabling ipaccess BTS mode, OML connecting to 200.239.93.116:3002 <000b> trx_if.c:1155 phy0.0: Open transceiver <0012> input/ipa.c:128 200.239.93.116:3002 connection done <0012> input/ipaccess.c:720 received ID get from 1000/0/0 <0001> oml.c:220 (bts=0,trx=0): O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX. <0001> oml.c:507 OC=BASEBAND-TRANSCEIVER(04) INST=(00,01,ff): Get Attributes for unknown Object Instance <0001> oml.c:446 OC=BASEBAND-TRANSCEIVER(04) INST=(00,01,ff): Sending FOM NACK with cause Object Instance unknown. <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:641 OC=BTS(01) INST=(00,ff,ff): Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0012> input/ipa.c:128 200.239.93.116:3003 connection done <0012> input/ipaccess.c:720 received ID get from 1000/0/0 <000b> trx_if.c:612 phy0.0: Response message 'RSP ERR 1' does not match command message 'CMD SETFORMAT 1' <000b> trx_if.c:488 phy0.0: Transceiver rejected the format negotiation command, using legacy TRXD header format version (0) <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline. <000b> trx_if.c:1096 phy0.0: Ignoring TX data, transceiver offline.
Osmo-TRX
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown opening configuration table from path :memory: Info: SSE3 support compiled in and supported by CPU Info: SSE4.1 support compiled in, but not supported by CPU Config Settings Log Level............... NOTICE Device args............. serial=E2R15U8B1 TRX Base Port........... 5700 TRX Address............. 127.0.0.1 GSM Core Address.........127.0.0.1 Channels................ 1 Tx Samples-per-Symbol... 4 Rx Samples-per-Symbol... 1 EDGE support............ Disabled Reference............... Internal C0 Filler Table......... Dummy bursts Multi-Carrier........... Disabled Tuning offset........... 0 RSSI to dBm offset...... 0 Swap channels........... 0 -- USRP-B100 clock control: 10 -- r_counter: 2 -- a_counter: 0 -- b_counter: 20 -- prescaler: 8 -- vco_divider: 5 -- chan_divider: 5 -- vco_rate: 1600.000000MHz -- chan_rate: 320.000000MHz -- out_rate: 64.000000MHz -- -- Loading FPGA image: /usr/share/uhd/images/usrp_b100_fpga.bin... done -- Transceiver active with 1 channel(s) NOTICE 139805836887808 17:05:26.2 Transceiver.cpp:791:driveControl: Changing TSC from 0 to 7 WARNING 139805836887808 17:05:26.2 Transceiver.cpp:820:driveControl: bogus command SETFORMAT on control interface. NOTICE 139805836887808 17:05:26.2 Transceiver.cpp:244:start: Starting the transceiver ERR 139805703104256 17:05:26.3 UHDDevice.cpp:844:check_rx_md_err: An internal receive buffer has filled at 104.424 sec. ERR 139805703104256 17:05:26.3 UHDDevice.cpp:844:check_rx_md_err: An internal receive buffer has filled at 104.424 sec. ERR 139805703104256 17:05:26.3 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=41772016 time_end=41768433 ERR 139805703104256 17:05:26.3 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=41772016 time_end=41768433
At this point I'm using OsmoTRX from commit aa60dda99a22f6a60d5c6f9b08d50febe49757ef, which we use in another workstation and it works. I'm referencing the commit here because this version has no command line argument to make it print its version nor VTY to interact with.
Osmo-BTS version is 1.1.0.4-f53f
OsmoBTS 1.1.0.4-f53f (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.
I managed to solve the error messages changing used OsmoBTS version to 0.8.1
OsmoBTS> show version OsmoBTS 0.8.1 (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.
But still no voice appeared on calls, just silence and a very low noise, which we could hear only be putting the cellphone very close to our ear.
I also updated OsmoTRX to latest version, using Osmo-TRX-UHD, but unfortunately seemingly gone for nothing.
root@obac01:/home/obac# osmo-trx-uhd -C osmo-trx.cfg
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in, but not supported by CPU
Fri Sep 13 14:39:34 2019 DLGLOBAL <0004> telnet_interface.c:104 Available via telnet 127.0.0.1 4237
Fri Sep 13 14:39:34 2019 DLCTRL <000b> control_if.c:911 CTRL at 127.0.0.1 4236
Fri Sep 13 14:39:34 2019 DMAIN <0000> osmo-trx.cpp:480 [tid=140597594882752] Config Settings
Log Level............... 0
Device args.............
TRX Base Port........... 5700
TRX Address............. 127.0.0.1
GSM BTS Address......... 127.0.0.1
Channels................ 1
Tx Samples-per-Symbol... 1
Rx Samples-per-Symbol... 1
EDGE support............ 0
Extended RACH support... 0
Reference............... 0
C0 Filler Table......... 1
Multi-Carrier........... 0
Tuning offset........... 0
RSSI to dBm offset...... 0
Swap channels........... 0
Tx Antennas............. 'TX/RX'
Rx Antennas............. 'TX/RX'
Fri Sep 13 14:39:35 2019 DDEV <0002> UHDDevice.cpp:430 [tid=140597594882752] Using discovered UHD device type=b200,name=MyB210,serial=318A038,product=B210
-- USRP-B100 clock control: 10
-- r_counter: 2
-- a_counter: 0
-- b_counter: 20
-- prescaler: 8
-- vco_divider: 5
-- chan_divider: 5
-- vco_rate: 1600.000000MHz
-- chan_rate: 320.000000MHz
-- out_rate: 64.000000MHz
--
Fri Sep 13 14:39:36 2019 DMAIN <0000> UHDDevice.cpp:206 [tid=140597594882752] Antennas configured successfully
Fri Sep 13 14:39:36 2019 DDEV <0002> UHDDevice.cpp:245 [tid=140597594882752] Rates configured for B100 1 SPS
Fri Sep 13 14:39:36 2019 DDEV <0002> UHDDevice.cpp:205 [tid=140597594882752] Supported Tx gain range [-20; 31]
Fri Sep 13 14:39:36 2019 DDEV <0002> UHDDevice.cpp:210 [tid=140597594882752] Supported Rx gain range [0; 51.5]
Fri Sep 13 14:39:36 2019 DDEV <0002> UHDDevice.cpp:214 [tid=140597594882752] Default setting Tx gain for channel 0 to 5.5
Fri Sep 13 14:39:36 2019 DDEV <0002> UHDDevice.cpp:221 [tid=140597594882752] Default setting Rx gain for channel 0 to 25.75
Fri Sep 13 14:39:36 2019 DDEV <0002> UHDDevice.cpp:529 [tid=140597594882752]
Single USRP:
Device: B-Series Device
Mboard 0: B100
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv3 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv3 TX+GDB
Fri Sep 13 14:39:36 2019 DMAIN <0000> Threads.cpp:117 [tid=140597365044992] Thread 140597365044992 (task 22520) set name: CtrlService0
Fri Sep 13 14:39:36 2019 DMAIN <0000> osmo-trx.cpp:528 [tid=140597594882752] -- Transceiver active with 1 channel(s)
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'POWEROFF'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP POWEROFF 0'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'POWEROFF'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP POWEROFF 0'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'RXTUNE 903000'
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:894 [tid=140597365044992]
Tune Result:
Target RF Freq: 903.000000 (MHz)
Actual RF Freq: 902.999105 (MHz)
Target DSP Freq: -0.000895 (MHz)
Actual DSP Freq: -0.000895 (MHz)
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP RXTUNE 0 903000'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'TXTUNE 948000'
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:894 [tid=140597365044992]
Tune Result:
Target RF Freq: 948.000000 (MHz)
Actual RF Freq: 947.999674 (MHz)
Target DSP Freq: 0.000326 (MHz)
Actual DSP Freq: 0.000326 (MHz)
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP TXTUNE 0 948000'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETTSC 7'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:878 [tid=140597365044992] Changing TSC from 0 to 7
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETTSC 0 7'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'POWERON'
Fri Sep 13 14:39:45 2019 DMAIN <0000> Transceiver.cpp:280 [tid=140597365044992] Starting the transceiver
Fri Sep 13 14:39:45 2019 DMAIN <0000> radioInterface.cpp:180 [tid=140597365044992] Starting radio device
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:600 [tid=140597365044992] Starting USRP...
Fri Sep 13 14:39:45 2019 DMAIN <0000> Threads.cpp:117 [tid=140597356652288] Thread 140597356652288 (task 22522) set name: UHDAsyncEvent
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:575 [tid=140597365044992] Initial timestamp 4028286
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:621 [tid=140597365044992] The current time is 10.074 seconds
Fri Sep 13 14:39:45 2019 DMAIN <0000> radioInterface.cpp:201 [tid=140597365044992] Radio started
Fri Sep 13 14:39:45 2019 DMAIN <0000> Threads.cpp:117 [tid=140597348259584] Thread 140597348259584 (task 22523) set name: TxLower
Fri Sep 13 14:39:45 2019 DMAIN <0000> Threads.cpp:117 [tid=140597339866880] Thread 140597339866880 (task 22524) set name: RxLower
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP POWERON 0'
Fri Sep 13 14:39:45 2019 DMAIN <0000> Threads.cpp:117 [tid=140597323081472] Thread 140597323081472 (task 22526) set name: TxUpper0
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETRXGAIN 1'
Fri Sep 13 14:39:45 2019 DMAIN <0000> Transceiver.cpp:1114 [tid=140597339866880] ClockInterface: sending IND CLOCK 353011
Fri Sep 13 14:39:45 2019 DMAIN <0000> Threads.cpp:117 [tid=140597331474176] Thread 140597331474176 (task 22525) set name: RxUpper0
Fri Sep 13 14:39:45 2019 DMAIN <0000> Transceiver.cpp:1139 [tid=140597331474176][chan=0] Something went wrong in thread RxUpper0, requesting stop
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:295 [tid=140597365044992] Set RX gain to 1dB (asked for 1dB)
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETRXGAIN 0 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETPOWER 0'
Fri Sep 13 14:39:45 2019 DDEV <0002> UHDDevice.cpp:277 [tid=140597365044992] Set TX gain to 31dB (asked for 31dB)
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETPOWER 0 0'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 0 4'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 0 4'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 1 7'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 1 7'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 2 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 2 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 3 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 3 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 4 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 4 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 5 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 5 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 6 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 6 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:776 [tid=140597365044992][chan=0] command is 'SETSLOT 7 1'
Fri Sep 13 14:39:45 2019 DTRXCTRL <0001> Transceiver.cpp:921 [tid=140597365044992][chan=0] response is 'RSP SETSLOT 0 7 1'
Fri Sep 13 14:39:46 2019 DMAIN <0000> osmo-trx.cpp:485 [tid=140597594882752] Shutting down transceiver...
Fri Sep 13 14:39:46 2019 DMAIN <0000> Transceiver.cpp:338 [tid=140597594882752] Stopping the transceiver
Fri Sep 13 14:39:46 2019 DMAIN <0000> Transceiver.cpp:351 [tid=140597594882752] Stopping the device
Fri Sep 13 14:39:46 2019 DMAIN <0000> Transceiver.cpp:364 [tid=140597594882752] Transceiver stopped
I'm attaching here my .cfg files as well, for further analysis. Any further infos needed, i can provide.
Updated by laforge about 3 years ago
- Tracker changed from Support to Bug
- Status changed from New to Rejected
rejecting. OsmoNITB is ancient, unsupported and predates the OsmoMGW based user plane flows that we have (and continuously test) these days.
