How to troubleshoot call routing - Revision history

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

2018-12-11T18:57:39Z

Get the log files from the server

2016-09-01T14:55:09Z

Changes SSH to sFTP

2016-08-09T20:50:32Z

Added {{DISPLAYTITLE:

2016-08-09T20:13:44Z

Updated CDR link

2016-08-09T20:12:36Z

Updated Call trace

2015-12-18T17:58:31Z

Update on link

2015-05-15T10:15:51Z

Add the required step to "Save" the config

2014-10-14T13:50:05Z

Updated to 2.7

2014-04-02T09:03:02Z

Reorganize application log trace

2013-03-15T15:52:28Z

Added tbuctwriter and tbsnmpmux

@@ Line 36: / Line 36: @@
 === <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:
-<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  ==

@@ Line 35: / Line 35: @@
 === <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>
 or

← Older revision		Revision as of 20: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>

@@ Line 3: / Line 3: @@
 == 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&nbsp; <br>  ==

@@ 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)]]
-== Using the Call Trace Tool&nbsp; (UCT or Unique Call Trace)<br>  ==
+== Using the Call Trace Tool&nbsp; <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  ==

@@ Line 27: / Line 27: @@
 === <br> Change an Application log trace level ===
 <br>You can change the trace level of the application here:
-<pre>Applications-&gt; Configurations -&gt; edit -&gt; Log Params -&gt; Default Trace Level -&gt; Save</pre>
+<pre>Applications-&gt; [Application name] -&gt; Advanced parameters -&gt; Default Trace Level -&gt; 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>
 === <br> Get log files from web portal ===

@@ Line 13: / Line 13: @@
 You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc.
-== <br> Using the log files  ==
+== <br> Using the applications log files  ==
-−
-*Log files from web portal
-<pre>Logs -&gt; Select filename -&gt; 2000 lines -&gt; select Read</pre>
 <br>Brief details on the application:
@@ Line 28: / Line 25: @@
 *'''tbuctwriter''' captures call traces
 <br>You can change the trace level of the application here:
 <pre>Applications-&gt; Configurations -&gt; edit -&gt; Log Params -&gt; Default Trace Level</pre>
 And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information.<br>
-== <br> Log files from server  ==
+=== <br> Get log files from web portal ===
 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:
 <pre>/lib/tb/toolpack/setup/12358/2.5/apps/</pre>
 or
 <pre>C:\TelcoBridges\toolpack\setup\12358\2.5\apps\</pre>
 == <br> Using the signaling traces  ==

@@ Line 22: / Line 22: @@
 *'''toolpack_engine''' handles the protocols (SS7, SIP, ISDN, CAS, Sigtran, etc.)&nbsp;and media (RTP, TDM, tones, etc)<br>
 *'''toolpack_sys_manager''' handles the configuration of the system
-*'''tboamapp''' controls the startup of the applicationsand system upgrades<br>
+*'''tboamapp''' controls the startup of the applications and system upgrades<br>
 *'''tbstreamserver''' is used for playing and recording files; by default this application is not started. See How to Start Stream Server
 *'''tblogtrace''' are low-level logs coming from the Telecom platform
 <br>You can change the trace level of the application here: