Executing Unified Messaging grammar generation
Grammar generation on a Unified Messaging server, using the galgrammargenerator.exe tool, should be the last step in UM deployment. In this excerpt from "Microsoft Exchange Server 2007: The Complete Reference," get information on how updating your grammar files can improve Automatic Speed Recognition (ASR) in the UM server speech engine.
Generating grammar files
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
 |
||||
|
|
|||
|
||||
The grammar files also define what options are available to a caller. When the Exchange Unified Messaging servers are deployed, they generate the grammar files based on default settings. The default settings will work fine the majority of the time, but Microsoft recommends that grammar generation be performed manually under the following circumstances:
- When you complete a new installation of the Unified Messaging server role
- After creating a new UM dial plan, UM Auto Attendant, custom address list or custom distribution list
- After creating UM-enabled users
- After modifying a UM dial plan
- After modifying a UM Auto Attendant
By default, grammar generation occurs every day at 2:00 A.M. The schedule can be modified with Set-UMserver in the EMS.
To make sure that the very first users of the Unified Messaging services are able to connect without errors, you should plan on running the executable galgrammargenerator.exe as the last step in the deployment process before allowing users to access the Unified Messaging servers. The grammar files are updated when:
- Unified Messaging servers join a UM dial plan
- Default or custom update schedules occur
- The file galgrammargenerator.exe is manually run
The galgrammargenerator.exe tool should be used to force an update when changes occur in the organization that affect the users' ability to find other recipients. As a side benefit, the tool can be used to repair missing or corrupted grammar files. Table 6 lists all the possible switches available with the tool.
| Switch | Description |
| -d <dialplan> | Creates a grammar file for a specified UM dial plan. |
| -g | Generates the grammar file. |
| -l | Generates a grammar file for a distribution list. |
| -o | Generates a log file. The default path is UnifiedMessagingTemp. |
| -p | Preloads all generated grammars into the Microsoft Speech Server platform. |
| -s <UMserver> | Creates a grammar file for each UM dial plan to which the specified Unified Messaging server belongs. |
| -u | Creates or updates DTMF maps for users who are enabled for UM and who are not enabled for UM. |
| -x | Defines the speech filter list that is used in XML format. |
The recommended command to issue after the initial deployment of a Unified Messaging Server is:
Galgrammargenerator.exe -s
Microsoft Exchange Server 2007 Unified Messaging for administrators
Home: Introduction to Unified Messaging on Exchange 2007
Part 1: An intro to voice systems for Exchange administrators
Part 2: Unified Messaging features in Exchange Server 2007
Part 3: Defining Exchange Unified Messaging architecture
Part 4: Deploying Unified Messaging servers on Exchange Server 2007
Part 5: Comparing VoIP PBX solutions for Unified Messaging
Part 6: Integrating Unified Messaging servers with a VoIP solution
Part 7: Creating a Unified Messaging Dial Plan
Part 8: Configuring a Unified Messaging IP gateway
Part 9: Mailbox policy configuration for Unified Messaging
Part 10: Creating and assigning a Unified Messaging hunt group
Part 11: Dialing rules and restrictions for Unified Messaging users
Part 12: Assigning Unified Messaging dialing rules to a mailbox policy
Part 13: Executing Unified Messaging grammar generation
Part 14: Enabling Unified Messaging mailboxes and users
 |
This chapter excerpt from Microsoft Exchange Server 2007: The Complete Reference, by Richard Luckett, William Lefkovics and Bharat Suneja, is printed with permission from McGraw-Hill Osborne Media, Copyright 2008. Click here for the chapter download or purchase the book here. |
Start the conversation
0 comments