Location update problems on Motorola C118

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Location update problems on Motorola C118

Maciej Grela
Hi,

I'm trying to run the latest osmocom-bb git on a Motorola C118 phone.
After a minor problem with the build (as you may've noticed in the
patch I've sent). I got to the point of successfuly running layer1 on
the phone and the mobile app on the PC (I have also enabled TX). The
process seems to be stuck on trying to perform a location update. The
status of the ms is always either:

show ms
MS '1' is up, MM connection active
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A1 trying RPLMN
                                     MCC=104 MNC=002 (104, 002)
  cell selection state: connected mode 1
                        ARFCN=19 MCC=104 MNC=002 LAC=0xb00f CELLID=0x4fd9
                        (104, 002)
  radio ressource layer state: connection pending
  mobility management layer state: wait for RR connection (location updating)

OsmocomBB>

or

show ms
MS '1' is up, service is limited (pending)
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A1 trying RPLMN
                                     MCC=104 MNC=002 (104, 002)
  cell selection state: C3 camped normally
                        ARFCN=19 MCC=104 MNC=002 LAC=0xb00f CELLID=0x4fd9
                        (104, 002)
  radio ressource layer state: idle
  mobility management layer state: MM idle, attempting to update

OsmocomBB>

I think, that because of this I can't make any calls or send sms (all
the requests are being rejected):

OsmocomBB# call 1 <X>
call 1 <X>
OsmocomBB#
% (MS 1)
% Call has been rejected

The log information from mobile when it's trying to do a location
update is show below:

