FreePBX | Register | Issues | Wiki | Portal | Support

Devices not registering after reboot, one more reboot fixes it


(Mike Waldron) #1

FreePBX 14, up to date. PJSIP Extensions

Today I powered off the server to attach a UPS. After it came up our Gigaset cordless and Cisco ATA wouldn’t register. I didn’t see any traffic being generated by FreePBX for these extensions. All our S500s acted normally, worked fine.

After exhausting my options with configuring the Gigaset, I figured I’d try a reboot. Boom, the ATA and Gigaset came right up.

I saw this in my asterisk log which I thought suspect, as it affected these devices:

[2017-09-13 14:03:49] VERBOSE[2900] res_pjsip/pjsip_configuration.c: Contact 218/sip:218@10.1.100.54:5060 has been deleted
[2017-09-13 14:03:49] VERBOSE[2900] res_pjsip/pjsip_configuration.c: Contact 210/sip:210@10.1.100.54:5060 has been deleted
[2017-09-13 14:03:49] VERBOSE[2900] res_pjsip/pjsip_configuration.c: Contact 211/sip:211@10.1.100.54:5060 has been deleted
[2017-09-13 14:03:49] VERBOSE[2900] res_pjsip/pjsip_configuration.c: Contact 555/sip:555@10.1.100.55:5060 has been deleted

Is the short answer here: Don’t use PJSIP?


(Mike Waldron) #2

I’ll add the only thing these extensions have in common is they are NOT Sangoma phones.


(Mike Waldron) #3

Doing some Googling… I think this might be the issue:

I was using a local server’s DNS and it probably wasn’t up when FreePBX came up. There’s apparently a reason there’s a big warning that says use 127.0.0.1 (local DNS relay in FreePBX), and THEN your DNS entries.

I’ve replaced the nameservers to public ones. It’s quite possible the reboot fixed it because the DNS server was up at that point.