[arm-allstar] Couple quirks with Echolink

[Doug Crompton]

Mike,

 No idea on the echolink. Is an Allstar link doing the same thing? Muffled
audio might indicate you need to enable pre-emphasis or disable
de-emphasis.  There is no reason you should have to use notch filters. You
should check the audio coming out with an amplifier to see what it sounds
like. Also consider the source of the echolink signal. Is it from a good
source?

Echolink announcements are on the node that echolink is attached to. It is
set by eanmode in the node section it is attached to in rpt.conf

;eannmode=1
                                ; Echolink announcement mode
                                ; Default: 1 = Say only node number on
echolink
                                ; connects. 2 = say phonetic call sign only
on
                                ; echolink connects. 3 = say phonetic call
sign
                                ; and node number on echolink connects

Remove the semicolon and set the mode.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Wed, Mar 6, 2019 at 4:49 PM "Mike Sullivan via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> All, after a losing battle with using Verizon, we ended up changing to a
> cable landline at our tower site. With this, we have no more
> port/connection issues and our node is finally online. I still have to fix
> a bunch of stuff, which is the reason I'm here. We're using a RPi3
> connected to a RIM-Lite designed for the RC210, plugged into Port 3 with
> our repeater, a VXR-7000 in Port 1.
>
> First off, the audio coming from the interface is absolutely horrible..
> really muffled when going from Echolink to repeater, but fine radio to
> radio and radio to Echolink. notch filters do not help. Any idea what I can
> do to improve it?
>
> Second.. we have had times where the node will be rebooted, and when it
> reboots it dead keys the repeater for a few minutes until the node
> announces the LAN IP, then after the controller times it out, and cancels
> the TO, it will stop.. hasn't done it the past few times, but not sure why
> yet.
>
> Also, even though the option is enabled in rpt.conf, the node is not
> announcing when a user connects/disconnects from Echolink.
>
> I'm sure there will be more things that I will find as we go along.. I'm at
> the tower site currently working on it, so any help is appreciated.
>
> 73 KN4IMU
> Mike Sullivan
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>