Newly installed FusionPBX times out SIP connection on port 5060

C

crusader.fgn

New Member
Jul 26, 2025
5
0
1
47
I've reinstalled a new FusionPBX since I'm still running a very old implementation of this PBX solution.
I've copied the configs a tried to do a switch of the PBX systems to the same IP the original old 3.x version had and phones are connecting with.
Now the issue is, that on the new PBX appliance the connection for SIP is timing out on port 5060, even though the port is open according to netstat/ss.
What exactly am I missing? I don't see incoming traffic in the log viewer, which makes it hard to guess what is causing the issue. Can someone support me on that topic?
Thank you in advance.
 
Did you check Iptables? Is the port open?

Also, check SNGREP to ensure the traffic is directed to your box.
 
I've checked the IPTables, it has all the necessary ports open. That doesn't seem to be the issue. The traffic is directed to my box, cause I checked it with wireshark and it's trying to reach the IP of my FusionPBX box, still it's not responding. Is it possible that there is a service not running properly, or somehow not active?
 
crusader.fgn said:
I've checked the IPTables, it has all the necessary ports open. That doesn't seem to be the issue. The traffic is directed to my box, cause I checked it with wireshark and it's trying to reach the IP of my FusionPBX box, still it's not responding. Is it possible that there is a service not running properly, or somehow not active?
Click to expand...
If traffic is directed to your box, it doesn't yet mean it reaches it. You need to run SNGREP to confirm that. Once you confirm, then check FreeSwitch running as @DigitalDaz suggested. Also, check the ports it's listening on.
 
Is the Freeswitch status something I can check on the WebUI as well, or is that only possible via CLI?
@pbxgeek: btw. the sngrep tells me that the registration requests are reaching the pbx box. So it has to be Freeswitch or another service.
Yet Freeswitch "is" in fact running, so what else can it be?
 
should I be able to see events directly on the CLI console? If that's the case, nothing is happening at all. According to the status:


Code: 
 show status
UP 0 years, 14 days, 0 hours, 55 minutes, 24 seconds, 822 milliseconds, 876 microseconds
FreeSWITCH (Version 1.10.12-release git d8481a9 2025-01-13 17:41:43Z 64bit) is ready
0 session(s) since startup
0 session(s) - peak 0, last 5min 0
0 session(s) per Sec out of max 30, peak 0, last 5min 0
1000 session(s) max
min idle cpu 0.00/97.03
Current Stack Size/Max 240K/8192K

there was any session. Yet I don't know if a session only counts as an active sip call or every event with a sip device.

Concerning the events, that's all I get:

Code: 
RECV EVENT
Event-Name: RE_SCHEDULE
Core-UUID: b34c7257-0863-40d2-be21-2f879d5011e7
FreeSWITCH-Hostname: fusionpbx
FreeSWITCH-Switchname: frollein
FreeSWITCH-IPv4: 192.168.10.10
FreeSWITCH-IPv6: ::1
Event-Date-Local: 2025-10-04 10:19:14
Event-Date-GMT: Sat, 04 Oct 2025 08:19:14 GMT
Event-Date-Timestamp: 1759565954335777
Event-Calling-File: switch_scheduler.c
Event-Calling-Function: switch_scheduler_execute
Event-Calling-Line-Number: 73
Event-Sequence: 143584
Task-ID: 2
Task-Desc: check_ip
Task-Group: core
Task-Runtime: 1759566014


