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
Jon, See responses below. On Thursday 22 June 2006 16:31, jon+apprpt@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@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
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@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
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@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@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@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
Also, whatever the FXS device is, it needs to support Groundstart (for transmit side) (or DPO).
From: Steve Rodgers <hwstar@rodgers.sdcoxmail.com> Reply-To: Asterisk Repeater Controler <app_rpt@lists.illiana.net> To: Asterisk Repeater Controler <app_rpt@lists.illiana.net> 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@steverod.sv.qrvc.com>for <app_rpt@lists.illiana.net>; Tue, 27 Jun 2006 09:55:16 -0400 X-Message-Info: txF49lGdW42KTLyn7xGNYIwZf6O3xZJwBClcbvrfnGQ= Return-Path: <hwstar@rodgers.sdcoxmail.com> Delivered-To: mailman-app_rpt@lists.illiana.net User-Agent: KMail/1.9.1 References: <20060622233150.GB1570@unicomsystems.com><200606230736.32332.hwstar@rodgers.sdcoxmail.com><20060627034851.GA20217@unicomsystems.com> X-BeenThere: app_rpt@lists.illiana.net X-Mailman-Version: 2.1.6 Precedence: list List-Id: Asterisk Repeater Controler <app_rpt.lists.illiana.net> List-Unsubscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-request@lists.illiana.net?subject=unsubscribe> List-Archive: <http://lists.illiana.net/pipermail/app_rpt> List-Post: <mailto:app_rpt@lists.illiana.net> List-Help: <mailto:app_rpt-request@lists.illiana.net?subject=help> List-Subscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-request@lists.illiana.net?subject=subscribe> Errors-To: app_rpt-bounces@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@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@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@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
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
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@lists.illiana.net [mailto:app_rpt-bounces@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@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
participants (5)
-
f6hqz-m＠hamwlan.net -
Jim Duuuude -
jon+apprpt＠unicomsystems.com -
jon＠unicomsystems.com -
Steve Rodgers