What does your echolink.conf file look like??

(please remember to omit your echolink password)

Jim

On Aug 14, 2009, at 2:51 PM, Todd Birkenholtz wrote:

Thanks James.

Unfortunately this is not the case.  I have verified both UDP ports are sent from my router to my internal server 192.168.2.110.
I also have run the windows Echolink and ran the test firewall function and I can verify my ISP does not filter the ports.

The following is a tcpdump of the inbound connection to my Asterisk box on a connect to verify the conversation makes it to my Asterisk box.

[root@test ~]# tcpdump host  204.13.148.174
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
14:37:49.056574 IP 204.13.148.174.5199 > 192.168.2.110.5199: UDP, length 96
14:37:49.056869 IP 204.13.148.174.5198 > 192.168.2.110.5198: UDP, length 36
14:37:49.057182 IP 192.168.2.110.5198 > 204.13.148.174.5198: UDP, length 74
14:37:49.057785 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 76
14:37:49.585296 IP 204.13.148.174.5199 > 192.168.2.110.5199: UDP, length 96
14:37:49.585602 IP 204.13.148.174.5198 > 192.168.2.110.5198: UDP, length 36
14:37:51.637508 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637515 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637521 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637526 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637532 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637537 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637542 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637547 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637552 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637558 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637563 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637568 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637573 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637578 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637583 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637588 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637592 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637597 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637602 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36
14:37:51.637607 IP 192.168.2.110.5199 > 204.13.148.174.5199: UDP, length 36

Thanks again.. I really appreciate the help

Todd


On Fri, Aug 14, 2009 at 3:39 PM, James Nessen <nessenj@jimsoffice.org> wrote:
If your node is behind a firewall, it sounds like you don't have ports 5198 and 5199 udp forwarded into your node.   If your node sits out on a public IP, make sure your upstream ISP doesn't filter on those ports.

Jim / K6JWN


On Aug 14, 2009, at 11:47 AM, Todd Birkenholtz 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@radio-secure:1] Answer("echolink/el0-12", "") in new stack
  -- Executing [2345@radio-secure:2] Playback("echolink/el0-12", "tt-weasels|skip") in new stack
  -- <echolink/el0-12> Playing 'tt-weasels' (language '')
  -- Executing [2345@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@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@qrvc.com
http://qrvc.com/mailman/listinfo/app_rpt-users

_______________________________________________
App_rpt-users mailing list
App_rpt-users@qrvc.com
http://qrvc.com/mailman/listinfo/app_rpt-users