[arm-allstar] Echolink and Proxies / Relays....

[Jeffrey Lehman, KC8QCH]

Good Morning David,

    Unfortunately, it only seems to happen with the mobile apps. When 
connecting from a PC client (either Windows or Linux) it works fine. I 
also have tried to duplicate it from the PC and have "failed" as well. 
However someone else may have had luck? Not sure what the difference 
would be but yeah.

    Jeff, KC8QCH


On 3/28/2018 07:18, "David McGough via arm-allstar" wrote:
> This morning I tried duplicating this wrong callsign issue, connecting
> from a Win7 client (running the MSWin software rev 2.0.908) and various
> public proxies and I even setup a private proxy to experiment with
> (running the EchoLinkProxy java software, rev 1.2.3) ...No luck, the
> proper callsign showed on the AllStar side every time.
>
> Does anyone know how to duplicate this issue while using the MSWin
> software???? ....This is much more convenient for me than running an app
> for a mobile device.  Thoughts??
>
> 73, David KB4FXC
>
>
> On Tue, 27 Mar 2018, "Charles Powell via arm-allstar" wrote:
>
>> This happens when the Echolink user has a proxy connection, such as
> from an iPhone, iPad, or Android phone.  Dave, KB4FXC, has been working
> on the code.  I pointed this problem out to him and he has it on his
> "to do" list.   I think if you connect from a computer, you will see
> that the information that registers is correct - but not from a phone.
>> 73,
>>
>> Charles - NK8O
>>
>>> On 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> <x-msg://35/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar <http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar>
>>>
>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org <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

-- 
Jeff Lehman, KC8QCH
https://kc8qch.ddns.net
kc8qch at gmail.com

Webmaster
Hamilton Couny ARPSC
https://www.hamcoarpsc.org
hamcoarpsc at gmail.com

AllStar 47374 Node Administrator
World Wide Amateur Radio Guild
https://theguildglobal.org