Toolpack Debug Application:Tbsigtrace
Tbsigtrace is a Toolpack debug tool that is use to collect protocol messages.
Contents |
Where it is located
The binary is located in the [InstallDir]/[PackageVersion]/bin/release/[Platform]/
Example:
Version 2.3.3, Windows system
C:\TelcoBridges\toolpack\pkg\2.3.3\bin\release\i586-win32\tbsigtrace.exe
Version 2.3.5, CentOS 64 bits system
/lib/tb/toolpack/pkg/2.3.5/bin/release/x86_64-linux64/tbsigtrace
How to use it
Command line
Options available:
- -d Daemon mode
- -name XYZ Application name
- -db Not used
- -c XYZ Configuration file to load
- -gw XYZ SystemId (i.e. 12358)
- -adapter TBXYZ Adapter name to connect
- -ss7 Default ss7 trace activation
- -isdn Default isdn trace activation
- -ip Default ip trace activation (sip and sigtran)
- -cap CAP format enabled
- -regroup Regroup entity of same type
Examples
This will gather all ss7 links from one blade and put this in a single cap file
tbsigtrace -gw 12358 -adapter TB000544 -ss7 -regroup -cap
This will gather all isdn links from one blade and put them in several files
tbsigtrace -gw 12358 -adapter TB000544 -isdn -cap
This will gather all sip traces and put them in a single cap file
tbsigtrace -gw 12358 -adapter TB000544 -sip -regroup -cap
In release 2.4
This will gather all sip and sigtran traces and put them in a single cap file for all adapters in the system
tbsigtrace -gw 12358 -adapter all -ip -regroup -cap
This command will regroup all signaling types by group in 3 files (1 file for ss7, 1 for isdn and a last for sip( or ip)).
tbsigtrace -gw 12358 -adapter TB000544 -regroup -cap
Configuration file
The configuration file will allow to get several blades in the same file
Example MTP2_LINK_0,MTP2_LINK_1 are on the same blade and MTP2_LINK_10,MTP2_LINK_11 are on an other blade
<signaling> <sysmgr name = "MTP2_LINK_0" grpname="LS1" capfile="true" /> <sysmgr name = "MTP2_LINK_1" grpname="LS1" capfile="true" /> <sysmgr name = "MTP2_LINK_10" grpname="LS1" capfile="true" /> <sysmgr name = "MTP2_LINK_11" grpname="LS1" capfile="true" /> </signaling>