<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'>
For those who might be interested:<br><br>I just added a new application to our distribution that allows for devices, such as a Voter/RTCM board<br>(and other hardware) to provide "transparent" transport of audio/keying.<br><br>Please the the comment section (from the source file):<br><br><br>/* This application is intended to provide a generic "bridging"<br> functionality for radio-oriented Asterisk channels.<br><br> The idea here is that certain radio applications lend themselves<br> to needing a "generic" (passes audio and tx/rx keying completely<br> transparently) to and from two or more endpoints.<br><br> An example of such an appication might be replacing (or providing<br> equivlent new functionaliy of) one or more full-duplex UHF control<br> links with an IP-based one(s).<br><br> app_radbridge allows multiple instances of radio-oriented channels<br> transparently "bridged" together.<br><br> The config file (radbridge.conf) allows specification of each<br> "bridging" instance and what radio-oriented Asterisk channels<br> are to be associated with it. There is no need for any other<br> specificaiton of configuration.<br><br> The file format for radbridge.conf departs somewhat from the standard<br> usage (at least for radio stuff) of the Asterisk config file architecture.<br><br> In most other radio-oriented cases, an instance of whatever it is<br> gets defined as a "Stanza" in the config file. In this case, because<br> of limitations in the way that Asterisk parses config files, that<br> was not possible. Instead, all config information goes into the<br> [general] stanza, and each line of config info defines a different<br> instance of radio bridging. For example:<br><br>[general]<br><br>instance1 = Voter/1234,Radio/5678<br>instance2 = Voter/1235,Radio/5679<br><br> This example would define two radio bridging instances "instance1"<br> and "instance2", each with 2 channels associated with them.<br><br> The supported channel types are "Voter" (chan_voter), "Radio"<br> (chan_usbradio), "SimpleUsb" (chan_simpleusb), and "Zap" ("Dahdi")<br> (chan_dahdi, for the couple of devices that use this channel<br> driver, such as the PCIRadio card, and separate analog channels<br> using an ARIB board or such).<br><br> Rather then "adding" (which would actually be a lot of *removing*<br> optionally) this functionality in app_rpt, it made more sense to<br> create a separate application specifically for this purpose. In<br> addition, this allows for a system that is merely provided for<br> doing this bridging application and nothing else radio-oriented,<br> to not have to run app_rpt at all.<br><br>*/<br><br>Jmi , WB6NIL<br><br><br> </div></body>
</html>