[arm-allstar] Echolink Deny=

Sean McCarthy smccarthy61 at gmail.com
Sat Jul 13 22:12:01 EDT 2019


Turns out it was the wildcard a1abc* did the trick...

Thanks!

On Sat, Jul 13, 2019 at 9:52 AM "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Yes permit and deny would never be logically used together. If you are
> permitting it means you are denying all but those permitted so no reason
> for deny and if you are denying you are permitting all but those you are
> denying.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Sat, Jul 13, 2019 at 8:58 AM Paul - KN2R <paulkn2r at gmail.com> wrote:
>
> > Also remember to use permit= or deny=, not both! There seems to be issues
> > using both!
> >
> > -----Original Message-----
> > From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> > "Doug Crompton via ARM-allstar"
> > Sent: Saturday, July 13, 2019 2:26 AM
> > To: ARM Allstar
> > Cc: Doug Crompton
> > Subject: Re: [arm-allstar] Echolink Deny=
> >
> > Also when you enter data in the echolink.conf file you must restart
> > asterisk
> > for it to take effect. You cannot just reload chan_echolink.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sat, Jul 13, 2019 at 12:42 AM Doug Crompton <wa3dsp at gmail.com> wrote:
> >
> > > It should be entered as a1abc*,a2abc*, etc.
> > >
> > > This prevents the call and -L and -R with the call from also
> connecting.
> > > Assuming that is what you want to do.
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > >
> > > On Sat, Jul 13, 2019 at 12:31 AM "Sean McCarthy via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > >> Anyone know why deny=a1abc in echolink.conf wouldn't be preventing
> > >> a1abc from connecting to my node? (a1abc is not the call in case it
> > >> isn't
> > >> obvious)
> > >>
> > >> I know this is not a Hamvoip specific problem, but I find most of us
> > >> stumble across the same issues...
> > >>
> > >> Thanks,
> > >> Sean
> > >> _______________________________________________
> > >>
> > >> 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