We are having issues with the unit connected to a small handheld that connects via RF to a UHF repeater in the next room then and that repeater connects to a VHF mountain top repeater for greater distance.
The issues is every time the repeater IDs, or keys up it is activating the Echolink. We need to know what Allstar settings need to be set to pickup voice only.
Another Echolink node in the near by county not using Allstar can connect but it’s not getting any auido back and forth.
Our Echo Link K5EMO-R is working fine on PC’s Smart Phones and allows connection via my Allstar Clear Node.
Your problem is an old one, and proper engineering of the link to the repeater is needed to resolve it. Tinkering with the software on the node won’t provide an acceptable solution.
There are a few options to fix this issue and stop repeater IDs getting into Echolink:
Good (and relatively simple). Have the repeater generate CTCSS only when there is a signal on the input. The node radio is set to decode the CTCSS tone, and will only receive audio when there’s a signal on the repeater input. While you’re at it, ditch the VOX and use a hardwired CTCSS Valid (or CTCSS AND COS) signal instead.
Better (but expensive) Install a dedicated duplex radio link between the node and repeater.
Best (but requires Internet and node at the repeater site) - install the node at the repeater, directly connected to a link port on the controller.
Any of these solutions will work well.
As for the other repeater having audio issues connecting to yours, that’s something I’d need to see for myself.
There is a simple solution that is cheap as well.
Have the elink connection on a private node where all telemetry is off.
ie
[1951] ; Echolink -R
rxchannel = dahdi/pseudo
duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time.
hangtime = 0 ; squelch tail hang time 0
althangtime = 0 ; longer squelch tail hang time 0
holdofftelem = 1 ; Hold off all telemetry when signal is present on receiver or from connected nodes
; except when an ID needs to be done and there is a signal coming from a connected node.
telemdefault = 0 ; 0 = telemetry output off.
telemdynamic = 0 ; 0 = disallow users to change the local telemetry setting with a COP command,
linktolink = no ; disables forcing physical half-duplex operation of main repeater while
; still keeping half-duplex semantics (optional)
nounkeyct = 1 ; Set to a 1 to eliminate courtesy tones and associated delays.
totime = 180000 ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)
You simply connect your primary node to the echolink node and no telemetry will broadcast on the elink node/network. And you have a bit more control of it.