Hi,

 

I have even tried authorizing imsi via sql. I could able to authorize by following https://osmocom.org/projects/osmonitb/wiki/OsmoNITB   and it lists the extension number, exactly what I have assigned.  

But the error still persists.

 

 

Issues listed below is similar to what I’m facing but is there any solution for this?

http://lists.osmocom.org/pipermail/openbsc/2012-February/004695.html

https://osmocom.org/issues/1648#note-19

 

 

Thanks,

Sudhanthiradasan R

 

From: Sudhanthiradasan R
Sent: Monday, October 16, 2017 6:28 PM
To: openbsc@lists.osmocom.org
Subject: Location Update Error

 

Hello,

 

I’m getting below error, when I ran “/usr/local/osmo_built/bin/osmo-nitb -c ./../osmo_cfg/osmo-nitb_2trx.cfg -l ./../osmo_cfg/hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM”

 

<0000> abis_rsl.c:2013 (bts=0,trx=1,ts=0,ss=0) SAPI=0 ESTABLISH INDICATION

<0000> gsm_04_08.c:3960 Dispatching 04.08 message, pdisc=5

<0002> gsm_04_08.c:1389 LOCATION UPDATING REQUEST: MI(IMSI)=901550000001016 type=NORMAL

<0001> gsm_04_08.c:149 (bts 0 trx 1 ts 0 pd 05) Sending 0x18 to MS.

<0000> abis_rsl.c:2013 (bts=0,trx=1,ts=0,ss=0) SAPI=0 ERROR INDICATION

<0000> abis_rsl.c:1954 (bts=0,trx=1,ts=0,ss=0) ERROR INDICATION cause=SABM frame with information not allowed in this state in state=ACTIVE

<0002> gsm_04_08.c:596 Location Updating Request procedure timedout.

<0002> gsm_04_08.c:474 Subscriber 901550000001016:

<0001> gsm_04_08.c:149 (bts 0 trx 1 ts 0 pd 05) Sending 0x04 to MS.

 

 

Anyone had the same issue earlier? Is there any solution for this error?

 

 

Thanks,

Sudhanthiradasan R



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------