The ones that connect for a couple seconds are usually having problems I 
hope, if not I don't see any more point in that than what I said before. My 
repeater has no courtesy tone and allows about 1 second of the tail to come 
through with tone squelch on but I have the settings high enough that that 
doesn't trigger the program or go out on the link radio. You can't hear the 
tail on the repeater hardly no matter what you do. My ID shouldn't go out 
either. I have the link setup at the house since the repeater is a Motorola 
MSF5000 which is totally stock except for the slight mods to get it in the 
ham band so there are no voice ID's, no courtesy tones, nothing like that on 
it and I don't think that's even available. I'm not sure if direct linking 
is possible or not, no one is doing it that I know of but I find it hard to 
believe it can't be done but I don't have access to the Internet where the 
repeater is anyway. The repeater's hard enough to get to 20 feet up in a 
loft over the town ambulances in their garage. I sure hope they never kick 
it out of there because I don't think there is a safe way to get it down. 
For those who haven't seen that repeater, it's in a 5 foot cabinet and 
weighs a little over 300 LBs. It's top heavy too which doesn't help. The 
only problem with my link is it keeps keying what ever it's connected to and 
it sounds like the line in is coming out the line out even muted so I'm 
going to try another sound card eventually and that will fix that I think.
----- Original Message ----- 
From: "Buddy Brannan" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Sunday, March 16, 2014 3:56 PM
Subject: Re: my intro: and help with echo link


> The biggest problem I have with computer connects are the drive-bys.=20
>
> That is, people who connect for 5-30 seconds,
> don=92t say anything, then disconnect.
>
> It=92s a bit annoying.
>
> The biggest problem I have with RF connects
> are that a lot of Echolink system operators
> run sloppy systems.=20
>
> They either are linking a radio sitting on a repeater that doesn=92t
> have any CTCSS squelch, or if it does,
> it=92s on all the time. So all the courtesy tones,
> tails, ID=92s, and crap also come through.
> The only thing that should come through a properly configured
> link are the voices of the operators on the repeater.
> If the repeater ID=92s during the transmission, OK, but I don=92t want
> to hear your repeater key up my repeater just to ID.
> I also don=92t need to hear your courtesy tones
> and three-second tails tying up the whole system for everyone else.=20
>
> It really makes doing very much of anything really difficult.
>
> So if you can=92t put Echolink directly on your controller, so it has
> zero hang time and doesn=92t send out RF iD=92s over the Internet,
> be sure that the repeater it is tuned to on the RF side
> has properly configured CTCSS squelch, which drops with the voice
> transmission drop and isn=92t active for ID=92s.=20
>
> Those are, IMO, the two things that really give
> Echolink its reputation. Well, those and poorly adjusted
> audio that the sysops do not or cannot fix.=20
>