[arm-allstar] Supermon issues

Wed Apr 10 22:59:44 EDT 2019

Yes you could BUT it is generally not recommended to change the general
connect/disconnect commands if you are using it publicly. If everyone did
that we would have no common connection method. I suspect you are doing it
to eliminate someone from connecting? There is a ban/allow script and a
button in Supermon to do that. Using DTMF to be more secure is kind of
useless for anyone that really wants to get in as all they have to do is
read the DTMF off air!

*73 Doug*

*WA3DSP*

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

On Wed, Apr 10, 2019 at 10:48 PM "Jay Urish via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> So theoretically,
>
> If I wanted a site access code setup, I could add some digits like this
>
> and make 9321 my site access code right?
>
>
> 93211=ilink,1
>   ; monitor link = *2<node>
> 93212=ilink,2
>   ; connect link transceive = *3<node>
> 93213=ilink,3
>   ; remote command = *4<node>
> 93214=ilink,4
>   ; execute macro = *5<macro#>
> 93215=macro,1
>
>
>
>
>
> On 4/10/19 9:13 PM, "Doug Crompton via ARM-allstar" wrote:
> > DTMF commands are mapped to ilink or other commands in the functions
> stanza
> > of rpt.conf.  Here is an example -
> >
> > The DTMF command on the left preceded by the lead in character (*) is
> > mapped to the command on the right.
> >
> > [functions]
> >
> >   ; disconnect link = *1<node>
> > 1=ilink,1
> >   ; monitor link = *2<node>
> > 2=ilink,2
> >   ; connect link transceive = *3<node>
> > 3=ilink,3
> >   ; remote command = *4<node>
> > 4=ilink,4
> >   ; execute macro = *5<macro#>
> > 5=macro,1
> >
> >   ; system status
> > 70=ilink,5
> >   ;  disconnect permanently connected link = *71<node>
> > 71=ilink,11
> >   ; connect link permanent monitor = *72<node>
> > 72=ilink,12
> >   ; connect link permanent transceive = *73<node>
> > 73=ilink,13
> >   ; play full system status
> > 75=ilink,15
> >   ; disconnect all links
> > 76=ilink,6
> >   ; reconnect previously disconnected links
> > 77=ilink,16
> >   ; permanently monitor link – local Monitor only
> > 78=ilink,18
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Wed, Apr 10, 2019 at 7:52 PM "Mike Sullivan via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> That email posted to the list about 2 hours after I solved it. Restarted
> >> the node and all was fine lol. It was weird. All seems to be working
> now,
> >> no issues yet.
> >>
> >> Slightly OT but since I’m replying anyways.. how hard is it to change
> the
> >> DTMF commands?
> >>
> >> On Wed, Apr 10, 2019 at 19:13 "Doug Crompton via ARM-allstar" <
> >> arm-allstar at hamvoip.org> wrote:
> >>
> >>> Mike,
> >>>
> >>>   The update would not have effected anything previously setup. Go over
> >> the
> >>> setup again. Is the allmon.ini file pointing to the correct manager Ip
> >>> address? 127.0.0.1 for same server or local IP address of another
> server
> >> on
> >>> your LAN or public IP if outside. Correct user/pass and same user/pass
> in
> >>> the manager.conf file? If the manager you are trying to reach is not on
> >> the
> >>> same server you need to set the bind address at that manager to 0.0.0.0
> >> not
> >>> 127.0.0.1. If it is outside your LAN you also need to port forward port
> >>> 5038 and you should firewall it as per the howto at hamvoip.org.
> >>>
> >>>
> >>> *73 Doug*
> >>>
> >>> *WA3DSP*
> >>>
> >>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>
> >>>
> >>> On Wed, Apr 10, 2019 at 5:45 PM "Mike Sullivan via ARM-allstar" <
> >>> arm-allstar at hamvoip.org> wrote:
> >>>
> >>>> I'm working on setting up Supermon on our node.. been working on
> >> getting
> >>>> everything set up. I have the page running, been trying to figure out
> a
> >>>> login issue, but can't figure out why. I did an update to be safe
> >> (after
> >>>> remembering the cosmetic update the other day) and now when I log in,
> >> the
> >>>> page is giving me "Could not login to Asterisk Manager".. any reason
> >> why?
> >>>> It was working before I ran the node update.
> >>>>
> >>>> Mike
> >>>> _______________________________________________
> >>>>
> >>>> 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
> > _______________________________________________
> >
> > 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