[arm-allstar] Echolink Connect announcements
Doug Crompton
wa3dsp at gmail.com
Mon Sep 3 12:57:06 EDT 2018
Mike,
We are going to look at this later today. I had not paid much attention to
it in the past. I think the bottom line is that telemdefault effects ALL
telemetry so it would also effect the telemetry from Echolink. Perhaps we
need an allstardefault also so that could be controlled independently of
Echolink. Some may want to be able to hear ALL echolink connect messages
while limiting allstar connect messages and currently that would not be
possible. The same would probably be true for IRLP with the irlpann command.
Allstar early on was kind of hodge·podge added on to. Echolink and IRLP
came later and this is the reason some of these commands work (or don't
work) the way you would expect them to. It would be nice to have a master
command to control telemetry which is what telemdefault is now but also
individual commands for each channel - Allstar, Echolink, IRLP, and in the
future DMR. Hopefully we can get to that point.
As for the NODE/CALL and just CALL in eannmode we will check.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Mon, Sep 3, 2018 at 12:15 PM "Mike Besemer via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Doug,
>
> Tried the following:
>
> eannmode=2 ; 0 = do not announce Echolink nodes at all
> ; 1 = announce only the node number
> (Allstar-translated)
> ; 2 = announce only the call of the
> echolink station
> ; 3 = announce both
>
> echolinkdefault=1 ; 0 = telemetry output off
> ; 1 = telemetry output on
> ; 2 = timed telemetry output on command
> execution and for a short time thereafter
> ; 3 = follow local telemetry mode
>
> telemdefault=2 ; 0= voice telemetry off
> ; 1= on
> ; 2= Only your telemetry actions then
> mutes in 1 minute
>
> With this configuration, there is no RF announcement when connecting to
> Echolink.
>
> Changing telemdefault=1 produces a connect announcement... BUT the
> announcement consists of both the phonetic callsign of the connecting
> station AND the node number (Whiskey Mike Four Bravo connected to Node
> 48166). Maybe I'm misunderstanding the purpose of eannmode, but I thought
> with eannmode=2, I would only hear the phonetic call of the connecting
> station and not node number as well. Am I confused again?
>
> What I'd REALLY like to hear is just the callsign (not phonetically) of
> the connecting station, the way it's done in Echolink (Connected W M 4 B);
> not sure why the phonetics are necessary. I suppose that since this is a
> worldwide network the phonetics might be handy occasionally, but since the
> voice is digital it seems kinda redundant to use phonetics.
>
> 73,
>
> Mike
> WM4B
>
>
> From: Doug Crompton [mailto:wa3dsp at gmail.com]
> Sent: Saturday, September 1, 2018 11:30 PM
> To: ARM Allstar; Mike Besemer
> Subject: Re: [arm-allstar] Echolink Connect announcements
>
> Mike,
>
> Try
>
> telemdefault=2 and echolinkdefault=1
>
> This should always announce echolink and only announce local RF Allstar
> connects/disconnects. Let me know if that works.
>
> The default echolinkdefault is 2 but that would mean you would only hear
> local echolink connects and disconnects. So that is probably the problem.
> Once it muted if someone came in from outside you would not hear it with
> option 2. I need to get that command added in for the download image so
> people see it. There are probably several seldom used commands not listed
> in rpt.conf but most any command you see in documentation is usable in the
> code.
>
> The echolinkdefault command should be added after the eannmode command in
> rpt.conf for clarity. You can change the eannmode command to the type of
> output you want. When you change these commands you need to reload the
> rpt.conf file or restart Asterisk.
>
> The question in my mind are the telemdefault and echolinkdefault
> independent of one another or does the telemdefault have an effect on the
> echolink telemetry in addition to the Allstar telemetry. I would hope they
> would be independent.
>
> The only way to really test this is to use the above commands and connect
> via echolink from the outside several minutes after you restart it and see
> if you get the connect message.
>
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
>
>
>
>
>
> On Sat, Sep 1, 2018 at 7:46 PM Mike Besemer <mwbesemer at cox.net> wrote:
> Doug,
>
> I came across this page while I was looking for a solution for this
> issue: http://docs.allstarlink.org/drupal/node/126
>
> Neither echolinkdefault nor echolinkdynamic is available in my Nodes
> Stanza; only eannmode, which is set to 2.
>
> Would adding echolinkdefault=1 (or 2) resolve my issue?
>
> 73,
>
> Mike
> WM4B
>
> From: Doug Crompton [mailto:wa3dsp at gmail.com]
> Sent: Saturday, September 1, 2018 7:20 PM
> To: Mike Besemer
> Cc: ARM Allstar
> Subject: Re: [arm-allstar] Echolink Connect announcements
>
> Mike,
>
> telemdefault=1 means you will hear all allstar announcements. Is that
> what you want? telemdefault=2 is the default which means you only hear RF
> connects and disconnects on your own server followed by a delay and it
> mutes other telemetry..
>
> Perhaps this is not working correctly as Echolink should do the same thing
> as Allstar. If you have telemdefault=2 it does not work?
>
>
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
>
> On Sat, Sep 1, 2018 at 6:53 PM Mike Besemer <mwbesemer at cox.net> wrote:
> I got it, Doug. I found an old email trail and set telemdefault=1. That
> look care of it.
>
> Thanks,
>
> Mike
> WM4B
>
> -----Original Message-----
> From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> "Doug Crompton via ARM-allstar"
> Sent: Saturday, September 1, 2018 5:24 PM
> To: ARM Allstar
> Cc: Doug Crompton
> Subject: Re: [arm-allstar] Echolink Connect announcements
>
> Mike,
>
> Echolink like Allstar will only announce on the RF link it is connected
> to. It is localplay like other messages. If you have Echolink on a node by
> itself without a radio you will not hear it. That is the one downside of
> having Echolink on a separate node. It that your scenario?
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Sat, Sep 1, 2018 at 5:08 PM "Mike Besemer via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Is anyone else not hearing Echolink Connect announcements? I has
> eannmode
> > in rpt.conf set to 1 and was hearing nothing. Just reset it to
> eannmode=2
> > and did an ASTModule/RPT Reload via SuperMon and still don't hear any
> > connection announcements.
> >
> > Mike
> > WM4B
> > _______________________________________________
> >
> > 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
> >
> _______________________________________________
>
> 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
>
> _______________________________________________
>
> 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
>
More information about the arm-allstar
mailing list