Can we make an IAXY ata device work then? that works using IAX not SIP. Thank You, Brian N2KGC -----Original Message----- From: Stephen Rodgers [mailto:hwstar@rodgers.sdcoxmail.com] Sent: Monday, March 12, 2007 11:53 AM To: Asterisk Repeater Controler Subject: Re: [App_rpt] Remote Base IAX2 already has radio support built-in with KEY and UNKEY messages in the control frames. This is how we link to other systems in app_rpt. IAX ATA's would have to be modified handle these control frames with a special configuration setting. For receive, the ATA would have to send a KEY message every time the loop is closed, and an UNKEY message every time the loop is opened. For transmit, the ATA would have to apply battery when the KEY message is received, and remove battery when the UNKEY message is received. Also for transmit, there needs to be a watchdog function to kill the TX if the connection is lost or degraded. Steve.
In my looking at this issue I noted that iax2 is headed for ietf standardization and is currently in draft. me thinks that a few choice commands placed in the iax2 protocol to do this in call signalling would be quite nice. (I may ask a friend of mine who works at digium about that) If IAX2 had the commands to do polarity reversal in call what would it take to have app_rpt control it?
Eric
On 3/11/07, Jim Duuuude <telesistant@hotmail.com> wrote:
No SIP ATA's even come CLOSE to supporting what we need.
What they call battery reversal is an indication that the call has answered on the far end which may happen ONLY once per call (if it un-answers on the far end it terminates the call).
Our needs are to have a SIP call initiated and for it to say up (rather permanently or so) and to have the ability to send on-hook/off-hook states many times as needed. No one does this or even has a concept of this.
From: Stephen Rodgers <hwstar@rodgers.sdcoxmail.com> Reply-To: Asterisk Repeater Controler <app_rpt@lists.illiana.net> To: Asterisk Repeater Controler <app_rpt@lists.illiana.net> Subject: Re: [App_rpt] Remote Base Date: Sun, 11 Mar 2007 13:58:52 -0700 MIME-Version: 1.0 Received: from marauder.illiana.net ([64.212.212.35]) by bay0-mc7-f20.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sun, 11 Mar 2007 13:58:35 -0700 Received: (qmail 26925 invoked by uid 1484); 11 Mar 2007 20:58:34 -0000 Received: from 127.0.0.1 by marauder (envelope-from <app_rpt-bounces@lists.illiana.net>, uid 71) with qmail-scanner-2.01 (clamdscan: 0.84/2481. Clear:RC:1(127.0.0.1):. Processed in 0.039165 secs); 11 Mar 2007 20:58:34 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 11 Mar 2007 20:58:34 -0000 Received: (qmail 26806 invoked by uid 1484); 11 Mar 2007 20:58:28 -0000 Received: from 68.15.19.112 by marauder (envelope-from<hwstar@rodgers.sdcoxmail.com>, uid 71) with qmail-scanner-2.01 (clamdscan: 0.84/2481. Clear:RC:0(68.15.19.112):. Processed in 0.288186 secs); 11 Mar 2007 20:58:28 -0000 Received: from wsip-68-15-19-112.sd.sd.cox.net (HELO sv.qrvc.com)(68.15.19.112) by 0 with SMTP; 11 Mar 2007 20:58:26 -0000 Received: from [192.168.17.10] (steverod.sv.qrvc.com [192.168.17.10])by sv.qrvc.com (Postfix) with ESMTP id F3EAB4207F5for <app_rpt@lists.illiana.net>; Sun, 11 Mar 2007 12:58:23 -0800 (PST) X-Message-Info: txF49lGdW42qcnmnBI8UHq9RUd57UmnYrrjh70Y4AzY= Return-Path: <hwstar@rodgers.sdcoxmail.com> Delivered-To: mailman-app_rpt@lists.illiana.net User-Agent: Thunderbird 1.5.0.9 (X11/20070103) References: <da99ac960702270929j376a4da6mbbb88e4687313b98@mail.gmail.com> < 45E4B697.6060900@rodgers.sdcoxmail.com>< 2ad2af430703111219p3940b2d2pdff030f1667cb31d@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 X-BeenThere: app_rpt@lists.illiana.net X-Mailman-Version: 2.1.6 Precedence: list List-Id: Asterisk Repeater Controler <app_rpt.lists.illiana.net> List-Unsubscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto: app_rpt-request@lists.illiana.net?subject=unsubscribe> List-Archive: <http://lists.illiana.net/pipermail/app_rpt> List-Post: <mailto:app_rpt@lists.illiana.net> List-Help: <mailto:app_rpt-request@lists.illiana.net?subject=help> List-Subscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto: app_rpt-request@lists.illiana.net?subject=subscribe> Errors-To: app_rpt-bounces@lists.illiana.net X-OriginalArrivalTime: 11 Mar 2007 20:58:35.0306 (UTC) FILETIME=[08D200A0:01C76420]
Eric,
You can research this further, but I'm not convinced SIP ATA's give a fine enough level of control for polarity reversal, or battery interruption.
What would be required are special SIP commands which tell the far end Asterisk server when a phone goes off hook (for RX), and special SIP commands for applying and removing battery for the TX loop.
For RX, SIP ATA's do not work like this. When a user goes off hook, a LOCAL dialtone is generated in the ATA, and only when the digits are dialed which match a route programmed into the ATA, does the ATA make connection with the Asterisk server. For TX, SIP ATA's provide battery all of the time and cannot be set up to interrupt battery on an ad-hoc basis.
Even if all of the above were eventually sfound to be supported, App_rpt wuld have to undergo a significant rewrite to support SIP on the repeater port. A lot of things in app_rpt depend on the support Zaptel provides.
Eric Fort wrote:
Steve, Yes I read your reply below...then I googled and composed this query. Why will it not work? how can it work?
(Worst case a patch to asterisk may come to mind since we are running seperate channels for tx/rx anyway)
All of the ata's below (the majority of the market) would appear to support polarity reversal now how can that feature be used with an arib board to place a remote node at the end of an ethernet cable across the network (where the controlling asterisk box is say on another continent)?
cisco ata186 and ata188
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administratio n_guide_chapter09186a0080160f73.html#1021012
SIPURA SPA-3000 http://www.sipura.com/Documents/SipuraSPAUserGuidev2.0.9.pdf also SPA-2000, SPA-2100, SPA-1001
ustarcom http://www.utstar.com/Document_Library/0043.pdf
HandyTone 286 http://www.grandstream.com/user_manuals/HandyTone.pdf
Grandstream Handytone ATA-496 http://www.grandstream.com/user_manuals/HT-496.pdf
Grandstream Handytone ATA-386 http://www.grandstream.com/user_manuals/HandyTone-386UserManual.pdf
Grandstream Handytone ATA-488 http://www.grandstream.com/user_manuals/HT488UserManual.pdf
Grandstream Handytone ATA-486 http://www.grandstream.com/user_manuals/HandyTone-486UserManual.pdf
Eric
On 2/27/07, Stephen Rodgers < hwstar@rodgers.sdcoxmail.com> wrote:
ATA's don't support the line signalling methods required by the ARIB
to
indicate PTT and/or COR presence.
Steve.
David Craig wrote:
Can App_rpt be used with an ATA for a simplex or half duplex remote base. The example might be an Grandstream HandyTone 286 with the FXS port connected ARIB.
I have a situation where I need a very small radio interface and my asterisk box will be remote via a high speed connection.
Thanks for any help.
David
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
------------------------------------------------------------------------
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt