[App_rpt] system architecture and implimentation

Tue Nov 14 00:01:07 UTC 2006

These are some excellent questions.

First of all, app_rpt does not have to talk to the radio over one our 
standard interfaces. It can
use anything that looks like a 4 wire (not 2 wire with unacceptable 
trans-hybrid loss for a full-
duplex channel) E&M circuit. This includes a channel on a channelized T-1 or 
E-1.

Given that, you could have an architecture where on each hill you have a 
pair of t1's (one
going to the next hop, one coming from the last hop), and they go into some 
sort of a
DACS/Channel bank (like the Adtran TSU-120 or something) which could pick 
off 1 channel
to run a radio on the hill and pass the rest down the chain. At some point a 
t1 could
end up on the ground where it goes into an asterisk box, which can use the 
T1 channels
as E&M interfaces and app_rpt can do that nicely. Of course you would need 
to make
an ARIB similar to ours, but uses E&M instead of 2 pots interfaces.

Or, you could use your t1's as unchannelized data T1's and put routers on 
each hill and an
asterisk box on each hill to do the radio stuff for that hill only.

If it were me, Id multiplex all the radio channels onto the t1's and bring 
them down the hill
to ground level where possible.

In either case, the asterisk boxes talk to each other over VOIP, so any 
communications done
between has to be IP. If you want them to talk to each other over the T1's 
then, you
are going to need to dedicate some of the T1 channels for data regardless 
(of course,
this still can be done with just asterisk boxes and no external routing 
hardware, if desired).

>From: "Eric Fort" <eric.fort at gmail.com>
>Reply-To: Asterisk Repeater Controler <app_rpt at lists.illiana.net>
>To: App_rpt at lists.illiana.net
>Subject: [App_rpt] system architecture and implimentation
>Date: Mon, 13 Nov 2006 12:00:12 -0800
>MIME-Version: 1.0
>Received: from lists.illiana.net ([207.227.243.140]) by 
>bay0-mc11-f19.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Mon, 
>13 Nov 2006 12:00:20 -0800
>Received: (qmail 23425 invoked from network); 13 Nov 2006 20:00:19 -0000
>Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1)  by 0 with SMTP; 13 
>Nov 2006 20:00:19 -0000
>Received: (qmail 23416 invoked from network); 13 Nov 2006 20:00:16 -0000
>Received: from wr-out-0506.google.com (64.233.184.231)by 0 with SMTP; 13 
>Nov 2006 20:00:16 -0000
>Received: by wr-out-0506.google.com with SMTP id i20so144574wrafor 
><App_rpt at lists.illiana.net>; Mon, 13 Nov 2006 12:00:13 -0800 (PST)
>Received: by 10.90.27.6 with SMTP id a6mr3424392aga.1163448012761;Mon, 13 
>Nov 2006 12:00:12 -0800 (PST)
>Received: by 10.90.114.3 with HTTP; Mon, 13 Nov 2006 12:00:12 -0800 (PST)
>X-Message-Info: txF49lGdW43riucQGbxnnM06JaLVQB+3D0Mqg36IJ+g=
>Return-Path: <eric.fort at gmail.com>
>Delivered-To: mailman-App_rpt at lists.illiana.net
>DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; 
>d=gmail.com;h=received:message-id:date:from:to:subject:mime-version:content-type;b=NdicoImuxGY2VH0kKdhc6gx5WrUk6UJ4ZX3ezw8b0ORQsmJn4a45hVH6ALzPNn6wKRaZG9RJukuwRtAwrjp43ZD9CLhCkVxRZDT79kYhg48O4ghUvdNQkvv6hdHQ9o7H+g+AzLgHVwcri03yNGliS1Rkd+2VJKddwp8TA+EKBpo=
>X-BeenThere: app_rpt at 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 at lists.illiana.net?subject=unsubscribe>
>List-Archive: <http://lists.illiana.net/pipermail/app_rpt>
>List-Post: <mailto:app_rpt at lists.illiana.net>
>List-Help: <mailto:app_rpt-request at lists.illiana.net?subject=help>
>List-Subscribe: 
><http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-request at lists.illiana.net?subject=subscribe>
>Errors-To: app_rpt-bounces at lists.illiana.net
>X-OriginalArrivalTime: 13 Nov 2006 20:00:21.0237 (UTC) 
>FILETIME=[5972E250:01C7075E]
>
>I have floated the idea of possibly using asterisk/app_rpt to update an
>existing linked system which currently covers multiple states.  In
>discussing this some questions of architecture have come up so I'm posing
>them to the list below.  Many if not most of our sites have no access to
>telecom facilities, can be inaccessible for about 4 months out of the year,
>and the temperature in the buildings can reach vast extremes.  Currently we
>link over radio channels on the 440 band but are working to move to
>microwave t-1 links with t-1 radios in the ham band and channel banks
>splitting out the audio.
>
>What signaling can be done over the existing single channel links to
>interface with legacy systems and how can the app_rpt boxes in the system
>signal each other over these links to convey status and signaling
>information between them?
>
>How would you go about addressing the environmental concerns above or
>architecting around them?
>
>Thanks,
>
>Eric
>KG6KQT

>_______________________________________________
>App_rpt mailing list
>App_rpt at lists.illiana.net
>http://lists.illiana.net/mailman/listinfo/app_rpt