[App_rpt] How are Steve and Jim doing?
Nevada Amateur Radio Repeaters, Inc.
w7aor at narri.org
Fri Dec 8 19:49:20 UTC 2006
How are Steve and Jim doing?
-----Original Message-----
From: app_rpt-bounces at lists.illiana.net
[mailto:app_rpt-bounces at lists.illiana.net] On Behalf Of
app_rpt-request at lists.illiana.net
Sent: Friday, December 08, 2006 3:11 AM
To: app_rpt at lists.illiana.net
Subject: App_rpt Digest, Vol 10, Issue 3
Send App_rpt mailing list submissions to
app_rpt at lists.illiana.net
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.illiana.net/mailman/listinfo/app_rpt
or, via email, send a message with subject or body 'help' to
app_rpt-request at lists.illiana.net
You can reach the person managing the list at
app_rpt-owner at lists.illiana.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of App_rpt digest..."
Today's Topics:
1. Re: RE : Configuration Hints for Multiple Radios on 1 node
(Steven Henke)
2. Asterisk controller to a CAT Controller(full duplex) (Will)
3. Re: Asterisk controller to a CAT Controller(full duplex) (Gary)
4. Asterisk Controller to a Cat Controllerl (Will Wright)
5. Re: Asterisk Controller to a Cat Controllerl (Jim Duuuude)
6. Re: Asterisk Controller to a Cat Controllerl (Gary Young)
7. Asterisk Controller and the CAT Controller (Will Wright)
8. DTMF tones not passing to connec to oether nodes (Will)
9. Re: DTMF tones not passing to connec to oether nodes (Gary)
10. Asterick controller to a CAT controller (Will)
11. Re: Asterick controller to a CAT controller (Jim Duuuude)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 Dec 2006 01:29:34 -0500 (EST)
From: "Steven Henke" <sph at xelatec.com>
Subject: Re: [App_rpt] RE : Configuration Hints for Multiple Radios on
1 node
To: f6hqz-m at hamwlan.net
Cc: 'Asterisk Repeater Controler' <app_rpt at lists.illiana.net>
Message-ID: <45452.192.168.1.226.1165300174.squirrel at 192.168.1.226>
Content-Type: text/plain;charset=iso-8859-1
Francois,
With 4 channels running I am sure you can help.
I did get the repeater and simplex stations connecting through iaxRpt but
not as dialup extensions.
I will resume work on this tomorrow and contact you then.
Thank You,
Steve
> Hi Steven and the list.
>
> I have 4 simplex channels into my Asterisk.
> May I can help you a little if you post your config files ?
>
> 73,
> F6HQZ,
> Francois BERGERET.
>
>
> -----Message d'origine-----
> De : app_rpt-bounces at lists.illiana.net
> [mailto:app_rpt-bounces at lists.illiana.net] De la part de Steven Henke
> Envoy? : mardi 5 d?cembre 2006 03:52
> ? : app_rpt at lists.illiana.net
> Objet : [App_rpt] Configuration Hints for Multiple Radios on 1 node
>
>
> Hello,
>
> Just shouting out for some configuration help. My system was up and
> running
> with one simplex radio and I added another ARIB and a repeater over the
> weekend.
>
> I can set up a configuration that works for either the repeater or for the
> simplex radio but not both.
>
> Also I'd like to be able to use the iaxRpt client to connect to either or
> both of the radio's.
>
> I've got a club demo to do so any hints or help would be appreciated.
>
> I'd be glad to call anyone back who can help.
>
> 73,
> Steve Henke, W9SH
> Allstar Link Node 2057 (which is down for local testing and development)
>
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
>
>
------------------------------
Message: 2
Date: Tue, 05 Dec 2006 23:19:10 -0600
From: Will <w4wwm at knology.net>
Subject: [App_rpt] Asterisk controller to a CAT Controller(full
duplex)
To: app_rpt at lists.illiana.net
Message-ID: <457652CE.1090900 at knology.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Gary,
Thanks for responding, I am trying to wire to the repeater port of the
Cat Controller and not to the link port of the Cat controller. I do
know that your first explanation will work, I've had it working. But
will work only from the link port of the Cat Controller. I'm asking is
it possible to make it work from the repeater port (Full duplex) to
Asterisk Controller (full duplex)?
Thanks
Will / W4WWM
------------------------------
Message: 3
Date: Tue, 05 Dec 2006 21:39:22 -0800
From: Gary <gary at tcomeng.com>
Subject: Re: [App_rpt] Asterisk controller to a CAT Controller(full
duplex)
To: Asterisk Repeater Controler <app_rpt at lists.illiana.net>
Message-ID: <4576578A.3050908 at tcomeng.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
The same connections shuold be made to either a link port or a repeater
port.
Set the node definition to:
duplex = 0
which is, no repeat - links only, and it should work.
I have an IRLP node connected this way and it works great.
Gary
Will wrote:
> Gary,
> Thanks for responding, I am trying to wire to the repeater port of the
> Cat Controller and not to the link port of the Cat controller. I do
> know that your first explanation will work, I've had it working. But
> will work only from the link port of the Cat Controller. I'm asking is
> it possible to make it work from the repeater port (Full duplex) to
> Asterisk Controller (full duplex)?
>
> Thanks
>
> Will / W4WWM
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
------------------------------
Message: 4
Date: Wed, 06 Dec 2006 17:28:45 -0600
From: Will Wright <w4wwm at knology.net>
Subject: [App_rpt] Asterisk Controller to a Cat Controllerl
To: app_rpt at lists.illiana.net
Message-ID: <1165447726.3170.7.camel at localhost.localdomain>
Content-Type: text/plain
Gary,
When I define duplex = 0, which means as you said to half duplex would I
have to switch the controller back to 2 wire? Right now it's set to 4w,
full duplex. Thanks
Will / w4wwm
------------------------------
Message: 5
Date: Wed, 06 Dec 2006 17:20:34 -0800
From: "Jim Duuuude" <telesistant at hotmail.com>
Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl
To: app_rpt at lists.illiana.net
Message-ID: <BAY119-F2267D808B094E3F4413A96B1DC0 at phx.gbl>
Content-Type: text/plain; format=flowed
nope, leave it in 4 wire
>From: Will Wright <w4wwm at knology.net>
>Reply-To: Asterisk Repeater Controler <app_rpt at lists.illiana.net>
>To: app_rpt at lists.illiana.net
>Subject: [App_rpt] Asterisk Controller to a Cat Controllerl
>Date: Wed, 06 Dec 2006 17:28:45 -0600
>MIME-Version: 1.0
>Received: from lists.illiana.net ([64.212.212.35]) by
>bay0-mc5-f18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 6
>Dec 2006 15:28:57 -0800
>Received: (qmail 11003 invoked from network); 6 Dec 2006 23:28:53 -0000
>Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 6
>Dec 2006 23:28:53 -0000
>Received: (qmail 10979 invoked from network); 6 Dec 2006 23:28:50 -0000
>Received: from smtp.knology.net (24.214.63.101)by 0 with SMTP; 6 Dec 2006
>23:28:50 -0000
>Received: (qmail 8064 invoked by uid 0); 6 Dec 2006 23:28:48 -0000
>Received: from unknown (HELO ?192.168.1.101?) (24.214.57.115)by
>smtp7.knology.net with SMTP; 6 Dec 2006 23:28:48 -0000
>X-Message-Info: txF49lGdW41zO4Wp2aslw9YW4p5TnIW2dDDtMtcsIB4=
>Return-Path: <w4wwm at knology.net>
>Delivered-To: mailman-app_rpt at lists.illiana.net
>X-Mailer: Evolution 2.2.2 (2.2.2-5) 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
@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
@lists.illiana.net?subject=subscribe>
>Errors-To: app_rpt-bounces at lists.illiana.net
>X-OriginalArrivalTime: 06 Dec 2006 23:28:57.0782 (UTC)
>FILETIME=[4D645560:01C7198E]
>
>Gary,
>
>When I define duplex = 0, which means as you said to half duplex would I
>have to switch the controller back to 2 wire? Right now it's set to 4w,
>full duplex. Thanks
>
>Will / w4wwm
>
>_______________________________________________
>App_rpt mailing list
>App_rpt at lists.illiana.net
>http://lists.illiana.net/mailman/listinfo/app_rpt
------------------------------
Message: 6
Date: Wed, 6 Dec 2006 18:17:22 -0800 (PST)
From: "Gary Young" <gary at tcomeng.com>
Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl
To: "Asterisk Repeater Controler" <app_rpt at lists.illiana.net>
Cc: app_rpt at lists.illiana.net
Message-ID: <2496.209.234.101.99.1165457842.squirrel at tcomeng.com>
Content-Type: text/plain;charset=iso-8859-1
What Jim said.....
Duplex=0 is just what you need for a 4W duplex connection to a controller.
--
Gary
> Gary,
>
> When I define duplex = 0, which means as you said to half duplex would I
> have to switch the controller back to 2 wire? Right now it's set to 4w,
> full duplex. Thanks
>
> Will / w4wwm
>
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
>
------------------------------
Message: 7
Date: Thu, 07 Dec 2006 00:10:56 -0600
From: Will Wright <w4wwm at knology.net>
Subject: [App_rpt] Asterisk Controller and the CAT Controller
To: app_rpt at lists.illiana.net
Message-ID: <1165471857.3170.30.camel at localhost.localdomain>
Content-Type: text/plain
Thanks Jim and Gary,
I did leave the switch in the 4 wire position and it is now working.
Just have some issues with DTMF tones at the right levels (I think). I
can DTMF in from the repeater and get the Asterisk Controller (ARIB) to
respond on the time, the version and the repeat only audio. But cannot
connect to a few nodes that I have connected to before. Oh maybe my IP
some how is at fault. Hmmmmm, Maybe my DTMF levels at this location on
the controllers are to low. Also, I can not hear my call sign when it is
announce, but I do see it on the CLI when announce. Anyone have any
ideas? Anyway, thanks again for responding and Jim I hope you are
feeling better.
Will / W4WWM
------------------------------
Message: 8
Date: Thu, 07 Dec 2006 21:12:03 -0600
From: Will <w4wwm at knology.net>
Subject: [App_rpt] DTMF tones not passing to connec to oether nodes
To: app_rpt at lists.illiana.net
Message-ID: <4578D803.7080503 at knology.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Gary or Jim,
I see back in October there was a discussion about passing dtmf tones
and the use of the command line mode.
I'm wondering would that be the issue here? As you know, I have the
asterisk Controller setup on the repeater port controller B. My repeater
(uhf) is on controller A, repeater port 2. On the third port it is
bridge or hardwired to Controller B link port. I can send tones over
from the controller A and get the asterisk node to respond to command
such as *7, *81, and *82, but cannot get the dtmf tones to respond to
distant nodes. Could this be the same case where I would have to use the
command line mode to pass the dtmf tones through? If so what or how I
could execute this command? or tell me where I can read about it more in
depth. Thanks
Will / W4WWM
Will / W4WWM
------------------------------
Message: 9
Date: Thu, 07 Dec 2006 19:19:52 -0800
From: Gary <gary at tcomeng.com>
Subject: Re: [App_rpt] DTMF tones not passing to connec to oether
nodes
To: Asterisk Repeater Controler <app_rpt at lists.illiana.net>
Message-ID: <4578D9D8.4050405 at tcomeng.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Are you are trying to send DTMF from the asterisk system to the Controller
B? If so, you need to
connect in command mode to the node that is interfaced to the controller to
send DTMF out to the
controller port.
If you have remote Asterisk nodes, they all need to be set to pass dtmf link
to link.
There is no real documentation that I know of on this.
Gary
Will wrote:
> Gary or Jim,
>
> I see back in October there was a discussion about passing dtmf tones
> and the use of the command line mode.
>
> I'm wondering would that be the issue here? As you know, I have the
> asterisk Controller setup on the repeater port controller B. My repeater
> (uhf) is on controller A, repeater port 2. On the third port it is
> bridge or hardwired to Controller B link port. I can send tones over
> from the controller A and get the asterisk node to respond to command
> such as *7, *81, and *82, but cannot get the dtmf tones to respond to
> distant nodes. Could this be the same case where I would have to use the
> command line mode to pass the dtmf tones through? If so what or how I
> could execute this command? or tell me where I can read about it more in
> depth. Thanks
>
> Will / W4WWM
>
> Will / W4WWM
>
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
------------------------------
Message: 10
Date: Fri, 08 Dec 2006 02:51:48 -0600
From: Will <w4wwm at knology.net>
Subject: [App_rpt] Asterick controller to a CAT controller
To: app_rpt at lists.illiana.net
Message-ID: <457927A4.6080007 at knology.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>Are you are trying to send DTMF from the asterisk system to the
Controller B?
Yes, I need to send DTFM to controller B. Asterisk is on controller B
wired the repeater port as of the few last e-mail post. On controller B
there are 3 link ports, port 1 is 2 meters, port 2 is IRLP(node4516) and
port 3 is the half duplex link (hard wired} to Controller A. If
possible I would like Asterisk to send DTMF to control the links. I
would also have the IRLP program to send DTMF tones back to Asterisk for
linkup to any Asterisk nodes, via from Controller A
Controller A is bridged or Hardwired by way of port 3 to Controller B
port 3. One side of my controls will be coming from Controller A to
Controller B and the other from B to C
Anyway if you like you can give me a call on my IRLP node 4516 any
time. Thanks
Will / W4wwm
------------------------------
Message: 11
Date: Fri, 08 Dec 2006 03:11:26 -0800
From: "Jim Duuuude" <telesistant at hotmail.com>
Subject: Re: [App_rpt] Asterick controller to a CAT controller
To: app_rpt at lists.illiana.net
Message-ID: <BAY119-F2901CC01CCE5AB5D4628FBB1D30 at phx.gbl>
Content-Type: text/plain; format=flowed
Well here's some documentation that I just whipped up
(not bad with 2 broken hands). You can tell I was sorta
getting slap happy near the end (with my dry humor).
Interfacing Alien Worlds (or linked systems at least)
When given the task of providing usable communications between
alien worlds, one first must analyze the similarities and
differences between them. Then you need to find the most
efficient way of dealing with the differences.
One of these 'worlds' is the 'conventional' radio system based
on controllers that have a 'common link path', that is where
controllers are linked together thru permanent RF links connected
to a controllers "link" port(s) and to provide linking between
repeater systems (connected to "repeater" ports on their associated
controller(s)), the controller opens an audio and control channel
between the repeater's port and the link's port.
In this manner, several repeaters on one controller (each on their
own repeater ports) and one or more links to other controllers (each on
their
own link ports) a multiple repeater linked network can be created.
Each node has DTMF commands that it can do. Generally, there is some
standard for the repeater functions on each node, and therefore some
standard form (digit-wise) for these commands.
There is also provided some form of being able to command a node (not
your local repeater, but another one on the link) that, by its very nature
differs from the commands for local node use (non-conflicting digit
sequences, etc).
One common example of this is to start local commands with an asterisk (*).
Remote node commands start with a pound (#) plus the node number. Say, for
example, you wanted to ask you local system what time it is. You might enter
*98 on your local repeater, but to ask another node (in this example node
123),
you might enter (#12398). This is a practical example of local/distant
control
differentiation, since by convention, all local commands start with (*) and
all link (distant) commands start with (#).
>From a technical standpoint, its also an easy an practical way to implement
controllers and links. A link port has a DTMF receiver listening for its
'addressing' code (like #123, in the example above). When it hears it, it
listens for the rest of the command, and does the appropriate thing. All
link
ports have a DTMF receiver listening to the same audio (well, they're linked
together, of course), but only the proper one reacts (based upon the prefix
code).
When you have a fixed link (and often single path link) system, this is an
excellent and time-proven design. Many, if not all of the amateur repeater
controllers are currently based on this type of archetecture.
App_rpt (Allstar, etc) definitely walks to the beat of a different drummer.
First of all, there are no 'hard' or 'permanent' links. Since the linking
media is TCP/IP, thus allowing connections from basically anywhere to
anywhere,
links are completey dynamic and at will. Any node can theoretically be
connected
to any node in any fashion. Several sets of links (not connected to each
other)
may be operating at any given time. Yes, the software does support the
concept
of 'establish a link and keep putting back up if it goes down'; Even these
are 'soft' links. Additionally, since the link media is TCP/IP, out-of-band
data may be sent between link endpoints, thus eliminating the need (or even
the
desire, for that matter) for in-band (such as DTMF) signalling between link
endpoints.
There are 2 very serious archetectural differences between app_rpt and
a 'conventional' system.
The first one is that all system endpoints including
repeaters, remote bases, and alien system interfaces, are separate nodes
(and have separate
node numbers assigned to them). Normally, a remote base is part of a repater
system. Not here. A remote base is a separate independent entity.
The second one is that you have to essentially 'speak' to a remote node to
give
it commands. Unlike a conventional system where all of the link entities are
on
a common talk path, and all have DTMF receivers decoding all of your digits,
you have to put your local system into remote command mode (to a particular
node),
then all the DTMF you send will go to the remote node, rather then being
interpreted
by the local system. Thats now app_rpt performs differentiation between
local and
remote commands. All app_rpt commands begin with (*) asterisk. The (#) pound
is used to exit things, like for example to exit command mode. Obvoiusly,
since
all commands start with (*) and cant contain (#), when youre in local
command mode
it knows what to send to the remote, and when youre done with it.
So, whether you are controlling another repeater, a remote base, or an alien
network,
you have to invoke command mode to the node that you are intending to
control.
Interface from app_rpt to an alien network is accomplished via a node
configured as
a repeater in duplex mode 0, and the propagate_dtmf and linktolink options
both
enabled.
Clearly there exists a very serious incompability in the concepts of DTMF
command
format and archetecture.
First of all, the app_rpt needs to respond as if it were another link node,
listening for
its prefix code, then acting appropriately. This can be accomplished with
the inxlat
configuration directive. First, there needs to be a sequence, which is to be
'turned into'
a (*) as far as the app_rpt is conerned, and also one that is to be 'turned
into'
a (#) as far as the app_rpt is concerned (you cant use a real * or # since
so many
of the alien's commands have these characters in them). So, you assign it a
node number,
say 456. So the sequence 4561 can represent *, and the 4562 can represent #
( or you can
assign 2 different prefixes, like 456 and 457 if you want it to be 1 digit
less), but in
any case you put in something like : inxlat = #456,#457,0123456789ABCD
That would mean: #456 is like (*), #457 is like (#), and just pass any of
the listed digits
in the 3rd arg, if they are not part of a command.
Now that we have that settled, the app_rpt node needs to send commands to
the rest of
the link as if it were one of them, meaning prefixed commands. As we already
know,
the normal (app_rpt) commands on the node that is connected to the alien
system start
with (*) and cant contain (#) (thats how we do it in app_rpt). so we need to
be able
to 'create' a way to send a (*) and (#) out the node. So we use outxlat, as
follows:
outxlat = *7,*0,0123456789#ABCD
This means that *7 get sent out to the alien system as a (*), *0 gets sent
out as a (#),
and pass any of the digits listed in the 3rd arg if not part of a local
command.
So, say the ailen system was on allstar node 123. We then want to command
the alien's
node 765 to do a *98 (like give us its local time).
On your local node you might enter:
*4123 (to put you into command node on 123, which is the alien system)
*076598 (to do the same as if you were entering #76598 on the alien system
directly on one
of its repeaters)
# (to exit command mode on your local node)
These two pieces of translation allow the systems to communicate with each
other
very nicely and with minimum hassle and/or discomfort for users of either
system
type.
JIM - WB6NIL
>From: Will <w4wwm at knology.net>
>Reply-To: Asterisk Repeater Controler <app_rpt at lists.illiana.net>
>To: app_rpt at lists.illiana.net
>Subject: [App_rpt] Asterick controller to a CAT controller
>Date: Fri, 08 Dec 2006 02:51:48 -0600
>MIME-Version: 1.0
>Received: from lists.illiana.net ([64.212.212.35]) by
>bay0-mc3-f5.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 8
>Dec 2006 00:52:54 -0800
>Received: (qmail 22992 invoked from network); 8 Dec 2006 08:51:53 -0000
>Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 8
>Dec 2006 08:51:53 -0000
>Received: (qmail 22966 invoked from network); 8 Dec 2006 08:51:51 -0000
>Received: from smtp.knology.net (24.214.63.101)by 0 with SMTP; 8 Dec 2006
>08:51:51 -0000
>Received: (qmail 4943 invoked by uid 0); 8 Dec 2006 08:51:50 -0000
>Received: from unknown (HELO ?192.168.1.101?) (w4wwm at 69.1.11.66)by
>smtp2.knology.net with ESMTPA; 8 Dec 2006 08:51:50 -0000
>X-Message-Info: txF49lGdW42+DGHr+cvEgbodQNncuZKWcInXLwzD5NI=
>Return-Path: <w4wwm at knology.net>
>Delivered-To: mailman-app_rpt at lists.illiana.net
>User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
>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
@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
@lists.illiana.net?subject=subscribe>
>Errors-To: app_rpt-bounces at lists.illiana.net
>X-OriginalArrivalTime: 08 Dec 2006 08:52:55.0001 (UTC)
>FILETIME=[405BF490:01C71AA6]
>
> >>Are you are trying to send DTMF from the asterisk system to the
>Controller B?
>
>Yes, I need to send DTFM to controller B. Asterisk is on controller B
>wired the repeater port as of the few last e-mail post. On controller B
>there are 3 link ports, port 1 is 2 meters, port 2 is IRLP(node4516) and
>port 3 is the half duplex link (hard wired} to Controller A. If
>possible I would like Asterisk to send DTMF to control the links. I
>would also have the IRLP program to send DTMF tones back to Asterisk for
>linkup to any Asterisk nodes, via from Controller A
>
>Controller A is bridged or Hardwired by way of port 3 to Controller B
>port 3. One side of my controls will be coming from Controller A to
>Controller B and the other from B to C
>
> Anyway if you like you can give me a call on my IRLP node 4516 any
>time. Thanks
>
>Will / W4wwm
>_______________________________________________
>App_rpt mailing list
>App_rpt at lists.illiana.net
>http://lists.illiana.net/mailman/listinfo/app_rpt
------------------------------
_______________________________________________
App_rpt mailing list
App_rpt at lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt
End of App_rpt Digest, Vol 10, Issue 3
**************************************
More information about the App_rpt-users
mailing list