8 April 2014, clintSVR 1.1.6 just released. This release supports CentOS 6.x 32bit OS. Moreover, this release fixed a bug that unable to login R13 and R14 issue. For details, please refer the support page.
26 March 2014, AvayaCDR 1.5.3 just released. This version supports writing CDR data to Splunk so you can use Splunk to Search CDR data and do Reporting. For details, please refer the support page.
I want to implement a front-end application for AvayaCDR. I have no plan so far because I know it is difficult to write such front-end application especially when CDR data is in customised format. I found someone using Splunk for Cisco CDR and implemented a Splunk app, this triggered me to use Splunk for my AvayaCDR program.
I plan to implement a Splunk connector. Such connector parses the incoming CDR streams, assigns each field with it’s name (when CDR fields are assigned with meaningful names, Searching and Reporting in Splunk becomes strait-forward.) and formats a new CDR record that can be recognised by Splunk. The AvayaCDR then forwards the new CDR data records to Splunk (using TCP), Splunk then performs indexing and allows users to perform Searching and Reporting. Dashboard reports for telecom charging can be created by Splunk when the new CDR data records contains charging information. Sample screen dumps attached.
Search Screen
Call Chart
Trunk Chart
4 March 2014, AvayaCDR 1.5.2 just released. This version supports CentOS 6.x and fixed a minor bug in the license key parsing function. If you are using AvayaCDR 1.5.1 Windows version, no need to upgrade. For details, please refer the support page.
28 February 2014, clintSVR 1.1.5 just released. This release supports Trunk Group Report and Event Count Summary reports. Moreover, XMPP connection is supported so you can connect clintSVR to XMPP server such as Openfire. For details, please refer the support page.
I forgot to link this program with static library. Some users may not run the program if they do not have the right library. If you encounter this problem, please use this one. I will include this file to my projects when they are released in the future.
I want to publish CMS data to Internet and enable users to use iPhone or Android devices to access the real time reports. To get real time data from clintSVR is easy, but the difficult part to me is to write an iPhone or Android application. I implemented an XMPP library before and I just thinking if I can use the library to write a bot module which allows XMPP clients to get the CMS data. I will write this module and include it in the next release of clintSVR. I did a prototype like this
12 February 2014, AvayaCDR 1.5.1 just released. This version supports Avaya Reliable Session Protocol and fixed a bug that Date Record followed with a valid cdr string is not written into database, file logging without problem by this bug.
I finally found the protocol design document. It is in the rdtt package. I plan to add the support of Reliable Session Protocol in the AvayaCDR. The code is under testing and I think the release by end of February.
6 February 2014 AvayaCDR 1.5.0 just released. This version supports charge information logging, a new table tChargeRate is provided for definition of patter and charge rate. From now on, the logging of CDR data to remote database is a licensed item, you can subscribe the 1-Year Email Support Service to get a permanent license key. The cost is only USD 100. Please keep using old version of AvayaCDR if new feature is not required. For detail information, please refer the support page.
UPINGET 