Troubleshooting Toolpack

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(Calls)
(Calls)
Line 46: Line 46:
 
Problem:
 
Problem:
 
: The Tmedia do not accept or generate calls
 
: The Tmedia do not accept or generate calls
 +
  
 
To debug calls, different methods can be used:
 
To debug calls, different methods can be used:
  
*Use the CDRs, in the configuration database, using Radius or in text files.
+
 
 +
*'''Using the CDRs'''
 +
 
 +
This can be done in the configuration database, using Radius or in text files.
 
See [[Text Call Detail Records (CDR)]]
 
See [[Text Call Detail Records (CDR)]]
  
*Log files from web portal
+
*'''Log files'''
 +
 
 +
'''Log files from web portal'''
  
 
Logs -> Select filename -> 2000 lines -> select Read
 
Logs -> Select filename -> 2000 lines -> select Read
 +
 
Brief details on the application:
 
Brief details on the application:
  
a) 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.
b) toolpack_Engine handles the protocols and media
+
c) toolpack_sys_manager handles the configuration of the system
+
d) tboamapp controls the startup of the applications
+
e) tbstreamserver is used for playing and recording files (by default it is not started)
+
f) tblogtrace are log coming from the platform (TMP6400 or other)
+
  
*You can change the trace level of the application here:
+
:'''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
 
Applications-> Configurations -> edit -> Log Params -> Default Trace Level
Line 70: Line 83:
 
And then activating the new configuration
 
And then activating the new configuration
  
*You can get the files directly from the server at this location:
+
'''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/
 
/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\
  
*How to get the protocol messages by [[Toolpack_Debug_Application:Tbsigtrace|using tbsigtrace]]
+
 
 +
*'''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 ==

Revision as of 14:20, 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.

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.
  • How to modify system configuration


Problem:

The system does not work properly with a copied 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 CDRs

This can be done in the configuration database, using Radius or in text files. See Text Call Detail Records (CDR)

  • 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\


  • 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:

Don't know what else to do
Personal tools