Call Trace
(→Configuration) |
(→Configuration) |
||
| Line 7: | Line 7: | ||
== Configuration == | == Configuration == | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.10#Troubleshooting|Web Portal v2.10: Call Trace]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.9#Troubleshooting|Web Portal v2.9: Call Trace]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.8#Troubleshooting|Web Portal v2.8: Call Trace]] | ||
*[[Web_Portal_Tutorial_Guide_v2.7#Troubleshooting|Web Portal v2.7: Call Trace]] | *[[Web_Portal_Tutorial_Guide_v2.7#Troubleshooting|Web Portal v2.7: Call Trace]] | ||
*[[Web_Portal_Tutorial_Guide_v2.6#Troubleshooting|Web Portal v2.6: Call Trace]] | *[[Web_Portal_Tutorial_Guide_v2.6#Troubleshooting|Web Portal v2.6: Call Trace]] | ||
Revision as of 20:36, 22 March 2017
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.
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.
Calls to view can be filtered according to called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.
Note: Call Trace is available starting with release 2.6
