- App_rpt-users - lists.keekles.org

[App_rpt] arib board
by Eric Fort 28 Jan '07

28 Jan '07

I'm about ready to build some arib boards. the question I have is how many? if I have a port I'm using as a remote base it seems obvious that I should only need one, but if I'm using 2 ports in full duplex operation, haw many boards do I need?

2 1

[App_rpt] what do I need to setup a node
by Eric Fort 22 Jan '07

22 Jan '07

Here's what I've collected so far to set up a node (maybe 2 if I can find another site): 1 2.4Ghz P4 computer (maybe 2 or more) running linux. 3 Digium TDM400 cards populated with 5 FXO and 5 FXS interfaces internet connectivity (dsl or T! at node sites and the colo facility I have rackspace in if I need a reflector - need hosting?) 1 FT-817/FT-857/FT-897 pots connectivity at most locations. VoIP account as necessary I know I need a few arib boards but how do they compare to http://www.hamwlan.net/images/FXS-SIMPLEX-RADIO-V2.jpg What else do I need? What could I put up? the simplex vs duplex thing has me a bit confused. my experience with true duplex is in a linked system where if 2 people talk at once you hear both and cross band monitoring of my own transmissions I'd like to put up a HF/VHF/UHF remote, maybe 2 that can be configured to linn between different bands and modes a static way in by radio fixed frequency, maybe a repeater but I don't expect great coverage in these locations (linking from them is possible though) other things? possible node locations include: phelan pomona irvine wilmington downtown Los Angeles Telecom hotel (difficult to attach radio ports here but maybe a good place to interlink with IRLP/EchoLink/SkypeLink) I'd like to get building soon. Eric

2 2

[App_rpt] Asterisk App_Rpt Segmentation Fault
by Niagassas Angelos 05 Jan '07

05 Jan '07

Hello to the group, I install Asterisk from SVN repository Ver SVN-trunk-r49321 including app_rpt using a TDM400P with 2 FXS daughter boards on a system running Suse-10.1. I wiil use the simplex interface as described at http://www.hamwlan.net/images/FXS-SIMPLEX-RADIO-V2.jpg in order to interconnect 2 simplex UHF radio to create a network. Using information from Francois BERGERET (f6hqz-m(a)hamwlan.net) and the mailing list I made adjustments to the pertinent files as follows: # zaptel.conf e&m=1-2 loadzone=us defaultzone=us Meaning 2 FXS ports configured as E&M signalling. ;zapata.conf [channels] callwaitingcallerid=no echocancel=yes echocancelwhenbridged=yes echotraining=no relaxdtmf=yes adsi=off usercallerid=yes callgroup=1 pickupgroup=1 group=1 signalling=em_rxtx immediate=yes context=radio1 channel=1 context=radio2 channel=2 Meaning 2 FXS ports signalling = em_rxtx and immediate = yes ;rpt.conf [1999] ; Node ID of remote base rxchannel = Zap/1 ; Rx audio/signalling channel remote = y duplex=0 context=radio1 [1900] rxchannel = Zap/2 remote = y duplex=0 context=radio2 [functions-remote] [telemetry] [morse] [nodes] 1999 = radio1(a)192.168.0.201/1999 1900 = radio2(a)192.168.0.201/1900 [memory] ;extensions.conf [general] static=yes writeprotect=no autofallthrought=yes clearglobalvars=no [globals] [default] [radio1] exten => 1900,1,rpt,1900|D [radio2] exten => 1999,1,rpt,1999|D [radio-secure1] exten => 1900,1,rpt,1900|D exten => 1999,1,rpt,1999|D [radio-secure2] exten => 1900,1,rpt,1900|D exten => 1999,1,rpt,1999|D ;iax.conf [gui] type=friend context=radio-secure1 username=gui secret=******** auth=md5 disallow=all allow=gsm notransfer=yes [gui2] type=friend context=radio-secure2 username=gui secret=******** auth=md5 disallow=all allow=gsm notransfer=yes ;sip.conf [gui] type=friend context=radio-secure1 username=gui secret=******** auth=md5 disallow=all allow=gsm notransfer=yes [gui2] type=friend context=radio-secure2 username=gui secret=******** auth=md5 disallow=all allow=gsm notransfer=yes With the above configuration I configure the system. Now calling from a remote PC Using iaxRpt the 1999 node I can connect to the radio and control it turning into transmit mode and receiving as expected !!!!!!!! Calling the 1900 node I have the following indication at the Asterisk console: ... --Executing [1900@radio-secure1:1] Rpt("IAX2/gui-10", "1900|D") in new stack Segmentation fault Xxxxxx:~ # Questions 1. Is something wrong with node 1900 ? It appears to me totally similar to 1999. 2. In addition I need a method - configuration to have the above 2 nodes interconnected automatically at Asterisk boot (Maybe by using MeetMe). 3. Extending the above requirement same need for remote running Asterisk boxes. Is any one to help me? Thanks in advance. Niagassas Angelos Project Manager Tel. +30 210 4821492 Mob. +30 6977919262 Messenger: niagassas(a)hotmail.com eMail: niagassas_ang(a)tellas.gr

