IRLP provides a means to link radio repeaters together anywhere there is high speed internet connection (128 kbs or more) available. The IRLP uses Voice-Over-IP software and the power of the Internet to link repeaters world wide. The system uses its own custom interface board and Linux based software suite. IRLP makes interfacing a  radio system to the world simple and cost effective.

The IRLP runs a large network of dedicated servers and nodes to offer the very best in voice communications. The IRLP Amateur Radio network consists of hundreds of nodes (repeater plus an IRLP computer) across the world, linking them all with a full dynamic range 32 bit audio. Node connections are made with DTMF on a HT or other radio. The IRLP System Designer is David Cameron VE7LTD.  

1)  Node-to-Node  Connections

Direct one node-to-another node or one node-to-many via a connection to a Reflector. Direct connect Node-to-Node is just like it sounds where node "A" connects direct with node "B".  In this mode the two nodes (repeaters) are interconnected and no other IRLP connections are possible.  While "A" and "B" are connected, anyone attempting to connect with either node “A” or “B” will be told by a wave file recording that: "The node you are calling is currently connected to call sign or node number".

2) Node-to-Reflector Connections

The IRLP system has a hand full of servers called "reflectors" that allow for many nodes to connect together for nets, special activities or HF style QSOs. When a node is connected to a reflector it hears all the audio streams that are sent between the nodes that are connected to the reflector.  Nodes will come and go freely to the reflectors, however, some node owners will leave their nodes connected to a reflector as a gateway for the local area.

Node 3210 was installed by W7AOR March 22, 2001 as the first node in Las Vegas. Node 3290 followed on September 15, 2001 and the Western Reflector 925 was installed December 12, 2001. Many other NARRI nodes have followed.

NARRI IRLP NODES 

Node  3641 447.000 MHz  (-) PL 100.0 Hz. Gateway to Western Reflector (Open Access).

Node 3260 147.000 (+) PL 123  Secondary Gateway to Western Reflector.  

Node 3290 145.370  (-) PL 123 Coverage along I-15 from Jean, NV to Mesquite and East and West on U.S. 95. 

Node 3194 447.725  (-) PL 107.2  Used to monitor Ref  9258 that is used as a NV interconnect and for NV Section ARRL nets. 

Node 3396 146.640 (-) PL 123 Tonopah, NV 

Node 3705  449.750 (-)   PL 123  Mesquite, NV 

Node 3729 146.460 Simplex PL 100 Pahrump, NV. (Down)

Node 3082 441.650 (+) PL 123  Reno-Sparks, NV

All Star System 

Node 2030 on 449.725 (-) PL 94.8. Using a Linux based computer system running the open-source Asterisk PBX telephone switch platform along with the "app_rpt" repeater/remote base controller/linking software module.  See www.allstarlink.org. 

ANNUAL  IRLP CONFERENCE

NARRI sponsors the Annual IRLP Conference  that is held in Las Vegas in the Spring just before the NAB Convention. Click here for information

THE WESTERN REFLECTOR

The Western Reflector is a IRLP Reflector with ten channels ( 9250 through 9259). It is located in a co-location facility in Las Vegas with very high bandwidth, much more than a T-1. It provides for multi node connections on each channel as opposed to a single node-to-node connection. The reflector allows for the linking of numerous node together for nets, multi node QSOs, and other special uses. The Las Vegas 447.000 (-) PL 100 repeater is normally connected to the Western Reflector Channel 0 (the main channel) as the local open Las Vegas area gateway for anyone wanting to talk or listen. The reflector is available 24 hours a day, seven days per week. 

The Alaska Reflector, used as an intertie for many Alaska repeaters, is linked to the Western Reflector. That means all the nodes on the Alaska Reflector and Western Reflector are tied together when you see the "Alaska Gateway" connected to the Western Reflector. Nodes connecting to either reflector will be heard on both reflectors.

IRLP Reflector Channel (9254) is linked to Echo link Conference Server *HI-GATE* 367564 full time to allow groups of IRLP and Echo link nodes to conference with each other.  This is useful for Emergency Service Nets and, other wise, for fun QSOs. 

Channel 5 - 9255  Special Activities and QSO's.

 This channel is used by American Red Cross, the Disaster Communicators Forum (DCF), and RACES organization residing outside Nevada (Nevada uses 9258 and *NV-GATE*.)  The DCF and ARC uses 9257 and Echo link  Conference Server *DCF-ARC*  336037 to link communicators together before, during, and after disasters. This is to augment local communications with communicators outside the     effected areas.

In the past various individuals and Amateur Radio organizations have come forth to provide emergency response communications where it was needed. Those affected by a disaster deeply appreciate the dedication and effectiveness of ham radio operators. Recent disasters have reaffirmed the need for ham radio operators to augment governmental operations. 

See http://groups.yahoo.com/group/DISASTER_COMMUNICATORS_FORUM/ This forum is for those who recognize the need to share information. including lessons learned, discuss preparedness planning and disaster relief coordination. It is intended that all organizations involved in preparedness and response, including, but not limited to ARC, ARES, RACES, FEMA, Sky warn, Salvation Army, ERC, and Homeland Security will participate in the Disaster Communicators Forum (DCF) for the betterment of the whole.

Click to join DISASTER_COMMUNICATORS_FORUM

See http://groups.yahoo.com/group/VoIP_American_Red_Cross_Communicators_Net/ for net information and group communications.

Channel 8 - 9258 Calls and Nets 

      Ref 9258 (Channel 8) is linked to Echo link Conference Server NV-GATE  (152566) and thus allows IRLP nodes on Channel 8 to talk to Echo link nodes on NV-GATE.  The NV Section ARRL    ARES-Skywarn  uses this channel for nets. 

