DNS issues / solutions?

[brk]

When my network goes down, freepbx (latest v14 distro) gets confused on the DNS entry and never recovers.

[2018-12-08 12:08:21] NOTICE[2323] chan_sip.c:    -- Registration for '[email protected]' timed out, trying again (Attempt #2)
[2018-12-08 12:08:42] NOTICE[2323] chan_sip.c:    -- Registration for '[email protected]' timed out, trying again (Attempt #3)
[2018-12-08 12:09:22] ERROR[2323] netsock2.c: getaddrinfo("inbound1.vitelity.net", "(null)", ...): Name or service not known
[2018-12-08 12:09:22] WARNING[2323] acl.c: Unable to lookup 'inbound1.vitelity.net'
[2018-12-08 12:09:22] NOTICE[2323] chan_sip.c:    -- Registration for '[email protected]' timed out, trying again (Attempt #4)
[2018-12-08 12:10:02] ERROR[2323] netsock2.c: getaddrinfo("inbound1.vitelity.net", "(null)", ...): Name or service not known
[2018-12-08 12:10:02] WARNING[2323] acl.c: Unable to lookup 'inbound1.vitelity.net'
[2018-12-08 12:10:02] NOTICE[2323] chan_sip.c:    -- Registration for '[email protected]' timed out, trying again (Attempt #5)
[2018-12-08 12:10:22] ERROR[2323] netsock2.c: getaddrinfo("inbound1.vitelity.net", "(null)", ...): Name or service not known
[2018-12-08 12:10:22] WARNING[2323] acl.c: Unable to lookup 'inbound1.vitelity.net'
[2018-12-08 12:10:22] NOTICE[2323] chan_sip.c:    -- Registration for '[email protected]' timed out, trying again (Attempt #6)

Machine name is still recognized by ping -

[root@xxxx asterisk]# ping inbound1.vitelity.net
PING inbound1.vitelity.net (64.2.142.26) 56(84) bytes of data.
64 bytes from 64.2.142.26 (64.2.142.26): icmp_seq=1 ttl=49 time=42.0 ms
64 bytes from 64.2.142.26 (64.2.142.26): icmp_seq=2 ttl=49 time=42.8 ms

“core restart gracefully” does not resolve the problem.

“fwconsole restart” does not resolve the problem

I have to restart the computer to fix it.

Any other way to avoid the problem? or fix without a reboot?

[brk]

Someone reported core reload resolved in the past -

IP Trunk Registration not re-connecting after internet outage

I also have the exact same problem, and I prefer logging into cli and just do a ‘core reload’ there, and it will reconnect to the trunks. Basically it just show the trunks registered, but they are lagging, so it doesn’t accept any call nor dial out. Does anybody have any solutions for this situation?

I’ll force an outage and find out.

This is in asterisk code?

[BlazeStudios (Tom Ray)]

Common issue with Chan_SIP. PJSIP does not have this issue, one of the things that was fixed between the two drivers.

You’ll basically have to do a sip reload each time this happens.

[brk]

Thank you.

I’ll see if I can switch. I have chan_pjsip for my backup outbound trunk and all my extensions, but I was unsuccessful in getting it to work with vitality last time I tried (over a year ago).

[brk]

Pjsip worked with no special settings this time! Thanks again @BlazeStudios!