Toolpack:Configuring Call Trace D - Revision history

Luc Morissette at 14:38, 5 March 2026

2026-03-05T14:38:32Z

@@ Line 24: / Line 24: @@
 A call path is shown as separate call legs, distinguishing the incoming portion with other portions of a call. Calls may be filtered by called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.
+<br><br>
 Call trace enables a default of 10,000 call legs to be stored in the system and to be viewed using the Web Portal. This value can be increased from the Call Trace application configuration parameters.

Luc Morissette at 14:33, 5 March 2026

2026-03-05T14:33:10Z

← Older revision		Revision as of 10:33, 5 March 2026
Line 82:		Line 82:
	'''Parameters (text)'''		'''Parameters (text)'''
	<pre>		<pre>
	/configurations/~~aaa_Innsys_201602~~/applications/tbuctwriter/log_parameters		/configurations/aaa_201602/applications/tbuctwriter/log_parameters
	default_trace_level = "Level 4 (quiet)"		default_trace_level = "Level 4 (quiet)"
	log_file_path = ""		log_file_path = ""

Allyntree at 17:11, 22 June 2024

2024-06-22T17:11:53Z

← Older revision		Revision as of 13:11, 22 June 2024
Line 7:		Line 7:
	\|-		\|-
	\|Tmedia		\|Tmedia
	\|2.9, 2~~.10~~, 3.0, 3.2		\|3.0, 3.2, 3.3
	\|-		\|-
	\|SBC		\|SBC
	\|3.0, 3.1		\|3.1, 3.3
	\|}		\|}

Allyntree at 19:23, 10 December 2020

2020-12-10T19:23:42Z

← Older revision		Revision as of 15:23, 10 December 2020
Line 1:		Line 1:
	~~=== '''''Applies to version(s): 2.9, 2.10, 3.0, 3.1, 3.2''''' ===~~
	{{DISPLAYTITLE:Configuring Call Trace}}		{{DISPLAYTITLE:Configuring Call Trace}}
			{\| class="wikitable"
			\|-
			\|rowspan="3"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|Tmedia
			\|2.9, 2.10, 3.0, 3.2
			\|-
			\|SBC
			\|3.0, 3.1
			\|}

	Call Trace is a diagnostic tool that is designed to trace the path a call takes through a system, and to provide information about numerous aspects of the call path, such as:		Call Trace is a diagnostic tool that is designed to trace the path a call takes through a system, and to provide information about numerous aspects of the call path, such as:

Allyntree at 18:11, 8 September 2020

2020-09-08T18:11:41Z

← Older revision		Revision as of 14:11, 8 September 2020
Line 1:		Line 1:
	=== '''''Applies to version(s): v2.9, v2.10, v3.0, v3.1''''' ===		=== '''''Applies to version(s): 2.9, 2.10, 3.0, 3.1, 3.2''''' ===
	{{DISPLAYTITLE:Configuring Call Trace}}		{{DISPLAYTITLE:Configuring Call Trace}}

Allyntree at 16:25, 21 May 2019

2019-05-21T16:25:45Z

← Older revision		Revision as of 12:25, 21 May 2019
Line 1:		Line 1:
	=== '''''Applies to version(s): v2.9, v2.10, v3.0''''' ===		=== '''''Applies to version(s): v2.9, v2.10, v3.0, v3.1''''' ===
	{{DISPLAYTITLE:Configuring Call Trace}}		{{DISPLAYTITLE:Configuring Call Trace}}

Allyntree at 17:55, 11 December 2017

2017-12-11T17:55:32Z

← Older revision		Revision as of 13:55, 11 December 2017
Line 1:		Line 1:
	=== '''''Applies to version(s): v2.9, v2.10''''' ===		=== '''''Applies to version(s): v2.9, v2.10, v3.0''''' ===
	{{DISPLAYTITLE:Configuring Call Trace}}		{{DISPLAYTITLE:Configuring Call Trace}}

	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:		Call Trace is a diagnostic tool that is designed to trace the path a call takes through a system, and to provide information about numerous aspects of the call path, such as:

	* The routing decision		* The routing decision

Allyntree at 18:27, 6 January 2017

