Good Day,
I've made a minor change to the app_rpt.c file, How do I recompile
app_rpt.c? I tried ./configure, make apps and then make install but
no joy, I must have missed something.
Thanks,
Bruce
Hi group, finally got everything running last weekend except for EchoLink.
When I try to do an inbound connection, it fails. An outbound connection
produces the following failure:
File.c : 1205 Unexpected control subclass '113
Then Asterisk stops and exits with a "exit 139" code
AllStar and IRLP are perfect, what did I do wrong?
Hello,
Since upgrading to app_rpt.c rev 190 our Asterisk system has been receiving a continual stream of:
"WARNING[6868] channel.c: Exceptionally long queue length queuing to Zap/pseudo-241657199 [Jun 22 20:37:37]" errors in /var/log/messages.
Will upgrading to rev 192 correct the problem?
Regards,
John
>
> From: Matt Beasant <g4rky(a)yahoo.co.uk>
> Date: 2009/06/22 Mon PM 02:05:25 PDT
> To: app_rpt <App_rpt-users(a)qrvc.com>
> Subject: [App_rpt-users] Beaconing node stanza
>
> Hi all,
> Where I can find the details of changes I need to make to my node stanza to
> get the newly added beacon mode enabled?
>
> Thanks,
>
> Matt
> G4RKY
>
>
Try searching http://app-rpt.qrvc.com for beaconing
Steve
WA6ZFT
_______________________________________________
App_rpt-users mailing list
App_rpt-users(a)qrvc.com
http://qrvc.com/mailman/listinfo/app_rpt-users
David Osborn wrote:
> Hello All.
>
>
>
> I am fairly new to AllStar but I now have got two nodes on the air (2480 &
> 2481), but not without a lot of help from Jim Dixon and Matt Beasant. Thank
> you both.
>
>
>
> I was wondering if I could retrieve the same status information that is
> posted to the stats.allstarlink.org database for my own use on another web
> site. I am thinking here of our repeater group page, where it would be
> useful to have up-to-the-minute node status data.
>
>
>
> Any suggestions as to how I might achieve this?
>
>
>
> Also, I see from /var/log/asterisk/messages that useful data is collected
> concerning EchoLink connections (amongst other stuff). I would like to parse
> out this information, again for posting on the website, but as I am not too
> well acquainted with the likes of grep, sed, awk and other tools, I'd be
> glad of some pointers - even a suggestion for a web-based tutorial on log
> file mangling would be good.
>
>
>
> Oh, one last thing. Can you guys advise on what console commands are
> available for checking Asterisk and app_rpt versions, so I can check where I
> am up to?
>
>
>
> Thanks.
>
>
>
> David Osborn
>
> GD4HOZ
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users(a)qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
The status information is sent to allstarlink.org using a wget commend.
If you want, you could replace the wget with a bash script, and send the
information to two destinations using two different wgets in the script.
This "splitter" script is something I'm going to code up soon.
We wrote some custom php code to receive the wget request and record the
information into a database which is then accessed when you visit stats.
allstarlink.org. A lot of static information also comes over the net
from the main allstarlink database. This would have to be supplied
locally in your case. This code is a hack. It is not able to be released
because of the potential support burden it would require from us.
Another approach would be to write a CGI to scrape the relevant
information from stats.allstarlink.org, and only display your nodes
on your club website. A better follow-on approach would be to make all
of the data available as a web service from stats.allstarlink.org as an
XML request, but that is a whole new project in and of itself. Note: You
won't get the fancy graphical node diagram doing this you would have to
cobble that together from the selected data you retrieved.
Regarding the use of sed, awk and friends on log files, please google
for this, there's plenty of information out there.
You can send DTMF commands from the Asterisk console using
the rpt fun command like this:
rpt fun 2480 *82
The above command will read back the app_rpt.c version number over the
node's transmitter.
Steve
WA6ZFT
Hello All.
I am fairly new to AllStar but I now have got two nodes on the air (2480 &
2481), but not without a lot of help from Jim Dixon and Matt Beasant. Thank
you both.
I was wondering if I could retrieve the same status information that is
posted to the stats.allstarlink.org database for my own use on another web
site. I am thinking here of our repeater group page, where it would be
useful to have up-to-the-minute node status data.
Any suggestions as to how I might achieve this?
Also, I see from /var/log/asterisk/messages that useful data is collected
concerning EchoLink connections (amongst other stuff). I would like to parse
out this information, again for posting on the website, but as I am not too
well acquainted with the likes of grep, sed, awk and other tools, I'd be
glad of some pointers - even a suggestion for a web-based tutorial on log
file mangling would be good.
Oh, one last thing. Can you guys advise on what console commands are
available for checking Asterisk and app_rpt versions, so I can check where I
am up to?
Thanks.
David Osborn
GD4HOZ
I have not been able to access the Asterisk node status page for several days.
Is it down, or am I having a local problem? Thanks.
Best regards,
Gary, K7EK
>
> From: Mark Cheavens <mcheavens(a)usa.net>
> Date: 2009/06/15 Mon PM 02:15:06 PDT
> To: app_rpt <app_rpt-users(a)qrvc.com>
> Subject: [App_rpt-users] How to update...?
>
> I have the latest version of ACID installed on 6+ nodes. I know that
> the astupd.sh script will at some time update the app_rpt and
> irlp/echolink channels, but in a step by step how would one get the
> latest builds (Bleeding edge) installed and built?
>
> Mark
> KC5EVE
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users(a)qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
>
There is no step-by-step guide to doing this as it is not a canned process. This is really something only a developer or tester should attempt. Tinkering with the latest code on production systems is not advised. If you have a sandbox system, you can check out the files using SVN then copy them over the top of the existing files in /usr/src using cp, then manually recompile everything, and restart your system. How to access SVN is noted here:
http://app-rpt.qrvc.com/node/6
Steve
WA6ZFT
