Rules

The rules of this reflector, in plain language

Any kind of system — portable/mobile node, fixed/simplex node, repeater, EchoLink gateway, other reflector — may be connected to this reflector, provided it holds a valid account and is technically sound. (Tests and adjustments are performed before the connection is enabled.) Radio traffic is monitored by several amateur-radio operators who may intervene, if necessary, to block, unblock, disconnect, reconnect, or modify any link to and from this reflector.

Abuses are discouraged and sanctioned, regardless of their origin, of the owner of the system, or of the reflector through which they arrive. Each of the following behaviours is considered abuse:

Because SVX585 is itself a system made up of several interconnected reflectors forming a unified network, we reserve the right to limit traffic to and from this reflector. It is therefore the responsibility of the administrators of the other reflectors to ensure that the radio traffic they bring in complies with the regulations to which amateur-radio operators are subject.

We wish you splendid contacts and responsible, common-sense operation! ;)

Technical rules (node configuration)

These limits are enforced by the reflector and by the node software, not by the operator. They exist so that one badly-configured radio cannot ruin a QSO for everyone else on the network.

Setting Value Where Purpose
SQL_TIMEOUT 180 s svxreflector.conf [GLOBAL] A single transmission longer than 3 minutes is muted automatically.
SQL_TIMEOUT_BLOCKTIME 10 s svxreflector.conf [GLOBAL] After being cut, the client is barred from transmitting again for this long — gives the channel time to clear.
SQL_HANGTIME ≤ 2000 ms each node’s svxlink.conf [Rx*] Tail — squelch hang-time after carrier drop. Keep it short so others can break in cleanly.

More technical rules will be added here as the network evolves.