Troubleshooting Toolpack
(add toolpack installer troubleshooting page) |
|||
Line 1: | Line 1: | ||
− | This page contains pointers to help troubleshoot [[Toolpack]]-based systems. | + | This page contains pointers to help troubleshoot [[Toolpack]]-based systems. |
+ | <br> | ||
== Installation == | == Installation == | ||
+ | |||
+ | '''Problem: Toolpack fails during installation''' | ||
+ | *See '[[Toolpack Installation:Toolpack installer troubleshooting|Toolpack installer troubleshooting]]' | ||
'''Problem: The Toolpack system does not start''' | '''Problem: The Toolpack system does not start''' | ||
Line 28: | Line 32: | ||
You see this error while trying to download a software package with wget:<br> | You see this error while trying to download a software package with wget:<br> | ||
− | ''Resolving download.telcobridges.com... failed: Temporary failure in name resolution.<br>wget: unable to resolve host address `download.telcobridges.com''' | + | ''Resolving download.telcobridges.com... failed: Temporary failure in name resolution.<br>wget: unable to resolve host address `download.telcobridges.com''' |
*See "nameserver" in [[TBLinux:How to change the ip address|How_to_change_the_ip_address]] | *See "nameserver" in [[TBLinux:How to change the ip address|How_to_change_the_ip_address]] | ||
Line 84: | Line 88: | ||
ps -ef | grep mysqld | ps -ef | grep mysqld | ||
− | </pre> | + | </pre> |
− | + | ||
== Toolpack application suite == | == Toolpack application suite == | ||
− | Coming soon. | + | Coming soon. |
== Calls == | == Calls == | ||
Line 100: | Line 103: | ||
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)]] | ||
− | <br> | + | <br> |
*'''Using the log files''' | *'''Using the log files''' | ||
Line 128: | Line 131: | ||
And then activate the new configuration. | And then activate the new configuration. | ||
− | <br> | + | <br> |
*'''Log files from server''' | *'''Log files from server''' | ||
Line 140: | Line 143: | ||
C:\TelcoBridges\toolpack\setup\12358\2.3\apps\ | C:\TelcoBridges\toolpack\setup\12358\2.3\apps\ | ||
− | <br> | + | <br> |
*'''Using the signaling traces''' | *'''Using the signaling traces''' | ||
Line 146: | Line 149: | ||
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]] | ||
− | + | <br> | |
*'''Using the Toolpack programs backdoor tool''' | *'''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. | + | 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 | + | Select this to learn [[How to use tbx cli tools remote program]].<br> |
+ | |||
+ | == How to gather all logs == | ||
+ | |||
+ | Problem: Which application logs should I gathered? | ||
+ | |||
+ | *See '[[Toolpack Debug Application:Tbdebug|How to gather logs with tbdebug]]' | ||
+ | |||
+ | <br> | ||
− | == How to | + | == How to submit a problem == |
− | + | ||
− | + | ||
+ | Problem: I don't know what else to do | ||
− | |||
− | |||
*Help our support team help you by giving as much information as possible; see '[[Support:How To Submit A Problem]]' | *Help our support team help you by giving as much information as possible; see '[[Support:How To Submit A Problem]]' |
Revision as of 10:04, 17 May 2010
This page contains pointers to help troubleshoot Toolpack-based systems.
Contents |
Installation
Problem: Toolpack fails during 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
Problem: Can't download a new software package
You see this error while trying to download a software package with wget:
Resolving download.telcobridges.com... failed: Temporary failure in name resolution.
wget: unable to resolve host address `download.telcobridges.com'
- See "nameserver" in How_to_change_the_ip_address
Web portal
Problem: The Toolpack web portal does not start or is not accessible.
- See 'How to troubleshoot the web portal'
- See 'How to get status of the system'
- See 'How to change the configuration of the system'
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.
- See 'How to Edit the active configuration'
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
- Help our support team help you by giving as much information as possible; see 'Support:How To Submit A Problem'