Troubleshooting Toolpack

From TBwiki
(Difference between revisions)
Jump to: navigation, search
m (Added See)
(Added Using the Toolpack programs backdoor tool)
Line 80: Line 80:
 
Coming soon.
 
Coming soon.
  
== Calls ==
+
== Calls ==
Problem: The Tmedia device does not accept or generate calls
+
 
 +
Problem: The Tmedia device does not accept or generate calls  
  
 
*To debug calls, different methods can be used:
 
*To debug calls, different methods can be used:
  
 
:*'''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)]]
 
  
 +
This can be done in the configuration database, using [[RADIUS]] or in text files. See [[Text Call Detail Records (CDR)]]
  
*'''Using the log files'''
+
<br>
:*'''Log files from web portal'''
+
  
  Logs -> Select filename -> 2000 lines -> select Read
+
*'''Using the log files'''
  
 +
:*'''Log files from web portal'''
  
Brief details on the application:
+
  Logs -&gt; Select filename -&gt; 2000 lines -&gt; select Read
 +
 
 +
<br>Brief details on the application:  
  
 
::'''gateway''' application is for high-level call routing, like calling number and NAPs.
 
::'''gateway''' application is for high-level call routing, like calling number and NAPs.
Line 109: Line 112:
 
::'''tblogtrace''' are log coming from the platform (TMP6400 or other)
 
::'''tblogtrace''' are log coming from the platform (TMP6400 or other)
  
 +
<br>You can change the trace level of the application here:
  
You can change the trace level of the application here:
+
  Applications-&gt; Configurations -&gt; edit -&gt; Log Params -&gt; Default Trace Level
  
  Applications-> Configurations -> edit -> Log Params -> Default Trace Level
+
And then activate the new configuration.  
 
+
And then activate the new configuration.
+
  
 +
<br>
  
 
*'''Log files from server'''
 
*'''Log files from server'''
You can get the files directly from the server running Toolpack at this location:
+
 
 +
You can get the files directly from the server running Toolpack at this location:  
 +
 
 
   /lib/tb/toolpack/setup/12358/2.3/apps/
 
   /lib/tb/toolpack/setup/12358/2.3/apps/
or
+
 
 +
or  
 +
 
 
   C:\TelcoBridges\toolpack\setup\12358\2.3\apps\
 
   C:\TelcoBridges\toolpack\setup\12358\2.3\apps\
  
 +
<br>
  
 
*'''Using the signaling traces'''
 
*'''Using the signaling traces'''
You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[Toolpack_Debug_Application:Tbsigtrace|using tbsigtrace]]
+
 
 +
You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[Toolpack Debug Application:Tbsigtrace|using tbsigtrace]]  
 +
 
 +
 
 +
 
 +
*'''Using the&nbsp;Toolpack programs backdoor tool'''
 +
 
 +
You can access to the toolpack applications directly by using the ''tbx_cli_tools_remote ''application. This application allows full control over any Toolpack application. This allows for example to view real time calls going through the Toolpack Engine.
 +
 
 +
Select this to&nbsp;learn&nbsp;[[How to use tbx_cli_tools_remote program]].<br>
  
 
== How to gather all logs ==
 
== How to gather all logs ==

Revision as of 14:58, 16 February 2010

This page contains pointers to help troubleshoot Toolpack-based systems.


Contents

Installation

Problem: The Toolpack system does not start


Problem: I want to change the Ip Address of the TMG800/TMG3200 from static to DHCP or from DHCP to static.


Problem: I want to change the hostname of the server running Toolpack


Problem: E1 trunks are not up

Web portal

Problem: The Toolpack web portal does not start or is not accessible.


Problem: I cannot perform addition or modification of configuration in the web portal. Usually this occurs in a new Toolpack Platform, for example, when new Toolpack software has been just installed on a host or a new TMG3200 is started up.


Problem: Do not have permission to add features.

  • See 'How to modify system configuration'


Problem: The system does not work properly with a copied configuration.


Problem: There are no web browser on the linux host server

ssh tunnel can be use to re-direct the connection on a remote host port to a local port:

Toolpack MySQL configuration database

Problem: I need to backup my Toolpack configuration.

To backup the MySQL database, use the following commands:

  mysqldump -u tbdb --password=tbdbpw --opt toolpack_0 > toolpack_0_bk.sql

Then, you need to save the "toolpack_0_bk.sql" file in a safe place.

You can recover the database this way:

mysql -u tbdb--password=tbdbpw toolpack_0 < toolpack_0_bk.sql

This procedure can also be used to make copies of similar configurations from one Toolpack system to another. The Serial Number of the hardware devices used (Tmedias) must be updated after the new database is in place (Hardware -> Edit -> Serial)


Other useful mysql commands:

mysql –u tbdb –p tbdbpw
use toolpack_0;
show tables;
SELECT * from system_infos;
SELECT * from mysql.user;
service mysqld stop
service mysqld start
ps -ef | grep mysqld

Toolpack application suite

Coming soon.

Calls

Problem: The Tmedia device does not accept or generate calls

  • To debug calls, different methods can be used:
  • 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)


  • Using the log files
  • Log files from web portal
 Logs -> Select filename -> 2000 lines -> select Read


Brief details on the application:

gateway application is for high-level call routing, like calling number and NAPs.
toolpack_engine handles the protocols and media
toolpack_sys_manager handles the configuration of the system
tboamapp controls the startup of the applications
tbstreamserver is used for playing and recording files; by default this application is not started. See How to Start Stream Server
tblogtrace are log coming from the platform (TMP6400 or other)


You can change the trace level of the application here:

 Applications-> Configurations -> edit -> Log Params -> Default Trace Level

And then activate the new configuration.


  • Log files from server

You can get the files directly from the server running Toolpack at this location:

 /lib/tb/toolpack/setup/12358/2.3/apps/

or

 C:\TelcoBridges\toolpack\setup\12358\2.3\apps\


  • Using the signaling traces

You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: using tbsigtrace


  • Using the Toolpack programs backdoor tool

You can access to the toolpack applications directly by using the tbx_cli_tools_remote application. This application allows full control over any Toolpack application. This allows for example to view real time calls going through the Toolpack Engine.

Select this to learn How to use tbx_cli_tools_remote program.

How to gather all logs

Problem: Which application logs should I gathered?


How to submit a problem

Problem: I don't know what else to do

Personal tools