TeleBoss 850 2.06.280_STD User Manual
Page 143
Configuration File
The record retrieving functionality is configured via a configuration file. This configuration file is a list of setting keys,
where a setting key is a "<setting> = <value>" statement. <setting> is a period-delimited string of keywords. These
keys can name all of the setup variables of the product. These include the generic operational parameters of the box
such as these below, as well as specialized parameters such as those for the Cisco CallManager:
net.ip=192.168.100.32
net.subnet=255.255.255.0
net.router=192.168.100.100
net.snmp[1]=192.168.100.36
net.snmp[2]=0.0.0.0
net.snmpcomm=public
The unit queries the CallManager database and, for each available record, retrieves the values (columns) specified in
the field table. The retrieved values are assembled into records as defined in the field table. Using this method we
can specify output fields using the specific database column numbers (shown in the tables below), or by specifying the
exact name of the database column.
Values can be retrieved from two CallManager tables: CallDetailRecord (CDR), and CallDetailRecordDiagnostic
(CMR). When CMR values are specified, values are retrieved only from CMR records that are related to CDR records
included in the query. When specifying fields, each field name/number is prefixed by "cdr." or "cmr." depending on
which table the field is coming from.
For example, if the user wants to create an output record which contains these fields:
cdr.dateTimeDisconnect, cdr.originalCalledPartyNumber, cdr.finalCalledPartyNumber, cdr.dateTimeOrigination
(converted to MM/DD/YYYY HH:MM:SS format), cdr.origIPAddr (converted to 4-dot notation), cdr.duration, cmr.jitter,
and cmr.latency, and the user wants to specify the fields using COLUMN NUMBERS, the field setup would look like
this:
iprc.field[1]=cdr.38,10,R // Date/time disconnect (integer format)
iprc.field[2]=cdr.26,25,R // Original called party number
iprc.field[3]=cdr.28,25,R // Final called party number
iprc.field[4]=cdr.5,17,R,NTOD // Date/time origination (date/time format)
iprc.field[5]=cdr.10,15,R,NTOIP // Orig IP address (4-dot notation)
iprc.field[6]=cdr.39,10,R // Duration
iprc.field[7]=cmr.13,10,R // Jitter
iprc.field[8]=cmr.14,10,R,0D0A // Latency
In the above, the field definition arguments are:
<field>=<column# , length of that value to take, justification[,end of line chars][,conversion]>
If the specified length is greater than the length of the returned value, then the returned value is padded with spaces
and justified within the output field based on the justification specification. 'L' means the value is left-aligned, 'R' means
the value is right-aligned, and 'N' means the output field retains the size of the returned value and is not padded with
spaces.
The 0D0A terminator on field 8 tells the unit to append CRLF to the end of that field. Note that in this example the
0D0A optional value places the end-of-line characters on the last field, but you could include the EOL characters at
other fields also so as to break the record into multiple lines. If the final field definition does not have any EOL
characters specified, then the unit appends CRLF automatically.
If we wanted to use explicit column names (if, for example, a column is desired that is not in the COLUMN NUMBER
table), the setup would look like this:
Содержание Teleboss 850
Страница 6: ......
