Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 03-07-2017, 12:16 AM
mjuluk mjuluk is offline
Aspiring Member
 
Join Date: Feb 2017
Posts: 2
mjuluk has 10 reputation points
Default Multiple records in hagent intrahour tables in Avaya DB for same interval

I recently looked at Avaya CMS data in hagent tables and I see that for the same logid, split, acd, row_date, starttime, loc_id combination, there are multiple records in the hagent table.

It means for the same agent, there are multiple entries of calls for the same split, in same ACD in the same day & interval, in the same location. This does not seem correct.
Is this a possible scenario?
We actually noticed a lot of such records for each such combinations.. sometimes 4-5 in a set. Why does CMS record so many instances? Which record can we consider for reporting complete information of that interval?

Also, We see that incomplete is 1 for many records. What we want to understand is, if the data is incomplete for a particular interval, will there be a corresponding record where data is complete? We have seen that in many cases there is no completed record.
Reply With Quote
  #2  
Old 05-17-2017, 11:14 PM
cartw7 cartw7 is offline
Brainiac
 
Join Date: Apr 2017
Posts: 57
cartw7 has 9 reputation points
Default

Hi, mjuluk! We noticed the same, too. I've been looking for a relevant doc over the internet, but had no such luck. How about you?
Reply With Quote
  #3  
Old 05-18-2017, 12:39 AM
shaikht shaikht is offline
Genius
.
 
Join Date: Feb 2010
Posts: 246
shaikht has 25 to 49 reputation pointsshaikht has 25 to 49 reputation pointsshaikht has 25 to 49 reputation points
Default

HI,

I will suggest to open SR with Avaya Support to look further into multiple records. There must be unique entry in each row causing multiple entries.

Regarding Incomplete, it is n indication of whether data is complete for this collection interval. Data is incomplete whenever the link goes down and whenever tracking is aborted for calls, because of the trunk going maintenance busy with a call active, protocol failures with data collection active, or when split/skill or VDN call profile is changed with data collection active. Valid values for the INCOMPLETE item are 1, which means that the data is incomplete, and 0, which means that the data is complete. The value in the daily, weekly, and monthly tables indicates the number of incomplete intervals in the day, week, or month

I hope it helps
Reply With Quote
  #4  
Old 05-20-2017, 08:34 PM
johns1224 johns1224 is offline
Brainiac
 
Join Date: Apr 2017
Posts: 56
johns1224 has 9 reputation points
Default

Thanks for your help, shaikht! This happened to us as well. Will try your suggestion in a while and let you know if it works.
Reply With Quote
Reply

Tags
incomplete

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 08:19 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.