Toolpack:Configuring Call Trace A
(put comment in bold) |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
{{DISPLAYTITLE:Configuring Call Trace}} | {{DISPLAYTITLE:Configuring Call Trace}} | ||
| − | Call Trace is a diagnostic | + | Call Trace is a diagnostic tool that is designed to trace the path a call takes through a Tmedia system, and to provide information about numerous aspects of the call path, such as: |
* The routing decision | * The routing decision | ||
| Line 12: | Line 12: | ||
* The termination result code, and more. | * The termination result code, and more. | ||
| − | A call path is shown as separate call legs | + | A call path is shown as separate call legs, distinguishing the incoming portion with other portions of a call. Call trace enables a default of 10,000 call legs to be stored on the system and be viewed using the Web Portal. |
| − | + | Calls may be filtered by called number, calling number, Network Access Point (NAP), time of day range, protocol and direction. | |
| − | + | <div class="mw-collapsible mw-collapsed" data-collapsetext="Enabling Call Trace" data-expandtext="Enabling Call Trace" style="width: 400px;"> | |
| − | + | '''This section only needs to be done once per system.''' | |
| + | |||
| + | 1- Go to the call trace application status | ||
| − | ''' | + | [[Image:ConfigureCallTrace_3_A.png]] |
| + | |||
| + | [[Image:ConfigureCallTrace_4_A.png]] | ||
| + | |||
| + | [[Image:ConfigureCallTrace_5_A.png]] | ||
| + | |||
| + | 2- Select '''Run''' then press '''Apply States''' | ||
| + | |||
| + | [[Image:ConfigureCallTrace_6_A.png]] | ||
| + | |||
| + | </div> | ||
| + | |||
| + | |||
| + | '''Retrieving calls:''' | ||
1- Click '''Call Trace''' in the navigation panel | 1- Click '''Call Trace''' in the navigation panel | ||
| Line 39: | Line 54: | ||
Once you are satisfied with the filter criteria, click '''Apply''' | Once you are satisfied with the filter criteria, click '''Apply''' | ||
| − | The filter results are displayed | + | |
| + | The filter results are displayed. | ||
3-Select a call in the results window to display further information about the call. | 3-Select a call in the results window to display further information about the call. | ||
| Line 47: | Line 63: | ||
| + | <div class="mw-collapsible mw-collapsed" data-collapsetext="To search for calls that are no longer in memory, do the following:" data-expandtext="Searching for calls that are no longer in memory" style="width: 400px;"> | ||
| + | By default, the system stores up to 10,000 call legs in memory. If the call is no longer in memory, it may be retrieved by using information from the uctdata log files. | ||
| − | + | By default the file is located in the following path: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<pre>/lib/tb/toolpack/setup/12358/2.6/apps/tbuctwriter/uctdata*</pre> | <pre>/lib/tb/toolpack/setup/12358/2.6/apps/tbuctwriter/uctdata*</pre> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | To | + | 1- Start [[How_to_use_tbx_cli_tools_remote_program|tbx_cli_tools_remote]] |
| + | 2- Select tbuctwriter | ||
| + | 3- To know which files are available, as well as the start and end time of each file, use the following options: | ||
| + | * 'p' to print all uctdata files on disk | ||
| − | *Option 'o' | + | To load a file into memory for viewing with the Web Portal: <br> |
| + | * Option 'o' followed by the data filename (uctdata*) | ||
| − | + | Use the Web Portal to search for calls using the appropriate filter criteria. The memory will not be overwritten until you restore normal process. | |
To restore normal process:<br> | To restore normal process:<br> | ||
Latest revision as of 15:46, 10 December 2012
Applies to version v2.6
Call Trace is a diagnostic tool that is designed to trace the path a call takes through a Tmedia system, and to provide information about numerous aspects of the call path, such as:
- The routing decision
- The outgoing call
- Subsequent outgoing calls, in the case of a route retry
- Parameters selected for a SIP SDP
- The SIP Call-id
- The trunk and timeslot chosen for TDM protocols
- The termination result code, and more.
A call path is shown as separate call legs, distinguishing the incoming portion with other portions of a call. Call trace enables a default of 10,000 call legs to be stored on the system and be viewed using the Web Portal.
Calls may be filtered by called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.
This section only needs to be done once per system.
1- Go to the call trace application status
2- Select Run then press Apply States
Retrieving calls:
1- Click Call Trace in the navigation panel
2- Set various parameters for the call trace, such as
- Time and date range
- Called or calling number
- Network Access Point (NAP)
- Incoming or outgoing calls
- Call Duration, Reason Code
Once you are satisfied with the filter criteria, click Apply
The filter results are displayed.
3-Select a call in the results window to display further information about the call.
By default, the system stores up to 10,000 call legs in memory. If the call is no longer in memory, it may be retrieved by using information from the uctdata log files.
By default the file is located in the following path:
/lib/tb/toolpack/setup/12358/2.6/apps/tbuctwriter/uctdata*
1- Start tbx_cli_tools_remote 2- Select tbuctwriter 3- To know which files are available, as well as the start and end time of each file, use the following options:
- 'p' to print all uctdata files on disk
To load a file into memory for viewing with the Web Portal:
- Option 'o' followed by the data filename (uctdata*)
Use the Web Portal to search for calls using the appropriate filter criteria. The memory will not be overwritten until you restore normal process.
To restore normal process:
- Option ‘c’ to clear memory
- Option ‘l’ to have calls put in memory again
