FreePBX server unable to register SIP trunk after upgrade from 2.1.4 to 2.1.5



  • Hello everyone.

    About two weeks ago I upgraded my firewall hardware from a mini-PC to a SuperMicro 1RU server and decided to upgrade the firmware from 2.1.4 to 2.1.5. This was a fresh install and not an upgrade. I backed up my configuration from the old hardware running 2.1.4 and restored it to the new hardware running 2.1.5. I didn't have any issues with that process however after a few hours my FreePBX VoIP server stopped registering with my SIP provider. I had this exact same problem several months ago when 2.1.5 first came out so I reverted back to 2.1.4 and things began working again. I don't want to revert back to 2.1.4 but I will if I'm unable to get this resolved.

    Nothing on my pfsense nor FreePBX server configuration has changed from 2.1.4 to 2.1.5. I can see from the logs of my FreePBX server that it keeps attempting to register the SIP trunk with the SIP provider but times-out due to no response. What's strange is I do not see these attempts in the firewall logs at all, however when I perform a pcap on the firewalls VoIP interface I do indeed see the traffic sourced from my FreePBX server destined to the SIP provider via UDP/5060. I've verified that the SIP provider's DNS name is properly resolving and that the destination MAC in the pcap is the MAC of my firewalls VoIP interface. So the server appears to be sending the appropriate reqeusts and they are reaching the firewall, however since I don't see that same traffic in the firewall logs (and Yes, I am logging every single firewall rule to include default denies at the end of the ACL, plus sending them to a syslog collector so logs runnnig past the local buffer isn't the issue either) it seems that the firewall is to blame for not processing the requests.

    When this first happened after the upgrade, I would restart the FreePBX server and it would connect to my SIP provider. Then after a few hours it would have the same issue. Now, no matter how many times I reboot the server it doesn't seem to want to connect anymore. I've also tried clearing the firewall state entries for this server but that doesn't seem to work. I'm pretty certain if I reboot the firewall that it will work but only to fail again after a few hours.

    Has anyone ran into this same problem with 2.1.5 or previous versions other than 2.1.4? Does anyone have any recommendations on what else I could do to try and troubleshoot the problem?

    Thank you all in advance for any help with this!



  • So after no luck trying to debug the problem while on 2.1.5, I upgraded to 2.2RC. With that I was still unable to get my FreePBX server to register with my SIP provider; actually it registered for a minute or two after the upgrade reboot but then lost registration rather quickly and never registered again. I was also unable to get STunnel to start up, I normally have this problem even with previous versions but a simple removal and adding back of the "redirect IP" field allows the service to start up, this time that would not work and I could not get the service running again. So I lost hope and did a fresh install of 2.1.4 and now my FreePBX server is happily registered and STunnel is also running. I also noticed with 2.1.5 and 2.2 that one of my PTP OpenVPN Server tunnels would not come up, but it came up immediately when back on 2.1.4 and is stable.

    This is kind of a let down as I dislike running depreciated versions of firmware but don't know what else I could have looked at to see why pfsense would not pass nor log the SIP traffic. I'll try 2.2 once it's in its final release with hopes of everything working as it does right now in 2.1.4.


Log in to reply