Cisco Cisco Unified MeetingPlace Audio Server Quick Setup Guide

Page of 766
Troubleshooting Cisco Unified MeetingPlace Web Conferencing
How to Resolve Problems With Secure Sockets Layer
23
 
Recordings Stuck in “Processing Now” State
Problem   
Attachment/Recording page of past meeting is stuck in “Processing Now” state. The past 
meeting may still show up in today’s find meeting page.
Possible Cause   
You are completing a new installation or upgrade that requires connecting to a new 
AD server and synchronizing many user profiles that may delay conversions.
Solution   
None. The process of synchronizing many user profiles for the first time causes a delay in web 
activities.
Possible Cause   
In comparison with other Cisco Unified MeetingPlace services, the Audio Service 
conversion process takes a lower priority. Therefore, during the peak hours of Cisco Unified 
MeetingPlace usage, audio files are converted and posted at a much slower rate. On an idle system, 
a recording can be accessible in minutes, while during peak hour activity it can take hours. 
Solution   
Give the system some time to do the conversions.
How to Resolve Problems With Secure Sockets Layer 
  •
Security Warnings
Problem   
You see the following warning: Name does not match the certificate.
Possible Cause   
It is possible that you did not define this Web Server properly. 
Solution   
 in the 
 module.
How to Resolve Web Server Time Synchronization Problems
If the time on the Cisco Unified MeetingPlace Web Server is different than the time on the Cisco Unified 
MeetingPlace Application Server, many symptoms arise, such as the following: 
  •
Scheduling and joining web meetings may not be honored 
  •
Recording voice and web meeting files may not be synchronized properly 
  •
Playback may not be possible 
  •
Other time related symptoms may be seen 
If the Web Server is part of a Windows domain, the web software overrides the domain NTP default 
settings. 
In Windows, go to System > Eventlog to see W32tm information and errors. This tells you which NTP 
server the Web Server is syncing with. Once you find the NTP server, use the following command from 
a DOS prompt to check if there are any communication issues between the Web Server and the NTP 
server: 
w32tm /monitor /computers:x.x.x.x