Contents

Create Private Contact Grammar

This TUI tool creates an ABNF grammar file containing the private contacts grammar according to the criteria specified as parameters. The grammar rule created by the tool has the following structure:

LeadingFiller Names TrailingFiller

The names are rendered depending on the various parameters. Assuming all options are enabled, the following rule fragment is rendered for each user:

[Jane] Doe | Jane [Doe] | Doe Jane.

Enabling the 'Last Name Optional' or 'First Name Optional' parameters will allow broader recognition (i.e. the callers don’t have to say the full name). However, for large organizations this will lead to lots of ambiguous matches, in particular for common names such as "Smith".

NOTE: All selected slots are always returned, even if the caller doesn’t say the corresponding component. For example, if the first name is optional and the user just says the last name of a person, the "firstname" slot will nevertheless be filled with the first name of the directory entry.

IMPORTANT: Do not use this tool to overwrite a preloaded grammar or a grammar that may be in use. Instead, a new grammar file with a unique name, for example by appending the current time and date, should be created. Rendering the private contacts list into the file may take quite some time. Overwriting a grammar file that may be used by the application could thus lead to a partially completed file being loaded and cause the grammar parser to fail. Creating a new file and only referencing it after it is completed prevents such problems. Use the Reco Add Preloaded Grammar tool to add/replace a preloaded grammar with the newly created private contact grammar.

Inputs

XML Document Handle

A XML document handle to be used to create the private contact grammar. Usually, this is the output of other voice recognition tools.

Grammar File Destination

A string variable of the full path of where the new grammar will be written.

Language

A string variable of the language to specify in the grammar.

If undefined, all users will be included.

Leading Filter

ABNF Rule fragment rendered as filler before the actual name tokens. For example:

[dial | call | (transfer | connect) [me] [to | with]]

NOTE: The filler must be in the SRGS ABNF format and is not rendered as optional. Thus, specifying "dial" as filler will mean that the user must say "dial" followed by the name for the grammar to match.

If undefined, no leading filler is rendered.

Trailing Filter

ABNF Rule fragment rendered as filler after the actual name tokens. For example:

[please]

NOTE: The filler must be in the SRGS ABNF format and is not rendered as optional.
If undefined, no trailing filler is rendered.

Custom Headers

Custom header fields and rules to inject into the SRGS ABNF grammar. The following headers are created by the tool and cannot be injected: 'mode', 'language', 'root'.

First Name Optional

This checkbox specifies whether the grammar should be rendered with an optional first name. If left unchecked, the caller must say the first name of the person. If checked, the fist name of the user is optional and callers may just say the last name.

Last Name Optional

This checkbox specifies whether the grammar should be rendered with an optional last name. If left unchecked, the caller must say the last name. If checked, the last name of the user is optional in the grammar and callers may just say the first name.

Recognize "Last, First" as well?

This checkbox specifies whether user may say "last name, first name" in addition to "first name, last name". If left unchecked, the grammar expects "first name, last name". If checked, the user may say either "first name, last name" or "last name, first name".