<nomatch> and <noinput>
Earlier we saw that when an entry did not match the grammar for a field, the server played a default message before returning to the field. Listing 2 shows how we can provide our own nomatch and noinput handlers when the voice server does not understand or get’s no input from the user.
To fine-tune the voice response, it’s also possible to add a count attribute to the nomatch or noinput elements. For example, when a nomatch event is thrown for the first time, the nomatch element with a count of 1 will be executed. Upon the second instance of the same event, the server will look for a handler with a count value of 2, if one exists—otherwise, it will simply execute the catch handler with the count of 1 again.