Archive for the ‘TSAPI’ Category

CallAnalytics 2.1.2 Released

Posted: June 12, 2022 in News, TSAPI

CallAnalytics 2.1.2 just released, this version has the following updates.

1. Keep the call state for the hold call and active call during call transfer before log the details to database and Splunk.
2. Update the hold duration for hold call of the transfer call.
3. Update the releasing device for the active call of the transfer call.
4. Supports 64bit Windows and CentOS/RedHat versions
5. The qacdsplit, qtrunkgroup, callaban, callqueue, callanswer and shortduration APIs supports multiple object that delimiter by “;”.
6. The splitskillstatus API with additional fields such as agentsacdin, agentsacw, agentsaux, AUX0-AUX9 total.
7. The listagent API with additional fields AUX0-AUX9 total.
8. The vdnreport API supports mulltiple object that delimiter by “;”.
9. The vdnreport is.interval field is wrongly use the moving average interval and it is fixed.
10. Creation of callaban json file for integration with other systems.
11. Transfer call from VDN call, the first transferring call will be counted as ended. The second call will not be counted in the VDN.
12. Supports ca_privatedataversion, ca_ueventworkersize and ca_ueventbuffersize parameters.

CallAnalytics can integrate with Grafana now! We can produce useful dashobards for Avaya call center by the integration. Traditionally, you cannot see which customer is waiting in queue, which one is abandoned and which one is disconnected right after an agent is connected using standard Avaya reports. Now you can see them in the Grafana. Here is the screen. You can contact service@upinget.com for more information.

CallAnalytics 2.1.1 Released

Posted: March 20, 2022 in News, TSAPI

CallAnalytics 2.1.1 just released, this version has the following updates.

1. Add fields extension, origextension, origagentid, origvdn and origsplit to splunk events.
2. Fixed the callinfoext without endtime for transfer call.
3. Add fields extension, origextension, origagentid, origvdn, type (vdn/extension) and map (active/cache) in the REST callinfo response message.
4. Supports SQLite as the configuration database.
5. Supports cacti interface for API CTI functions and events notification integration.
6. Supports caws interface for WebSocket CTI functions and events notification.
7. Supports callinfo API searching from the cache map.

Simple WFH Solution

Posted: March 15, 2022 in TSAPI

If you are using old Avaya CM that you can’t use IP softphones for your home agents, you can try AutoBridge. AutoBridge is a CTI module that monitors a pool of agent physical phones and conferences agent’s mobile when the any of the phones is engaging a call. Under this situation, an agent simply required a notebook / home computer, a VPN account and a mobile phone can work as a home agent. All recordings of the phones in the call center still recording by your existing solution, no big investiment to enable the WFH solution.

CallAnalytics 2.0.13 Released

Posted: October 5, 2021 in News, TSAPI

CallAnalytics 2.0.13 just released, this version has the following updates.

1. Supports cache call info so asterisk or other external system can query the call info data using UCID even agent call is transferred.
2. VDN call will look up the Extension call info to update the extension, agentid, vdn and split of the call.
3. Supports new function queryagentstates to query agent states collected by CallAnalytics.

Traditionally, we are using IVR platform to implement after call CSAT survey. This kind of solution is very expensive because of the high cost of the IVR platform and the related licenses. But we can use Asterisk as a low cost replacement solution for CSAT survey and it works for both inbound and outbound calls.

The diagram above illustrates our CSAT survey solution, it using Asterisk and integrated with Avaya by SIP trunk. Basic information such as UCID can be sent in the SIP header, the UCID can be used as a common key to link the Avaya call information. Also we can make use the dialed digits that sent from Avaya to Asterisk to carry more information for the survey.

Our solution also can integrate with Avaya CTI, more useful information such as agent id, VDN, Hunt Group numbers or application data can be stored together with the CSAT survey.

If you are interested about this solution, please contact us for more detail information.

CallAnalytics 2.0.12 Released

Posted: March 15, 2021 in News, TSAPI

CallAnalytics 2.0.12 just released, this version has the following updates.

1. The userdata in JSON format is special handled for JSON entity or simply string value.
2. Hangup user data is added to the callinfo API.
3. Fixed the segmentation fault which is caused by multiple threads accessing the tsapi event array.

AstLogger 1.4.14 Released

Posted: February 15, 2021 in News, TSAPI

AstLogger 1.4.14 just released. The updates are

