I tried this with a basic switch (unmanaged) and it still doesn’t work.
Now I have a new issue as well.
Outbound calls ring, if I answer, it keeps ringing.
I tried this with a basic switch (unmanaged) and it still doesn’t work.
Now I have a new issue as well.
Outbound calls ring, if I answer, it keeps ringing.
That’s a fault in the phone, or you are talking about ringback tone at the caller, rather than the actual ringing of the phone. I’m assuming VoIP, as it could be a ring trip problem on an analogue line.
Hi @AlexMHz
Morning, I have not seen details of your installation ? did you install your FreePBX-17 to Debian or Ubuntu ? and how you did installed ? Which method or way did you follow?
I’ve tried with a physical IP phone and a Sangoma softphone.
I call out from the Sangoma phone, to my personal mobile, if I answer, the Sangoma softphone keeps ringing.
Morning,
I originally installed Debian (Latest version) and then ran the FreePBX script command line as per installation guide.
I think multiple advice from all of us may be leaving @AlexMHz confused. I will step back and allow @david55 or @shahin lead the troubleshooting and only step in on an ongoing troubleshooting step if/when there is a need to. I’m vested in this and would like to see how it is resolved.
Thank you, I really appreciate your time on this as well.
About a month ago, I installed Debian 12.8 as normal in a brand new Protectli device.
I made sure Debian was fully up to date with the following commands:
“apt-get update” and “apt-get upgrade”.
After than, in root, I ran the installation scripts as found in the FreePBX Github:
wget https://github.com/FreePBX/sng_freepbx_debian_install/raw/master/sng_freepbx_debian_install.sh -O /tmp/sng_freepbx_debian_install.sh
and then
bash /tmp/sng_freepbx_debian_install.sh
The installation took a while to finish but eventually I had the Web UI.
I went through with the configuration and then, I set up a static IP for the FreePBX on our pfSense firewall.
Restarted FreePBX and accessed it with the new IP address. Created a new pjsip trunk with the credentials given to me by our VoIP provider (ICUK) and it was immediately reachable and connected.
I then created an extension to test things with. I grabbed an IP phone and added the credentials details and the local IP of the FreePBX for the phone to register to. Worked immediately.
I then created an inbound route for a testing number (DID was set as +44NumberGoesHere), CID was any and the destination was the extension I created.
I then created an outbound route with the same testing number as the Route CID, and made sure the trunk sequence for matched routes was set to the ICUK Trunk.
I also added some dial patterns.
After that, I gave the system a reboot for good measure.
When the system was fully online, I attempted to call out to my personal mobile. Worked.
I then called in from my personal mobile. Worked.
Then I carried on with setting up more extensions, registering to a FQDN for a Let’s Encrypt certificate, that worked straight away as well.
We eventually got Sangoma softphones (Sangoma Connect) and that was working pretty well too.
I also had Ring Groups and Time Conditions, it was all working beautifully.
Obviously at this point, I had added IP addresses to the trusted zone, such as the SIP provider’s IP address, and I also had firewall rules to allow UDP traffic into the right RDP ports, screenshots uploaded yesterday.
Then, suddenly about a week ago, all inbound calls stopped working. No changes.
I had made backups so I restored to a day or two before, no changes.
Then, I basically did the whole thing again from scratch, no difference.
Really puzzled.
Thank you for good & simple explanation, its puzzled
may i ask you to send us some details. i wondered could be your Debian to have another firewall service ? running background.
# cat /etc/debian_version
# uname -a
# systemctl list-units --type=service --state=active
# ls -d /sys/class/net/*/device | cut -d/ -f5
# ethtool -i Printerd-NIC-NAME
# route -n
cat /etc/debian_version
12.10
uname -a
Linux FreePBX 6.1.0-34-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.135-1 (2025-04-25) x86_64 GNU/Linux
systemctl list-units --type=service --state=active
UNIT LOAD ACTIVE SUB DESCRIPTION
apache2.service loaded active running The Apache HTTP Server
apparmor.service loaded active exited Load AppArmor profiles
atd.service loaded active running Deferred execution scheduler
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
chrony.service loaded active running chrony, an NTP client/server
connect-proxy.service loaded active running Sangoma connect-proxy
console-setup.service loaded active exited Set console font and keymap
cron.service loaded active running Regular background program processing daemon
dbus.service loaded active running D-Bus System Message Bus
fail2ban.service loaded active running Fail2Ban Service
freepbx.service loaded active exited FreePBX VoIP Server
[email protected] loaded active running Getty on tty1
haproxy.service loaded active running HAProxy Load Balancer
[email protected] loaded active exited ifup for enp1s0
ifupdown-pre.service loaded active exited Helper to synchronize boot up for ifupdown
incron.service loaded active running file system events scheduler
keyboard-setup.service loaded active exited Set the console keyboard layout
kmod-static-nodes.service loaded active exited Create List of Static Device Nodes
mariadb.service loaded active running MariaDB 10.11.11 database server
networking.service loaded active exited Raise network interfaces
openvpn.service loaded active exited OpenVPN service
postfix.service loaded active exited Postfix Mail Transport Agent
[email protected] loaded active running Postfix Mail Transport Agent (instance -)
redis-server.service loaded active running Advanced key-value store
rsyslog.service loaded active running System Logging Service
sangoma-pnpd.service loaded active running Sangoma PnP Service
ssh.service loaded active running OpenBSD Secure Shell server
systemd-binfmt.service loaded active exited Set Up Additional Binary Formats
systemd-fsck@dev-disk-by\x2duuid-697B\x2dE264.service loaded active exited File System Check on /dev/disk/by-uuid/697B-E264
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-sysusers.service loaded active exited Create System Users
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create System Files and Directories
systemd-udev-trigger.service loaded active exited Coldplug All udev Devices
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
systemd-update-utmp.service loaded active exited Record System Boot/Shutdown in UTMP
systemd-user-sessions.service loaded active exited Permit User Sessions
tftpd-hpa.service loaded active running LSB: HPA’s tftp server
[email protected] loaded active exited User Runtime Directory /run/user/1000
[email protected] loaded active running User Manager for UID 1000
xinetd.service loaded active running LSB: Starts or stops the xinetd daemon.LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
47 loaded units listed.
ls -d /sys/class/net/*/device | cut -d/ -f5
enp1s0
enp2s0
ethtool -i Printerd-NIC-NAME
-bash: ethtool: command not found.
I ran apt-get install ethtool, but same error afterwards.
route -n
-bash: route: command not found
My bad i think by default net-tools
is not coming. you have to install separately.
root@FreePBX:/home/admin# sudo apt install net-tools
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
net-tools is already the newest version (2.10-0.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@FreePBX:/home/admin# net-tools
bash: net-tools: command not found
Same behaviour
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 enp1s0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp1s0
If I go into “Core Set Verbose 5” within Asterisk -r
I get this every 15 seconds or so:
[2025-04-29 12:39:26] ERROR[1821]: res_pjsip_stir_shaken.c:413 stir_shaken_outgoing_request: ICUK: No channel
[2025-04-29 12:39:26] WARNING[1821]: res_pjsip_geolocation.c:492 handle_outgoing_request: ICUK: Session has no channel. Skipping.
Not sure how relevant it is.
STIR/SHAKEN! That’s a US thing! I wouldn’t have thought of that as most of my work is with US providers. Might have to call in the Sangoma big guns for that. I didn’t even know it was installed by default.
Can you reinstall using the older FreePBX isos to see if this issue still persists? I feel there’s something not right with the Install script
https://downloads.freepbxdistro.org/ISO/SNG7-PBX16-64bit-2306-1.iso
I see that the new script was updated yesterday. Something in a more recent change may be triggering that. Personally, I never download and use the the script live of Github. Download, test, keep my own copy that I reuse unless I need updated functionality
Absolutely, I’ll do a fresh install with that ISO and report back
Are you 100% sure this is for an inbound call? If it is then it appears the be truncated as the first entry in this log in the PBX sending a request to the pfSense firewall. That shouldn’t be what is happening for an inbound request, the tcpdump on FreePBX would show an incoming request from pfSense followed by the replies for it.
The system also wouldn’t be doing an SRV lookup as part of the response to an incoming request. It seems this is not an actual dump of a new incoming request.
pfSense is infamous for handling SIP like a dumpster fire. Not sure why all this work is being done on the PBX system when not one piece of data shows an incoming request actually hitting the PBX.
DO NOT DO THAT. This isn’t a FreePBX issue or an install issue of FreePBX. You haven’t shown (again) that new incoming requests are even making it to the FreePBX, your outbound calls are working but the issue with the connection after answering is due to a firewall/NAT problem.
In other words, this is a networking issue not a PBX system issue or FreePBX issue.
I just don’t know why it would work fine for a while and then suddenly stop working, there had been no firewall changes since then.
Nothing is hitting the PBX when I call in so I’ve got nothing to show there.
Could you possibly point me to the right direction regarding the firewall rules ?
I’m sure they’re correct, but I’m happy to check again just in case I’m missing something there.