When I first setup EchoLink on my HUB node, I could log into the CLI from remote and monitor the activity of the node. I would see that EchoLink would update its databases about once a minute or so and when ever someone on EchoLink connects to the node, I would see what the station was. It actually listed their Call sign. If you looked at the status page for AllStar, it would show all the nodes connected as well as the EchoLink stations with their call sign. I know there is an "undocumented feature" that AllStar does not show the correct EchoLink node number because it could be going through a proxy or relay, But it showed the correct call sign in the status and CLI. I never had success getting the EchoLink call signs to properly announce them selves. I decided to update the SVN to the latest. After I was done, I noticed no activity in the CLI for EchoLink. Also, when an EchoLink station connects, it just says "Connected (hub node #)" I tried changing the verbosity of the CLI, but nothing changed for EchoLink. Im not looking to get the announcement working, although it would be nice, but I would like to get the information in the CLI working again. Has anyone else experienced this? How do I resolve it?
Yeah - version 266 showed the E/L station's name, IP address and callsign on the CLI - even when a proxy was used. Version 304 shows nothing like that on the CLI. The announcement is either the node number, or nothing (just ".connected") depending on which mode you configure. Interestingly, when announcing nothing, there are still messages on the CLI as if a node number announcement was being played . I think eliminating the E/L database update status messages somehow (unintentionally) screwed up the ID announcement. Ken KE2N From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Bob Roszkowski Sent: Monday, September 03, 2012 5:46 PM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] EchoLink and the CLI When I first setup EchoLink on my HUB node, I could log into the CLI from remote and monitor the activity of the node. I would see that EchoLink would update its databases about once a minute or so and when ever someone on EchoLink connects to the node, I would see what the station was. It actually listed their Call sign. If you looked at the status page for AllStar, it would show all the nodes connected as well as the EchoLink stations with their call sign. I know there is an "undocumented feature" that AllStar does not show the correct EchoLink node number because it could be going through a proxy or relay, But it showed the correct call sign in the status and CLI. I never had success getting the EchoLink call signs to properly announce them selves. I decided to update the SVN to the latest. After I was done, I noticed no activity in the CLI for EchoLink. Also, when an EchoLink station connects, it just says "Connected (hub node #)" I tried changing the verbosity of the CLI, but nothing changed for EchoLink. Im not looking to get the announcement working, although it would be nice, but I would like to get the information in the CLI working again. Has anyone else experienced this? How do I resolve it?
Is there any way to roll back just echolink? If so, what does the new version fix/give us that the old one doesn't? boB On Sep 3, 2012, at 7:47 PM, "Ken" <ke2n@cs.com> wrote:
Yeah – version 266 showed the E/L station’s name, IP address and callsign on the CLI – even when a proxy was used.
Version 304 shows nothing like that on the CLI. The announcement is either the node number, or nothing (just “…connected”) depending on which mode you configure. Interestingly, when announcing nothing, there are still messages on the CLI as if a node number announcement was being played …
I think eliminating the E/L database update status messages somehow (unintentionally) screwed up the ID announcement.
Ken KE2N
From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Bob Roszkowski Sent: Monday, September 03, 2012 5:46 PM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] EchoLink and the CLI
When I first setup EchoLink on my HUB node, I could log into the CLI from remote and monitor the activity of the node. I would see that EchoLink would update its databases about once a minute or so and when ever someone on EchoLink connects to the node, I would see what the station was. It actually listed their Call sign. If you looked at the status page for AllStar, it would show all the nodes connected as well as the EchoLink stations with their call sign. I know there is an "undocumented feature" that AllStar does not show the correct EchoLink node number because it could be going through a proxy or relay, But it showed the correct call sign in the status and CLI. I never had success getting the EchoLink call signs to properly announce them selves. I decided to update the SVN to the latest. After I was done, I noticed no activity in the CLI for EchoLink. Also, when an EchoLink station connects, it just says "Connected (hub node #)" I tried changing the verbosity of the CLI, but nothing changed for EchoLink.
Im not looking to get the announcement working, although it would be nice, but I would like to get the information in the CLI working again.
Has anyone else experienced this? How do I resolve it?
participants (3)
-
Bob Roszkowski -
Bob＠w5evh.org
-
Ken