8000 TAK Server does not update participant callsign and subsequently fails to route messages afterwards · Issue #31 · TAK-Product-Center/Server · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

TAK Server does not update participant callsign and subsequently fails to route messages afterwards #31

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.

Sign up for GitHub

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

Jump to bottom
Open
dnlbaldwin opened this issue Sep 17, 2023 · 0 comments
Open

TAK Server does not update participant callsign and subsequently fails to route messages afterwards #31

dnlbaldwin opened this issue Sep 17, 2023 · 0 comments

Comments

@dnlbaldwin
Copy link

I recently encountered an issue on an exercise where text messaging between individual units was failing. Upon closer inspection it appears as though TAK Server >= 4.7 fails to update participant callsigns after they have connected. Because TAK clients such as WinTAK may route messages by callsign and not UID this means messages addressed to an individual may not be delivered.

The only workaround I have is to disconnect the client and then reconnect with the new callsign.

Steps to reproduce:

  1. Connect TAK client to server
  2. Navigate to the client dashboard on the TAK server (Monitoring -> Client Dashboard)
  3. Observe the callsign for the TAK client
  4. Change the callsign for the TAK client
  5. Observe the callsign has not changed in the client dashboard

Screenshots:

Original connection to TAK server:
image

Changing callsign in TAK client:
image

Observing callsign not changing in Server
image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dnlbaldwin
0