Change ASR Server page field descriptions

If you are using a Nuance server, this name must be between 1 and 32 characters.

	Note:
	Once you save the ASR server, this name cannot be changed.

The default is Yes, which means the server is available.

	Note:
	When you change this value from Yes to No, no new calls will use this server. However, any calls in progress may continue to use the speech server. You must let the ongoing calls to complete before taking the speech server out of service to avoid application errors.

The options are:

• Loquendo

• Nuance

• Nuance DLGaas

• Google Speech

• Dialogflow

The selection of an engine type in this field affects what the EPM displays as the defaults in the Base Port, New Connection per Session, Languages and RTSP URL fields.

	Note:
	Once you save the ASR server, this type cannot be changed.

This field is displayed only when you select Naunce DLGaaS in the Engine Type field.

For more information on the client authentication credentials, see the Nuance DLGaaS documentation.

This field is displayed only when you select Naunce DLGaaS in the Engine Type field.

For more information on the client authentication credentials, see the Nuance DLGaaS documentation.

This field is displayed only when you select Google Speech or Dialogflow in the Engine Type field.

For more information on the authentication credentials, refer to the Google Speech or Dialogflow Engine documentation.

For information on how to get credentials for Dialogflow, see the Avaya Experience Portal Dialogflow White Paper.

The options are:

• Yes

• No

This field is displayed only when you select Google Speech or Nuance DLGaaS in the Engine Type field.

Enter a number in the range 1 to 128. The default value is 8.

This field is displayed only when you select Nuance DLGaaS, Google Speech, or Dialogflow in the Engine Type field.

Note:

The data rate for audio sent to the cloud is 16,000 bytes per second for each active cloud speech recognition resource and is essentially constant. The Audio Chunk Size parameter only marginally affects the data rate by reducing packet overhead proportional to larger chunk sizes. The VAD mode application setting and the use of barge-in in the automated agent has a larger impact on the overall data rate by affecting the activation of a speech resource.

This must be a valid network address in the form of a fully qualified hostname or an IP address.

When you enter an address in this field, the EPM automatically inserts the address as part of the RTSP URL field.

The default value for this field depends on which engine type and MRCP protocol you select:

• For Loquendo, the default is 554

• For Nuance, the default is port 4900

The default port value changes to 5060 if you select MRCPV2 (TCP) protocol and to 5061 for MRCPV2 (TLS) protocol.

	Important:
	These values are set to the default port numbers on the respective ASR servers. Unless you have manually changed the default settings on the ASR server, you should not have to change them here.

Experience Portal uses this information to determine the total number of ASR resources available to the Experience Portal system.

If you are using:

• Loquendo, the default is Yes

• Nuance, the default is No

	Important:
	You must use the above settings for this parameter.

Select an individual entry in this list by clicking on it, or use Ctrl+Click and Shift+Click to select multiple entries.

Then, click the button to move the selected languages to the Selected Languages field. To move the languages back from the Selected Languages field to the Languages field, click on the button.

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 No ASR Resource exception to the application. What happens then depends on the event handler that the application uses.

If you are logged into the EPM using the init account, enter the LDN number for this server as it appears in the Avaya Services database. If an LDN number is not specified for this server, Experience Portal uses the default value (000)000-0000.

This field specifies the number of seconds the Experience Portal system waits between heartbeat messages.

Enter an integer in this field. The default is 15.

Enter an integer in this field. The default is 4.

The options are:

• MRCP V1

• MRCP V2 — MRCPv2 option is shown only when you select Nuance in the Engine Type field.

	Note:
	If you have installed Avaya Aura® Media Server on the system, the only option available is MRCP V1.

The default is MRCP V1.

The default path depends on:

• The network address as set in the Network Address field. If you change the network address, the default RTSP URL updates to reflect the change.

• Which ASR engine type you have selected in the Engine Type field. If you change the engine type, the default RTSP URL updates to reflect the change.

	Tip:
	If you change the default URL, make sure you specify the network address and select the ASR engine type first. Otherwise, Experience Portal will overwrite your changes when you enter a new network address or change the engine type.

The options are:

• Yes: Session.xml specified for each voice application is sent to the speech server. If Session.xml is not specified for the voice application, the system generates and sends a session.xml file that consists of an organization and application name.

• No: Session.xml is not sent to the speech server for any voice application.

• TCP

• TLS

The default is TCP.

The TLS option is shown only when you select Nuance in the Engine Type field.

Important:

If you select TLS, ensure that the CA certificate that signed the identity certificate of the speech server is installed on Experience Portal as a trusted certificate. On the EPM navigation pane, click Security > Certificates > Trusted Certificates. Ensure that the required trusted certificate of the speech server is installed. If it is not uploaded, upload the certificate. Click System Maintenance > Log Viewer to check for speech server connection errors.

• Yes: This connection uses SRTP.

• No: This connection does not use SRTP.

• AES_CM_128: This connection uses 128 key encryption.

• None: Messages sent through this connection are not encrypted.

• HMAC_SHA1_80: Authentication is done with HMAC SHA-1 which uses 80 bit key for the authentication..

• HMAC_SHA1_32: Authentication is done with HMAC SHA-1 which uses 32 bit key for the authentication..

• Yes: This connection uses RTP Control Protocol encryption.

• No: This connection does not use RTP Control Protocol encryption.

• Yes: This connection uses Real-time Transport Protocol authentication.

• No: This connection does not use Real-time Transport Protocol authentication.