I’ve been involved with Asterisk since 2006. In 2007 my husband and I started an Asterisk integration shop in Croatia. We cater to small businesses, because we are small.

Some of our clients that have small call centers needed a reporting solution. Also some of our other clients expressed a need to see more information about their call traffic. After some consideration I decided to build it using Delphi. I wanted something easy to install, with no maintenance and no pre-install software requirements. It was not meant to be “All-In-One” solution that does configuration, monitoring, click-to-dial, provisioning, etc. Neither was it meant to be a real-time reporting.

It was envisioned to do just one thing, show the call records, for both queues and CDRs, without presuming anything about the underlying system. The main goal of the application is to  leverage what is already there in your Asterisk box, thus it operates on log files and not the database that you might have installed, or not.

The goal is also to show the information, as opposed to data, in an orderly and easily understood format. To be able to see multiple information displayed at once without any noise (information overload). Ease of use was also high on my list, therefore I opted for a “drag and drop” approach.

The application is currently used by the two of my clients. (Beta is about to start in 9 days) It was important to make it as simple as possible for them to update their reports when needed. Therefore I included a small SFTP client. Introducing the end users with  WinSCP would complicate things too much for them. It’s much easier to click on the “Transfer files” icon from within the application.

SAM Reports is aimed at small businesses using Asterisk.  I built it to solve the pain that I had : provide my clients, small businesses, with a reporting solution without the need to make any changes to their Asterisk boxes. And also to give them reporting that’s easy for them to use. I wanted to be able to offer it to both my call-center clients and those without, therefore the application handles both CDRs and queues.

This is a short overview of why we did SAM Reports and how. I’ll be posting here on the development process (changes, what features are planned, what’s coming). I’ll also desrcibe use-cases, real and virtual (aka, what’s possible, what might be a good use of).

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

2 Responses to “Why SAM Reports?”

  1. Adam Mathews March 10, 2010 at 3:49 pm #

    I would love to have the oppotunity to get an early look at this, I am currently working with Atcom IPPBX systems and am looking for a simple reporting solution

  2. admin March 15, 2010 at 5:51 pm #

    I tried to contact you via email, but the address is wrong. Email me if you like.

Leave a Reply

Clicky Web Analytics