From: "Yokshs" <yokshs@sbcglobal.net>
Date: 2009/12/08 Tue AM 09:04:21 PST
To: <app_rpt-users@qrvc.com>
Subject: Re: [App_rpt-users] usbradio similar driver with non usb
> I made the changes to usbradio that you suggest about a year or so ago, and it worked ok. However I was just getting started with app-rpt, and
> there were some other little issues I was having. I decided to mod the cm108 device and see how that compared. Unless you're using the
> recommended hardware/software, it's really hard for anyone to help.
I'm also interested in such a driver. I'd really like to continue using my IRLP board, but I can't seem to make app-rpt work with it directly.
73,
Kyle
K0KN
As Jim Dixon stated previously, this is a can of worms about to be opened. If someone wants to offer support other than us, that is OK, but this project does not have the developer resources to support every conceivable sound card which is what this would entail. There was a real good reason to limit support to 1 or 2 radio interfaces! The radio interface hardware could then be controlled as a known quantity. This has been our philosophy since the project began.
Supporing the IRLP board is not a simple prospect. The IRLP board is not the only peice of the puzzle. The IRLP board depends on a sound card, and this sound card can be anything.
Although sound cards and IRLP interfaces are what folks have, and these folks don't want to invest in a whole new radio interface due to the added costs, the developers feel that this is too much of a burden on them and therefore have no inclination to open up support for every sound card out there.
As there is already software which supports sound cards and IRLP boards (and a bunch of Echolink interfaces), such as thelinkbox, perhaps improving the integration batween Asterisk and this sort of software would be worth doing. I'd certainly like to be able to integrate Asterisk smoothly with my linkbox based systems. The chan_rtpdir driver went a long way to doing this, but it had a few limitations, like being stuck with the GSM codec.
I'm sure if a better interface was developed, Skip would be happy to support it in thelinkbox and thebridge. I know chan_echolink or chan_irlp could be used to make an audio link, but on some configurations, that requires some careful scripting to treat the internal link to Asterisk separately from any conventional IRLP or Echolink connections.
At 04:56 AM 12/9/2009, hwstar@rodgers.sdcoxmail.com wrote:
Although sound cards and IRLP interfaces are what folks have, and these folks don't want to invest in a whole new radio interface due to the added costs, the developers feel that this is too much of a burden on them and therefore have no inclination to open up support for every sound card out there.
At 04:56 AM 12/9/2009, hwstar@rodgers.sdcoxmail.com wrote:
Although sound cards and IRLP interfaces are what folks have, and these folks don't want to invest in a whole new radio interface due to the added costs, the developers feel that this is too much of a burden on them and therefore have no inclination to open up support for every sound card out there.
As there is already software which supports sound cards and IRLP boards (and a bunch of Echolink interfaces), such as thelinkbox, perhaps improving the integration batween Asterisk and this sort of software would be worth doing. I'd certainly like to be able to integrate Asterisk smoothly with my linkbox based systems. The chan_rtpdir driver went a long way to doing this, but it had a few limitations, like being stuck with the GSM codec.
<-- Hi Tony! - chan_rtpdir supports ulaw; I believe it was updated many moons ago.
But is it configurable. I use the principle of tinkering least with the audio. Also, if tbd is the endpoint, the codec must match what tbd is using, since tbd can't transcode (only tlb can).