Cisco Cisco Unified MeetingPlace Audio Server Installation Guide
4-12 Database planning
Cisco MeetingPlace Audio Server Installation Planning Guide
February 27, 2004
MeetingPlace Directory Services Gateway synchronizes information in your
corporate directory server with information in your MeetingPlace server. It
interacts with common corporate directories such as Microsoft Active
Directory and Netscape Directory Server through Lightweight Data Access
Protocol (LDAP).
corporate directory server with information in your MeetingPlace server. It
interacts with common corporate directories such as Microsoft Active
Directory and Netscape Directory Server through Lightweight Data Access
Protocol (LDAP).
Information about new employees is entered into the corporate directory
when they join the company. MeetingPlace Directory Services Gateway
detects the addition and instantly creates a profile for new employees. As
employees change departments and offices, their contact information changes.
To ensure that MeetingPlace has the most accurate information, changes to a
person’s information in the corporate directory are recognized and replicated
on MeetingPlace Directory Services Gateway. These automatic profile
updates ease system use and limit calls to the help desk.
when they join the company. MeetingPlace Directory Services Gateway
detects the addition and instantly creates a profile for new employees. As
employees change departments and offices, their contact information changes.
To ensure that MeetingPlace has the most accurate information, changes to a
person’s information in the corporate directory are recognized and replicated
on MeetingPlace Directory Services Gateway. These automatic profile
updates ease system use and limit calls to the help desk.
For more information, see the MeetingPlace Directory Services Gateway
System Manager’s Guide.
System Manager’s Guide.
Manual file import
If you do not have MeetingPlace Directory Services Gateway installed, you
must complete a manual file import. To simplify this process, you can import
only those fields that contain profile- or group-specific information, such as
user IDs, profile numbers, group names, group numbers, and contact
information (such as e-mail addresses and phone numbers).
must complete a manual file import. To simplify this process, you can import
only those fields that contain profile- or group-specific information, such as
user IDs, profile numbers, group names, group numbers, and contact
information (such as e-mail addresses and phone numbers).
Before you perform a manual file import, keep the following points in mind:
•
Any fields not included in the import file automatically derive their value
from either the guest profile or the user group to which the user has been
assigned.
from either the guest profile or the user group to which the user has been
assigned.
•
If you do not assign users to groups, make sure the settings in the guest
profile are correct for the users you add to the system. For example, to
allow users to outdial from meetings when the value of the guest profile’s
Can Call Out from Mtgs parameter is No, change this setting in the guest
profile before importing the profiles. After importing, make sure the
values for the guest profile are correct.
profile are correct for the users you add to the system. For example, to
allow users to outdial from meetings when the value of the guest profile’s
Can Call Out from Mtgs parameter is No, change this setting in the guest
profile before importing the profiles. After importing, make sure the
values for the guest profile are correct.
•
If you assign users to groups, you must include the Group Name or Group
Number field in the import file.
Number field in the import file.
•
You must use unique values for the user ID and profile number. For
example, if you import the data from your voice-mail system, use each
person’s telephone number as the profile numbers. If an e-mail system
database is your source, use the person’s e-mail user ID as the
MeetingPlace user ID. If used, the group name and group number values
must also be unique.
example, if you import the data from your voice-mail system, use each
person’s telephone number as the profile numbers. If an e-mail system
database is your source, use the person’s e-mail user ID as the
MeetingPlace user ID. If used, the group name and group number values
must also be unique.
N
OTES
In the following table:
•
Items marked with an asterisk (*) identify user-specific fields. These are
the most important fields to include in the import file when adding users to
the system.
the most important fields to include in the import file when adding users to
the system.