2017-01-06T18:27:13Z

← Older revision		Revision as of 14:27, 6 January 2017
Line 1:		Line 1:
	=== '''''Applies to version(s): 2.9''''' ===		=== '''''Applies to version(s): v2.9, v2.10''''' ===
	{{DISPLAYTITLE:Configuring Call Trace}}		{{DISPLAYTITLE:Configuring Call Trace}}

Allyntree: added northbound data

2016-02-10T15:06:30Z

added northbound data

← Older revision		Revision as of 11:06, 10 February 2016
Line 66:		Line 66:
	'''Path'''		'''Path'''
	<pre>		<pre>
			/configurations/AllynWikiSystem/applications/tbuctwriter/log_parameters
	</pre>		</pre>

	'''Parameters (text)'''		'''Parameters (text)'''
	<pre>		<pre>
			/configurations/aaa_Innsys_201602/applications/tbuctwriter/log_parameters
			default_trace_level = "Level 4 (quiet)"
			log_file_path = ""
			max_gzipped_log_files_size = "100 MB"
			max_log_file_segment_size = "10 MB"
	</pre>		</pre>

	'''Parameters (json)'''		'''Parameters (json)'''
	<pre>		<pre>
	</pre>		{
			"application_type" : "TbUctWriter",
			"bin_path" : "@{PKG_BIN}/tbuctwriter",
			"command_line_arguments" : "",
			"log_parameters" : {
			"default_trace_level" : "Level 4 (quiet)",
			"log_file_path" : "",
			"max_gzipped_log_files_size" : "100 MB",
			"max_log_file_segment_size" : "10 MB"
			},
			"working_path" : "../tbuctwriter/"
			}</pre>
	</div>		</div>

Allyntree: Created page with "=== '''''Applies to version(s): 2.9''''' === {{DISPLAYTITLE:Configuring Call Trace}} Call Trace is a diagnostic tool that is designed to trace the path a call takes through a..."

2015-12-08T15:43:37Z

Created page with "=== '''''Applies to version(s): 2.9''''' === {{DISPLAYTITLE:Configuring Call Trace}} Call Trace is a diagnostic tool that is designed to trace the path a call takes through a..."

New page

=== '''''Applies to version(s): 2.9''''' ===
{{DISPLAYTITLE:Configuring Call Trace}}

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. 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 procedure only needs to be carried out one time for each system.'''

1- Select '''Applications''' in the navigation menu.

[[Image:EnableCallTrace_B_0.png]]

2- Select the '''Status''' tab.

[[Image:EnableCallTrace_B_1.png]]

3- Select the '''tbuctwriter''' application

[[Image:EnableCallTrace_B_2.png]]

3- Select '''Run'''
* Click '''Apply States'''

[[Image:EnableCallTrace_B_3.png]]

</div>

Call trace enables a default of 10,000 call legs to be stored in the system and to be viewed using the Web Portal. This value can be increased from the Call Trace application configuration parameters.

1- Select '''Applications''' in the navigation menu.

[[Image:EnableCallTrace_B_0.png]]

2- Select the '''tbuctwriter''' application

[[Image:ConfigureCallTrace_B_0.png]]

3- Click '''Application Parameters'''

[[Image:ConfigureCallTrace_B_1.png]]

4- Configure the '''Trace Level''' and other associated trace parameters.
* Click '''Save'''

[[Image:ConfigureCallTrace_B_2.png]]

<div class="mw-collapsible mw-collapsed" data-collapsetext="Northbound Interface" data-expandtext="Northbound Interface" style="width: 400px;">

'''Path'''
<pre>
</pre>

'''Parameters (text)'''
<pre>
</pre>

'''Parameters (json)'''
<pre>
</pre>
</div>

==List of Parameters==

* [[Parameter: Call_Trace_Trace_Level|Trace Level]]
* [[Parameter: Call_Trace_Maximum_Compressed_Directory_Size|Maximum compressed directory size]]
* [[Parameter: Maximum_File_Size|Maximum file size]]
* [[Parameter: Maximum_Call_Legs|Maximum call legs]]
* [[Parameter: Consulted_Legs_Recall|Consulted legs recall]]