I really need to get this resolved. This production system has been deployed since October of last year, and this issue has persisted since then; even through an in-place upgrade from FreePBX 14 - Asterisk 13 to FreePBX 15 - Asterisk 16. This system is at a doctor’s office, with 20 Sangoma phones (s705’s and s405’s, and around 3 Cisco SPA112 ATAs for fax on some copiers).
Basically here are the symptoms. Randomly, but usually after a couple days of low activity (like over the weekend), I believe the system is losing its trunk registration. If I try and call their primary (trunk) number from my cell, I will get a Verizon wireless message like the number doesn’t exist. Typically if I just place an outbound call from any desk phone or even a soft phone app, the system will immediately begin working as expected.
This issue happens any time they lose their cable internet connection for a few minutes, but also happens sometimes when there’s just been little to no activity on the system (like over the weekend).
I would be glad to provide any additional information that may help in troubleshooting this issue.
Here are some details that may prove helpful. Their SIP trunk provider is Momentum
This is only because of the relationship with the local internet provider. Back when they were on an old NEC PBX, they received their phone service from the local internet provider through an Adtran. The local internet provider uses Momentum as their SIP trunk provider, so in order to keep everything under one bill (Literally electric, cable internet, phone, water, sever, and trash pickup), I stuck with Momentum. I have them configured as a PJSIP trunk directly in FreePBX.
Here are some of the settings…anything not listed is likely default.
DTMF Mode: Auto
Trust RPID/PAI: Yes
Send RPID/PAI: Send P-Asserted-Identity header
Because it’s using outbound authentication, I do not have any ports manually opened on the firewall. In other words, there’s no inbound NAT port forwarding of UDP 5060 to the FreePBX server. But again, if the registration is outbound, I wouldn’t think it would be necessary to open this port to the world. And, again, keep in mind this system has been in production since October of last year, and except for a Asterisk bug that caused issues with their Sangoma phones locking up, this is the only other major issue they’ve faced.
Any help would be greatly appreciated.