Re: [Svxlink-devel] Repeater RF audio not going out internet

[David R. <k9...@gr...>]

* Rob Janssen <pe...@am...> [2015-04-07 22:24]:
> 
> No, this audio is not sent to echolink.  This is done to allow the echolink user to
> transmit quickly when someone releases the mike.  The long gaps to allow echolink
> stations to transmit are not required on an svxlink repeater, especially not when
> using Qtel as a client.  Of course, it means that the echolink user does not experience
> the "sound" of the repeater.  (ID, roger beep etc)
> 
> Note that "the squelch is open" and "the repeater is open" are two different things.
> Check the OPEN_ON setting so it opens on SQL when you want that.

This is a good point.  There's potentially some miscommunication in the
terms being used to describe what's happening.  What I'm trying to fix
is:

1. Ham A with an HT keys up and transmits to RF repeater at 440.150
2. RF Repeater re-transmits and my mobile receives the RF audio
3. Mobile sends to the soundcard input of my svxlink node
4. svxlink takes that input and sends out to the echolink network
5. echolink client receives the audio

The part I'm trying to fix is step #4.  

Looking at the OPEN_ON options in my config, it's currently set for
OPEN_ON_1750, which doesn't actually help me much.  If I take your
meaning of "Note that "the squelch is open" and "the repeater is open"
are two different things." correctly, what you are saying is the svxlink
"repeater" won't do anything with the RF audio if it isn't told to
"open" first.  In my case, that would mean it would never "open" because
I'm configured to open on a tone burst that never happens.

In other words, I'm using SQL_DET=VOX in my Rx1, svxlink is seeing the
audio coming in, but the RepeaterLogic isn't set correctly to actually
use it.


-- 
David, K9DWR
k9...@gr...