Page History
| Panel | |
|---|---|
In this section:
|
Call Trace Filtering
| Multiexcerpt include | ||||
|---|---|---|---|---|
|
The maxTriggerCount parameter is used to set/reset the Trigger Count, a mechanism used to limit the logging of call/error filter events in the .TRC file.
| Info | ||
|---|---|---|
| ||
A system reboot, an application restart or a Live Software Upgrade (LSWU) causes the following call trace filters to go offline:
|
To rectify this, disable and then reenable the applicable filters using the following CLI command syntax:
| Code Block | ||
|---|---|---|
| ||
% set global callTrace signalingPacketCapture state disable % set global callTrace signalingPacketCapture state enable % set global callTrace callFilter <filterName> state disabled % set global callTrace callFilter <filterName> state enabled % set global callTrace callFilter <filterName> mediaPacketCapture disable % set global callTrace callFilter <filterName> mediaPacketCapture enable % set global callTrace callFilter <filterName> callDetailCapture disable % set global callTrace callFilter <filterName> callDetailCapture enable |
| Info | ||
|---|---|---|
| ||
As a general rule, set Call Trace to ingress mode unless egress mode is mandatory. |
| Warning | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Do not turn on the Call Trace Filter to trace all calls. Use of the Call Trace feature can have significant impact on the network performance of the
|
Use the following criteria to establish a Call Trace Filter:
- Called Party Number
- Calling Party Number
- Contractor Number
- Peer IP Address
- Redirecting Number
- Transfer Capability
- Trunk Group
Use the match keyword to specify criteria to use to capture call data upon a match. Use the key keyword to specify criteria on which to filter call data.
Call events captured are:
- Call attempt
- Lookup request sent
- Lookup request received
- Alerting received
- Cut-through received
- Call Answer received
- Cut-through complete
- Service established
- Disconnect Request received
- Call terminated
- Wait for more digits
- Extra digits receiveda
- Initiating new attempt
- Signal messages received or sent
- Egress call setup message
- Route lookup failure
- Call blocked
- Policy Request
- Policy Response
- Policy processing of calls in different layers like pre-processor, services, pre-router, router, and post-router.
- SIP signaling events for a single call incoming/outgoing to a particular source/destination IP endpoint
- SIP Protocol Data Units (PDUs) for a single call incoming/outgoing from/to a particular source/destination IP endpoint
- SIP out-of-dialog PDUs such as 18X, BYE, and INFO, regardless of whether they are successfully parsed
The TRC event log level must be info for this facility to operate properly.
Use the maxTriggerCount parameter to limit the logging of call/error filter events in the .TRC file. After configuring and enabling the callFilter, an ingress/egress call that matches the filter criteria causes the corresponding events to be logged to the .TRC file, as long as the Trigger Count has not been reached. Once the configured Trigger Count has been reached, the matching callFilter will not be triggered and events associated with the call trace filter will not be logged in the .TRC file. To reenable triggering, you must configure the Trigger Count to a non-zero value less than 65.
Once the maxTriggerCount is reached or callTraceTimer expires, the call trace stops. To restart the call trace without changing the callTrace configuration, use following CLI command:
| Code Block | ||
|---|---|---|
| ||
% request global callTrace action command start |
| Info | ||
|---|---|---|
| ||
This command is only exposed after callTrace configuration is established. If no entries are present in the callTrace, this command is not available from CLI. |
Command Syntax
Use following CLI syntax to configure call trace filters:
Global Call Trace Syntax
| 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> filter <signaling trace filter name> signalingPacketCaptureTimer <0-360 seconds> state <disable | enable> |
Call Filter Syntax
| Code Block | ||
|---|---|---|
| ||
% set global callTrace callFilter <callFilter_name> 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> |
| Info | ||
|---|---|---|
| ||
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. |
To configure signaling state:
| Code Block | ||
|---|---|---|
| ||
% set global callTrace signalingPacketCapture state <enable | disable> |
Command Parameters
Global Call Trace Parameters
| Caption | ||||
|---|---|---|---|---|
| ||||
Parameter | Length/Range | Description | ||||||
|---|---|---|---|---|---|---|---|---|
| 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. See Call Filter Parameters table below for details. | ||||||
callTraceTimer | 1-360 | Duration in minutes that call trace is enabled. (default = 180) | ||||||
| N/A | Use this object to specify the system-wide call trace error filter trigger criteria.
| ||||||
| 0-64 | Maximum number of calls that match the (default = 0) | ||||||
| N/A | Signaling Packet Capture configuration.
|
Call Filter Parameters
| 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:
|
Command Examples
To enable call tracing based on the called number:
| Code Block | ||
|---|---|---|
| ||
% set global callTrace callFilter CF-1 level level1 state enabled key called,calling match called 978% % set global callTrace callFilter CF-1 mediaPacketCapture enable % set global callTrace callFilter CF-1 callDetailCapture enable |
To view the recently-enabled call trace filter:
| Code Block | ||
|---|---|---|
| ||
% show table global callTrace callFilter
callFilter CF-1 {
state enabled;
level level1;
key called,calling;
match {
called 978%;
}
mediaPacketCapture enable;
callDetailCapture enable; |
To enable signaling packet capture:
| Code Block | ||
|---|---|---|
| ||
% Set global callTrace signalingPacketCapture state enable |
Offline Call Trace Analysis Using LX Utility
| Multiexcerpt include | ||||
|---|---|---|---|---|
|
| Pagebreak |
|---|
Overview
Content Tools