Troubleshooting Toolpack: Difference between revisions
(→Calls) |
(some formatting clean-up) |
||
| Line 1: | Line 1: | ||
This page contains pointers to help | This page contains pointers to help troubleshoot [[Toolpack]]-based systems. | ||
== Installation == | == Installation == | ||
Problem | Problem: The Toolpack system does not start | ||
: The Toolpack system does not start | *See '[[Toolpack_Installation:Validate_Toolpack_Installation|How to validate the Toolpack installation]]' | ||
* | |||
Problem: | Problem: I want to change the Ip Address of the TMG800/TMG3200 from static to DHCP or from DHCP to static. | ||
: I want to change the hostname of the server running Toolpack | *See '[[TBLinux:How to change_the_ip_address|How to change the IP address of a TMG800/TMG3200]] | ||
* | |||
Problem: I want to change the hostname of the server running Toolpack | |||
*See '[[Toolpack_Installation:Change hostname|How to change the host name]]' | |||
== Web portal == | == Web portal == | ||
Problem | Problem: The Toolpack web portal does not start or is not accessible. | ||
: The web portal | *See '[[Toolpack_Troubleshooting:Web_Portal|How to troubleshoot the web portal]]' | ||
* | *See 'How to get status of the system' | ||
*How to get status of the system | *See 'How to change the configuration of the system' | ||
*How to change the configuration of the system | |||
Problem: | 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 [[Toolpack Troubleshooting:Cannot Add or Edit Configuration|solve this problem]]' | |||
*How to | |||
Problem: | Problem: Do not have permission to add features. | ||
: The system does not work properly with a copied configuration. | *See 'How to modify system configuration' | ||
* | |||
Problem: The system does not work properly with a copied configuration. | |||
*See [[Web_Portal:Configuration_Copy|How to copy a configuration]] | |||
== Toolpack application suite == | == Toolpack application suite == | ||
Coming soon. | |||
== Calls == | == Calls == | ||
Problem | Problem: The Tmedia device does not accept or generate calls | ||
: The Tmedia | |||
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)]] | |||
*'''Using the log files''' | **'''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. | ::'''gateway''' application is for high-level call routing, like calling number and NAPs. | ||
| Line 75: | Line 71: | ||
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''' | **'''Using the signaling traces''' | ||
You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[Toolpack_Debug_Application:Tbsigtrace|using tbsigtrace]] | |||
== How to gather all logs == | == How to gather all logs == | ||
Problem | Problem: Which application logs should I gathered? | ||
: Which application logs should I gathered? | *See '[[Toolpack_Debug_Application:Tbdebug|How to gather logs with tbdebug]]' | ||
* | |||
== How to submit a problem == | == How to submit a problem == | ||
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 [[Support:How_To_Submit_A_Problem]] | |||
Revision as of 09:36, 22 October 2009
This page contains pointers to help troubleshoot Toolpack-based systems.
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
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 solve this problem'
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.
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
- Using the log files
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 it is not started)
- 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
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'