So recently had a power outage that lasted for a bit, afterwards our 3cx installation running on Linux debian had changed to DHCP for some unexplainable reason.
Changed it back to it's default static IP, phones started to register immediately, Trunk registered, FQDN resolves, Firewall OK, SBC good, all green, or so it seemed.
Except, when someone calls in, goes through the queue (no problem here) then after getting connected to a phone/user the call gets dropped after exactly 17 seconds, 3cx simply reports "Lost Call in Queue" with no further explanation. Outgoing calls work just fine.
Second thing I noticed was that when I changed the Trunk to route directly to an extension (instead of Queue:81 Ext:10 and this for calls outside of office hours) it wouldn't accept this change and still route me to the original Queue (81 playing the office closed prompt) instead of routing to the extension, it will however properly route if I change the office hours.
I SSH'd into the 3cx, but everything seems to check out, timezone and time is correct. Currently blanking on what could possibly be causing this issue.
Changed it back to it's default static IP, phones started to register immediately, Trunk registered, FQDN resolves, Firewall OK, SBC good, all green, or so it seemed.
Except, when someone calls in, goes through the queue (no problem here) then after getting connected to a phone/user the call gets dropped after exactly 17 seconds, 3cx simply reports "Lost Call in Queue" with no further explanation. Outgoing calls work just fine.
Second thing I noticed was that when I changed the Trunk to route directly to an extension (instead of Queue:81 Ext:10 and this for calls outside of office hours) it wouldn't accept this change and still route me to the original Queue (81 playing the office closed prompt) instead of routing to the extension, it will however properly route if I change the office hours.
I SSH'd into the 3cx, but everything seems to check out, timezone and time is correct. Currently blanking on what could possibly be causing this issue.
