[arm-allstar] dtmf macros for repeater control

Robert Conklin n4wgy.ham at gmail.com
Sun Dec 27 22:06:07 EST 2015


Thanks for that acknowledgement David.
I would put my money where my mouth is if I knew the difference between
winding my butt or scratching my watch when it comes to software
development.
What I can do is apply the all powerful rule of "Light but Consistent
pressure" against stodginess and beg software folks like yourself to help
put ammo in my bullet box to fight it.

Rob Conklin
*N4WGY <http://qrz.com/db/N4WGY>*

On Sun, Dec 27, 2015 at 8:57 PM, David McGough <kb4fxc at inttek.net> wrote:

>
> Rob, *sigh* ...Yes, you are correct!
>
> On Sun, 27 Dec 2015, Robert Conklin wrote:
>
> > Thanks everyone for your thoughtful and informative inputs, excellent
> stuff.
> >
> > As reliable and agile as the AllStar system may for repeater control,
> there
> > is a multitude of legacy hardware based systems out there that are are
> > owned by municipalities and large repeater associations. These systems
> are
> > not going to be replaced anytime soon with more modern systems,
> regardless
> > of the validity of any argument that could be brought up to do so.
> >
> > The reasons for this stodginess are fodder for much debate, perhaps in
> > another thread.
> >
> > During that interim it would powerful to be able to propagate dtmf thru
> > allstar to control the behaviors of those legacy controllers. The agility
> > to work reliably alongside and with legacy repeater controllers would
> make
> > a real and present argument to eventually replace those older controllers
> > with these more reliable and agile tools.
> >
> > Rob Conklin
> > *N4WGY* <http://qrz.com/db/N4WGY>
> >
> > On Sun, Dec 27, 2015 at 4:49 PM, David McGough <kb4fxc at inttek.net>
> wrote:
> >
> > >
> > > Hi Everyone,
> > >
> > > Ah. DTMF propagation. Hum. Well, there are a some areas of AllStar that
> > > are weak in performance when compared to typical analog controllers,
> and
> > > IMO, this is one of them.  I agree with Willem's and Rob's comments
> about
> > > propagate_dtmf and related functionality--I've had less than
> satisfactory
> > > results as well, for several reasons (that I won't elaborate on just
> now).
> > >
> > > My solution has been to add several hacks to the app_rpt source code,
> but,
> > > even this still has rough edges, partly due to imperfect muting of the
> > > source DTMF signaling.
> > >
> > > Another possibility might be to add DTMF generation macros in the
> dialplan
> > > (extensions.conf file).
> > >
> > > I'll investigate this further. It has been been on my to-do list a long
> > > time.  I've got an SCOM 7330 and Link-Comm club sitting on the shelf I
> can
> > > experiment with--both of these controllers got replaced by AllStar
> > > controllers and honestly, I've never looked back!
> > >
> > >
> > > 73, David KB4FXC
> > >
> > >
> > >
> > >
> > >
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20151227/9a974c36/attachment.html>


More information about the arm-allstar mailing list