PreviousNextIndex
Nodes and Palette Options > Detailed Palette Option Descriptions > No Input
 
No Input

Type

Event handler

Available from

Purpose

When a caller does not respond to a request for input within a specified period of time, the system throws a No Input event. The No Input event handler makes it possible to specify how the system responds when these No Input events are thrown.

Behavior

Within the scope defined for it, the No Input event handler waits for a No Input event to be thrown. When such an event is thrown, the No Input event handler responds according to the options you use with it. See the next section, "Properties."

The No Input event handler responds to a No Input event anywhere within the scope of the handler. For example, if you place the No Input event handler in the AppRoot node, it acts as a global event handler for No Input events. It can catch No Input events no matter where in the application the events are thrown. If you place the No Input event handler in another node, however, it can catch a No Input event only if it is thrown while in that node. If you place the No Input event handler underneath a node item, it can catch the No Input event only if it is thrown within that node item.

A No Input event handler at the node item level overrides a No Input event handler at the node level. Likewise, a No Input event handler at the node level overrides a No Input event handler at the AppRoot, or global, level.

Note:

This event handler is one of the default event handlers defined by the W3C VoiceXML 2.0 Recommendation and it is identified as a noinput event handler.

Properties

The No Input event handler has no inherent properties, but you must use one or more of the following options with it:


PreviousNextIndex

©2009, Avaya Inc. All rights reserved.