[Openbts-discuss] asterisk error: no matching peer found

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

I am working on openbts-2.5.4Lacassine and my phone is getting openbts network 
but asterisk shows some error. Here is the log of asterisk error:

root@ubuntu:~# asterisk -r
Asterisk 1.6.2.7-1ubuntu1.1, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer <mar...@di...>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for 
details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.6.2.7-1ubuntu1.1 currently running on ubuntu (pid = 
1031)
[Apr 26 13:41:47] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102953411 <sip:IMSI410035102953411@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:41:49] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001291195 <sip:IMSI410035001291195@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:41:49] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035103214510 <sip:IMSI410035103214510@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:23] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035002595443 <sip:IMSI410035002595443@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:25] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035000092359 <sip:IMSI410035000092359@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:27] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035106734134 <sip:IMSI410035106734134@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:30] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035100698529 <sip:IMSI410035100698529@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:34] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035105603822 <sip:IMSI410035105603822@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:47] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001713559 <sip:IMSI410035001713559@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:42:51] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035103246921 <sip:IMSI410035103246921@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:43:10] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035103259581 <sip:IMSI410035103259581@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:43:38] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410036105451192 <sip:IMSI410036105451192@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:43:49] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001966825 <sip:IMSI410035001966825@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:44:38] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410037104855080 <sip:IMSI410037104855080@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:44:42] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035101877370 <sip:IMSI410035101877370@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:45:19] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035002392052 <sip:IMSI410035002392052@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:45:23] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001262176 <sip:IMSI410035001262176@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:45:33] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035105542194 <sip:IMSI410035105542194@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:45:38] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102259871 <sip:IMSI410035102259871@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:45:58] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035000383843 <sip:IMSI410035000383843@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:46:50] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035106455125 <sip:IMSI410035106455125@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:46:50] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102754357 <sip:IMSI410035102754357@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:47:31] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102548242 <sip:IMSI410035102548242@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:47:51] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035103214510 <sip:IMSI410035103214510@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:47:51] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102953411 <sip:IMSI410035102953411@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:47:52] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001291195 <sip:IMSI410035001291195@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:48:22] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035104126213 <sip:IMSI410035104126213@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:48:29] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035106734134 <sip:IMSI410035106734134@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:48:30] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035000092359 <sip:IMSI410035000092359@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:48:34] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035100698529 <sip:IMSI410035100698529@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:48:36] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035105603822 <sip:IMSI410035105603822@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:48:51] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001713559 <sip:IMSI410035001713559@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:49:06] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035105091970 <sip:IMSI410035105091970@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:49:38] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035100700481 <sip:IMSI410035100700481@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:49:51] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001966825 <sip:IMSI410035001966825@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:50:07] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001262176 <sip:IMSI410035001262176@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:50:11] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410036105451192 <sip:IMSI410036105451192@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:50:57] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035103051230 <sip:IMSI410035103051230@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:51:32] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410036106963022 <sip:IMSI410036106963022@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:51:33] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410039101199240 <sip:IMSI410039101199240@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:51:34] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035002392052 <sip:IMSI410035002392052@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:51:35] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035105542194 <sip:IMSI410035105542194@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:51:40] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035101877370 <sip:IMSI410035101877370@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:51:40] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102259871 <sip:IMSI410035102259871@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:52:00] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035000383843 <sip:IMSI410035000383843@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:52:06] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035001514681 <sip:IMSI410035001514681@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:52:31] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410037104855080 <sip:IMSI410037104855080@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:52:53] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035102754357 <sip:IMSI410035102754357@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:53:00] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035100503663 <sip:IMSI410035100503663@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:53:09] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410037104855080 <sip:IMSI410037104855080@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:53:25] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410036000739107 <sip:IMSI410036000739107@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:54:32] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035000092359 <sip:IMSI410035000092359@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:54:36] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035100698529 <sip:IMSI410035100698529@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found
[Apr 26 13:54:37] NOTICE[1064]: chan_sip.c:21549 handle_request_register: 
Registration from 'IMSI410035105603822 <sip:IMSI410035105603822@127.0.0.1>' 
failed for '127.0.0.1' - No matching peer found

