Sessions and Queueing

Every transmission is a session between the transmitter client and the server. The server decides whether a new session is admitted immediately, queued or rejected.

Session lifecycle

A session created with Start TX passes through these states:

• Starting: the client is contacting the server.
• Queued: the server is full for now; the list shows how many sessions are ahead. The session starts automatically when a slot frees up.
• Running: the transmission is on the air and telemetry updates the Radio Deck.
• Stopping / Stopped: the operator ended the session.
• Finished: the source completed (for example the audio file ended).
• Failed: the server rejected the session; the reason is shown.
• Kicked: the server operator ended the session remotely; a dialog shows the reason.

Server limits

Servers can limit the total number of sessions, the number of transmit sessions, and the number of sessions per user. The user bucket is the callsign (case-insensitive) or, depending on server policy, the client address. When a transmit limit is reached new sessions are queued in order; when a policy forbids the session outright it is rejected with a reason.

Multiple sessions

The client can run several sessions at once (subject to server limits). The Active Sessions list shows each with its own state, and Stop Selected / Stop All control them individually or together.

Disconnects

If the control connection drops, the client reconnects automatically every 3 seconds. Sessions that were kicked or rejected show the server-supplied reason; an empty reason is displayed as "No reason given".