Troubleshooting Toolpack
(→Calls) |
m (Formatting update (:* vs **)) |
||
| Line 45: | Line 45: | ||
*To debug calls, different methods can be used: | *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)]] | 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 | Logs -> Select filename -> 2000 lines -> select Read | ||
| Line 77: | Line 77: | ||
| − | + | *'''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/ | ||
| Line 84: | Line 84: | ||
| − | + | *'''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]] | ||
Revision as of 15:40, 8 December 2009
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
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.
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
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'
