Konrad Roeder -- WA4OSH
toggle quoted messageShow quoted text
Steve wrote --- Ah, not sure what you mean that they have not been able to talk to each other.
I don't see very many "reflectors" or conference bridges advertised to bridge for example D-Star with analog repeaters. Maybe I'm not that observant.
On Thu, Aug 3, 2017 at 3:03 AM, Steve N4IRS <szingman@...>
On 08/03/2017 05:24 AM, Konrad Roeder
-- WA4OSH wrote:
I waited a bit before responding to you. First of all, I don't want to brag or
come off brash. Just to let you know, I worked on the first full-duplex
Land-Mobile trunking radios in the very early 1990's and have
a very good understanding of Voice over IP. I have been
working all my life in the interface between radio
transceivers and various forms of voice and data
applications. I understand RPi, Linux, RF, etc. I'm involved
with military communications currently in my professional
Yes, I of course I understand that AllStarLink (ASL) was *primarily
intended* to connect directly to a radio through Asterisk, an
open source VoIP PBX. The
real beauty here is the *full duplex* Asterisk VoIP core and
being able to interface to radios through a USB-based
interface, the URI. Other boards have been built to provide
simulcast interfaces for linking repeaters. But things
sometimes are such a great idea that they can grow beyond what
they were initially intended to be.
Yes, ASL supports simulcast and receiver voting.
I also understand that you
intend on building a channel driver so that the Asterisk VoIP
PBX can talk to a massively superior interface directly from
the Raspberry Pi's GPIO bus instead of being constrained by a
USB interface. I can see how it will give you direct control
over the COR, the PTT and the CTCSS encode/decode. Please note
that I have bought a UDRC-II and have used it in a number of
experiments and see the huge potential for the Asterisk
channel driver. I think it deserves a complementary name to
Asterisk ... Obelisk. I'm patiently waiting.
Not sure what you are renaming. it will simply be chan_udrc
Besides the app_rpt, the
AllStarLink applications and hopefully the UDRC-II interface,
there are many other modules that can be used to interface
Asterisk, including an ALSA interface and the SIP interface.
Yes, I understand the primary
reason for the ALSA interface. I have explored it in the last
six months, looking at all sorts of ways of interfacing sound
boards, audio filters, FFT's, etc. etc. A lot of these
require a GUI interface in order to make use of them. This
was my primary interest in bringing up a GUI.
I'm also very interested in the
SIP interface, which essentially means that you can have a
Cisco 79xx phone reflashed for SIP, or something like a
Grandstream 701 phone adapter to a POTS phone connected to a
vast ham radio / VoIP network. The possibilities are really
We have been connecting sip phones to ASL for years. ASL also
supports IOS and Android apps.
I want you to know that I fully
understand the potential of a UDRC-II board interfaced with
Asterisk can mean. For example, An Asterisk VOIP PBX can host
Analog, D-Star, DMR, Fusion, Single Sideband, etc. users all
on one conference bridge or "reflector". Asterisk also serves
voicemail and phone trees (IVR) and connections to services
that we have not invented yet. Think of it as the central
Rosetta stone that can join these dissimilar networks
together. The UDRC-II is far superior to the USB-based boards
out there today due to its onboard DSP and the DAC/ADCs. It's
a great interface for digital radios, but it has not been put
to the task of interfacing to a VoIP PBX yet. I get it.
This has applications far beyond ham radio, especially when
serving Part 90 and 95 communities. They've never been able
to talk with each other before.
Ah, not sure what you mean that they have not been able to talk to
My two cents ...
I await the totally awesome applications.
73, Steve N4IRS