How to troubleshoot call routing

• 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 web portal status

Status -> NAP -> Edit

You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc.

* 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 called number, Network Access Points, routing scripts, regular expressions.
• toolpack_engine handles the protocols (SS7, SIP, ISDN, CAS, Sigtran, etc.) and media (RTP, TDM, tones, etc)
  
• toolpack_sys_manager handles the configuration of the system
• tboamapp controls the startup of the applicationsand system upgrades
  
• tbstreamserver is used for playing and recording files; by default this application is not started. See How to Start Stream Server
• tblogtrace are low-level logs coming from the Telecom platform

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. Connect SSH to the management port of the unit and get the files 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.

Typical errors:

404 not found