Re: [Openbts-discuss] First installation problems

[Balthasar I. <ba...@in...>]

Back at the office now, and it seems to transmit the cell information
just fine. I can see and decode the OpenBTS signal with the other B200
running airspy/gsmprobe, it reports the correct MCC/MNC/LAC/CID that
I've set via the OpenBTSCLI interface.

With the iPhone I can see and manually select my network. However,
when I select it, the iPhone 5 displays first No Service for 10-20
seconds, then SOS Only, and stays on SOS Only with my network selected
(which would be OK as the IMSI is not yet registered on that network).
Starting the iPhone engineering console never completes (not sure if
that's by design, i.e. you need to be a subscriber to get the network
info, probably).

On the OpenBTS side nothing seems to happen at all. stats shows no
count increase on anything other than the OpenBTSCLI commands. The
power, gain and noise all seem to be in OK ranges. Looking at the
spectrum I selected it is clean before the access point is started
(see spectrum plot here:
https://cloud.inside.net/index.php/s/k4zQRGTcGxzrjsk, ARFCN 1 is at
935.2 MHz, left most peak in the plot. At the bottom of the waterfall
you can see the clean spectrum before I switched it on, there's
nothing else there).

OpenBTS> power
current downlink power -20 dB wrt full scale

OpenBTS> rxgain
current RX gain is 10 dB

OpenBTS> noise
noise RSSI is -79 dB wrt full scale
MS RSSI target is -50 dB wrt full scale
INFO: the current noise level is acceptable.

tmsis displays nothing. About once every 30 odd seconds, this log
entry is made in syslog:
Jan 22 17:34:49 x transceiver: NOTICE 8449:9083 2016-01-22T17:34:49.7
Transceiver.cpp:192:pushRadioVector: dumping STALE burst in TRX->USRP
interface

Not sure if that says anything.

What else can I check?


On 22 January 2016 at 12:41, Balthasar Indermuehle <ba...@in...> wrote:
> Many thanks for your help Tom! I think the patch did the trick.
>
> I can now run the OpenBTSCLI and set up the network, I can see the
> B200 putting out power at the right frequencies (benefits of having
> two I guess!).
>
> On 22 January 2016 at 11:17, Tom Tsou <tom...@et...> wrote:
>> On Thu, Jan 21, 2016 at 4:01 PM, Balthasar Indermuehle <ba...@in...> wrote:
>>> Jan 22 10:56:33 x openbts: EMERG 3594:3603 2016-01-22T10:56:33.5
>>> OpenBTS.cpp:185:startTransceiver: Transceiver quit with status 32512.
>>> Exiting.
>>
>> There is no way to pass device arguments into OpenBTS to pass down to
>> transceiver.
>>
>> I would disable the OpenBTS transceiver start and run the transceiver
>> manually from the command line with the device arguments.
>>
>>   -TT