Unable to get not ready reason codes through cachedb (avaya aura contact center)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • avc869434885302
    Aspiring Member
    • Aug 2024
    • 2

    Unable to get not ready reason codes through cachedb (avaya aura contact center)

    Hello I am developing a reporting dashboard for my client which displays state changes of agent in contact center. Client wants the dashboard to reflect changes with minimum delay. Right now I am able to access client's cache database through odbc.
    I am able to pull ready, not ready, logged in, ... state changes through eAgentLoginStat table. According to documentation here (https://support.avaya.com/css/public...ents/101059033), it should update every 3 minutes.

    However there is no information about not ready status code in this table. Now I am trying to find something similar for not ready reason codes, which can give me reason codes with around same delay of 3 minutes.
    There is another eActivityCodeStat table which has the information about time agent spent in given status in every 15 minutes interval.
    But there are 2 issues here,
    1. Is there a way to get not ready status code updates at higher frequency (like 3 minutes with eAgentLoginStat table).
    2. Is there a way to get not ready status code updates along with their respective timestamps when agent went into not ready status with that particular reason code.
  • oconnor22
    Member
    .
    • Jun 2024
    • 4

    #2
    1: The minimum Data Collection interval is 15minutes as this is the interval written to the database see screenshot below.

    AACC CCMA->Launchpad0>Configuration->CCMS->Real-time Statistics.

    Click image for larger version

Name:	RealTimeStat.jpg
Views:	61
Size:	16.3 KB
ID:	48458
    2: If you want Real Time Data , e.g time in not ready status . It might be worth looking at the RTDSDK. RTdView.exe is a useful demo of what's available here.
    Not Ready State, Time in State and Not Ready Reason Codes are available here.


    I would suggest logging a DevConnect Technical ticket if you need further help with this sdk.
    Attached Files

    Comment

    • avc869434885302
      Aspiring Member
      • Aug 2024
      • 2

      #3
      Thank you oconnor22 for the quick reply.

      Looking at the documentation, I was under the impression that all event based stats are written every 3 mins.
      Also regarding RTDSDK, I have a restriction that I cant deploy any application in client's environment and my application has to connect to client's environment through private tunnel.
      As mentioned here (https://support.avaya.com/css/public...ents/101090671), for real time interface to work I will have to use rmi and multicast in my java application.
      I am trying to avoid using this as there can be multiple complexity running rmi and multicast over private tunnel and I already have access to cachedb.
      Anyways as you have suggested let me raise a technical ticket with devconnect.


      Click image for larger version

Name:	image.png
Views:	64
Size:	60.5 KB
ID:	48467

      Comment

      • oconnor22
        Member
        .
        • Jun 2024
        • 4

        #4
        Just a Note on the above image "Event Statistics".
        Events is collected every 3 minutes as described in chapter 7.
        But the data collected as events is limited to the views: starting with the letter "e" in the namespace "CCMS_STAT" and is not as detailed as the Historical data written every 15 minutes.


        Comment

        Loading