From eric at lylix.net Tue Jun 6 00:12:00 2006 From: eric at lylix.net (Eric Tichansky) Date: Mon, 05 Jun 2006 20:12:00 -0400 Subject: [App_rpt] app_rpt.c test version 0-46-6 In-Reply-To: <200605132108.16608.hwstar@rodgers.sdcoxmail.com> References: <200605132108.16608.hwstar@rodgers.sdcoxmail.com> Message-ID: <4484C850.4040708@lylix.net> URL not found... is it in SVN? Eric NI3S Steve Rodgers wrote: > Well, I decided I didn't like the way the autopatch default overrides > (patchfarenddisconnect, patchnoct, patchdialtime) were implemented in > app_rpt.pre-0-46-4.c so I ripped them out and started over. > > This method provides much more flexibility. Instead of specifying settings in > the node configuration block, you now override the defaults in the function > block for autopatch up. In other words, autopatchup can can optionally take > comma delimited setting=value pairs. > > There are currently 5 setting=value pairs defined in app_rpt.pre-0-46-6.c: > > context=string > > Override default context with "string" > > dialtime=ms > > Specify the max number of milliseconds between phone number ) > > farenddisconnect=1 > > Automatically disconnect when called party hangs up > > noct=1 > > Don't send repeater courtesy tone during autopatch calls > > quiet=1 > > Don't send dial tone, or connect messages. Do not send patch down message when > called party hangs up > > > Example: 123=autopatchup,dialtime=20000,noct=1,farenddisconnect=1 > > The example will set a 20 second limit on dial time between phone number > digits, not send the courtesy tone during the time the patch is up, and > disconnect the patch if the called party hangs up. > > By redoing this, we gain a whole bunch more flexibility because we can define > several different DTMF sequences for autopatchup which can direct the > autopatch to act differently. By defining 3 different patch up sequences, you > can now for example, have one for emergency numbers, one for normal numbers, > and one for system information messages. You can set the individual autopatch > up sequences to use different contexts which can then be added to > extensions.conf. > > Note: I did not remove the autopatch up and down messages from the telemetry > block. These are still there so that you can override the default up and down > messages. > > app_rpt.pre-0-46-6c can be downloaded from http://zapatatelephony.com using > the following URL: > > http://zapatatelephony.com/app_rpt.pre-0-46-6.c > > Note: are running asterisk 1.2.7.1 or earlier, you will need to uncomment the > #define for OLD_ASTERISK at the top of the file. > > Steve WA6ZFT > > > > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > -- Eric Tichansky Administrator LYLIX.NET http://lylix.net/ (724) 602-2264 From hwstar at rodgers.sdcoxmail.com Tue Jun 6 01:04:07 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Mon, 5 Jun 2006 18:04:07 -0700 Subject: [App_rpt] app_rpt.c test version 0-46-6 In-Reply-To: <4484C850.4040708@lylix.net> References: <200605132108.16608.hwstar@rodgers.sdcoxmail.com> <4484C850.4040708@lylix.net> Message-ID: <200606051804.07321.hwstar@rodgers.sdcoxmail.com> Eric, Yes app_rpt version 0.46 is in Digium SVN as revision 29935 or later. Better to use the the released version as it has a notch filtering feature as well. Steve. On Monday 05 June 2006 17:12, Eric Tichansky wrote: > URL not found... is it in SVN? > > Eric NI3S > > Steve Rodgers wrote: > > Well, I decided I didn't like the way the autopatch default overrides > > (patchfarenddisconnect, patchnoct, patchdialtime) were implemented in > > app_rpt.pre-0-46-4.c so I ripped them out and started over. > > > > This method provides much more flexibility. Instead of specifying > > settings in the node configuration block, you now override the defaults > > in the function block for autopatch up. In other words, autopatchup can > > can optionally take comma delimited setting=value pairs. > > > > There are currently 5 setting=value pairs defined in > > app_rpt.pre-0-46-6.c: > > > > context=string > > > > Override default context with "string" > > > > dialtime=ms > > > > Specify the max number of milliseconds between phone number ) > > > > farenddisconnect=1 > > > > Automatically disconnect when called party hangs up > > > > noct=1 > > > > Don't send repeater courtesy tone during autopatch calls > > > > quiet=1 > > > > Don't send dial tone, or connect messages. Do not send patch down message > > when called party hangs up > > > > > > Example: 123=autopatchup,dialtime=20000,noct=1,farenddisconnect=1 > > > > The example will set a 20 second limit on dial time between phone number > > digits, not send the courtesy tone during the time the patch is up, and > > disconnect the patch if the called party hangs up. > > > > By redoing this, we gain a whole bunch more flexibility because we can > > define several different DTMF sequences for autopatchup which can direct > > the autopatch to act differently. By defining 3 different patch up > > sequences, you can now for example, have one for emergency numbers, one > > for normal numbers, and one for system information messages. You can set > > the individual autopatch up sequences to use different contexts which can > > then be added to extensions.conf. > > > > Note: I did not remove the autopatch up and down messages from the > > telemetry block. These are still there so that you can override the > > default up and down messages. > > > > app_rpt.pre-0-46-6c can be downloaded from http://zapatatelephony.com > > using the following URL: > > > > http://zapatatelephony.com/app_rpt.pre-0-46-6.c > > > > Note: are running asterisk 1.2.7.1 or earlier, you will need to > > uncomment the #define for OLD_ASTERISK at the top of the file. > > > > Steve WA6ZFT > > > > > > > > _______________________________________________ > > App_rpt mailing list > > App_rpt at lists.illiana.net > > http://lists.illiana.net/mailman/listinfo/app_rpt From eric at lylix.net Tue Jun 6 14:18:32 2006 From: eric at lylix.net (Eric Tichansky) Date: Tue, 06 Jun 2006 10:18:32 -0400 Subject: [App_rpt] app_rpt.c test version 0-46-6 In-Reply-To: <200606051804.07321.hwstar@rodgers.sdcoxmail.com> References: <200605132108.16608.hwstar@rodgers.sdcoxmail.com> <4484C850.4040708@lylix.net> <200606051804.07321.hwstar@rodgers.sdcoxmail.com> Message-ID: <44858EB8.2010602@lylix.net> Super. Just built version 0.47 from SVN on my Asterisk 1.2.5 system. The new autopatch features are excellent additions! Thumbs up! I finally acquired two mini HTs (2M and 440) from a recent local hamfest, and have been able to do alot of testing. Between the additional duplex states and the new autopatch features, the system is quite robust and fits the bill perfectly. It is nice to be able to run a full duplex autopatch w/o RX audio injection to the transmit side. Great work. Eventually we plan to setup remote links to another app_rpt enabled repeater for greater coverage. Eric NI3S Steve Rodgers wrote: > Eric, > > Yes app_rpt version 0.46 is in Digium SVN as revision 29935 or later. > Better to use the the released version as it has a notch filtering feature as > well. > > Steve. > > -- Eric Tichansky Administrator LYLIX.NET http://lylix.net/ (724) 602-2264 From hwstar at rodgers.sdcoxmail.com Tue Jun 6 17:36:59 2006 From: hwstar at rodgers.sdcoxmail.com (hwstar at rodgers.sdcoxmail.com) Date: Tue, 6 Jun 2006 10:36:59 -0700 Subject: [App_rpt] app_rpt.c test version 0-46-6 Message-ID: <20060606173701.QGDU3326.dukecmmtao03.coxmail.com@dukecmmtao03> Eric, Glad to see you are up and runnign with 0.47. Will you be linking with RF to the remote site, or are you planning on doing the link with app_rpt over the Internet? Steve WA6ZFT > > From: Eric Tichansky > Date: 2006/06/06 Tue AM 07:18:32 PDT > To: Asterisk Repeater Controler > Subject: Re: [App_rpt] app_rpt.c test version 0-46-6 > > Super. Just built version 0.47 from SVN on my Asterisk 1.2.5 system. > The new autopatch features are excellent additions! Thumbs up! > > I finally acquired two mini HTs (2M and 440) from a recent local > hamfest, and have been able to do alot of testing. Between the > additional duplex states and the new autopatch features, the system is > quite robust and fits the bill perfectly. It is nice to be able to run > a full duplex autopatch w/o RX audio injection to the transmit side. > Great work. Eventually we plan to setup remote links to another app_rpt > enabled repeater for greater coverage. > > Eric NI3S > > Steve Rodgers wrote: > > Eric, > > > > Yes app_rpt version 0.46 is in Digium SVN as revision 29935 or later. > > Better to use the the released version as it has a notch filtering feature as > > well. > > > > Steve. > > > > > -- > > Eric Tichansky > Administrator > LYLIX.NET > http://lylix.net/ > > (724) 602-2264 > > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > From eric at lylix.net Tue Jun 6 17:50:26 2006 From: eric at lylix.net (Eric Tichansky) Date: Tue, 06 Jun 2006 13:50:26 -0400 Subject: [App_rpt] app_rpt.c test version 0-46-6 In-Reply-To: <20060606173701.QGDU3326.dukecmmtao03.coxmail.com@dukecmmtao03> References: <20060606173701.QGDU3326.dukecmmtao03.coxmail.com@dukecmmtao03> Message-ID: <4485C062.4070708@lylix.net> Steve I haven't considered which method as of yet, nor have I explored the capabilities of app_rpt for Internet linking. At this stage, for the sake of reliability and to aide in non-congestion of the bands, we would probably go for Internet linking. The equipment we are using for the repeater itself is rather low-cost and aged, but performs very well for it's limited use atm (HW-2036A RX, Midland 70-525B TX - 20W, Astron 35, 2M 11-el yagi, 440 3-el yagi). The setup would be rather easy to duplicate at another location and be quite cost effective. The use of yagis was chosen to provide a specific coverage area, but perhaps the next site will have verticals for more general coverage. Eric NI3S hwstar at rodgers.sdcoxmail.com wrote: > Eric, > > Glad to see you are up and runnign with 0.47. Will you be linking with RF to the remote site, or are you planning on doing the link with app_rpt over the Internet? > > Steve WA6ZFT > > -- Eric Tichansky Administrator LYLIX.NET http://lylix.net/ (724) 602-2264 From jon+apprpt at unicomsystems.com Thu Jun 22 23:31:50 2006 From: jon+apprpt at unicomsystems.com (jon+apprpt at unicomsystems.com) Date: Fri, 23 Jun 2006 09:31:50 +1000 Subject: [App_rpt] Interface questions Message-ID: <20060622233150.GB1570@unicomsystems.com> Hello all, First off, I must say that app_rpt looks like a very promising project and this style or repeater controller looks like the way of the future. I have a few questions that I couldn't quite come up with an answer for myself with a high degree of certainty, using the existing material online. 1). Does the 4 port radio interface card allow for 4 duplex repeater channels, or 2 duplex repeater channels? 2). The 600 ohm line transformer as used in the analogue radio interface appears to be out of stock on Digikey. Does anyone have alternative stockists or transformer models? Or even spares they'd be willing to sell? 3). Is app_rpt compatible with the TDM1200P or similar? I also have a few more developmental/roadmap oriented questions, namely, would it be possible for an interface to be developed that used a full duplex sound card and a serial or other data port to interface to a radio? Or could an interface be developed that had the necessary functions so that it only needed an FXO port on the Asterisk side, seeing FXOs can be got from even basic devices like some winmodems? Note that I'm not trying to rubbish the project or its developers with these questions, I'm sure the current interfaces work very well, but seeing as we're not interfacing phones, I thought it would've been possible design a way to interface at an even lower price point, opening access further, and further benefiting app_rpt with greater uptake levels from all sorts of radio people around the world. Best Regards, Jon From hwstar at rodgers.sdcoxmail.com Fri Jun 23 14:36:32 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Fri, 23 Jun 2006 07:36:32 -0700 Subject: [App_rpt] Interface questions In-Reply-To: <20060622233150.GB1570@unicomsystems.com> References: <20060622233150.GB1570@unicomsystems.com> Message-ID: <200606230736.32332.hwstar@rodgers.sdcoxmail.com> Jon, See responses below. On Thursday 22 June 2006 16:31, jon+apprpt at unicomsystems.com wrote: > Hello all, > > First off, I must say that app_rpt looks like a very promising project > and this style or repeater controller looks like the way of the future. > > I have a few questions that I couldn't quite come up with an answer for > myself with a high degree of certainty, using the existing material > online. > 1). Does the 4 port radio interface card allow for 4 duplex repeater > channels, or 2 duplex repeater channels? 4 duplex radio channels. > > 2). The 600 ohm line transformer as used in the analogue radio interface > appears to be out of stock on Digikey. Does anyone have alternative > stockists or transformer models? Or even spares they'd be willing to sell? Last time we bought them form excesssolutions.com > > 3). Is app_rpt compatible with the TDM1200P or similar? We haven't tested this but the chips used on the TDM1200p are exactly the same as the ones used on the TDM400. > > I also have a few more developmental/roadmap oriented questions, namely, > would it be possible for an interface to be developed that used a full > duplex sound card and a serial or other data port to interface to a radio? > Or could an interface be developed that had the necessary functions so that > it only needed an FXO port on the Asterisk side, seeing FXOs can be got > from even basic devices like some winmodems? Too many sound cards out there to support and having to deal with all of them is a burden we don't want to shoulder. > > Note that I'm not trying to rubbish the project or its developers with > these questions, I'm sure the current interfaces work very well, but seeing > as we're not interfacing phones, I thought it would've been possible design > a way to interface at an even lower price point, opening access further, > and further benefiting app_rpt with greater uptake levels from all sorts of > radio people around the world. Let's just say that we are aware of this issue, and that we are working on a solution. > > > Best Regards, > > Jon > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt From clayton.hull at illuminatnm.com Mon Jun 26 16:00:21 2006 From: clayton.hull at illuminatnm.com (clayton.hull) Date: Mon, 26 Jun 2006 12:00:21 -0400 Subject: [App_rpt] Autorun macro Message-ID: <000001c69939$a1525170$753fa8c0@claytonh> Is there any way to run a macro in app_rpt automatically on startup? (For example, to command a node to link to other nodes automatically.) Clayton From telesistant at hotmail.com Mon Jun 26 17:24:36 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 26 Jun 2006 10:24:36 -0700 Subject: [App_rpt] Autorun macro In-Reply-To: <000001c69939$a1525170$753fa8c0@claytonh> Message-ID: of course, that what startup_macro is for in app_rpt. for example startup_macro = *31234*35678 would automatically link up node 1234 and 5678 >From: "clayton.hull" >Reply-To: clayton.hull at illuminatnm.com,Asterisk Repeater Controler > >To: >Subject: [App_rpt] Autorun macro >Date: Mon, 26 Jun 2006 12:00:21 -0400 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc12-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Mon, >26 Jun 2006 10:02:28 -0700 >Received: (qmail 16468 invoked from network); 26 Jun 2006 15:59:32 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 26 >Jun 2006 15:59:32 -0000 >Received: (qmail 16453 invoked from network); 26 Jun 2006 15:59:29 -0000 >Received: from upstart1.illuminatnm.com (196.3.142.204)by 0 with SMTP; 26 >Jun 2006 15:59:29 -0000 >Received: from mrserv1.neal-and-massy.com by upstart1.illuminatnm.comvia >smtpd (for marauder.illiana.net [207.227.243.140]) with ESMTP;Wed, 19 Apr >2006 10:23:27 -0400 >Received: from relib1.neal-and-massy.com ([196.3.142.202]) >bymrserv1.neal-and-massy.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 26 >Jun 2006 11:59:11 -0400 >Received: from relib1.neal-and-massy.com ([196.3.142.202]) >byrelib1.neal-and-massy.comvia smtpd (for mrserv1.neal-and-massy.com >[192.168.1.8]) with ESMTP;Wed, 19 Apr 2006 10:23:25 -0400 >X-Message-Info: txF49lGdW438Hukf+AQaeSFYDc+hncvXNhTG/06vmpo= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-MSMail-Priority: Normal >X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 >Return-Path: clayton.hull at illuminatnm.com >X-OriginalArrivalTime: 26 Jun 2006 15:59:11.0468 >(UTC)FILETIME=[76F65AC0:01C69939] >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 > >Is there any way to run a macro in app_rpt automatically on startup? >(For example, to command a node to link to other nodes automatically.) > >Clayton > >_______________________________________________ >App_rpt mailing list >App_rpt at lists.illiana.net >http://lists.illiana.net/mailman/listinfo/app_rpt From f6hqz-m at hamwlan.net Mon Jun 26 18:52:41 2006 From: f6hqz-m at hamwlan.net (f6hqz-m at hamwlan.net) Date: Mon, 26 Jun 2006 20:52:41 +0200 Subject: [App_rpt] RE : Autorun macro In-Reply-To: Message-ID: Hello Jim and the list, Wow ! Very interesting, realy ! Jim, have you some other good tips like this or a complete features list ? I have not seen such a comment into your source code. I MUST certainly re-read it with more attention ;-) Is the list knows that I have now a simplex VHF base in France to remotely use by them ? VHF is actualy not so used here, due to HF migration of all our HAM's licenses for about 2 years. We can hear some VHF / UHF traffic near during contests only :-( I think that if you, guys, call my french HAM's friends from time to time, you must attract few international app_RPT good traffic. 73, F6HQZ, Francois BERGERET, France. -----Message d'origine----- De : app_rpt-bounces at lists.illiana.net [mailto:app_rpt-bounces at lists.illiana.net] De la part de Jim Duuuude Envoy? : lundi 26 juin 2006 19:25 ? : app_rpt at lists.illiana.net Objet : Re: [App_rpt] Autorun macro of course, that what startup_macro is for in app_rpt. for example startup_macro = *31234*35678 would automatically link up node 1234 and 5678 >From: "clayton.hull" >Reply-To: clayton.hull at illuminatnm.com,Asterisk Repeater Controler > >To: >Subject: [App_rpt] Autorun macro >Date: Mon, 26 Jun 2006 12:00:21 -0400 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc12-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Mon, >26 Jun 2006 10:02:28 -0700 >Received: (qmail 16468 invoked from network); 26 Jun 2006 15:59:32 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 26 >Jun 2006 15:59:32 -0000 >Received: (qmail 16453 invoked from network); 26 Jun 2006 15:59:29 -0000 >Received: from upstart1.illuminatnm.com (196.3.142.204)by 0 with SMTP; 26 >Jun 2006 15:59:29 -0000 >Received: from mrserv1.neal-and-massy.com by upstart1.illuminatnm.comvia >smtpd (for marauder.illiana.net [207.227.243.140]) with ESMTP;Wed, 19 Apr >2006 10:23:27 -0400 >Received: from relib1.neal-and-massy.com ([196.3.142.202]) >bymrserv1.neal-and-massy.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 26 >Jun 2006 11:59:11 -0400 >Received: from relib1.neal-and-massy.com ([196.3.142.202]) >byrelib1.neal-and-massy.comvia smtpd (for mrserv1.neal-and-massy.com >[192.168.1.8]) with ESMTP;Wed, 19 Apr 2006 10:23:25 -0400 >X-Message-Info: txF49lGdW438Hukf+AQaeSFYDc+hncvXNhTG/06vmpo= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-MSMail-Priority: Normal >X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 >Return-Path: clayton.hull at illuminatnm.com >X-OriginalArrivalTime: 26 Jun 2006 15:59:11.0468 >(UTC)FILETIME=[76F65AC0:01C69939] >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 > >Is there any way to run a macro in app_rpt automatically on startup? >(For example, to command a node to link to other nodes automatically.) > >Clayton > >_______________________________________________ >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 jon+apprpt at unicomsystems.com Tue Jun 27 03:48:51 2006 From: jon+apprpt at unicomsystems.com (jon+apprpt at unicomsystems.com) Date: Tue, 27 Jun 2006 13:48:51 +1000 Subject: [App_rpt] Interface questions In-Reply-To: <200606230736.32332.hwstar@rodgers.sdcoxmail.com> References: <20060622233150.GB1570@unicomsystems.com> <200606230736.32332.hwstar@rodgers.sdcoxmail.com> Message-ID: <20060627034851.GA20217@unicomsystems.com> Hello Steve, On Fri, Jun 23, 2006 at 07:36:32AM -0700, Steve Rodgers wrote: > Jon, > > See responses below. > > On Thursday 22 June 2006 16:31, jon+apprpt at unicomsystems.com wrote: > > Hello all, > > > > First off, I must say that app_rpt looks like a very promising project > > and this style or repeater controller looks like the way of the future. > > > > I have a few questions that I couldn't quite come up with an answer for > > myself with a high degree of certainty, using the existing material > > online. > > 1). Does the 4 port radio interface card allow for 4 duplex repeater > > channels, or 2 duplex repeater channels? > > 4 duplex radio channels. > > Excellent, makes it the best value for money for > 2 channels. > > > > 2). The 600 ohm line transformer as used in the analogue radio interface > > appears to be out of stock on Digikey. Does anyone have alternative > > stockists or transformer models? Or even spares they'd be willing to sell? > > Last time we bought them form excesssolutions.com Hrm, they certainly have plenty, and at a good price, but overseas UPS shipping is a killer, about USD$100 to ship a dozen or so to Australia. Does anyone have spare stock they want to sell or are willing to order on my behalf and resend using USPS? > > > > > 3). Is app_rpt compatible with the TDM1200P or similar? > > We haven't tested this but the chips used on the TDM1200p are exactly the same > as the ones used on the TDM400. > Is it hard to support different FXS devices? I'm not sure exactly how entwined app_rpt is with driver code. The reason I ask is one possible avenue for me is some clone TDM cards from http://www.openvox.com.cn but it looks like their TDM1200P clone uses a different driver. Their 400P uses the standard digium driver. > > > > I also have a few more developmental/roadmap oriented questions, namely, > > would it be possible for an interface to be developed that used a full > > duplex sound card and a serial or other data port to interface to a radio? > > Or could an interface be developed that had the necessary functions so that > > it only needed an FXO port on the Asterisk side, seeing FXOs can be got > > from even basic devices like some winmodems? > > Too many sound cards out there to support and having to deal with all of them > is a burden we don't want to shoulder. > Fair enough, and looking at the inadequacy and system specificness of other repeater linking hardware systems around, this is a condition I'm willing to live with. > > > > > Note that I'm not trying to rubbish the project or its developers with > > these questions, I'm sure the current interfaces work very well, but seeing > > as we're not interfacing phones, I thought it would've been possible design > > a way to interface at an even lower price point, opening access further, > > and further benefiting app_rpt with greater uptake levels from all sorts of > > radio people around the world. > > Let's just say that we are aware of this issue, and that we are working on a > solution. > Good to hear. I hope development on app_rpt will keep moving forward, I can see it becoming a big player in the repeater controller arena as well as the area of repeater linking. Regards, Jon From hwstar at rodgers.sdcoxmail.com Tue Jun 27 13:55:14 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Tue, 27 Jun 2006 06:55:14 -0700 Subject: [App_rpt] Interface questions In-Reply-To: <20060627034851.GA20217@unicomsystems.com> References: <20060622233150.GB1570@unicomsystems.com> <200606230736.32332.hwstar@rodgers.sdcoxmail.com> <20060627034851.GA20217@unicomsystems.com> Message-ID: <200606270655.14847.hwstar@rodgers.sdcoxmail.com> Jon, See responses below. Some questions for you: Will you be using this in an Amatuer Radio repeater system or a commercial system? Last time I checked, Australia does not permit Amateur repeaters connect to the phone system (via automatic phone patching or autopatching) is this still the case? The reason I ask is that our systems in the US have this capability, and if we are linked together, would it be breaking the rules if someone in the US did this and and we were linked to a system in Australia? In this case, the phone conversation taking place on the US system would be rebroadcast on the Australian system. > Hrm, they certainly have plenty, and at a good price, but overseas UPS >shipping is a killer, about USD$100 to ship a dozen or so to Australia. I'm willing to send you 2 transformers with each board blank ordered for $5.00US extra plus shipping. Please contact me off list for details. > Is it hard to support different FXS devices? I'm not sure exactly how > entwined app_rpt is with driver code. The reason I ask is one possible > avenue for me is some clone TDM cards from http://www.openvox.com.cn > but it looks like their TDM1200P clone uses a different driver. Their > 400P uses the standard digium driver. As long as the FXS device is seen as a Zaptel device in Asterisk, it will work with app_rpt. In our systems, we use ARIB cards with Digium TE110p/T100p T1 cards and a channel bank. It doesn't matter which driver is required as long is it is a Zaptel driver. On Monday 26 June 2006 20:48, jon+apprpt at unicomsystems.com wrote: > Hello Steve, > > On Fri, Jun 23, 2006 at 07:36:32AM -0700, Steve Rodgers wrote: > > Jon, > > > > See responses below. > > > > On Thursday 22 June 2006 16:31, jon+apprpt at unicomsystems.com wrote: > > > Hello all, > > > > > > First off, I must say that app_rpt looks like a very promising project > > > and this style or repeater controller looks like the way of the future. > > > > > > I have a few questions that I couldn't quite come up with an answer for > > > myself with a high degree of certainty, using the existing material > > > online. > > > 1). Does the 4 port radio interface card allow for 4 duplex repeater > > > channels, or 2 duplex repeater channels? > > > > 4 duplex radio channels. > > Excellent, makes it the best value for money for > 2 channels. > > > > 2). The 600 ohm line transformer as used in the analogue radio > > > interface appears to be out of stock on Digikey. Does anyone have > > > alternative stockists or transformer models? Or even spares they'd be > > > willing to sell? > > > > Last time we bought them form excesssolutions.com > > Hrm, they certainly have plenty, and at a good price, but overseas UPS > shipping is a killer, about USD$100 to ship a dozen or so to Australia. > > Does anyone have spare stock they want to sell or are willing to order > on my behalf and resend using USPS? > > > > 3). Is app_rpt compatible with the TDM1200P or similar? > > > > We haven't tested this but the chips used on the TDM1200p are exactly the > > same as the ones used on the TDM400. > > Is it hard to support different FXS devices? I'm not sure exactly how > entwined app_rpt is with driver code. The reason I ask is one possible > avenue for me is some clone TDM cards from http://www.openvox.com.cn > but it looks like their TDM1200P clone uses a different driver. Their > 400P uses the standard digium driver. > > > > I also have a few more developmental/roadmap oriented questions, > > > namely, would it be possible for an interface to be developed that used > > > a full duplex sound card and a serial or other data port to interface > > > to a radio? Or could an interface be developed that had the necessary > > > functions so that it only needed an FXO port on the Asterisk side, > > > seeing FXOs can be got from even basic devices like some winmodems? > > > > Too many sound cards out there to support and having to deal with all of > > them is a burden we don't want to shoulder. > > Fair enough, and looking at the inadequacy and system specificness of > other repeater linking hardware systems around, this is a condition > I'm willing to live with. > > > > Note that I'm not trying to rubbish the project or its developers with > > > these questions, I'm sure the current interfaces work very well, but > > > seeing as we're not interfacing phones, I thought it would've been > > > possible design a way to interface at an even lower price point, > > > opening access further, and further benefiting app_rpt with greater > > > uptake levels from all sorts of radio people around the world. > > > > Let's just say that we are aware of this issue, and that we are working > > on a solution. > > Good to hear. I hope development on app_rpt will keep moving forward, I > can see it becoming a big player in the repeater controller arena as well > as the area of repeater linking. > > > Regards, > > Jon > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt From telesistant at hotmail.com Tue Jun 27 19:15:06 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 27 Jun 2006 12:15:06 -0700 Subject: [App_rpt] Interface questions In-Reply-To: <200606270655.14847.hwstar@rodgers.sdcoxmail.com> Message-ID: Also, whatever the FXS device is, it needs to support Groundstart (for transmit side) (or DPO). >From: Steve Rodgers >Reply-To: Asterisk Repeater Controler >To: Asterisk Repeater Controler >Subject: Re: [App_rpt] Interface questions >Date: Tue, 27 Jun 2006 06:55:14 -0700 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc3-f13.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, >27 Jun 2006 10:04:37 -0700 >Received: (qmail 8805 invoked from network); 27 Jun 2006 13:55:19 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 27 >Jun 2006 13:55:19 -0000 >Received: (qmail 8791 invoked from network); 27 Jun 2006 13:55:16 -0000 >Received: from dukecmmtao03.coxmail.com (68.99.120.70)by 0 with SMTP; 27 >Jun 2006 13:55:16 -0000 >Received: from steverod.sv.qrvc.com ([68.15.19.112])by >dukecmmtao03.coxmail.com(InterMail vM.6.01.05.02 201-2131-123-102-20050715) >with ESMTP >id<20060627135516.BVOU3326.dukecmmtao03.coxmail.com at steverod.sv.qrvc.com>for >; Tue, 27 Jun 2006 09:55:16 -0400 >X-Message-Info: txF49lGdW42KTLyn7xGNYIwZf6O3xZJwBClcbvrfnGQ= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >User-Agent: KMail/1.9.1 >References: ><20060622233150.GB1570 at unicomsystems.com><200606230736.32332.hwstar at rodgers.sdcoxmail.com><20060627034851.GA20217 at unicomsystems.com> >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: 27 Jun 2006 17:04:39.0110 (UTC) >FILETIME=[C66EB660:01C69A0B] > > >Jon, > >See responses below. > >Some questions for you: > >Will you be using this in an Amatuer Radio repeater system or a commercial >system? > >Last time I checked, Australia does not permit Amateur repeaters connect >to >the phone system (via automatic phone patching or autopatching) is this >still >the case? The reason I ask is that our systems in the US have this >capability, and if we are linked together, would it be breaking the rules >if >someone in the US did this and and we were linked to a system in Australia? >In >this case, the phone conversation taking place on the US system would be >rebroadcast on the Australian system. > > > > > Hrm, they certainly have plenty, and at a good price, but overseas UPS > >shipping is a killer, about USD$100 to ship a dozen or so to Australia. > > >I'm willing to send you 2 transformers with each board blank ordered for >$5.00US extra plus shipping. Please contact me off list for details. > > > > Is it hard to support different FXS devices? I'm not sure exactly how > > entwined app_rpt is with driver code. The reason I ask is one possible > > avenue for me is some clone TDM cards from http://www.openvox.com.cn > > but it looks like their TDM1200P clone uses a different driver. Their > > 400P uses the standard digium driver. > >As long as the FXS device is seen as a Zaptel device in Asterisk, it will >work >with app_rpt. In our systems, we use ARIB cards with Digium TE110p/T100p T1 >cards and a channel bank. It doesn't matter which driver is required as >long >is it is a Zaptel driver. > > > > >On Monday 26 June 2006 20:48, jon+apprpt at unicomsystems.com wrote: > > Hello Steve, > > > > On Fri, Jun 23, 2006 at 07:36:32AM -0700, Steve Rodgers wrote: > > > Jon, > > > > > > See responses below. > > > > > > On Thursday 22 June 2006 16:31, jon+apprpt at unicomsystems.com wrote: > > > > Hello all, > > > > > > > > First off, I must say that app_rpt looks like a very promising >project > > > > and this style or repeater controller looks like the way of the >future. > > > > > > > > I have a few questions that I couldn't quite come up with an answer >for > > > > myself with a high degree of certainty, using the existing material > > > > online. > > > > 1). Does the 4 port radio interface card allow for 4 duplex repeater > > > > channels, or 2 duplex repeater channels? > > > > > > 4 duplex radio channels. > > > > Excellent, makes it the best value for money for > 2 channels. > > > > > > 2). The 600 ohm line transformer as used in the analogue radio > > > > interface appears to be out of stock on Digikey. Does anyone have > > > > alternative stockists or transformer models? Or even spares they'd >be > > > > willing to sell? > > > > > > Last time we bought them form excesssolutions.com > > > > Hrm, they certainly have plenty, and at a good price, but overseas UPS > > shipping is a killer, about USD$100 to ship a dozen or so to Australia. > > > > Does anyone have spare stock they want to sell or are willing to order > > on my behalf and resend using USPS? > > > > > > 3). Is app_rpt compatible with the TDM1200P or similar? > > > > > > We haven't tested this but the chips used on the TDM1200p are exactly >the > > > same as the ones used on the TDM400. > > > > Is it hard to support different FXS devices? I'm not sure exactly how > > entwined app_rpt is with driver code. The reason I ask is one possible > > avenue for me is some clone TDM cards from http://www.openvox.com.cn > > but it looks like their TDM1200P clone uses a different driver. Their > > 400P uses the standard digium driver. > > > > > > I also have a few more developmental/roadmap oriented questions, > > > > namely, would it be possible for an interface to be developed that >used > > > > a full duplex sound card and a serial or other data port to >interface > > > > to a radio? Or could an interface be developed that had the >necessary > > > > functions so that it only needed an FXO port on the Asterisk side, > > > > seeing FXOs can be got from even basic devices like some winmodems? > > > > > > Too many sound cards out there to support and having to deal with all >of > > > them is a burden we don't want to shoulder. > > > > Fair enough, and looking at the inadequacy and system specificness of > > other repeater linking hardware systems around, this is a condition > > I'm willing to live with. > > > > > > Note that I'm not trying to rubbish the project or its developers >with > > > > these questions, I'm sure the current interfaces work very well, but > > > > seeing as we're not interfacing phones, I thought it would've been > > > > possible design a way to interface at an even lower price point, > > > > opening access further, and further benefiting app_rpt with greater > > > > uptake levels from all sorts of radio people around the world. > > > > > > Let's just say that we are aware of this issue, and that we are >working > > > on a solution. > > > > Good to hear. I hope development on app_rpt will keep moving forward, I > > can see it becoming a big player in the repeater controller arena as >well > > as the area of repeater linking. > > > > > > Regards, > > > > Jon > > _______________________________________________ > > 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 jon at unicomsystems.com Wed Jun 28 02:13:52 2006 From: jon at unicomsystems.com (Jon Teh) Date: Wed, 28 Jun 2006 12:13:52 +1000 Subject: [App_rpt] Interface questions In-Reply-To: <200606270655.14847.hwstar@rodgers.sdcoxmail.com> References: <20060622233150.GB1570@unicomsystems.com> <200606230736.32332.hwstar@rodgers.sdcoxmail.com> <20060627034851.GA20217@unicomsystems.com> <200606270655.14847.hwstar@rodgers.sdcoxmail.com> Message-ID: <20060628021352.GB20217@unicomsystems.com> On Tue, Jun 27, 2006 at 06:55:14AM -0700, Steve Rodgers wrote: > > Jon, > > See responses below. > > Some questions for you: > > Will you be using this in an Amatuer Radio repeater system or a commercial > system? Current plans are not amateur related, so this shouldn't be a problem. > > Last time I checked, Australia does not permit Amateur repeaters connect to > the phone system (via automatic phone patching or autopatching) is this still > the case? The reason I ask is that our systems in the US have this > capability, and if we are linked together, would it be breaking the rules if > someone in the US did this and and we were linked to a system in Australia? In > this case, the phone conversation taking place on the US system would be > rebroadcast on the Australian system. > I know that the Australian Communications and Media Authority put out a paper specifically stating that Internet linking was permitted and was not considered connecting to the PSTN. If there's phone patches in the US, then I guess that makes it a bit grey. But unless it's a major problem, I doubt ACMA would bother as they generally have higher priority things to police than amateur radio. > > > > Hrm, they certainly have plenty, and at a good price, but overseas UPS > >shipping is a killer, about USD$100 to ship a dozen or so to Australia. > > > I'm willing to send you 2 transformers with each board blank ordered for > $5.00US extra plus shipping. Please contact me off list for details. Sounds like an idea, I'll talk to you off list about it. > > > > Is it hard to support different FXS devices? I'm not sure exactly how > > entwined app_rpt is with driver code. The reason I ask is one possible > > avenue for me is some clone TDM cards from http://www.openvox.com.cn > > but it looks like their TDM1200P clone uses a different driver. Their > > 400P uses the standard digium driver. > > As long as the FXS device is seen as a Zaptel device in Asterisk, it will work > with app_rpt. In our systems, we use ARIB cards with Digium TE110p/T100p T1 > cards and a channel bank. It doesn't matter which driver is required as long > is it is a Zaptel driver. > Ah okay, that clears it up a little. I was planning on saving up for quad radio card, especially for its DCS and CTCSS capabilities. However, I have been offered a T1 card and channel bank for an unrefusable price, so I'm probably going that way. Regards, Jon From f6hqz-m at hamwlan.net Wed Jun 28 18:20:10 2006 From: f6hqz-m at hamwlan.net (f6hqz-m at hamwlan.net) Date: Wed, 28 Jun 2006 20:20:10 +0200 Subject: [App_rpt] RE : Interface questions In-Reply-To: <20060628021352.GB20217@unicomsystems.com> Message-ID: Hello friends, You can also consider the price of a Digium TDM2460B (24 FXS channels) or TDM2460E (same with hardware echocan) or with minus quad FXS modules (scalable from 4 to 24 channels by 4 lines step) against a T1+channel bank. It's how I do here without any issue. Or wait a little for the new Digium TDM which must replace the "old" TDM400P serie. It will accept 4 old one line only modules (for TDM400P) or 2 new "quad" modules (for TDM2400P) + an optional echocan module derivated from the TDM2400P but with minus chips due to the module number reduction. 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 Jon Teh Envoy? : mercredi 28 juin 2006 04:14 ? : Asterisk Repeater Controler Cc : Jon Teh Objet : Re: [App_rpt] Interface questions ...SNIP... > > As long as the FXS device is seen as a Zaptel device in Asterisk, it > will work > with app_rpt. In our systems, we use ARIB cards with Digium TE110p/T100p T1 > cards and a channel bank. It doesn't matter which driver is required as long > is it is a Zaptel driver. > Ah okay, that clears it up a little. I was planning on saving up for quad radio card, especially for its DCS and CTCSS capabilities. However, I have been offered a T1 card and channel bank for an unrefusable price, so I'm probably going that way. Regards, Jon _______________________________________________ App_rpt mailing list App_rpt at lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt From hwstar at rodgers.sdcoxmail.com Wed Jun 28 19:34:33 2006 From: hwstar at rodgers.sdcoxmail.com (hwstar at rodgers.sdcoxmail.com) Date: Wed, 28 Jun 2006 12:34:33 -0700 Subject: [App_rpt] Interface questions Message-ID: <20060628193433.JRPL3326.dukecmmtao03.coxmail.com@dukecmmtao03> Jon, As Jim stated in a prior E-mail, you must make sure the channel bank supports DPO (Groundstart mode) or the transmitter will stay keyed all the time. The transmitter is keyed by the presence of battery on the TX pair. Steve. > > From: jon at unicomsystems.com (Jon Teh) > Date: 2006/06/27 Tue PM 07:13:52 PDT > To: Asterisk Repeater Controler > CC: Jon Teh > Subject: Re: [App_rpt] Interface questions > > On Tue, Jun 27, 2006 at 06:55:14AM -0700, Steve Rodgers wrote: > > > > Jon, > > > > See responses below. > > > > Some questions for you: > > > > Will you be using this in an Amatuer Radio repeater system or a commercial > > system? > > Current plans are not amateur related, so this shouldn't be a problem. > > > > > Last time I checked, Australia does not permit Amateur repeaters connect to > > the phone system (via automatic phone patching or autopatching) is this still > > the case? The reason I ask is that our systems in the US have this > > capability, and if we are linked together, would it be breaking the rules if > > someone in the US did this and and we were linked to a system in Australia? In > > this case, the phone conversation taking place on the US system would be > > rebroadcast on the Australian system. > > > > I know that the Australian Communications and Media Authority put out > a paper specifically stating that Internet linking was permitted and was > not considered connecting to the PSTN. If there's phone patches in the US, > then I guess that makes it a bit grey. But unless it's a major problem, > I doubt ACMA would bother as they generally have higher priority things > to police than amateur radio. > > > > > > > Hrm, they certainly have plenty, and at a good price, but overseas UPS > > >shipping is a killer, about USD$100 to ship a dozen or so to Australia. > > > > > > I'm willing to send you 2 transformers with each board blank ordered for > > $5.00US extra plus shipping. Please contact me off list for details. > > Sounds like an idea, I'll talk to you off list about it. > > > > > > > > Is it hard to support different FXS devices? I'm not sure exactly how > > > entwined app_rpt is with driver code. The reason I ask is one possible > > > avenue for me is some clone TDM cards from http://www.openvox.com.cn > > > but it looks like their TDM1200P clone uses a different driver. Their > > > 400P uses the standard digium driver. > > > > As long as the FXS device is seen as a Zaptel device in Asterisk, it will work > > with app_rpt. In our systems, we use ARIB cards with Digium TE110p/T100p T1 > > cards and a channel bank. It doesn't matter which driver is required as long > > is it is a Zaptel driver. > > > > Ah okay, that clears it up a little. I was planning on saving up for quad > radio card, especially for its DCS and CTCSS capabilities. However, I have > been offered a T1 card and channel bank for an unrefusable price, so I'm > probably going that way. > > > Regards, > > Jon > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > From jon+apprpt at unicomsystems.com Fri Jun 30 03:23:05 2006 From: jon+apprpt at unicomsystems.com (jon+apprpt at unicomsystems.com) Date: Fri, 30 Jun 2006 13:23:05 +1000 Subject: [App_rpt] Interface questions In-Reply-To: <20060628193433.JRPL3326.dukecmmtao03.coxmail.com@dukecmmtao03> References: <20060628193433.JRPL3326.dukecmmtao03.coxmail.com@dukecmmtao03> Message-ID: <20060630032305.GK20217@unicomsystems.com> On Wed, Jun 28, 2006 at 12:34:33PM -0700, hwstar at rodgers.sdcoxmail.com wrote: > Jon, > > As Jim stated in a prior E-mail, you must make sure the channel bank supports DPO (Groundstart mode) or the transmitter will stay keyed all the time. The transmitter is > keyed by the presence of battery on the TX pair. > > Steve. Hello Steve, I'm going with a Wildcard T100P and a Zhone Xplex 10 Channel Bank. Looking at the data sheet for the channel bank, it appears to support groundstart operation. Hopefully I shouldn't have *too* much of a learning curve getting this running, once I've built this machine for it. Regards, Jon