what does it mean? 
help me.
Regards,
Adeel

________________________________
From: "ope...@li..." 
<ope...@li...>
To: ope...@li...
Sent: Mon, April 25, 2011 7:08:59 PM
Subject: Openbts-discuss Digest, Vol 32, Issue 16

Send Openbts-discuss mailing list submissions to
    ope...@li...

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.sourceforge.net/lists/listinfo/openbts-discuss
or, via email, send a message with subject or body 'help' to
    ope...@li...

You can reach the person managing the list at
    ope...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openbts-discuss digest..."

Today's Topics:

   1. re how to register with the openbts?? (gm praveen)
   2. Re: re how to register with the openbts?? (Alexander Chemeris)
   3. Wavetek 4201s - GSM Test Set (Luca Bongiorni)
   4. AT&T starts selling 'cell tower in a suitcase' (Isaac Gerg)
   5. 52Mhz external clock reference required?? (adeel khan)

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

Message: 1
Date: Mon, 25 Apr 2011 07:23:00 +0530 (IST)
From: gm praveen <gm...@ya...>
Subject: [Openbts-discuss] re how to register with the openbts??
To: ope...@li...
Message-ID: <436...@we...>
Content-Type: text/plain; charset="utf-8"

thanks for the reply..
when trying to register with openbts i got the following log
1303692623.8328 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo: 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
Yeah: 1303692623.8328 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo: 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
1303692640.7792 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM 
Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe) 
MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0 
powerCap=3)
Yeah: 1303692640.7792 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM 
Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe) 
MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0 
powerCap=3)
1303692640.7793 INFO 3065236336 
MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating 
Request LAI=(MCC=234 MNC=10 LAC=0xfffe) MobileIdentity=(IMSI=234101493065396) 
classmark=(revision=1 ES-IND=1 A5/1=0 powerCap=3)
Yeah: 1303692640.7793 INFO 3065236336 
MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating 
Request LAI=(MCC=234 MNC=10 LAC=0xfffe) MobileIdentity=(IMSI=234101493065396) 
classmark=(revision=1 ES-IND=1 A5/1=0 powerCap=3)
1303692640.7795 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo: 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
Yeah: 1303692640.7795 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo: 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
1303692657.4904 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM 
Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe) 
MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0 
powerCap=3)
Yeah: 1303692657.4904 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM 
Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe) 
MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0 
powerCap=3)
1303692657.4905 INFO 3065236336 
MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating 
Request LAI=(MCC=234 MNC=10 LAC=0xfffe) MobileIdentity=(IMSI=234101493065396) 
classmark=(revision=1 ES-IND=1 A5/1=0 powerCap=3)
Yeah: 1303692657.4905 INFO 3065236336 
MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating 
Request LAI=(MCC=234 MNC=10 LAC=0xfffe) MobileIdentity=(IMSI=234101493065396) 
classmark=(revision=1 ES-IND=1 A5/1=0 powerCap=3)
1303692657.4908 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo: 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
Yeah: 1303692657.4908 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo: 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
1303692674.2018 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM 
Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe) 
MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0 
powerCap=3)
Yeah: 1303692674.2018 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM 
Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe) 
MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0 
powerCap=3)
1303692674.2019 INFO 3065236336 
MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating 
Request LAI=(MCC=234 MNC=10 LAC=0xfffe) MobileIdentity=(IMSI=234101493065396) 
classmark=(revision=1 ES-IND=1 A5/1=0 powerCap=3)
Yeah: 1303692674.2019 INFO 3065236336 
MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating 
Request LAI=(MCC=234 MNC=10 LAC=0xfffe) MobileIdentity=(IMSI=234101493065396) 
classmark=(revision=1 ES-IND=1 A5/1=0 powerCap=3)

