also, lets not forget about duplex=0
From: Steve Rodgers <hwstar@rodgers.sdcoxmail.com> To: pcfrover@tcomeng.com, Asterisk Repeater Controler <app_rpt@lists.illiana.net> CC: telesistant@hotmail.com Subject: Re: [App_rpt] Passing DTMF? Date: Fri, 27 Oct 2006 20:15:21 -0700 MIME-Version: 1.0 Received: from sv.qrvc.com ([68.15.19.112]) by bay0-mc10-f9.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 27 Oct 2006 20:15:52 -0700 Received: from steverod.sv.qrvc.com (steverod.sv.qrvc.com [192.168.17.10])by sv.qrvc.com (Postfix) with ESMTP id 3F1DC4204BD;Fri, 27 Oct 2006 20:15:22 -0700 (PDT) X-Message-Info: LsUYwwHHNt2kboKMuduNa7Os9cSSI6xecS6toF5roo4= User-Agent: KMail/1.9.1 References: <000c01c6f96b$047f3420$6301a8c0@DEN> Return-Path: hwstar@rodgers.sdcoxmail.com X-OriginalArrivalTime: 28 Oct 2006 03:15:53.0089 (UTC) FILETIME=[60394F10:01C6FA3F]
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@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt