How to troubleshoot call routing
From TBwiki
(Difference between revisions)
(New page) |
|||
| Line 1: | Line 1: | ||
| − | * 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) | + | This can be done in the configuration database, using RADIUS or in text files. See Text Call Detail Records (CDR) |
<br> * Using the web portal status | <br> * Using the web portal status | ||
| − | <pre>Status -> NAP -> Edit</pre> | + | <pre>Status -> NAP -> Edit</pre> |
| − | You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc. | + | You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc. |
<br> * Using the log files | <br> * Using the log files | ||
| − | * Log files from web portal | + | *Log files from web portal |
| − | <pre>Logs -> Select filename -> 2000 lines -> select Read</pre> | + | <pre>Logs -> Select filename -> 2000 lines -> select Read</pre> |
| − | <br>Brief details on the application: | + | <br>Brief details on the application: |
*'''gateway''' application is for high-level call routing, like called number, Network Access Points, routing scripts, regular expressions. | *'''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)<br> | + | *'''toolpack_engine''' handles the protocols (SS7, SIP, ISDN, CAS, Sigtran, etc.) and media (RTP, TDM, tones, etc)<br> |
*'''toolpack_sys_manager''' handles the configuration of the system | *'''toolpack_sys_manager''' handles the configuration of the system | ||
| − | *'''tboamapp''' controls the startup of the applicationsand system upgrades<br> | + | *'''tboamapp''' controls the startup of the applicationsand system upgrades<br> |
*'''tbstreamserver''' is used for playing and recording files; by default this application is not started. See How to Start Stream Server | *'''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 | *'''tblogtrace''' are low-level logs coming from the Telecom platform | ||
| − | <br>You can change the trace level of the application here: | + | <br>You can change the trace level of the application here: |
| − | <pre>Applications-> Configurations -> edit -> Log Params -> Default Trace Level</pre> | + | <pre>Applications-> Configurations -> edit -> Log Params -> Default Trace Level</pre> |
| − | And then activate the new configuration. | + | And then activate the new configuration. |
<br> * Log files from server | <br> * 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: | + | 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: |
| − | <pre>/lib/tb/toolpack/setup/12358/2. | + | <pre>/lib/tb/toolpack/setup/12358/2.5/apps/</pre> |
| − | or | + | or |
| − | <pre>C:\TelcoBridges\toolpack\setup\12358\2. | + | <pre>C:\TelcoBridges\toolpack\setup\12358\2.5\apps\</pre> |
<br> * Using the signaling traces | <br> * Using the signaling traces | ||
| − | You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[ | + | You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[Toolpack Debug Application:Tbsigtrace|using tbsigtrace]] |
<br> * Using the Toolpack programs backdoor tool | <br> * 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. | + | 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 [[ | + | Select this to learn [[How to use tbx cli tools remote program|How to use tbx cli tools remote program]].<br><br> |
| − | Typical errors: | + | Typical errors: |
404 not found | 404 not found | ||
Revision as of 14:29, 10 May 2011
- 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.5/apps/
or
C:\TelcoBridges\toolpack\setup\12358\2.5\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
