APRS TT and APRS BEACON rate on ALLSTAR LINK..
To get aprs TT working on ALLSTARLINK down load the latest from the SVN. Upgrading Asterisk to latest (SVN) version If you are using a brand-new current version of ACID or Limey Linux (that was released after the implementation of this new Portal) you are already upgraded sufficiently. If not ... Asterisk must be upgraded to the latest SVN version. For the ACID distribution (and other Linux platforms): cd /usr/src rm -rf astsrc wget http://x.allstarlink.org/svn-trunk.tar.gz -O- | tar xzv mv trunk astsrc cd astsrc make upgrade-acid Then go into the rpt.conf file and add APRSTT= some where in that file. I made it the first line in that config file right underneath the node number Then just google APRS TT and there is a link on Bob's aprs site on everything about APRSTT.. Then to get it to only beacon every 10 min's i added interval=600 into the gps.conf file. 73's Bradley
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:00:22 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:52:32 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "*[Invalid object]*"? Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck 2012-06-04 14:05:58 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> * * * * *
APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
On Thu, May 3, 2012 at 8:09 PM, Bradley Haney <kc9gqr@gmail.com> wrote:
To get aprs TT working on ALLSTARLINK down load the latest from the SVN.
Upgrading Asterisk to latest (SVN) version
If you are using a brand-new current version of ACID or Limey Linux (that was released after the implementation of this new Portal) you are already upgraded sufficiently. If not ...
Asterisk must be upgraded to the latest SVN version.
For the ACID distribution (and other Linux platforms): cd /usr/src rm -rf astsrc wget http://x.allstarlink.org/svn-trunk.tar.gz -O- | tar xzv mv trunk astsrc cd astsrc make upgrade-acid
Then go into the rpt.conf file and add APRSTT=
some where in that file. I made it the first line in that config file right underneath the node number
Then just google APRS TT and there is a link on Bob's aprs site on everything about APRSTT..
Then to get it to only beacon every 10 min's i added interval=600 into the gps.conf file.
73's
Bradley _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson < rpt2@chuck.midlandsnetworking.com> wrote:
APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "*[Invalid object]*"?
Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:00:22 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:52:32 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
2012-06-04 14:05:58 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> * * * * *
APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is: ;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user (note the extra space before the "*") -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey
Boy, *that* was just painfully obvious... (NOT!) Okay, I'll fix it. :-) Thanks for letting me know. JIM From: tom.km5vy@gmail.com Date: Mon, 4 Jun 2012 10:44:03 -0600 To: rpt2@chuck.midlandsnetworking.com CC: kc9gqr@gmail.com; app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] APRS TT and APRS BEACON rate on ALLSTAR LINK.. On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson <rpt2@chuck.midlandsnetworking.com> wrote: APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "[Invalid object]"? Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck 2012-06-04 14:05:58 UTC: WB9UUS-R>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user [Invalid object] 2012-06-04 15:00:22 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user [Invalid object] 2012-06-04 15:52:32 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: WB9UUS-R>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is: ;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user (note the extra space before the "*") -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On Mon, Jun 4, 2012 at 11:35 AM, Jim Duuuude <telesistant@hotmail.com>wrote:
Boy, *that* was just painfully obvious... (NOT!)
Heh. It's documented pretty clearly in the APRS spec, once you find it. Unfortunately the spec is divided between an official PDF document and a collection of HTML "addenda". All can be found (with a little eye strain) on www.aprs.org.
Okay, I'll fix it. :-)
Excellent.
Thanks for letting me know.
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:00:22 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:52:32 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
NP. ------------------------------ From: tom.km5vy@gmail.com Date: Mon, 4 Jun 2012 10:44:03 -0600 To: rpt2@chuck.midlandsnetworking.com CC: kc9gqr@gmail.com; app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] APRS TT and APRS BEACON rate on ALLSTAR LINK.. On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson < rpt2@chuck.midlandsnetworking.com> wrote: APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "*[Invalid object]*"? Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck 2012-06-04 14:05:58 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> * * * * *
APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is: ;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user (note the extra space before the "*") -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey
Well I don't think I can enter a space using touchtone so it must need to be fixed in the app_rpt software. I am running the latest software as of May 9 2012. I'm not sure where in the C code to fix this but I think maybe it would be in gps.c sprintf(buf,"%s>APSTAR:;%s-12*%02d%02d%02dz%s%c%sA%s\n", call,theircall,tm->tm_hour,tm->tm_min,tm->tm_sec,lat,overlay,lon,comment); if theircall is less than 6 char then theircall-12 needs to be padded on the right with spaces to make it a total of 9 char in length. I think that it will be easy for Jim to fix, he might even have it fixed faster than I can type this email. Chuck On Mon, Jun 4, 2012 at 11:44 AM, Tom Russo <tom.km5vy@gmail.com> wrote:
On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson < rpt2@chuck.midlandsnetworking.com> wrote:
APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "*[Invalid object]*"?
Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:00:22 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:52:32 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
2012-06-04 14:05:58 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> * * * * *
APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is:
;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user
(note the extra space before the "*")
-- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey
On Mon, Jun 4, 2012 at 11:55 AM, Chuck Henderson < rpt2@chuck.midlandsnetworking.com> wrote:
Well I don't think I can enter a space using touchtone so it must need to be fixed in the app_rpt software. I am running the latest software as of May 9 2012. I'm not sure where in the C code to fix this but I think maybe it would be in gps.c sprintf(buf,"%s>APSTAR:;%s-12*%02d%02d%02dz%s%c%sA%s\n",
call,theircall,tm->tm_hour,tm->tm_min,tm->tm_sec,lat,overlay,lon,comment);
if theircall is less than 6 char then theircall-12 needs to be padded on the right with spaces to make it a total of 9 char in length.
Yes, that's precisely where the fix needs to happen. On Mon, Jun 4, 2012 at 11:44 AM, Tom Russo <tom.km5vy@gmail.com> wrote:
On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson < rpt2@chuck.midlandsnetworking.com> wrote:
APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "*[Invalid object]*"?
Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:00:22 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user *[Invalid object]* 2012-06-04 15:52:32 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R>
2012-06-04 14:05:58 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> * * * * *
APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: *WB9UUS-R<http://aprs.fi/?c=raw&limit=&call=WB9UUS-R> *>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is:
;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user
(note the extra space before the "*")
-- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey
-- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey
This problem has been fixed, and the new source code for app_gps.c will be available in the public SVN update at 08:15 PDT today. Jim WB6NIL From: tom.km5vy@gmail.com Date: Mon, 4 Jun 2012 12:06:10 -0600 To: rpt2@chuck.midlandsnetworking.com CC: kc9gqr@gmail.com; app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] APRS TT and APRS BEACON rate on ALLSTAR LINK.. On Mon, Jun 4, 2012 at 11:55 AM, Chuck Henderson <rpt2@chuck.midlandsnetworking.com> wrote: Well I don't think I can enter a space using touchtone so it must need to be fixed in the app_rpt software.I am running the latest software as of May 9 2012. I'm not sure where in the C code to fix this but I think maybe it would be in gps.c sprintf(buf,"%s>APSTAR:;%s-12*%02d%02d%02dz%s%c%sA%s\n", call,theircall,tm->tm_hour,tm->tm_min,tm->tm_sec,lat,overlay,lon,comment); if theircall is less than 6 char then theircall-12 needs to be padded on the right with spaces to make it a total of 9 char in length. Yes, that's precisely where the fix needs to happen. On Mon, Jun 4, 2012 at 11:44 AM, Tom Russo <tom.km5vy@gmail.com> wrote: On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson <rpt2@chuck.midlandsnetworking.com> wrote: APRSTT on my systems works for some call signs but not for some others. Here is an example from the aprs.fi raw log. Can anyone shed some light on why N9DOA shows up as "[Invalid object]"? Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf? Chuck 2012-06-04 14:05:58 UTC: WB9UUS-R>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 2012-06-04 14:06:08 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user 2012-06-04 14:38:05 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user [Invalid object] 2012-06-04 15:00:22 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user 2012-06-04 15:13:33 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user [Invalid object] 2012-06-04 15:52:32 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user 2012-06-04 15:52:39 UTC: WB9UUS-R>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is: ;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user (note the extra space before the "*") -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." - Edward Abbey _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (4)
-
Bradley Haney -
Chuck Henderson -
Jim Duuuude -
Tom Russo