QSL
Confirm a chaser’s contact. When the OTA bot relays a DE message to you,
answer with QSL and that chaser’s callsign. The QSO is logged, scored, and
relayed back to them.
Send the QSL from the station running your op.
The other spelling
@W1XYZ-5 QSL thx for the contact 73 confirms exactly the same contact. Both
spellings are permanent, so use whichever you remember.
What neither can do without is the callsign. A host with a pileup can have several chasers waiting at once, so a QSL carrying nothing but a message cannot say who was worked, and the bot asks for the call rather than guessing:
The word matters as much as the callsign. Name a chaser without it and nothing is confirmed, so the bot says the contact is still waiting rather than guessing that you meant to log it:
See exchange messages for the whole QSO, step by step.
Reference
QSL <callsign> [message...] | @<callsign> QSL [message...]
Confirm a chaser's contact and log the QSO.
- callsign
- The chaser you are confirming. Any SSID form of their callsign works.
- message
- Free text relayed back to the chaser with the QSL. optional
Replies
qsl_relayDE {station_call} QSL {message}
Hints
- a QSL not sent via RF
You must transmit via RF to confirm a QSOlimited to 1 per 24 hours, then silent- a QSL with no op on the air
QSL needs an op on the air. Send HOST to start one.limited to 1 per 24 hours, then silent- a QSL from a different SSID than the op's
Your op is run by {station_call}. Send QSL from it.limited to 1 per 24 hours, then silent- a QSL with no relayed chase by that operator
No chase from {base_call} to confirmlimited to 1 per 24 hours, then silent- a host naming a chaser who is waiting on their QSL, with no keyword in the message
{base_call} is waiting on your QSL. Send QSL {base_call}.limited to 3 per 15 minutes and 5 per 24 hours, then silent- a QSL with no callsign
QSL needs a callsign. Send QSL callsign to confirmlimited to 1 per 24 hours, then silent