Hi Michael,
The easiest way to always make sure a DNS name resolves is to define static IP
addresses in:
Network tab -> Network Services: -> DNS Forwarder & DHCP Server: { Configure
DNS Hosts }
There you can statically define DNS host names without requiring any changes to
your Asterisk configuration. Of course if your SIP provider makes changes you
will have to reconfigure the DNS IP's like a bunny.
Another approach, or in tandem, is to not depend on OPTIONS pings (qualify=yes)
to keep firewall ports open, instead (qualify=no) use very specific (secure)
firewall rules for inbound SIP calls.
To be clear, it is not recommended to do either of the above as a general
practice, but you do what you have to do.
Lonnie
On Jan 11, 2018, at 10:50 PM, Michael Knill <michael.kn...@ipcsolutions.com.au>
wrote:
> Hi Group
>
> I have started a new thread although this is a continuation of my
> intermittent issues with sip trunks not coming back after a network outage.
> After some testing in the lab I have realised that most of these problems are
> related to DNS resolution.
>
> Basically I am using sip domain names for all my providers so DNS resolution
> is necessary. What I have found is that if for some reason DNS resolution is
> not possible (e.g. network is down), if the system is rebooted or Asterisk
> loses the resolved address, it no longer sends the OPTIONS pings as it cant
> find the address obviously.
> Yes that makes sense however the problem arises when the network is restored,
> Asterisk is completely unaware and therefore makes no attempt in resolving
> the address.
> I believe this is what is causing my intermittent issues which is easily
> resolved by doing an Asterisk Reload when network connectivity is restored. I
> have also enabled the Asterisk dnsmgr which does not fix the problem. I
> suspect that if it couldn't initially resolve it then it gives up totally.
>
> So what is the fix. Here are some of my options:
> • Don't use DNS but just use the IP Address instead. This will most
> certainly resolve the issue but is it the best way? Something in the Hosts
> file maybe?
> • Perform sip monitoring using the SIP Monitor script or Monit. If the
> SIP URL is resolvable but the status is UNKNOWN then issue a module reload of
> chan_sip
> • Something else
>
> PS the SIP Monitor does not seem to work for me. It only sends me an email
> when the system is rebooted.
> Thanks all.
>
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
