Thank you Tim!

As soon as I get a day off I’ll try it.

From: Tim Sawyer [mailto:tim.sawyer@mac.com]
Sent: Thursday, October 04, 2012 10:32 PM
To: Jeffrey S. Carrier
Cc: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] rptbridge

I have some new info on this. First, radbridge is not better than a permanent connection of your nodes. Radbridge is intended for systems that don't use app_rpt, systems that are not allstar nodes. So you probably can't use it as it will likely conflict with app_rpt. Secondly, radbridge has never been used anywhere except between a couple of test systems. You're really on the bleeding edge. Having said that, here's how it is set up.

In usbradio.conf (or simpleusb.conf as appropriate) add a stanza. The stanza can be a string of letters or numbers or both, [foo99] or [foobar] for example. Nothing needs to be under the stanza. Configuration of three radios might look like this:

On system #1

usbradio.conf

[foo1]

On system #2

usbradio.conf

[foo2]

On System #3

usbradio.conf

[foo3]

radbridge.conf

[general]

instance1 = Radio/foo1, Radio/foo2, Radio/foo3

--
Tim
:wq

On Oct 4, 2012, at 3:26 PM, Tim Sawyer <tim.sawyer@mac.com> wrote:

Ok, then I'm out of ideas. Hopefully someone else will jump in here to help out.

--
Tim
:wq

On Oct 4, 2012, at 2:49 PM, Jeffrey S. Carrier <jeff.carrier@rmsmsecurity.com> wrote:

Yes, yes and yes

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

Are you using chan_usbradio?

Are those private nodes able to connect to each other with regular connects, ie *31970?

Do you have current source?

--
Tim
:wq

On Oct 4, 2012, at 12:36 PM, Jeffrey S. Carrier <jeff.carrier@rmsmsecurity.com> wrote:

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@gmail.com] On Behalf Of Tim Sawyer
Sent: Thursday, October 04, 2012 1:34 PM
To: Jeffrey S. Carrier
Cc: app_rpt-users@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@rmsmsecurity.com> wrote:

I actually meant “radbridge” sorry for the typos

From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jeffrey S. Carrier
Sent: Thursday, October 04, 2012 10:04 AM
To: app_rpt-users@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@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users