Error Status On Dispositions

[Andy_N]

Morning Everyone ,

Hope you all are well ,

Please assist on this issue as it persists.

I am concerned on the DONEM status as its a randon status we dont have in our dispositions. Is there a way to adjust the system and put a different status when system timeout? It is an error status and our report look quite not right as this DONEM status takes a lot of numbers.

Is there a way we can sort these statuses and put a different system timeout error status? Please help!

Kind Regards
Andy

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (11.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (EG: vSphere Version 6.X.X). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox 11.X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC Mbd | Core2Quad Q6600 CPUs

3) To quote Mflorell from http://vicidial.org/VICIDIALforum/viewt ... =4&t=39154:

It's a hard-coded internal temporary in-between status that should not stick to a lead unless something goes wrong with the agent screen as it's processing a function at the end of a call.

Thus your installation method is a notable factor in the solution to your problem.

4) Option (before we find out what went wrong with your installation and solve the problem completely):

(Left menu) Reports => (Bottom link) "Admin Utilities" => Basic Lead Tools => Update Lead Statuses

5) As something is broken, it may be useful to check logs for apache (var/log/apache2) and mysql (depending on your install, could be in a few places) and even the Console logs for the agent(s) experiencing the issue.

6) Can you reliably reproduce the problem with a specific situation?
*