Possible bug preventing comms (Group & DMs) from ATAK/WinTAK clients back through RabbitMQ to stand-alone Meshtastic clients.

[ki6uve]

Friendly reminder to check code for possible bug that would prevent messages from progressing from ATAK or WinTAK clients, back through OTS / RabbitMQ to reach stand-alone Meshtastic clients that are not connected to OTS directly via the Meshtastic plugin in ATAK. AKA EUDs that are running Meshtastic app only, not ATAK.

[ki6uve]

This issue was resolved by correcting user configuration settings to assure that Meshtastic channel name was identical in both OTS web UI's Meshtastic tab and the OTS-associated Meshtastic gateway node's channel settings. This issue can be closed.