<000b> gsm48_rr.c:2174 PAGING REQUEST 1
<000b> gsm48_rr.c:2141  IMSI 260021964220249 (not for us)
<000b> gsm48_rr.c:2132  TMSI fd82a501 (not for us)
<000e> gsm48_mm.c:344 Location update retry
<0005> gsm48_mm.c:345 timer T3211 (loc. upd. retry delay) has fired
<0005> gsm48_mm.c:4311 (ms 1) Received 'MM_EVENT_TIMEOUT_T3211' event
in state MM IDLE, attempting to update
<000e> gsm48_mm.c:2199 Perform location update (MCC 104, MNC 002 LAC 0xb00f)
<0005> gsm48_mm.c:2333 LOCATION UPDATING REQUEST
<0005> gsm48_mm.c:2355  using LAI (mcc 104 mnc 002 lac 0xb00f)
<0005> gsm48_mm.c:2363  using TMSI 0x28a3d62e
<0005> gsm48_mm.c:914 new state MM IDLE, attempting to update -> wait
for RR connection (location updating)
<0001> gsm48_rr.c:5428 (ms 1) Message 'RR_EST_REQ' received in state
idle (sapi 0)
<000e> gsm48_rr.c:1318 Establish radio link due to mobility management request
<0003> gsm322.c:4037 (ms 1) Event 'EVENT_LEAVE_IDLE' for Cell
selection in state 'C3 camped normally'
<0003> gsm322.c:823 new state 'C3 camped normally' -> 'connected mode 1'
<0003> gsm322.c:3653 Going to camping (normal) ARFCN 19.
<0003> gsm322.c:463 Sync to ARFCN=19 rxlev=-74 (Sysinfo, ccch mode NON-COMB)
<0001> gsm48_rr.c:366 new state idle -> connection pending
<0001> gsm48_rr.c:1465 CHANNEL REQUEST: 00 (Location Update with NECI)
<0003> gsm322.c:2938 Channel synched. (ARFCN=19, snr=16, BSIC=17)
<0001> gsm322.c:2959 using DSC of 90
<0003> gsm48_rr.c:4816 Channel provides data.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 5)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 0 ra 0x0e)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 4)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x07)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462  (ta 2/1107m ra 0x75 chan_nr 0x0a MAIO 0 HSN 38
TS 2 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462  (ta 2/1107m ra 0x75 chan_nr 0x0a MAIO 0 HSN 38
TS 2 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber=  0 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 3)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x0f)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 2)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x01)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 1/553m ra 0x18 chan_nr 0x59 ARFCN 19 TS 1
SS 3 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 1/553m ra 0x18 chan_nr 0x59 ARFCN 19 TS 1
SS 3 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 1)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x0a)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber=  1 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 0)
<0001> gsm48_rr.c:1605 Done with sending RANDOM ACCESS bursts
<0001> gsm48_rr.c:836 starting T3126 with 5.000 seconds
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber=  0 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 2/1107m ra 0x0a chan_nr 0x41 ARFCN 19 TS 1
SS 0 TSC 1)
<0001> gsm48_rr.c:2393 request 0a matches but not frame number
(IMM.ASS fn=22,6,30 != RACH fn=22,5,25)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 2/1107m ra 0x05 chan_nr 0x49 ARFCN 19 TS 1
SS 1 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 2/1107m ra 0x05 chan_nr 0x49 ARFCN 19 TS 1
SS 1 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-77 snr= 0 ber=  6 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 2/1107m ra 0x00 chan_nr 0x61 ARFCN 19 TS 1
SS 4 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473  (ta 2/1107m ra 0x00 chan_nr 0x61 ARFCN 19 TS 1
SS 4 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462  (ta 2/1107m ra 0x7d chan_nr 0x0b MAIO 0 HSN 38
TS 3 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462  (ta 2/1107m ra 0x7d chan_nr 0x0b MAIO 0 HSN 38
TS 3 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber=  0 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber=  3 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462  (ta 2/1107m ra 0x77 chan_nr 0x09 MAIO 0 HSN 38
TS 1 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462  (ta 2/1107m ra 0x77 chan_nr 0x09 MAIO 0 HSN 38
TS 1 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber=  6 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:765 timer T3126 has fired
<000e> gsm48_rr.c:770 Requesting channel failed
<0001> gsm48_rr.c:366 new state connection pending -> idle
<0003> gsm322.c:4037 (ms 1) Event 'EVENT_RET_IDLE' for Cell selection
in state 'connected mode 1'
<0003> gsm322.c:3565 Selecting ARFCN 19. after LOC.UPD.
<0003> gsm322.c:463 Sync to ARFCN=19 rxlev=-74 (Sysinfo, ccch mode NON-COMB)
<0003> gsm322.c:823 new state 'connected mode 1' -> 'C3 camped normally'
<0005> gsm48_mm.c:3902 (ms 1) Received 'RR_REL_IND' from RR in state
wait for RR connection (location updating) (sapi 0)
<0005> gsm48_mm.c:2732 RR link released after loc. upd.
<000e> gsm48_mm.c:2676 Location update failed
<000e> gsm48_mm.c:2686 Try location update later
<0005> gsm48_mm.c:2688 Loc. upd. failed, retry #0
<0005> gsm48_mm.c:413 starting T3211 (loc. upd. retry delay) with 15.0 seconds
<0005> gsm48_mm.c:1143 We are camping normally as returning to MM IDLE
<0005> gsm48_mm.c:1159 Loc. upd. allowed.
<0005> gsm48_mm.c:919 new state wait for RR connection (location
updating) -> MM IDLE, location updating needed
<0005> gsm48_mm.c:909 new MM IDLE state location updating needed ->
attempting to update
<0005> gsm48_mm.c:2215 Loc. upd. already pending.
<0005> gsm48_mm.c:4311 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event
in state MM IDLE, attempting to update
<0005> gsm48_mm.c:2215 Loc. upd. already pending.
<0003> gsm322.c:2938 Channel synched. (ARFCN=19, snr=16, BSIC=17)
<0001> gsm322.c:2959 using DSC of 90

Can you provide me any hints on how to debug this ? Why is the
location update failing constantly ?
Thanks in advance for your help.

Best regards,
Maciej Grela

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118

Sylvain Munaut
Hi,

> I'm trying to run the latest osmocom-bb git on a Motorola C118 phone.
> After a minor problem with the build (as you may've noticed in the
> patch I've sent). I got to the point of successfuly running layer1 on
> the phone and the mobile app on the PC (I have also enabled TX).

1) Where are you in the world ?
2) Are you _sure_ you enabled TX ? Did you check the layer 1 log
doesn't say TX is disabled ?

Cheers,

    Sylvain

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118

Maciej Grela
2012/9/16 Sylvain Munaut <[hidden email]>:
> Hi,
>
>> I'm trying to run the latest osmocom-bb git on a Motorola C118 phone.
>> After a minor problem with the build (as you may've noticed in the
>> patch I've sent). I got to the point of successfuly running layer1 on
>> the phone and the mobile app on the PC (I have also enabled TX).
>
> 1) Where are you in the world ?

Poland.

> 2) Are you _sure_ you enabled TX ? Did you check the layer 1 log
> doesn't say TX is disabled ?

Yes, I'm sure. Here is the beginning of layer1 booting:


>Received DOWNLOAD ACK from phone, your code is running now!
battery_compal_e88_init: starting up


OsmocomBB Layer 1 (revision osmocon_v0.0.0-1658-g6ce46e7-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: 058d392b9c039bfc
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 7130!

Best regards,
Maciej Grela

> Cheers,
>
>     Sylvain
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118

Maciej Grela
In reply to this post by Sylvain Munaut
2012/9/16 Sylvain Munaut <[hidden email]>:

> Hi,
>
>> I'm trying to run the latest osmocom-bb git on a Motorola C118 phone.
>> After a minor problem with the build (as you may've noticed in the
>> patch I've sent). I got to the point of successfuly running layer1 on
>> the phone and the mobile app on the PC (I have also enabled TX).
>
> 1) Where are you in the world ?
> 2) Are you _sure_ you enabled TX ? Did you check the layer 1 log
> doesn't say TX is disabled ?

Also, fyi:

1. The phone works OK on the stock firmware.
2. I was able to successfuly make calls and send sms with osmocombb on
this particular phone during haxogreen.lu in Luxemburg in August 2012.
I don't remember which network I used then.

Br,
Maciej Grela

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118 on real network (network location::india)

prakash
hi,
             i am using osmocombb in motorola c118.
                 when i load firmware (layer1) on phone and start the
application MOBILE,
              it gets all parameters from phone,
                     gets plmn
                     finds cell
                     but location update is rejected with cause ILLEGAL ME.
                     
                    i am trying in a network in india.
                    i dont know the real problem behind this. plz help me


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118 on real network (network location::india)

Sylvain Munaut
On Thu, Jan 31, 2013 at 11:42 AM, prakash <[hidden email]> wrote:
> hi,
>              i am using osmocombb in motorola c118.
>                  when i load firmware (layer1) on phone and start the
> application MOBILE,
>               it gets all parameters from phone,
>                      gets plmn
>                      finds cell
>                      but location update is rejected with cause ILLEGAL ME.

Try setting the IMEI to something valid.

Cheers,

    Sylvain

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118 on real network (network location::india)

Kurtis Heimerl
Should people be attaching Osmocom to real networks?


On Thu, Jan 31, 2013 at 8:40 PM, Sylvain Munaut <[hidden email]> wrote:
On Thu, Jan 31, 2013 at 11:42 AM, prakash <[hidden email]> wrote:
> hi,
>              i am using osmocombb in motorola c118.
>                  when i load firmware (layer1) on phone and start the
> application MOBILE,
>               it gets all parameters from phone,
>                      gets plmn
>                      finds cell
>                      but location update is rejected with cause ILLEGAL ME.

Try setting the IMEI to something valid.

Cheers,

    Sylvain


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118 on real network (network location::india)

Sylvain Munaut
> Should people be attaching Osmocom to real networks?

Well, it's of course their responsibility, but both the stack and RF
control are designed to be compliant to specs. Doesn't mean there is
no bugs of course, but I mean, there is bug in commercial stacks as
well.

Cheers,

    Sylvain

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118 on real network (network location::india)

Harald Welte-3
In reply to this post by Kurtis Heimerl
Hi Kurtis,

On Fri, Feb 01, 2013 at 12:44:42AM +0900, Kurtis Heimerl wrote:
> Should people be attaching Osmocom to real networks?

If they feel that their local jurisdiction permits the use of modified
software on certified/approved phone hardware: It is their choice.

Regards,
        Harald
--
- Harald Welte <[hidden email]>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Location update problems on Motorola C118

asghar.mustafa
This post has NOT been accepted by the mailing list yet.
In reply to this post by Maciej Grela
Hello All:
I am facing a similar problem while in the procedure of making the call. I am currently located in Pakistan and using Pakistan networks (Ufone/Warid) for this purpose.
Once i have booted layer 1 (with the same output as given by Maciej) and then run the mobile application, it says "Paging ignored, we are not camping" and the location update also fails. I have enabled the Tx command on line 132 of the main file in target/firmware/makefile. However i didn't understand that someone in this thread mentioned about layer 1 log, how to check it? and what to check there?
Now once i telnet localhost 4247 it starts an infinite loop as
MS#1
registering with the network
MS#1
registering with the network
MS#1
registering with the network
MS#1
Searching network
MS#1
registering with the network
etc..... and even if i put 'show ms' command it gives exactly the same response as mentioned in this thread and if i call 1 <X> it says call released but doesn't proceed further.
An urgent help would highly be appreciated,
REGARDS,
Loading...