callhistory.log documentation

[etsik]

Is there any documentation on the structure of callhistory.log file?

 

[nb]

Hi

What version are you using?

we did not do any documentation because we are still adding extra information. This will be 100% complete when we release the new call reporter.

Why do you need the documentation? You need to analyze the calls? Because we are going to have a process that does this.

 

[etsik]

I use 07.4744 paid.
I want to load the call data directly to my application. I do not see the reason to go through loading the calls to callhistory2 in your DB and having to aquire it from there.
Is there another way to do that?

Thanks

 

[nb]

Hi

I understand your situation.

I will give you a very brief overview just to give you a quick idea of a quick sample call. It is quite complex to explain it all because there are many fields now and we are still adding as we go along. So probably if I explain further than this, the information here will be outdated by the time 7.1 is out. However with the next release of 7.1 you will get exactly what you want with CDR.
example:
1 call from extension 116 to 112 will log these entries in the log

1,20090114145329.036,75415f048378ee48,116,112,116,112,1
3,20090114145329.036,75415f048378ee48,116,,116,,1
3,20090114145329.052,75415f048378ee48,112,,116,112,1
2,20090114145330.144,75415f048378ee48,116,112,116,112,1
4,20090114145331.626,75415f048378ee48,112,,112,,1
4,20090114145331.626,75415f048378ee48,116,,116,,1
6,20090114145331.782,75415f048378ee48,,,,,

There are 8 columns in the first row,
C1 = these represent the events of each call as the call proceeds - these can be:

Connecting = 1,
CallEstablished = 2,
PartyAdded = 3,
PartyRemoved = 4,
PartyChanged = 5,
Disconnected = 6,
DestNoAnswer = 7,
DestIsBusy = 8,
DestNotAvail = 9

C2 timestamp
C3 Call ID
C4 C6 Source numbers
C5 C7 Destination numbers
C8 1=voice 0=fax type of call

Also keep in mind that this is a simple call from extension to extension. The complexity of this is proportional to the complexity of the call you are making increasing call information as you go along. Hope this helps a bit understand the records.

 

[mbaltus]

We have a lot of users using the MakeCall HTTP API call. When we use that, the Call Reporter shows from MAKECALL to extension of the user. In this case we would like to see from extension to destination.

This applies to 7.0 Access app, new v7.1 seperate app and CDR. From the CDR in the end you can manage to gather the detail records, but for 2000+ calls a day this is somewhat more difficult. I would be nice if it would show the correct to and from numbers (and perhaps Makecall as a status code).

 

[nb]

Point taken on Make call.

 

[nb]

Hi Etsik

I use 07.4744 paid.
I want to load the call data directly to my application. I do not see the reason to go through loading the calls to callhistory2 in your DB and having to aquire it from there.
Is there another way to do that?

You can switch off automated insertion of the call history to the database - Just go to Advanced / Custom Parameters and set this to false

CALLHISTTODB = false
Then output from CDR Only.

 

[abruton]

What is the structure for Ver 6.1.0?

Andre

 

[nb]

Version 6 is completely different. Many states are missing. If you plan to develop something you have to use version 7 - with version 6 you are limited. Also your work will not be compatible for version 7 - so you will have double work to do. The easiest way is to go to Version 7.