RECV EVENT
Event-Name: HEARTBEAT
Core-UUID: b34c7257-0863-40d2-be21-2f879d5011e7
FreeSWITCH-Hostname: fusionpbx
FreeSWITCH-Switchname: frollein
FreeSWITCH-IPv4: 192.168.10.10
FreeSWITCH-IPv6: ::1
Event-Date-Local: 2025-10-04 10:19:34
Event-Date-GMT: Sat, 04 Oct 2025 08:19:34 GMT
Event-Date-Timestamp: 1759565974335773
Event-Calling-File: switch_core.c
Event-Calling-Function: send_heartbeat
Event-Calling-Line-Number: 95
Event-Sequence: 143585
Event-Info: System Ready
Up-Time: 0 years, 14 days, 1 hour, 3 minutes, 20 seconds, 118 milliseconds, 177 microseconds
FreeSWITCH-Version: 1.10.12-release+git~20250113T174143Z~d8481a949d~64bit
Uptime-msec: 1213400118
Session-Count: 0
Max-Sessions: 1000
Session-Per-Sec: 30
Session-Per-Sec-Last: 0
Session-Per-Sec-Max: 0
Session-Per-Sec-FiveMin: 0
Session-Since-Startup: 0
Session-Peak-Max: 0
Session-Peak-FiveMin: 0
Idle-CPU: 97.133333


RECV EVENT
Event-Name: RE_SCHEDULE
Core-UUID: b34c7257-0863-40d2-be21-2f879d5011e7
FreeSWITCH-Hostname: fusionpbx
FreeSWITCH-Switchname: frollein
FreeSWITCH-IPv4: 192.168.10.10
FreeSWITCH-IPv6: ::1
Event-Date-Local: 2025-10-04 10:19:34
Event-Date-GMT: Sat, 04 Oct 2025 08:19:34 GMT
Event-Date-Timestamp: 1759565974335773
Event-Calling-File: switch_scheduler.c
Event-Calling-Function: switch_scheduler_execute
Event-Calling-Line-Number: 73
Event-Sequence: 143586
Task-ID: 1
Task-Desc: heartbeat
Task-Group: core
Task-Runtime: 1759565994


RECV EVENT
Event-Name: HEARTBEAT
Core-UUID: b34c7257-0863-40d2-be21-2f879d5011e7
FreeSWITCH-Hostname: fusionpbx
FreeSWITCH-Switchname: frollein
FreeSWITCH-IPv4: 192.168.10.10
FreeSWITCH-IPv6: ::1
Event-Date-Local: 2025-10-04 10:20:14
Event-Date-GMT: Sat, 04 Oct 2025 08:20:14 GMT
Event-Date-Timestamp: 1759566014355757
Event-Calling-File: switch_core.c
Event-Calling-Function: send_heartbeat
Event-Calling-Line-Number: 95
Event-Sequence: 143589
Event-Info: System Ready
Up-Time: 0 years, 14 days, 1 hour, 4 minutes, 0 seconds, 138 milliseconds, 607 microseconds
FreeSWITCH-Version: 1.10.12-release+git~20250113T174143Z~d8481a949d~64bit
Uptime-msec: 1213440138
Session-Count: 0
Max-Sessions: 1000
Session-Per-Sec: 30
Session-Per-Sec-Last: 0
Session-Per-Sec-Max: 0
Session-Per-Sec-FiveMin: 0
Session-Since-Startup: 0
Session-Peak-Max: 0
Session-Peak-FiveMin: 0
Idle-CPU: 96.966667


So I don't even see the registration attempts which are in fact reaching the host itself.
 
Last edited:
If you are trying to watch SIP traffic that is not secured with SSL. Then you can use sngrep, it has an easy and intuitive interface. FusionPBX installs this by default, as it is a very useful command-line tool.
```
sngrep
```
You also need to look at FreeSWITCH.
  • If using FusionPBX, you would go to Status -> SIP Status
    • If not, and you are using FreeSWITCH, then use the command line
    • fs_cli -x 'sofia status'
  • Make sure the SIP profiles are running.
  • Make sure FreeSWITCH is not binding to loopback on 127.0.0.1. This happens if FreeSWITCH starts too fast before the network is fully ready.
  • Check Status -> Event Guard to make sure the IP address for your phone wasn't blocked.
 
If I check the SIP Status from within FusionPBX I only see this:

1759616392821.png
So ipv6 is running but shouldn't there be a ipv4 as well? I think in my old version there was.

This is what the status shows in the SIP Status

1759616448798.png

According to my Event Guard there is no blocked phone at all.
 
You must log in or register to reply here.
Top Bottom