| Monitoring Requirements |
All nodes connected to Ref9610 (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, and may be blocked. CTCSS or DCS squelch on your repeater is strongly encouraged.
Special Note for Operators of Simplex Nodes: Monitoring your node means being able to hear what your node receiver is hearing and sending up to the reflector. In most cases this means you must stay in the room with the node so you can hear it. Tone squelch is mandatory for simplex nodes. |
| Repeater Hang Time and IDs | If your node is linked to a repeater, there must be NO repeater hangtime allowed to pass through to IRLP nor anything resembling a courtesy tone. This means set it to zero, not 100ms. If you are using a keyed PL method to solving 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 any reflector. Remember that any IDs or hangtime passes through, completely blocks the reflector. |
| Register your Node |
Your node must be registered with the status page database to use Reflector 9610. If your node shows up
on the
status page
as Unknown, you may be blocked from all channels of 9610. See the installation documention
"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 the 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. |
| 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 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 half 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 'cops') to block a node that is causing a problem for connected nodes. This is a 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. |
| Did you get Blocked? Now what do you 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 cop may remove the block without being asked once your node has disconnected, but we often forget, so the reply is important. |
| Operating Tips and Bits |
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 QSO. Resist the temptation to break into a QSO unless invited or the conversation is obviously open. It is rude to interrupt an eyeball QSO, it is 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 is a great way to solicit a contact. Every Ham knows what that means. If you are specifically trying to make a contact, be sure to make that fact known in your call, especially if you are demonstrating IRLP. All Topics of conversation within the realm of "Good Amateur Practice" are allowed. There are no specifically prohibited topics, but 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. When disconnecting from the reflector, it is not necessary to announce that fact to everyone connected. In fact, a disconnect announcement can be disruptive if you are sneaking in between transmissions of a QSO you are otherwise not a part of. Just bleep in your code and be gone. 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. |
|
Channels and Net Assignments
|
The use of Reflector resources are open. You do not need specific permission to use 9610 for your general QSO's.
For a long term temporary event, please feel free to use channel 9 (9619). Just send an E-Mail using
this widget to let us know you are there and for how long. If you have more long term re-occuring needs, please contact us for a possible permanent assignment.
9610 - Open for ragchew (English) 9611 - *COLLEGE* conference Nets NET: Please email kb8zgl@kb8zgl.net to have your NET listed 9612 - Reserved for the Pacific Interconnection (W6REB Admin) NET: - Florida Hurricane and Skywarn (only when active) (K9EE Admin) 9613 - Kentucky IRLP Reflector Channel (N4AI Admin) 9614 - South CARS VOIP tied to Echolink Confrence *SCARS* (KY6V Admin) NET: - "South CARS Full Net" Saturdays 1300-1500 UTC NET: - "South CARS Pacific Coast Connection" Saturdays 1700-1800 UTC NET: - "South CARS Eurasia Connection" Saturdays 1800-1900 UTC NET: - "South CARS Australia Connection" Sundays 0200-0300 UTC NET: - "South CARS Traders Net" Sundays 1500-1600 UTC NET: - "South CARS" Traders Net" Wednesdays 1500-1600 UTC NET: - "South CARS TNT Open Forum" Fridays 0100 UTC 9615 - Available 9616 - *DODROPIN* Conference IRLP connection (VO1UKZ Admin) INFO: - http://www.dodropin.org 9617 - MICHIGAN tied to Echolink Confrence *MICHIGAN* (KB8ZGL Admin) 9618 - FRIENDS IRLP tied to Echolink Confrence *FRIENDS* 9619 - Reserved for Wisconsin Skywarn activities (KC0ARF Admin) |
| Who's who | Reflector Keeper: Mike W8MW |