Change MPP Server page field descriptions

This address can be a fully qualified domain name or an IP address, but the address must be unique on this Experience Portal system and the machine must already have the MPP software installed on it.

You cannot use any of the following hostnames: 127.0.0.1, localhost, or localhost.local.domain.

	Note:
	This field cannot be changed.

To use the IP address associated with the address in the Host Address field, enter <Default> in this field.

	Tip:
	This address is usually the same as the host IP address.

To use the IP address associated with the address in the Host Address field, enter <Default> in this field.

	Tip:
	This address is usually the same as the host IP address.

To use the IP address associated with the address in the Host Address field, enter <Default> in this field.

Enter an integer in this field.

	Note:
	For assistance in sizing your MPP server capacity and setting the correct value for the Maximum Simultaneous Calls parameter for each MPP server, contact your Avaya Services representative or Avaya Business Partner. For more information, see Avaya Experience Portal Overview and Specification on http://support.avaya.com.

• Yes: If the MPP stops unexpectedly, Experience Portal brings it back online automatically.

• No: If the MPP stops, it must be manually restarted.

	Note:
	This option also affects an MPP that has received an explicit Reboot or Halt command. For details about issuing a Halt command and changing the operational state of one or more MPPs, see Administering Avaya Experience Portal on http://support.avaya.com.

• The Avaya Services init account created when the Avaya Service accounts were configured.

  In this case, you can enter a value in this field.

• Any other EPM user account and an Avaya Services representative has previously set the LDN value.

  In this case, the field is read only.

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.

You cannot save the MPP until the certificate is accepted.

• Use MPP Settings: The MPP uses the default settings for all MPPs set on the MPP Settings page.

• Custom: The MPP uses the trace level settings in the table in this section.

	Note:
	If you want to set any of the trace levels, you must select the Custom radio button first.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

This component collects events from other MPP processes and sends them to the network log web service on the EPM.

Select Off, Fine, Finer, or Finest.

This trace component controls the logging for the media endpoint interface in the MediaManager process. The media endpoint interface controls the RTP (audio, video) flow through the MediaManager and to the external servers.

Select Off, Fine, Finer, or Finest.

This trace component controls the logging for the start and shutdown of the MediaManager process.

Select Off, Fine, Finer, or Finest.

This trace component controls the logging for the video interface in the MediaManager process. The video interface handles:

• Downloading of any files (.txt, .jpg, .3pg and so on.) referenced in the Synchronized Multimedia Integration Language (SMIL) from the application server

• Rendering video based on the video configuration from EPM and commands from SessionManager

  	Note:
  	SMIL parsing is done in SessionManager and low level video commands are sent to this component.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

This component logs the Global Session ID (GSID) in the trace files when you set the tracing level to Finest.

Select Off, Fine, Finer, or Finest.

The Trace Logger uploads the MPP traces requested by the trace client that runs on EPM. This trace component controls the logging for the activities of trace retrieval in the Trace Web Service.

Select Off, Fine, Finer, or Finest.

Select Off, Fine, Finer, or Finest.

This component connects the Voice eXtensible Markup Language (VoiceXML) interpreter to the MPP. Its logs:

• Indicate the progress of VoiceXML execution and any exceptions or errors from VoiceXML documents

• Contain the status and errors from platform initialization and interpreter initialization

Select Off, Fine, Finer, or Finest.

This component manages:

• Downloading content such as VoiceXML and prompts from the application server

• Storing this content in the local VoiceXML interpreter cache

Select Off, Fine, Finer, or Finest.

This component parses and interprets the VoiceXML commands and controls the flow of the application based on Dual-tone multi-frequency (DTMF) or recognition results.

Select Off, Fine, Finer, or Finest.

This component perform the ECMAScript execution from the VoiceXML documents. Its logs contain the status of script execution and any ECMAScript semantic errors.

Select Off, Fine, Finer, or Finest.

This component is the interface to the platform module that performs VoiceXML element execution.

Select Off, Fine, Finer, or Finest.

This component handles messages from the MPP vxmlmgr process, the wrapper for the VoiceXML interpreter.

Select Off, Fine, Finer, or Finest.

This component controls queuing, converting, and playing prompts.

Select Off, Fine, Finer, or Finest.

This component controls queuing, loading, and unloading grammars.

Select Off, Fine, Finer, or Finest.

This component is the interface to the telephony system of the MPP. It handles features such as features as disconnect, blind transfer, and bridge transfer. In addition, its log also contains any channel initialization errors that the system encounters.

Select Off, Fine, Finer, or Finest.