Losing connection

I have a problem that had dogged me for a while. Ever so often my FreePBX computer loses connection with the SIP provider (Flowroute), and does not seem to be able to recover from that. A reboot of the system fixes that every time. I would appreciate if anybody has some insight into this.

I am using FreePBX 12.0.76.4 and Asterisk (Ver. 11.25.2).

I have discussed this with Flowroute, and they changed their registration to an IP registration (The system is sitting behind an Xfinity modem and a firewall with a fixed IP address), but it still happens. Here is a typical scenario from the log files (some information changed for security reasons):

[2018-03-12 11:34:29] ERROR[2262] netsock2.c: getaddrinfo(“sip.flowroute.com”, “(null)”, …): Temporary failure in name resolution
[2018-03-12 11:34:29] WARNING[2262] acl.c: Unable to lookup ‘sip.flowroute.com
[2018-03-12 11:34:49] ERROR[2262] netsock2.c: getaddrinfo(“sip.flowroute.com”, “(null)”, …): Temporary failure in name resolution
[2018-03-12 11:34:49] WARNING[2262] acl.c: Unable to lookup ‘sip.flowroute.com
[2018-03-12 11:34:49] NOTICE[2262] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #2)
[2018-03-12 11:35:02] NOTICE[2262] chan_sip.c: Peer ‘1700’ is now UNREACHABLE! Last qualify: xxx
[2018-03-12 11:35:02] NOTICE[2262] chan_sip.c: Peer ‘1600’ is now UNREACHABLE! Last qualify: xxx
[2018-03-12 11:35:09] ERROR[2262] netsock2.c: getaddrinfo(“sip.flowroute.com”, “(null)”, …): Temporary failure in name resolution
[2018-03-12 11:35:09] WARNING[2262] acl.c: Unable to lookup ‘sip.flowroute.com
[2018-03-12 11:35:09] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #3)
[2018-03-12 11:35:29] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #4)
[2018-03-12 11:35:39] NOTICE[2262] chan_sip.c: Peer ‘1700’ is now Reachable. (50ms / 2000ms)
[2018-03-12 11:35:39] NOTICE[2262] chan_sip.c: Peer ‘1600’ is now Reachable. (69ms / 2000ms)
[2018-03-12 11:35:49] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #5)
[2018-03-12 11:36:09] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #6)
[2018-03-12 11:36:11] NOTICE[2262] chan_sip.c: Received SIP subscribe for peer without mailbox: 1500
[2018-03-12 11:36:29] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #7)
[2018-03-12 11:36:49] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #8)
[2018-03-12 11:37:09] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #9)
[2018-03-12 11:37:10] VERBOSE[2262] chan_sip.c: – Registered SIP ‘1500’ at 192.168.x.x:xxxx
[2018-03-12 11:37:10] NOTICE[2262] chan_sip.c: Peer ‘1500’ is now Reachable. (80ms / 2000ms)
[2018-03-12 11:37:11] NOTICE[2262] chan_sip.c: Received SIP subscribe for peer without mailbox: 1500
[2018-03-12 11:37:29] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #10)
[2018-03-12 11:37:49] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #11)
[2018-03-12 11:38:09] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #12)
[2018-03-12 11:38:29] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #13)
[2018-03-12 11:38:49] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #14)
[2018-03-12 11:39:09] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #15)
[2018-03-12 11:39:29] NOTICE[2262] chan_sip.c: – Registration for '‘[email protected]’ timed out, trying again (Attempt #16)

(… ad absurdum).

It used to happen every few days, so I put the system on an automatic reboot at 4 AM, that fixed it for about a year. Now it seems to happen again more frequently. The problem is, of course, that this only shows up when someone tries to call out,. Everybody who calls in gets a message like “The party cannot be reached”.

mike_b, off chance you recall this issue and/or found a resolution? I’m in the same boat with a client using almost the same version (12.0.76.6). This issue has only reared its ugly head for the past couple of months.

The problem was in the original question. Are you also having Address Resolution (DNS Failure) problems?

Ahh gotcha. Their SIP trunks are configured via IP, so not a DNS issue. Thanks for the response.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.