Monitoring Requirements

All nodes connected to Ref9100 (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.  CTCSS or DCS squelch on your repeater is strongly encouraged, urged and begged.

Special Note for Operators of Simplex Nodes

Monitoring your node means being able to hear what your node RECEIVER is hearing and sending out-bound 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 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 hang-time 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 solve 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 9100, also remember that if any IDs or hang-times leak through, they completely block the reflector from other users.  If there were fifty 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 9100.  This does not happen automatically.  If your node shows up on the status page as Unknown, you may be blocked from all channels of 9100.  See the installation documentation "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 to a 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 on 9100.  If your node is capable of cross linking to something else, please disable that capability before connecting to Ref910x.  If you have a special exception request contact your local node operator and Shorty K6JSI via email.

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 please 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 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 'monitors') to block a node that is causing a problem for connected nodes.  This is a very 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 node contact advising them 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 monitor may remove the block without being asked once your node has disconnected, but we often forget, so the reply is important.

Operating Tips

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 conversation.
 
Resist the temptation to break into a conversation unless invited or it is obviously open.  It is rude to interrupt an eyeball conversation, and it is also 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 may be a great way to solicit a contact on HF, but not on a reflector.  Unlike the noisy conditions of HF, and the tuning required to hear other stations, we are channelized here on FM.  That means we are ALL listening to the same channel, and we will be able to hear your call, without the necessity of a CQ.  

We recommend simply putting your callsign out there, with a statement that you’re looking for a contact.  Another very good way of getting a response is to ask for a WIN System demonstration.  We will usually then come back and identify our selves, with our name and location.  Very good for a live demonstration of the capabilities of the IRLP and the WIN System.

All Topics of conversation within the realm of "Good Amateur Practice" are allowed.  There are only three rules on the WIN System, 1) Please use the golden rule, that is treat others as you would like to be treated, and the only specifically prohibited topics are 2) politics, 3) religion.  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.  Do not ever say control codes over the air, even connect and disconnect codes.

When disconnecting from Ref9100, it is not necessary to announce that fact to everyone connected before you hit buttons.  In fact, a disconnect announcement can be disruptive if you are sneaking in between transmissions of a conversation you are otherwise not a part of.  Just bleep in your code and be gone.  You may announce your disconnection afterward if you care to, or our disconnect wav file that plays will do it for you.  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-Channels
9100 - 9109

Use of Reflector sub-channels is encouraged.  You do not need specific permission to use any of the general use channels.  If you would like to discuss the use of a 9100 reflector channel on an on-going basis, contact Shorty K6JSI.  Current channel assignments
Below:

9100     WIN System, 24x7
9101     General Traffic
9102     General Traffic
9103     General Traffic
9104     General Traffic
9105     General Traffic
9106     General Traffic
9107     General Traffic
9108     General Traffic
9109     General Traffic

  Contact Information

Reflector Owner is:  Shorty K6JSI  The WIN System
Reflector Control Operators are:  K6SLS, KB6OT, K6KYA, K6BDM, KI6IXQ, K6UFX, N6WI, N5ZUA, WI6RE, WA6NIF, WB6IAG, W6JZL, AF6EQ, K6JRM, KF6QYX, WH6FM, K6WKB, KI6SEJ
IRLP System Designer is:  Dave VE7LTD