PreviousNextIndex
Creating Scripts for Testing > Using Scripts to Simulate Caller Responses > Creating a Response Script
 
Creating a Response Script

To work correctly with the Avaya Voice Browser (AVB), the response script must be in the form of an XML file. You can use any good text editor to create the file.

When creating your script, use the following guidelines:

Note:

For a sample script that illustrates these guidelines, see Sample Response Script.

Note:

You can have one or multiple item entries for each ASR recognition response. If you want to simulate only a single response, use only one item entry. If you want to simulate multiple responses to a single ASR attempt, you can add as many item entries as you need.

Tip:

Avaya Voice Browser response scripts are useful when working on long and complex applications. An excellent way to use scripts is to enter only as many responses as needed to get to the point in the application that is currently being worked on.     For example, suppose an application prompts the caller for twelve different responses. You have completed the application up to the sixth prompt and are working on the seventh and eighth prompts. A script can be created that provides responses for only the first six prompts. In other words, the Avaya Voice Browser uses the scripted responses for the first six prompts and then goes into normal interactive mode so that the seventh and eighth prompts can be tested manually.

Valid Values for Use in Scripts 

Name

Type

Value

Comments

rec - Recognition responses

 

asr -  spoken responses

Any expected spoken response.

Valid values include any item in an active grammar.

 

dtmf -  touchtone key presses

One or more key presses

Valid values include numbers, star (*), and pound sign (#) characters.

 

err -  error

nomatch

Simulates a situation in which no caller response matches an expected response.

 

noinput

Simulates a situation in which the caller did not respond at all.

tel - Telephony system responses

 

hangup

n/a

No value is required, because this type simulates a caller hanging up. You can either leave this field blank or leave it out entirely.

 

err - error

trans_noanswer

Simulates an attempted transfer in which the destination number did not answer.

  

trans_busy

Simulates an attempted transfer in which the destination number was busy.

  

trans_netbusy

Simulates an attempted transfer in which the network was not able to reach the destination because all network lines were busy.

  

trans_fardiscon

Simulates a successful call transfer in which the party at the other end hung up.

  

trans_netdiscon

Simulates a successful call transfer in which the network for some reason disconnected the call prematurely.

  

trans_maxdiscon

Simulates a successful call transfer which was terminated by the system because the length of the call exceeded the maximum allowable amount of time.

record - Responses recorded by the system

Note: This option does not actually record any responses.

.

max -  maximum record time

n/a

Simulates a situation in which the caller exceeded the maximum allowable length of time for a recording and the system terminated the recording.

You can either leave the value field blank or leave it out entirely.

 

done

n/a

Simulates a situation in which the caller completed the recording and signaled that it was complete.

You can either leave the value field blank or leave it out entirely.

 

err -  error

Any positive integer

Simulates a situation in which there was an error in the recording. The value field contains a numeric code that identifies the cause of the error.

 

dtmf -  touchtone key press

One key press

Simulates the key the caller pressed to terminate the recording.

quit

 

n/a

n/a

Terminates the script and the simulation. Use this option only when you want the script to terminate the simulation.

When you use this option, you can either leave the type and value fields blank or leave them out entirely.


PreviousNextIndex

©2009, Avaya Inc. All rights reserved.