Hi,
There is a welcome message, post that IVR will ask customer to enter the CARD No or CIN Number,
Customers are entering the CARD No or CIN Number before completing welcome prompt, But when customer starts enter the Digits(CARD No or CIN). it supposed to stop playing the prompt. But this not happening, Please advise.

Already we set Bargin = true, Still it's continuing to play prompt.

Please open a tech support request (link to the left) and provide the VXML script you are working with (or the appropriate subset with the problem), and we can compare it to other work and see if we can find the issue. Without access to your script I can only speculate or give broad guidance.

I know that the message drop and blast record announcement web service's VXML handling properly allows interruption. If you have installed this package and have it working, you could take a look at the VXML that is being used there and try to determine what the difference in the two scripts is.

Please find the VXML Script
<audio src="http://192.168.0.1/prompts/PP/10001.ulaw"></audio>
</prompt>
<prompt bargein="true" timeout="5s">
<audio src="http://192.168.0.1/prompts/PP/10001.ulaw"></audio>
</prompt>

<form id="WelcomeAnnc_PP">
<block><assign name="currentNode" expr="'WelcomeAnnc_PP'"/>
<log>
Testing the application
</log>
<prompt bargein="true" bargeintype="speech" timeout="5s">
<audio src="http://192.168.0.1/prompts/PP/10001.ulaw"></audio>
</prompt>
<goto expr="'#next_page'"/>
</block>
</form>

Please open a tech support request (link to the left)

based on the subset of the VXML page you provided...

here are our guesses.



I'd need to see the entire VXML page but from the small segment I see in the post, I think the problem may be they don't have a grammar defined. If there is no grammar the system is not expecting input so you won't get any bargein behavior. Also, they may want to put the bargintype in all of the prompt tags. As an alternative, they can also assign bargein and bargeintype properties in the page so the scope covers all prompts in a page. Or they could put the properties in the root document scope to cover all prompts in the entire application. Then they don't need to set it for all of the individual prompt tags.