2 1

[App_rpt] No DTMF control
by Will Wright 03 Jan '07

03 Jan '07

Hello to the group, My node, 2059 will not respond to any of the DTMF commands. Is there any one could help get me back on track? Thanks Will / W4WWM

2 6

[App_rpt] Newbie in Asterisk
by Νιαγάσας Αγγελος 30 Dec '06

30 Dec '06

Hello to the group, I just install a new Asterisk system in order to be used as controller of a radio shack. I install Suse Linux ver. 10.1 with Kernel 2.6 I install Asterisk-1.2.14 including app_rpt with a TDM400P with 2 FXS daughter boards. I wiil use the simplex interface as described at http://www.hamwlan.net/images/FXS-SIMPLEX-RADIO-V2.jpg in order to interconnect a series of simplex UHF radio to create a network. Trying to test the system I hooked 2 analog telephone sets replacing the radio interfaces. Using information send from your very helpful friend Francois BERGERET (f6hqz-m(a)hamwlan.net) I made adjustments to the pertinent files as follows: # zaptel.conf e&m=1-2 loadzone=us defaultzone=us # #EOF # Meaning 2 FXS ports configured as E&M signalling. ;zapata.conf [channels] callwaitingcallerid=no echocancel=yes echocancelwhenbridged=yes echotraining=no relaxdtmf=yes adsi=off usercallerid=yes callgroup=1 pickupgroup=1 group=1 signalling=em_rxtx immediate=yes context=channel1 channel=1 context=channel2 channel=2 Meaning 2 FXS ports signalling = em_rxtx and immediate = yes ;rpt.conf [1999] ; Node ID of remote base rxchannel = Zap/1 ; Rx audio/signalling channel remote = n duplex=0 [1998] rxchannel = Zap/2 remote = n duplex=0 [functions-remote] [telemetry] [morse] [nodes] 1999 = radio(a)127.0.0.1/1999 1998 = radio(a)127.0.0.1/1998 [memory] ;extensions.conf [general] static=yes writeprotect=no autofallthrought=yes [globals] [default] [channel1] exten => s,1,rpt(1998|D) exten => s,n,Hangup [channel2] exten => s,1,rpt(1999|D) exten => s,n,Hangup With the above configuration we tried to configure the system as to automatically call the other set each time the one goes Off Hook. But this was my desire. Unfortunately the system is fully silent. When I modified the line in zapata.conf from signalling=em_rxtx to signalling=em the system started to call as expected. Substituting the telephone sets with the radio interfaces, making a test I have the following situation: 1. Incoming call is answered OK. = PTT is energized 2. Initiating side receives a ring back condition. As consequence I loose the capability to release the line using the COR/BUSY control. Making measurements at the RING/TIP pair I found that incoming call reverses the polarity of the line and stays at this condition until the line is released some how. At the initiating side (Rx) the polarity is RING - TIP = -48V at idle. When COR/BUSY control change state the Opto opens and the call is initiated. But after some milliseconds polarity reverses causing the receive opto to open and the system is in answer condition. In order to release the line I have to disconnect manually the RJ45 from the board. Is any one to help me? Niagassas Angelos Project Manager Tel. +30 210 4821492 Mob. +30 6977919262 Messenger: niagassas(a)hotmail.com eMail: niagassas_ang(a)tellas.gr

2 1

[App_rpt] Log files after operating in command mode
by Will Wright 26 Dec '06

26 Dec '06

Hello to the group, Is there some sort of log file established while one is in the command mode. Just to see or confirm what dtmf digit were passed? I hope the question make sense? if not I'll try again. Thanks Will / W4WWM

1 0

Re: [App_rpt] How are Steve and Jim doing?
by hwstar＠rodgers.sdcoxmail.com 10 Dec '06

