The most important guideline to remember is to leave a 2 second pause after pressing the PTT button as well as between transmissions.  Just as with any linking system, the IRLP is subject to some audio delays. These delays are caused by the amount of time digital information can take to be compressed and travel across the internet between the nodes and PL decoder boards on all of the participating repeaters. So the first thing to remember is to slow down and be patient. When in a conversation, remember to leave a second of dead air before speaking. Due to the timing issues with the system some nodes may require a longer period.  By leaving a pause between transmissions you 

• allow users on other nodes a chance to check in
• allow other nodes time to send touch-tone commands to drop their node

Here is a quick summary of DO'S and DON'TS: 

• DO pause between transmissions to allow for control codes and to let others in.
• DO hold your microphone PTT for about 2 seconds before talking to allow all systems time to rise.
• DO NOT rag-chew on your local repeater while connected to the Reflector.
• DO pause for 15 seconds after connecting to a Reflector to see if other stations are already talking.
• DO identify before sending DTMF command tones (and make sure your signal is good enough that you can reliably bring down any connection that you initiate).
• DO NOT discuss up/down codes on the air -- please refer people who want information to a control op.
• Remember: anything you do on an IRLP reflector can be heard on the participating linked repeaters around the world.

NOTE: If the your repeater or the destination repeater is already connected, a message will play to tell you so. 

After entering codes to bring up a connection you should hear a carrier as the repeater waits for the connection to be established.  This can take a few seconds of dead-air so don't be concerned. 

2. After hearing the voice ID confirming the connection is established, be sure to listen at 
least  15 seconds as: 

• A QSO could already be in progress.
• The voice ID of your node is longer than the voice ID of their node, and the connection is not made until the ID is fully played.
• Their computer may be slower, and hence take longer to process the connection than yours.

3. When you hear the confirmation ID always WAIT at least 15 seconds before transmitting as a QSO could be in progress.  Press and hold the microphone PTT and wait for a second before announcing your presence.  Are you calling someone specifically or just looking for a QSO with another ham in that city? 

4. If no response is heard, announce your call and your intent to drop the link and then touch tone in the OFF code.  It is not a good idea to transmit touch-tone commands without first giving your call-sign.  Not only is this courteous it may be a regulatory issue in the country to which you connected. 

TIMEOUT: Should you stay connected node-to-node and there is no activity for 5 minutes, the connection will time out and automatically disconnect providing voice IDs to both nodes that the other node is disconnecting.

1. As above, listen to the local machine and then announce your intention to connect to another node before keying the link on command. 

2. After hearing the voice ID confirming the connection is established, be sure to listen at least 15 seconds as: 

• You are most likely now connected with many repeaters and a QSO could be in progress.
• The voice ID of your node is longer than the voice ID of their node, and the connection is not made until the ID is fully played.
• Their computer may be slower, and hence take longer to process the connection than yours.

3. If after 15 seconds you hear nothing, identify yourself and indicate you are listening to the Reflector from "City and State". With the world-wide IRLP activity the repeater now has world wide coverage thus the suggestion to better detail your QTH. 

4. Don't be in a hurry to hear someone come back to you.  You may have to do a bit of pleading from time to time to un-lodge someone from whatever they are currently doing. It is not unusual for repeaters with minimal traffic to stay connected to the Reflector for extended periods of time. 

Out of courtesy to others who may want to use the reflector, please do not engage in a prolonged rag-chew (move ragchews to node-to-node connections). 

Participating in Reflector Roundtables

Roundtables are conversations involving more than 2 parties.  Unlike a net a roundtable requires some organization to keep the conversation thread passing in an orderly fashion from party to party.   Do not become intimidated if a group grows and, if mobile, do not be overly concerned if you are unable to remember all or any callsigns.  Just try and remember the call and or name of the next station that you pass it to.  If you are listening and wish to break into a conversation, let a cycle go by so you know the participating station are then announce your callsign during one of the "pauses". You should be recognized and then when finished with your transmission be sure to specify who you are turning it over to.  If you do not specify a station to pick up the connection chaos will result as 2 or more stations may try to talk at once.
 

• "The node you are calling is not responding, please try again later" -- This is caused by a loss of internet connectivity to one end of the call attempt.
• "BEEP Error- The call attempt has timed out, the connection has been lost" -- This error occurs when a node is OFF-LINE or there is a software error.  Some nodes such as in the UK use dial-up connections and then, only for short periods.  Also there may be temporary net or node problems.
• "The Connection Has Been Lost" -- If the internet connection drops, this error message will be heard. 

• Do not connect your local node to the net during net times unless someone is acting as a local net controller.
• Do not make calls directly to other stations during the net.
• Above all NO local conversations during the net while connected to the reflector.
• Do not attempt a call unless your local net controller has you as a pre check-in.
• Disconnect our node if any local interference is present.
• Keep your check-in short and to the point. Remember that several hundred others may be waiting for a chance to check-in as well.

The IRLP International net is a way for all hams in all areas of the world to be hear and be heard. Let's keep the net viable with proper operation.  Check the Official IRLP Net web page for details on schedules.

User Access

• The 146.775 repeater (node 4260) is dedicated to continuous IRLP reflector connections, so any ham can tune in almost anytime and work DX.  You are welcome to jump in and join a conversation or start one yourself. If you don't hear the courtesy tone on 146.775, the node has been disconnected overnight while unattended or for maintenance or service upgrades.  Please do not kerchunk or key up without speaking -- this causes major problems with all of the other nodes connected to the reflector. Because the system has global coverage, please avoid local ragchews on 146.775.  Remember: anything you do on an IRLP reflector can be heard on the participating linked repeaters around the world.

• The 441.725 repeater (Node 4270) is linked to other KD4RAA-K4JDR Repeater Group repeaters -- 444.150, 444.325, 444.375, 444.550, 444.775, 444.875, 444.925 and others.  This node will be available to KD4RAA Repeater Group supporters for bringing up or receiving point-to-point contacts from around the world. Support Policy and Support Membership Donations information is on the KD4RAA Repeater Group Donation Policy Page.  Further questions about support of the project can be directed to Danny Musten KD4RAA or Ron Casey K4JDR  (additional contact information is on the Control Ops page).  Please use our IRLP and Support Member registration form to request access to the IRLP codes.  Jim Price WW4M has been designated as our node administrator for the Raleigh, NC project nodes. Please direct all policy questions and control code queries to Jim Price WW4M. We encourage and appreciate your support of this new technology in amateur radio repeater linking.

• The 444.675 repeater is host for KD4RAA's personal IRLP Node 5270, that is used for testing other nodes in the system and is available for general use in Raleigh as a part of the member support participation.  You might just find Mark Gibson N4MQU parked on this repeater and can be helpful if you need access.

• Nodes 7480 and 7140 are on the N4JDW 145.170 and 442.075 repeaters in Wilmington. Contact David Wicker N4JDW for user access information when traveling to the Coast.

• The 444.575 repeater in Kinston, Node 4290 is also a part of the KD4RAA Repeater Group and sports its own IRLP node.  For details on this repeater and use of this IRLP node contact Doug Blizzard N4HAJ.
   

• Node 7410 is active on the KB4PQA 442.250 repeater in Greenville, South Carolina. You may want to give Terry Lambert KB4PQA a shout while in that area.
  
  Here is a Complete list of sponsored IRLP nodes and UHF links that will be helpful as a reference.  Connect status of all IRLP nodes in the network -status.irlp.net .  A global map of IRLP nodes is available here .