We are having an issue with 3CX that we cannot seem to get any answers on, and I am banging my head on a wall trying to figure this out. We have been using 3CX for close to the past 10 years, while we have had our ups and downs with the software, we have not really had any real issues affecting our day-to-day processes.
We currently have somewhere around 125 active agents in the system and at what appears to be random moments outbound dialing seizes to function. Regardless of rebuilding the outbound prefixes or creating new ones, it provides a busy beep with 3 beeps and then hangs up. Inbound is not affected when this happens.
There are no error messages or related activity logs in 3CX we have even checked verbose logging with no results related. Twilio our VoIP provider has no logs and states they are not even receiving the dials so I do not believe it's on them.
Our fix is to reboot 3CX services at which it functions for anywhere from 24 hours to several weeks without issue. Rebooting services in the middle of the day is kicking out on average 100 callers who have to dial back causing us CSAT issues and client related conversations around technology that we should not need to have.
What we have done:
We currently have somewhere around 125 active agents in the system and at what appears to be random moments outbound dialing seizes to function. Regardless of rebuilding the outbound prefixes or creating new ones, it provides a busy beep with 3 beeps and then hangs up. Inbound is not affected when this happens.
There are no error messages or related activity logs in 3CX we have even checked verbose logging with no results related. Twilio our VoIP provider has no logs and states they are not even receiving the dials so I do not believe it's on them.
Our fix is to reboot 3CX services at which it functions for anywhere from 24 hours to several weeks without issue. Rebooting services in the middle of the day is kicking out on average 100 callers who have to dial back causing us CSAT issues and client related conversations around technology that we should not need to have.
What we have done:
- Verified firewall rules are correct per 3CX documentation.
- Verified server compute is per 3CX documentation.
- Rebuilt our 3CX servers on Windows Server 2022 machines.
- Rebuilt the outbound dialing prefixes in 3CX.
