[App_rpt] Passing DTMF?
Gary Young
pcfrover at tcomeng.com
Sat Oct 28 16:56:03 UTC 2006
With these settings I get a very short burst of the dtmf propagated, very
short.
Is there a way to make the dtmf burst longer in duration?
The inxlat and outxlat do not seem to do anything with these settings.
propagate_dtmf = yes
linktolink = yes
inxlat = 7
outxlat = 0
Gary
> -----Original Message-----
> From: Steve Rodgers [mailto:hwstar at rodgers.sdcoxmail.com]
> Sent: Friday, October 27, 2006 8:15 PM
> To: pcfrover at tcomeng.com; Asterisk Repeater Controler
> Cc: telesistant at hotmail.com
> Subject: Re: [App_rpt] Passing DTMF?
>
>
> Gary,
>
> We have some functionality for this when operating a node as
> a bridge to a
> legacy RF-linked system. (We do this on the Calnet node)
>
> There are settings to faclitate this in rpt.conf:
>
> propagate_dtmf
> linktolink
> notelemtx
> inxlat
> outxlat
>
> They're not documented in the rpt. conf file yet, so you'll
> have to look at
> the app_rpt.c source file to figure out how to use them.
>
> The problem comes when you want to pass * and #. Since these
> mean something to
> the app_rpt command decoder, they need to be escaped with a 2
> digit sequence.
> When you enable command passthrough on a node acting as a bridge, *
> traditionally becomes *7, and # becomes *0. This is true for
> all app_rpt
> commands directed at that node as well. This is what the
> inxlat and outxlat
> are used for.
>
>
> Steve
>
>
>
> On Thursday 26 October 2006 18:55, Gary wrote:
> > Is there a way to open up a Link Port or Remote Base port
> to pass DTMF
> > Audio?
> >
> > Gary
> >
> >
> > _______________________________________________
> > App_rpt mailing list
> > App_rpt at lists.illiana.net
> > http://lists.illiana.net/mailman/listinfo/app_rpt
>
More information about the App_rpt-users
mailing list