Nevada ARES/Skywarn Net   Every Wednesday at 7 PM Pacific Time. This net is for all parties interested in Skywarn activities. Other ARES business may follow Skywarn. All check-ins provide a weather report for practice and are able to check equipment. 

Nevada State ARES/RACES Net   Every Thrusday at 7 PM Pacific time. For the leasdership and all intersted parties.

Channel 9 - 9259    Reserved for ERC-ECS Nets. Not open for QSOs.

BLOCKING NODES FROM THE WESTERN REFLECTOR

Please contact Kent W7AOR by e-mail, w7aor@narri.org,  if you want to add a net or any other significant special events so schedules may be published. Your activity will be assigned to a non-zero channel so that we can keep 925(0) available for calling and general rag chew. 

John KB2ERJ  kb2erj@kb2erj.com ;  Ernie W6CAP, w6kap@arrl.net;   Carter, KH6FV, kh6fv@hawaii.rr.com;  Jack , KH6DQ, tsujimur@hawaii.edu; David, N7EIZ, d@n7eiz.com,  and Kent, W7AOR,  w7aor@narri.org . The Western Reflector Owner W7AOR has given the above indicated Reflector Cops the ability to block and unblock nodes as the means to remove a node causing a problem.  It is important to keep the channel free of a problem that may degrade reflector performance.

The most common reasons for a lockout are:

Node is sending pulses to the reflector
Node squelch is opening without valid signal (intermod)
Communication is one-way
Local QSO is in progress without any breaks between transmissions.
Courtesy Tone is being heard over reflector
Hangtime is being sent to reflector
Automated repeater ID being sent to reflector
Emergency net - Node not in affected area
Unauthorized links to the IRLP node
Local user connect interfering with a net in progress
Prolonged connect to the Reflector without reason or permission
Music or other illegal broadcasting
Profane or other un-acceptable language
QRM: Intentional, malicious interference from someone using your node

If a node owner is locked out, he(she) receives an e-mail that is automatically generated by the lock out software and is asked to: 1)  provide the immediate fix and the long term corrective action (training, a PL or whatever) that will prevent future occurrences of the problem, and then to 2) e-mail the individual who applied the lock out with a copy to problems@irlp.net and state the immediate and long term corrective action. The node will be un blocked if the response is satisfactory. 

WESTERN REFLECTOR OPERATIONS POLICIES

These operating procedures are provided help assure your enjoyment of the Western Reflector. Please pause for three seconds before talking upon connecting to any Western Reflector channel to allow the audio streams to reach your node, and to make sure a QSO is not in progress, before you start talking. Pause between transmissions to allow others into QSOs and key up for a long second so others will have chance to hear all other. Quick keying is not the sign of a good reflector user.
 
Click Here to See Western Reflector Rules for Node Owners and Users

IRLP OPERATING GUIDELINES

Listen to others use the IRLP to get the hang of it. Here is a few DO's and DON'Ts:

DO pause between transmissions to let other in or others to enter DTMF command.

DO hold your microphone PTT for one or more seconds before talking to allow all systems time to connect.       

DO NOT try to make or break connections unless you are an authorized control operator.Those who control must  identify themselves as controlling before sending DTMF command tones and return the node to the connection state you found it in, i.e., idle or connected to a node or reflector.  Always ask if someone is using the connection before you change it.
       
DO NOT rag chew locally on a reflector or on a node connection. When the IRLP system is busy keep QSOs to 5 minutes or less.
        
DO pause for at least three to five seconds before talking after the node connects to a reflector to make sure you will not talk over a QSO in progress.

Don't use 11 meter lingo when talking on the system. Speak normally.  Some examples:

    Don't say, "(call sign) trying."  

    Don’t say, "The personal here is _ _ _" (use name).

    Don’t say, "Thanks for the comeback" (use thanks for the call/answer).

    Don’t say, "I’ve destinated" (use I’ve arrived).

    Don’t repeatedly say, "I hear that" or "roger that" or "QSL" in response to every transmission/comment.

    Don’t say your, or the other person’s, call sign every transmission (only your call is required once every 10 minutes).

    Don’t just kerchunk the repeater without saying your call (at least on the second kerchunk).

    Don’t shout into your microphone.

    Don’t give one-word answers or comments.

    Don’t break in on an ongoing conversation unless you know who all is in it, and you have something meaningful to contribute.

When in a QSO with more than two people involved, turn it over to someone by name (go ahead Jim).

When you sign clear, turn it over to someone by name or call (don’t just sign clear because no one knows who should pick up).

Use a mike hanger in your vehicle to avoid sitting on the microphone and inadvertently keying up the system with people all over listening to your conversation.

DO NOT TRY TO CONTROL IF NOT AUTHORIZED TO DO SO OR TALK ABOUT THE CONTROL CODES OR HOW TO CONTROL. That is the business of the node or reflector owner. He will tell who he wants to know. Always ask an owner if you can use his equipment. It should be noted that not all nodes use the same control commands - ask the owner. It is rude to try to control a node if you have not asked first. Just like some repeaters, some nodes are private. More and more node owners are installing passwords to discourage button pushers from trying to operate their node equipment. It is always safe to ask for a control operator when you are a visitor to a node. Vistors to Las Vegas should e-mail w7aor@narri.org to inform NARRI of your desire to operate its nodes and obtain permission and necessary information. Any reasonable request will be honored. Many visiting node owners and users have used NARRI nodes to talk home.

Return to Main Page