Toolpack:Configuring Call Trace A
| Line 46: | Line 46: | ||
| − | + | <div class="mw-collapsible mw-collapsed" data-collapsetext="To start Call Trace, do the following:" data-expandtext="Starting Unique Call Trace" style="width: 400px;"> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == To start Unique Call Trace | + | |
From the web interface:<br> | From the web interface:<br> | ||
<pre>Applications -> Instances -> Status tab -> tbuctwriter -> Oam target state [Run]</pre> | <pre>Applications -> Instances -> Status tab -> tbuctwriter -> Oam target state [Run]</pre> | ||
| − | To modify application configuration ( | + | To modify the application configuration (such as the trace level and memory size):<br> |
<pre>Applications -> Configurations -> tbuctwriter [Edit] | <pre>Applications -> Configurations -> tbuctwriter [Edit] | ||
Systems -> Activate Configuration</pre> | Systems -> Activate Configuration</pre> | ||
| Line 64: | Line 59: | ||
<br> | <br> | ||
| − | + | </div> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== How to search for calls no longer in Memory == | == How to search for calls no longer in Memory == | ||
Revision as of 17:13, 25 October 2012
Applies to version v2.6
Call Trace is a diagnostic tools that is designed to trace the path that a call takes through a Tmedia system and provide information about various 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 to distinguish 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 directly with the Web Portal.
NOTE
Older logs can be loaded and viewed on the same system, or exported to other systems. Once a specific call has been consulted, it will remain in memory for a longer period of time, so that it can be consulted later on.
Calls may be filtered by called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.
To configure call trace:
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.
From the web interface:
Applications -> Instances -> Status tab -> tbuctwriter -> Oam target state [Run]
To modify the application configuration (such as the trace level and memory size):
Applications -> Configurations -> tbuctwriter [Edit] Systems -> Activate Configuration
To see logs
From the web interface:
Call Trace
How to search for calls no longer in Memory
The system will store a number of calls in memory and the search can be done directly from the web interface using Call Trace.
If the call is no longer in memory you can retrieve the information from the uctdata log files.
The default file location is here:
/lib/tb/toolpack/setup/12358/2.6/apps/tbuctwriter/uctdata*
First, start tbx_cli_tools_remote, select tbuctwriter
To know which files are available and the start and end time of each file:
- Option 'p' to print all uctdata files on disk
To load a file in memory to be seen from Web (live calls continue to be captured to files):
- Option 'o' with the data filename (uctdata*)
Once done, you can go back in the Web portal and select Call Trace from the menu on the left. You can search for calls using the filters. 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
