[App_rpt-users] Asterisk and Echolink no direct connected radio
Todd Birkenholtz
birkey at gmail.com
Mon Aug 17 20:44:12 UTC 2009
Still issues with Echolink Audio.
As a recap...
I have verified my firewall is not blocking ports.
I am able to register a node in Echolink with APP_RPT
I set Set rxchannel = Zap/pseudo in place chan_usb because I am not using a
hardware connection.
As a simple test I created a Extension that when I connect to Echolink from
a remote node I want Asterisk to answer the call and playback a sound then
close the connection.
[radio-secure]
exten => 2345,1,Answer
exten => 2345,n,Playback(tt-weasels,skip)
exten => 2345,n,Hangup
My asterisk log indicates it is playing back the sound file does not make it
to the calling Echolink station.
*CLI> [Aug 14 11:45:36] NOTICE[16779]: chan_echolink.c:2189 do_new_call:
new CALL=W0IOU,ip=204.13.148.184,name= Todd
-- Executing [2345 at radio-secure:1] Answer("echolink/el0-12", "") in new
stack
-- Executing [2345 at radio-secure:2] Playback("echolink/el0-12",
"tt-weasels|skip") in new stack
-- <echolink/el0-12> Playing 'tt-weasels' (language '')
-- Executing [2345 at radio-secure:3] Hangup("echolink/el0-12", "") in new
stack
== Spawn extension (radio-secure, 2345, 3) exited non-zero on
'echolink/el0-12'
Any Idea's before give up.
Thanks Todd
On Sat, Aug 15, 2009 at 9:33 AM, Todd Birkenholtz <birkey at gmail.com> wrote:
> Group
>
> Thanks for the help thus far.
>
> In this simple example All I want to do is be able to connect to my
> Echolink node and have my Asterisk server playback audio.
> A connection is made but audio is not played back through Echolink but my
> Asterisk logs indicate it is.
>
>
> Todd Birkenholtz W0IOU
>
> On Fri, Aug 14, 2009 at 7:27 PM, James Nessen <nessenj at jimsoffice.org>wrote:
>
>> my untrained asterisk eye leads me to believe that your issue lies here:
>>
>> [radio-secure]
>> exten => 2345,1,Answer
>> exten => 2345,n,Playback(tt-weasels,skip)
>> exten => 2345,n,Hangup
>>
>> This tells me to answer, playback a sound and then hang up the connection,
>> and your log confirms this:
>>
>> *CLI> [Aug 14 11:45:36] NOTICE[16779]: chan_echolink.c:2189 do_new_call:
>> new CALL=W0IOU,ip=204.13.148.184,name= Todd
>> -- Executing [2345 at radio-secure:1] Answer("echolink/el0-12", "") in
>> new stack
>> -- Executing [2345 at radio-secure:2] Playback("echolink/el0-12",
>> "tt-weasels|skip") in new stack
>> -- <echolink/el0-12> Playing 'tt-weasels' (language '')
>> -- Executing [2345 at radio-secure:3] Hangup("echolink/el0-12", "") in
>> new stack
>> == Spawn extension (radio-secure, 2345, 3) exited non-zero on
>> 'echolink/el0-12'
>>
>> I am running things the old way, but the ACID manual should cover you here
>> as well:
>>
>> [el0]
>> confmode=no
>> call=WU7Q-R
>> pwd=password
>> name=WU7Q-Repeater
>> qth=Sacramento-CA
>> email=email-addr
>> maxstns=20
>> rtcptimeout=10
>> node=3590
>> recfile=/tmp/recorded.gsm
>> astnode=2194
>> context=echolink-in
>> server1=server1.echolink.org
>> server2=server2.echolink.org
>> server3=server3.echolink.org
>>
>> extensions.conf
>>
>> [echolink-in]
>>
>> ;exten => ${ECHOLINK}/3001083,1,hangup
>> ;exten => ${ECHOLINK}/3021507,1,hangup
>> ;exten => ${ECHOLINK}/3111234,1,hangup
>> ;exten => ${ECHOLINK}/3208345,1,hangup
>> exten => ${ECHOLINK}/3066432,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3009875,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3083598,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3127901,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3009865,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3214691,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3302333,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/3005539,1,Rpt,${NODE}
>> exten => ${ECHOLINK}/_3XXXXXX,1,hangup
>>
>> This was the old way to do access control on echolink nodes, this
>> particular setup only allows connections from known users and then
>> disconnects everyone else. Again, not the preferred method (see the ACID
>> manual), but it works for us.
>>
>> Jim, K6JWN
>>
>> On Fri, Aug 14, 2009 at 11:47 AM, Todd Birkenholtz <birkey at gmail.com>wrote:
>>
>>> Thanks Jim I will change my rpt.conf to rxchannel = Zap/pseudo
>>>
>>> Any Idea on why no audio in my inbound Echolink connections?
>>>
>>> My echolink inbound connection looks like this.
>>>
>>> In extensions.conf
>>>
>>> [radio-secure]
>>> exten => 2345,1,Answer
>>> exten => 2345,n,Playback(tt-weasels,skip)
>>> exten => 2345,n,Hangup
>>>
>>> *CLI> [Aug 14 11:45:36] NOTICE[16779]: chan_echolink.c:2189 do_new_call:
>>> new CALL=W0IOU,ip=204.13.148.184,name= Todd
>>> -- Executing [2345 at radio-secure:1] Answer("echolink/el0-12", "") in
>>> new stack
>>> -- Executing [2345 at radio-secure:2] Playback("echolink/el0-12",
>>> "tt-weasels|skip") in new stack
>>> -- <echolink/el0-12> Playing 'tt-weasels' (language '')
>>> -- Executing [2345 at radio-secure:3] Hangup("echolink/el0-12", "") in
>>> new stack
>>> == Spawn extension (radio-secure, 2345, 3) exited non-zero on
>>> 'echolink/el0-12'
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> On Fri, Aug 14, 2009 at 12:58 PM, Steve Zingman <szingman at msgstor.com>wrote:
>>>
>>>> Todd Birkenholtz wrote:
>>>> > Fellow Hams and PBX tinkerer's
>>>> >
>>>> > I want to provide a auto-patch and a repeater dial-in for our club
>>>> > repeater using my existing home Asterisk PBX in a Flash setup.
>>>> > Our club repeater is connected to Echolink so I was thinking about
>>>> > creating a Echolink node on my server that users could link to then I
>>>> > would allow an outbound call.
>>>> > On the reverse I would like to provide a repeater dial-in number that
>>>> > would route through my Asterisk server to our club's node via
>>>> > Echolink. Keeping in mind at no time does my Asterisk server actually
>>>> > communicates with a radio directly it is just acting as a Echolink
>>>> > gateway.
>>>> >
>>>> > I have been experimenting with ACID but it appears the radio/usb
>>>> > driver is preventing Asterisk from loading without a actual usb radio
>>>> > connected. If I noload=chan_usbradio in the modules.conf file then
>>>> > Asterisk appears to load but I am still having problems with refrence
>>>> > to it in my rpt.config file.
>>>> >
>>>> > I have been able to configure a Echolink connection but I
>>>> > cant send audio to the connected node when the remote station connects
>>>> > but the Asterisk debug indicates it is.
>>>> > Does anybody have a working Echolink node that they would like to
>>>> > share their iax,echolink,rpt and extensions config file with me.
>>>> >
>>>> >
>>>> Todd,
>>>> Set rxchannel = Zap/pseudo in place chan_usb in rpt.conf You will not
>>>> need the hardware.
>>>>
>>>>
>>>> 73, Steve N4IRS
>>>> _______________________________________________
>>>> App_rpt-users mailing list
>>>> App_rpt-users at qrvc.com
>>>> http://qrvc.com/mailman/listinfo/app_rpt-users
>>>>
>>>
>>>
>>> _______________________________________________
>>> App_rpt-users mailing list
>>> App_rpt-users at qrvc.com
>>> http://qrvc.com/mailman/listinfo/app_rpt-users
>>>
>>>
>>
>>
>> --
>> Jim Nessen K6JWN
>> Email: nessenj at jimsoffice.org | Ph: 530.564.0039
>> IRLP: Node 3598 | Echolink: 83598 K6JWN-R | AllStar: Node 2165
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20090817/e97c3403/attachment.html>
More information about the App_rpt-users
mailing list