-
-
Save Jared-Prime/58287b934d982b2cc62f to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shanmugham, et al. Informational [Page 46] | |
RFC 4463 MRCP by Cisco, Nuance, and Speechworks April 2006 | |
001 no-match RECOGNIZE completed, but no match | |
was found | |
002 no-input-timeout | |
RECOGNIZE completed without a match | |
due to a no-input-timeout | |
003 recognition-timeout | |
RECOGNIZE completed without a match | |
due to a recognition-timeout | |
004 gram-load-failure | |
RECOGNIZE failed due grammar load | |
failure. | |
005 gram-comp-failure | |
RECOGNIZE failed due to grammar | |
compilation failure. | |
006 error RECOGNIZE request terminated | |
prematurely due to a recognizer | |
error. | |
007 speech-too-early | |
RECOGNIZE request terminated because | |
speech was too early. | |
008 too-much-speech-timeout | |
RECOGNIZE request terminated because | |
speech was too long. | |
009 uri-failure Failure accessing a URI. | |
010 language-unsupported | |
Language not supported. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Burnett & Shanmugham Standards Track [Page 80] | |
RFC 6787 MRCPv2 November 2012 | |
+------------+-----------------------+------------------------------+ | |
| Cause-Code | Cause-Name | Description | | |
+------------+-----------------------+------------------------------+ | |
| 000 | success | RECOGNIZE completed with a | | |
| | | match or DEFINE-GRAMMAR | | |
| | | succeeded in downloading and | | |
| | | compiling the grammar. | | |
| | | | | |
| 001 | no-match | RECOGNIZE completed, but no | | |
| | | match was found. | | |
| | | | | |
| 002 | no-input-timeout | RECOGNIZE completed without | | |
| | | a match due to a | | |
| | | no-input-timeout. | | |
| | | | | |
| 003 | hotword-maxtime | RECOGNIZE in hotword mode | | |
| | | completed without a match | | |
| | | due to a | | |
| | | recognition-timeout. | | |
| | | | | |
| 004 | grammar-load-failure | RECOGNIZE failed due to | | |
| | | grammar load failure. | | |
| | | | | |
| 005 | grammar-compilation- | RECOGNIZE failed due to | | |
| | failure | grammar compilation failure. | | |
| | | | | |
| 006 | recognizer-error | RECOGNIZE request terminated | | |
| | | prematurely due to a | | |
| | | recognizer error. | | |
| | | | | |
| 007 | speech-too-early | RECOGNIZE request terminated | | |
| | | because speech was too | | |
| | | early. This happens when the | | |
| | | audio stream is already | | |
| | | "in-speech" when the | | |
| | | RECOGNIZE request was | | |
| | | received. | | |
| | | | | |
| 008 | success-maxtime | RECOGNIZE request terminated | | |
| | | because speech was too long | | |
| | | but whatever was spoken till | | |
| | | that point was a full match. | | |
| | | | | |
| 009 | uri-failure | Failure accessing a URI. | | |
| | | | | |
| 010 | language-unsupported | Language not supported. | | |
| | | | | |
Burnett & Shanmugham Standards Track [Page 81] | |
RFC 6787 MRCPv2 November 2012 | |
| 011 | cancelled | A new RECOGNIZE cancelled | | |
| | | this one, or a prior | | |
| | | RECOGNIZE failed while this | | |
| | | one was still in the queue. | | |
| | | | | |
| 012 | semantics-failure | Recognition succeeded, but | | |
| | | semantic interpretation of | | |
| | | the recognized input failed. | | |
| | | The RECOGNITION-COMPLETE | | |
| | | event MUST contain the | | |
| | | Recognition result with only | | |
| | | input text and no | | |
| | | interpretation. | | |
| | | | | |
| 013 | partial-match | Speech Incomplete Timeout | | |
| | | expired before there was a | | |
| | | full match. But whatever was | | |
| | | spoken till that point was a | | |
| | | partial match to one or more | | |
| | | grammars. | | |
| | | | | |
| 014 | partial-match-maxtime | The Recognition-Timeout | | |
| | | expired before full match | | |
| | | was achieved. But whatever | | |
| | | was spoken till that point | | |
| | | was a partial match to one | | |
| | | or more grammars. | | |
| | | | | |
| 015 | no-match-maxtime | The Recognition-Timeout | | |
| | | expired. Whatever was spoken | | |
| | | till that point did not | | |
| | | match any of the grammars. | | |
| | | This cause could also be | | |
| | | returned if the recognizer | | |
| | | does not support detecting | | |
| | | partial grammar matches. | | |
| | | | | |
| 016 | grammar-definition- | Any DEFINE-GRAMMAR error | | |
| | failure | other than | | |
| | | grammar-load-failure and | | |
| | | grammar-compilation-failure. | | |
+------------+-----------------------+------------------------------+ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment