[bbbeavis]

I have five trunks with different providers; all IAX accounts. I'm behind a Linksys WRT54G w/ Sveasoft firmware with udp port 4569 pointed to my AAH server, dynamic IP on the wan side. All except my Telasip IAX trunk works great. The Telasip trunk occasionally becomes unregistered (no incoming or outgoing). I restart AAH - no joy. I reboot the OS - trunk is fully operational. iax.conf is the usual server, username, secret, registration string (userassword@gw3.telasip.com) and I added notransfer=yes. This config is typical for my other trouble-free trunks. Any suggests?

[bbbeavis]

Ran "iax2 show registry" and all of my trunks were not registered. I could only call out on my Voipjet line. Restarted Asterisk and still no go. Rebooted OS and all lines are now registered. I'm really confused :?

[mberlant]

Do you have a fixed or dynamic IP address? Even though it is not supposed to matter, you may be better off setting your externip= to your IP address.

[mberlant]

I see you have a dynamic IP address. Even though it is not supposed to matter for IAX, you may be better off setting your externip= to your dyndns name and setting a cron job to refresh this setting as often as you feel it is necessary. Search for "cron job" to find the thread that talks about this.

[bbbeavis]

I already instituted the externip=dyndns renewed every 10 min (I saw your previous post in the forum). Just checked my registrations and only my FWD account is still registered. Checked the router; gremlins changed my dyndns password to the wrong one ops: . Corrected the password; rebooted the router; dyndns registered properly; all trunks now unregistered Restarted Asterisk; still not registering. I'm going to reboot the server and see if the problem magically goes away; FWD registered, Telasip unregistered, iaxtel deleted because I never could get it register. . . ever. I'm starting to look for hardware issues (this machine is an old 700mhz Duron doorstop).

OK, did SMART Drive Status test and was rewarded with " The previous self-test completed having the read element of the test failed". I hate computers :x

[mberlant]

Don't be quick to blame your hardware. If you caught some of the fine print on my postings you will know that I run a pretty busy little Asterisk on a Pentium 200 MMX (yes, a Pentium I) with 96MB RAM and 3GB HDD.

Of course, if your HDD is dying you may need to replace it with another. I recommend at least 4GB to give enough space for voice mail messages and log files.

[bbbeavis]

24hrs later and still 100% registered I forgot to mention that the original HD was making a soft "tick-tick-kachunk" sound every 20-30 seconds. I'm one of those people who has had more than my share of failed drives and this sound was all too familiar. I did a full reinstall on another HD including manual reconfigure of a new system using the backup for reference. Thanks for the help. Now if I only can make my incoming SIP calls traverse my Linksys WRT54G 8)

[mberlant]

My Asterisk is in the DMZ of my WRT54GS.