Peter N Spotts wrote:
> I'm a newcomer to Qtel, so have mercy...
Welcome to the list!
> I've been trying to use Qtel and find that while a ham friend of mine
> can hear me on his local EchoLink repeater, I can't hear his side of the
> conversation. I've check all my audio mixer settings, and all is well.
I am no expert on the subject, but it is sure sounds like a firewall
issue to me.
> As a test, I've set up EchoLink for Windows via Wine and get audio
> kicked back to me from the EchoLink test site. So that tells me my
> firewall settings are correct.
Not necessarily. When you connect to the test site, you are initiating
the connection, so your firewall adjusts to allow the Echolink port
access back to your PC. For proper incoming operation, you need to
setup port forwarding from your firewall back to your particular PC.
When I was first setting up my system without the firewall correctly
set, I found that the remote test server would connect fine, but the
incoming audio only worked *after* I had transmitted. In other words, I
would miss the audio blurb "Welcome to the..." but otherwise everything
else worked fine. If you too are missing this, I would highly suspect
the firewall settings.
Also, have you tried using the native Qtel client to connect to the test
server? To be honest, I have not really used Qtel much, but I am pretty
sure that it will work as well, if not better, than using Wine and the
> I'm sure I'm overlooking something
> ridiculously obvious, but...any suggestions?
The Echolink site has some good information on troubleshooting such
> Do I need to install
> svxlink in addition to Qtel? Or is Qtel a standalone?
I would think it should work by itself, but again, I have not really
used Qtel much myself.
> With best regards,
Good luck Pete, and please keep us posted on your progress.
73 de Tim
Tim Miller WB0RXX [EN24dw]
SvxLink v0.9.0rc1 (Apr 25 2007)/Slackware 10.1/P200 MHz/64 MB