Thanks for the info. I am not sure how to disable iptables, but I will be scouring the net for the next couple of hours or so. I simply couldn't believe that * was as unstable as it has been seeming. At least now I know that I'm not crazy. Rich, a previous poster, suggested the following path:
>All the words that you've used tend to suggest a firewall is getting in the way (eg, iptables). A few things you >can do to help narrow down the problem. >1. on each system, do a "arp -a" before and after the connection fails to see what each system thinks is the >current IP & MAC address. If there are no entries, then that system has not even attempted communications at the >layer-3 level. If the entries are present (on each system), then at least you know each has made "some" attempt. > >2. download and implement ethereal, and run it until the failure occurs. Look at the packet displays and see if >that helps point to an issue. If you can't read packet traces from ethereal, there are lots of others on this list >that can. It at least helps point to the problem. > >3. in the /etc/asterisk/logger.conf file, configure it for "debug". Restart asterisk (not reload). Asterisk will >then write lots of detailed messages in a file at /var/log/asterisk (if memory serves correctly). That is may current game plan. Since I do not have any idea how to read the output from step 1 or step 2 I may need to post the results and see if anyone on the list will be able to decipher them. Thanks for your help, Robert -----Original Message----- From: Olle E. Johansson [mailto:[EMAIL PROTECTED] Sent: Saturday, April 10, 2004 4:24 PM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Newbie Issues => SIP won't stay connected, and IAX Unable to Create Channel Robert Jackson wrote: > I am terribly sorry to bother the list with such generic and bizarre > problems, but I have been racking my brain with these for the last > week working on it for at least 60 hours. No need for excuse, we're here to help. You've obviously spent time looking for an answer... All iptables default rules are set allow > and no other rules are entered. The whole setup is a proof of concept Without knowing much about iptables I would say that the "default rules" sounds like a good candidate for further inspection. Can you disable iptables and test without it? Sounds like the iptable fw needs traffic from the inside (ping) to allow anything from the outside. So client's can't register unless the server spoke to them first. And there seems to be a timeout as well on this "session" in your iptables setup. Why an ICMP ping opens up for UDP is a mystery... I'm on very thin ice here, so treat this as a friendly guess from my side. I've seen a few similar mails, but no solution so we need to come up with a problem description and a solution for the FAQ. Good luck! And please tell us what it was that caused the problem when you've solved it. /Olle _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users