<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.simtx.net/index.php?action=history&amp;feed=atom&amp;title=Sessions_and_Queueing</id>
	<title>Sessions and Queueing - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.simtx.net/index.php?action=history&amp;feed=atom&amp;title=Sessions_and_Queueing"/>
	<link rel="alternate" type="text/html" href="https://wiki.simtx.net/index.php?title=Sessions_and_Queueing&amp;action=history"/>
	<updated>2026-07-29T07:30:10Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://wiki.simtx.net/index.php?title=Sessions_and_Queueing&amp;diff=8&amp;oldid=prev</id>
		<title>Clanker: Create sessions page</title>
		<link rel="alternate" type="text/html" href="https://wiki.simtx.net/index.php?title=Sessions_and_Queueing&amp;diff=8&amp;oldid=prev"/>
		<updated>2026-07-05T08:43:08Z</updated>

		<summary type="html">&lt;p&gt;Create sessions page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;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.&lt;br /&gt;
&lt;br /&gt;
== Session lifecycle ==&lt;br /&gt;
A session created with &amp;#039;&amp;#039;&amp;#039;Start TX&amp;#039;&amp;#039;&amp;#039; passes through these states:&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Starting&amp;#039;&amp;#039;&amp;#039;: the client is contacting the server.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Queued&amp;#039;&amp;#039;&amp;#039;: the server is full for now; the list shows how many sessions are ahead. The session starts automatically when a slot frees up.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Running&amp;#039;&amp;#039;&amp;#039;: the transmission is on the air and telemetry updates the Radio Deck.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Stopping / Stopped&amp;#039;&amp;#039;&amp;#039;: the operator ended the session.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Finished&amp;#039;&amp;#039;&amp;#039;: the source completed (for example the audio file ended).&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Failed&amp;#039;&amp;#039;&amp;#039;: the server rejected the session; the reason is shown.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Kicked&amp;#039;&amp;#039;&amp;#039;: the server operator ended the session remotely; a dialog shows the reason.&lt;br /&gt;
&lt;br /&gt;
== Server limits ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Multiple sessions ==&lt;br /&gt;
The client can run several sessions at once (subject to server limits). The &amp;#039;&amp;#039;&amp;#039;Active Sessions&amp;#039;&amp;#039;&amp;#039; list shows each with its own state, and &amp;#039;&amp;#039;&amp;#039;Stop Selected&amp;#039;&amp;#039;&amp;#039; / &amp;#039;&amp;#039;&amp;#039;Stop All&amp;#039;&amp;#039;&amp;#039; control them individually or together.&lt;br /&gt;
&lt;br /&gt;
== Disconnects ==&lt;br /&gt;
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 &amp;quot;No reason given&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
[[Category:SimTX]]&lt;/div&gt;</summary>
		<author><name>Clanker</name></author>
	</entry>
</feed>