Simulation Profiles
Preferences > Avaya > Application Simulation > Dialog Designer Simulation > Simulation Profiles
The Simulation Preferences area allows the developer to define simulation profiles. Profiles include calling parameters, Dialog Designer runtime session parameters, Dialog Designer scripts, and administrative variable definitions. Click the Edit button to display the following tabs:
- New - To define a new profile, enter a name of the profile when prompted, then select it among the Available Profiles, and click Edit to edit the profile parameters.
- Edit - Click this button to edit the defined parameters of the profile.
- Remove - Select a profile from the list, and click this button to remove it.
- Import - Click this button to import a profile XML file. To view the expected format, create a dummy profile, and then export it. Edit the profile as desired, and import the profile again.
- Export - Click this button to export an existing profile.
See the following sections for more details on the profile parameter tabs.
Call Tab
In the Call Tab, specify the communication numbers to use in the simulation..
Simulation Profiles-Call Tab
|
Setting
|
Description
|
|---|
Calling Number
| Simulates ANI. Enter the number that represents the originating telephone number in this field. Use numbers only.
Note: If you use characters other than numbers, the Avaya Application Simulator passes them along exactly as you enter them in this field. However, in a live system with a deployed application, only numbers are passed to the application. For this reason, Avaya recommends that you use only numbers in this field during simulations. |
Called Number
| Simulates DNIS. Enter the number that represents the telephone number the caller must dial to get to this application. Use numbers only.
Note: If you use characters other than numbers, the Avaya Application Simulator passes them along exactly as you enter them in this field. However, in a live system with a deployed application, only numbers are passed to the application. For this reason, Avaya recommends that you use only numbers in this field during simulations. |
Converse On Data
| Lets you simulate data that you can receive from the switch.
Note: The application must be specifically designed to collect converse on values. For setting up converse on data, on the actual runtime platform requires configuration on both the switch and vectors as well as the Interactive Response or Voice Portal. For more information on working with converse on data, - For Voice Portal, refer section "Symptoms of common MPP problems" section of Troubleshooting Voice Portal Guide.
- For Interactive Response, refer "Miscellaneous instructions" section of Application Development Guide and "ASAI versus the converse vector step" section of Specialized applications Guide.
|
Dialog Designer RunTime Session
The DDRun Time Session tab allows you to configure parameters to simulate different settings or configurations in VXML and CCXML applications. It is like you are launching the application via a VXML or CCXML Web service on the Voice Portal.
|
Tab Area
|
Description and Usage
|
|---|
Call Control Protocol Parameters
| Allows protocol specific parameters to be set, and passed when simulating your application. Entered parameters must be the following format: session.connection[<protocol_name>].*
Enter a protocol name and version. Then enter a parameter name and value, and click Add Param.
In a real deployment, these values might otherwise be set automatically by the supporting platform (for example, Voice Portal platform).
|
Call Control Session Parameters
| Allows session-based parameters to be set, for a VXML session to simulate launching the CCXML Web services. Entered parameters must be the following format:
session.*
Enter a protocol name and version. Then enter a parameter name and value, and click Add Param.
In a real deployment, these values might otherwise be set automatically by the supporting platform (for example, the Voice Portal platform).
|
AAI/UUI Options
| Allows Voice Portal specific UUI/AAI parameters to be set. There are two modes:
- Shared - Means that the format of the configured value is fixed, and as specified by Voice Portal.
- Service Provider - Means that the value is uninterpreted.
If the mode is shared, the following considerations apply:
- VXML - session.connection.aai is unpacked into the shareduui variable; session.avaya.uui.mode stored in session:sharedmode; if there is a UCID in the AAI, it is decoded into session.avaya.ucid and session:sessionlabel is set to the UCID
- CCXML - connection.aai is unpacked into connection.avaya.uui.shared; mode is in connection.avaya.uui.mode; if there is a UCID in the AAI, it is decoded into connection.avaya.ucid
An example of the AAI is:
- 12, 01DR12345678; FA, 0001001C46E70028
where 12 and FA is the application ID, and the remaining characters in the string are the values, respectively.
For additional information on UUI data passed in SIP headers, refer to the "SIP application support" section of Administering Voice Portal Guide.
|
Call Classification
| These parameters allow you to simulate different types of calls at the voice platform in CCXML. The types of calls are:
- live_voice - person answered
- fax_calling_tone - sending tone, inbound call from a fax machine
- timeout - timeout on classification expired
The call classifications are passed to an application via the "call classification" query string variable to the Web service.
|
Speech Application Parameters
| These parameters, when set to values in a VXML session take the parameters in the namelist. Entered parameters must be the following format: session.*
Enter a protocol name and version. Then enter a parameter name and value, and click Add Param.
The parameter is added to the table list, and passed to the simulated application. It allows you to test your application as though it was launched in CCXML.
In a real deployment, these values might otherwise be set automatically by the supporting platform (for example, IR or the Voice Portal platform).
|
Dialog Designer Scripts
This tab provides options to enable and import connector and application simulation file scripts. The following table lists some sample scripts as examples:
Simulation Profiles-DD Scripts Tab
|
Setting
|
Description
|
|---|
| Connector Scripts
|
Enable connector simulation file processing
| Select this option to enable connector simulation processing for the designated file.
|
Simulation file name
| Click Browse to select a connector simulation file script.
|
| Application Scripts
|
Enable Application simulation file processing
| Select this option to enable application simulation processing for the designated file.
|
Simulation file name
| Click Browse to select a application simulation file script.
|
Call Control and Speech Input Script Example
As an alternative to simulating caller responses and other inputs during simulation, create an XML script to simulate them automatically running a simulation. Following are some general command guidelines and examples of scripts to simulate caller response.
Following is a list of all the valid commands used in the Call Control and Speech Input scripts. Note that the "value" attribute for the rec asr, rec dtmf, record err, and record dtmf will vary. For a rec type asr, you can have one or more items. Using multiple items allows you to simulate n-best results.
<?xml version="1.0" encoding ="UTF-8"?>
<callscript>
<call>
<command name="rec" type="asr">
<item value="dog blue"/>
</command>
<command name="rec" type="asr">
<item value="dog blue" confidence=".7"/>
</command>
<command name="rec" type="asr">
<item value="dog blue"/>
<item value="fog blue"/>
</command>
<command name="rec" type="asr">
<item value="dog blue" conficence=".7"/>
<item value="fog blue" conficence=".4"/>
</command>
<command name="rec" type="dtmf" value="1" />
<command name="rec" type="err" value="nomatch" />
<command name="rec" type="err" value="noinput" />
<command name="tel" type="hangup" delay="10"/>
<command name="tel" type="answered"/>
<command name="tel" type="answered" value="live_voice"/>
<command name="tel" type="progress" value="some reason value"/>
<command name="tel" type="busy"/>
<command name="tel" type="noanswer"/>
<command name="record" type="max"/>
<command name="record" type="done"/>
<command name="record" type="err" value="45" />
<command name="record" type="dtmf" value="1" />
<command name="quit" type="" value="" />
<command name="merge" type="" value="ok" />
<command name="merge" type="" value="fail" />
</call>
</callscript>
Example of handling a transfer, far end hangs up after 10 seconds:
<?xml version="1.0" encoding ="UTF-8"?>
<callscript>
<call>
</call>
<call>
<command name="tel" type="answered" value="live_voice"/>
<command name="tel" type="hangup" delay="10"/>
</call>
</callscript>
Example of handling a transfer, near end hangs up after 10 seconds:
<?xml version="1.0" encoding ="UTF-8"?>
<callscript>
<call>
<command name="tel" type="hangup delay="10"/>
</call>
<call>
<command name="tel" type="answered"/>
</call>
</callscript>
Example of handling a transfer, hot word recognition:
<?xml version="1.0" encoding ="UTF-8"?>
<callscript>
<call>
<command name="rec" type="asr">
<item value="dog blue"/>
</command>
</call>
<call>
<command name="tel" type="answered"/>
</call>
</callscript>
Example of merging 2 calls:
<?xml version="1.0" encoding="UTF-8"?>
<callscript>
<call>
<command name="merge" value="okay"/>
</call>
<call>
<command name="tel" type="answered"/>
<command name="merge" value="okay"/>
</call>
</callscript>
Note that any command can have a delay attribute. This attribute specifies the time taken to activate a command after the processing of the previous command. In the far end disconnect example, the hangup is sent 10 seconds after the call is answered. In the near end disconnect the hangup is sent 10 seconds after the initial incoming call. Note that the first call in the script never has an answer that is implicit. If you do answer the incoming call, an error will result.
Variable Administration
Simulation Profiles-Variable Administration Tab
|
Setting
|
Description
|
|---|
Name
| Name of the configurable variable
|
Value
| Value for the configurable variable used for simulation
|
Param Name
| Configurable name input. If you click the Add Variable button, the variable gets added to the table
|
Param Value
| Configurable variable value input that pairs the variable name
|
Import Variables
| This button launches the project selector dialog box. The project selector dialog box allows you to choose the project to import all its configurable variables into a table instead of typing them in one-by-one
|