10 Dec '06

All As of 12/7 Im out of surgery and am starting physical therapy. Steve, WA6ZFT > > From: "Nevada Amateur Radio Repeaters, Inc." <w7aor(a)narri.org> > Date: 2006/12/08 Fri AM 11:49:20 PST > To: <app_rpt(a)lists.illiana.net> > Subject: [App_rpt] How are Steve and Jim doing? > > How are Steve and Jim doing? > > -----Original Message----- > From: app_rpt-bounces(a)lists.illiana.net > [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of > app_rpt-request(a)lists.illiana.net > Sent: Friday, December 08, 2006 3:11 AM > To: app_rpt(a)lists.illiana.net > Subject: App_rpt Digest, Vol 10, Issue 3 > > Send App_rpt mailing list submissions to > app_rpt(a)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(a)lists.illiana.net > > You can reach the person managing the list at > app_rpt-owner(a)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(a)xelatec.com> > Subject: Re: [App_rpt] RE : Configuration Hints for Multiple Radios on > 1 node > To: f6hqz-m(a)hamwlan.net > Cc: 'Asterisk Repeater Controler' <app_rpt(a)lists.illiana.net> > Message-ID: <45452.192.168.1.226.1165300174.squirrel(a)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(a)lists.illiana.net > > [mailto:app_rpt-bounces@lists.illiana.net] De la part de Steven Henke > > Envoy? : mardi 5 d?cembre 2006 03:52 > > ? : app_rpt(a)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(a)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(a)knology.net> > Subject: [App_rpt] Asterisk controller to a CAT Controller(full > duplex) > To: app_rpt(a)lists.illiana.net > Message-ID: <457652CE.1090900(a)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(a)tcomeng.com> > Subject: Re: [App_rpt] Asterisk controller to a CAT Controller(full > duplex) > To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> > Message-ID: <4576578A.3050908(a)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(a)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(a)knology.net> > Subject: [App_rpt] Asterisk Controller to a Cat Controllerl > To: app_rpt(a)lists.illiana.net > Message-ID: <1165447726.3170.7.camel(a)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(a)hotmail.com> > Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl > To: app_rpt(a)lists.illiana.net > Message-ID: <BAY119-F2267D808B094E3F4413A96B1DC0(a)phx.gbl> > Content-Type: text/plain; format=flowed > > nope, leave it in 4 wire > > > >From: Will Wright <w4wwm(a)knology.net> > >Reply-To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> > >To: app_rpt(a)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(a)knology.net> > >Delivered-To: mailman-app_rpt(a)lists.illiana.net > >X-Mailer: Evolution 2.2.2 (2.2.2-5) X-BeenThere: app_rpt(a)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(a)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(a)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(a)tcomeng.com> > Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl > To: "Asterisk Repeater Controler" <app_rpt(a)lists.illiana.net> > Cc: app_rpt(a)lists.illiana.net > Message-ID: <2496.209.234.101.99.1165457842.squirrel(a)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(a)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(a)knology.net> > Subject: [App_rpt] Asterisk Controller and the CAT Controller > To: app_rpt(a)lists.illiana.net > Message-ID: <1165471857.3170.30.camel(a)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(a)knology.net> > Subject: [App_rpt] DTMF tones not passing to connec to oether nodes > To: app_rpt(a)lists.illiana.net > Message-ID: <4578D803.7080503(a)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(a)tcomeng.com> > Subject: Re: [App_rpt] DTMF tones not passing to connec to oether > nodes > To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> > Message-ID: <4578D9D8.4050405(a)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(a)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(a)knology.net> > Subject: [App_rpt] Asterick controller to a CAT controller > To: app_rpt(a)lists.illiana.net > Message-ID: <457927A4.6080007(a)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(a)hotmail.com> > Subject: Re: [App_rpt] Asterick controller to a CAT controller > To: app_rpt(a)lists.illiana.net > Message-ID: <BAY119-F2901CC01CCE5AB5D4628FBB1D30(a)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(a)knology.net> > >Reply-To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> > >To: app_rpt(a)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(a)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(a)knology.net> > >Delivered-To: mailman-app_rpt(a)lists.illiana.net > >User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) > >X-BeenThere: app_rpt(a)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(a)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(a)lists.illiana.net > >http://lists.illiana.net/mailman/listinfo/app_rpt > > > > > ------------------------------ > > _______________________________________________ > App_rpt mailing list > App_rpt(a)lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > > > End of App_rpt Digest, Vol 10, Issue 3 > ************************************** > > _______________________________________________ > App_rpt mailing list > App_rpt(a)lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt >

