IRLP Operating Procedures

Written by Andrew Koenig

This may seem like a lot too read, but you need to know the proper operating procedures for IRLP.

IRLP Node Directions

Here are some directions from the local IRLP Node owner Steve N5ZUA. Please read all of this before using my node or any other node.I have some information on how it works in the FAQs section.

INSTRUCTIONS

#1 PAUSE...
Pause for two full seconds when you key up. PL has to be decoded in the
repeater and link radio on this end (about a half second each) and has to be
encoded on the other end (again, about a half second each) so that's 2 full
seconds. Press the PTT and count to yourself one thousand one, one
thousand two, then begin speaking. In this manner, you will not cut yourself
off at the beginning of every transmission, especially if you are answering
a "yes" or "no" type of question and then unkeying.

#2 PAUSE...AGAIN
Pause for 2 seconds BETWEEN transmissions. This means after the courtesy
beep sounds and tail of the repeater drops completely out, you can key up
and reply. This allows breaking stations to get in and also allows other
nodes who want to disconnect to get in between transmissions to do so (you
will hear a half second of DTMF indicating that they are disconnecting).

If you quick key and don't pause, the reflector control stations can, and
probably will, lock this node out to where it cannot connect, and usually do
so without any warning. If this happens, then I have to send an email
explaining what happened and request to be re-instated, so please be darn
sure you pause. If you notice someone else is not pausing, then go the
extra mile and leave a little extra space in there, just to be sure.

#3 CONNECT / DISCONNECT
Using your radio's DTMF keypad (you knew you would find a use for
this someday!) dial 73 to disconnect. This is the universal disconnect
code worldwide. To connect, just dial the 4 digit node number or 4 digit
reflector number. For Echolink nodes, dial zero + node number.

Please do not give connect and disconnect codes out over the air, as it is
against Reflector rules. Instead, have anyone interested contact me via
email, so I can send them this file. The individual node list is available
at http://status.irlp.net/statuspage.html and the node / reflector / and
connected nodes summary is available at http://status.irlp.net/ For
Echolink, have a look at http://www.echolink.org/logins.jsp

#4 REFLECTORS
An IRLP reflector (or Echolink Conference Server) is just like an email
reflector, it takes your voice and broadcasts it to all connected nodes.
If you call direct to another IRLP node, no other nodes can join in.
However, if you plan an extended QSO, a node to node connection is
better than tying up a reflector for a long time.

The most popular reflector for random contacts is 9250. At 0100 local
daily, the node is connected to 9453 for the hour long Insomniac Net
from California, if you like trivia and are a night owl. After the regular
check in list is called, they will call for guests from the IRLP and you
can check in then if you like.

While in QSO on a reflector, if there are several other stations in QSO,
then please state to whom you are turning it over to when you unkey.
Saying things like, "back to the Alberta station" if you do not remember
their call sign are perfectly acceptable. The worst thing you can do is not say
anything at all and unkey. Then, everyone is scratching their heads
wondering whose turn it is next. This sets everyone else up to double,
which cannot happen as only one node can capture a reflector at a time.
Pass it around fairly so that everyone has a turn, and nobody is left out.

If your reflector QSO exceeds five minutes, then consider asking the other
station to disconnect from the reflector and call you on a node to node to
connection, in order to free up the reflector.

Please keep in mind that there are stations from around the world on the
reflector. As such, other countries may have more restrictive rules about
things such as third party traffic, etc... so take this in to account.

Reflectors require that the only thing that passes to them is voice audio.
This means no repeater tails, courtesy beeps, or identifiers, only voice
audio with no delays. This node and repeater work together as a team,
and have been carefully engineered to be in compliance with the strict
reflector rules of IRLP. While you will hear the courtesy beep, repeater
tail, and cw identifier locally, they are not passed over the Internet.

#5 OPERATING PRACTICES
If you connect somewhere, please don't wander off and leave it connected. Go
ahead and disconnect. Since this is an open node, the person who controls it
is responsible for the connection (control operator). So please disconnect
when you are done. Once connected, please be sure to identify. If you just
connect without identifying, this node will most likely be blocked from
being able to connect to that node in the future. Once connected, identify.

Please do not attempt the use of crossband equipment, as it will
add a detectable tail to your audio and the node will be locked out.

Please do not "kerchunk" the repeater. When you do, you kerchunk all of
the connected repeaters around the world. The node may be disconnected
and disabled if this is detected. However, when other nodes connect to a
reflector, it will cause a kerchunk to this node. This is normal operation.

#6 IDENTIFY
The FCC requires you (not optional) to identify. The question is WHEN to
do so. If you know that the node is connected to a reflector, and you want to
disconnect it, then identify AFTER you disconnect and hear the message
play confirming the disconnect. Reflector owners prefer you do it this way
with the numerous connects and disconnects that go on so they don't hear
callsigns all day long. For example, you would key up and dial 73 to make
sure it is disconnected, wait for the message if it was, then identify with
your callsign. If you get no message after you dial 73 then go ahead and
identify as it is not connected. You are not required to say,
"controlling IRLP" but if you do then other local stations won't mistake you
as looking for a QSO with them.

#7 PROBLEMS
Have Fun! If you do experience a problem, or the node is locked out while
you are on, please email me right away and let me know as much as you can.
Also, if a reflector monitor calls for a control operator on IRLP node 3018 or
Echolink node 263961, then please answer the call. The reflector monitoring
software they use is foolproof and will point to this node if there is a problem
originating from here. Failure to do so will result in the node being locked out
for no control operator present, if nothing else. When you respond to such a
call, listen closely to what is being asked or told. Offer to voluntarily
disconnect if given the chance and informed there is a problem on this node.
Be cooperative with the reflector monitors to minimize the potential for being
locked out.

< Prev