Hi Phil, this happens to me 2 or 3 times in a session. To be specific, all message boxes are always correctly filled with the my own and my qso partners callsigns. When the problem occurs, the message appears in the "rx frequency" window with the qso partners callsign replaced with someone elses. Sometimes this completely prevents calling a particular station as the "wrong" callsign goes out right from the start in message 1. Other times the switch occurs mid qso and usually causes the qso to get stuck in an endless exchange of messages. It is what I described as "callsign hijacking" in my email of 24th January this year. I have found the only reliable way to escape the condition is abandon the qso and stop trying to work that station as the condition recurs if you come back some time later for another try. On one occasion I was able to complete the qso by editing the outgoing message 5 box to swap the angle brackets <> from the affected callsign to the other.
73 Paul VK2/G3NJV Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: t...@gmx.fr Date: 07/02/2019 03:53 (GMT+10:00) To: wsjt devel list <wsjt-devel@lists.sourceforge.net> Subject: [wsjt-devel] Sudden call replacement Hi, I was having QSO with 3G3G. All of a sudden the call 3G3G was replaced by IV3ONZ on the same frequency. I tried to restore the proper call sign by clicking on the call sign in the Rx Frequency box. No ways! Strangely, just after I did it, <3G3G> ZS1/F5FDV RRR appeared in the Tx4 box but it was <IV3ONZ> ZS1/F5FDV RRR that was displayed in the Rx Frequency box. Screen copy attached. 73 Phil F5FDV
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
