Welcome to the IRLP
Crossroads Reflector 9200

All
nodes connected
to Ref9200 (main channel) are expected to be monitored at all times
while connected to
the reflector. Please do not disable inactivity timeouts and leave your
node connected to the reflector for extended periods. Nodes left
connected
to the main channel for 1 day or longer (as reported on the status page) are suspect (we doubt
you are monitoring continuously), thus are subject to
bad opinions and may be blocked. CTCSS or DCS squelch on your repeater
is strongly encouraged, urged and begged for.

Special Note for
Operators
of Simplex NodesMonitoring your node
means
being able to hear what your node RECEIVER is hearing and sending up to
the reflector. You generally cannot do this from your car or La-Z-Boy
mounted
handhelds in the living room. In most cases this means you must stay in
the room with the node receiver so you can hear it. CTCSS or DCS
squelch is mandatory for simplex nodes, but make sure your radio
properly executes the tone squelch, many (like Kenwoods) do not. Check
this with the readinput utility.

Repeater
Hang
Time and IDs

If
your node is
linked to a repeater, there must be NO (as in zero) repeater hangtime
allowed
to pass through to IRLP nor anything resembling a courtesy tone. This
means
set it to zero, not 500ms or even 100ms. If you are using a keyed
CTCSS approach to solving this problem, make sure your tone
encoder/decoder
combination drops as fast as possible. No repeater IDs or
controller
messages are allowed at all, unless they are under a user
transmission.
This requirement is very important on a busy reflector like 9200,
remember
that any IDs or hangtime that leaks through, completely block the
reflector
from other users. If there were thirty nodes connected and each one
ID'd
across the reflector every 10 minutes... well, you get the drift.

Register
your Node

Your node must be
registered
with the status page database to use Reflector 9200. This does not
happen
automatically. If your node shows up on the status page
as Unknown, you may be blocked from all channels of 9200. See the
installation documention "What do you do after the installation" for
registration details.

Pulsecheck
and Readinput

Remember
your
utilities: pulsecheck and readinput are your friends.
Please
check your node with the 'readinput' command before connecting
anywhere,
especially the reflector. Any strange or fluctuating activity must be
fixed
before using your node. Please use the 'pulsecheck' program with your
node
in its final configuration with all links up and operational.

No
Cross-Links
to Other Linking Methods

Cross-links
to
other linking programs (echolink, eQSO, etc.) or even other IRLP
reflectors
are prohibited. If your node is capable of cross linking to
something
else, please disable that capability before connecting to
Ref9200.
If you have a special exception request contact K9DC either on Node
4730
or via e-mail.

Avoid
Local
Traffic

Please
advise
your users to disconnect your node if a local conversation becomes
extended.
Short local greetings are okay while connected, but do not tie up the
reflector
with a 10 minute local QSO.

Pause,
Pause,
Pause

The
three most
important rules for successful reflector contacts. Please leave plenty
of space between transmissions. For many nodes, the only time control
ops
can get in to disconnect is between transmissions. Also remember to key
up and wait for a half second or so before speaking. The exact amount
of
delay varies by node and linking technology, but PTT across IRLP is not
as fast as local carrier squelch simplex.

On
Being Blocked

All
reflectors
have a management function that allows reflector operators
(affectionately
known as 'cops') to block a node that is causing a problem for
connected
nodes. This is a necessary function in order to have a reasonably clean
place for nodes to connect. No one would use it if it was just a place
to collect international intermod, courtesy tones or IDs.

Blocks are NEVER
personal,
nor should they be considered punitive in any way. Every PTT across a
reflector
is logged by node number. If we hear something bad, a glance at the
reflector
console tells the operator exactly what node number the problem is
coming
from. It is then a simple command to block that node. An e-mail message
is automatically sent to the registered contact advising of the block
and
why it was invoked.

Blocked?
What
to Do.

If
your node has
been blocked, please reply to the e-mail you received, advising the
problem
has been corrected and how or what action was taken, if appropriate.
Please
quote the complete message you received in your reply. If the
block
was for some temporary condition, such as local traffic, a reflector
cop
may remove the block without being asked once your node has
disconnected,
but we often forget, so the reply is important.

Operating
Tips
& Bits

Remember
the PAUSE
PAUSE PAUSE procedure described above.

When first
connecting, remember
you may be dropping into a conversation in progress, so wait 30 seconds
or so before transmitting to avoid interrupting a QSO.

Resist the
temptation to break
into a QSO unless invited or the conversation is obviously open. It is
rude to interrupt an eyeball QSO, it is rude on the radio too.
"I-Layer"
propagation always provides a good path, so there is no need to hurry
to
work the "rare one" before the band dies out.

Calling CQ is a
great way
to solicit a contact. Every Ham knows what that means. If you are
specifically
trying to make a contact, be sure to make that fact known in your call,
especially if you are demonstrating IRLP.

All Topics of
conversation
within the realm of "Good Amateur Practice" are allowed. There are no
specifically
prohibited topics, but remember you have an international audience thus
your conversation will be heard worldwide. If you are discussing IRLP
operating
procedures or practices, remember that node access and policies vary
considerably
based upon local requirements.

When disconnecting
from Ref9200,
it is not necessary to announce that fact to everyone connected. In
fact,
a disconnect announcement can be disruptive if you are sneaking in
between
transmissions of a QSO you are otherwise not a part of. Just bleep in
your
code and be gone. If you are fortunate enough to have a full
duplex
control connection, it is actually completely silent if you disconnect
on top of another transmission.

Sub-Channels9201 - 9209

Use of
Reflector
sub-channels is encouraged. You do not need specific permission to use
any of them. Current channel assignments below.

9200
General ragchew - English9201
General ragchew - Spanish9202
General ragchew - Japanese9203
General ragchew - French9204
Open and available9205
Open and available - Nets9206
Open and available - More nets9207
Open and available9208
So California & Mexico - Spanish9209
Open and available - Even more nets