Adding channel drivers to ASL3

Third-Party Apps
1

Hi Guys:

How can I add channel drivers to an existing ASL3 install (both on a Pi, as well as an install on a Debian server)?

Seems like the install just provides compiled binaries of the most popular channel drivers. I am interested in dropping in an additional channel driver (chan_rptdir.c), and then (re) compiling asterisk.

Thanks in advance,

Ramesh, VA3UV, WA3UV, G4PNQ

2

The build should be enabling all channel drivers in Asterisk that don't have oddball dependencies that are difficult to deal with broadly. I've never heard of chan_rptdir.c. Can you point us to it?

3

Hello…

Here is some dated info / downloads:

I have a much later version than this. Essentially rtpDir allows you to create a bridge to other VoIP networks and protocols, e.g., D-STAR.

I’d like to add this driver in, and then re-compile Asterisk.

Thanks,

Ramesh, VA3UV, WA3UV, G4PNQ

4

This code is over 20 years old. It's talking about pre-ASL Zapatel and RedHat 9. It's highly doubtful this is compatible with modern Asterisk. Did you look at DVSwitch if you're trying to bridge to digital modes?

5

What’s the advantage, especially for D-STAR, of using this rather than DVSwitch over USRP plus a DV3000 vocoder dongle and ircddbgatewayd? The only software implementation of that vocoder I know of sounds absolutely awful, and is only good for testing purposes.

I’ve seen a lot of bridges over the years, and have never heard of anyone using this combination. However, especially if you don’t use analog radios, you can achieve pretty much the same native sound with DVSwitch Server and Allstarlink.

6

@N8EI - yes, I have looked at DVSwitch - got it working here on a Pi. Audio from BM to FM (and vice-versa) sound crummy (to my ears, anyway). D-STAR to FM (and vice-versa) isn’t too bad. The problem with DVSwitch is that the D-STAR interface is designed to connect to ircddbgateway, and mimics a repeater module (e.g., port 20011, etc…)

rtpDir allowed you to interface with a dplus client and connect directly to an external reflector (e.g., an XLX reflector) acting as a broker for all analog traffic. The client also allowed you to send a short text message - e.g, “ANALOG BRIDGE” so everyone knew that the traffic was via the bridge, etc. DVSwitch does not appear to have this capability.

Now having said that, I have not tried to install ircddbgteway on the local Pi running DVSwitch.

@N2DYI - Regarding the vocoder - I connected the BM side to a static TG (302050), where I already have a bridge (using an AMBE server) to bridge BM to D-STAR, and that bridge uses a DVStick 33 hardware transcoder.

OK on rtpDir potentially not working with the newer version of Allstar, it was worth a shot. Let me try installing a local instance of ircddbgateway and see if I can get that working using a local transcoder.

Cheers,

Ramesh, VA3UV, WA3UV, G4PNQ

7

Regarding your original question about building from source… see here: