Hi all,
I am facing an error while trying to make a call from vty
here is my mobile.cfg output
! ! OsmocomBB () configuration saved from vty !! ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default gps enable ! no hide-default ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap sim reader network-selection-mode auto imei 415239521974659 0 imei-random 15 no emergency-imsi no sms-service-center no call-waiting no auto-answer no force-rekey clip no clir tx-power auto no simulated-delay no stick location-updating neighbour-measurement codec full-speed prefer codec half-speed no abbrev support sms a5/1 a5/2 p-gsm e-gsm r-gsm no gsm-850 dcs no pcs class-900 4 class-850 4 class-dcs 1 class-pcs 1 channel-capability sdcch+tchf+tchh full-speech-v1 full-speech-v2 half-speech-v1 min-rxlev -100 dsc-max 90 no skip-max-per-band exit test-sim imsi 001010000000000 ki xor 00 00 00 00 00 00 00 00 00 00 00 00 no barred-access no rplmn hplmn-search foreign-country exit no shutdown exit !
the debbuging output is
<0009> mnccms.c:570 Make call to 123456789 <0009> mnccms.c:150 support TCH/H also <0009> mnccms.c:174 support full rate v2 <0009> mnccms.c:178 support full rate v1 <0009> mnccms.c:187 support half rate v1 <0006> transaction.c:76 ms 1 allocates transaction (proto 3 trans_id 255 callref 1 mem 0xf408d0) <0006> gsm48_cc.c:243 new state NULL -> MM_CONNECTION_PEND <0006> gsm48_cc.c:507 Sending MMCC_EST_REQ <0005> gsm48_mm.c:3783 (ms 1) Received 'MMCC_EST_REQ' event in state MM idle <0005> gsm48_mm.c:3786 -> substate PLMN search <0005> gsm48_mm.c:3788 -> callref 1, transaction_id 255 <0005> gsm48_mm.c:3051 Init MM Connection, not in normal state. <0006> gsm48_cc.c:2161 (ms 1) Received 'MMCC_REL_IND' in CC state MM_CONNECTION_PEND <0006> gsm48_cc.c:196 (ms 1 ti ff) Sending 'MNCC_REL_IND' to MNCC. <0006> gsm48_cc.c:243 new state MM_CONNECTION_PEND -> NULL <0006> transaction.c:104 ms 1 frees transaction (mem 0xf408d0) <0009> mnccms.c:372 Call has been released (cause 21) <0009> mnccms.c:71 (call 1) Call removed.
and also my ms output from vty
OsmocomBB> enable OsmocomBB# show ms MS '1' is up, service is limited IMEI: 418873812577882 IMEISV: 4188738125778820 IMEI generation: random (15 trailing digits) automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search
OsmocomBB# show subsccriber 1 % Unknown command. OsmocomBB# show sub OsmocomBB# show subscriber 1 OsmocomBB# show subscriber 1 Mobile Subscriber of MS '1': IMSI: 405025012498239 ICCID: 89910255110124982391 Status: U1_UPDATED IMSI detached TMSI 0x1d315a07 LAI: MCC 405 MNC 025 LAC 0x42d8 (405, TATA DOCOMO) Key: sequence 2 a6 78 30 12 22 45 0b 03 Access barred cells: no Access classes:
Kindly assist me with some suggestions.
Regards, Cris
cris crazy wrote:
OsmocomBB# show ms MS '1' is up, service is limited IMEI: 418873812577882 IMEISV: 4188738125778820 IMEI generation: random (15 trailing digits) automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search
hi,
it seems that you did not yet started your phone, since the network search has not started. service remains limited until you are attached to the network, but you don't. did you start layer 1? try bcch_scan and ccch_scan app to check if your phone works and you can sync to a cell.
regards,
andreas
p.s. please don't make private infos like your IMSI public. they could be abused.
Hi Andreas,
Thanks for your suggestions ...
Below is the output after loading the layer1 to mobile
OsmocomBB Layer 1 (revision osmocon_v0.0.0-1747-geeafd9f-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: ee180728b042174d ====================================================================== 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 Installing DSP extensions patch Setting some dsp_api.ndb values Setting API NDB parameters Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 7089!
and i am able to see the layer 1 osmocom-bb in the mobile.
As per your suggestion i checked with bcch_scan
here is the output snippet from the console of ./bcch_scan
arfcn=853 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=870 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=876 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=877 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=881 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=882 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=885 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=-1 rxlev=0
It goes on like this and finally ends with negative value.
and in osmocon console the output is like
Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=849, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=853, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=870, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=876, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=877, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=881, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=882, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=885, flags=0x7
by this i assume that my mobile is not able to sync with the network ..please correct me if i was wrong...
and also kindly assist me for any kind of modifications.
thanks in advance
Regards, Cris
On Mon, Feb 18, 2013 at 2:57 PM, jolly andreas@eversberg.eu wrote:
cris crazy wrote:
OsmocomBB# show ms MS '1' is up, service is limited IMEI: 418873812577882 IMEISV: 4188738125778820 IMEI generation: random (15 trailing digits) automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search
hi,
it seems that you did not yet started your phone, since the network search has not started. service remains limited until you are attached to the network, but you don't. did you start layer 1? try bcch_scan and ccch_scan app to check if your phone works and you can sync to a cell.
regards,
andreas
p.s. please don't make private infos like your IMSI public. they could be abused.
Hi,
I'm kindly requesting some suggests for the below issue as i totally don't know how to resolve/rectify it.
Regards, Cris
On Tue, Feb 19, 2013 at 2:49 AM, cris crazy critsit1234@gmail.com wrote:
Hi Andreas,
Thanks for your suggestions ...
Below is the output after loading the layer1 to mobile
OsmocomBB Layer 1 (revision osmocon_v0.0.0-1747-geeafd9f-modified)
Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: ee180728b042174d ====================================================================== 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 Installing DSP extensions patch Setting some dsp_api.ndb values Setting API NDB parameters Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 7089!
and i am able to see the layer 1 osmocom-bb in the mobile.
As per your suggestion i checked with bcch_scan
here is the output snippet from the console of ./bcch_scan
arfcn=853 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=870 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=876 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=877 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=881 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=882 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=885 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=-1 rxlev=0
It goes on like this and finally ends with negative value.
and in osmocon console the output is like
Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=849, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=853, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=870, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=876, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=877, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=881, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=882, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=885, flags=0x7
by this i assume that my mobile is not able to sync with the network ..please correct me if i was wrong...
and also kindly assist me for any kind of modifications.
thanks in advance
Regards, Cris
On Mon, Feb 18, 2013 at 2:57 PM, jolly andreas@eversberg.eu wrote:
cris crazy wrote:
OsmocomBB# show ms MS '1' is up, service is limited IMEI: 418873812577882 IMEISV: 4188738125778820 IMEI generation: random (15 trailing digits) automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search
hi,
it seems that you did not yet started your phone, since the network search has not started. service remains limited until you are attached to the network, but you don't. did you start layer 1? try bcch_scan and ccch_scan app to check if your phone works and you can sync to a cell.
regards,
andreas
p.s. please don't make private infos like your IMSI public. they could be abused.
Hi Chris,
I have had similar problems. Some suggestions you can try out.
1. Put a real IMEI code. Some networks check for "fake" IMEI codes which were common in some mobiles and refuse connections to those mobiles. Your case looks like one. Once it works, you can try to randomise the last few digits only. Quite possibly this will solve your problem.
2. Put the real IMSI code of your SIM.
3. Do a cold start and try again. Sometimes the connection is unstable. I have no idea why.
4. Enable "stick" option.
5. Try manual network selection.
6. Put correct SMS service centre number.
Let the list know what works. :-)
Good luck!
B
On Wed, Feb 20, 2013 at 10:21 PM, cris crazy critsit1234@gmail.com wrote:
Hi,
I'm kindly requesting some suggests for the below issue as i totally don't know how to resolve/rectify it.
Regards, Cris
On Tue, Feb 19, 2013 at 2:49 AM, cris crazy critsit1234@gmail.com wrote:
Hi Andreas,
Thanks for your suggestions ...
Below is the output after loading the layer1 to mobile
OsmocomBB Layer 1 (revision osmocon_v0.0.0-1747-geeafd9f-modified)
Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: ee180728b042174d ====================================================================== 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 Installing DSP extensions patch Setting some dsp_api.ndb values Setting API NDB parameters Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 7089!
and i am able to see the layer 1 osmocom-bb in the mobile.
As per your suggestion i checked with bcch_scan
here is the output snippet from the console of ./bcch_scan
arfcn=853 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=870 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=876 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=877 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=881 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=882 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=885 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=-1 rxlev=0
It goes on like this and finally ends with negative value.
and in osmocon console the output is like
Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=849, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=853, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=870, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=876, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=877, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=881, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=882, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=885, flags=0x7
by this i assume that my mobile is not able to sync with the network ..please correct me if i was wrong...
and also kindly assist me for any kind of modifications.
thanks in advance
Regards, Cris
On Mon, Feb 18, 2013 at 2:57 PM, jolly andreas@eversberg.eu wrote:
cris crazy wrote:
OsmocomBB# show ms MS '1' is up, service is limited IMEI: 418873812577882 IMEISV: 4188738125778820 IMEI generation: random (15 trailing digits) automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search
hi,
it seems that you did not yet started your phone, since the network search has not started. service remains limited until you are attached to the network, but you don't. did you start layer 1? try bcch_scan and ccch_scan app to check if your phone works and you can sync to a cell.
regards,
andreas
p.s. please don't make private infos like your IMSI public. they could be abused.
baseband-devel@lists.osmocom.org
-
Bhaskar11 -
cris crazy -
jolly