Just in the process of setting up an Asterisk node (AllStar 2199). At this time, the node has no local RF hardware (I am seriously considering adding a Kenwood remote base early next year), but I want to have a link to a remote system using chan_rtpdir, which will link to an established system.
I have some sample configs, and the N9YTY notes, but those notes assume a local RF link.
What I want to do is accept connections to AllStar node 2199 and have those linked to the rtpDir system. And from the other end, I want to be able to connect to other AllStar nodes.
Anyone able to offer insight on this configuration?
My current Asterisk installation is a hand compiled system (app_rpt is included). I didn't use EVB or ACID, because Asterisk is installed on an existing IRLP node, and I didn't want to wipe the system (for obvious reasons!).
I may also look into configuring the system to link to the local IRLP node on demand, once I've got the hang of driving Asterisk.
I played with Asterisk a long time ago and was able to set it up as a reasonable PBX with VoIP and a single analog line, but I'm a bit rusty now and I've never used app_rpt before.
I think the question is what to define for your rxchannel/txchannel on the Allstar link node... In my config, I created a "fake" node number with the chan_rtpdir and then I link that up with my AllStar node that owns the radio.
Have you tried to define the AllStar node definition using chan_rtpdir and not using a separate node number at all? Without trying it, I'm thinking that this may work. You may want to define the parameters much like I had them in that sample config for node 1000 as far as the linktolink, hangtime and other parameters just so that the asterisk node doesn't send anything but pure voice data.
Let me know if I can help, I'll do whatever I can and I'd be willing to do some testing here as well. You had a good point in that other post in that the best audio quality may be obtained by having IRLP own the radio anyway so that no conversion to GSM is done. I know that IRLP allows quite extensive use of scripting from DTMF, and also that asterisk can be controlled from the command line, so it may be interesting to try this approach as well.
Steve
···
On Jul 24, 2008, at 4:45 AM, Tony Langdon, VK3JED wrote:
I have some sample configs, and the N9YTY notes, but those notes
assume a local RF link.
RF Hardware is not required. Instead of using chan_usbradio and setting
rxchannel=Radio/usb, you redirect it to the chan_rtpdir driver. Its
invoked as rtpdir/HISIP:HISPORT[:MYPORT] Example:
[2199]
rxcnannel=rtpdir/127.0.0.1:4000
This specifies the localhost as the IP address, and to use port 4000.
There is a text writeup on these details in the first part of the
chan_rtpdir source file.
Steve R.
WA6ZFT
Tony Langdon, VK3JED wrote:
···
Just in the process of setting up an Asterisk node (AllStar
2199). At this time, the node has no local RF hardware (I am
seriously considering adding a Kenwood remote base early next year),
but I want to have a link to a remote system using chan_rtpdir, which
will link to an established system.
I have some sample configs, and the N9YTY notes, but those notes
assume a local RF link.
What I want to do is accept connections to AllStar node 2199 and have
those linked to the rtpDir system. And from the other end, I want to
be able to connect to other AllStar nodes.
Anyone able to offer insight on this configuration?
My current Asterisk installation is a hand compiled system (app_rpt
is included). I didn't use EVB or ACID, because Asterisk is
installed on an existing IRLP node, and I didn't want to wipe the
system (for obvious reasons!).
I may also look into configuring the system to link to the local IRLP
node on demand, once I've got the hang of driving Asterisk.
I played with Asterisk a long time ago and was able to set it up as a
reasonable PBX with VoIP and a single analog line, but I'm a bit
rusty now and I've never used app_rpt before.
I think the question is what to define for your rxchannel/txchannel
on the Allstar link node... In my config, I created a "fake" node
number with the chan_rtpdir and then I link that up with my AllStar
node that owns the radio.
Have you tried to define the AllStar node definition using
chan_rtpdir and not using a separate node number at all? Without
trying it, I'm thinking that this may work. You may want to define
the parameters much like I had them in that sample config for node
1000 as far as the linktolink, hangtime and other parameters just so
that the asterisk node doesn't send anything but pure voice data.
I was going to do that, except James K6JWN mentioned that there is no traffic on the link, unless I get an incoming call. He suggested I try a dummy node using ztdummy and then using the method you used to bring in the link. Haven't finalised my configs yet, so yet to fire up the node. I may be doing the occasional outbound call once I can establish an Asterisk reflector out there (I don't have the CPU or bandwidth to support conferencing locally), but my remote sites can't run the meetme conference, because they can't load ztdummy (Virtuozzo VPS).
Let me know if I can help, I'll do whatever I can and I'd be willing
to do some testing here as well. You had a good point in that other
post in that the best audio quality may be obtained by having IRLP own
the radio anyway so that no conversion to GSM is done. I know that
IRLP allows quite extensive use of scripting from DTMF, and also that
asterisk can be controlled from the command line, so it may be
interesting to try this approach as well.
Well, I will initially be linking remotely, the local IRLP node is not yet ready for linking to Asterisk, because the IRLP scripts don't integrate well. I would have to upgrade it to my beta code to allow the local node to work. That's getting higher up the todo list.
I will also need to know how to connect to other nodes as well.
RF Hardware is not required. Instead of using chan_usbradio and setting
rxchannel=Radio/usb, you redirect it to the chan_rtpdir driver. Its
invoked as rtpdir/HISIP:HISPORT[:MYPORT] Example:
[2199]
rxcnannel=rtpdir/127.0.0.1:4000
This specifies the localhost as the IP address, and to use port 4000.
