Connecting and channel assignment
Generally all of the channels on the Seattle Reflector are open for any licensed ham radio operator to use. Currently channel 8 is the only channel with a defined use, and that is to link up some repeaters located around the Seattle area. Anybody may connect to any channel, including channel 8, and feel free to talk to the other nodes connected if you see them connected.
If you want to link up a couple nodes on a temporary basis feel free to use any idle channel on the reflector.
| Channel Num | Assigned Use |
| 0 | Un-assigned, available for public use |
| 1 | Un-assigned, available for public use |
| 2 | Un-assigned, available for public use |
| 3 | Un-assigned, available for public use |
| 4 | Un-assigned, available for public use |
| 5 | Un-assigned, available for public use |
| 6 | Un-assigned, available for public use |
| 7 | Un-assigned, available for public use |
| 8 | Special:Echolink Gateway channel, links to Echolink conference *SEATTLE* as node number 9198 on both Echolink and IRLP. Often a few repeaters from around the Seattle, WA will stay linked here. |
| 9 | Un-assigned, available for public use |
Monitoring Requirements
All nodes connected to the Seattle reflector must 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 are subject to ridicule and may be blocked. CTCSS or DCS squelch on your repeater is strongly encouraged.
Repeater Hang Time and IDs
If your node is linked to a repeater, there must be absolutely no repeater hangtime heard through the IRLP link, nor anything resembling a courtesy tone. Automatic ID's are ONLY acceptible when the ID occurs on top of a station talking where it's unavoidable. Automatic ID's heard through the link from a node that's otherwise not transmitting will probably result in your node being blocked.
Pulsing
When you set up your IRLP node PLEASE run the pulsecheck utility to make sure your node will not transmit pulses into the network. A pulse is when your link radio hears the repeater's hang time after transmitting and flips around and transmits the hang time back into the reflector. This could lock up the reflector for long periods of time and will get your node blocked. See the IRLP Reflector Connection Guidelines page for more information.
If you are blocked
Reflector operators have a management function that allows a node that is causing a problem on the reflector to be blocked. This is a necessary function in order to have a reasonably quiet and functional place for nodes to connect. No one would use our reflector it if it was constantly filled with local QSO's, courtesy tones, repeater ID's, or pulsing nodes.
If your node is blocked an e-mail will be sent to the node administrator's address. Please read the e-mail and resolve whatever problem was reported. When the problem has been addressed, please reply to the e-mail and request for your node to be unblocked.
Links and Information
IRLP Status Page / Reflector SummaryReflector 9200 Policy page