Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Use this page to change an existing application.
This page contains the:
Field |
Description |
|---|---|
Zone |
The name of the zone where you want to add the application.
Note:
This field is displayed only if zones are configured in the system.
Note:
You cannot change the zone name. |
Name |
The name used to identify this application on the Experience Portal system. If you are using a Nuance server, the maximum length of this field is 32 characters.
Note:
You cannot change the application name. |
Enable |
Whether this application is available for use by the Experience Portal system. The default is Yes, which means the application is available. |
Type |
The type of Multipurpose Internet Mail Extensions (MIME) encoding used by this application. The options are:
Note:
Additional type options may be available if you have installed managed application on Experience Portal. For more information on managed application type, see the documentation delivered with the managed application. |
Message Type |
The system displays this field if you have selected either SMS or Email application. Each SMS or email application can have the following message types:
|
Reserved SIP Calls |
The option to reserve SIP ports for an application. This option is not available for SMS and email applications. The options are:
|
Requested |
The minimum or maximum number of the Reserved SIP Calls requested for the application. This field is enabled only when you select the Minimum or Maximum option in the Reserved SIP Calls field. |
Field |
Description |
|---|---|
Type |
The options are:
|
CCXML URL |
The HTTP path to the root document of the Call Control eXtensible Markup Language (CCXML) speech application. The URL must be in the format
Note:
Experience Portal uses the OktopousTM ccXML Interpreter. |
VoiceXML URL |
The HTTP path to the root document of the VoiceXML speech application. The URL must be in the format
|
SMS URL |
The HTTP path to the root document of the SMS application. The URL must be in the format
|
Email URL |
The HTTP path to the root document of the Email application. The URL must be in the format
|
HTML URL |
The HTTP path to the root document of the HTML application. The URL must be in the format
There are two types of HTML URLs:
|
Verify |
Instructs Experience Portal to open the associated root document in a new browser window. If the document cannot be found, the new browser window displays a file not found error.
Note:
Verify is not displayed if the URL(s) contains a secure HTTP protocol (https:), and the Mutual Certificate Authentication field is set to Yes. |
Mutual Certificate Authentication |
Enables mutual certificate authentication between the EPM/MPP and the application.
Important:
Do not enable this option if your application uses external grammars stored on the application server. The speech servers do not support mutual certificate authentication and therefore will not fetch the grammar from the application server.
If you select this option ensure that:
|
Basic Authentication |
Enables user name and password authentication between the EPM/MPP and the application. Ensure that the application server is configured to support basic configuration.
Important:
If you select the Basic Authentication option, Experience Portal displays:
Do not enable this option if your application uses external grammars stored on the application server and uses a Nuance speech server, as Nuance does not support basic authentication.
Note:
You can select both Mutual Certificate Authentication and Basic Authentication options. |
Notification Enabled |
A notification-type message displays the delivery status of an email or an SMS message. This field must be enabled for Orchestration Designer applications that are written to accept a notification-type message. The system displays this field if you select either SMS or Email type from the General Settings section. If you select Single or Load Balance: If Notification is enabled, Notification URL field is displayed. If Notification is not enabled, Notification URL field is not displayed. If you select Fail Over : If Notification is enabled, Notification URL1 and Notification URL2 fields are displayed. If Notification is not enabled, Notification URL field is not displayed. |
Notification URL |
Enter the URL of the SMS or Email notification. |
Field |
Description |
|---|---|
Engine Types |
If this application uses Automatic Speech Recognition (ASR) resources, this field lets you select the ASR engine type that will be used. The options are:
Select an individual entry in this list by clicking on it, or use Ctrl+Click and Shift+Click to select multiple entries. Then, click If you select an engine type, Experience Portal displays the following fields which are specific to an ASR speech server engine type:
|
Selected Engine Types |
The ASR engine types that you select in the Engine Types pane appear in this pane. |
Default Engine |
When multiple speech servers are added in the Selected Engine Types for an application, the Default Engine option becomes available. The Default Engine drop-down contains all engine values that have been added in the Selected Engine Types list. If the com.avaya.asr.vendor property is not specified in VXML/CCXML Application and multiple engines are selected:
This ensures that at least one engine is always selected, thereby helping to prevent errors and allowing grammars to load correctly for smooth recognition without manual intervention. |
Languages |
Displays all the languages that application servers can use on this system. Select an individual entry in this list by clicking on it, or use Ctrl+Click and Shift+Click to select multiple entries. Then, click This list is prepopulated with the list of the languages that were available for the designated ASR engine type when Experience Portal was released. It is maintained in a special file on the Experience Portal system and is not automatically updated. You must verify that the languages you select here are actually installed and available on the target ASR server. You can add more languages to this list by clicking Configuration>Speech Servers from the EPM menu and selecting Customize in the ASR tab.
Note:
If a speech application is configured to use more languages than are configured for any single ASR server, Experience Portal sends a |
Selected Languages |
All languages that you select in the Languages pane appear in this pane. |
Resources |
If an ASR speech server is selected, this field lets you select how the application acquires the ASR speech resource. The options are:
|
N Best List Length |
The maximum number of recognition results that the ASR engine can return.
Note:
If you are using Orchestration Designer, see the N-Best input form field description in your Orchestration Designer documentation. |
Speech Complete Timeout |
The number of milliseconds of silence required following user speech before the speech recognizer either accepts it and returns a result or reject it and returns a No Match event.
Enter an integer in this field.
This value is used when the recognizer currently has a complete match of an active grammar, and specifies how long it should wait for more input declaring a match. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar.
Tip:
Take care when setting this property. If you set the number too high, it can slow down system response time, even for successful recognitions. If you set the number too low, it can lead to an utterance being cut off prematurely. Reasonable values for this property are usually in the range of 5000 to 15000 milliseconds. |
Speech Incomplete Timeout |
The number of milliseconds of silence following user speech after which a recognizer finalizes a result.
Enter an integer in this field.
The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the speech recognizer rejects the partial result and returns a No Match event.
Tip:
Take care when setting this property. If you set the number too high, it can slow down system response time, even for successful recognitions. If you set the number too low, it can lead to an utterance being cut off prematurely. This property is usually set lower than the Speech Complete Timeout but high enough to allow for callers to pause mid-utterance.
Note:
If you are using Orchestration Designer, see the Timeout Incomplete field description in your Orchestration Designer documentation. |
Project ID |
The Google Dialogflow BOT Project ID. This field is displayed only when you select Dialogflow in the ASR Engine Types field. |
Location |
The region for the Google Dialogflow BOT. The system will default to using the Global region if you do not specify any value in this field. This field is displayed only when you select Dialogflow in the ASR Engine Types field. |
VAD Parameters |
The Voice Activity Detection (VAD) parameters. This field is displayed only when you select Dialogflow or Naunce DLGaaS in the ASR Engine Types field. |
Vendor Parameters |
Any vendor-specific or platform-specific parameters that the ASR server requires to function correctly with this speech application.
Note:
Contact your speech server provider for details on vendor parameters. These parameters must be in the general form For example, for Nuance DLGaaS, you may need to specify: ep.ThresholdSnr=12;Rec.PPR=1 |
Credentials |
The authentication credentials for communicating with a Google Speech Engine or Google Dialogflow Engine. The options are:
The Credentials field is displayed only when you select either Google Speech or Dialogflow in the ASR Engine Types field. For more information on the authentication credentials, refer to the Google Speech Engine or Google Dialogflow Engine documentation. |
Client ID |
The client authentication credentials ID for communicating with a Nuance DLGaaS engine. This field is displayed only when you select Nuance DLGaaS in the ASR Engine Type field. For more information on the client authentication credentials, see the Nuance DLGaaS documentation. |
Client Secret |
The client authentication credentials secret for communicating with a Nuance DLGaaS engine. This field is displayed only when you select Nuance DLGaaS in the ASR Engine Type field. For more information on the client authentication credentials, see the Nuance DLGaaS documentation. |
Field |
Description |
VAD Mode |
The Voice Activity Detection mode. VAD Mode determines whether local VAD, the VAD of the cloud speech provider, or a combination of both VADs are used. The VAD mode values are the following:
|
VAD Type |
The Voice Activity Detection algorithm type. The options are:
Note:
This field is displayed only when you set the VAD Mode to Enabled or Hybrid. |
Starting Minimum Energy |
Minimum energy threshold required for frame analysis during the barge-in phase of speech input. Enter a value in the range 0 to 16,383. The default value is 2048.
Note:
This field is displayed only when you select GMM as the VAD Type. |
Starting Minimum Energy Scale |
Power of two scale factor for the minimum energy threshold during the barge-in phase of speech input. Enter a value in the range 0 to 32. The default value is 6.
Note:
This field is displayed only when you select GMM as the VAD Type. |
Starting Minimum Energy Frames |
Minimum number of consecutive frames with speech energy required to trigger the VAD during the barge-in phase of speech input. Enter a value in the range 1 to 100. The default value is 3.
Note:
This field is displayed only when you select GMM as the VAD Type. |
Interim Minimum Energy |
Minimum energy threshold required for frame analysis after interruptible prompts are finished playing. Enter a value in the range 0 to 16,383. The default value is 2048.
Note:
This field is displayed only when you select GMM as the VAD Type. |
Interim Minimum Energy Scale |
Power of two scale factor for the minimum energy threshold after interruptible prompts are finished playing. Enter a value in the range 0 to 32. The default value is 6.
Note:
This field is displayed only when you select GMM as the VAD Type. |
Interim Minimum Energy Frames |
Minimum number of consecutive frames with speech energy required to trigger the VAD after interruptible prompts are finished playing. Enter a value in the range 1 to 100. The default value is 3.
Note:
This field is displayed only when you select GMM as the VAD Type. |
Starting Noise Floor |
Minimum value for adaptive energy threshold during the barge-in phase of speech input. Enter a value in the range 0 to 100. The default value is 22.0
Note:
This field is displayed only when you select Inqa as the VAD Type. |
Starting Noise Offset |
Offset value, relative to the adaptive energy threshold, required for frame analysis during the barge-in phase of speech input. Enter a value in the range 0 to 100. The default value is 1.0.
Note:
This field is displayed only when you select Inqa as the VAD Type. |
Interim Noise Floor |
Minimum value for adaptive energy threshold after interruptible prompts are finished playing. Enter a value in the range 0 to 100. The default value is 22.0.
Note:
This field is displayed only when you select Inqa as the VAD Type. |
Interim Noise Offset |
Offset value, relative to the adaptive energy threshold, required for frame analysis after interruptible prompts are finished playing. Enter a value in the range 0 to 100. The default value is 1.0.
Note:
This field is displayed only when you select Inqa as the VAD Type. |
Field |
Description |
TTS |
If this application uses Text-to-Speech (TTS) resources, this field lets you select the TTS engine type that will be used. The options are:
|
Voices |
If a TTS engine is selected, this field displays the voices configured for the TTS servers of that engine type on the Experience Portal system. Select one or more default voices for this application. Your selections must match exactly the TTS voice defined in the speech application. Use Ctrl+Click and Shift+Click to make more than one selection from this list. The first selected voice becomes the default for this application. Then, click
Note:
You can switch languages within a single speech application, provided all the required languages are configured on the same TTS server. If a speech application is configured to use more language/voice combinations than are configured for any single TTS server, Experience Portal sends a No TTS Resource exception to the application. What happens then depends on the event handler that the application uses. |
Selected Voices |
Displays the selected voices that the TTS server is configured to use. |
Experience Portal uses the information you enter in this group to make a master list of all telephone numbers and Universal Resource Indicators (URIs) that are mapped to specific applications. It then takes the number or URI dialed by the caller as input and determines which speech application is assigned to handle that number.
If you do not map any phone numbers or URIs to an application, then that application automatically handles any calls that come from numbers or URIs that are not otherwise mapped. However, you can only have one such application on the system. If you attempt to configure a second application without a DNIS or URI, the system generates an error.
Field or Button |
Description |
|---|---|
Application Launch type radio buttons |
The options are:
Note:
The rest of the fields in this section are displayed only when you select the Inbound option. |
Application Launch Parameters for Email Application |
When defining Inbound Email applications, you can configure the launch parameters for the applications. The launch parameters allow you to assign multiple applications to a common incoming number or incoming email address. When a message arrives, the system checks if the message matches the options specified in the launch parameters. If the parameters match, the application receives the message, subject to the application launch order. The options are:
Note:
Additional Launch Parameters:
To add multiple launch parameters, click Add. To remove a launch parameter, click Remove. |
Number type radio buttons for Voice Application |
The options are:
|
Called Number |
The definition of this field depends on the selected number type.
You can enter from 1 to 15 digits. Do not include spaces or special characters such as (, ), or -. |
To |
Enter the highest telephone number in the range you want to associate with the application. If you selected Number Range as the number type, this field is displayed. If you selected any other number type, this field is not available. |
Called URI |
Enter the URI you want to associate with the application. If you selected URI as the number type, this field is displayed. If you have selected any other number type, this field is not available. You can use any valid regular expression such as the following:
Note:
Do not enter leading sip: or sips: in this field. Experience Portal strips these characters from the URI that is received on SIP INVITE before comparing with the values that are entered in this field. |
Add |
Associates the number, range of numbers, or URI with the application. After you click Add, the specified number, range of numbers, or URI appears in the display text box. |
Number type radio buttons for SMS Application |
When defining the Inbound SMS applications, you must configure the short codes for these applications.
The options are:
|
Short Code/Long Number |
The definition of this field depends on the selected number type. If the number type is:
|
Short Code Expression |
If you select the number type Expression, associate this Short Code Expression with the application. You can use any valid regular expression such as the following:
If you select any other number type, this field is not available. |
Display text box |
If you have selected VoiceXML or CCXML Application, this field displays all the DNIS numbers and URIs that are mapped to the speech application. If you have selected SMS Application, this field displays the short codes of the application. Select an individual entry in this list by clicking on it, or use Ctrl+Click and Shift+Click to select multiple entries. |
Remove |
Removes the association between the selected entries in the display text box and the application. |
Additional Launch Parameters for SMS Application |
When defining Inbound SMS applications, you can configure the launch parameters for the applications. The launch parameters allow you to assign multiple applications to a common incoming number or incoming email address. When a message arrives, the system checks if the message matches the options specified in the launch parameters. If the parameters match, the application receives the message, subject to the application launch order. The options are:
To add multiple launch parameters, click Add. To remove a launch parameter, click Remove. |
SIP Header Source |
Use the SIP Header Source field to select the source of the launch number for SIP inbound calls. The options are:
|
When determining what value to use for each of the following settings, Experience Portal looks at the following sources:
The speech application itself. If the parameter is defined in the application, Experience Portal uses that value.
The values entered on this page. If the parameter is not defined in the application but is defined on this page, Experience Portal uses the value defined here.
The values entered on the Browser Settings page.
The default values defined for the Automatic Speech Recognition (ASR) or Text-to-Speech (TTS) server by the server manufacturer. To determine the default settings for your ASR server, consult your server documentation.
If these fields are not displayed, click the group heading to expand the group.
Field |
Description |
|---|---|
ASR section |
|
Confidence Threshold |
The confidence level below which the ASR engine will reject the input from the caller. Enter a number from 0.0 to 1.0. This value is mapped to whatever scale the ASR engine uses to compute the confidence level. In the case of ASR engines that use MRCP, this value is mapped in a linear fashion to the range 0 to 100.
Note:
If you are using Orchestration Designer, see the Confidence field description in your Orchestration Designer documentation. |
Sensitivity Level |
How loud an utterance must be for the ASR engine to start speech recognition. Enter a number from 0.0 to 1.0. The higher the sensitivity level, the lower the input volume required to start speech recognition. This value is mapped to whatever scale the ASR engine uses to compute the sensitivity level for speech recognition.
Note:
If you are using Orchestration Designer, refer to the Nodes and Palette Options chapter in the Orchestration Designer Developer's Guide for more information on the Sensitivity field description. |
Speed vs. Accuracy |
The balance between speed of recognition and accuracy of recognition. Enter a number from 0.0 to 1.0. While using ASR servers with MRCP, if you want to:
This value is mapped to whatever scale the ASR engine uses to compute the balance between speed and accuracy of recognition.
Note:
If you are using Orchestration Designer, see the Speed vs. Accuracy field description in your Orchestration Designer documentation. |
No Input Timeout |
The number of milliseconds the system waits for a caller to respond after the prompt is finished playing and before the system throws a No Input event. For Nuance and Loquendo, enter an integer value in the range 0 to 65535.
Note:
If you are using Orchestration Designer, see the Timeout field on the Prompt main tab in your Orchestration Designer documentation. |
Recognition Timeout |
The number of milliseconds the system allows the caller to continue speaking before the system ends the recognition attempt and throws a maxspeechtimeout event. For Nuance and Loquendo, enter an integer value in the range 0 to 65535.
Note:
This field corresponds to the Maximum Speech field in your VoiceXML application. For more information, see your Orchestration Designer documentation. |
Maximum Grammar Cache Age |
The maximum length of time that an utterance can be in the cache before the application considers it to be stale and forces the MPP to download the utterance again. Enter a whole number of seconds in this field. When determining whether an utterance is stale or not, the application adds this time together with the value specified in the Maximum Grammar Staleness field and compares that to the age of the utterance plus the value in the Minimum Grammar Freshness Time field. The maximum grammar cache age plus the maximum grammar staleness time must be greater than or equal to the age of the utterance plus the minimum grammar freshness time. For example, if the:
Then the application will accept the utterance from the MPP because the expression 60 + 20 > 45 + 30 evaluates as True.
Note:
For the purposes of this calculation, if the maximum grammar staleness field is blank, that is the same as setting it to infinity. In that case, the application will always accept the cached utterance from the MPP because the maximum grammar cache age plus infinity will always be greater than the utterance age plus the minimum grammar freshness time. |
Minimum Grammar Freshness Time |
The minimum length of time beyond an utterance’s current age for which the utterance must remain fresh to be accepted by the application. Enter a whole number of seconds in this field. The application adds this value to the current age of the utterance and compares the result to the value in the Maximum Grammar Cache Age field plus the value in the Maximum Grammar Staleness field, as described above. |
Maximum Grammar Staleness |
The maximum amount of time beyond the normal expiration time of an utterance that the application server will accept. Enter a whole number of seconds in this field, or leave it blank to instruct the application to always use a cached response of any age. The application adds this value to the value in the Maximum Grammar Cache Age field and compares it to the current age of the utterance plus the value in the Minimum Grammar Freshness Time field, as described in the Maximum Grammar Cache Age field. |
Remote Utterance URL |
The destination for remote utterance is based on the option you select here. The options are:
The default is No. |
Session XML |
The drop-down list provides options to select None or Custom. Select one of the following options:
|
TTS section |
|
Prosody Volume |
The default value for the loudness of the synthesized speech output. Specify one of the following values from the drop-down list or enter a value in the text field.
Note:
The text field is enabled only when you select None in the drop-down list. The text field is not displayed if you select Loquendo in the TTS field. Enter a number from 0 to 100, where zero (0) represents no audible output and 100 represents full volume
Note:
You can set the Prosody Volume to 50 to ensure that:
|
Prosody Rate |
Experience Portal uses this value to fine tune the default TTS speaking rate relative to the server default. Specify one of the following values from the drop-down list or enter a value in the text field.
Note:
The text field is enabled only when you select None in the drop-down list. The text field is not displayed if you select Loquendo in the TTS field. For Nuance and Loquendo servers, enter a number from 1 to 100. |
Vendor Parameters |
Any vendor-specific or platform-specific parameters that the TTS server requires to function correctly with this speech application.
Note:
Contact your speech server provider for details on vendor parameters. These parameters must be in the general form For example, to specify that a Nuance RealSpeak server should use the custom dictionary called mydictionary.dct on a Linux RealSpeak server, you would enter:ssftrs_dict_enable=file:///opt/ttsdict/mydictionary.dct. For more information, see Administering Avaya Experience Portal . |
Session XML |
The drop-down list provides options to select None or Custom. Select one of the following options:
|
If these fields are not displayed, click the group heading to expand the group.
Field |
Description |
|---|---|
|
Transcription section
Note:
The Change Transcription Privacy feature controls the DTMF Data, Prompt Data, TTS Data , and Speech Data fields on the applications web page. The Transcription fields are enabled when a user logs in with the Privacy Manager role. The Transcription fields are disabled when a user does not have the Privacy Manager role. To assign the Privacy Manager role, you can create a new user account by navigating to the User Management > Users page and adding a new user. You can assign the Privacy Manager role to this new account. When you sign in with the Privacy Manager user role, the Transcription fields are enabled. |
|
Transcription Enabled |
The options are:
|
Transcription Sample Rate |
The percentage of times that this application will generate a transcription log when it runs. For example, if this field is set to 25%, then the application will generate a transcription log once out of every four times it runs. You can use this field to reduce application logging if your Experience Portal system is running under a heavy load. |
Performance Trace |
The options are:
|
DTMF Data |
Determines the information Experience Portal saves in the application's transcription log when a Dual-tone multi-frequency (DTMF) event occurs. The options are:
Note:
Only users with the Privacy Manager role are allowed to change the DTMF Data field. |
Prompt Data |
Determines the information Experience Portal saves in the application's transcription log when a prompt event occurs. The options are:
Note:
Only users with the Privacy Manager role are allowed to change the Prompt Data field. |
TTS Data |
Determines the information Experience Portal saves in the application's transcription log when a Text-to-Speech (TTS) event occurs. The options are:
Note:
Only users with the Privacy Manager role are allowed to change the TTS Data field. |
Speech Data |
Determines the information Experience Portal saves in the application's transcription log when a speech event occurs. The options are:
Note:
Only users with the Privacy Manager role are allowed to change the Speech Data field. |
Intent Sample Rate |
The percentage of times that the application generates intent reporting data when it runs. For example, if this field is set to 25%, then the application generates intent reporting data once out of every four times it runs. You can use this field to cut down on application logging if your Experience Portal system is running under a heavy load. |
Orchestration Designer Application Logging section |
|
Minimum Level |
Determines what messages will be sent by this application through the Application Logging web service. You can view this information in the Application Summary or Application Detail report. The options are:
|
Call Flow Data Sample Rate |
The percentage of times that this application will generate call flow data when it runs. For example, if this field is set to 25%, then the application will generate crumbs once out of every four times it runs. You can use this field to cut down on application logging if your Experience Portal system is running under a heavy load. |
Orchestration Designer Application Tracing section |
|
Runtime Traces |
The options are:
The default value is No. |
Show XML Output |
The options are:
The default value is No. |
Show XML Root |
Determines if the root document, which is always inline, is displayed for every node or only once. The options are:
The default value is Once. |
Application Traces |
The trace statements that the application adds through Orchestration Designer. The options are:
The default value is No. |
Soap Traces |
Enables the WSOP to print the soap request and soap response to the console. The options are:
|
Local Report Log |
The options are:
|
Show Exception Stack Trace |
The options are:
The default value is No. The system records the exceptions in the EPM reports. To view the exceptions in the report, run the Application Detail report. |
Web Services Traces |
The options are:
The default value is No. Traces of the web service operation call is logged in the trace.log file in the application‘s log directory on the application server. |
Privacy section
Note:
This section is displayed only when you select SMS or Email application. |
|
SMS Message |
The privacy options displayed for SMS Message are:
|
Email Messages |
The privacy options displayed for Email Messages are:
|
If these fields are not displayed, click the group heading to expand the group.
Field |
Description |
|---|---|
Support Remote DTMF Processing |
Whether the ASR server or the MPP server performs Dual-tone multi-frequency (DTMF) processing. The options are:
|
DTMF Type Ahead Enabled |
Whether the application supports DTMF type ahead. DTMF type ahead feature allows a user to provide DTMF input when the prompt is being presented and thereby skip the prompt. The options are:
Note:
This field is enabled only when the Support Remote DTMF Processing field is set to No. |
Converse-On |
Whether the application is invoked by an Avaya Call Center system using the converse-on vector command. The converse-on vector command makes it possible for the Call Center vector program to call and access a speech application on the Experience Portal system. When it does so, the vector program on the Call Center server makes it possible to send data in the form of DTMF tones. This option tells Experience Portal to listen for these DTMF tones before starting the VoiceXML application.
Note:
At run time, the MPP writes the DTMF digit data to the session variable |
Network Media Service |
Whether this application uses the “voice dialog” Network Media Service for passing the application starting URI as part of the SIP invitation.
Note:
For more information, see RFC 4240 at http://www.rfc-archive.org/getrfc.php?rfc=4240. |
Early Media |
Whether the administrator has enabled early media for the application. Experience Portal applications interact with callers before the incoming call is answered. For application types that include voice such as VoiceXML, CCXML, or VoiceXML/CCXML, the administrator can enable or disable early media on the EPM web interface. Early Media informs CCXML applications that the application is to be launched before the call is answered. The default CCXML application will launch the application without accepting the call when this flag is set. The options are:
The default is No. |
Sync FROM and PAI Headers |
If a caller A calls into an application or agent and the application or agent needs to place an outbound call for call transfer, then on the deskphone caller ID, the system displays that the call is originating from caller A instead of displaying the application or agent phone number. The options are:
The default is No. |
Dialog URL Pattern |
A regular expression used to verify the starting URI form the SIP invitation. This is a security parameter used to verity the URI is “trusted.” If it is blank, then any URI will be accepted. |
VoiceXML Event Handler |
The VoiceXML event handler to use for this application. The options are:
|
CCXML Event Handler |
The CCXML event handler to use for this application. The options are:
|
Generate UCID |
The Universal Call Identifier (UCID) is an Avaya-proprietary call identifier used to help correlate call records between different systems. Inbound Calls: If the Avaya Communication Manager (CM) passes a UCID to Experience Portal, Experience Portal always uses that UCID regardless of the setting in this field. If, however, CM does not pass a UCID, the Experience Portal MPP server can generate one for the call. The options are:
Transfers & Outbound calls: The options are:
|
Operation Mode |
The SIP header for each call can contain User-to-User Interface (UUI) information that the switch can either pass on as a single block or attempt to parse so that the information can be acted on. This field determines how Experience Portal treats the UUI data. The options are:
|
Transport UCID in Shared Mode |
If Operation Mode is set to Shared UUI and Generate UCID is set to Yes, this field determines whether Experience Portal encodes the Experience Portal-generated UCID and adds it to the UUI data for all outbound calls. The default is No, which means that a UCID is only passed as part of the UUI information if that UCID was passed to Experience Portal by the application. |
Maximum UUI Length |
The maximum length of the UUI data that can be passed in the SIP header. If this length is exceeded and Experience Portal generated a UCID for the call, the UCID is removed from the UUI data. If the result still exceeds this value, or if the UCID was passed to Experience Portal by the application, Experience Portal does not send any UUI data. Instead, it leaves the entire field blank because it has no way to determine what can be left out. Enter an integer between 0 and 2,048, where 0 indicates that Experience Portal should not check the length of the UUI data. The default is 128. |
Fax Detection Enabled |
Whether this application should detect whether the inbound number is a fax machine. The options are:
The default is No. |
Fax Phone Number |
If Fax Detection Enable is set to Yes, this is the telephone number or URI to which fax machines calls should be routed. |
Video Enabled |
Whether to enable or disable the support for the video server.
The options are:
|
Video Screen Format |
Select the video screen format.
The options are:
|
Video Minimum Picture Interval |
Video Minimum Picture Interval (MPI) is the time interval used to define the frame rate. MPI uses the CIF, QCIF, and SQCIF formats. Enter a value in the range 1 to 32. The default is 2. For CIF, QCIF and SQCIF, if the value is zero, the screen format is disabled otherwise the frame rate is defined by (29.97/MPI). For example: for value 1 = 30 FPS, for 2 = 15 FPS, and so on. |