[App_rpt-users] rptbridge

[Jeffrey S. Carrier]

I did see that.  I actually tried something like this:  

 

[general]

 

instance1 = Radio/1970,Radio/1971,Radio/1975

 

To no avail, it caused asterisk to crash.

 

 

 

________________________________

From: Tim Sawyer [mailto:tisawyer at gmail.com] On Behalf Of Tim Sawyer
Sent: Thursday, October 04, 2012 1:34 PM
To: Jeffrey S. Carrier
Cc: app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] rptbridge

 

Never used it myself but this comment from the source might be helpful:

 

/* This application is intended to provide a generic "bridging"

   functionality for radio-oriented Asterisk channels.

 

   The idea here is that certain radio applications lend themselves

   to needing a "generic" (passes audio and tx/rx keying completely

   transparently) to and from two or more endpoints.

 

   An example of such an appication might be replacing (or providing

   equivlent new functionaliy of) one or more full-duplex UHF control

   links with an IP-based one(s).

 

   app_radbridge allows multiple instances of radio-oriented channels

   transparently "bridged" together.

 

   The config file (radbridge.conf) allows specification of each

   "bridging" instance and what radio-oriented Asterisk channels

   are to be associated with it. There is no need for any other

   specificaiton of configuration.

 

   The file format for radbridge.conf departs somewhat from the standard

   usage (at least for radio stuff) of the Asterisk config file architecture.

 

   In most other radio-oriented cases, an instance of whatever it is

   gets defined as a "Stanza" in the config file. In this case, because

   of limitations in the way that Asterisk parses config files, that 

   was not possible. Instead, all config information goes into the

   [general] stanza, and each line of config info defines a different

   instance of radio bridging.  For example:

 

[general]

 

instance1 = Voter/1234,Radio/5678

instance2 = Voter/1235,Radio/5679

 

    This example would define two radio bridging instances "instance1"

    and "instance2", each with 2 channels associated with them.

 

    The supported channel types are "Voter" (chan_voter), "Radio"

    (chan_usbradio), "SimpleUsb" (chan_simpleusb), and "Zap" ("Dahdi")

    (chan_dahdi, for the couple of devices that use this channel

    driver, such as the PCIRadio card, and separate analog channels

    using an ARIB board or such).

 

    Rather then "adding" (which would actually be a lot of *removing*

    optionally) this functionality in app_rpt, it made more sense to

    create a separate application specifically for this purpose. In

    addition, this allows for a system that is merely provided for

    doing this bridging application and nothing else radio-oriented,

    to not have to run app_rpt at all. 

*/

 

--
Tim
:wq

 

On Oct 4, 2012, at 9:10 AM, Jeffrey S. Carrier <jeff.carrier at rmsmsecurity.com> wrote:

 

I actually meant "radbridge" sorry for the typos

________________________________

From: app_rpt-users-bounces at ohnosec.org <mailto:app_rpt-users-bounces at ohnosec.org>  [mailto:app_rpt-users-bounces at ohnosec.org <mailto:users-bounces at ohnosec.org> ] On Behalf Of Jeffrey S. Carrier
Sent: Thursday, October 04, 2012 10:04 AM
To: app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org> 
Subject: [App_rpt-users] rptbridge

 

I'm probably missing something but I can seem to find the answer anywhere so I thought I'd turn to the experts.  Can rptbridge be used to bridge say 3 different nodes on 3 different servers which are all on the same LAN?  I have them set up to do a permanent connection and didn't know if this might be a better way.

 

 

Thanks,

 

Jeff KØJSC

 

 

 

_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org> 
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20121004/bac1f6aa/attachment.html>