" /> Best Log File for Abandoned Calls - Genesys CTI User Forum

Author Topic: Best Log File for Abandoned Calls  (Read 3049 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Best Log File for Abandoned Calls
« on: April 27, 2009, 07:25:46 PM »
Advertisement
Hello,
Which is the best log file to track abandoned calls? URS,t-server or Statserver?
Does it actually specify that this event has actually occurred?

I thought this would be the URS file but cannot see this defined specifically as so?  But just might be not analyzing it enough.

Thanks,
WA

Offline SisB

  • Jr. Member
  • **
  • Posts: 60
  • Karma: 0
Re: Best Log File for Abandoned Calls
« Reply #1 on: April 27, 2009, 10:12:27 PM »
T-Server.

What are you looking at and what type of DN?
« Last Edit: April 27, 2009, 10:14:34 PM by SisB »

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: Best Log File for Abandoned Calls
« Reply #2 on: April 28, 2009, 06:13:39 PM »
Our routing strategy is skill based so from tracking the call I can see it check the status of agents with relevant skill (in this case max time in ready state).  None are available (most are in 'no ready') before the call is diverted to an ACD queue but I cannot see where the final result is - all this from the URS log.

Also when the log file defines the agent as not ready during the select target process, does this mean they are not ready or could be on a call as well?

Thanks,
WA

Offline SisB

  • Jr. Member
  • **
  • Posts: 60
  • Karma: 0
Re: Best Log File for Abandoned Calls
« Reply #3 on: April 28, 2009, 08:13:16 PM »
URS is not the right place for tracking the calls that travel through ACDQueue types. Check T-Server logs.

Not ready means NOT ready, anything except ready e.g. in a call, aux, acw etc.