Filter
Top Products
Dialogic
®
Global Call IP Technology Guide — November 2007 379
Dialogic Corporation
Debugging Dialogic
®
Global Call API IP Applications
Module Sections
The RtfConfig.xml file contains a number of module sections, each of which controls the logging of
trace statements for a specific RTF module. Three RTF modules apply to the IP Call Control
library: gc_h3r, h323_stack, and sip_stack.
Each module section begins with a <Module> tag (with name and state attributes) and ends with a
</Module> tag. Between these two tags, the configuration file contains one or more “MLabel”
elements to locally enable or disable logging of the RTF labels that are used by the specific module.
The behavior of the “MLabel” elements for each of the RTF modules for the IP Call Control library
are described in the following sections of this chapter.
Client Entries
In addition to “MLabel” elements, a module section may also contain a number of “MClient”
elements for any clients that are defined within the module. Each of the three of the RTF modules
for the IP Call Control library include a number of MClient elements, as described in the following
sections of this chapter.
7.2.2 Configuring the gc_h3r Logging Module
The gc_h3r module controls logging of error and debug statements that related to the call control,
signal handling, and signal adaptation layer software modules of the IP Call Control library. These
statements were logged to the gc_h3r.log file in previous implementations.
The RTF gc_h3r module supports three user-maskable RTF labels: Error, Warning, and Debug.
This is in contrast to the previous non-RTF implementation of the GC_H3R module, which used
six debug levels. The old levels are mapped to the new labels as follows:
In addition to the five GC_H3R debug levels that are mapped to RTF labels, there is an additional
level, LEVEL_SPECIAL, which is not mapped to an RTF label and is therefore non-maskable.
Statements marked with LEVEL_SPECIAL are always printed to the log file.
The Error label is normally enabled globally. The Warning label is normally enabled locally, on the
module level. The Debug label is enabled and disabled on the module level, and if the label is
enabled the logging of these statements is controllable on an individual client basis.
The cg_h3r module in the RtfConfig.xml file begins with the statement:
<Module name="gc_h3r" state="1">
Following this statement are “MLabel” statements to set the local state of the Warning and Debug
labels. In the default RtfConfig.xml file, the Warning label is enabled (state="1") and the Debug
label is disabled (state="0").
RTF Label (and default state) Old GC_H3R Debug Levels
Error (globally enabled) LEVEL_ERROR
Warning (locally enabled) LEVEL_WARNING
Debug (locally disabled) LEVEL_INFO, LEVEL_INFO_EXT, LEVEL_ALL