<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>The dial plan method has benefits for RF nodes on the same server, which I'm guessing would be the large majority of implementations.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Once I get the node actually registering with Echolink servers from within the BBB/RPi, the dial plan should be easy to add. The Echolink login/password works just fine from a Windows client. Need more time in front of the asterisk editor. It's pretty low priority.<br><br>tnx<div>Mike Roden / AT&T</div><div>404-277-3494</div></div><div><br>On Mar 24, 2016, at 1:08 PM, Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><font style="" face="Tahoma,sans-serif" color="#000000">Mike,<br><br> One other thing that I am sure you understand but others who read this may not is why do it using the dialplan method. The answer is it allows Echolink to be on a pseudo node and also allow users to enter specific Echolink node numbers. The line -<br><br>/usr/bin/asterisk -rx "rpt fun xxxxx $1$2<br><br>in the script is executed on the server where both the pseudo node and radio node reside. So in the above line the xxxxx is the node number of the pseudo node but the command actually comes from the radio node.<br id="FontBreak"></font><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4"><a href="http://www.crompton.com/hamradio">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt;" size="4"><br></font><br><br> </div>
</div></blockquote></body></html>