Agent on Live Call showing as DEAD in Live Report

[nitinjain.techie]

Vicidial Version : 2.4

I am facing an issue of Wrong Agent Live Status. My agent is on call but it show as DEAD some times.
Any help appreciated

[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 and vicidial version with 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 "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. 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 (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox 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 | Core2Quad Q6600

3) Usually bad network somewhere in your system. Between the agent and dialer quite often. Unless of course you are wrong and the agent only LOOKS like he's on a call but the customer has hung up (this is actually the definition of "DEAD CALL").

[omar]

Same problem. Did you solve it?

--------------------------------
ViciBox v.7.0.3
Vicidial Version: 2.12b0.5
Vicidial SVN Rev: 2580
Asterisk 11.23.1-vici
1xDB-Web-Dialer-Archive (all in one server)

[ClearCall]

Did anyone find a solution for this?

[mflorell]

Try upgrading, we've updated code related to this in the last couple months.