I have read the thread started by BenS on whirpool forum and all the suggestions of making a fake trunk or installing caching DNS but it does not work for me. Any new fix or work-around? I do not like the idea of using SPA3000 or another local hardware SIP trunk just to circumnavigate this bug.

forums.whirlpool.net.au/forum-replies-archive.cfm/960451.html

I hate to break it to you but it appears that the FreePBX developers are not going to be doing anything on this until at least the next milestone (see www.freepbx.org/trac/ticket/3199 and note the comments). Feel free to add your comments to that ticket, but my impression is that this is something that is not a very high priority for them (I may be wrong).

Basically what's needed is a module that will disable selected SIP trunks when internet connectivity is lost. Maybe such a module could be included in Elastix?

srvlookup=no solved the problem for me

Cheers
Garry

srvlookup = no
The easiest solution so far. I will try this but what would be the downside of using this? Routing issues when VOSP changes IP addresses?

gbrook wrote:
srvlookup=no solved the problem for me

Where are you placing that, in the individual trunk configuration?

I wonder if it could be placed in one of the custom SIP files and work just as well. If so, you could run a bash or perl script that checks every five minutes to see if you have a working Internet connection (I think I am running something that checks my IP address every five minutes and rewrites sip_nat.conf it it changes, so the two functions could probably be combined). All you'd have to do is add it to the appropriate file, then reload Asterisk. Once your Internet connection was restored you could reverse the process. This would only work if the srvlookup=no could be placed in one of the general files such as sip_nat.conf (only because I'm already rewriting that file) or sip_general_custom.conf (although strangely enough, I find I already have that statement in there, yet it did not seem to have any effect the last time we had an Internet outage).

It's just weird where this works and where it doesn't. I keep hoping that eventually the FreePBX folks (and in turn, Elastix) will switch from Asterisk to FreeSwitch as the basic engine - I can't imagine the FreeSwitch people would allow this type of stupid bug to continue to exist, whereas the Asterisk developers seem quite content to let a bug like this go unfixed through several major versions. And at the core, this IS an Asterisk problem - the FreePBX folks could write a workaround for it (and I wish they would; they've had to do it for other Asterisk bugs) but the real fault is in Asterisk itself.

Try to setup a local dns server and point elastix to it.

Reaper wrote:
Try to setup a local dns server and point elastix to it.

Well, since a local DNS server is not included with Elastix (although that might not be such a bad idea) that's probably not something that most users (including me) would be capable of. However, I *do* have Webmin installed; do you know of any simple DNS servers that can be set up using Webmin?

By the way, I read a comment in another thread that leads me to think this problem might be fixed in Asterisk 1.6, although until we get that there's no way to know for sure. It seems to me there was Enlaces ocultos para usuarios no registrados. Inicie sesión o regístrese Aquí where someone did upgrade both FreePBX and Asterisk. I'd be happy if we could just upgrade FreePBX and not have it mess up the Extensions page in Elastix, as some have reported it does if you try to upgrade.

EDIT: Added link to the other thread!

Bind or bind9 is pretty simple to setup. Even got a gui for gnome.

Reaper wrote:
Try to setup a local dns server and point elastix to it.

I followed following instructions to setup caching DNS server from PIAF forum. But that does not work either.


1. Install cache only name server on the Asterisk server (BIND with caching configuration)
yum -y install caching-nameserver
chkconfig --add named
chkconfig --level 345 named on
echo "* IN A 127.0.0.2" >> /var/named/localdomain.zone
service named start

2. Set Asterisk as its own DNS server by adding 127.0.0.1 on the first line of /etc/resolve.conf, like
127.0.0.1
your.other.dns.servers

3. Make sure Asterisk has default settings for file /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=your_asterisk_server_name.localdomain
(Do not change HOSTNAME to your_asterisk_server_name.yourdomain.com )

4. Then in file /etc/hosts, something like
127.0.0.1 your_asterisk_server_name.localdomain your_asterisk_server_name localhost.localdomain localhost

5. Reboot (try without the internet connected)

Very similar in concept to the one above, if you want to look at www.elastixconnection.com. There is a new tutorial on there called DNS Cache for Elastix.

It is not as complex to setup. However, I do not have failing SIP system to test it with, so any feedback is welcome...

Regards

Bob