CallAban Design History
At day 1, the CallAban was designed for logging of abandon and short duration calls. The VDN, TSAPI Engine, CallInfo and DB Manager were designed at that time. Avaya VDN(s) were monitored and CallInfo, abandon and short duration records were logged into MySQL database.
Later, Splunk Manager was added to log the CallInfo, abandon and short duration call records to Splunk for big data analysis. By using Splunk, we can find a lot of insights simply from the call records. For example, how long a customer waits for an agent. How many repeated calls a customer contact the call center per day.
In call center, call statistics such as ASA, ACHT and LWT are very important for call center management. Therefore, a Moving Stat and Scheduler were introduced to measure the statistics figures based on the call records.
In some call centers, they want to know immediately the caller information for abandon or short duration calls. They want to integrate their ticketing systems with these information, therefore Email Manager was introduced for email integration with these ticketing systems.
For call centers that do not have CMS or BCMS, CallAban is the right choice for reporting and real time data. Report Agent and Real-time Report were designed for extraction of real time data. This page mentioned that we can simulate CMS Split Skill Status report by using CallAban.
I am planning to add a module to simulate and generate CMS historical interval reports, an Interval Stat module will be designed. This module will save interval such as 15 minutes or 30 minutes interval reports to database or Splunk. I target to have it ready for testing by Q1 2016.