<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Our architecture for Echolink differs a great deal from most others. Since there is no sane<br>reason in the universe to do otherwise, our Echolink presence is both more-or-less a "conference",<br>since it will ALWAYS accept multiple inbound connections and tie them together (as any connection<br>is on an app_rpt node), and have the ability to support multiple outbound connections (also tied together<br>with everything else on the app_rpt node) simultaneously. There is no reason to create "artificial"<br>limitations of this nature.<br><br>Since the Echolink reporting system is really designed for implementation that basically do<br>"one thing at a time", there is only a concept of a single status message. To make a (rather<br>feeble) attempt at "fitting into the mold", I decided to report the "inbound" status when there<br>are no outbound connections active. If outbound connections are active, it reports the information<br>for the last one connected (if multiple outbound connections are active).<br><br>Therefore, by definition, the node can *never* be "busy" according to the Echolink reporting<br>definition of "busy". <br><br>And yes, the "20" means "of 20 maximum connections". However, the connection limit was never<br>implemented (after all, I try to avoid artifical limits on things). If and when there is a compelling reason<br>do to so, I will. Currently, the system will take as many connections as there is bandwidth and CPU power for.<br><br>JIM WB6NIL<br><br><br>> Date: Sat, 22 Jan 2011 14:26:22 -0600<br>> From: kt9ac@ameritech.net<br>> To: app_rpt-users@ohnosec.org<br>> Subject: Re: [App_rpt-users] Echolink Link Status<br>> <br>> Just updated my test system to 0.281 and verified that when idle it <br>> shows a [0/20] next to my QTH. When connected, shows the "In conference <br>> with..." status.<br>> <br>> Does this mean we can host 20 connections from Echolink per Allstar <br>> node? Also, when would the "ON" versus "BUSY" flag change.<br>> <br>> I don't use Echolink a lot, but its interesting...<br>> <br>> Thanks,<br>> Tony<br>> <br>> On 01/21/2011 11:26 PM, K&R Yoksh wrote:<br>> ><br>> > ----- Original Message -----<br>> >> Date: Fri, 21 Jan 2011 18:27:15 -0800<br>> >> From: Jim Duuuude<br>> >> Subject: Re: [App_rpt-users] Echolink Link Status<br>> >><br>> >> Chan_echolink now supports proper display/reporting to the echolink <br>> >> server stuff.<br>> ><br>> > Hello Jim (and the group),<br>> ><br>> > Many thanks for this great addition!<br>> ><br>> > 73.<br>> ><br>> > Kyle<br>> > K0KN<br>> ><br>> > _______________________________________________<br>> > App_rpt-users mailing list<br>> > App_rpt-users@ohnosec.org<br>> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br>> ><br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br> </body>
</html>