Asterisk Resources Overview
Anything that is being analyzed, viewed at, by the application is considered a resource. So extensions (channels) local to your PBX are the resources. Trunks that connect your PBX to the outside world are also resources. Agents in your call center, together with queues are the resources. All the people that called your PBX are the resources as well. So we might put it this way:
There are three groups of resources:
Channels And Trunks
Channels are the extensions of your Asterisk PBX. All the extensions registered at your local PBX. IAX, SIP, ZAP, etc. They let you “dial from“. Extensions, channels, are what your phone devices are connected to.
Trunks are what traditional telephony considers phones lines to be. They connect your Asterisk PBX to the world, let you “dial out“. So some SIP or IAX VoIP provider is a trunk for our Asterisk PBX. The same goes for a telephony card plugged into our Asterisk’s machine.
After you install SAM Reports, and download the log files you have to decide which of your channels are trunks, and which are extensions (plain channels). The application asks you that just once upon first parsing of your CDR data. SAM Reports tries to guess which of the channels are actually trunks, and displays a list of all channels/trunks found in your CDRs. You can then make changes, but you can do the same from this window as well.
It is useful to give your extensions a name. You can do that by assigning a contact to a channel. If you don’t have any contacts, you can create one by clicking on the “New Contact For Channel” button. For example Mary who always uses the extension 101 may be associated with SIP/101 channel (if that’s a SIP device in deed). And the phone that sits in you office’s kitchen may be given a contact named “The Kitchen”.
You can print channels and trunks. When you do The Print Preview Window appears, which looks the same for all the data across the application.
Agents And Queues
Here you can see all your agents and queues as well as their relations. Like in what queues does agent Keila Bortle participate, or which agents are in a queue “Sales”… SAM Reports does not ask YOU those questions, but informs you of what it found out while parsing a queue log.
You cannot add new agents or delete them, you can just assign a contact to an agent to make the reports more meaningful. Reports are more readable if you add a description for your queues.
Yo can see all the relationships between queues and agents. Which agents are in which queues, and vice versa.
Distribution Of Queues By Agent
Distribution Of Agents By Queue
Contact (Caller-ID) Resources
Contact resources are made from the caller-id information found in the CDR and queue log files. This window lets you match those phone numbers with real names.
As you can see on the image above, company names are just gibberish. I needed to protect the real company names from appearing on this image.
Matching caller-id data with contact names
The caller-id data in question is called by the application “The Unknown Phone Numbers”. To match the unknown phone numbers with the appropriate contact names you have to do one of the things mentioned below:
- Assign the unknown number to one of the existing contacts.
- Create a new contact and do the same.
- Assign multiple unknown numbers to contacts.
Assign the unknown number to one of the existing contacts
Just choose an unknown number and assign it to the currently selected contact by clicking on a tool button.
Assign multiple unknown numbers to contacts
To be able to automate the process you first have to export the caller-ids. Then generate a text file of a specific structure that SAM Reports understands. At the end you just choose the “Import Unknown Numbers” command from the ribbon.
The process:
- Export unknown numbers
- Generate a text file with contact information
- Import that text file into SAM Reports
Export unknown numbers
To do that you just choose “Export Unknown numbers” command.
Generate a text file with contact information
You have to generate this file yourself, SAM Reports just processes it.The text file has to be a CSV (Comma Separated Values). It is advisable for it to be an UTF8 unicode document, if you do have a need for special characters. For each unknown number (caller-id) that was exported (above), the file has to contain the following five values: country code, local prefix, phone number, contact name and the original caller-id (the unknown number). All values have to be double-quoted and separated with commas “,”. Individual lines (contacts) have to be separated by CR-LF combo, which is a standard Windows-style line breaking.
Here’s the structure of one line:
- “Country Code”,
- “Local Prefix”,
- “Just the phone part”,
- “Name”,
- “caller-ID”
Import Unknown Numbers
Now that you have a text file with contact information matched to the unknown numbers, you can import it into SAM Contacts. Just click on that command in the ribbon.
One possible scenario:










