Categories

Standard > Troubleshooting Data: References > TPO > Syslog and Trace Engine

Category names are defined in order to group traces which are conceptually related.

For instance “CCL” category refers to the call control module which is part of application that handles SIP messages.

Commonly used TPO logging categories

•APP : module startup and shutdown

•OLD : main TPO module in charge of call orchestration among other things

•TSSOLD : sub-category of main module that manages interactions with BSCG module

•BSCG : communications with the TSS

•CCL : SIP communications and SIP stack object management

•CCLBACKUP : sub category of CCL that is specific to hot backup restoration context

•CCL.SIP.CONNECTIONS: sub category of CCL that refers to TCP/TLS inbound connections

•SIPSTACK: this category is used to trace all messages coming from the SIP stack library. See SIPSTACK exception case here after.

•OLDCB, MMCLIENT, DIEDCALL : all those 3 categories refers to media manager and RTP stream control

•RECORDER : call recording

•RECMIXER : mixing for call recording

•CERTIFICATE : TPO certificate management

•BACKUP.RECEIVER, BACKUP.EMITTER : Inter TPO protocol for hot backup purpose

•SNMP : SNMP client

Advanced turret logging categories

Some categories are obsolete or almost never used in production environments:

•MCAST.EMITTER, MCAST.RECEIVER : ITMH protocol related

•APPMON : inter module communication system

Note the following categories are by default configured in info level: APP, CCLBACKUP, OLD, TSSOLD, BABKUP.EMITTER, BACKUP.RECEIVER, SIPSTACK and CCL.SIP.CONNECTIONS

SIPSTACK exception case

As mentioned here above, this category is used to trace all messages coming from the SIP stack library.

This category is configured with a warning default level, and it might be useful, especially when investigating issues that occur in the field and cannot be reproduced at will.

Important_icon

As SIPSTACK messages are generated inside the library, we do not precisely control SIP Stack messages severity level. That leads some messages to be traced with a non-relevant security level. As an example, when generating a debug information, SIP Stack always generates 2 fatal messages that have no impact at all on the system stability or user experience and must be ignored.

We recommend not to decrease SIPSTACK logging verbosity level, but just ignore this category messages.

How to increase SIP STACK logger verbosity

In some specific cases, such as CCL!F0001, you might have to increase SIPSTACK logging verbosity to debug2.

Doing so requires more than just changing the logger level; SIP Stack Log Filters must be changed as well.

This cannot be done "On the Fly" as it requires to reboot the device.

In order to activate SIP Stack trace debug2 level you have to:

1.Add following configuration keys in your TPO boot settings:

•application.sip.stack.defaultLogFilters = 31

•trace.logger@sipstack.eventlevel = debug2

•trace.logger@ccl.eventlevel = debug2

2.Reboot your turret and execute your scenario.

3.Collect generated logs.

4.Remove the configuration keys from your turret boot settings.

5.Reboot your turret.

Note that procedure here above sets CCL category to debug2 as issues that require to increase SIP Stack logging verbosity are, most of the time, related to CCL module as well.