Echolink

[SpaceForceCmdr]

Not exactly sure if this topic fit in here, but seemed like it might. Many of the repeaters around me have Echolink, and some have Allstar. Is there a specific section on here to discuss these services? Echolink is cool because you can just key in '00' and it connects you to a random node. I tried it out last night, and I got a guy in Tucson, AZ. Here's what I'm wondering: I think when I activate my local repeater and connect to a node, the repeater is tied up, correct? So, if anyone else calls into it, they would also hear me talking to the other people on Echolink, and if they transmitted, it would go to the other repeater, too?

Also, regarding the AZ repeater my local repeater connected to, would it interrupt local traffic on that repeater when mine links to it? I wouldn't want to bust in on a net or conversation that was taking place, but I'm not sure how I could know if it was in use, especially if I use the random feature. Maybe it doesn't work that way?

 

[nd5y]

EchoLink has a lot of sysop settings that can be changed. You never know if somebody is doing something special, weird, wrong, or stupid with their node.

I think when I activate my local repeater and connect to a node, the repeater is tied up, correct?

Echolink can be configured for multiple connections.
If it is configured for only one connection then if somebody else tries to connect they will get a busy announcement.
If you are playing around with EchoLink then that ties up the repeater. Only one person at a time can talk on it.

So, if anyone else calls into it, they would also hear me talking to the other people on Echolink, and if they transmitted, it would go to the other repeater, too?

Normally yes but EchoLink has a monitor mode where audio can come in from the internet but not go out.

Also, regarding the AZ repeater my local repeater connected to, would it interrupt local traffic on that repeater when mine links to it? I wouldn't want to bust in on a net or conversation that was taking place, but I'm not sure how I could know if it was in use, especially if I use the random feature.

The other node you connect to should get a connect announcement unelss they have announcements disabled.
If somebody is talking when that happens it should announce the connection when they finish talking.
Your node should also confirm that you connected to another node.

The local users of a repeater should know that it has EchoLink (or IRLP or AllStar or whatever) and not be shocked or surprised if somebody connects to it out of the blue.

 

[SpaceForceCmdr]

OK, appreciate the info, thanks. I think I'm starting to get my head wrapped around it all. On the one repeater, I tried connecting to the test server (9999), but it didn't work. Then, I tried connecting to a random node, and that was a success

If I'm understanding this correctly, it wouldn't really screw things up for other people if they were already talking on the node I connected to, right? They would hear the connection announcement, but in theory, they could keep on with their conversation. It's just that I would be there, too, and whenever they transmit it'd get sent our to their local area over their repeater (like usual), and to my local area over my repeater?

I know some people will just use their phone or PC for this type of thing, but IMO, then it's not really radio anymore. I know some will say it's not even "real" radio when connecting the way I did, but I like to think of it as hybrid radio.

Basically, I like Echolink and plan on experimenting with it, but just want to make sure I don't step on any toes or piss of the locals. I did email the owners of the one repeater to get clarification on instructions for use, but haven't gotten a reply.

 

[nd5y]

The sysop can change the DTMF commands. You might need to dial a prefix instead of just the node number to connect to another node including the test server. They could have left the default setting for random connect.

When you connect to a node it should immediately establish a two way audio path unless there are firewall, network or node configuration issues at one or both nodes.

If somebody on the other end is talking when you connect you should start hearing them.
If you start talking after you get the "connected" announcement they shoud hear you on the other end.

EchoLink with the default settings has about 1.5 seconds of audio and network buffering which creates the problem of people on repeaters and simplex nodes doubling and not knowing it.

If there is a net or something going on when you connect then they should have sense enough to tell you to stand by.


EchoLink has good documentation on their web site and also in the Windows software help (F1).

 

[AK9R]

Is there a specific section on here to discuss these services?

Allstar, Echolink, and IRLP are voice over IP services (VoIP). Therefore, conversations about them go in the Digital Voice for Amateur Use forum...which is where this thread has been moved to.

 

[SpaceForceCmdr]

Thanks!

 

[K5MPH]

Go to echolink.org all the info you need is on that website,echolink can be fun I call it the forgotton voip mode.......