From sph at xelatec.com Tue Dec 5 02:36:36 2006 From: sph at xelatec.com (Steven Henke) Date: Mon, 4 Dec 2006 21:36:36 -0500 (EST) Subject: [App_rpt] Hopes and Prayers for Steve and Jim Message-ID: <48153.192.168.1.226.1165286196.squirrel@192.168.1.226> Dear Steve and Jim, I am so sorry to hear about your accident and I hope and pray for a speedy recovery for you both. Please keep us posted. Sincerely, Steve Henke, W9SH From sph at xelatec.com Tue Dec 5 02:51:59 2006 From: sph at xelatec.com (Steven Henke) Date: Mon, 4 Dec 2006 21:51:59 -0500 (EST) Subject: [App_rpt] Configuration Hints for Multiple Radios on 1 node Message-ID: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> 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) From gary at tcomeng.com Tue Dec 5 02:56:51 2006 From: gary at tcomeng.com (Gary) Date: Mon, 04 Dec 2006 18:56:51 -0800 Subject: [App_rpt] Configuration Hints for Multiple Radios on 1 node In-Reply-To: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> References: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> Message-ID: <4574DFF3.2@tcomeng.com> I am not grasping your exact question here. Can you post your config and hardware setup? Gary Steven Henke wrote: > 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 From gary at tcomeng.com Tue Dec 5 02:59:35 2006 From: gary at tcomeng.com (Gary) Date: Mon, 04 Dec 2006 18:59:35 -0800 Subject: [App_rpt] Serial Data Code? In-Reply-To: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> References: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> Message-ID: <4574E097.1090406@tcomeng.com> Can anyone point me to where in the app_rpt code I can add a null string to output before every serial Remote Command that gets sent out the serial I/O port? Gary From gary at tcomeng.com Tue Dec 5 03:02:53 2006 From: gary at tcomeng.com (Gary) Date: Mon, 04 Dec 2006 19:02:53 -0800 Subject: [App_rpt] Interface a CAT200B controller to the ARIB In-Reply-To: <456D18CF.2050208@knology.net> References: <456D18CF.2050208@knology.net> Message-ID: <4574E15D.1050405@tcomeng.com> This is fairly straight forward. Connect the ARIB PTT to the COR input of your controller. Connect the Controller PTT to the COR input of the controller. Connect the ARIB TX audio to the RX audio of the controller. Connect the Controler TX audio to the RX audio input to the ARIB. Gary Will wrote: > Hello to the group, > > Is there anybody in the group have interfaced the ARIB to a controller? > I have a CAT200B+RLS1000B, which is a 4 port repeater controller with 1 > repeater and 4 link ports. I am wondering is it possible to interface > the ARIB to the repeater port and have ARIB talk to the link ports. The > link ports will be 2 meters, an IRLP node and a toss up between a 220 or > a 440 rig. this will also link up to a 440 repeater on hill top here in > the city. > > If anyone could help I would really appreciate it. I do have a wiring > diagram that I will share if you would like to see what I have > attempted. Thanks > > Will / W4WWM > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt From sph at xelatec.com Tue Dec 5 03:18:21 2006 From: sph at xelatec.com (Steven Henke) Date: Mon, 4 Dec 2006 22:18:21 -0500 (EST) Subject: [App_rpt] W9SH app-rpt Multi-Radio Node Setup Message-ID: <32771.192.168.1.226.1165288701.squirrel@192.168.1.226> Here is some more information for those who might help. Asterisk 2.6GHz, 512MB, PC Host Centos 4.4 asterisk-1.2.13 asterisk-addons-1.2.5 libpri-1.2.4 zaptel-1.2.11 1 Digium TMD-400P with 3 FXS cards and 1 FXO card. 2 ARIB Interfaces. First ARIB interface is connected to Zap1-2 and then to a full-duplex transceiver (repeater). Of course all of the repeater logic is disconnected since app-rpt takes care of that. It works and sounds well. Second ARIB interface is connected to Zap3 and a simplex transceiver. It was installed first on Zap2 and worked fine until I moved it to Zap3 and put the repeater on Zap1-2. The iaxRpt client worked fine with the simplex radio and now works fine with the repeater. I've got things set up with private node numbers now so as to not bother everyone. Looking forward to getting it all back on line and showing it off. Here's the current zaptel.conf ---------------------------------- [root at auggie etc]# cat zaptel.conf # # zaptel.conf # # Repeater Full Duplex 2 FXS fxogs=1 # TX pair fxols=2 # RX pair # Simplex Radio 1 FXS e&m=3 # TX/RX on single channel # fxo card fxsks=4 loadzone = us defaultzone=us # # End of file # Here's the current zapata.conf ---------------------------- [root at auggie asterisk]# cat zapata.conf ; ; Zapata telephony interface ; ; Configuration file ; 20061127 1135 sphenke merged ; 20061203 1925 sphenke adding repeater channel ; We empirically learned that normal Zap channels (e.g. non-e&m) must be ; defined before the app-rpt e&m channels or they will not load. [trunkgroups] [channels] signalling=fxo_ks callwaitingcallerid=no echocancel=yes echocancelwhenbridged=yes echotraining=no relaxdtmf=yes immediate=no adsi=off usecallerid=yes callgroup=1 pickupgroup=1 group=1 ;Include AMP configs #include zapata_additional.conf relaxdtmf=yes ; Repeater TX callerid=asreceived context=repeatertx callwaiting=no threewaycalling=no transfer=no mailbox= signalling=fxo_tx channel=>1 ; Repeater RX signalling=fxo_rx context=repeaterrx threewaycalling=no callwaiting=no transfer=no mailbox= channel=>2 ; Simplex Station TX/RX signalling=em_rxtx context=repeaterrx threewaycalling=no callwaiting=no transfer=no mailbox= channel=>3 group=9 channel=>pseudo language=en context=from-zaptel signalling=fxs_ks rxwink=300 ; Atlas seems to use long (250ms) winks ; ; Whether or not to do distinctive ring detection on FXO lines ; ;usedistinctiveringdetection=yes usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=no echotraining=800 rxgain=0.0 txgain=0.0 group=0 callgroup=1 pickupgroup=1 immediate=no ;faxdetect=both faxdetect=incoming ;faxdetect=outgoing ;faxdetect=no ;Include genzaptelconf configs #include zapata-auto.conf group=1 ;Include AMP configs (moved see above) ;#include zapata_additional.conf ; ; End of file ; Here's the current rpt.conf ---------------------------- [root at auggie asterisk]# cat rpt.conf ; Radio Repeater configuration file (for use with app_rpt) ; ; 20061203 2015 sphenke installing repeater interface ; ; auggie repeater ; [3001] ; Name of First Repeater rxchannel = Zap/2 ; Rx audio/signalling channel ; Note: if you use a unified interface (tx/rx on one channel), only ; specify the rxchannel and the txchannel will be assumed from the rxchannel txchannel = Zap/1 ; Tx audio/signalling channel functions=functions ; Repeater Function Table link_functions=link-functions ; Link Function Table telemetry=telemetry ; Telemetry descriptions wait_times=wait-times ; Wait times context = radio ; dialing context for phone callerid = "Your Repeater" <6198192562> ; callerid for phone calls idrecording = /etc/asterisk/id ; id recording accountcode=RADIO ; account code (optional) hangtime=1000 ; squelch tail hang time (in ms) (optional) totime=170000 ; transmit time-out time (in ms) (optional) idtime=540000 ; id interval time (in ms) (optional) ; The default values for hangtime, time-out time, and id interval time are ; 5 seconds (5000 ms), 3 minutes (180000 ms), and 5 minutes (300000 ms) ; respectively politeid=30000 ; time in milliseconds before ID timer ; expires to try and ID in the tail. ; (optional, default is 30000). idtalkover=|iid/r ; Talkover ID (optional) default is none unlinkedct=ct2 ; unlinked courtesy tone (optional) default is none ; ; auggie simplex radio ; ;[2057] ; Name of First Repeater [3003] rxchannel = Zap/3 ; Rx audio/signalling channel ; Note: if you use a unified interface (tx/rx on one channel), only ; specify the rxchannel and the txchannel will be assumed from the rxchannel ;txchannel = Zap/1 ; Tx audio/signalling channel functions=functions ; Repeater Function Table link_functions=link-functions ; Link Function Table telemetry=telemetry ; Telemetry descriptions wait_times=wait-times ; Wait times duplex=0 ; Half-duplex context = radio ; dialing context for phone callerid = "Your Repeater" <6198192562> ; callerid for phone calls idrecording = /etc/asterisk/id ; id recording accountcode=RADIO ; account code (optional) hangtime=100 ; squelch tail hang time (in ms) (optional) totime=170000 ; transmit time-out time (in ms) (optional) idtime=540000 ; id interval time (in ms) (optional) archivedir= /var/log/asterisk/rpt ; The default values for hangtime, time-out time, and id interval time are ; 5 seconds (5000 ms), 3 minutes (180000 ms), and 5 minutes (300000 ms) ; respectively politeid=30000 ; time in milliseconds before ID timer ; expires to try and ID in the tail. ; (optional, default is 30000). idtalkover=|iid/r ; Talkover ID (optional) default is none unlinkedct=ct2 ; unlinked courtesy tone (optional) ; default is none ; ; Repeater function table for node 010 ; [functions] 1=ilink,1 ; Specific link disconnect 2=ilink,2 ; Specific Link connect - monitor only 3=ilink,3 ; Specific Link connect - transceive 4=ilink,4 ; Enter command mode on a specific link 7=ilink,5 ; Link status 80=status,1 ; System info 81=status,2 ; Time 82=status,3 ; app_rpt.c Version 6=autopatchup ; Autopatch up 0=autopatchdn ; Autopatch down 99=cop,4 ; Audio test tone ; ; Link function table ; ; If this section is defined, then the remote user accessing our machine in command mode ; will only be able to do the functions defined in this section. If this section is ; omitted, then the link functions will be the same as the repeater functions. ; [link-functions] 1=ilink,1 ; Specific link disconnect 2=ilink,2 ; Specific Link connect - monitor only 3=ilink,3 ; Specific Link connect - transceive 7=ilink,5 ; Link status 80=status,1 ; System info 81=status,2 ; Time 82=status,3 ; app_rpt.c Version 6=autopatchup ; Autopatch up 0=autopatchdn ; Autopatch down 99=cop,4 ; Audio test tone [telemetry] ; Telemetry entries can be shared across all repeaters, or defined for each repeater. ; Can be a tone sequence, morse string, or a file ; ; |t - Tone escape sequence ; ; Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, duration, amplitude) ; Single frequencies are created by setting freq1 or freq2 to zero. ; ; |m - Morse escape sequence ; ; Sends Morse code at the telemetry amplitude and telemetry frequency as defined in the ; [morse] section. ; ; Follow with an alphanumeric string ; ; |i - Morse ID escape sequence ; ; Sends Morse code at the ID amplitude and ID frequency as defined in the ; [morse] section. ; ; Follow with an alphanumeric string ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ct2=|t(660,880,150,2048) ct3=|t(440,0,150,2048) ct4=|t(550,0,150,2048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ct8=|t(700,1100,150,2048) remotetx=|t(1633,0,75,2048)(0,0,75,0)(1209,0,75,2048); remotemon=|t(1209,0,75,2048) cmdmode=|t(900,903,200,2048) functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) ; ; Morse code parameters, these are common to all repeaters. ; [morse] speed=20 ; Approximate speed in WPM frequency=800 ; Morse Telemetry Frequency amplitude=4096 ; Morse Telemetry Amplitude idfrequency=1064 ; Morse ID Frequency idamplitude=3072 ; Morse ID Amplitude ; ; This section allows wait times for telemetry events to be adjusted ; A section for wait times can be defined for every repeater ; [wait-times] telemwait=1750 ; Time to wait before sending most telemetry idwait=500 ; Time to wait before starting ID unkeywait=1000 ; Time to wait after unkey before sending CT's and link telemetry calltermwait=1500 ; Time to wait before announcing "call terminated" ; ; This is where you define your nodes which can be connected to. ; [nodes] ;2057= radio at 127.0.0.1/2057,NONE ; This must be changed to your node number 3001=radio at 127.0.0.1/3001,NONE 3003=radio at 127.0.0.1/3003,NONE ; ; end of file ; And finally iax.conf ---------------------------- [root at auggie asterisk]# cat iax.conf ; Inter-Asterisk eXchange driver definition ; ; [general] bindport = 4569 ; Port to bind to (IAX is 4569) bindaddr = 0.0.0.0 ; Address to bind to (all addresses on machine) disallow=all allow=ulaw allow=alaw allow=gsm allow=g726 jitterbuffer=yes tos=lowdelay mailboxdetail=yes #include iax_additional.conf #include additional_a2billing_sip.conf ; Incoming radio connections [radio] type=user disallow=all allow=g726 allow=gsm codecpriority=host context=radio-secure [gui] type=user disallow=all allow=g726 allow=gsm codecpriority=host context=radio-gui ;secret=purdue secret=xxxxxxx NODE=3003 [radio] type=user disallow=all allow=g726 allow=gsm codecpriority=host context=radio-secure [gui] type=user disallow=all allow=g726 allow=gsm codecpriority=host context=radio-gui ;secret=purdue secret=xxxxxxx ; end of radios ; Setup for outgoing calls [yourprovider] ; This needs to change type=peer host=127.0.0.1 secret=nunya auth=md5 notransfer=yes disallow=all allow=gsm ---------------------------------------- Any help is appreciated. Steve Henke, W9SH From sph at xelatec.com Tue Dec 5 04:32:21 2006 From: sph at xelatec.com (Steven Henke) Date: Mon, 4 Dec 2006 23:32:21 -0500 (EST) Subject: [App_rpt] app-rpt W9SH Update Much Progress Message-ID: <42984.192.168.1.226.1165293141.squirrel@192.168.1.226> Hello Group, Well I've got both the repeater and the simplex radios simultaneously accessible via iaxRpt. Very neat! It took separate stanzas for both devices of course. It takes a while to get the concepts and syntax down for this system but hopefully I keep ramping up the learning curve. Now on to interconnect to the repeater as an extension. I wonder what will happen when I dial into the simplex radio? Will the Tx just stay up? VOX? # up, * down? More Later, Steve Henke, W9SH From gary at tcomeng.com Tue Dec 5 04:38:00 2006 From: gary at tcomeng.com (Gary) Date: Mon, 04 Dec 2006 20:38:00 -0800 Subject: [App_rpt] app-rpt W9SH Update Much Progress In-Reply-To: <42984.192.168.1.226.1165293141.squirrel@192.168.1.226> References: <42984.192.168.1.226.1165293141.squirrel@192.168.1.226> Message-ID: <4574F7A8.8010307@tcomeng.com> Look under the [repeater-commands] for cop,6 that defines the keyup dtmf command from the phone. It is usually set to 0 which means *0 for keyup and a # unkeys. Gary Steven Henke wrote: > Hello Group, > > Well I've got both the repeater and the simplex radios simultaneously > accessible via iaxRpt. Very neat! It took separate stanzas for both > devices of course. > > It takes a while to get the concepts and syntax down for this system but > hopefully I keep ramping up the learning curve. > > Now on to interconnect to the repeater as an extension. > > I wonder what will happen when I dial into the simplex radio? Will the Tx > just stay up? VOX? # up, * down? > > More Later, > > Steve Henke, W9SH > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt From f6hqz-m at hamwlan.net Tue Dec 5 06:24:26 2006 From: f6hqz-m at hamwlan.net (f6hqz-m at hamwlan.net) Date: Tue, 5 Dec 2006 07:24:26 +0100 Subject: [App_rpt] RE : Configuration Hints for Multiple Radios on 1 node In-Reply-To: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> Message-ID: 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 From sph at xelatec.com Tue Dec 5 06:29:34 2006 From: sph at xelatec.com (Steven Henke) Date: Tue, 5 Dec 2006 01:29:34 -0500 (EST) Subject: [App_rpt] RE : Configuration Hints for Multiple Radios on 1 node In-Reply-To: References: <45619.192.168.1.226.1165287119.squirrel@192.168.1.226> Message-ID: <45452.192.168.1.226.1165300174.squirrel@192.168.1.226> 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 > > From w4wwm at knology.net Wed Dec 6 05:19:10 2006 From: w4wwm at knology.net (Will) Date: Tue, 05 Dec 2006 23:19:10 -0600 Subject: [App_rpt] Asterisk controller to a CAT Controller(full duplex) Message-ID: <457652CE.1090900@knology.net> 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 From gary at tcomeng.com Wed Dec 6 05:39:22 2006 From: gary at tcomeng.com (Gary) Date: Tue, 05 Dec 2006 21:39:22 -0800 Subject: [App_rpt] Asterisk controller to a CAT Controller(full duplex) In-Reply-To: <457652CE.1090900@knology.net> References: <457652CE.1090900@knology.net> Message-ID: <4576578A.3050908@tcomeng.com> 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 From w4wwm at knology.net Wed Dec 6 23:28:45 2006 From: w4wwm at knology.net (Will Wright) Date: Wed, 06 Dec 2006 17:28:45 -0600 Subject: [App_rpt] Asterisk Controller to a Cat Controllerl Message-ID: <1165447726.3170.7.camel@localhost.localdomain> 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 From telesistant at hotmail.com Thu Dec 7 01:20:34 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Wed, 06 Dec 2006 17:20:34 -0800 Subject: [App_rpt] Asterisk Controller to a Cat Controllerl In-Reply-To: <1165447726.3170.7.camel@localhost.localdomain> Message-ID: nope, leave it in 4 wire >From: Will Wright >Reply-To: Asterisk Repeater Controler >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: >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 >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-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 From gary at tcomeng.com Thu Dec 7 02:17:22 2006 From: gary at tcomeng.com (Gary Young) Date: Wed, 6 Dec 2006 18:17:22 -0800 (PST) Subject: [App_rpt] Asterisk Controller to a Cat Controllerl In-Reply-To: <1165447726.3170.7.camel@localhost.localdomain> References: <1165447726.3170.7.camel@localhost.localdomain> Message-ID: <2496.209.234.101.99.1165457842.squirrel@tcomeng.com> 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 > From w4wwm at knology.net Thu Dec 7 06:10:56 2006 From: w4wwm at knology.net (Will Wright) Date: Thu, 07 Dec 2006 00:10:56 -0600 Subject: [App_rpt] Asterisk Controller and the CAT Controller Message-ID: <1165471857.3170.30.camel@localhost.localdomain> 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 From w4wwm at knology.net Fri Dec 8 03:12:03 2006 From: w4wwm at knology.net (Will) Date: Thu, 07 Dec 2006 21:12:03 -0600 Subject: [App_rpt] DTMF tones not passing to connec to oether nodes Message-ID: <4578D803.7080503@knology.net> 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 From gary at tcomeng.com Fri Dec 8 03:19:52 2006 From: gary at tcomeng.com (Gary) Date: Thu, 07 Dec 2006 19:19:52 -0800 Subject: [App_rpt] DTMF tones not passing to connec to oether nodes In-Reply-To: <4578D803.7080503@knology.net> References: <4578D803.7080503@knology.net> Message-ID: <4578D9D8.4050405@tcomeng.com> 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 From w4wwm at knology.net Fri Dec 8 08:51:48 2006 From: w4wwm at knology.net (Will) Date: Fri, 08 Dec 2006 02:51:48 -0600 Subject: [App_rpt] Asterick controller to a CAT controller Message-ID: <457927A4.6080007@knology.net> >>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 From telesistant at hotmail.com Fri Dec 8 11:11:26 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Fri, 08 Dec 2006 03:11:26 -0800 Subject: [App_rpt] Asterick controller to a CAT controller In-Reply-To: <457927A4.6080007@knology.net> Message-ID: 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 >Reply-To: Asterisk Repeater Controler >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: >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 >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-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 From gary at tcomeng.com Fri Dec 8 16:06:25 2006 From: gary at tcomeng.com (Gary) Date: Fri, 08 Dec 2006 08:06:25 -0800 Subject: [App_rpt] Asterick controller to a CAT controller In-Reply-To: References: Message-ID: <45798D81.8050303@tcomeng.com> Thanks Jim! This explains the mysterious in/outxlat feature that I never fully understood. Gary Jim Duuuude wrote: > 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 >> Reply-To: Asterisk Repeater Controler >> 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: >> 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 >> List-Unsubscribe: >> , >> List-Archive: >> List-Post: >> List-Help: >> List-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 From w7aor at narri.org Fri Dec 8 19:39:09 2006 From: w7aor at narri.org (Nevada Amateur Radio Repeaters, Inc.) Date: Fri, 8 Dec 2006 11:39:09 -0800 Subject: [App_rpt] FW: [asterisk_radio] Fwd: 2007 IRLP Conference Message-ID: <000601c71b00$89ff2c20$32e3fa40@kbj16da0678ae8> -----Original Message----- From: asterisk_radio at yahoogroups.com [mailto:asterisk_radio at yahoogroups.com] On Behalf Of w7aor Sent: Wednesday, December 06, 2006 10:39 AM To: asterisk_radio at yahoogroups.com; erc_ecs at yahoogroups.com; GE-MastrII at yahoogroups.com; InternetLinking at yahoogroups.com; motorola_radio_discussion at yahoogroups.com; NV_ARES at yahoogroups.com; Repeater-Builder at yahoogroups.com; VoIP_American_Red_Cross_Communicators_Net at yahoogroups.com; VOIP-WXNET at yahoogroups.com; w7aor at narri.org Subject: [asterisk_radio] Fwd: 2007 IRLP Conference "Nevada Amateur Radio Repeaters, Inc." 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. 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 in this topic (1) Reply (via web post) | Start a new topic Messages | Files | Photos | Links | Database | Polls | Members | Calendar Yahoo! Groups Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch format to Traditional Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe Visit Your Group Y! GeoCities Be Interactive Create a conver- sation with blogs. Free Blogging Y! Web Hosting Share your views with the world. Yahoo! Groups Start a group in 3 easy steps. Connect with others. . __,_._,___ -------------- next part -------------- An HTML attachment was scrubbed... URL: From w7aor at narri.org Fri Dec 8 19:40:17 2006 From: w7aor at narri.org (Nevada Amateur Radio Repeaters, Inc.) Date: Fri, 8 Dec 2006 11:40:17 -0800 Subject: [App_rpt] FW: [asterisk_radio] Fwd: 2007 IRLP Conference Message-ID: <000b01c71b00$b214b540$32e3fa40@kbj16da0678ae8> -----Original Message----- From: asterisk_radio at yahoogroups.com [mailto:asterisk_radio at yahoogroups.com] On Behalf Of w7aor Sent: Wednesday, December 06, 2006 10:39 AM To: asterisk_radio at yahoogroups.com; erc_ecs at yahoogroups.com; GE-MastrII at yahoogroups.com; InternetLinking at yahoogroups.com; motorola_radio_discussion at yahoogroups.com; NV_ARES at yahoogroups.com; Repeater-Builder at yahoogroups.com; VoIP_American_Red_Cross_Communicators_Net at yahoogroups.com; VOIP-WXNET at yahoogroups.com; w7aor at narri.org Subject: [asterisk_radio] Fwd: 2007 IRLP Conference --- In irlp at yahoogroups. com, "Nevada Amateur Radio Repeaters, Inc." 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. 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 in this topic (1) Reply (via web post) | Start a new topic Messages | Files | Photos | Links | Database | Polls | Members | Calendar Yahoo! Groups Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch format to Traditional Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe Visit Your Group Y! GeoCities Be Interactive Create a conver- sation with blogs. Free Blogging Y! Web Hosting Share your views with the world. Yahoo! Groups Start a group in 3 easy steps. Connect with others. . __,_._,___ -------------- next part -------------- An HTML attachment was scrubbed... URL: From w7aor at narri.org Fri Dec 8 19:49:20 2006 From: w7aor at narri.org (Nevada Amateur Radio Repeaters, Inc.) Date: Fri, 8 Dec 2006 11:49:20 -0800 Subject: [App_rpt] How are Steve and Jim doing? In-Reply-To: Message-ID: <001a01c71b01$f5318910$32e3fa40@kbj16da0678ae8> 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" Subject: Re: [App_rpt] RE : Configuration Hints for Multiple Radios on 1 node To: f6hqz-m at hamwlan.net Cc: 'Asterisk Repeater Controler' 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 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 Subject: Re: [App_rpt] Asterisk controller to a CAT Controller(full duplex) To: Asterisk Repeater Controler 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 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" Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl To: app_rpt at lists.illiana.net Message-ID: Content-Type: text/plain; format=flowed nope, leave it in 4 wire >From: Will Wright >Reply-To: Asterisk Repeater Controler >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: >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 >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-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" Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl To: "Asterisk Repeater Controler" 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 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 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 Subject: Re: [App_rpt] DTMF tones not passing to connec to oether nodes To: Asterisk Repeater Controler 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 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" Subject: Re: [App_rpt] Asterick controller to a CAT controller To: app_rpt at lists.illiana.net Message-ID: 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 >Reply-To: Asterisk Repeater Controler >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: >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 >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-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 ************************************** From w4wwm at knology.net Sat Dec 9 05:19:54 2006 From: w4wwm at knology.net (Will Wright) Date: Fri, 08 Dec 2006 23:19:54 -0600 Subject: [App_rpt] Alien Interfaces Message-ID: <1165641595.2874.57.camel@localhost.localdomain> 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 From telesistant at hotmail.com Sat Dec 9 13:17:30 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 09 Dec 2006 05:17:30 -0800 Subject: [App_rpt] Alien Interfaces In-Reply-To: <1165641595.2874.57.camel@localhost.localdomain> Message-ID: no. you set up your alien system in whatever normal manner those types of systems get set up in. if it has node numbers, then set them up, if not, then it doesnt. the app_rpt node numbers only have to do with app_rpt. So you assign a node number to your gaeway node (the one thats hooked up to the ailen system). Then, the ailen system, as a whole, will be known to the app_rpt systems as the node number you assign to the gateway. >From: Will Wright >Reply-To: Asterisk Repeater Controler >To: app_rpt at lists.illiana.net >Subject: [App_rpt] Alien Interfaces >Date: Fri, 08 Dec 2006 23:19:54 -0600 >MIME-Version: 1.0 >Received: from lists.illiana.net ([64.212.212.35]) by >bay0-mc5-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 8 >Dec 2006 21:21:03 -0800 >Received: (qmail 28246 invoked from network); 9 Dec 2006 05:20:02 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 9 >Dec 2006 05:20:02 -0000 >Received: (qmail 28225 invoked from network); 9 Dec 2006 05:19:59 -0000 >Received: from smtp.knology.net (24.214.63.101)by 0 with SMTP; 9 Dec 2006 >05:19:59 -0000 >Received: (qmail 22465 invoked by uid 0); 9 Dec 2006 05:19:56 -0000 >Received: from unknown (HELO ?192.168.1.101?) (24.214.57.115)by >smtp1.knology.net with SMTP; 9 Dec 2006 05:19:56 -0000 >X-Message-Info: txF49lGdW43jU32uNaSXfYXDyrVgX8V49EHto+wlPF0= >Return-Path: >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 >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net >X-OriginalArrivalTime: 09 Dec 2006 05:21:03.0453 (UTC) >FILETIME=[D21968D0:01C71B51] > >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 > >_______________________________________________ >App_rpt mailing list >App_rpt at lists.illiana.net >http://lists.illiana.net/mailman/listinfo/app_rpt From hwstar at rodgers.sdcoxmail.com Sun Dec 10 23:03:52 2006 From: hwstar at rodgers.sdcoxmail.com (hwstar at rodgers.sdcoxmail.com) Date: Sun, 10 Dec 2006 15:03:52 -0800 Subject: [App_rpt] How are Steve and Jim doing? Message-ID: <20061210230353.KWDI60.dukecmmtao03.coxmail.com@dukecmmtao03> All As of 12/7 Im out of surgery and am starting physical therapy. Steve, WA6ZFT > > From: "Nevada Amateur Radio Repeaters, Inc." > Date: 2006/12/08 Fri AM 11:49:20 PST > To: > Subject: [App_rpt] How are Steve and Jim doing? > > 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" > Subject: Re: [App_rpt] RE : Configuration Hints for Multiple Radios on > 1 node > To: f6hqz-m at hamwlan.net > Cc: 'Asterisk Repeater Controler' > 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 > 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 > Subject: Re: [App_rpt] Asterisk controller to a CAT Controller(full > duplex) > To: Asterisk Repeater Controler > 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 > 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" > Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl > To: app_rpt at lists.illiana.net > Message-ID: > Content-Type: text/plain; format=flowed > > nope, leave it in 4 wire > > > >From: Will Wright > >Reply-To: Asterisk Repeater Controler > >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: > >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 > >List-Unsubscribe: > >, @lists.illiana.net?subject=unsubscribe> > >List-Archive: > >List-Post: > >List-Help: > >List-Subscribe: > >, @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" > Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl > To: "Asterisk Repeater Controler" > 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 > 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 > 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 > Subject: Re: [App_rpt] DTMF tones not passing to connec to oether > nodes > To: Asterisk Repeater Controler > 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 > 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" > Subject: Re: [App_rpt] Asterick controller to a CAT controller > To: app_rpt at lists.illiana.net > Message-ID: > 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 > >Reply-To: Asterisk Repeater Controler > >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: > >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 > >List-Unsubscribe: > >, @lists.illiana.net?subject=unsubscribe> > >List-Archive: > >List-Post: > >List-Help: > >List-Subscribe: > >, @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 > ************************************** > > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > From rhammock at speakeasy.net Sun Dec 10 23:14:37 2006 From: rhammock at speakeasy.net (Randy Hammock) Date: Sun, 10 Dec 2006 15:14:37 -0800 Subject: [App_rpt] How are Steve and Jim doing? In-Reply-To: <20061210230353.KWDI60.dukecmmtao03.coxmail.com@dukecmmtao03> References: <20061210230353.KWDI60.dukecmmtao03.coxmail.com@dukecmmtao03> Message-ID: <1165792477.28904.75.camel@red.kc6hur.net> On Sun, 2006-12-10 at 15:03 -0800, hwstar at rodgers.sdcoxmail.com wrote: > > All > > As of 12/7 Im out of surgery and am starting > physical therapy. > > Steve, WA6ZFT Most excellent! We've been rooting for ya. -- Randy Hammock KC6HUR IRLP 4494 EchoLink 120688 (KC6HUR-L) http://kc6hur.net http://irlp.kc6hur.net From gary at tcomeng.com Mon Dec 11 03:55:50 2006 From: gary at tcomeng.com (Gary) Date: Sun, 10 Dec 2006 19:55:50 -0800 Subject: [App_rpt] How are Steve and Jim doing? In-Reply-To: <20061210230353.KWDI60.dukecmmtao03.coxmail.com@dukecmmtao03> References: <20061210230353.KWDI60.dukecmmtao03.coxmail.com@dukecmmtao03> Message-ID: <457CD6C6.1010103@tcomeng.com> Great to hear from you Steve! Hope things go well for your recovery. Gary hwstar at rodgers.sdcoxmail.com wrote: > > All > > As of 12/7 Im out of surgery and am starting > physical therapy. > > Steve, WA6ZFT > >> From: "Nevada Amateur Radio Repeaters, Inc." >> Date: 2006/12/08 Fri AM 11:49:20 PST >> To: >> Subject: [App_rpt] How are Steve and Jim doing? >> >> 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" >> Subject: Re: [App_rpt] RE : Configuration Hints for Multiple Radios on >> 1 node >> To: f6hqz-m at hamwlan.net >> Cc: 'Asterisk Repeater Controler' >> 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 >> 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 >> Subject: Re: [App_rpt] Asterisk controller to a CAT Controller(full >> duplex) >> To: Asterisk Repeater Controler >> 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 >> 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" >> Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl >> To: app_rpt at lists.illiana.net >> Message-ID: >> Content-Type: text/plain; format=flowed >> >> nope, leave it in 4 wire >> >> >>> From: Will Wright >>> Reply-To: Asterisk Repeater Controler >>> 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: >>> 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 >>> List-Unsubscribe: >>> ,> @lists.illiana.net?subject=unsubscribe> >>> List-Archive: >>> List-Post: >>> List-Help: >>> List-Subscribe: >>> ,> @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" >> Subject: Re: [App_rpt] Asterisk Controller to a Cat Controllerl >> To: "Asterisk Repeater Controler" >> 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 >> 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 >> 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 >> Subject: Re: [App_rpt] DTMF tones not passing to connec to oether >> nodes >> To: Asterisk Repeater Controler >> 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 >> 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" >> Subject: Re: [App_rpt] Asterick controller to a CAT controller >> To: app_rpt at lists.illiana.net >> Message-ID: >> 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 >>> Reply-To: Asterisk Repeater Controler >>> 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: >>> 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 >>> List-Unsubscribe: >>> ,> @lists.illiana.net?subject=unsubscribe> >>> List-Archive: >>> List-Post: >>> List-Help: >>> List-Subscribe: >>> ,> @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 >> ************************************** >> >> _______________________________________________ >> 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 From w4wwm at knology.net Tue Dec 26 05:38:32 2006 From: w4wwm at knology.net (Will Wright) Date: Mon, 25 Dec 2006 23:38:32 -0600 Subject: [App_rpt] Log files after operating in command mode Message-ID: <1167111512.17044.18.camel@localhost.localdomain> 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 From niagassas_ang at tellas.gr Sat Dec 30 21:18:55 2006 From: niagassas_ang at tellas.gr (=?iso-8859-7?B?zenh49zz4fIgwePj5evv8g==?=) Date: Sat, 30 Dec 2006 23:18:55 +0200 Subject: [App_rpt] Newbie in Asterisk Message-ID: 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 at 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 at 127.0.0.1/1999 1998 = radio at 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 at hotmail.com eMail: niagassas_ang at tellas.gr -------------- next part -------------- An HTML attachment was scrubbed... URL: From f6hqz-m at hamwlan.net Sat Dec 30 22:27:58 2006 From: f6hqz-m at hamwlan.net (f6hqz-m at hamwlan.net) Date: Sat, 30 Dec 2006 23:27:58 +0100 Subject: [App_rpt] RE : Newbie in Asterisk In-Reply-To: Message-ID: Hi Niagassas, Nice to hear from you. If you have trouble with the opto-transistor and the polarity change, you can use an opto-triac which doesn't care of the polarity of the line. This can close the line when the COR/BUSY condition change during RX state. But, I have never checked my interface under this condition (e&m only) and I don't know in advance if this will be ok for your project, sorry. Tell me more when you will do other tests. I will tempt from my side if I will have the time next week if nobody has a better idea to help you. Best 73's, F6HQZ, Francois BERGERET. -----Message d'origine----- De : ???????? ??????? [mailto:niagassas_ang at tellas.gr] Envoy? : samedi 30 d?cembre 2006 22:19 ? : app_rpt at lists.illiana.net Cc : f6hqz-m at hamwlan.net Objet : Newbie in Asterisk 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 at 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 at 127.0.0.1/1999 1998 = radio at 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 at hotmail.com eMail: niagassas_ang at tellas.gr -------------- next part -------------- An HTML attachment was scrubbed... URL: