Hi,
the problem is not in osmo-bts-trx <-> osmo-trx, that's working fine so
far on your setup (sending a POWEROFF at startup is fine since then it
makes sure the osmo-trx is powered off before configuring it and finally
running POWERON on it). It won't be configured until the BSC (in your
case osmo-nitb) instructs osmo-bts-trx on how to do it through Abis OML
connection.
The problem is here:
On 5/9/20 3:15 AM, cruise wrote:
*_/About one minutes later, the osmo-bts-trx will exit
automatically,
and the following messages was printed./_*
<0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 90 0f 00 c8
<0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 88 12 06
00 00 00 00 00 00
<000d> abis.c:143 Signalling link down
<0001> bts.c:293 Shutting down BTS 0, Reason Abis close
Shutdown timer expired
The Abis connection, be it OML or RSL, between the BTS and the BSC (in
your case osmo-nitb) fails at some point. Unfortunately unless you
provide config files, complete logs and pcap files it's difficult to
tell you more. Please next time provide those while reporting.
*3. osmo-nitb*
FYI, osmo-ntib is deprecated and not maintained since years ago.
Please better use new software stack:
https://osmocom.org/projects/cellular-infrastructure/wiki
--
- Pau Espin Pedrol <pespin(a)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