[arm-allstar] App_rpt Variables for Dialplan Use?

[Lee Woldanski]

Yep, I can build a template in the dialplan and go that route. Figured I
would check if there was an undocumented feature.


Thanks!

On Fri., May 22, 2020, 2:03 p.m. "Doug Crompton via ARM-allstar", <
arm-allstar at hamvoip.org> wrote:

> Lee,
>
>  I don't believe there is any knowledge of what node called the autopatch.
> I suspect a global variable could be added to do that but in the meantime a
> work around would be to have each node call a different context in
> extensions.
>
> In rpt.conf -
>
> [functionsnode1]
> 61....   context=node1
>
> [functionsnode2]
>
> 61....  context=node2
>
> etc.
>
> Then in the extensions you would know what node originated the call.  Would
> this work?
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Fri, May 22, 2020 at 12:55 PM "Lee Woldanski via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Is there a list of variables that app_rpt sets that are available to the
> > rest Asterisk?
> >
> > Specifically, if I call "autopatchup" and send the call to a custom
> context
> > in extensions.conf, I want to know what node that request came from, so I
> > can pass the node number variable to an external script (along with the
> > extension/dtmf string that was dialed).
> >
> > The external script needs the node number to make sure that the node is
> > linked to the hub as part of it's work.
> >
> >
> > Thanks!
> >
> >
> > Lee
> > --
> > Lee Woldanski, AScT
> > VE7FET
> > _______________________________________________
> >
> > 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/4 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/4 web page - http://hamvoip.org
>