[SOLVED] What could cause SIP_REG to timeout on a working connection?

NOTICE[2343]: chan_sip.c:15180 sip_reg_timeout: – Registration for ‘[email protected]’ timed out, trying again (Attempt #319)

I tried pinging the IP associated with the domain and I can ping it, and I can SSH into this freepbx machine so it does have access to the internet.

I rebooted the PBX remotely and it fixed the issue, but I don’t quite understand what caused this to begin with. I understand that this is not something anyone can answer remotely, but any clues as to what I should do to try and figure out why this occurred to begin with?

Thank you!

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]

…and i spoke too soon. I changed all the pfsense settings, but same thing. Must be something else. I imagine this is going to be a nightmare.

[quote][2016-02-09 01:09:04] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:09:24] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #2)
[2016-02-09 01:09:25] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:09:44] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #4)
[2016-02-09 01:11:29] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:11:49] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]roxy.voicepulse.com’ timed out, trying again (Attempt #2)
[2016-02-09 01:11:49] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:12:09] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #4)
[2016-02-09 01:13:54] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:14:14] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #3)
[2016-02-09 01:15:59] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:16:19] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #2)
[2016-02-09 01:16:19] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:16:39] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #3)
[2016-02-09 01:16:39] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:16:59] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #4)
[2016-02-09 01:18:44] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[2016-02-09 01:19:04] NOTICE[2137] chan_sip.c: – Registration for ‘[email protected]’ timed out, trying again (Attempt #2)
[2016-02-09 01:19:05] VERBOSE[2137] chan_sip.c: – Got SIP response 503 “Not registered” back from 54.175.63.250:5060
[/quote]

The secret to log into the SIP trunk provider was too long. changing it to a shorter, simpler passcode fixed the issue entirely. I was using a secure password generator to create the passwords/secrets for the extensions, as well as for the SIP trunk provider. It’s been registered for three days now.

I just figured I’d come back and post this incase anyone else has the same problem.

2 Likes