1. Increase buffer size from 1024 to 4096 for bigger CSTA and Private data events.
2. Fine tune the stream checking to avoid false alarm detection.
3. Change TSAPI event notification method from acsSetESR to acsEventNotify.
4. Update the AstLogger web pages to align with DMCCLogger web pages.
5. Update the t_astcalldata with logger id field and merge the t_astappdata call data fields.
6. Display call end party on the call search web page.

Grafana is a great analytics platform, we can use Open Source Grafana to monitor Avaya Call Center. We have several tools that can integrate with Avaya via the Avaya CM, AES and CMS interfaces to get real-time and history data. This post illustrates the step by step procedure to use Grafana and these tools to produce a lot of useful real time dashboards for Avaya call center. These dashboards including

  • Real-time Trunk Report – Incoming calls of a call center firstly hit the trunks of the call center. We can use bcmsSVR to monitor the real-time trunk status. The dashboard will show how many trunk members are idle, in used or in unknown status.
  • Real-time VDN Report – Individual incoming call then reached a VDN and a vector is executing to route the call. We can use bcmsSVR to monitor the real-time VDN status. The dashboard will show number of calls waiting, number of ACD calls handled, the average talk time, etc.
  • Real-time Queue Report – The call then routed to Queue and finally delivered to an agent. We can use bcmsSVR to monitor the real-time Queue status. The dashboard will show number of calls waiting, number of agent staffed and the number of agent in different ACD status, etc.
  • Real-time KPI Report – The KPI dashboard will show the KPI performance of an specific Queue, it contains data such as Calls Waiting, Oldest Calls Waiting, ACHT and Service Level, etc.
  • Real-time Call Queue Report – To identify which customer is waiting in the queue and showing the waiting time and position of the caller is critical to improve customer service. We can use CallAnalytics to get data such as the caller, VDN, and waiting time of all customers waiting in a specific VDN.
  • Real-time Call Answer Report – This report will show all the customers who is talking to the agents for a specific VDN. We can use CallAnalytics to get data such as caller, VDN and answering time of the calls.
  • Real-time Agent Report – A Queue is a logical unit for Automatic Call Distribution. There are numerous of agents login to ACD to handle the calls. We can use the bcmsSVR to monitor the real-time Queue status. The dashboard will show all agents in the Queue and their real-time status.
  • Intra-day VDN Report – We can use bcmsSVR to get interval (24 hours / 12 hours) report of a specific VDN.
  • Intra-day Queue Report – We can use bcmsSVR to get interval (24 hours / 12 hours) report of a specific Queue.

We have successfully integrated bcmsSVR and CallAnalytics with Grafana using JSON API developed by Marcus Olsson.  Please follow the procedure to install the API. 

First, we add the JSON API as data source for different bcmsSVR and CallAnalytics API. These API include

  • bcmsSVR statustrunk JSON API
  • bcmsSVR bcmsmonitorvdn JSON API
  • bcmsSVR bcmsmonitorsplit JSON API
  • bcmsSVR bcmsmonitorsystem JSON API
  • bcmsSVR bcmslistvdn JSON API
  • bcmsSVR bcmslistsplit JSON API
  • CallAnalytics callqueue JSON API
  • CallAnalytics callanswer JSON API

Second, we add the panels one by one and the screen dump of these panel configurations as follows

  • Trunk Panel
  • VDN Panel
  • Queue Panel
  • Call Queue Panel
  • Call Answer Panel
  • KPI Panel
  • Agent Panel
  • VDN Intra-day Panel
  • Queue Intra-day Panel

The final output of the dashboard by grouping the panels together

If you are interested the integration of Grafana with Avaya, you can contact us directly. Our contact is service@upinget.com. Have fun!

ctiSVR 1.2.14 Released

Posted: January 4, 2021 in News, TSAPI

Happy New Year! ctiSVR 1.2.14 just released, this version has the following updates:

1. Supports bulk version of queryacdsplits(), querydeviceinfos() and queryagentstates() API.
2. Fixed the segmentation fault which is caused by multiphe threads accessing the tsapi event array.
3. Supports DMCC Physical Device Services and Events. New APIs getbuttoninformation(), getlampmode(), buttonpress(), getdisplay(), sethookswitchstatus(), gethookswitchstatus(),
getringerstatus(), getregistrationstate(), validatedevicesecuritycode(), changedevicesecuritycode() and getlinkstatus() are supported.
4. Supports splitskillstatus() API.
5. Supports HookswitchEvent, DisplayUpdatedEvent, RingerStatusEvent and LampModeEvent in XML and JSON formats.
6. The ivrSVR uses the LampModeEvents to enhance the determination of the agent state for the splitskillstatus() API.