FreeBPX 2.5.1.5 - extensions won't connect after network outage

General Help
1

Hey Guys

I’ve got a weird issue with my FreePBX install.
I had a internet outage caused by an issue with my Fortinet firewall. I’ve repaired that. But now my VOIP handsets won’t register with FreeBPX.

I’ve rebooted the FreeBPX Pika device. FreePBX comes back online. Server status says OK (though disk says 100% in red, not sure if that’s just from my backup tasks).

However, in the Status panel all the snom extensions are greyed out. (ex 100(fax), 1001(loud speaker), 140(security) are ok though).

I rebooted the phones and that didn’t solve the issue. I then reset one of the phones and rebuilt the settings. But I get the same result.

Here is a snapshot of the phone log with the connection error:
[5] 18/12/2013 14:47:28: SIP: transport error: 1000000 -> udp:192.168.45.50:5060
[5] 18/12/2013 14:47:28: SIP: final transport error: 1000000 -> udp:192.168.45.50:5060
[2] 18/12/2013 14:47:28: Transport Error: Pending packet 1000000: generating fake
[2] 18/12/2013 14:47:28: Registrar [email protected] timed out
[5] 18/12/2013 14:48:25: send lldp advertisment
[5] 18/12/2013 14:49:00: SIP: transport error: 1000002 -> udp:192.168.45.50:5060
[5] 18/12/2013 14:49:00: SIP: final transport error: 1000002 -> udp:192.168.45.50:5060
[2] 18/12/2013 14:49:00: Transport Error: Pending packet 1000002: generating fake
[2] 18/12/2013 14:49:00: Registrar [email protected] timed out

I’m a bit stumped as to what could be causing the time out.
What do you guys think could be causing it?
What should I do next to troubleshoot?

Kind Regards
Aaron

2

If the extensions are greyed out Asterisk probably can’t start because the disk is full.

3

Ahh so that is causing a problem.
How do I free up some space on the disk?

4

By removing files you don’t need.

5

I have not removed files from a Pika PABX system running FreeBPX before. From the FreePBX admin web console I can’t see an option to delete files on the disk. Is this something I have to do by command line?

6

Ended up resolving the issue by fixing the DNS resolution.
Thanks for your help SkykingOH :slight_smile: