[arm-allstar] Unknown new tone

[Bryan St Clair]

Turns out it was the *4 feature was stuck on/open?

I had sent a *4 command to a node the day before and for some reason, this
tone started after.  A fellow HAM told me to send a # over DTMF on the node
and it would close the open *4 feature.   Sent the # and it went away.  I
had no other connections and even rebooted without success.

Not sure how it got stuck on/open as I sent a simple disconnect command as
I have done in the past without issue.

3rd tone is gone now.  Thanks for the reply.

On Wed, Feb 19, 2020, 10:17 David McGough <kb4fxc at inttek.net> wrote:

>
> Is it possible the 3rd tone is a repeater courtesy tone, from a repeater
> linked in via a simplex node?  The reason I ask is that I've can generate
> the exact style of tone sequence when linking my VHF (AllStar) remote
> bases (mode: duplex=0, linktolink=yes) to repeaters.
>
>
> 73, David KB4FXC
>
>
>
> On Wed, 19 Feb 2020, "Bryan St Clair via ARM-allstar" wrote:
>
> > I suddenly have a new tone on a linked unkey.  A solid beep at the end of
> > my current double unkey tone.  Heard here (3rd tone is unknown and new)
> >
> > Any ideas of where to identify it in the config?
> >
> > my ct8 looks like it has been for well over a year, no change yet the
> audio
> > is now different.
> >
> >
> https://drive.google.com/file/d/1jXAN6bRRH7bhMxk8PhmaBstoOwBrldre/view?usp=sharing
> >
> > Thanks for any help
> >
> >
>
>