Re: [Openbts-discuss] RRLP Help

[Kurtis H. <khe...@cs...>]

First off, great work on figuring all of this out.

I've been able to confirm that it's not your phone; I'm see the exact
same behavior. I'm going to start a discussion with the developer of
this stack and see what he has to say. Basically, at this point,
there's clearly got to be a technical problem as there's no way that
the sendrrlp command should result in an SMS being received by the
user.

I'll get back to this once I learn more.

On Tue, Nov 29, 2011 at 11:04 AM, Ed Bindl <eb...@gm...> wrote:
> This was my experience with RRLP.  I'm not going to put it on the wiki yet
> because I still don't have it working.  But this should help get some people
> started.  Please follow these directions critically, because I have NO idea
> what I'm doing here.
> Get RRLP:
>
> svn co http://wush.net/svn/range/software/public/RRLP/trunk
>
> Install Erlang:
> sudo apt-get install erlang
>
> In the trunk directory:
> Open setUpFiles.sh and change the CGIBIN path to the proper path (Where ever
> you have configured it in apache: mine was defaulted to /usr/lib/cgi-bin/)
>
> Run:
> sudo sh ./setUpFiles.sh
>
> Verify that you can see the cgi file by browsing to it in a web browser.
> Depending on your apache settings the url should look something like:
> http://localhost/cgi-bin/rrlpserver.cgi
>
> This should return: “error=empty QUERY_STRING”
>
> Now open openBTS and update your config file to point at this cgi script. My
> command was:
> config GSM.RRLP.SERVER.URL http://localhost/cgi-bin/rrlpserver.cgi
>
> Now run:
> sudo mkdir /var/run/rrlp
> sudo chmod a+rw /var/run/rrlp
>
> Now go back to the trunk directory and:
>
> First try:
> ./rrfake testlled
> That verifies that the erlang stuff is running.
> If it doesn't work, perhaps you didn't compile. Or don't have erlang.
>
> Then you can try
> ./rrfake loc
> ./rrfake assist
> ./rrfake testpos
>
> These all depend on reading the ephemeris.
> If it doesn't work, perhaps you don't have a writable /var/run/rrlp where it
> caches the ephemeris.
>
>
> If all this works you should now be able to run:
>
> ./sendrrlp.escript <IMSI> <ACCURACY> <REFERENCE_NUMBER>
>
> Not sure what significance ACCURACY and REFERENCE NUMBER have, but I've been
> using 127 and 0, respectively.
>
> This then responds with:
>
> sending 0001FE98
>
> And I get a text message on my phone that says RRLP0001FE98.
> On Tue, Nov 29, 2011 at 1:51 PM, Gloria Mazzi
> <maz...@gm...> wrote:
>>
>> Hi all,
>> i'm still reading/understanding the sources, but if someone will write
>> just few lines of 'how to', i will be happy to make some tests and publish
>> related results.
>>
>> Cheers,
>> Gloria
>>
>>> Yea, I'll try to remember everything I did.  I meant to make note of
>>> everything, but I didn't exactly follow through.
>>>
>>> I sent the rrlp message through the command line and the same thing
>>> happens, I just get a text message that says RRLP0001FE98 (or what ever
>>> command I send it).
>>>
>>> The Nokia2310 is the only 2G phone I have that seems to be cooperating,
>>> so hopefully it's not simply a case of this phone not handling the request
>>> correctly.
>>>
>>> Let me try to put together my notes real quick.
>>>
>>> -Ed
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Openbts-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>
>