3 2

[App_rpt] Alien Interfaces
by Will Wright 09 Dec '06

09 Dec '06

Hello Jim, Jim, I must say the information is good but I'm still not sure If I understand all of it. So, here's my crack at it's working. The controllers are alien to app_rpt, this I thought was real neat and did have me chuckling a bit hi hi. Controller A, B or C better know as alien interfaces that should be given a node number? If so, do I assign them just for the local system? Or is it assign by the Allstar Linking System? I will then set up a stanza in rpt.conf defining the node such as: [443] duplex=0 propagate=yes linktolink=yes inxlat=#443,#444,0123456789ABCD outxlat=*7,*0.0123456789#ABCD Would I establish another stanza and node number for controller B, and C (Alien interfaces) hi hi How would the command mode be entered or define? Is it *40 on all sysytem, I hope I'm not too far off on how this all work. But it look like I will need some help. Thanks Jim, you really did a great job on the paper. I just need more help to understand it. Thanks Will / W4WWM

2 1

[App_rpt] How are Steve and Jim doing?
by Nevada Amateur Radio Repeaters, Inc. 08 Dec '06

08 Dec '06

How are Steve and Jim doing? -----Original Message----- From: app_rpt-bounces(a)lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of app_rpt-request(a)lists.illiana.net Sent: Friday, December 08, 2006 3:11 AM To: app_rpt(a)lists.illiana.net Subject: App_rpt Digest, Vol 10, Issue 3 Send App_rpt mailing list submissions to app_rpt(a)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(a)lists.illiana.net You can reach the person managing the list at app_rpt-owner(a)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(a)xelatec.com> Subject: Re: [App_rpt] RE : Configuration Hints for Multiple Radios on 1 node To: f6hqz-m(a)hamwlan.net Cc: 'Asterisk Repeater Controler' <app_rpt(a)lists.illiana.net> Message-ID: <45452.192.168.1.226.1165300174.squirrel(a)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(a)lists.illiana.net > [mailto:app_rpt-bounces@lists.illiana.net] De la part de Steven Henke > Envoy? : mardi 5 d?cembre 2006 03:52 > ? : app_rpt(a)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(a)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(a)knology.net> Subject: [App_rpt] Asterisk controller to a CAT Controller(full duplex) To: app_rpt(a)lists.illiana.net Message-ID: <457652CE.1090900(a)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(a)tcomeng.com> Subject: Re: [App_rpt] Asterisk controller to a CAT Controller(full duplex) To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> Message-ID: <4576578A.3050908(a)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(a)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(a)knology.net> Subject: [App_rpt] Asterisk Controller to a Cat Controllerl To: app_rpt(a)lists.illiana.net Message-ID: <1165447726.3170.7.camel(a)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(a)hotmail.com> Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl To: app_rpt(a)lists.illiana.net Message-ID: <BAY119-F2267D808B094E3F4413A96B1DC0(a)phx.gbl> Content-Type: text/plain; format=flowed nope, leave it in 4 wire >From: Will Wright <w4wwm(a)knology.net> >Reply-To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> >To: app_rpt(a)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(a)knology.net> >Delivered-To: mailman-app_rpt(a)lists.illiana.net >X-Mailer: Evolution 2.2.2 (2.2.2-5) X-BeenThere: app_rpt(a)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(a)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(a)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(a)tcomeng.com> Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl To: "Asterisk Repeater Controler" <app_rpt(a)lists.illiana.net> Cc: app_rpt(a)lists.illiana.net Message-ID: <2496.209.234.101.99.1165457842.squirrel(a)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(a)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(a)knology.net> Subject: [App_rpt] Asterisk Controller and the CAT Controller To: app_rpt(a)lists.illiana.net Message-ID: <1165471857.3170.30.camel(a)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(a)knology.net> Subject: [App_rpt] DTMF tones not passing to connec to oether nodes To: app_rpt(a)lists.illiana.net Message-ID: <4578D803.7080503(a)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(a)tcomeng.com> Subject: Re: [App_rpt] DTMF tones not passing to connec to oether nodes To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> Message-ID: <4578D9D8.4050405(a)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(a)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(a)knology.net> Subject: [App_rpt] Asterick controller to a CAT controller To: app_rpt(a)lists.illiana.net Message-ID: <457927A4.6080007(a)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(a)hotmail.com> Subject: Re: [App_rpt] Asterick controller to a CAT controller To: app_rpt(a)lists.illiana.net Message-ID: <BAY119-F2901CC01CCE5AB5D4628FBB1D30(a)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(a)knology.net> >Reply-To: Asterisk Repeater Controler <app_rpt(a)lists.illiana.net> >To: app_rpt(a)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(a)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(a)knology.net> >Delivered-To: mailman-app_rpt(a)lists.illiana.net >User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) >X-BeenThere: app_rpt(a)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(a)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(a)lists.illiana.net >http://lists.illiana.net/mailman/listinfo/app_rpt ------------------------------ _______________________________________________ App_rpt mailing list App_rpt(a)lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt End of App_rpt Digest, Vol 10, Issue 3 **************************************

