User Cannot Join a Meeting

If an end user can get into the Cisco Unified MeetingPlace Express system but cannot join a meeting, check the following:

•Are there enough available ports for the meeting? As the system administrator, try to join a meeting. If you can join, then there are enough ports.

•Check that there are enough voice conferencing and web conferencing licenses. If other users are using all the licenses, then this end user may have to wait for a license to become free.

•Ensure that the end user entered a valid meeting ID.

•Ensure that the meeting is actually at this time.

•Check the Meeting Details page to see if a meeting password is required. If a password is required, ensure that the end user has the correct password.

•Check the Meeting Details page to see if this meeting is only for users with Cisco Unified MeetingPlace Express profiles. Ensure that this if this meeting is for profiled users only, then this end user has a profile.

User Cannot Receive "Find Me" Calls on a Non-Direct Dial Pager

If an end user is not receiving "find me" calls on a non-direct dial pager, it may be because the pager phone number or the PIN is set incorrectly.

Non-direct dial pagers are pagers that do not have individual phone numbers. Instead, there is a common phone number for all pagers and each end user has a PIN. For the system to call non-direct dial pagers, the system must first dial the common pager phone number and then enter the PIN for the specific end user. The common pager phone number is set in the group profile on the Edit User Groups Details page, but the PIN is set in the user profile in the Pager # field on the Edit User Profiles Details page.

Problems can occur if a system administrator moves an end user from one group to another. The common pager phone number in the new group may not be the correct pager phone number for this user. Check that the common pager phone number is set correctly in the group profile and that the end user's PIN is set correctly in the user profile.

Viewing the System Log

The system log captures and buffers high-level details about system software activities. You can choose the severity level that you want to see. The output lists the date and time of the exception, the exception code, the file in which the exception occurs, and a text description of the exception.

Viewing the System Information Capture Log

The System Information Capture log provides details about the configuration and failure of the Cisco Unified MeetingPlace Express system during a particular time period. In general, every bug report should include the System Information Capture log.

Running this log generates a very large zip file that you can send to Cisco TAC, who can help you troubleshoot problems. After you download the zip file, be sure to delete it from its temporary location (usually in the /tmp directory) to save space on your system.

Note To display the current status of the Cisco Unified MeetingPlace Express system, instead of over a period of time, see the "Viewing System Status" section.

About Alarms

Alarms are caused by network connectivity failures and are usually software-related. They can also occur when there is a surge of activity on the network. Examples of conditions that can cause an alarm include not having any conferencing licenses installed or changing the LDAP configuration.

Viewing, Deleting, and Exporting Alarms

On the Alarms page, you can view all system alarms in the alarm table. You can also delete certain alarms after they are resolved and you can export the alarms to a text file which you can later send to Cisco TAC for help with troubleshooting.

Procedure

Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Services.

b. Click Alarms.

The Alarms page displays the current alarms.

Step 4 (Optional) On the Alarms page, you can do the following:

•To delete one or more alarms, select those you want to delete, and click Delete Selected.