Actions

Call Trace: Difference between revisions

m (moved Using Unique call trace to Call Trace: simplify article title)
mNo edit summary
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Unique call trace (uct) was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, the routing decision, outgoing calls, other outgoing calls if there is route retry, the parameters selected for SIP SDP, the SIP Call-id, the trunk and timeslot chosen for TDM protocols, the termination result code, and more.  
{{DISPLAYTITLE:Call Trace}}
Call trace (uct) was created to trace the callflow from an incoming call through the Tmedia system. It enables viewing of the incoming call, the routing decision, outgoing calls, other outgoing calls if there is route retry, the parameters selected for SIP SDP, the SIP Call-id, the trunk and timeslot chosen for TDM protocols, the termination result code, and more.  


It allows to store information for long periods of time and search for calls in history. The last 10,000 call legs (default size) can be seen directly in the web portal. 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.<br>Calls to view can be filtered according to called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.  
It stores information for long periods of time and search for calls in history. The last 10,000 call legs (default size) can be seen directly in the web portal. 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.<br>Calls to view can be filtered according to called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.  


== To start Unique Call Trace<br>  ==
== Features ==
* Troubleshooting call flows
* Download audio from recorded calls
* Terminate suspicious calls


From the web interface:<br>
=== Filter parameters ===
<pre>Applications -&gt; Instances -&gt; Status tab -&gt; tbuctwriter -&gt; Oam target state [Run]</pre>
* [[Filter_parameters_reference_guide_A|Filter parameters reference guide]]
To modify application configuration (like trace level and memory size):<br>
<pre>Applications -&gt; Configurations -&gt; tbuctwriter [Edit]
Systems -&gt; Activate Configuration</pre>
== To see logs<br>  ==


From the web interface:  
== Configuration ==
<pre>Call Trace</pre>
* Web Portal v3.2
<br>
**[[Toolpack:Troubleshooting_E|Tmedia Call Trace]]
* Web Portal v3.1
**[[Toolpack:Tsbc_Troubleshooting_3.1|ProSBC Call Trace]]
* Web Portal v3.0
**[[Toolpack:Tsbc_Troubleshooting_3.0|ProSBC Call Trace]]
**[[Toolpack:Troubleshooting_D|Tmedia Call Trace]]
* Web Portal v2.10
**[[Toolpack:Tsbc_Troubleshooting_A#Call_Trace|Tsbc Call Trace]]
**[[Toolpack:Troubleshooting_C#Call_Trace|Tmedia Call Trace]]
*[[Toolpack:Troubleshooting_B#Call_Trace|Web Portal v2.9: Call Trace]]


== Call Filters<br>  ==
[[Category:Revise on Major]]
 
Calls can be filtered using the following information:<br>
 
*Time and date range
*Called or calling number
*Network Access Point (NAP)
*Incoming or outgoing calls
*Call Duration, Reason Code
 
[[Image:Sample call trace filter.jpg|787x192px]]<br>
 
You can then select the call to see and it will display information about the calls.
 
[[Image:Sample Call Trace.jpg|785x515px]]<br>
 
<br>
 
== 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:
<pre>/lib/tb/toolpack/setup/12358/2.6/apps/tbuctwriter/uctdata*</pre>
First, start [[How_to_use_tbx_cli_tools_remote_program|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): <br>
 
*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:<br>
 
*Option ‘c’ to clear memory
*Option ‘l’ to have calls put in memory again
 
<br>
 
''Note: Unique Call Trace (UCT) is available starting with release 2.6''<br><br>

Revision as of 10:11, 8 September 2022

Call trace (uct) was created to trace the callflow from an incoming call through the Tmedia system. It enables viewing of the incoming call, the routing decision, outgoing calls, other outgoing calls if there is route retry, the parameters selected for SIP SDP, the SIP Call-id, the trunk and timeslot chosen for TDM protocols, the termination result code, and more.

It stores information for long periods of time and search for calls in history. The last 10,000 call legs (default size) can be seen directly in the web portal. 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 to view can be filtered according to called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.

Features

  • Troubleshooting call flows
  • Download audio from recorded calls
  • Terminate suspicious calls

Filter parameters

Configuration