Hi, 

I figured out that the issue is in connectivity between BSC and BTS. I am able to fix half of the issue. I would appreciate any further guidance. 

Firstly, I ran only BTS module. In the BTS log, I see an OML connection established. Transcribed are the logs.

<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:1024 enabling ipaccess BTS mode, OML connecting to 127.0.0.1:3002
<000b> trx_if.c:1174 phy0.0: Open transceiver
<0012> input/ipa.c:128 127.0.0.1:3002 connection done
<0012> input/ipaccess.c:846 received ID_GET for unit ID 1800/0/0
<000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF)

It again fails to get any response. 

Next, I ran the combination of TRX-UHD module and BTS module. I failed to get even OML connection. 

<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:1024 enabling ipaccess BTS mode, OML connecting to 127.0.0.1:3002
<000b> trx_if.c:1174 phy0.0: Open transceiver
<000d> abis.c:142 Signalling link down
<0001> bts.c:292 Shutting down BTS 0, Reason Abis close
Shutdown timer expired

I could see only this in trace. 

Thanks for the help.

On Tue, 14 Apr 2020 at 16:27, Aalto Koskinen <aaltokoskinen@gmail.com> wrote:

Hi Vadim and Pau,

Thank you for the quick replies.

Pau: Probably your guess is correct. I am looking into it in detail at the moment the core network configurations.
Vadim: I started osmo-trx first and waited until the message "Transceiver active with 1 channel(s)", before running osmo-bts-trx and other modules.
I will look into the wireshark capture to ensure that there are RSL and OML packets. Yes. I am using the configuration examples from https://osmocom.org/attachments/3473/nitb.tar. I am not sure, how to test osmo-bsc is actually running on 192.168.122.1 (I guess, I have to ping to ensure). Meanwhile, is there a basic configuration where I can run the system? Can I find it somewhere(I tried to run /usr/local/etc/osmocom config files and it didn't work. Probably, I have to fine tune the configurations)? And, is there a wireshark trace by any chance for reference? 

On Thu, 9 Apr 2020 at 15:39, Pau Espin Pedrol <pespin@sysmocom.de> wrote:

Hi,

I have the feeling the connection between osmo-trx and osmo-bts-trx is
good. The problem is that your BTS<->BSC<->... is failing.

BTs shows these messages at startup because osmo-trx is not yet running:
""""
 > osmo-bts-trx[23221]: <000b> trx_if.c:1174 phy0.0: Open transceiver
 > osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory
 > response from transceiver(CMD POWEROFF)
"""

Then at some point osmo-trx answers:
"""
 > ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr  9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
 > ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr  9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
"""

But it's already too late, the BTS is already exiting due to some issue
in Abis:
"""
 > osmo-bts-trx[23221]: <000d> abis.c:142 Signalling link down
 > osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason
Abis close
"""

Regards,
Pau

--
- Pau Espin Pedrol <pespin@sysmocom.de>         http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte