On Fri, Jun 18, 2010 at 07:40:10AM +0200, Harald Welte wrote:
I've tried today. Everything seems to work fine
from the OpenBSC side,
i.e. OML and RSL are initialized. On the Air interface howerver, I can
only see the carrier (RxLev) on the ARFCN go high, but the phones never
get further than decoding the BSIC. They don't list the network in the
network selection, and they never consider selecting this cell if it is
part of a bigger network.
I thought of some problem in the SYstem Information, but after checking them
manually in wireshark (from the bsc_hack generated pcap file), there seems
no obvious mistake.
So I'm suspecting some kind of regression in current OpenBSC. Thus my
question for feedback: Which version did you last use successfully with
the BS-11?
I've now looked at this with OsmocomBB, and what I get when using layer23 on
the ARFCN is:
Starting FCCH Recognition
FB0 (9:4): TOA= 4224, Power= -47dBm, Angle= -367Hz
FB1 (19:8): TOA= 9183, Power= -47dBm, Angle= -47Hz
=>FB @ FNR 18 fn_offset=18 qbits=1548
Synchronize_TDMA
LOST!SB1 (42:1): TOA= 29, Power= -47dBm, Angle= 65Hz
=> SB 0x019122fd: BSIC=63 fn=770488(581/ 4/31) qbits=24
and from that on:
<000b> l1ctl.c:100 SCH: SNR: 1 TDMA: (0581/04/31) bsic: 63
<000b> l1ctl.c:158 BCCH (0581/00/02) 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b
<000b> l1ctl.c:162 Dropping frame with 38 bit errors
<000b> l1ctl.c:158 PCH/AGCH (0581/04/06) 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b 2b
<000b> l1ctl.c:162 Dropping frame with 34 bit errors
<000b> l1ctl.c:158 PCH/AGCH (0581/10/12) 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b 2b
<000b> l1ctl.c:162 Dropping frame with 43 bit errors
<000b> l1ctl.c:158 PCH/AGCH (0581/14/16) 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b 2b
<000b> l1ctl.c:162 Dropping frame with 45 bit errors
<000b> l1ctl.c:158 BCCH (0581/25/02) 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b
<000b> l1ctl.c:162 Dropping frame with 41 bit errors
<000b> l1ctl.c:158 PCH/AGCH (0581/03/06) 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b 2b 2b 2b 2b 2b 2b 2b
<000b> l1ctl.c:162 Dropping frame with 51 bit errors
<000b> l1ctl.c:158 PCH/AGCH (0581/09/12) 15 06 21 00 01 02 2b 2b 2b 2b 2b 2b 2b 2b
b9 37 2b 2b 2b 2b 2b 2b 2b
All the messages have a large number of biterrors, whether they're sent on bcch
or not. The BCCH frames also seem to be set to anything to the specified SI /
BCCH PAYLOAD
Any ideas?
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)