Am I using Echolink wrong?

[KB3TKL]

I can connect to the local Echolink repeater with my HT and then talk on any Echolink repeater throughout the country. But when I use the Echolink software to connect to the local Echolink repeater I can hear myself on the repeater with my HT but if I call back I never hear the audio on my computer. It also doesn't say RX in the Echolink software when I key up the local repeater. I have used the test server fine and I've talked to people who were also connected to the Echolink network using the Echolink software. Any idea on what I am doing wrong or doesn't Echolink work this way?

[W9PSK]

How are you set up on your computer? Are you a sysop user or computer user?

[K0RGR]

EchoLink works by taking the audio from a link transceiver that's tuned to the repeater, and feeding it through the soundcard on a gateway PC that's connected to the Internet.

If you can connect to remote repeaters through your HT, and the people on the other end can hear you, that says that the audio from the repeater is being picked up and retansmitted over the Internet. It should work the same way for stations that connect from outside via the Internet.

Most gateway stations use a VOX function to 'key' EchoLink. My first guess would be that your audio is too low, or the clip level is set too low on the EchoLink gateway. Find someone with good audio into the repeater and see if you can hear them through EchoLink. If not, the sysop needs to investigate.

[KB3TKL]

How are you set up on your computer? Are you a sysop user or computer user?

Computer user


Most gateway stations use a VOX function to 'key' EchoLink. My first guess would be that your audio is too low, or the clip level is set too low on the EchoLink gateway. Find someone with good audio into the repeater and see if you can hear them through EchoLink. If not, the sysop needs to investigate.

The Echolink repeater I'm hitting with my HT while trying to hear myself on the computer is on the mountain a few miles from my house.

I just tried it with someone in another state on a different repeater and the same thing happened. They could hear me but when they transmitted it was never picked up in the Echolink software.

Is there something that needs to be done on the radio end when they hear someone talking on the repeater through Echolink? Or does it act the same way as another other communication?

My only other guess would be to move my wireless router so I can get signal outside in the truck while I try to hit the repeater with my mobile setup.

[K8MHZ]

My only other guess would be to move my wireless router so I can get signal outside in the truck while I try to hit the repeater with my mobile setup.

Try it without the router. Echolink and wireless routers don't play well together.

[K0RGR]

I'm confused now.

How was the remote station on another repeater trying to talk to you exactly?

When you said originally that you could access EchoLink with your HT and talk to people on other repeaters with it, I assumed you meant that you could talk both directions. Is that not true? If it's only working one way - that is, if the remote people can hear you when you talk, but not other way around, it probably means that the sysop for the local EchoLink gateway doesn't have one of his audio lines hooked up to the computer.

What's the node # or callsign for the local EchoLink node? I looked for you as a computer user and couldn't find you.

[W9PSK]

Computer user



The Echolink repeater I'm hitting with my HT while trying to hear myself on the computer is on the mountain a few miles from my house.

I just tried it with someone in another state on a different repeater and the same thing happened. They could hear me but when they transmitted it was never picked up in the Echolink software.

Is there something that needs to be done on the radio end when they hear someone talking on the repeater through Echolink? Or does it act the same way as another other communication?

My only other guess would be to move my wireless router so I can get signal outside in the truck while I try to hit the repeater with my mobile setup.

Huh? Now you have me totally confused. Why would you want the signal from your router to reach your truck? Are you using a laptop from your truck? If so, why?

It sounds to me like your problem is related to ports 5198 and 5199. Did you open those ports on your router's firewall?

[K0RGR]

Audio problems like this usually don't involve the ports. More likely, it's plugs in soundcards or audio clip levels.

[W9PSK]

I'm confused now.

How was the remote station on another repeater trying to talk to you exactly?

When you said originally that you could access EchoLink with your HT and talk to people on other repeaters with it, I assumed you meant that you could talk both directions. Is that not true? If it's only working one way - that is, if the remote people can hear you when you talk, but not other way around, it probably means that the sysop for the local EchoLink gateway doesn't have one of his audio lines hooked up to the computer.

What's the node # or callsign for the local EchoLink node? I looked for you as a computer user and couldn't find you.

He's talking about two different situations. When he accesses Echolink through the repeater, using his HT, it works just fine. When he accesses Echolink through his computer, he gets out but there's no incoming audio. Why he would want the signal from his router to reach his truck is a bit baffling, unless he is using a laptop from his truck.

[W9PSK]

Audio problems like this usually don't involve the ports. More likely, it's plugs in soundcards or audio clip levels.

Reread what he's saying. He can connect and get out as a computer user, but there's no return audio from the people he connects with. That's a classic 5198/5199 issue.

[K0RGR]

He's talking about two different situations. When he accesses Echolink through the repeater, using his HT, it works just fine. When he accesses Echolink through his computer, he gets out but there's no incoming audio. Why he would want the signal from his router to reach his truck is a bit baffling, unless he is using a laptop from his truck.
Yeah, but then he brought another station into it, and I'm confused about how he did it and exactly what he is hearing or not hearing.

