Format

A template file is a set of instructions telling the system how to extract the necessary information from the data sent from your telephone system. A sample template is shown here to demonstrate its use.

The file consists of a [Type] and [Options] section required to pre-process the data before it is usable, and a [CallTypes] section which holds the information necessary to extract the call record components from the raw data.

[Type] Section

This describes how the information is presented to the software. Possible options are described below:

[Options] Section

This section contains the settings necessary to determine what data pre-processing is required - if any- before the individual call record elements can be extracted. Possible options are described below:

[CallTypes] Section

This section contains information about how the system identifies each line of call logging data, in terms of its call type, e.g. outgoing, incoming, etc, and how to extract the call record elements from the each line. Each call type is being assigned a code, which is then used to identify each line of data with a particular type of call.

Each type of call consists of three lines of data, as shown below:

First line

Second line

Third line

The third line contains the code associated with the type of call. These call type numbers are internally used to identify the call type, as follows:

A template file is a set of instructions telling the system how to extract the necessary information from the data that is sent from your PABX (or PABXs).

A sample template is shown here to demonstrate its use. This example is not a complete template and should not be used:

The file consists of a Type, any Options required to pre-process the data before it is useable, and a CallTypes section which holds the information necessary to extract the various call record components from the raw data.

[Type] Section

This describes how the information is presented to the software. This can be one of the following:

[Options] Section

This section contains the various settings to determine what (if any) pre-processing of the raw data is necessary before the individual call record elements can be extracted. Possible options are as follows:

[CallTypes] Section

This section contains descriptions for each type of call - eg. outgoing, incoming answered, incoming abandoned, etc. - including what that type of call 'looks' like (how the system identifies a line of PBX data as such), how to extract the call record elements from the line, and finally a code that pertains to the particular type of call.

Each type of call consists of three lines (excluding comments), for example:

The first line (##-???-## ##:##:##) is the match line, which tells the system how to match this particular call type. The # symbol indicates any digit between 0 and 9, and a ? symbol indicates any character including letters and numbers. The * symbol at the end of the line is important if there may be other data attached to the line that you're not interested in. The * indicates that anything else on the line does not matter.

The second line (aa bbb cc dd ee ff) tells the system how to extract each call record element from the line of data. In this example, the aa spans the first two characters of the data line meaning that the call date's day should be taken from here; bbb spans three characters starting at column 4 showing where the month is taken from, and so on.

The third line represents the number associated with the type of call. These call type numbers are internally used to identify types of calls and are summarised as follows: