How to troubleshoot call routing - Revision history

Luc Morissette: /* Get the log files from the server */

2023-08-16T19:24:34Z

Get the log files from the server

← Older revision		Revision as of 15:24, 16 August 2023
Line 37:		Line 37:
	=== <br> Get the log files from the server ===		=== <br> Get the log files from the server ===
	You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:		You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:
	<pre>/lib/tb/toolpack/setup/12358/2.9/apps/</pre>		<pre>/lib/tb/toolpack/setup/12358/3.1/apps/</pre>

	== <br> Using the signaling traces ==		== <br> Using the signaling traces ==

2023-01-11T14:32:17Z

2022-05-31T03:59:47Z

← Older revision		Revision as of 23:59, 30 May 2022
Line 30:		Line 30:
	<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>		<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>
	And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>		And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>
	For a more detailed walk-through see: [[~~Application_log_level~~\|How to change an application's ~~log~~ level]]		For a more detailed walk-through see: [[Application_trace_level\|How to change an application's trace level]]

	=== <br> Get log files from web portal ===		=== <br> Get log files from web portal ===

2022-05-31T03:19:28Z

Change an Application log trace level

← Older revision		Revision as of 23:19, 30 May 2022
Line 30:		Line 30:
	<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>		<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>
	And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>		And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>
			For a more detailed walk-through see: [[Application_log_level\|How to change an application's log level]]

	=== <br> Get log files from web portal ===		=== <br> Get log files from web portal ===

2018-12-11T18:57:39Z

Get the log files from the server

← Older revision		Revision as of 14:57, 11 December 2018
Line 36:		Line 36:
	=== <br> Get the log files from the server ===		=== <br> Get the log files from the server ===
	You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:		You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:
	<pre>/lib/tb/toolpack/setup/12358/2.7/apps/~~</pre>~~		<pre>/lib/tb/toolpack/setup/12358/2.9/apps/</pre>
	or
	~~<pre>C:\TelcoBridges\toolpack\setup\12358\2.7\apps\~~</pre>

	== <br> Using the signaling traces ==		== <br> Using the signaling traces ==

2016-09-01T14:55:09Z

Changes SSH to sFTP

← Older revision		Revision as of 10:55, 1 September 2016
Line 35:		Line 35:

	=== <br> Get the log files from the server ===		=== <br> Get the log files from the server ===
	You can get the files directly from the server running Toolpack. Connect ~~SSH~~ to the management port of the unit and get the files at this location:		You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:
	<pre>/lib/tb/toolpack/setup/12358/2.7/apps/</pre>		<pre>/lib/tb/toolpack/setup/12358/2.7/apps/</pre>
	or		or

2016-08-09T20:50:32Z

Added {{DISPLAYTITLE:

← Older revision		Revision as of 16:50, 9 August 2016
Line 1:		Line 1:
			{{DISPLAYTITLE:How to Troubleshoot Call Routing}}
	To debug calls, different methods can be used: <br>		To debug calls, different methods can be used: <br>

2016-08-09T20:13:44Z

Updated CDR link

← Older revision		Revision as of 16:13, 9 August 2016
Line 3:		Line 3:
	== Using the Call Detail Records ==		== Using the Call Detail Records ==

	This can be done in the configuration database, using RADIUS or in text files. See [[~~Text Call Detail Records (CDR)~~\|~~Text~~ Call Detail Records (CDR)]]		This can be done in the configuration database, using RADIUS or in text files. See [[Call_detail_record\|Call Detail Records (CDR)]]

	== Using the Call Trace Tool  <br> ==		== Using the Call Trace Tool  <br> ==

2016-08-09T20:12:36Z

Updated Call trace

← Older revision		Revision as of 16:12, 9 August 2016
Line 5:		Line 5:
	This can be done in the configuration database, using RADIUS or in text files. See [[Text Call Detail Records (CDR)\|Text Call Detail Records (CDR)]]		This can be done in the configuration database, using RADIUS or in text files. See [[Text Call Detail Records (CDR)\|Text Call Detail Records (CDR)]]

	== Using the Call Trace Tool  ~~(UCT or Unique Call Trace)~~<br> ==		== Using the Call Trace Tool  <br> ==

	Call Trace was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, outgoing calls, TDM channel, SIP SDP and more. This can be accessed from the Web Portal. You can create a filter to see call information. See [[Using Unique call trace\|Using ~~Unique call trace~~]].<br>		Call Trace was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, outgoing calls, TDM channel, SIP SDP and more. This can be accessed from the Web Portal. You can create a filter to see call information. See [[Using Unique call trace\|Using Call Trace]].<br>

	== <br> Using the web portal status ==		== <br> Using the web portal status ==

2015-12-18T17:58:31Z

Update on link

← Older revision		Revision as of 13:58, 18 December 2015
Line 27:		Line 27:
	=== <br> Change an Application log trace level ===		=== <br> Change an Application log trace level ===
	<br>You can change the trace level of the application here:		<br>You can change the trace level of the application here:
	<pre>Applications-> ~~Configurations~~ -> ~~edit -> Log Params~~ -> Default Trace Level -> Save</pre>		<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>
	And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>		And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>

	=== <br> Get log files from web portal ===		=== <br> Get log files from web portal ===