Trace Components
Component | Description |
APP | VXML2 Application logging |
CALL | Call handling |
CCXML_LOG | Tracing intended for the log file (including the <log> element) from CCXML |
CCXML_PARS | CCXML Parser (executing event processor and handling tags) |
CCXML_RUNT | CCXML Runtime environment (Generating events, handling events from the call/vxml) |
CDR | Call detail records |
CODEC | Audio codec |
COMMAND | BVR command message handling |
CONFIG | Configuration |
CORE | Core tracing |
DTMFCOMP | DTMF grammar |
DTNA | DTNA kernel - not used |
IFIX | All interim fix/debug related tracing |
MRCP | MRCPv2 (not stack) |
MRCP_STACK | MRCPv2 stack |
SDP | SDP handling |
SIGNALLING | Signalling handling |
SIP | SIP handling (not stack) |
SIP_MONITOR | SIP messages |
SIPSTACK | SIP stack |
STREAMING | Audio commands/handling |
VXI | VXML2 browser |
VXML | VXML2 |
Configuration setting of Component trace
Allows the trace level to be modified per-component. This section can appear multiple times in the trace.
The header for this section is [[component_trace_level]].
Name | Mandatory? | Type | Description |
component | Yes | String | The trace component to set the trace level for. Valid components are: ALL CCXML_PARS CCXML_RUNT For a more detailed description of what these components mean, see "Problem Determination". |
level | Yes | String | The trace level to set for the component. Valid levels are (in order of intensity): OFF ERROR WARNING INFO LOG TRACE DEBUG ENTRY EXIT INTENSIVE If a level is specified, any levels above that level will also be traced. For example, if the level is set to TRACE, all ERROR, WARNING, INFO, LOG and TRACE statements will appear in the log. For a more detailed description of what these levels mean, see "Problem Determination". |