Booting

The MPP is in the process of restarting and is not yet ready to take new calls.

It is not responding to heartbeats and last MPP state was Rebooting.

If the MPP remains in this state for more than 10 minutes, the state changes to Not Responding.

Degraded

The MPP is running but it is not functioning at full capacity.

This usually means that:

• Some of the H.323 or SIP telephony resources assigned to the MPP are not registered with the switch. For more information on viewing telephony port distribution, see Administering Avaya Experience Portal.

• Enough ports have gone out of service to trigger a fatal alarm. The percentage of out of service ports that trigger such an alarm is specified in the Out of Service Threshold group on the VoIP Settings page.

• A critical process has stopped on the MPP server.

If an MPP has issued a fatal event and remains in that state for three minutes, Experience Portal automatically restarts the MPP in an attempt to fix the problem. If the problem persists after the restart, Experience Portal tries to restart the MPP up to two more times. If after three restarts the MPP is still encountering fatal errors, the state changes to Error.

Error

The MPP has encountered a severe problem and cannot recover.

Halted

The MPP is no longer responding to heartbeats because it received a Halt command.

The MPP cannot be restarted until its server machine has been manually restarted.

Halting

The MPP is responding to heartbeats but is not taking new calls.

Experience Portal shuts down the corresponding server machine after all calls in progress are completed or the grace period ends, whichever comes first.

Once an MPP has halted, you must manually turn on the corresponding server machine before the MPP can be restarted.

Never Used

The MPP has never successfully responded to a heartbeat request.

New MPPs start to receive heartbeat requests during the next polling interval after they have been configured. This state occurs when an MPP has either not yet been sent a heartbeat request after it was added or the MPP did not respond to the heartbeat request.

Not Responding

The MPP is not responding to heartbeat requests and it has not received a Restart or Halt command.

You should manually check the MPP server machine.

Rebooting

The MPP is responding to heartbeats but is not taking new calls.

Experience Portal reboots the corresponding server machine after all calls in progress are completed or the grace period ends, whichever comes first.

Recovering

The MPP has encountered a problem and is attempting to recover.

Restart Needed

This state is most often reached when the MPP has encountered a problem that it cannot recover from and it requires a manual restart. However, it may also appear for an MPP when the EPM software has been upgraded and the MPP software has not. In that case, the state should update automatically when you upgrade the MPP software.

Running

The MPP is responding to heartbeat requests and is accepting new calls.

Starting

The MPP is responding to heartbeats but not taking new calls because it is transitioning from the Stopped state to the Running state.

Stopped

The MPP is responding to heartbeats but is not taking new calls. The MPP enters this state while it initializes after it restarts or when a Stop command is received.

Experience Portal will restart the MPP automatically if the MPP:

• Stopped unexpectedly and the Auto Restart option is selected for that MPP. In this case, Experience Portal restarts the MPP immediately.

• Has a specified restart schedule. In this case, Experience Portal restarts the MPP when the scheduled restart time arrives whether the MPP stopped because of an explicit Stop command or because the MPP encountered a problem and was not configured to restart automatically.

Stopping

The MPP is responding to heartbeats but is not taking new calls.

Experience Portal stops the corresponding server machine after all calls in progress are completed or the grace period ends, whichever comes first.