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