RE: some issues configuring openbsc

Steve, I would strongly suggest you look at your configuration file and http://openbsc.osmocom.org/trac/wiki/osmo-nitb_VTY. There are a few parameters you need to set. It appears from the output you provided that there is a mismatch between the band setting in the configuration file and what the BTS actually supports. In addition to the band setting, I would adjust the max_power_red setting for the TRX. For bench testing this allows you to decrease the TX power and coverage of the BTS so you do not attract unwanted handsets, or worse. Regards, Caleb -----Original Message----- From: openbsc-bounces(a)lists.osmocom.org [mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Stephen Siadak Sent: Tuesday, September 13, 2011 0643 To: openbsc(a)lists.osmocom.org Subject: some issues configuring openbsc While I think I am pretty close to getting my ip.access nanoBTS to communicate with my laptop running osmo-nitb I seem to be running into a problem. I am running openbsc-0.9.13 and using libosmocore-0.1.30 When I start osmo-nitb I see this error: ./osmo-nitb -T -c ./openbsc.cfg DB: Database initialized. DB: Database prepared. Sat Sep 10 17:39:42 2011 <0007> sms_queue.c:223 Attempting to send 20 SMS Sat Sep 10 17:39:45 2011 <000d> input/ipaccess.c:650 accept()ed new OML link from 2.2.2.1 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 8a c4 0b Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 00 00 c0 a8 ea 01 00 00 00 00 00 00 00 00 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 d4 07 c0 a8 ea 01 38 a4 45 00 04 59 40 00 Sat Sep 10 17:39:45 2011 <0005> bsc_init.c:50 Failed to set BTS attributes. That is fatal. Was the bts type and frequency properly specified? I am using one of the stock nitb configuration files with no modifications. openbsc.git/openbsc/doc/examples/osmo-nitb/nanobts/openbsc.cfg My setup is a little odd. I did not do the original configuration for the nanoBTS. I was hoping to just get stuff working with the current configuration before I changed anything. The nanoBTS comes up with an IP of 2.2.2.1 and expects a gateway of 2.2.2.2. So I simply configured the ip eth0 on my laptop to 2.2.2.2. Then annoyingly the nanoBTS starts looking for 3.3.3.3. Now I start getting a little hacky to try and move stuff along: ip addr add 3.3.3.3/24 dev eth0 ip route add 3.3.3.3/32 via 2.2.2.2 I am able to use ipaccess-find: ./ipaccess-find eth0 # finally shows # MAC Address='00:02:95:00:51:83' IP Address='2.2.2.1' Unit ID='1801/0/0' # Location 1='' Location 2='BTS_NBT131G' Equipment Version='165b029_58' # Software Version='168a302_v142b13d0' Unit Name='nbts-00-02-95-00-51-83' # Serial Number='00106317' I am also able to use ipaccess-config: ./ipaccess-config -u 1801/0/0 -o 2.2.2.2 -r 2.2.2.1 # Trying to connect to ip.access BTS ... # <0005> abis_nm.c:537 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) # <0005> abis_nm.c:537 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled # AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # OML link established using TRX 0 # setting Unit ID to '1801/0/0' # setting primary OML link IP to '2.2.2.2' # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=GPRS-NSVC(f2) INST=(00,01,ff) STATE CHG: # OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked # <0005> abis_nm.c:537 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) # IPACCESS(0xf0): SET NVATTR ACK # Set the NV Attributes. # The BTS has acked the restart. Exiting. At this point I try to start osmo-nitb and receive the error I mentioned earlier: ./osmo-nitb -T -c ./openbsc.cfg DB: Database initialized. DB: Database prepared. Sat Sep 10 17:39:42 2011 <0007> sms_queue.c:223 Attempting to send 20 SMS Sat Sep 10 17:39:45 2011 <000d> input/ipaccess.c:650 accept()ed new OML link from 2.2.2.1 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 8a c4 0b Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 00 00 c0 a8 ea 01 00 00 00 00 00 00 00 00 Sat Sep 10 17:39:45 2011 <0004> e1_input.c:238 rsl_sendmsg: msg->trx->rsl_link == NULL: 81 81 c1 10 02 00 d4 07 c0 a8 ea 01 38 a4 45 00 04 59 40 00 Sat Sep 10 17:39:45 2011 <0005> bsc_init.c:50 Failed to set BTS attributes. That is fatal. Was the bts type and frequency properly specified? I think the bts type is set correct in the configuration file: type nanobts I am not sure what setting actually sets the frequency. I am happy to provide more information and any help is appreciated. Thanks in advance, -Steve