The *KC4QLP* [General Use]
Echolink conference server (Node number 267137) is back online as of 5/5/19 and is also running an IRLP reflector as node number EXP0037 and a D-Star reflector as node number XRF267.
The *KC4QLP* and *KC4QLP-C* [General Use and WX-Nets]
Echolink Conference Servers (Node number 267137 / 290251), IRLP node EXP0037, D-Star reflector XRF267 owned by KC4QLP is an open system, free to all to use and is
often part of major WX related net activities in a listen only mode from *WX_TALK*.
The systems are capable of supporting 2000+ concurrent stations if
the need becomes necessary. The server is fitted with redundant power supplies including full
UPS support to deliver a high availability 24x7x365 redundant Echolink conference server.
The *eQSO and Free Radio Network* [General Use and WX-Nets]
We now have an eQSO server and Free Radio Network linking server online. The servers are password protected as they are for Amatuer radio/licensed radio operators only. Email us your call sign and a copy of your license to firstname.lastname@example.org and we will email you the eQSO passord and give you access rights to the FRN network.
The server address for eQSO is: kc4qlp.ddns.net, port 10027. The Free Radio Network address is kc4qlp.ddns.net, port 10024.
The KC4QLP-R node, 56703
(temporarly off the air) operates locally on 145.290 mhz, (In the process of obtaining tower space in the Little Falls NY area...more information will be released here as the processes of coordination and tower space is obtained. The repeater, we hope will have coverage from Rome NY to the Capitol district, to Cooperstown to Old Forge. The repeater will be part of the Skywarn Network and will be tied into 911 services.). Requires a PL tone of 167.9hz to access the system.
The KC4QLP-L node, 56704
will operate locally on a 10 meter FM simplex frequency. The frequency will be 29.500 mhz. Equipment is being connected and testing will begin soon!
The KC4QLP node, 89052
is a non RF node and is used for local communications from IP to RF and for administrative purposes during weather nets. You can also find us while mobile via this node on our network radio.
IMPORTANT TO NOTE: All three nodes do not allow mulitconferencing, however all three nodes are connected to conference servers *KC4QLP-C* and or *KC4QLP*, IRLP exp0037, D-Star XRF267. So if you are on Echolink and are looking to talk to someone locally, please connect to either one of the conference servers as that will get you on 145.290 mhz and 10 meter FM [when it becomes available] in the Mohawk Valley area of Central New York. If you try to connect to nodes 56703, 56704 or 89052 directly, you will only get a "busy" message. -Only- connect directly to nodes 290251 or 267137. Doing so -will- get you connected to nodes 56703, 56704 and 89052. Thank you for your understanding of how the systems are configured and feel free to connect up anytime for as long as you wish.
Conference Server Nodes Operating Rules
The conference servers has a strict language and usage policy in
place. - All -
be made using the "English" language and sufficient breaks between overs must be maintained.
Failure to adhere to this policy will in the initial stages result in the offending system
being disconnected from the conference. Persistent offenders will be "banned" from the
conference server for a short period while the issue is resolved.
The language policy is in place as the "team" prefer to be able
to monitor "all" traffic across the system to prevent license breaches.
NOTE: DO NOT CROSS LINK TO ANY OTHER CONFERENCE SERVER WITHOUT PRIOR PERMISSION
-WHILE- connected to *KC4QLP* [General Use] or *KC4QLP-C* [General Use and WX_Nets]. Doing
so without prior permission will result in -YOUR- node being permanently ban FOREVER. It is not necessary to tie up half of the conference servers on
Echolink with having the same traffic on all of them. While having another server connected
to another server to assist in directing "lurkers" away from main net channels is useful,
connecting a half a dozen servers together "just for the heck of it" defeats the purpose of
having a wide variety of conference servers operating on Echolink. What the *KC4QLP*
[General Use] and *KC4QLP-C* [General Use and WX_Nets] , IRLP exp0037, D-Star XRF267 does support are important
organizations such as the Hurricane nets and the New England emergency nets along with
various nightly nets that are of proven good value to the Amateur community. Any organization
looking for bandwidth to host a net are welcome....as long as your organization knows what it
is doing and has a good standing/track record with the Amateur community. Stations wishing to
connect to join regular QSO's or stations in NY wishing to form an adhoc network are
welcomed. For additional info and/or inquiries send an email to KC4QLP@midatlanticengineeringservice.com.
Do NOT send your repeater and links ID's (voice or CW), TONES, BEEPS and other NOISES from the RF side into the internet side of the network. To setup a node that allows your IDs and tones from the RF side to enter into the network is improper. There is an easy fix for preventing your repeater tones and IDs from entering the network, contact us via email for a step by step procedure on how to make this happen. Stations that connect to our servers that send their repeater IDs and tones from RF to the network will be disconnected and contacted about the matter to give you a chance to fix the issue. Stations that refuse to correct the issue will be prevented from using the network any further. One must understand that if two or more improperly configured stations were on the network sending ID's and tones back and forth, this would create a ping pong effect rendering the entire network useless. IRLP and D-Star networks are very strict on this policy. Since our nodes are part of those two networks, we must enforce this policy. Also do NOT bring in or start nets on the servers without prior permission. To do so will get you removed from the system. The conference servers are not a "broadcasting system". HF traffic other than from 10 meter FM should not be put on the network unless prior arrangements have been made and a control operator is present. "Broadcasting" one way HF traffic is forbidden, and "broadcasting" such traffic will get you kicked off of the network. Like it or not, that is the way it is and please respect that.... Thank You.
Sometimes you will see a message "Doubling With *KC4QLP*" or
"Doubling With *KC4QLP-C*" depending on which server you are on, this is an advisory message
and does not mean that you are doing anything wrong. It is because your station has entered
transmit mode before the conference server has entered receive mode. It is there to remind a
station to leave a suitable break between transmissions. You can also get this if a link is
bouncing and you try to go into transmit. There is nothing as we said to worry about you or
your gateway is not causing a problem. Each server has a "Pause time" and "belch filter"
The pause time setting is there to ensure that there's a break
between transmissions to allow simplex links to leave the conference. This "pausetime" is set
to 1750 ms.
The "belch filter" is set to a minimum number of milliseconds that -L and -R stations must
transmit before being recognized on the system. This parameter may help prevent
repeater "bouncing" that occurs when multiple repeaters or link stations are logged into a
conference room with poor operating parameters. The belch filter has been set 2000 ms. So
slow down, pause, then key up, pause 2 seconds before speaking.
Bouncing links will be disconnected from the conference Server
immediately as will any conference hosting them, if a station / conference regardless of its
class continues to disrupt the system then they will be "banned" from joining the conference
Stations not identifying correctly will also be disconnected and
banned from the conference server.
In the case of disputes the stations involved will be
disconnected. They should contact the administrators via the web site as soon as possible.
The same with basic rules apply for "text messages". Do not bring the amateur service into
disrepute with the text messages you send. A few programs have been developed that will speak
the text messages for our visual impaired operators. Use of profanity in text will also get
you barred from the nodes as it is possible for the text to speech programs to read the text
messages over the air. Use of profanity is poor operating practice and use of the "7
forbidden words" are a violation of part 97 FCC rules and regulations in the United States.
This similar rule applies in most if not all countries around the globe.
Standalone stations operating in conference
mode while connected to the conference servers or KC4QLP is forbidden. The conference servers will be employing a conference killer script on their return. Anyone operating on conference mode or attempting to connect a conference server that is not on the prearranged connection list will automatically disconnected
from the system and prevented from accessing it further. Special permission will be granted
to those stations that need to connect while in conference mode. This requirement is only to
help manage connected stations and the traffic that passes through the system. The conference
servers have enough bandwidth available, so individual conference nodes would only open a
possible situation of uncontrolled traffic.
Many stations who operate this mode do not understand the
implications of their operating style. We have seen many station's operating in this mode and
broadcasting the idents and various announcements from these systems that they have linked to
or have linked to them.
This is unacceptable, You should only operate in conference mode
when you are a stand-alone station if you understand the Echolink system and monitor your
connection should there be problems.
Also there have been occasions where stations have been making
general broadcasts via the Echolink system and using both the conference server and the
KC4QLP repeater as a platform for this type of operation. This is NOT permitted via any of
our systems and again action will be taken to prevent such operations from continuing.
The conference server runs using the Bridge Software and is administered
using the groups own custom command and control software. Systems administration is performed
by selected stations across the world and is monitored constantly. It is the role of the
administrators to enforce the language and usage policy.
A few commands are available to users that are unique to thebridge. Commands
are entered on the message line in the same way as a text message, by
prepending a '.' (period). Commands are not forwarded to other conference
users so they are non-intrusive to normal operations. The command must begin
at the first character on the line.
Commands may be abbreviated to the shortest length that is still unique. For
example ".stat", ".sta", and ".st" are valid abbreviations for the
".stats" command, but not ".s" since there are two commands that start with
the letter 's' .
".help" and ".?"
This command does much as you would guess, it lists the available commands.
This command lists any bulletins or recorded nets that may be available to
be played back.
This commands displays the node number, Qth and busy status for a specified
station. The station must be online or have been online recently for the
information to be available.
".play ", ".stop"
This command starts playing the selected bulletin or recording. Any text
messages that were sent during a net are also replayed sent. While you are in
playback mode you will not be listed on the station list of thebridge and
you will not receive any live conference traffic, voice or text. To end the
playback enter the .stop command or simply disconnect.
This command dumps the user list with IP addresses.
Format: <'S' | 'R' | 'E'>
The list is terminate by a blank line. The final character indicates the
users protocol, SpeakFreely, RTP, or EchoLink. The callsign field will
also contain the user's IP address if the protocol does not provide a callsign.
This commands displays interesting (to some) technical statistics about
the operation of the conference bridge such as when the maximum number of
users were connected.
".lurk" and ".delurk"
The EchoLink system is very different than "real" radio in one important way...
everyone knows who is listening. Sometimes you might only want to monitor a
channel, but not get involved in a conversation. This is particularly useful
for nets when you want to listen, but don't have anything to contribute.
The ".lurk" command allow you to suppress the listing of your callsign as an
active member of the conference, but you will still be able to listen. You
can rejoin the conference at any time by using the ".delurk" command or by
This command displays the amount of time thebridge has been running since it
was loaded. I'll admit it, the primary purpose is for bragging rights... "my
conference bridge has been up for ..."
This command displays the version of thebridge software and the type
of operating system it's running on.
This command causes thebridge to record your next transmission and then play
it back to you when you stop transmitting. This allows you to test your setup
and adjust audio levels etc without assistance. Audio quality is a very
subjective thing, it's always best to hear it yourself.
Note: The UDP protocol used for conferencing is not 100% reliable, the
".test" command will send you the response "Your next transmission will
be recorded and played back." to indicate that your command was received.
Please do *NOT* make a long test transmission unless you receive the response!
Otherwise your test transmission will be sent live over the conference bridge.
Bob KC4QLP, Bobby W2RFS, and Tony VK3JED who also provided us with days of tech support via email
Check here often for streaming audio
Universal Time Coordination
LINK / NODE STATS
Node 56704 10 meter FM simplex KC4QLP-L [online]
Node 56703 Repeater node- KC4QLP-R [online]
IRLP node EXP0037 (interconnected to *KC4QLP* Echolink node 267137) [online]
D-Star node XRF267 (interconnected to *KC4QLP* Echolink node 267137) [online]
Node 267137 *KC4QLP* "General Use" [online]
Node 290251 *KC4QLP-C* "General Use and WX_Nets" [online]
FRN Server [OFFLINE - under development]
EchoLink Conference & RF nodes status
If you want your node listed here, ensure that
(Tools>Preferences>Connections>Show Name of connected conference) is checked within the
All data sourced from http://www.echolink.org/logins.asp
All data sourced from webcast version="0.94" (c) Dean
The Web to APRS to Echolink to Text box and vise versa feature can be found at KC4QLP-EC
Typical Echolink Text Box, Echolink to APRS formating to make text go to APRS looks like this:
KC4QLP-L>[17:51:19] APRS EchoLink Crosslink. To send /receive messages to/from APRS stations.(APRS callsign - KC4QLP-EC)
A message received from APRS on Echolink looks like this:
KC4QLP-L>[22:12:07] KC4QLP-R>APRS/Echolink & Echolink txt/APRS link@KC4QLP-EC
A message sent from Echolink to APRS looks like this:
KC4QLP-R>>KC4QLP-EC wx traffic to/from APRS stations may be passed here
To send a text to APRS stations via KC4QLP-EC in the text box add this symbol:
Add that symbol > and then the callsign KC4QLP-EC in the text box
Our Current Position on APRS (Click on the icon FMI)
Our Current Position on APRS (Echolink to APRS Crosslink)
Our Current Position on APRS (APRS Weather, click on the icon for WX info)
WQJK414 & GMRS Radio
Visit our company home page.
We QSL only VIA eQSL.cc.
VOIP Weather Net, where the coordinating group for hurricane nets begin and are heard on the *KC4QLP-C* network.