If he gets on the local repeater with his HT, the gateway should pick up his audio and key the node into 'transmit' and he should see his side go into 'Receive'. He said previously that didn't happen. If he's connecting to a remote repeater from his computer and not hearing any audio coming back, then it's most likely something on his computer.

I've never seen a case where one of the two ports wasn't working and he could still fully connect, but I've been wrong before.

[W9PSK]

Try it without the router. Echolink and wireless routers don't play well together.

This is true. I tried it with my laptop here at home and finally gave up. For some reason the computer you use has to be hard wired to the router for Echolink to work well.

However, I do know of some folks that have had success with a wireless connection. I know of one ham that accesses the internet wirelessly and goes through one of the proxies Echolink offers. Echolink works great for her.

[W9PSK]

Yeah, but then he brought another station into it, and I'm confused about how he did it and exactly what he is hearing or not hearing.

All he did was connect to another station as a computer user. This is why he started this thread. When he goes through the repeater using his HT, he doesn't have any issues. When he tries using the program as a computer user, it doesn't work properly.

[W9PSK]

Yeah, but then he brought another station into it, and I'm confused about how he did it and exactly what he is hearing or not hearing.

If he gets on the local repeater with his HT, the gateway should pick up his audio and key the node into 'transmit' and he should see his side go into 'Receive'. He said previously that didn't happen. If he's connecting to a remote repeater from his computer and not hearing any audio coming back, then it's most likely something on his computer.

I've never seen a case where one of the two ports wasn't working and he could still fully connect, but I've been wrong before.

That didn't happen when he tried listening to himself on his own user node. See the difference? He went through the repeater's node to try to listen to himself on his node. The repeater's Echolink setup is working like it should. It's the one he has set up at his house as a computer user that isn't working properly.

[KB3SYZ]

What I'm getting is that when he hits the repeater with hit HT it works as it should.

When he uses Echolink he can connect to the node and hold a QSO with another Echolink user.

But when he uses his HT to talk to an Echolink user it does not work. Same way when he uses Echolink he can not talk to a non Echolink user.

By the way I use Echolink via a wireless connection with no problems.

[K0RGR]

Here's from the Echolink website FAQ's:

"I seem to be able to connect to other stations, but I can't hear them, or they can't hear me. What's the problem?

If you're not hearing any audio, first check to see if a text message appears on the right-hand side of the screen when you establish the connection. (Typically, this message says a few words about the station you have connected to.) If not, you might have a "firewall" problem that needs to be resolved -- see the Connecting FAQ.

Next, double-check the settings under Tools->Setup, on the Audio tab. The two audio devices listed should match the name of the sound card you're using, or should be set to "[system default]".

Finally, be sure your computer's microphone and speakers are plugged in properly, and the audio levels are set right. Go to Tools->Adjust Volume->Recording and be sure the Microphone is turned up, selected, and not muted. Then, go to Tools->Adjust Volume->Playback and be sure that Volume Control and Wave are both turned up, selected, and not muted. Also, be sure the volume control on your speakers is turned up.

If you are running Windows 98 or Windows 95, be sure there is no other program on the computer that might be using the sound card for recording. For example, if you have speech-recognition or dictation software installed, be sure it is not running when you use EchoLink."

[KB3TKL]

To clear some things up the only reason I'm trying to talk to myself is because when I try to talk to other people it doesn't work and instead of wasting their time with my problem I'm trying to troubleshoot this by myself.

Using a wired or wireless connection doesn't seem to make a difference with my problem. I've tried putting my laptop in a DMZ (where everything is open to the internet and also disabled my software firewall on my computer) and it didn't seem to make a difference. I will try running the cable directly from the modem to my computer in a few minutes.

If one of you is using the Echolink software and I am also using the Echolink software we can communicate fine back and forth. It's when I try and use the software to connect to an Echolink repeater node is when I have the problems. The people on the repeater hear the announcement that I have connected and they hear me speak. But if they try and answer me back I don't hear anything. Using software to software communications the RX light works fine but doesn't show up when going from repeater to software.

[W9PSK]

To clear some things up the only reason I'm trying to talk to myself is because when I try to talk to other people it doesn't work and instead of wasting their time with my problem I'm trying to troubleshoot this by myself.

Using a wired or wireless connection doesn't seem to make a difference with my problem. I've tried putting my laptop in a DMZ (where everything is open to the internet and also disabled my software firewall on my computer) and it didn't seem to make a difference. I will try running the cable directly from the modem to my computer in a few minutes.

If one of you is using the Echolink software and I am also using the Echolink software we can communicate fine back and forth. It's when I try and use the software to connect to an Echolink repeater node is when I have the problems. The people on the repeater hear the announcement that I have connected and they hear me speak. But if they try and answer me back I don't hear anything. Using software to software communications the RX light works fine but doesn't show up when going from repeater to software.