what does the this mean ??
when registering my mobile says unknow error
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 2
Date: Mon, 25 Apr 2011 09:49:45 +0400
From: Alexander Chemeris <ale...@gm...>
Subject: Re: [Openbts-discuss] re how to register with the openbts??
To: gm praveen <gm...@ya...>
Cc: ope...@li...
Message-ID: <BANLkTinp=OeLXQ71DosOR+Uz=sksz=yy...@ma...>
Content-Type: text/plain; charset=UTF-8

Probably you haven't configured Asterisk correctly. I recommend you to
read "OpenBTS for Dummies".

On Mon, Apr 25, 2011 at 05:53, gm praveen <gm...@ya...> wrote:
> thanks for the reply..
> when trying to register with openbts i got the following log
> 1303692623.8328 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo:
> 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
> Yeah: 1303692623.8328 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo:
> 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
> 1303692640.7792 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM
> Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> Yeah: 1303692640.7792 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv
> MM Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> 1303692640.7793 INFO 3065236336
> MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating
> Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> Yeah: 1303692640.7793 INFO 3065236336
> MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating
> Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> 1303692640.7795 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo:
> 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
> Yeah: 1303692640.7795 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo:
> 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
> 1303692657.4904 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM
> Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> Yeah: 1303692657.4904 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv
> MM Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> 1303692657.4905 INFO 3065236336
> MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating
> Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> Yeah: 1303692657.4905 INFO 3065236336
> MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating
> Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> 1303692657.4908 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo:
> 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
> Yeah: 1303692657.4908 INFO 3065236336 CollectMSInfo.cpp:124:logMSInfo:
> 
(IMSI=234101493065396)Lat,Lon,FER,RSSI,timingError,actualMSPower,actualMSTiming
> 1303692674.2018 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv MM
> Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> Yeah: 1303692674.2018 INFO 3065236336 GSML3Message.cpp:162:parseL3: L3 recv
> MM Location Updating Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> 1303692674.2019 INFO 3065236336
> MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating
> Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
> Yeah: 1303692674.2019 INFO 3065236336
> MobilityManagement.cpp:137:LocationUpdatingController: MM Location Updating
> Request LAI=(MCC=234 MNC=10 LAC=0xfffe)
> MobileIdentity=(IMSI=234101493065396) classmark=(revision=1 ES-IND=1 A5/1=0
> powerCap=3)
>
> what does the this mean ??
> when registering my mobile says unknow error
>
>
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can gain
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> Openbts-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>
>

-- 
Regards,
Alexander Chemeris.

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

Message: 3
Date: Mon, 25 Apr 2011 12:02:20 +0200
From: Luca Bongiorni <luc...@st...>
Subject: [Openbts-discuss] Wavetek 4201s - GSM Test Set
To: ope...@li...
Message-ID: <745...@st...>
Content-Type: text/plain; charset=windows-1252

Hi all,

i'm selling my Wavetek 4201s.

Unfortunately some days ago i was upgrading the firmware and the power went 
down.

Now it stucks at initializing process.

http://tinyurl.com/3dnetqu

As you can see was fully working and i used it to make tests with osmocomBB and 
airprobe.

http://tinyurl.com/43exn2s

http://tinyurl.com/3qlvz52

As i guess, is possible to repair the corrupted firmware through serial or an 
internal jtag, unfortunately i have no time to do it and i'm buying another one.

I bought it, 3 months ago, fully calibrated and working. (payed 750 ?).

About the price i thought around 250 euro (because is only a software problem 
and on ebay is still around 1500 ?).

About the shipping? will be signed-for (from 4 to 7 days Worldwide), around 30 
?.

