Perhaps your router is going bad. If its not forwarding port 4569 UDP properly, despite it says it is, then you wont be able to connect to any one. As you said if you move the node to the DMZ then it works.
I have seen routers do this over a period of time. Perhaps a router reboot will help.

Also I have seen in the past some nodes dont seem to get the node lists for a while. If the node you are trying to connect to isn't in your node list or the list is stale, then you wont be able to connect. Also if your node isn't in the extnode list that gets pushed out then nobody else can connect to you because you don't exist as far as they are concerned.

You can look in the extnodes list to see if the node you want to connect to is there.

Its located at: /var/lib/asterisk/rpt_extnodes

If all was working in the past then I'm thinking you router may be on its way out.

You can monitor the traffic on port 4569 to see if the stat packets are going out and receiving the ack by running this command at the root prompt:

tcpdump udp port 4569 -ni eth0

Use CTL C to stop monitoring.

If you dont see the ack in bound to port 4569 then it could be your  router.

As for the stat reporting, normally when a node is off line and goes on line the node must report to the stat page at regular times. And it must get the extnode file on a regular basis. As it was said you must wait for the node list to be pushed out to all the nodes before you exist to them. My experience is 10 -15 min but it varies.

Use the TCP dump to confirm this is going on.

Hope this helps.

Jon VA3RQ

On 8/25/2012 12:27 AM, Jim W7RY wrote:
You are.. It has been on line for 2 days. Please check the status page for node 28238 and you can see that it’s been on for several days. The node was blocked from the WIN system. But that doesn't explain why I couldn't connect to anyone else.
 
Thanks
73
Jim W7RY
 
 
 
 
Sent: Friday, August 24, 2012 7:47 PM
Subject: Re: [App_rpt-users] Why Can't I Connect?
 

Patience is virtue ... Once node is booted and reporting on the status pages ... WAIT ...

It takes time for register / authenticate protocols to activate fully, you'll notice that eL is operational before the AllStar node I'n some cases ...
 
So my best advice is WAIT, at least a good 30 mins before attempting to connect is what I stress. I get the phone calls "My Node Is Broken, fix it" ...
 
Blah!
 
And during your wait time you can test a few things just to test, if you like testing. TRY from the CLI:
 
iax2 show registry
 
And maybe a few ping test will bypass enough time for your node to come online ... So if after 30 mins connection fails I'd begin the troubleshooting ...
 
I may be way off, but I bet others are wandering the same thing.
 
73
 
k5TRY

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users