`PSESM00093`

Event name: PSESM00093
Event text: Speech recognition engine was not found by vendor: {0} in Application: {1} Session: {2} Grammar with ID: {3} cannot be loaded
Event level: Warning event. No alarm is generated
Trigger component: MPP Session Manager process

Problem description

{0} - The value of the com.avaya.asr.vendor VXML property that failed to match a configured speech recognition engine for this application.

{1} - The name of the related application.

{2} - The ID of the related session.

{3} - The ID of the grammar that failed to load.

The SessionManager component encountered an error when attempting to load a VXML grammar. A matching speech recognition engine for this grammar could not be found in this application based on the com.avaya.asr.vendor VXML property that was in scope.

Common causes

A speech application (OD or VXML) has defined an invalid or empty vendor property when loading a grammar.
A speech application (OD or VXML) has defined a valid vendor property when loading a grammar, however the specified speech recognition engine is not assigned to the application.
A speech application (OD or VXML) has multiple speech vendors configured, however a vendor property was not defined in scope when loading a grammar.

Proposed Solution

Procedure

Review the application configuration in Experience Portal and the application (VXML or OD) that reported the error.
1. Ensure that the speech vendor outputted in the log event correlates with a speech recognition engine that is assigned to the application.
2. If multiple speech recognition vendors are assigned to the application, ensure that all grammars defined in the application have a valid com.avaya.asr.vendor property in scope. The value of the property must match a speech recognition engine assigned to the application.
3. If a single speech recognition vendor is assigned to the Application, you do not need to specify a com.avaya.asr.vendor property when defining grammars. If a vendor property is defined in this application, it can be removed. Alternatively, ensure that the vendor property is valid and matches the speech recognition engine assigned to the application.
4. Review the spelling of all defined com.avaya.asr.vendor properties, both name and value, in the application.
Check the following location for log files in conjunction with the Grammar ID and Session ID to know which grammar failed to load:
- $AVAYA_MPP_HOME/logs/process/SessMgr
- $AVAYA_MPP_HOME/logs/process/VB