Proposed Solution 3

Procedure

On the Media Server Service Menu, click Resources.
On the Resources page, click Telephony.

Tip:

You can also use the listst.php administrative script to obtain this information about the MPP.
On the Telephony Resources page, verify that all channels display a state of In-Service in the Channel State column.
If a channel does not display In-Service, troubleshoot the problem between the Communication Manager and the MPP:
- On the EPM, check the H.323 connection settings, especially the password as described in the H.323 connections in Avaya Experience Portal topic in the Administering Avaya Experience Portal guide.
- On the EPM, check the information for the channel (port) or channels that seem to be experiencing problems.
- Check theCommunication Manager to see if it displays the same status for the affected channels (ports) as the MPP does, as described in your Communication Manager documentation.
- If you cannot resolve the problem using any of these strategies, contact your Avaya technical support representative for assistance.
Check the SessionManager logs for errors that indicate the system has had problems gaining access to Automatic Speech Recognition (ASR) or Text-to-Speech (TTS) resources:
1. On the Media Server Service Menu, click Logs.
2. On the Log Directories page, click SessMgr.
3. Click on the log you want to view.
  The available log types are:
  - SessionManager.log: Contains data related to events that are not specifically associated with a single session.
  - SessionSlot-###.log: Contains data related to Session Manager operations for individual sessions. The ### represents the unique cookie, or identifier, that you can use to find related Session Manager, CCXML interpreter, and Avaya Voice Browser logs.

	Tip:
	You can also use the listst.php administrative script to obtain this information about the MPP.