[arm-allstar] Taking my node on the road.
Doug Crompton
doug at crompton.com
Fri Aug 14 19:46:47 EST 2015
That is a general message that basically says I can't get through. If others can connect inbound to that node then you can rule out a port forwarding problem at that node. The other thing I mentioned does that node know of your presence in it's database. I would think it would if it is downloading the database. I have it here in mine and it would be the same if another node properly downloaded it.
The only way you would be able to know for sure is to look at the client log at the end you are connecting to. If you see nothing then your connection is not even getting through to Allstar. If you see an error then you can work from there. It is possible it could be a codec issue if the node operator changed the allowable codecs and they did not match yours. That is not likely though. That is something that would show up in error messages at the client.
There are also strange routing issues that occasionally show up on the Internet where node A would have a route to node B and C but node B would not have a route to C. Something like that is out of your hands but could be reported if you can validate it.
73 Doug
WA3DSP
http://www.crompton.com/hamradio
Date: Fri, 14 Aug 2015 16:46:03 -0400
From: steves68 at gmail.com
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Taking my node on the road.
This is what I get when I try to connect to node 42242:
[Aug 14 16:03:54] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char *[Aug 14 16:03:54] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char 3[Aug 14 16:03:54] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char 4[Aug 14 16:03:54] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char 2[Aug 14 16:03:55] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char 2[Aug 14 16:03:55] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char 4[Aug 14 16:03:55] NOTICE[268]: chan_simpleusb.c:3019 simpleusb_read: Got DTMF char 2[Aug 14 16:03:56] WARNING[268]: channel.c:2447 ast_indicate_data: Unable to handle indication 13 for 'IAX2/76.0.xxx.xxx:4569-3579' -- Hungup 'DAHDI/pseudo-620421355' -- Hungup 'DAHDI/pseudo-1622420236'[Aug 14 16:03:59] NOTICE[255]: chan_iax2.c:4087 __auto_congest: Auto-congesting call due to slow response -- Hungup 'IAX2/76.0.xxx.xxx:4569-3579'
It is the same message every time.
N4YOGSteve
On Fri, Aug 14, 2015 at 10:37 AM, Steve Stark <steves68 at gmail.com> wrote:
Hello group,
I have taken my node with me out of town. I have experienced something interesting. There are 2 nodes I connect to regularlly 42235 and 42242. Now that I am out of town I can't connect or receive connections from 42242 but I can connect to 42235 no problem. I have setup port forwarding at my temporary location on the router. Any Ideas of what may cause this?
Thanks,N4YOGSteve
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150814/365d660e/attachment-0001.html>
More information about the arm-allstar
mailing list