This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Pierre Kim admin at manateeshome.comWith the newest git repo version of osmo-bsc, my nanoBTS fails to start.
I can confirm that they work normally with ip.access softBSC.
I thought osmocom Redmine issue #3063 might be relevant and tried
setting/unsetting force-combined-si but I am still getting the same
result. Attached are the packet capture and bsc config file
The following is the log from osmo-bsc:
<0015> input/ipa.c:262 accept()ed new link from 192.168.27.40 to port 3002
<0004> abis_nm.c:847 OC=BTS(01) INST=(ff,ff,ff): GET ATTRIBUTE NACK
<0004> osmo_bsc_main.c:178 BTS0 does not support Get Attributes OML message.
<0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0:
ARI reported sw[0/5]: 168a004 is v136d0
<0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0:
ARI reported sw[1/5]: 168a002 is v136d0
<0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0:
ARI reported sw[2/5]: 168a002 is v136d0
<0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0:
ARI reported sw[3/5]: 168a001 is v136d0
<0004> abis_nm.c:560 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): BTS0:
ARI reported sw[4/5]: 168a001 is v136d0
<0004> abis_nm.c:494 BTS0 Attribute Manufacturer Dependent State is
unreported
<0004> abis_nm.c:2888 (bts=0,trx=0) IPA RSL CONNECT IP=0.0.0.0 PORT=3003
STREAM=0x00
<0015> input/ipa.c:262 accept()ed new link from 192.168.27.40 to port 3003
<0003> osmo_bsc_main.c:283 bootstrapping RSL for BTS/TRX (0/0) on ARFCN
600 using MCC-MNC 450-09 LAC=23 CID=0 BSIC=63
BTS 0: Failure Event Report: Type=processing failure, Severity=critical
failure, Probable cause=Manufacturer specific values: Fatal software
error, Additional Text=l2_bch.c:1149
****
** l2_bch.c#1149:BCHbcchSItypeValid( prim_p->infoType )
** IPA_SW_FATAL_ERROR
** In task "TRX Proc:L2_BCH" @ (325).
****
.
BTS 0: Failure Event Report: Type=processing failure, Severity=critical
failure, Probable cause=Manufacturer specific values: Fatal software
error, Additional Text=TRX Proc:L2_BCH:l2_bch.c#1149 (325).
BTS 0: Failure Event Report: Type=processing failure, Severity=warning
level failure, Probable cause=Manufacturer specific values: Software
warning, Additional
Text=31782:WARN:OAM_RES:trx_fatal_error_log.c#255:TRX has logged the error:
.
BTS 0: Failure Event Report: Type=processing failure, Severity=warning
level failure, Probable cause=Manufacturer specific values: Software
warning, Additional
Text=31782:WARN:OAM_RES:trx_fatal_error_log.c#256:TRX
Proc:L2_BCH:l2_bch.c#1149 (325)
-------------- next part --------------
!
! OsmoBSC (1.3.0.139-75f03) configuration saved from vty
!!
!
log stderr
logging filter all 1
logging color 1
logging print category 0
logging timestamp 0
logging print file 1
logging level rll notice
logging level mm notice
logging level rr notice
logging level rsl notice
logging level nm info
logging level pag notice
logging level meas notice
logging level msc notice
logging level ho notice
logging level hodec notice
logging level ref notice
logging level nat notice
logging level ctrl notice
logging level filter debug
logging level pcu debug
logging level lcls notice
logging level chan notice
logging level ts notice
logging level as notice
logging level lglobal notice
logging level llapd notice
logging level linp notice
logging level lmux notice
logging level lmi notice
logging level lmib notice
logging level lsms notice
logging level lctrl notice
logging level lgtp notice
logging level lstats notice
logging level lgsup notice
logging level loap notice
logging level lss7 notice
logging level lsccp notice
logging level lsua notice
logging level lm3ua notice
logging level lmgcp notice
logging level ljibuf notice
!
stats interval 5
!
line vty
no login
!
e1_input
e1_line 0 driver ipa
e1_line 0 port 0
no e1_line 0 keepalive
cs7 instance 0
point-code 0.23.3
network
network country code 450
mobile network code 09
encryption a5 1 3
neci 0
paging any use tch 0
bts 0
type nanobts
band PCS1900
cell_identity 0
location_area_code 23
base_station_id_code 63
ms max power 15
cell reselection hysteresis 4
rxlev access min 0
radio-link-timeout 32
channel allocator ascending
rach tx integer 9
rach max transmission 7
channel-descrption attach 1
channel-descrption bs-pa-mfrms 5
channel-descrption bs-ag-blks-res 1
no access-control-class-ramping
access-control-class-ramping-step-interval dynamic
access-control-class-ramping-step-size 1
early-classmark-sending forbidden
early-classmark-sending-3g allowed
ip.access unit_id 1801 0
oml ip.access stream_id 255 line 0
neighbor-list mode manual
codec-support fr hr efr amr
amr tch-f modes 1 2 6 7
amr tch-f threshold ms 32 32 32
amr tch-f hysteresis ms 8 8 8
amr tch-f threshold bts 32 32 32
amr tch-f hysteresis bts 8 8 8
amr tch-f start-mode auto
amr tch-h modes 1 2 4 5
amr tch-h threshold ms 32 32 32
amr tch-h hysteresis ms 8 8 8
amr tch-h threshold bts 32 32 32
amr tch-h hysteresis bts 8 8 8
amr tch-h start-mode auto
gprs mode none
force-combined-si
trx 0
rf_locked 0
arfcn 600
nominal power 23
max_power_red 0
rsl e1 tei 0
timeslot 0
phys_chan_config CCCH
hopping enabled 0
timeslot 1
phys_chan_config SDCCH8
hopping enabled 0
timeslot 2
phys_chan_config TCH/F
hopping enabled 0
timeslot 3
phys_chan_config TCH/F
hopping enabled 0
timeslot 4
phys_chan_config TCH/F
hopping enabled 0
timeslot 5
phys_chan_config TCH/F
hopping enabled 0
timeslot 6
phys_chan_config TCH/F
hopping enabled 0
timeslot 7
phys_chan_config TCH/F
hopping enabled 0
msc 0
ip.access rtp-base 4000
no bsc-welcome-text
no bsc-msc-lost-text
no bsc-grace-text
codec-list hr3
type normal
allow-emergency deny
amr-config 12_2k forbidden
amr-config 10_2k forbidden
amr-config 7_95k forbidden
amr-config 7_40k forbidden
amr-config 6_70k forbidden
amr-config 5_90k allowed
amr-config 5_15k forbidden
amr-config 4_75k forbidden
asp-protocol m3ua
lcls-mode disabled
lcls-codec-mismatch forbidden
bsc
mid-call-timeout 0
no missing-msc-text
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nanobts.pcap
Type: application/octet-stream
Size: 30322 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20181126/bc2fca41/attachment.obj>