Troubleshooting Toolpack
(→Calls) |
(→Calls) |
||
| Line 50: | Line 50: | ||
To debug calls, different methods can be used: | To debug calls, different methods can be used: | ||
| − | *'''Using the Call Detail | + | *'''Using the Call Detail Records''' |
This can be done in the configuration database, using Radius or in text files. | This can be done in the configuration database, using Radius or in text files. | ||
Revision as of 14:21, 21 October 2009
This page contains pointers to help troubleshooting the Toolpack system.
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
Web portal
Problem:
- The web portal do not start or is not accessible.
- How to troubleshoot the web portal.
- How to get status of the system.
- 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.
- How to solve this problem.
Problem:
- Do not have permission to add features.
- How to modify system configuration
Problem:
- The system does not work properly with a copied configuration.
- How to copy a configuration
Toolpack application suite
Problem:
Calls
Problem:
- The Tmedia do 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 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 activating 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 gathered logs with tbdebug
How to submit a problem
Problem:
- Don't know what else to do
- Help our support team help you by giving as much information as possible Support:How_To_Submit_A_Problem
