[arm-allstar] Supermon issues

Thu Apr 11 21:33:17 EDT 2019

Echolink can announce calls, nodes, or both -

;eannmode=1
                                ; Echolink announcement mode
                                ; Default: 1 = Say only node number on
echolink
                                ; connects. 2 = say phonetic call sign only
on
                                ; echolink connects. 3 = say phonetic call
sign
                                ; and node number on echolink connects

On telemetry the answer is no you cannot change it other than changing node
numbers to calls or something else. It is best to leave it tuned off for
outside connects using telemdefault=2 whcih is the default.

*73 Doug*

*WA3DSP*

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

On Thu, Apr 11, 2019 at 9:29 PM "Mike Sullivan via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Okay, I'll probably leave it as is, unless we end up needing to change it
> for some reason. A couple more grievances (is it too late for the airing of
> grievances?) that I wanted to ask about..
>
> 1. Is it possible to show node callsigns versus #'s on Echolink? Some of or
> members liked being able to see the callsigns instead of just node #'s.
> 2. On the telemetry voice, is there a way to change the voice itself as
> well as speed it up? And is it possible to pronounce short letters instead
> of phonetics when announcing calls, similar to what the Echolink PC app
> does?
>
> On Wed, Apr 10, 2019 at 10:14 PM "Doug Crompton via ARM-allstar" <
> arm-allstar at hamvoip.org> 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