Sample context file
The following code shows a sample context file.
<?xml version="1.0"?>
<context>
<property name="confidencelevel" value=".95"/>
<!-- As with <property>s in VoiceXML, if a <property> occurs
more than once in the same scope, the last seen value takes
precedence. -->
<property name="confidencelevel" value=".85"/>
<!-- Most Nuance extensions to VoiceXML <property>s are
supported.-->
<property name="nuance.packagename" value="en-US_configA"/>
<!-- All contexts (outermost or otherwise) may contain nested
contexts.-->
<context>
<!-- The semantics of nested <context>s are similar to those
in VoiceXML. <property>s contained within enclosing
<context>s are included "as if by copy" into nested
<context>s, giving priority to <property>s within the inner
context. Here, the confidencelevel <property> is given
the value .75, overriding the value .85 supplied from the
enclosing <context>. -->
<property name="confidencelevel" value=".75"/>
<!-- <property>s need not override enclosing <property>s to
take effect. -->
<property name="maxnbest" value="5"/>
<!-- The innermost "leaf" contexts must be labeled with an
identifier that is unique to the entire context file.-->
<context id="Account_Balance">
<!-- When specifying VoiceXML time-based <property>s, the
same time conventions apply. Use s for seconds, ms for
milliseconds; defaults to milliseconds.-->
<property name="timeout" value="3s"/>
</context>
</context>
<!-- Every <context> may contain several nested <context>s.
These child contexts may themselves be parent contexts (as in
the previous example) or leaf contexts (as in this example).
-->
<context id="Account_Maintenance">
<!-- Nuance recommends that a context file contain either
standard VoiceXML properties or NVP service properties
exclusively. The following example is discouraged. -->
<property name="nuance.core.client.AllowBargein" value="true"/>
</context>
<!-- Example of an empty context used to get parent’s default
values. -->
<context id="Description"/>
</context>
