Project

General

Profile

Actions

Support #4358

closed

CalypsoBTS: No satisfactory response from transceiver

Added by enceladusspace over 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
CalypsoBTS
Target version:
-
Start date:
01/11/2020
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

Good evening, Moscow time, I’m still a beginner in your project, but have already learned something, stopped at one of the stages, I get the following output in the terminal (I attach the screenshot and output) I use the configuration files with github, how do I gradually correct the settings and files?

root@space:~/.osmocom# osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM
<001e> telnet_interface.c:104 Available via telnet 127.0.0.1 4242
<0020> input/ipaccess.c:863 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports
<0025> control_if.c:911 CTRL at 127.0.0.1 4249
DB: Database initialized.
DB: Database prepared.
<0020> input/ipa.c:287 0.0.0.0:3002 accept()ed new link from 127.0.0.1:46113
<0005> abis_nm.c:497 BTS0 Get Attributes Response: reported unexpectedly long (3 bytes) feature vector - most likely it was compiled against newer BSC headers. Consider upgrading your BSC to later version.
<0005> abis_nm.c:507 BTS0 feature 'EGPRS' reported via OML does not match statically set feature: 0 != 1. Please fix.
<0005> abis_nm.c:507 BTS0 feature 'OML Alerts' reported via OML does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:507 BTS0 feature 'CBCH' reported via OML does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:577 BTS0: failed to parse SW-Config part of Get Attribute Response Info: Invalid argument
<0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is unreported
<0005> abis_nm.c:577 BTS0: failed to parse SW-Config part of Get Attribute Response Info: Invalid argument
<0005> abis_nm.c:2757 (bts=0,trx=0) IPA RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00
<0020> input/ipa.c:287 0.0.0.0:3003 accept()ed new link from 127.0.0.1:39653
<0004> bsc_init.c:312 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 975 using MCC-MNC 001-01 LAC=1 CID=0 BSIC=63

root@space:~/.osmocom# osmo-bts-trx --debug DRSL:DOML:DLAPDM -r 99((*)) |
/ \ OsmoBTS
<0001> oml.c:1462 Initializing OML attribute definitions
<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:901 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:724 received ID_GET for unit ID 1801/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:641 OC=BTS INST=(00,ff,ff): Ignoring T2000 (150 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:641 OC=BTS INST=(00,ff,ff): Ignoring T2001 (180 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:641 OC=BTS INST=(00,ff,ff): Ignoring T2002 (180 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:641 OC=BTS INST=(00,ff,ff): Ignoring T2003 (1680 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:641 OC=BTS INST=(00,ff,ff): Ignoring T2004 (520 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:641 OC=BTS INST=(00,ff,ff): Ignoring T2005 (165 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:641 OC=BTS INST=(00,ff,ff): Ignoring T2006 (1680 ms) as sent by BSC due to suspected LAPDm bug!
<0012> input/ipa.c:128 127.0.0.1:3003 connection done
<0012> input/ipaccess.c:724 received ID_GET for unit ID 1801/0/0
<0009> sysinfo.c:199 Disabling GPRS Indicator in SI3 (No PCU connected)
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:610 Failed to send SI13 to PCU: -5
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<0009> pcu_sock.c:740 PCU socket not connected, dropping message
<000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF)


Files

1.png View 1.png 230 KB enceladusspace, 01/11/2020 05:23 PM
2.png View 2.png 99.7 KB enceladusspace, 01/11/2020 05:23 PM
111.png View 111.png 226 KB enceladusspace, 01/12/2020 09:40 AM
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)