Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Page of 348
Reservationless meetings  9-13
February 27, 2004
Cisco MeetingPlace Audio Server System Manager’s Guide
You can also configure a complementary “reservationless WebConnect” 
service for MeetingPlace Web. For more information see the MeetingPlace 
Web System Manager’s Guide
. However, because WebConnect and RSNA 
work independently, you must ensure that each is configured correctly to 
be synchronized.
Resolving recorded user name problems
A user may have a different recorded name on each server. The first time that 
logged-in users attend a meeting hosted on each remote server, they are asked 
to record their name.
If users do not like their user name on some server, have them note the 
meeting with the undesirable recording, and tell their system manager. The 
system manager should then find that meeting, determine which server is the 
problem, and give users the phone number to call to access that server. Users 
can then enter their profile on that server and rerecord the user name.
Alarm codes for RSNA
The following table describes minor alarms that may be generated by the 
RSNA feature. These descriptions may help system managers to troubleshoot 
problems.
Alarm
Description
0x30130 (196912) "RSNA 
transfer loop? UserID=%d 
MtgOwner=%d"
(Minor alarm) RSNA transfer loop. Indicates an 
inter-server configuration conflict or user 
database synchronization problem.
0x30134 (196916) "RSNA 
user unknown, 
user=%08x%08x%08x%08x"
(Minor alarm) User identified in an RSNA 
transfer is unknown. Indicates a user database 
inter-server synchronization problem.
0x30137 (196919) "RSNA: 
Password mismatch, 
user=%08x%08x%08x%08x"
(Minor alarm) Password provided in the transfer 
information block does not match the local user's 
password. Indicates an inter-server database 
synchronization problem.
0x30138 (196920) "RSNA: 
Info block verification failed, 
ex=%#x"
(Minor alarm) Corrupted information block 
received from the transferring server. Indicates 
the information was corrupted in transmission, a 
software version mismatch, clock skew, or an 
attempt at forgery. Look up the secondary 
exception code (ex=) for more specifics.