[arm-allstar] Echolink

[Doug Crompton]

To All Echolink users!

   Please be thankful that you have Echolink in conjunction with the
Allstar code and that we (hamvoip) have solved many of the serious issues
plaguing it in the past. Not seeing a call is NOT a serious issue. I am not
saying it will not be addressed and possibly fixed but it is not a high
priority issue on our table. Allstar always comes first and we have and
will be making vast improvements there. If you came to Allstar just to use
Echolink and expect all the bells and whistles you had in Windows or on
your phone then you came to the wrong place. The best thing you could do is
encourage your Echolink friends to see the light and come to Allstar!


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Tue, Mar 27, 2018 at 2:22 PM, "Robert Forest via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> I have the same problem. I connect tried to connect to a friend's Echolink
> node and because the call it says I am connecting from is not in his white
> list I cannot connect to him. He can connect to me just fine and his call
> comes up correct. When I get connections from friends using the Echolink
> app their call signs are not showing up correct in SuperMon
>
> On Tue, Mar 27, 2018 at 1:16 PM, "Sandy via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Hi Doug, and the rest of the Allstar Team.
>>
>>
>>
>> When I connect or receive an Echolink connection the ID is wrong.
>>
>> Not only is the ID wrong it is random. Each connection has a different
>> ID. (call and number)
>>
>> This is using the Android App connecting to Allstar with Echolink active.
>>
>> I connected to myself and then to a friend’s node – same results.
>>
>> When connecting Echolink via Allstar to Allstar, the ID is correct.
>>
>> The Echolink via Allstar to Allstar was just for a test.
>>
>> I almost never use Echolink, but I was told by a friend that they
>> connected to me via Echolink.
>>
>> I examined my connection log and according to it, they did not. The log
>> listed an Echolink ID for the same time period, but was not someone that I
>> recognized.
>>
>>
>>
>> This maybe a problem on Echolink’s side, but thought that I would bring
>> it up.
>>
>>
>>
>> Thanks for the effort and time that is given to Allstar by you guys.
>>
>>
>>
>>
>>
>> 73,
>>
>>
>>
>> Sandy – w9sbe
>>
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>> www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>> <#m_392519631362461363_m_6848030351749374263_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20180327/90f301fa/attachment-0001.html>