Noprint | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
Section | |
---|---|
Column | |
Panel | |
In this section:
|
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.
...
Use following CLI syntax to configure call trace filters:
Code Block | ||||
---|---|---|---|---|
| ||||
% set global callTrace
callFilter <callFilter_name>
callTraceTimer <1-360>
errorFilter errorType <any | earlyAttempt | none | outOfDialog | parseError>
maxTriggerCount <0-64>
signalingPacketCapture devices <mgmt0 | mgmt1 | pkt0 | pkt1 | pkt2 | pkt3> <VLAN tag> |
Code Block | ||
---|---|---|
| ||
% set global callTrace callFilter <callFilter_name> callDetailCapture <disable|enable> callDetailCapture <disable|enable> key <called | calling | cddn | contractor | peerIpAddress | redirecting | transferCapability | trunkGroup> level <level1 | level2 | level3 | level4> match called <string> calling <string> cddn <string> contractor <string> peerIpAddress <IP address> redirecting <string> transferCapability <audio31Khz | speech | unrestricted | unrestrictedWithTones | video> trunkGroup <trunkGroup_name> mediaPacketCapture <disable|enable> state <disabled|enabled> stopMatch <supported | unsupported> callTraceTimer <1-360> errorFilter errorType <any | earlyAttempt | none | outOfDialog | parseError> maxTriggerCount <0-64> signalingPacketCapture devices <mgmt0 | mgmt1 | pkt0 | pkt1 | pkt2 | pkt3> <VLAN tag> |
Note |
---|
The default value for vlanTag is "0". If you want to configure VLAN and capture the packets on a specific VLAN, you must provide the devices name and the vlanTag value. |
...
Code Block | ||
---|---|---|
| ||
% set global callTrace signalingPacketCapture state <enable | disable> |
Caption | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
Caption | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Parameter | Description |
---|---|
callDetailCapture | Specifies whether the call details are captured or not. |
...
The files |
...
are saved as ".out" files.
|
key |
...
Choose one or more active key components for this filter |
...
:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
level |
...
The trace level of this call trace entry.
| |||
match |
...
Use this keyword to specify criteria to use to capture call data upon a match. Options are:
|
...
| ||
mediaPacketCapture |
...
Specifies whether to enable or disable media packet capture settings. These files will be stored as ".pkt"files.
| |||||||
state |
...
Administrative state of this filter:
| |
|
...
Use this flag to stop matching filter profiles once a match is found:
|
...
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:
...
mgmt0
mgmt1
pkt0
pkt1
pkt2
pkt3
...
|
To enable call tracing based on the called number:
...