1 0

[App_rpt] FW: [asterisk_radio] Fwd: 2007 IRLP Conference
by Nevada Amateur Radio Repeaters, Inc. 08 Dec '06

08 Dec '06

-----Original Message----- From: asterisk_radio(a)yahoogroups.com [mailto:asterisk_radio@yahoogroups.com] On Behalf Of w7aor Sent: Wednesday, December 06, 2006 10:39 AM To: asterisk_radio(a)yahoogroups.com; erc_ecs(a)yahoogroups.com; GE-MastrII(a)yahoogroups.com; InternetLinking(a)yahoogroups.com; motorola_radio_discussion(a)yahoogroups.com; NV_ARES(a)yahoogroups.com; Repeater-Builder(a)yahoogroups.com; VoIP_American_Red_Cross_Communicators_Net(a)yahoogroups.com; VOIP-WXNET(a)yahoogroups.com; w7aor(a)narri.org Subject: [asterisk_radio] Fwd: 2007 IRLP Conference --- In irlp@yahoogroups. <mailto:irlp%40yahoogroups.com> com, "Nevada Amateur Radio Repeaters, Inc." <w7aor@...> wrote: 2007 Annual Las Vegas IRLP Conference is now set for April 14 Saturday 8 AM through April Sunday Noon at the Imperial Palace on the Las Vegas strip. Ask for group rate of $119.00 per week end day. Come early or stay over; rates are much lower on non-week end days. The format of the conference is to have Dave Cameron as the featured speaker. Node owner special interest presentations are welcome. I expect to see demos of micro node computers, mobile nodes and much more. Technical information presentations and papers on other VOIP systems such as Echo link, D Star and All Star Link (Full Duplex Asterisk ) are welcome and encouraged. The date of the IRLP conference was set to coincide with the National Association of Broadcasters Conference: April 14-19, 2007. The conference is sponsored by Nevada Amateur Radio Repeaters, Inc. (NARRI). More information will be post via yahoo groups and the NARRI web site http://www.narri. <http://www.narri.org/Annual_IRLP_Conference.html.> org/Annual_IRLP_Conference.html. Feel free to contact Kent W7AOR by e-mail direct or on the Western Reflector 9250 with any questions. [Non-text portions of this message have been removed] --- End forwarded message --- __._,_.___ Messages <http://groups.yahoo.com/group/asterisk_radio/message/36;_ylc=X3oDMTMxNHUza3 AyBF9TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMzNg RzZWMDZnRyBHNsawN2dHBjBHN0aW1lAzExNjU0MzA1MjQEdHBjSWQDMzY-> in this topic (1) <http://groups.yahoo.com/group/asterisk_radio/post;_ylc=X3oDMTJvZ3A1dWhhBF9T Azk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMzNgRzZWMD ZnRyBHNsawNycGx5BHN0aW1lAzExNjU0MzA1MjQ-?act=reply&messageNum=36> Reply (via web post) | Start <http://groups.yahoo.com/group/asterisk_radio/post;_ylc=X3oDMTJmaTRiNmFwBF9T Azk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNu dHBjBHN0aW1lAzExNjU0MzA1MjQ-> a new topic Messages <http://groups.yahoo.com/group/asterisk_radio/messages;_ylc=X3oDMTJmb2Q5Mmww BF9TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNs awNtc2dzBHN0aW1lAzExNjU0MzA1MjQ-> | Files <http://groups.yahoo.com/group/asterisk_radio/files;_ylc=X3oDMTJnaTRnYml0BF9 TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawN maWxlcwRzdGltZQMxMTY1NDMwNTI0> | Photos <http://groups.yahoo.com/group/asterisk_radio/photos;_ylc=X3oDMTJmcGExNXUwBF 9TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsaw NwaG90BHN0aW1lAzExNjU0MzA1MjQ-> | Links <http://groups.yahoo.com/group/asterisk_radio/links;_ylc=X3oDMTJnZjVucW9yBF9 TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawN saW5rcwRzdGltZQMxMTY1NDMwNTI0> | Database <http://groups.yahoo.com/group/asterisk_radio/database;_ylc=X3oDMTJkYzdmc3Fq BF9TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNs awNkYgRzdGltZQMxMTY1NDMwNTI0> | Polls <http://groups.yahoo.com/group/asterisk_radio/polls;_ylc=X3oDMTJnY2xmbjllBF9 TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawN wb2xscwRzdGltZQMxMTY1NDMwNTI0> | Members <http://groups.yahoo.com/group/asterisk_radio/members;_ylc=X3oDMTJmOG4wdW5tB F9TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsa wNtYnJzBHN0aW1lAzExNjU0MzA1MjQ-> | Calendar <http://groups.yahoo.com/group/asterisk_radio/calendar;_ylc=X3oDMTJlNThwbnNi BF9TAzk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNs awNjYWwEc3RpbWUDMTE2NTQzMDUyNA--> <http://groups.yahoo.com/;_ylc=X3oDMTJlcHA2NmsxBF9TAzk3MzU5NzE0BGdycElkAzE3M DE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTE2NTQzMDUyN A--> Yahoo! Groups Change <http://groups.yahoo.com/group/asterisk_radio/join;_ylc=X3oDMTJnb3VzcGY4BF9T Azk3MzU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNz dG5ncwRzdGltZQMxMTY1NDMwNTI0> settings via the Web (Yahoo! ID required) Change settings via email: Switch <mailto:asterisk_radio-digest@yahoogroups.com?subject=Email%20Delivery:%20Di gest> delivery to Daily Digest | Switch <mailto:asterisk_radio-traditional@yahoogroups.com?subject=Change%20Delivery %20Format:%20Traditional> format to Traditional Visit <http://groups.yahoo.com/group/asterisk_radio;_ylc=X3oDMTJlM3VtcTA4BF9TAzk3M zU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNocGYEc 3RpbWUDMTE2NTQzMDUyNA--> Your Group | Yahoo! Groups <http://docs.yahoo.com/info/terms/> Terms of Use | Unsubscribe <mailto:asterisk_radio-unsubscribe@yahoogroups.com?subject=> Visit <http://groups.yahoo.com/group/asterisk_radio;_ylc=X3oDMTJmOTZmNGxkBF9TAzk3M zU5NzE0BGdycElkAzE3MDE4MTM2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2Z2hwB HN0aW1lAzExNjU0MzA1MjQ-> Your Group Y! GeoCities Be <http://us.ard.yahoo.com/SIG=12hia2n6a/M=493064.8985658.9760664.8674578/D=gr oups/S=1705063108:NC/Y=YAHOO/EXP=1165437724/A=3848541/R=0/SIG=12ban20bv/*htt p:/us.rd.yahoo.com/evt=42416/*http:/geocities.yahoo.com/ps/y360/?v=f> Interactive Create a conver- sation with blogs. Free Blogging Y! <http://us.ard.yahoo.com/SIG=12icsd93i/M=493064.9337501.10154278.8674578/D=g roups/S=1705063108:NC/Y=YAHOO/EXP=1165437724/A=4025377/R=0/SIG=12mdvba2o/*ht tp:/us.rd.yahoo.com/evt=44092/*http:/smallbusiness.yahoo.com/webhosting/blog .php> Web Hosting Share your views with the world. Yahoo! Groups Start <http://groups.yahoo.com/start;_ylc=X3oDMTJwdjRnZm8wBF9TAzk3MzU5NzE0BF9wAzME Z3JwSWQDMTcwMTgxMzYEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwNuY21vZARzbGsDZ3JvdXBzMgRz dGltZQMxMTY1NDMwNTI0> a group in 3 easy steps. Connect with others. . <http://geo.yahoo.com/serv?s=97359714/grpId=17018136/grpspId=1705063108/msgI d=36/stime=1165430524/nc1=3848541/nc2=4025377/nc3=3> __,_._,___

1 0