...
| Caption |
|---|
| 0 | Table |
|---|
| 1 | Call Trace Status and Settings parameters |
|---|
|
| |
| Anchor |
|---|
| Call Trace Error Types |
|---|
| Call Trace Error Types |
|---|
|
Parameter | Description |
|---|
Call Trace Duration | Specifies the duration for the Call Trace to run on the selected filter. The options are: Run trace until stopped (by clicking the Stop Trace button): If selected, the trace will keep running till it is stopped manually (by clicking the Stop Trace button).
Stop trace after __ minutes: If selected, add the number of minutes for the Call Trace to run. The value ranges from 1 to 360 minutes and the default value is 360 minutes.
|
Number of Matches (optional) | Specifies the number of times the Call Filter criteria should match before stopping the trace. The value ranges from 1 to 64 times. |
Trace Calls with errors of the type | Use this object to specify the system-wide call trace error filter trigger criteria. none (default)—No SIP PDU logging for this error filter.Any—Log all SIP PDUs that meet the requirement of the Parse Error, Out of Dialog, and Early Attempt options below.Parse Error—Log received SIP PDUs that fail parsing. If an error is detected by SIP signaling, the accompanying PDUs will not be 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 by this software and not forwarded to SIP signaling. This prevents an offending PDU from being logged by both the pre-parser and SIP signaling.Out of Dialog—Log incoming syntactically correct SIP PDUs (except INVITE) that do not belong to an existing dialog.Early Attempt—Logs incoming SIP PDUs that result in early termination of the call (by either the pre-parser or SIP signaling).
| Include Page |
|---|
| Call_Trace_ErrorFilter_Note |
|---|
| Call_Trace_ErrorFilter_Note |
|---|
|
For further details on error logs, see the section Call Trace Log Messages. |
Call Trace Status | Displays the current status of the Call Trace. - When there are no trace running, the application states Call trace stopped with a red dot.
- when a trace is running, the application states Call trace running with a green dot.
|
...
Once the trace is complete, the logs are generated and stored at Log Management. Look for TRC and PKT log files (.trc and .pkt log files). For more details on log messages, see the section Call Trace Log Messages.
| Anchor |
|---|
| Log Message Facts |
|---|
| Log Message Facts |
|---|
|
Call Trace Log Messages| Include Page |
|---|
| Notes_and_Examples_on_Call_Trace_Log_Message |
|---|
| Notes_and_Examples_on_Call_Trace_Log_Message |
|---|
|
Offline Call Trace Analysis Using LX Utility
| Excerpt Include |
|---|
| Media Capture and Call Trace |
|---|
| Media Capture and Call Trace |
|---|
| nopanel | true |
|---|
|
The Call Trace Filter