<div>Mars and Steve,</div>
<div> </div>
<div>Thanks for the response It wasn't what I wanted to hear but it did explain why I couldn't get two-way audio to work correctly through Echolink. I assumed the the Echolink driver used some type of vox to convert it to a by-directional circuit using the magic inside app_rpt.</div>
<div> </div>
<div>N0PCO, you gave me a couple of options to think over and in typical HAM fashion it looks like I am going to need some duct tape and baling twine... I like it !! ;-)</div>
<div> </div>
<div>Do either of you know if the dtpDir soluton will work in the same manner?</div>
<div> </div>
<div> </div>
<div>Thanks again for your detailed response to my issue.</div>
<div> </div>
<div> </div>
<div>73 W0IOU<br>Todd Birkenholtz<br></div>
<div> </div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Sat, Aug 22, 2009 at 3:36 PM, <a href="mailto:app_rpt@alertradio.net" target="_blank">app_rpt@alertradio.net</a> <span dir="ltr"><<a href="mailto:app_rpt@alertradio.net" target="_blank">app_rpt@alertradio.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">Todd, are you using one computer for both Asterisk and EchoLink?<br><br>If you are using two computers, I have a easy way to make things work (or at least some what easy).<br><br>The key you will need to have a USB Audio Adapter on the Asterisk server. The USB Audio Adapter doesn't need to be modified to do what you are wanting, it just needs to be present for the audio from the Asterisk server in such a way that the ACID installations nows that there's an actual audio source available. Depending on how you have EchoLink attached to the repeater, you will need to build a lashup circuit that will bring the audio from the Asterisk server to the EchoLink host. <br>
<br><br>==========================<br><br>So your primary objective is to use Asterisk PBX without the RF Gateway, a better solution to the Asterisk ACID package would be to get one of the PBX software packages such as Elastix or PBX in a Flash. Then on the EchoLink host, add a second sound card or a USB Audio Adapter; this second sound card will be used with a program called X-Lite. X-Lite is a softphone that can be controlled by scripts and easily managed via the EchoLink API./Script (assuming that EchoLink is running on a Windows box). Once again you will need the lashup circuit to bring the audio to/from EchoLink to the softphone<br>
<br>===========================<br><br>It really all comes down to how you presently have EchoLink setup. If you are using VOX control, the task will be easy in regards to pushing audio via X-Lite. Otherwise you will need a circuit for the COS detection. If that's the case might as well just go for the full Asterisk PBX / RF Gateway configuration and modify a USB Audio Adapter (with the CM108 chip in it) or get one of the USB Radio Interfaces. You don't have to have the Asterisk Allstar Link Node to make it work, but you will need a private node number on the Asterisk side primarily for routing purposes. Plug in your EchoLink information and create some routing information for telephone calls and things will operate quite nicely. <br>
<br>For security purposes having the RF Gateway and PBX in separate computers can be beneficial. And as Steve has mentioned the pre-announcement before making a call can be a bit tricky to accomplish. The way things are set up here, for PSTN calls one has to enter the Patch Code-Telephone Number and then the server asks for a PIN number. Calls that are routed internally do not need a PIN number to complete the call. On Elastix you can set it up where each person has their own PIN number as well a voice-mailbox. <br>
<br><br>The way things are set up here presently, I have three different computers managing the PBX and RF Gateways. Usually they are all stand-alone but can quickly be brought together when needed. There's some advantages to this especially in regards to redundancy. I'll always have at least one way to connect without total reliance on a single box. (If one has a backup machine pre-configured this wouldn't be a problem at all)<br>
<br><br>Mars, N0PCO<br><a href="http://asteriskradio.net/" target="_blank">http://asteriskradio.net</a><br><a href="http://alertradio.net/" target="_blank">http://alertradio.net</a><br><br><br><br><br><br><br><br><br><br>
<br><br><br>=======================================================================
<div>
<div></div>
<div><br><br>Stephen Rodgers wrote:
<blockquote type="cite"><pre>Todd Birkenholtz wrote:
</pre>
<blockquote type="cite"><pre>I have been working on this for weeks and am getting nowhere.
This is what I would like to accomplish.
I have no need at this point to link two repeaters together via IRLP or via
an IAX Allstarlink my goal is to allow our club's repeater with an Echolink
node connect to Asterisk via Echolink.
Since I will be acting as a pure voip gateway I will not be using the usb
driver or connect directly to an radio.
After our club repeater connects to my Echolink node I would like to greet
the station with a welcome message and request a DTMF password. After they
provide the password I would like to provide a dial tone to be used as a
autopatch.
On the flip side I would like to provide a dial-in phone number on my
Asterisk system that would connect my Echolink node with our clubs repeater
node after the dial-in user provides a password.
I am quite conffient I can do the Asterisk dial-plans I just need some
assistance with the rpt integration.
I was wondering if someone would share their config files to help me get
started in the right direction.
Thanks and 73
Todd Birkenholtz W0IOU
------------------------------------------------------------------------
_______________________________________________
App_rpt-users mailing list
<a href="mailto:App_rpt-users@qrvc.com" target="_blank">App_rpt-users@qrvc.com</a>
<a href="http://qrvc.com/mailman/listinfo/app_rpt-users" target="_blank">http://qrvc.com/mailman/listinfo/app_rpt-users</a>
</pre></blockquote><pre>What you are asking for would require code changes to app_rpt
and use of an IAX/allstar and not an Echolink connection.
VOIP connections are radio connections are treated differently in
app_rpt and echolink connections and they cannot be manipulated using
extension logic. All incoming echolink connections go directly to the
echolink channel driver.
The app_rpt code does not support greeting incoming connections
(echolink, irlp, or allstar) with a password on standard nodes.
Echolink connections are inherently half duplex, and useless for
carrying an autopatch call. The radio connection would have to be
IAX2/allstar to support a remote autopatch, and if this is the case,
then you'd have to have asterisk installed at the repeater and replace
the echolink software. (Probably what you are trying to avoid).
Steve
WA6ZFT
_______________________________________________
App_rpt-users mailing list
<a href="mailto:App_rpt-users@qrvc.com" target="_blank">App_rpt-users@qrvc.com</a>
<a href="http://qrvc.com/mailman/listinfo/app_rpt-users" target="_blank">http://qrvc.com/mailman/listinfo/app_rpt-users</a>
</pre></blockquote><br></div></div></div></blockquote></div><br>