Cisco Cisco Unified MeetingPlace Audio Server 관리 매뉴얼
Cisco MeetingServer 5.1 System Manager’s Guide
104
Cisco Systems
March 2003
How Server Notifications are Sent
Specific events such as scheduling and rescheduling meetings, inviting or
uninviting participants, and adding or replacing attachments trigger the
notification process. MeetingPlace automatically sends notifications to all
meeting participants.
uninviting participants, and adding or replacing attachments trigger the
notification process. MeetingPlace automatically sends notifications to all
meeting participants.
Viewing Server Notification Status
To view the status of server notifications, such as the backlog of requests in
the queue or the status of a particular event, follow these steps:
the queue or the status of a particular event, follow these steps:
1.
From the System tab select Notification Queue Status.
2.
Click Execute to view the status window.
3.
Click the desired notification message to view the disposition.
Figure 4-19 MeetingPlace Server Notification Status
4.
Click Done to exit.
Determining Causes of Notification Failure
From the Disposition area of the server notification status window you can
determine the state of a particular notification. Some common causes of failure
are listed in Table 4-3 below:
determine the state of a particular notification. Some common causes of failure
are listed in Table 4-3 below:
Table 0-3 Causes of Notification Failure
Status Message
Description
Party has notif off
The intended recipient has selected None for both primary and
alternate notification methods.
alternate notification methods.
E-mail is not selected by
user
user
The recipient has selected e-mail as their notification method,
however, they have not specified the type of e-mail system.
however, they have not specified the type of e-mail system.
User has no primary
notif method
notif method
The recipient has not specified a primary notification method.