DEFAULT
     
  Home Page  
      
 
 

Navigation Menu
 
 
 

Repeater: IRLP & EchoLink

 

Node Numbers

The VE3MIS repeater operates as the following node numbers;

IRLP Node 2998

EchoLink Node 404792 (VE3MIS-R)

IRLP node status on Twitter

To view a Twitter posting of IRLP/Echolink connect and idle events, click on the following link http://twitter.com/irlp2998/.

Important notes

Please let John VA3XJL, or Michael, VE3TKI know if there are any problems with the IRLP/EchoIRLP node. A single computer provides access to both IRLP and EchoLink, but does not link the two methods.

Please note that the #67 and #76 access commands are no longer required.  All you have to do is enter the node number by itself.

The 73 command still is retained to hang up. Please do so after use.

Operation notes

Assuming the repeater is clear; identify yourself and state your intention to use the IRLP link. 

Example: "VE3XYZ for the Link", and then un-key. Then enter the node number of the node you wish to connect to and release your PTT. For EchoLink, be sure to prefix the EchoLink node number with #. Our repeater will respond with the courtesy tone as it waits for the connection to be authenticated. This can take a few seconds of dead air...so don't be concerned. When the connection is confirmed, the voice ID of the destination node will be transmitted back to you and the VE3MIS node voice ID will be sent to the other repeater. Once connected and after hearing the confirming voice ID, wait at least 15 seconds before transmitting as.......

1. The repeater may be in use, and your entry may have occurred between transmissions.

2. 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.

3. Their computer may be slower, and hence take longer to process the connection than yours.

Press and hold the microphone PTT for at least one or two seconds and then announce your presence and your intention, e.g., that you are calling someone specifically or just looking for a QSO with another ham in that city. Calling CQ on a quiet node is acceptable practice.

If no response is heard, announce your call and your intent to drop the link and then key in the OFF code, which is universally 73 for both IRLP and EchoLink.

Once the node you are connected to has announced that it has successfully disconnected, you may enter another node number and repeat the above process if you wish.

Note: Some nodes are configured so that you cannot connect to them if that repeater is active. In this case, you will receive the message "The node you are calling is being used locally". If you receive this message, wait 5 or 10 minutes and then try again.

Warning: If you stay connected to a node and there is no activity on our repeater for 4 minutes, the connection will time out and automatically disconnect with a voice ID disconnect message on both nodes.

Node Codes 

Most nodes are open for anyone to connect to and their node address code can be found at http://status.irlp.net/statuspage.html and http://www.echolink.org/.

Some node operators choose to add a prefix to their node. Also some nodes require membership. So the easiest way to get current codes is to contact the node operator or custodian. To email a node owner go to http://status.irlp.net, find the node you wish to contact and click on the node number. At the bottom of the node info is a link to create an email message.

Reflector Use

The connection process to a reflector is identical to that of an individual node. The only difference is operational guidelines When you hear the confirmation ID from the reflector, always WAIT at least 15 seconds before transmitting as you are most likely now be connected with many repeaters and a QSO could be in progress. If after 15 seconds you hear nothing, identify yourself and indicate you are listening to the Reflector from "City and, Province./State, Country". With the world-wide IRLP activity, your local repeater now has world-wide coverage thus the suggestion to better detail your QTH.

Don't be in a hurry to hear someone come back to you. You may have to do a bid of pleading from time-to-time to dislodge someone from whatever they are currently involved with.

By default, connections to the reflectors now time out with no activity, however many node owners set this period to a long period. So it is not unusual for repeaters with minimal traffic to stay connected to the Reflector for extended periods of time. When or if the node times out from a Reflector connection, a standard time-out greeting will precede the time-out saying, "Activity time out ... Reflector xxxx, link off".

If you hear or wish to engage in a prolonged rag-chew on your local repeater such as long discussion of a local nature, for out of courtesy to other node listeners, please drop the reflector and close the IRLP gateway. When disconnecting from a reflector, the off code is again universally 73. However, by the nature of the communication between nodes and reflectors, there needs to be a moment of quiet for the system to “hear” the disconnect tone. On a busy reflector, it is probably wise to announce that you intend to disconnect. Prior to doing so, giving others on the reflector a heads up will prompt them to pause so you can disconnect more easily.

Good luck and enjoy your time on IRLP.

IRLP Error Messages

From time-to-time you may receive error messages when attempting to connect with a node or reflector. The most common ones are:

"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. 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.

"The node you are calling is currently connected to callsign."
If the node you a calling is already connected to another node or reflector, you will hear this message.

"The node you are calling is being used locally."
If the node you are calling has local activity on the repeater or frequency, you will hear this message. Try calling again in a minute or so.

"<busy signal>"
The node you are calling is not connected to another node or reflector; however, the repeater or frequency is in use locally or the IRLP node hardware is being used for some other function (e.g. Voice-mail, playing Newsline, etc.).