Recognizer START-INPUT-TIMERS

This request is sent from the client to the recognizer resource when it knows that a kill-on-barge-in prompt has finished playing.  This is useful in the scenario when the recognition and synthesizer engines are not in the same session.  

When a kill-on-barge-in prompt is being played, the client may want a RECOGNIZE request to be simultaneously active so that it can detect and implement kill-on-barge-in.  But at the same time the client doesn't want the recognizer to start the No-Input Timer until the prompt is finished.

The Start-Input-Timers header field in the RECOGNIZE request allows the client to specify whether or not the timers should be started immediately. 

If this value is not set to true in the RECOGNIZE request, the recognizer resource will not start the timers until the client sends a START-INPUT-TIMERS method to the recognizer resource.

In the above example, the RECOGNIZE request explicitly indicates that the No-Input-Timer should not begin until a subsequent START-INPUT-TIMERS request is sent by the client. This is indicated by the client setting the Start-Input-Timers header value to false.

Alternatively, if the client wanted to begin the No-Input-Timer as soon as the RECOGNIZE request is processed, this could be done by setting this Start-Input-Timers header to a value of true, as shown here:

Note that this is an MRCPv2 method, and should not be confused with the similar RECOGNITION-START-TIMERS method belonging to MRCPv1, which performs a similar function.

MRCPv2 START-INPUT-TIMERS Example: