Hello everyone, after changing the external IP address (due to relocation) and changing the firewall at the same time (Sophos → Watchguard), telephony with a FreePBX no longer works at all - telephony worked before. Neither incoming calls nor outgoing calls work properly. I have more or less inherited this problem, the colleague at the site has unfortunately left us. My experience with FreePBX and VoIP in general is limited. I have almost no idea at all. Nevertheless, I have to somehow make sure that it works again. I’ve rummaged through the logs and created Wireshark traces, but I can’t figure out what the problem is. Perhaps it makes sense if I first describe the problem of calling out. When you try to call out, you get the message: “all circuits are busy now”. The FreePBX log then reports
5959 [2025-07-31 11:19:33] VERBOSE[4307][C-00000029] pbx.c: Executing [continue@macro-dialout-trunk:1] NoOp(“PJSIP/141-00000046”, “TRUNK Dial failed due to CHANUNAVAIL HANGUPCAUSE: 58 - failing through to other trunks”) in new stack
and in Wireshark you can find this entry:
Status-Line: SIP/2.0 488 Not Acceptable Here
Status-Code: 488
[Resent Packet: False]
[Request Frame: 23]
[Response Time (ms): 34]
Now this somehow looks like a problem with the configuration of the trunk on the FreePBX, but nothing has changed (except for the IP address).
This looks like a problem with the configuration of the trunk on the FreePBX, but nothing has changed (apart from the IP address). The provider was informed about the change of the external IP address and has confirmed the change. I have also changed the external IP address in the FreePBX under Asterisk SIP Settings. The Watchguard Firewall allows the FreePBX to use every port to every destination (just for testing purposes). I have no idea what I can do with the information I have to narrow down the problem. Do you have any tips for me? Thanks a lot!
Your not acceptable response is out of context, so one can’t tell whether it is even relevant. Generally not acceptable here means either the UAC is requesting a codec that the UAS doesn’t support (I can’t tell which of UAC and UAS Asterisk is here), or the UAS is requesting encryption options that are not compatible with the UAS (which could include requesting no encryption, when it is required or v.v.
You are potentially dealing with 2 separate issues, of which there could be a problem with both. (Watchguard and external IP)
Did your Internal LAN addresses / subnets change ?
Is everything else on your network working, just not the phones ?
Who is your SIP Service Provider ? AS an example, in SipStation, you have to log into their account and you can set your expected IP Addresses on their website, not just in FreePBX.
Are you positive your upstream is not blocking port 5060 ?
I am worried about that, too. I think dealing with the external IP should be the easier fix. Dealing with the firewall switch gives me a headache, though.
No
Everything else works fine. But there is no other system using the external IP address to be accessed.
It is Byon which resells Colt I believe. Authentication works over external IP address. There is no password needed. I have contacted Byon so that the check if there is something on their end that needs to be fixed. The only response I got from them is that the freepbx is cancelling the call with Q.850 cause 34.
Yes.
Yes, several times.
As far as I can tell in the pcap traces the external IP address back and forth is correct. I am not getting why the freepbx should be cancelling the call.