...
Call Trace Filtering
The global Call Trace command allows you to create and configure Call Trace Filters using criteria to determine call events added to the system trace data event log (which uses the ".TRC" file extension). The first three Call Trace filters are logged unless the stopMatch
flag in enabled (whereby the number of filters logged may be less than three). The stopMatch
flag will halt filter profile matching once a match is found.
...
Note |
---|
This command is only exposed after callTrace configuration is performed. If no entries are present in the callTrace, this command is not available from CLI. |
Use following CLI syntax to configure call trace filters:
...
Code Block |
---|
|
% set global callTrace signalingPacketCapture state <enable | disable> |
Command Parameters
Caption |
---|
0 | Table |
---|
1 | Global Call Trace Parameters |
---|
|
Parameter | Length/Range | Description |
---|
callFilter
| 1-23 | The name of a call trace filter to apply to the system trace data log file. This filter may be created, configured, and deleted. | callTraceTimer | 1-360 | Duration in minutes that call trace is enabled. (default = 180) | errorFilter
| N/A | Call error trace for SIP Call Traces only. errorType – Type of error to log:any – Log all SIP PDUs that meet the requirement of the parseerror, outofdialog, and early attempt options below.earlyattempt – Logs incoming SIP PDUs that result in early termination of the call (by either the pre-parser or SIP signaling).none – (default) No SIP PDU logging, including validation/parsing errors.outofdialog – Log incoming syntactically correct SIP PDUs (except INVITE) that do not belong to an existing dialog.parsError – Log received SIP PDUs that fail parsing. If an error is detected by SIP signaling, the accompanying PDUs is not associated with any dialog, including an existing dialog. Hence all in dialog and out of dialog PDUs are assigned to this category. If an error is detected at the front end pre-parser, the PDU is logged and not forwarded to SIP signaling to prevent logging an offending PDU by both the pre-parser and SIP signaling.
| maxTriggerCount
| 0-64 | Maximum number of calls that match the callFilter criteria and the errorFilter type that may be logged to the .TRC file, per slot. When this limit is reached on a module in a particular slot, this parameter value becomes 0 and matching events are no longer logged. To re-enable logging, you must issue a CLI command that configures this parameter to a nonzero value (default = 0). | signalingPacketCapture
| N/A | Specifies the signaling packet capture devices and the admin state. These files are saved as .pkt files. The options are: devices – List of devices for signaling packet capture. The options are:-
mgmt0 mgmt1 pkt0 pkt1 pkt2 pkt3
<VLAN tag> – Enter VLAN tag of the device used for signaling capture (or enter "0" for no VLAN).
|
|
Command Examples
To enable call tracing based on the called number:
...
Code Block |
---|
|
% Set global callTrace signalingPacketCapture state enable |
Offline Call Trace Analysis Using LX Utility
Excerpt Include |
---|
| Media Capture and Call Trace |
---|
| Media Capture and Call Trace |
---|
nopanel | true |
---|
|