Com.X Administrator Guide
Page 176
Log level
Description
debug
Source code level debug reports. Enabling this level results in a large
volume of logging data.
notice
Informative messages that report on system, channel, span and call
state.
warning
Informational messages requiring attention and evaluation. Warnings
may indiacte conditions that may limit or in future potentially impede
functionality.
error
Error reports indicating items that should be addresses should system
functionality be affected.
verbose
Additional informational messages (similar to notices), allowing more
effective call tracing.
Table 47: Logging levels
Logging takes place on the CLI as well as to
/var/log/asterisk/messages.
From the Com.X GUI, two levels of detail can be selected, namely “brief” or
“verbose”. These may be accessed using Monitor -> Asterisk -> Set log level
<Brief/Verbose>
5.3 Call Detail Records (CDR)
5.3.1 Reviewing Call Detail Records
The Com.X records call detail records for all calls. To access these records, select
“Call Log” from the Reports menu. Specify the period for which records should be
retrieved and select “Search”.
Figure 98: Call record search options
For each record, the date, channel, call source, caller ID, destination, the disposition
and duration of the call is logged.An additional UUID field is provided for each call,
containing the unique identifier, or a recording of the call, if one exists.
Note: If the outbound CID on a trunk has been configured with an override (or as
'hidden'), the override CID will be stored in the caller ID field, not the original CID, as
well as in the Source field (empty if the override is 'hidden').
If the extension number or a specific account code should rather be stored in the
CDR when the trunk CID has been over-ridden, configure the “Account code” field
©2010 –
2016
Far South Networks