OK. Thanks for clearing that up. As you can tell, your first post left us with different impressions of what the problem could be. This problem--is it just with that one specific repeater, or is it any repeater node? If it's just that one specific repeater, then the problem is on their end not yours.

[K0RGR]

And this happens on multiple remote repeaters?

There's a 'monitor only' Sysop function that they might have turned on for one node, but not all of them.

Are you using the latest version of the the EchoLink code, and can you find out what the node is using? The latest versions are 'firewall friendly'.

Have you tried using the public EchoLink proxies? You might give that a try. If it works through a proxy, then you do have some sort of a firewall issue.

[W9PSK]

TKL, log into Echolink on your computer. Maybe we can all put our heads together there and figure out what the problem is. My node number is 401099.

[K0RGR]

Have you tried the Firewall test in the Tools menu?

[KB3TKL]

This problem--is it just with that one specific repeater, or is it any repeater node? If it's just that one specific repeater, then the problem is on their end not yours.

I've tried two different Echolink repeaters.



Are you using the latest version of the the EchoLink code, and can you find out what the node is using? The latest versions are 'firewall friendly'.

Have you tried using the public EchoLink proxies? You might give that a try. If it works through a proxy, then you do have some sort of a firewall issue.

I have the newest version of Echolink (908). I'll do some research on the public proxies now. I was going to download the proxy software but it looked like I would need another internet connection for it to work.


TKL, log into Echolink on your computer. Maybe we can all put our heads together there and figure out what the problem is. My node number is 401099.

I'm logged in now I just had a blue screen issue. I see you on the network but it says you are a link. How does that work for connecting to you?


Have you tried the Firewall test in the Tools menu?

Yeah I tried the firewall test and Test #1 Port 5198 fails but then Test #1 5199 passes as well as Test #2 5198 + 5199. I emailed Echolink thinking it might be some sort of bug but they just replied with the standard reply. I couldn't find anything in Google for just the very first test failing and all the other 3 passing. It was either the first two failing and the last two passing or none passing.

[W9PSK]

I've tried two different Echolink repeaters.



I have the newest version of Echolink (908). I'll do some research on the public proxies now. I was going to download the proxy software but it looked like I would need another internet connection for it to work.



I'm logged in now I just had a blue screen issue. I see you on the network but it says you are a link. How does that work for connecting to you?



Yeah I tried the firewall test and Test #1 Port 5198 fails but then Test #1 5199 passes as well as Test #2 5198 + 5199. I emailed Echolink thinking it might be some sort of bug but they just replied with the standard reply. I couldn't find anything in Google for just the very first test failing and all the other 3 passing. It was either the first two failing and the last two passing or none passing.

Try looking up your router on www.portforward.com . It's an excellent resource for properly configuring your router firewall. Also, if you are using XP, make sure that Echolink has been added to your firewall exceptions list. Lastly, if you have a program like Zone Alarm, that includes yet another firewall, make sure Echolink has the proper permission for outgoing and incoming.

[W9PSK]

BTW, you can connect to me just like you would any other station. It announced that you were connecting, but then said it timed out. That is usually a firewall related issue.

[W9PSK]

Mike, I just checked and Echolink lists you as "busy". Unless you are connected to someone else right now, it shouldn't do that. Did you click the "list me as busy" button at the top?

[KB3TKP]

I was having the same issue when I downloaded Echo link (I could tx but not RX). It was my wireless router.
I went through portforward .com and followed the instructions and haven't had any issue's since.

[KB3TKL]

Try looking up your router on www.portforward.com. It's an excellent resource for properly configuring your router firewall. Also, if you are using XP, make sure that Echolink has been added to your firewall exceptions list. Lastly, if you have a program like Zone Alarm, that includes yet another firewall, make sure Echolink has the proper permission for outgoing and incoming.

Right now I have the windows firewall disabled and I even uninstalled Norton since I could never get it to actually disable.


BTW, you can connect to me just like you would any other station. It announced that you were connecting, but then said it timed out. That is usually a firewall related issue.

I updated the firmware in my router and never switched all my settings back. Everything should work fine now.


Mike, I just checked and Echolink lists you as "busy". Unless you are connected to someone else right now, it shouldn't do that. Did you click the "list me as busy" button at the top?

Yeah I switched my status to busy because I was out shoveling the driveway.


I was having the same issue when I downloaded Echo link (I could tx but not RX). It was my wireless router.
I went through portforward .com and followed the instructions and haven't had any issue's since.

I've already tried everything on portforward.com including putting my computer in a DMZ. http://en.wikipedia.org/wiki/DMZ_(computing)

I'm actually an IT nerd trying amateur radio. I think thats the reason this is driving me nuts. That is why I was wondering if maybe I was using Echolink wrong since I could talk computer to computer but not computer to repeater.