MS cannot connect; Location Update Request not received by BTS?

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/.

Holger Freyther holger at freyther.de
Tue Sep 27 21:58:33 UTC 2016


> On 27 Sep 2016, at 23:51, Abdulghafar Shabaneh <abdulghafar1412 at gmail.com> wrote:
> 
> Hi 

Hi!


> That's the same that is happening with me since about two weeks, and I was unable to solve it. They told me it might be uhd problem, but I installed different uhds with the same issue. 


same disclaimer that I have only worked with the BS11, nanoBTS and the last years with the sysmoBTS.



> osmo-bitb shows the same error like this:
> <0000> chan_alloc.c:342 (bts=0,trx=0,ts=7,pchan=TCH/F) Allocating lchan=0 as TCH_F
> <0004> abis_rsl.c:1727 (bts=0,trx=0,ts=7,ss=0) Activating ARFCN(60) SS(0) lctype TCH_F r=EMERGENCY ra=0xab ta=3
> <0004> abis_rsl.c:536 (bts=0,trx=0,ts=7,pchan=TCH/F) Tx RSL Channel Activate with act_type=INITIAL
> <0004> abis_rsl.c:1127 (bts=0,trx=0,ts=7,ss=0) state NONE -> ACTIVATION REQUESTED
> <0004> abis_rsl.c:1456 (bts=0,trx=0,ts=7,ss=0) CHANNEL ACTIVATE ACK
> <0004> abis_rsl.c:1127 (bts=0,trx=0,ts=7,ss=0) state ACTIVATION REQUESTED -> ACTIVE
> <0004> abis_rsl.c:806 (bts=0,trx=0,ts=7,ss=0) RF Channel Release CMD due error 1
> <0004> abis_rsl.c:718 (bts=0,trx=0,ts=7,ss=0) DEACTivate SACCH CMD
> <0004> abis_rsl.c:1127 (bts=0,trx=0,ts=7,ss=0) state ACTIVE -> RELEASE DUE ERROR
> <0004> abis_rsl.c:863 (bts=0,trx=0,ts=7,ss=0) RF CHANNEL RELEASE ACK
> <0004> abis_rsl.c:767 (bts=0,trx=0,ts=7,ss=0) is back in operation.
> 
> 
> it once showed this error:
> <0022> control_if.c:286 Failed to parse ip access message: -5
> <0000> chan_alloc.c:355 Failed to allocate SDCCH channel
> <0004> abis_rsl.c:1678 BTS 0 CHAN RQD: no resources for SDCCH 0x10


I think this is not the first issue but a consequence of many channels ending up in error.


> 
> I use USRP2 , I used recently a reference clock of 10 MHz but didn't solve the issue, but it is good to know that N210 is with the same error.
> 
> Another thing that my network rarely shows on the MS, but the osmo-nitb still shows the output every minute or more or when I do a mobile network search.


Same hint as to the original poster. Try an older version of osmo-bts and tell us preferable the SHA1 of it. Then we will ask you to git bisect between working and non-working version.


holger


More information about the OpenBSC mailing list