<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Greetings,</div>
<div> </div>
<div>I've been running an older (12+months) build of OpenBSC for a while now over a USRP N210 with no issues, but have recently upgraded to more 'current' builds and am now unable to connect a MS to the BTS.</div>
<div> </div>
<div>In the output of osmo-nitb with extended debugging turned on, I see the following when a MS tries to connect:</div>
<div> </div>
<div>
<div><0000> chan_alloc.c:342 (bts=0,trx=0,ts=1,pchan=SDCCH8) Allocating lchan=0 as SDCCH<br/>
<0004> abis_rsl.c:1727 (bts=0,trx=0,ts=1,ss=0) Activating ARFCN(520) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x06 ta=1<br/>
<0004> abis_rsl.c:536 (bts=0,trx=0,ts=1,pchan=SDCCH8) Tx RSL Channel Activate with act_type=INITIAL<br/>
<0004> abis_rsl.c:1127 (bts=0,trx=0,ts=1,ss=0) state NONE -> ACTIVATION REQUESTED<br/>
<0004> abis_rsl.c:1456 (bts=0,trx=0,ts=1,ss=0) CHANNEL ACTIVATE ACK<br/>
<0004> abis_rsl.c:1127 (bts=0,trx=0,ts=1,ss=0) state ACTIVATION REQUESTED -> ACTIVE</div>
<div>****<br/>
<0004> abis_rsl.c:806 (bts=0,trx=0,ts=1,ss=0) RF Channel Release CMD due error 1<br/>
<0004> abis_rsl.c:718 (bts=0,trx=0,ts=1,ss=0) DEACTivate SACCH CMD<br/>
<0004> abis_rsl.c:1127 (bts=0,trx=0,ts=1,ss=0) state ACTIVE -> RELEASE DUE ERROR<br/>
<0004> abis_rsl.c:863 (bts=0,trx=0,ts=1,ss=0) RF CHANNEL RELEASE ACK<br/>
<0004> abis_rsl.c:767 (bts=0,trx=0,ts=1,ss=0) is back in operation.<br/>
<0004> abis_rsl.c:1127 (bts=0,trx=0,ts=1,ss=0) state RELEASE DUE ERROR -> NONE</div>
<div> </div>
<div>There's a delay of ~10s at the line marked **** where the BTS seems to wait for a location update request from the MS; which never gets received, hence the BTS times out and releases the channel. Using a phone in diagnostic mode, this message appears to be sent correctly, however the BTS never receives/processes it.</div>
<div> </div>
<div>I've tried using older configuration files (which have worked with older builds), as well as the sample configuration files contained with each of the master branches, but to no differing effect.</div>
<div> </div>
<div>Given the MS can see and attempt to connect to the BTS, I'm assuming the transceiver chain is working correctly... my thoughts are that perhaps I've got some simple configuration set incorrectly somewhere along the way.</div>
<div> </div>
<div>Any assistance would be great thankyou!</div>
<div> </div>
</div>
<div>Thankyou,</div>
<div>Bruce</div>
<div> </div>
<div>------------------</div>
<div>Details of current install (including last updated dates of master branches):</div>
<div>Ubuntu 16.04 LTS</div>
<div>libosmocore (master) - 2016-08-30</div>
<div>libosmo-abis (master) - 2016-09-05</div>
<div>libosmo-netif (master) - 2016-07-07</div>
<div>openggsn (master) - 2016-06-05</div>
<div>libosmo-sccp (master) - 2016-07-07</div>
<div>openbsc (master) - 2016-09-05</div>
<div>osmo-bts (master) - 2016-09-06</div>
<div>osmo-pcu (master) - 2016-09-06</div>
<div>osmo-trx (master) - 2016-08-11</div>
<div>uhd_003.009.002-0</div></div></body></html>