I have two all-star nodes and i have echo link installed on both units and when i take my iPhone or iPad or other computer and log into the echo link on the pi’s running all-star echo link it shows the echo link number and NOT the call sign is there a way to change this ? I have looked for 2 days now trying to fond out out how to change and I have not found anything
both echo link nodes are ke3jp-r and ke3jp-l
thanks for any help on this Mike ke3jp
I don’t think you have the ability to control how this works from the Pi’s/nodes CLI view’s perspective… nor can you tell from the Echolink client what your ASL node’s connected-call sign is… You are going to see the node number only in each case…
If you’re in the asterisk CLI, you can run an ID lookup like so, and the results will give you call sign…
node*CLI> echolink dbget nodename xxxxxx
I do know that the Supermon utility would reveal this information to you as it queries your Pi node’s connections, and you could use Supermon to see this detail. I also believe your node’s connection logs should be able to give this away.
Hope this helps…
Byron
Is there any plan to add the ability for users connected to Echolink via the Echolink apps, to see the connected stations' callsigns rather than just the node numbers? I have recently added Echolink to my ASL3 node at a main site to get rid of the remotely located Echolink host PC. I am now getting complaints from the user base that they can no longer see who is connected during nets etc... Net control ops, even if running the net via RF, normally log into Echolink so they can verify check ins.
Eric
K2CB
Are you saying that you moved from some sort of Echolink Conference/Hub application running on a PC that had a single connection to an ASL system to one that's using chan_echolink to host all of the Echolink connections? And then when you say "see" are you talking about in the Echolink application having the ASL node numbers resolve to registered Echolink callsigns?
If so, that's an issue for the Echolink client to resolve the node numbers.
Yes. Echolink was running in sysop -R mode on a PC connected to the repeater controller. Users connecting to this Echolink node would see the callsigns of the other connected stations on their PC or phone Echolink client app.
We decommissioned the PC, and now have chan_echolink running on an ASL node, connected to the repeater controller. Users now only see the Echolink node numbers, and not the actual callsigns, of the other connected stations.
I guess the question is, does the Echolink user application resolve the id to callsign locally in the app, or is the callsign itself being sent to the app? I suspect it may be the latter. Otherwise, one would expect it to resolve the node number to callsign either way.
Eric
K2CB
I don't really use Echolink and have never used it with anything except an ASL node so I've only ever seen the numbers. Didn't know there was any other mode.
Everything in ASL is based on node numbers and it's up to client applications to decide what the numbers actually mean. There's a CLI function in app_rpt that gets and resolves Echolink IDs upon request but that's just for admin convenience because you can't really do it without an authenticated Echolink client.
You could file an enhancement request in the app_rpt project on GitHub for chan_echolink but we'd need someone to work on that. You'd basically need to alter the protocols to send callsigns not node numbers. That might be a lot of work for questionable value.
Please excuse my ignorance.......... I took a look around the app_rpt GitHub site, and could not find where to enter such a request. Can you kindly point me to the correct location to submit such a request?
Eric
K2CB
For those following, @K2CB filed app_rpt : Issue #670