Author Topic: Wrong info about some calls  (Read 3155 times)

emel_punk

  • Jr. Member
  • **
  • Posts: 97
  • Karma: 0
    • View Profile
    • Email
Wrong info about some calls
« on: September 04, 2009, 01:21:08 »
 >:(

Hello its me again  ::)


I've been in trouble  with   some info that its been show it into queuemetrics, when its displayed for some queues that we have  for  a company. for example

- when im gonna see  the calls unanswered for today it show me that some agents have been waiting about 15 minuts o even an hour  ,then i checked out my asteriskcdrdb database and the calls appear  as a ANSWERED call .

- Some times it show me calls like Disconection : Unaswered yet. on Unanswered calls.

- In other situation, im gonna check out Realtime monitor,  and i see calls  that  has been procesed and that my agent has 30 minutes or even more speaking . Which  i corroborate  it trying to spying the agent and offcourse the agent is in another call or simply not making any call at all. Im using agentlogin() for those agents.


and my QM version is 1.52. asterisk 1.4.26.1.


any helps its helpfull for me !!   8)


this is a pic !!!
http://i279.photobucket.com/albums/kk121/emel_punk/errorqmetriz.jpg

http://i279.photobucket.com/albums/kk121/emel_punk/errorqmsept03de20093.jpg
« Last Edit: September 04, 2009, 15:58:28 by emel_punk »

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Wrong info about some calls
« Reply #1 on: September 07, 2009, 17:22:22 »
Are those calls inbound or outbound? it looks like a lot of events are not logged.....

emel_punk

  • Jr. Member
  • **
  • Posts: 97
  • Karma: 0
    • View Profile
    • Email
Re: Wrong info about some calls
« Reply #2 on: September 11, 2009, 07:36:29 »
they are  outbound calls .... ???

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Wrong info about some calls
« Reply #3 on: September 15, 2009, 09:17:03 »
If they are outbound, it likely means that your logging script (which one are you using?) is losing events. You should try and track call progress manually and see if/where it crashes.