Hi All,

Upon running "osmo-bts-trx -c osmo-bts.cfg” while "osmo-nitb -C -c openbsc.conf 
-T -P -m” and “osmo-trx” are running, the following error shows and also shuts 
down “osmo-trx”

osmo-bts-trx error:


root@entropy:~/osmocom_files# osmo-bts-trx -c osmo-bts.cfg

((*))

  |

 / \ OsmoBTS

<0017> control_if.c:725 CTRL at 127.0.0.1 4238

<0010> telnet_interface.c:95 telnet at 127.0.0.1 4241

<0012> input/ipaccess.c:885 enabling ipaccess BTS mode, OML connecting to 
192.168.1.129:3002

<000b> trx_if.c:584 Open transceiver for phy0.0

<0012> input/ipa.c:129 connection done.

<0012> input/ipaccess.c:706 received ID get

<0001> oml.c:475 Ignoring T200[0] (150 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:475 Ignoring T200[1] (180 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:475 Ignoring T200[2] (180 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:475 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:475 Ignoring T200[4] (520 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:475 Ignoring T200[5] (165 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:475 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected 
LAPDm bug!

<0001> oml.c:844 ADM state already was Unlocked

<0012> input/ipa.c:129 connection done.

<0012> input/ipaccess.c:706 received ID get

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<0009> pcu_sock.c:651 PCU socket not connected, dropping message

<000b> trx_if.c:187 No response from transceiver for phy0.0

<0009> pcu_sock.c:848 PCU socket connected to external PCU

<0001> oml.c:72 Reporting FAILURE to BSC: 0.3.20170425

<0000> rsl.c:624 (bts=0,trx=0,ts=4,ss=0) not sending CHAN ACT ACK

<0000> rsl.c:624 (bts=0,trx=0,ts=5,ss=0) not sending CHAN ACT ACK

<0000> rsl.c:624 (bts=0,trx=0,ts=6,ss=0) not sending CHAN ACT ACK

<0000> rsl.c:624 (bts=0,trx=0,ts=7,ss=0) not sending CHAN ACT ACK

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<000b> trx_if.c:187 No response from transceiver for phy0.0

<0007> l1sap.c:413 Invalid condition detected: Frame difference is > 1!

<0001> bts.c:208 Shutting down BTS 0, Reason No clock from osmo-trx

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<0000> rsl.c:528 (bts=0,trx=0,ts=4,ss=0) not sending REL ACK

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<0000> rsl.c:528 (bts=0,trx=0,ts=5,ss=0) not sending REL ACK

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<0000> rsl.c:528 (bts=0,trx=0,ts=6,ss=0) not sending REL ACK

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please 
fix!

<0000> rsl.c:528 (bts=0,trx=0,ts=7,ss=0) not sending REL ACK

Shutdown timer expired

osmo-trx logs:


NOTICE 139966735525632 16:51:01.4 Transceiver.cpp:794:driveControl: Changing 
TSC from 0 to 7

NOTICE 139966735525632 16:51:01.4 Transceiver.cpp:243:start: Starting the 
transceiver

Illegal instruction (core dumped)

osmo-nitb logs:


Thu Apr 27 16:50:43 2017 <001e> input/ipa.c:263 accept()ed new link from 
192.168.1.129 to port 3002

Thu Apr 27 16:50:43 2017 <001e> input/ipa.c:263 accept()ed new link from 
192.168.1.129 to port 3003

Thu Apr 27 16:50:43 2017 <0004> bsc_init.c:288 bootstrapping RSL for BTS/TRX 
(0/0) on ARFCN 885 using MCC=1 MNC=1 LAC=1 CID=1 BSIC=63

BTS 0 reported connected PCU version 0.3.20170425

Thu Apr 27 16:51:06 2017 <001e> input/ipaccess.c:241 Sign link vanished, dead 
socket

Thu Apr 27 16:51:06 2017 <001e> input/ipaccess.c:69 Forcing socket shutdown 
with no signal link set

Thu Apr 27 16:51:06 2017 <0020> bsc_init.c:341 Lost some E1 TEI link: 1 
0x7f5f48820070

Thu Apr 27 16:51:06 2017 <0020> bsc_init.c:341 Lost some E1 TEI link: 2 
0x7f5f48820070

^Csignal 2 received


Also attached the configuration files used.

What seems causes the issue?

OS: Ubuntu 16.04
SDR: B210

Best Regards,

Ron Rylan B. Menez
Operations Manager
+63 998 989 7973
+63 2 893 1781

[cid:[email protected]]

Singapore * Philippines
Products:
Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development
This email (including any attachment to it) is confidential and intended only 
for the use of the individual named above and may contain information that is 
privileged. If you are not the intended recipient, you are notified that any 
dissemination, distribution or copying of this email is strictly prohibited. If 
you have received this email in error, please notify us immediately by return 
email or telephone and destroy the original message (including any attachment 
to it). Thank you.

Attachment: osmo-bts.cfg
Description: osmo-bts.cfg

Attachment: openbsc.conf
Description: openbsc.conf

Reply via email to