![]() |
|
![]() ![]() ![]() |
Nodes and Palette Options > Detailed Palette Option Descriptions > No Match | |
![]() |
No Match ![]() |
Type
Event handler
Available from
Purpose
When a caller does not respond to a request for input with a response that matches any that the system is set to recognize, the system throws a No Match event. The No Match event handler makes it possible to specify how the system responds when these No Match events are thrown.
Behavior
Within the scope defined for it, the No Match event handler waits for a No Match event to be thrown. When such an event is thrown, the No Match event handler responds according to the options you use with it. See the next section, "Properties."
The No Match event handler responds to a No Match event anywhere within the scope of the handler. For example, if you place the No Match event handler in the AppRoot node, it acts as a global event handler for No Match events. It can catch No Match events no matter where in the application the events are thrown. If you place the No Match event handler in another node, however, it can catch a No Match event only if it is thrown while in that node. If you place the No Match event handler underneath a node item, it can catch the No Match event only if it is thrown within that node item.
A No Match event handler at the node item level overrides a No Match event handler at the node level. Likewise, a No Match event handler at the node level overrides a No Match event handler at the AppRoot, or global, level.
This event handler is one of the default event handlers defined by the W3C VoiceXML 2.0 Recommendation. There it is identified as a nomatch event handler.
Properties
The No Match event handler has no inherent properties, but you must use one or more of the following options with it:
![]() ![]() ![]() |
©2009, Avaya Inc. All rights reserved.
|