I just noticed the one difference in this system; it used to be behind an ASUS RT-66 with no issues. It was moved to a location with a PFsense router. Time to figure out if PFsense is causing some funny issues. I turned off scrubbing in the advanced system settings. Here was the long error log that I saw. The PBX was rebooted at 9:30 AM, and this occurred in the middle of the day. It wouldn’t work until rebooted again.
[quote=“thender, post:2, topic:33177, full:true”][2016-02-08 15:40:51] VERBOSE[2161] asterisk.c: Asterisk Ready.
[2016-02-08 15:40:51] NOTICE[2341] chan_sip.c: Peer ‘301’ is now Reachable. (8ms / 2000ms)
[2016-02-08 15:41:22] WARNING[2341] chan_sip.c: Timeout on [email protected] on non-critical invite transaction.
[2016-02-08 15:46:27] ERROR[2341] netsock2.c: getaddrinfo(“xxx.dca.proxy.voicepulse.com”, “(null)”, …): Name or service not known
[2016-02-08 15:46:27] WARNING[2341] acl.c: Unable to lookup ‘xxx.dca.proxy.voicepulse.com’
[2016-02-08 15:47:07] ERROR[2341] netsock2.c: getaddrinfo(“xxx.dca.proxy.voicepulse.com”, “(null)”, …): Name or service not known
[2016-02-08 15:47:07] WARNING[2341] acl.c: Unable to lookup ‘xxx.dca.proxy.voicepulse.com’
[2016-02-08 15:47:07] NOTICE[2341] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #2)
[2016-02-08 15:47:47] ERROR[2341] netsock2.c: getaddrinfo(“xxx.dca.proxy.voicepulse.com”, “(null)”, …): Name or service not known
[2016-02-08 15:47:47] WARNING[2341] acl.c: Unable to lookup ‘xxx.dca.proxy.voicepulse.com’
[2016-02-08 15:47:47] NOTICE[2341] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #3)
[2016-02-08 15:48:07] NOTICE[2341] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #4)
[/quote]