Hello, My apologies if this has been covered.. I searched the archives this morning before posting.. I'm just getting my Echolink node connected, and curious if it's possible to report my node to Echolink's Link Status screen? http://www.echolink.org/links.jsp Thanks.. 73, Kyle K0KN
On 1/20/11 9:55 AM, K&R Yoksh wrote:
Hello, My apologies if this has been covered.. I searched the archives this morning before posting.. I'm just getting my Echolink node connected, and curious if it's possible to report my node to Echolink's Link Status screen? http://www.echolink.org/links.jsp Thanks.. 73, Kyle K0KN I'm thinking not, since the verbiage at the bottom of the page says: "The table above shows information collected during the past several minutes from EchoLink "sysop" stations (those with a -L or -R suffix). The only stations shown are those which are *running EchoLink version 1.6 * or above, and have entered location information on the RF Info tab of Sysop Settings."
We're not running Echolink software...so, while we're able to register our nodes, I'm thinking that the Echolink mother ship is studiously ignoring, for the sake of display, alternative software that speaks their language. Hey, it's free as in beer, fwiw. Not saying they shouldn't, but, that would seem to be the most logical explanation...because I'm sure that trying to support a published API for every version of off-brand, so to speak, software that wants to talk to their server is probably not going to happen any time soon. -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me.
Hey, it's free as in beer, fwiw.
I posted something on this more than a year ago (in the bug list and desired features reflector). We figured out what the format of the required data was (as I recall it is encrypted info) but the whole thing was regarded as really a low priority, nice-to-have, item. My experience is that your node does show up in http://www.echolink.org/logins.jsp Interestingly enough, I found you can run the Windows version of the program at the same Internet address and put all your information in there and it will show up on the desired listing while Asterisk actually answers the call and talks to the radios. Ken KE2N
I suspect that the app_rpt echolink client is not reporting to the mothership, not that the mothership is ignoring us. If that's the case, maybe our exalted developer would add echolink status reporting. -- Tim :wq On Jan 20, 2011, at 7:16 AM, Bryan D. Boyle wrote:
We're not running Echolink software...so, while we're able to register our nodes, I'm thinking that the Echolink mother ship is studiously ignoring, for the sake of display, alternative software that speaks their language.
Jim, I believe what people are asking for is to have app_rpt send status updates when connects and disconnects occur. Below is the format for echolink status reporting taken from Skip's WB6YMH source for thelinkbox. Looks like the connect message would be "=NNTECHTALK at 1530" for example. I assume the disconnect message would be " On @ 1545". EchoLink sends a packet once every 10 minutes to aprs.echolink.org. It also sends a packet when the node status changes (i.e., when somebody connects or disconnects, or the node comes online or goes offline). The packet is an RTP control packet, and thus is sent to port 5199. The CNAME portion is the node callsign (including -L/-R), followed by a slash, followed by a "password", which is actually a hash of the callsign. However, at this time, the password field is ignored by the server; a future release of the server will verify the authenticity of the packet by its source IP address. So the callsign can be repeated in this second field. The format of the LOC portion is as follows: )EL-nnnnnn!DDMM.HHNXDDDMM.HHW0PHGphgd/FFFFFF/PPPyyyyyyyyyyzzzzzzzz Where: nnnnnn is the 6 character node Name or Callsign (right-padded with spaces to 6 chars) DDMM.HHN DDDMM.HHW is the LAT/LONG of the node, using degrees, minutes, and 100ths of minutes, and E/W/N/S X is the letter "E", for EchoLink 0 is a "zero",the ICON character p is the power (encoded) h is the antenna height (encoded) g is the antenna gain (encoded) d is the antenna directivity (encoded) FFFFFF is the frequency in KHz /PPP is the PL in whole number Hz yyyyyyyyyy Second line on a D7 (11th to 20th on a D700) zzzzzzzz last 8 not shown on a D7 but are on the D700 Formats for the variable field YYYYYYYYYY and ZZZZZZZZ: Offline: " Off @HHMM........" can contain some comment On-Line: " On @ HHMM........" Time it returned to ON-Line Busy: " Busy HHMM........" Time it went busy Connected: "=NNnnnnnnn at HHMM" Shows call/Name of connection The encoding of the p/h/g/d fields is as follows: DIGITS 0 1 2 3 4 5 6 7 8 9 ------------------------------------------------------------------- POWER 0, 1, 4, 9, 16, 25, 36, 49, 64, 81 watts SQR(P) HEIGHT 10,20,40, 80,160,320,640,1280,2560,5120 feet LOG2(H/10) GAIN 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 dB DIR omni,45,90,135,180,225,270, 315, 360, . deg (D/45) For example: // )EL-K1RFD !4118.52NE07329.97W0PHG7430/144300/000 On @0444 Rdgfld -- Tim :wq On Jan 20, 2011, at 8:08 AM, Tim Sawyer wrote:
I suspect that the app_rpt echolink client is not reporting to the mothership, not that the mothership is ignoring us. If that's the case, maybe our exalted developer would add echolink status reporting. -- Tim :wq
On Jan 20, 2011, at 7:16 AM, Bryan D. Boyle wrote:
We're not running Echolink software...so, while we're able to register our nodes, I'm thinking that the Echolink mother ship is studiously ignoring, for the sake of display, alternative software that speaks their language.
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Chan_echolink now supports proper display/reporting to the echolink server stuff. Please download the new version of chan_echolink.c from SVN. For details on configuration, please see: http://209.159.155.200/drupal/node/56 Note the following additions to the echolink.conf file: freq=145.000 ; Freq in MHz tone=100.0 ; CTCSS Tone (0 for none) lat=34.74978 ; Latitude in decimal degrees lon=-92.27666 ; Longitude in decimal degrees power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) gain=7 ; Gain in db (0-9) dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction) JIM WB6NIL
Awesome! Thank you Jim. -- Tim :wq On Jan 21, 2011, at 6:27 PM, Jim Duuuude wrote:
Chan_echolink now supports proper display/reporting to the echolink server stuff.
Please download the new version of chan_echolink.c from SVN.
For details on configuration, please see:
http://209.159.155.200/drupal/node/56
Note the following additions to the echolink.conf file:
freq=145.000 ; Freq in MHz tone=100.0 ; CTCSS Tone (0 for none) lat=34.74978 ; Latitude in decimal degrees lon=-92.27666 ; Longitude in decimal degrees power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) gain=7 ; Gain in db (0-9) dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction) JIM WB6NIL
The lat / lon format is incorrect.. Go to the link below and convert your dd.mmmmm to dd mm.mm and enter as 44.mmmm only the first 4 digits after the . count So for my location (KB2EAR-R / 2298) its: 40.2526 and not 40.421103 and -74.3392 and not -74.565346 http://www.csgnetwork.com/gpscoordconv.html -----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Bryan D. Boyle Sent: Friday, January 21, 2011 10:39 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Link Status On 1/21/2011 10:33 PM, Tim Sawyer wrote:
Awesome! Thank you Jim. --
Agreed! Thank you for the added functionality. building now...and editing the file...:) Bryan WB0YLE Allstar 27294 _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
oh poo!! Ill have to fix it. Its truly meant to be decimal degrees. JIM WB6NIL
From: kb2ear@kb2ear.net To: bdboyle@bdboyle.com; app_rpt-users@ohnosec.org Date: Fri, 21 Jan 2011 22:53:29 -0500 Subject: Re: [App_rpt-users] Echolink Link Status
The lat / lon format is incorrect.. Go to the link below and convert your dd.mmmmm to dd mm.mm and enter as 44.mmmm only the first 4 digits after the . count
So for my location (KB2EAR-R / 2298) its: 40.2526 and not 40.421103 and -74.3392 and not -74.565346
http://www.csgnetwork.com/gpscoordconv.html
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Bryan D. Boyle Sent: Friday, January 21, 2011 10:39 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Link Status
On 1/21/2011 10:33 PM, Tim Sawyer wrote:
Awesome! Thank you Jim. --
Agreed! Thank you for the added functionality.
building now...and editing the file...:)
Bryan WB0YLE Allstar 27294 _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 1/21/2011 11:15 PM, Jim Duuuude wrote:
oh poo!! Ill have to fix it. Its truly meant to be decimal degrees.
JIM WB6NIL
Also....here's a good one...send up the frequency as 224.540...EL displays as 224.539...:) Talk about a little rounding error (or not...)...close enough for small tactical nukes...;). But, works nice so far. bryan wb0yle allstar 27294
All righty... Lets try this again.. Please download the latest version of chan_echolink.c from SVN, and we'll see if this works better. JIM
Date: Fri, 21 Jan 2011 23:21:20 -0500 From: bdboyle@bdboyle.com To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Link Status
On 1/21/2011 11:15 PM, Jim Duuuude wrote:
oh poo!! Ill have to fix it. Its truly meant to be decimal degrees.
JIM WB6NIL
Also....here's a good one...send up the frequency as 224.540...EL displays as 224.539...:) Talk about a little rounding error (or not...)...close enough for small tactical nukes...;).
But, works nice so far.
bryan wb0yle allstar 27294
I know how to download the entire set of source files, but how do I download just one file such as chan_echolink.c? On Fri, Jan 21, 2011 at 8:27 PM, Jim Duuuude <telesistant@hotmail.com>wrote:
Chan_echolink now supports proper display/reporting to the echolink server stuff.
Please download the new version of chan_echolink.c from SVN.
http://app-rpt-svn.ohnosec.org/viewvc/projects/allstar/astsrc-1.4.23-pre/tru... On 01/22/2011 05:39 PM, Chuck Henderson wrote:
I know how to download the entire set of source files, but how do I download just one file such as chan_echolink.c?
On Fri, Jan 21, 2011 at 8:27 PM, Jim Duuuude <telesistant@hotmail.com <mailto:telesistant@hotmail.com>> wrote:
Chan_echolink now supports proper display/reporting to the echolink server stuff.
Please download the new version of chan_echolink.c from SVN.
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
I have updated to ver 0.281 and I see the enhanced echolink info on echolink.org I assume I should see a position on the APRS map too http://aprs.fi/ but I do not see it there. I have a manually-generated config file app_gps.conf along the lines of what is on the web site with the password generated at the portal (manually). Is there some "switch" that needs to be turned on somewhere (send_APS=yes) or something like that? Should I see a status message on the CLI when the info is sent ? I only see echolink updates Tnx Ken KE2N 27021 W4BRM/R (w4brm-1)
On 2/6/2011 5:48 PM, Ken wrote:
I have updated to ver 0.281 and I see the enhanced echolink info on echolink.org
I assume I should see a position on the APRS map too
Yup. do a search on WB0YLE-8, and you'll see my 'tower'...:)
but I do not see it there.
I have a manually-generated config file app_gps.conf along the lines of what is on the web site with the password generated at the portal (manually).
Is there some "switch" that needs to be turned on somewhere (send_APS=yes) or something like that?
Should I see a status message on the CLI when the info is sent ? I only see echolink updates
At least this is what I did on my system (ACID load, up to date...): system.conf: aprsenable=1 my gps config file is named just gps.conf, don't know whether that makes any diff. 73, BB WB0YLE Allstar 27294 Echolink WB0YLE-R
And...btw...this is my gps.conf, for what it's worth...: [general] call = WB0YLE-8 ; callsign (including SSID) for APRS purposes password = changeme ; Password for APRS-IS server for above callsign comment = 224.54/222.94, PL 141.3 (4A). AllStar node 27294 connected to the 27200 hub, Echolink WB0YLE-R. Member of the Penn Wireless and Raritan Valley Radio Clubs. Join the RVRC social net Sundays at 8PM ET on this frequency. ; Text to be displayed associated with this station server = second.aprs.net ; APRS-IS server to report information to port = 10151 ; port on server to send data icon = r ; Icon do be displayed for station on APRS display debug = y ; set this for debug output freq=224.54 ; Display Frequency of station tone=141.3 ; CTCSS tone of station (0.0 for none) lat=40.1982 ; Fixed (default) latitude in decimal degrees lon=-74.8114 ; Fixed (default) longitude in decimal degrees elev=47.24 ; Elevation of Antenna in Meters (*NOT* HAAT) power=9 ; Power level (see below) height=2 ; Antenna Height in HAAT (see below) gain=7 ; Antenna Gain (see below) dir=0 ; Antenna Direction (see below) HTH. 73 BB WB0YLE Allstar 27294 Echolink WB0YLE-R
I am curious about this entry in the config file (It is not explained in the web help) recfile=/tmp/recorded.gsm is there where echolink audio is (temporarily) recorded? I think not, since this directory/file does not show up on my system. Perhaps this is intended to be a connect message? In which case I should re-name it to something in /var/lib/asterisk/sounds/... Right now when an echolink user connects he hears absolutely nothing unless there is a QSO in progress Is there a way to send a connect message to the connectee? Tnx Ken
It does absolutely nothing and doesnt belong there. JIM WB6NIL
From: ke2n@cs.com To: app_rpt-users@ohnosec.org Date: Sun, 13 Feb 2011 14:38:06 -0500 Subject: [App_rpt-users] echolink
I am curious about this entry in the config file (It is not explained in the web help) recfile=/tmp/recorded.gsm
is there where echolink audio is (temporarily) recorded? I think not, since this directory/file does not show up on my system.
Perhaps this is intended to be a connect message? In which case I should re-name it to something in /var/lib/asterisk/sounds/...
Right now when an echolink user connects he hears absolutely nothing unless there is a QSO in progress Is there a way to send a connect message to the connectee?
Tnx Ken
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Sunday, February 13, 2011 3:52 PM To: ke2n@cs.com; app_rpt mailing list Subject: RE: [App_rpt-users] echolink It does absolutely nothing and doesnt belong there.
I am curious about this entry in the config file recfile=/tmp/recorded.gsm
============== Alright, that's half the question. Has anyone figured out how to do a connect message? The "playback" command does not seem to put any audio onto the echolink - link Ken
participants (8)
-
Bryan D. Boyle -
Chuck Henderson -
Jim Duuuude -
K&R Yoksh -
Ken -
Scott Weis -
Tim Sawyer -
Tony KT9AC