Forum: GNU Radio How to run OpenBTS? Where to subscribe the openbts mailing list?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
9f439a67199b34986c71a6ada12e9870?d=identicon&s=25 Jane Chen (jane)
on 2009-04-21 07:37
(Received via mailing list)
Hi all,
 
I tried to subscribe the openbts mailing list, but I did not succeed.  I
sent email to dburgess@kestrelsp.com to subscribe the openbts mailing
list. Could anyone please help me solve the following problem?
 
I tried to run the OpenBTS according to the instruction.
http://www.gnuradio.org/trac/wiki/OpenBTS/BuildingAndRunning.
 

Start Asterisk.
Start your SIP test phone and be sure that it can register with
Asterisk.
Start the transceiver (in Transceiver/). It's best to route the output
to /dev/null.
Start OpenBTS<whatever> (in apps/). You probably want to pipe the output
through grep.

"grep Control" to see L3 activities.
"grep LAPDm" to see L2 transactions.
"grep SIP" to see SIP transactions.
 
I am not sure what I did is what the instruction means. Does "start
asterisk" mean "asterisk -vvvc"? Does "start SIP phone" means to execute
the executable zoiper? How can I know if the SIP phone can register with
Asterisk? Does "start the transceiver" mean "nice -10 ./transceiver
>/dev/null"?  Does "start  OpenBTS<whatever>"  mean
"./OpenBTS900 |grep Control"?
 
However, I  got Segmentation fault.
 
#nice -10 ./transceiver >/dev/null
1240289394.105683 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.105769 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.105830 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.108622 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.110821 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.111397 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.351538 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.412328 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.415883 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.417252 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.716621 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.725226 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.736446 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.749662 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.750709 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.751416 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.757197 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.757249 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.759224 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.763311 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.764137 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.765609 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.766290 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.766334 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.767556 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289395.040693 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.675760 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.695241 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.714066 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.741100 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
Segmentation fault




#./OpenBTS900 |grep Control
1240289393.494647 2987666320: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.632717 2985544592: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.658338 2984479632: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.680024 2983414672: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.811467 2982349712: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.017113 2981018512: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.259516 2979687312: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.518855 2978356112: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.764171 2977024912: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289395.026865 2975693712: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289395.214604 2974362512: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
 
 
Thank you,
Jane
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2009-04-21 18:14
(Received via mailing list)
On Mon, Apr 20, 2009 at 10:35:44PM -0700, Jane Chen wrote:
> Start OpenBTS<whatever> (in apps/). You probably want to pipe the output through grep.
>
> "grep Control" to see L3 activities.
> "grep LAPDm" to see L2 transactions.
> "grep SIP" to see SIP transactions.
>  
> I am not sure what I did is what the instruction means. Does "start asterisk" mean 
"asterisk -vvvc"? Does "start SIP phone" means to execute the executable zoiper? How can I 
know if the SIP phone can register with Asterisk? Does "start the transceiver" mean "nice 
-10 ./transceiver >/dev/null"?  Does "start  OpenBTS<whatever>"  mean
> "./OpenBTS900 |grep Control"?
>  
> However, I  got Segmentation fault.

Jane,

Have you tried using gdb to see where the segfault is coming from?

Eric
C265fb2d2e273d02baff8dd2cec68f63?d=identicon&s=25 Hassan Moradi (Guest)
on 2009-04-21 22:25
(Received via mailing list)
I didn't know that there is a mailing list specified for OpenBTS. What's
the e-mail address?

I tried to install OpenBTS. I made it successfully by "make" command.
However some files, e.g. the files in "tests" directory, are not
compiled. Also, apparently, "make install" does nothing! No library is
added to my lib directory.

Anyway, I don't know how to use the OpenBTS library in my script? Shall
I use APIs in my C program? Does anybody know about that?

Thanks,
Hassan

 



________________________________
From: Jane Chen <janechen_1979@yahoo.com>
To: discuss-gnuradio@gnu.org
Sent: Monday, April 20, 2009 10:35:44 PM
Subject: [Discuss-gnuradio] How to run OpenBTS? Where to subscribe the
openbts mailing list?


Hi all,

I tried to subscribe the openbts mailing list, but I did not succeed.  I
sent email to dburgess@kestrelsp.com to subscribe the openbts mailing
list. Could anyone please help me solve the following problem?

I tried to run the OpenBTS according to the instruction.
http://www.gnuradio.org/trac/wiki/OpenBTS/BuildingAndRunning.

  1. Start Asterisk.
  2. Start your SIP test phone and be sure that it can register with
Asterisk.
  3. Start the transceiver (in Transceiver/). It's best to route the
output to /dev/null.
  4. Start OpenBTS<whatever> (in apps/). You probably want to pipe the
output through grep.
  * "grep Control" to see L3 activities.
  * "grep LAPDm" to see L2 transactions.
  * "grep SIP" to see SIP transactions.

I am not sure what I did is what the instruction means. Does "start
asterisk" mean "asterisk -vvvc"? Does "start SIP phone" means to execute
the executable zoiper? How can I know if the SIP phone can register with
Asterisk? Does "start the transceiver" mean "nice -10 ./transceiver
>/dev/null"?  Does "start  OpenBTS<whatever>"  mean
"./OpenBTS900 |grep Control"?

However, I  got Segmentation fault.

#nice -10 ./transceiver >/dev/null
1240289394.105683 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.105769 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.105830 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.108622 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.110821 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.111397 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.351538 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.412328 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.415883 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.417252 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.716621 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.725226 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.736446 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.749662 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.750709 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.751416 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.757197 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.757249 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.759224 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.763311 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.764137 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.765609 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.766290 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289394.766334 3085982608: USRPDevice..cpp:347: WARNING -- UNDERRUN
in TRX->USRP interface
1240289394.767556 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289395.040693 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.675760 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.695241 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.714066 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
1240289405.741100 3085982608: USRPDevice.cpp:347: WARNING -- UNDERRUN in
TRX->USRP interface
Segmentation fault




#./OpenBTS900 |grep Control
1240289393.494647 2987666320: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.632717 2985544592: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.658338 2984479632: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.680024 2983414672: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for SDCCH ESTABLISH
1240289393.811467 2982349712: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.017113 2981018512: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.259516 2979687312: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.518855 2978356112: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289394.764171 2977024912: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289395.026865 2975693712: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH
1240289395.214604 2974362512: DCCHDispatch.cpp:105 ControlLayer
DCCHDisptacher waiting for FACCH ESTABLISH


Thank you,
Jane
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2009-04-22 07:23
(Received via mailing list)
On Tue, Apr 21, 2009 at 01:23:41PM -0700, Hassan Moradi wrote:
> I didn't know that there is a mailing list specified for OpenBTS. What's the e-mail 
address?

This is the right place.  However, the OpenBTS guys are currently
operating under a restraining order which is why you haven't heard
from them.  They hope to have their problem resolved soon (perhaps a
week or two.)

I haven't played with OpenBTS much, so at least for now, everybody is
on their own to understand the code, share what you figure out and
send up patches to fix anything that's broken.

Eric
This topic is locked and can not be replied to.