16 Apr
2021
16 Apr
'21
1:58 a.m.
Le 15/04/2021 à 18:15, Rob PE1CHL via 44Net a écrit :
I will explain things here on the list as there may be
other people wondering about this...
Wow ! What can I say more than : "Thank you very much" :-) You provided
in one message all the answers I didn't find in the Echolink
documentation, HI :-)
In fact, I never managed to get my personal callsign registered at
Echolink, and that's one of the reasons reason why I don't really enjoy
"closed source" and "closed networks" :-) But it's just a personal
opinion, HI :-) As far as some of our users do enjoy Echolink, my job is
to provide network access :-)
Yesterday, when trying to troubleshoot a problem with our Asterisk /
app_rpt / chan_echolink, I noticed that, when selecting "auto proxy" on
the client, I was redirected to 44.190.8.180 (VK3JED), with a ping of
256ms (Hello Tony, are your proxies using "long path", HI ?)
What made me think about installing some local proxy :-)
Anyway, reading your clear explanation, I think it would be a waste of
public IPs. AFAIK, I can install some "local proxies" and point my users
specifically to them. But it's not possible to make "local relays" and
restrict them to my local users. And I don't have network resources for
providing WW relays. Then, as far as our BGP gateway for 44.190
addresses is in Paris, and most French public ISP traffic (even from our
island of Corsica) goes through Paris, it seems clever to use existing
proxies/relays in Europe, and in the Netherlands (which is very near
from Paris in terms of ping).
Then, the remaining question is :
When using Echolink Android client, and selecting "Auto proxy" settings,
why does it select VK3JED and not PE1CHL ?
73 de TK1BI