All installation and configuration problems and questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
by joebiden » Tue Aug 06, 2019 4:34 pm
Hi,
I been encountering this and i dont know what seems causing this, is this a bug?
Regards,
VERSION: 2.14-705a BUILD: 190327-2311 | Asterisk 13.21.1-vici | Clustered Server No Digium/Sangoma Hardware | No Extra Software After Installation
-
joebiden
-
- Posts: 23
- Joined: Wed Apr 17, 2019 3:43 pm
by mflorell » Wed Aug 07, 2019 8:39 am
This is a response to a bug actually. If the system is checking to see if there is a call about to be sent to the agent, the system will not allow the agent to go into a paused state.
-
mflorell
- Site Admin
-
- Posts: 18384
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
-
by joebiden » Wed Aug 07, 2019 10:40 am
Hi,
How can we resolved this as we already updated to the current release
Regards,
VERSION: 2.14-705a BUILD: 190327-2311 | Asterisk 13.21.1-vici | Clustered Server No Digium/Sangoma Hardware | No Extra Software After Installation
-
joebiden
-
- Posts: 23
- Joined: Wed Apr 17, 2019 3:43 pm
by mflorell » Thu Aug 08, 2019 8:30 am
If this happens a lot on your system, it is usually either a network issue or a database issue. The most common problem is a database that has too many active records in it, like within the vicidial_list table or some of the log tables. Make sure you are regularly archiving your logs, and depending on your database hardware you should have less than 2-10 million leads in the vicidial_list table.
-
mflorell
- Site Admin
-
- Posts: 18384
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
-
Return to Support
Who is online
Users browsing this forum: No registered users and 119 guests