Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong echolink number Node in status - EL Android #49

Open
sp2ong opened this issue Jan 21, 2020 · 2 comments
Open

Wrong echolink number Node in status - EL Android #49

sp2ong opened this issue Jan 21, 2020 · 2 comments
Labels
bug pinned Pinned - Keeps stale issues from being auto closed

Comments

@sp2ong
Copy link

sp2ong commented Jan 21, 2020

When we use echolink Android application to connect echolink node running on Allstarlink always in status node ASL display wrong number echolink node connected to ASL. For example, my echolink node is 926515 and when I connect to my ASL echolink node in status "Node currently connected to us" is showed number 3437911. When I look at http://echolink.org/logins.jsp I found that echolink number node 437911 belongs to KO4AVA. When I disconnect and connect again to ASL the my number EL was changed to another 3876316 and when I check on EL status page I found that the number belongs to DV2EVE.

But when I use the software PC version echolink the number my echolink node in status ASL is correct 3926515.

Does it look like bug ASL which not properly get information about connected number EL node with the station who uses EL Android application?

@sp2ong
Copy link
Author

sp2ong commented Jan 21, 2020

Ok, short discussion about this issue:
https://dvswitch.groups.io/g/allstarlink/topic/69951556#1011

@KG7QIN KG7QIN added the bug label Mar 28, 2020
@KG7QIN KG7QIN added the pinned Pinned - Keeps stale issues from being auto closed label Apr 30, 2020
@sp2ong
Copy link
Author

sp2ong commented Jul 12, 2020

Where is in ASL part of code (chan_echolink.c) which delivers node number in the status ASL ? or it may be part of code where is generate status node get wrong number node?

I have test with dump echolink DB in ASL (*echolink dbdump) and always in database echolink number node, callsign and IP address are correct. IP address is change depend on select options in Android application in NETWORK "DIRECT" or "PROXY".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug pinned Pinned - Keeps stale issues from being auto closed
Projects
None yet
Development

No branches or pull requests

2 participants