Post by va3css on Feb 18, 2005 1:38:46 GMT -5
As an avid user and monitor of Echolink, I hear a lot of things that I find annoying.
For example:
I monitor a local repeater that's Echolink-enabled, and I often hear a station connect, but then no audio. The repeater announces the connecting station with it's robotic voice, but then afterwards, silent transmissions.
Generally, there are three or four attempts to transmit, as above, then the user disconnects due to no answer.
But sometimes, the user tries over and over and over and over and over...
It almost appears that the users above don't test their setups before tying up a repeater.
Don't do this. Spare us all the bother.
It's very simple to test your setup to see if it works properly on Echolink. The system has a test server, which is node number 9999, and can also be found via a button on the Echolink program toolbar, in case a number like 9999 is too hard to remember. When you connect to the test server, a message comes back telling you how it works. You simply "transmit" to the test server, which records your transmission, then plays it back to you, so that you can hear what it sounds like. You can stay connected to the test server for as long as you wish to get the results you want. You'll be listed as "busy" or "in conversation" to the others on Echolink, so don't worry about being interrupted.
It's simple, really, and takes only a minute or so out of your day to prevent tying up a repeater for no reason.
Another thing I hear often is broken audio. I've heard many users connect with what sounds like a poor connection on their computer mic. You can answer them all you want, trying to tell them what is happening, but most often it's to no avail.
Round and round and round we go... some users will go around like this for half an hour if you keep on trying with them.
What you must remember when using Echolink, folks, is that while you tie up a repeater trying to make a contact, you may be disrupting a QSO on that repeater for the entire time you sit there trying over and over.
Have a little respect. Check the Echolink test server before you connect to a repeater. It may not be much of a bother when connecting to another ham directly when you have problems like this, because they can use the message window in Echolink to simply type a message to you. Those of us listening to your futile efforts over the air on a repeater don't have that ability.
The other thing I hear a lot from Echolink users is this:
Um... yes... as a matter of fact, we're in the middle of a net here... thanks for asking...
Try listening for a moment before blurting out.
There are more examples, but there's a few to start with.
For example:
I monitor a local repeater that's Echolink-enabled, and I often hear a station connect, but then no audio. The repeater announces the connecting station with it's robotic voice, but then afterwards, silent transmissions.
Connected. (callsign of station) (courtesy tone)
....
(long silence) (courtesy tone)
...
(long silence) (courtesy tone)
...
(long silence) (courtesy tone)
....
(long silence) (courtesy tone)
...
(long silence) (courtesy tone)
...
(long silence) (courtesy tone)
Generally, there are three or four attempts to transmit, as above, then the user disconnects due to no answer.
(callsign) Disconnected.
But sometimes, the user tries over and over and over and over and over...
It almost appears that the users above don't test their setups before tying up a repeater.
Don't do this. Spare us all the bother.
It's very simple to test your setup to see if it works properly on Echolink. The system has a test server, which is node number 9999, and can also be found via a button on the Echolink program toolbar, in case a number like 9999 is too hard to remember. When you connect to the test server, a message comes back telling you how it works. You simply "transmit" to the test server, which records your transmission, then plays it back to you, so that you can hear what it sounds like. You can stay connected to the test server for as long as you wish to get the results you want. You'll be listed as "busy" or "in conversation" to the others on Echolink, so don't worry about being interrupted.
It's simple, really, and takes only a minute or so out of your day to prevent tying up a repeater for no reason.
Another thing I hear often is broken audio. I've heard many users connect with what sounds like a poor connection on their computer mic. You can answer them all you want, trying to tell them what is happening, but most often it's to no avail.
How... (silence) .... (crackle) ... is a .... (clunk) (silence) .... (crackle) ... (courtesy tone).
"Ah... Echolink station, your audio is very badly broken up. Please check your connections and repeat. This is (callsign)."
...
Ok... (crackle) ... (silence) ... and ... (crackle)...(courtesy tone).
"Ah... Echolink station, your audio is very badly broken up. Please check your connections and repeat. This is (callsign)."
...
Ok... (crackle) ... (silence) ... and ... (crackle)...(courtesy tone).
Round and round and round we go... some users will go around like this for half an hour if you keep on trying with them.
What you must remember when using Echolink, folks, is that while you tie up a repeater trying to make a contact, you may be disrupting a QSO on that repeater for the entire time you sit there trying over and over.
Have a little respect. Check the Echolink test server before you connect to a repeater. It may not be much of a bother when connecting to another ham directly when you have problems like this, because they can use the message window in Echolink to simply type a message to you. Those of us listening to your futile efforts over the air on a repeater don't have that ability.
The other thing I hear a lot from Echolink users is this:
(callsign) Connected.
This is (callsign). Anybody around?
This is (callsign). Anybody around?
Um... yes... as a matter of fact, we're in the middle of a net here... thanks for asking...
Try listening for a moment before blurting out.
There are more examples, but there's a few to start with.
