Proposed Solution

Procedure

If your system uses H.323 connections, you must configure the MPP server you want to monitor to use the Test operational mode so that you are certain your test calls will go to the correct MPP.
Verify that you have the trace logging for the MPP enabled and set to the appropriate levels.
1. Log on to the EPM web interface by using an account with the Administration user role.
2. From the EPM main menu, select System Configuration > MPP Servers.
3. On the MPP Servers page, click the name of the MPP you want to monitor in the Name column.
4. On the Change MPP Server page, go to the Categories and Trace Levels section and set the appropriate options.
5. When you are finished, click Save.
If you want to clear all log files so that you can easily see what data is being added:
1. Log in to the Media Server Service Menu as described in the Logging in to the MPP Service Menu topic in the Administering Avaya Experience Portal guide.
2. From the Media Server Service Menu, select Logs.
3. Click Clear log files in all the directories.
Log in to Linux on the MPP server that you want to monitor using an account that is a member of the avayagroup.
If you want to monitor:
- Live output to the Session Manager log file, enter the commands cd $AVAYA_MPP_HOME/logs/process/SessMgr and tail –f SessionManager.log
- Live output to the session slot log file, enter the commands cd $AVAYA_MPP_HOME/logs/process/SessMgr and tail –f SessionSlot-####.log
Make a test call and observe the data output.

Tip:

Depending on the trace logging level you have selected for the MPP, the information might scroll by faster than you can read it. If that happens, use the vi command.
If the SessionManager.log file does not contain the information you need to solve your problem, review the other MPP server log files.

	Tip:
	Depending on the trace logging level you have selected for the MPP, the information might scroll by faster than you can read it. If that happens, use the vi command.