<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
The chan_voter channel driver that goes along with app_rpt has a couple of new<br>features (current in SVN).<br><br>The 'voter test' CLI command now takes an instance id and no longer supports<br>modes < 0 (force vote for testing purposes). It still supports the 'torture' tests<br>that have always existed.<br><br>A config file parameter (on a client-by-client basis, in the client string specification)<br>called 'prio=XXX' has been added. This allow specification of a default 'prio level'<br>for the specified client.<br><br>There is a new 'voter prio' CLI command. This specifies (or allows query of)<br>a value to override the config-file specified 'priority level' for the specified<br>voter client. <br><br>An effective priority level is calculated for each client, based upon the level specified<br>in the config file, and the override level if specified from a CLI command.<br><br>For a 'voting' (GPS-timing based) client, this allows 'groups' of clients with higher<br>priority levels to be 'favored' over 'groups' of clients with lower priority levels<br>when making the 'voting' decision. <br><br>For a 'non-voting' (non-GPS-timing based) client, it provides a means whereby<br>if a signal is received from a 'non-voting' client with a priority > 1, the one with<br>the highest priority 'takes over' the channel's audio (does not include the voted<br>audio or other 'non-voting' clients not at this priority level). This could potentially<br>be useful for implementing some sort of control station hierarchy or something of<br>that nature.<br><br>For either type of client, setting its priority to -1 make it ineligible for consideration<br>(locks its out entirely).<br><br>JIM WB6NIL<br><br><br><br> </div></body>
</html>