About the payment: Paypal (i'll value other ways, if suggested).

What is included:
- Wavetek 4201s
- Power cable (EU)
- Serial Cable
- Coupler Antenna R&S CMD-z10 (see here: http://tinyurl.com/3fxf4t8 )
- Manual (IT)
- Firmware upgrades by email

If someone is interested, please contact me.

Thank you for attention

Cheers

Luca Bongiorni

P.S: I apologize for the spam, but i thought that here is the right place to 
find people with enough skills, time and few money to repair and use it, instead 
to leave him on the desk and accumulating dust.

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

Message: 4
Date: Mon, 25 Apr 2011 09:04:11 -0400
From: Isaac Gerg <isa...@ge...>
Subject: [Openbts-discuss] AT&T starts selling 'cell tower in a
    suitcase'
To: ope...@li...
Message-ID: <BANLkTi=LQqXNoYfDJE5s=gC6...@ma...>
Content-Type: text/plain; charset="iso-8859-1"

FYI

http://finance.yahoo.com/news/ATampT-starts-selling-cell-apf-3974826065.html?x=0&.v=4

-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 5
Date: Mon, 25 Apr 2011 07:08:49 -0700 (PDT)
From: adeel khan <ade...@ya...>
Subject: [Openbts-discuss] 52Mhz external clock reference required??
To: ope...@li...
Message-ID: <554...@we...>
Content-Type: text/plain; charset="us-ascii"

I am looking for a 52Mhz external clock for my USRP(openbts). Anybody please 
send me link(references) to buy it.
Thanks,
Adeel

________________________________
From: "ope...@li..." 
<ope...@li...>
To: ope...@li...
Sent: Mon, April 25, 2011 12:42:47 AM
Subject: Openbts-discuss Digest, Vol 32, Issue 15

Send Openbts-discuss mailing list submissions to
    ope...@li...

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.sourceforge.net/lists/listinfo/openbts-discuss
or, via email, send a message with subject or body 'help' to
    ope...@li...

You can reach the person managing the list at
    ope...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openbts-discuss digest..."

Today's Topics:

   1. Re: IMSI-Catcher?! Is it legal?! (Royce Brisbane)
   2. TX failed to tune (gm praveen)
   3. anyone know sine wave or square wave external    clock is better
      for usrp (John Wu)
   4. Re: anyone know sine wave or square wave external clock is
      better for usrp (Sylvain Munaut)
   5. unable to register with the networkx (gm praveen)
   6. how to register with openbts?? (gm praveen)
   7. Re: how to register with openbts?? (abhinav anand)

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

Message: 1
Date: Thu, 21 Apr 2011 22:49:13 +0000
From: Royce Brisbane <roy...@ho...>
Subject: Re: [Openbts-discuss] IMSI-Catcher?! Is it legal?!
To: <maz...@gm...>,
    <ope...@li...>
Message-ID: <DUB...@ph...l>
Content-Type: text/plain; charset="iso-8859-1"

Do not deal with these guys I think it is a scam. The reason I say this is that 
I think I know who is behind it and if it is them, then the solution will not 
work as they say but they will want all your money up front. If required I can 
provide full e-mail proof and telephone call recordings to back this up.

Date: Fri, 22 Apr 2011 00:17:47 +0200
From: maz...@gm...
To: ope...@li...
Subject: [Openbts-discuss] IMSI-Catcher?! Is it legal?!

Hi guys,

i was searching on google about Open-BTS and i found this:

http://www.recursion.com/assets/Documents/xIMSI-vFinal.pdf

and i thought to publish here it, because i think that an IMSI-catcher (not for 
an educational purpose) is not so legal...

Regards

Gloria

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been 
demonstrated beyond question. Learn why your peers are replacing JEE 
containers with lightweight application servers - and what you can gain 
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
Openbts-discuss mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openbts-discuss                    

-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 2
Date: Fri, 22 Apr 2011 05:40:51 +0530 (IST)
From: gm praveen <gm...@ya...>
Subject: [Openbts-discuss] TX failed to tune
To: ope...@li...
Message-ID: <920...@we...>
Content-Type: text/plain; charset="utf-8"

thanks for replying
i have followed the https://github.com/GREO/OpenBTS/wiki  instruction
i got this error
can u give me link how to get git version and install procedure
one of my friend using the same usrp1 but he has a clock in the usrp haven't got 

any error
is it necessary to keep  clock and antenna for the usrp ???
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 3
Date: Fri, 22 Apr 2011 09:31:04 +0800
From: John Wu <jw...@gm...>
Subject: [Openbts-discuss] anyone know sine wave or square wave
    external    clock is better for usrp
To: ope...@li...
Message-ID: <BAN...@ma...>
Content-Type: text/plain; charset="iso-8859-1"

Hi all.
I need to use external clock on usrp, there are two kinds of clock: sine
wave and square wave. which
is better for usrp?
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 4
Date: Fri, 22 Apr 2011 08:25:56 +0200
From: Sylvain Munaut <24...@gm...>
Subject: Re: [Openbts-discuss] anyone know sine wave or square wave
    external clock is better for usrp
To: John Wu <jw...@gm...>
Cc: ope...@li...
Message-ID: <BANLkTi=5_mMntAM+En0Ei3keGj=aT...@ma...>
Content-Type: text/plain; charset=UTF-8

> I need to use external clock on usrp, there are two kinds of clock: sine
> wave and square wave. which
> is better for usrp?

square

1 Vpp (peak-to-peak)

Cheers,

    Sylvain

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

Message: 5
Date: Sat, 23 Apr 2011 07:35:46 +0530 (IST)
From: gm praveen <gm...@ya...>
Subject: [Openbts-discuss] unable to register with the networkx
To: ope...@li...
Message-ID: <119...@we...>
Content-Type: text/plain; charset="utf-8"

hiii
i have installed the openbts with 2 1800 rx cards i can see the network in my 
mobile 
is it necessary flash the cards to 900MHz?? because i can see the network when i 

only modify the
GSM.BAND 900
GSM.AFRCN 51 
otherwise it shows tx failed to tune.. . y??
any trick to regsiter with the openbts with any operator sim??

thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 6
Date: Sun, 24 Apr 2011 21:03:07 +0530 (IST)
From: gm praveen <gm...@ya...>
Subject: [Openbts-discuss] how to register with openbts??
To: ope...@li...
Message-ID: <134...@we...>
Content-Type: text/plain; charset="utf-8"

hiii

i  have installed the openbts . i would like how to register with openbts ??
is there any possibility to register with any operator sim like o2 , orange ?? 
or any other foreign sim??

thanks in advance .......
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 7
Date: Sun, 24 Apr 2011 12:42:39 -0700
From: abhinav anand <a.a...@gm...>
Subject: Re: [Openbts-discuss] how to register with openbts??
To: ope...@li...
Message-ID: <BANLkTikvnP9UJ3ocv4_h-VHS2n09ec=3T...@ma...>
Content-Type: text/plain; charset="iso-8859-1"

you can use any sim for registration as long as that operator is not present
in
your area. Best way is to operate OpenBTS in a frequency band separate from
your local operators. You need to Manual scan for your BTS signal in the
phone
and select BTS when seen.
Refer: OpenBTS_Guide_En_v0.1.pdf (google)

Regards,
Abhinav

On Sun, Apr 24, 2011 at 8:33 AM, gm praveen <gm...@ya...> wrote:

> hiii
>
> i  have installed the openbts . i would like how to register with openbts
> ??
> is there any possibility to register with any operator sim like o2 , orange
> ?? or any other foreign sim??
>
> thanks in advance .......
>
>
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can gain
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> Openbts-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...

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

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been 
demonstrated beyond question. Learn why your peers are replacing JEE 
containers with lightweight application servers - and what you can gain 
from the move. http://p.sf.net/sfu/vmware-sfemails

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

_______________________________________________
Openbts-discuss mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openbts-discuss

End of Openbts-discuss Digest, Vol 32, Issue 15
***********************************************
-------------- next part --------------
An HTML attachment was scrubbed...

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

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been 
demonstrated beyond question. Learn why your peers are replacing JEE 
containers with lightweight application servers - and what you can gain 
from the move. http://p.sf.net/sfu/vmware-sfemails

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

_______________________________________________
Openbts-discuss mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openbts-discuss

End of Openbts-discuss Digest, Vol 32, Issue 16
***********************************************

[Openbts-discuss] asterisk error: no matching peer found

GSM L1-L3 stack with SIP network interfaces

[Openbts-discuss] asterisk error: no matching peer found