Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Users

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Integrating with Microsoft Office Communicator


To initiate Cisco Unified MeetingPlace meetings, a MOC user must have a Cisco Unified MeetingPlace profile. The MOC user must also have meeting settings configured for their MOC client.


Complete the following tasks in the order listed to configure user clients for Cisco Unified MeetingPlace meetings:


Contents

The MOC Client

Install and test the MOC client on the PCs of all end users who will use the Cisco Unified MeetingPlace LCS Gateway. See the Microsoft documentation for information.



Cisco Unified MeetingPlace Profiles for MOC Users

You must add user profiles for MOC users to the Cisco Unified MeetingPlace database. See Configuring User Profiles and User Groups for Cisco Unified MeetingPlace for information on how to add users.

  • When a MOC user initiates a Cisco Unified MeetingPlace meeting, the type of meeting that is initiated depends on the value selected for the Use Reservationless attribute in the user profile:
    • If the Use reservationless attribute is set to Yes, meetings that the user initiates from MOC are created as reservationless meetings. This approach has the advantage of providing users with a meeting ID they are familiar with (their reservationless ID), which they can easily distribute to others so that they can always enter the same meeting ID when they dial in to meetings initiated by MOC.
    • If Use reservationless attribute is set to No, meetings that the user initiates from MOC are created as immediate meetings with random unique meeting IDs.
  • For all users, set the Can call out from meetings attribute to Yes.



Meeting Settings on the MOC Client

To configure the meeting settings required to initiate Cisco Unified MeetingPlace meetings, you must set the EnableConferencingService group policy setting on user PCs, either by using the administrative template (.adm) file provided with your Microsoft LCS Server software, or by running a script on the client machine (for example, when installing MOC) to set the policy setting in the registry.


To enable the settings via the registry, create and run a .reg file containing the following two lines:

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator]

"EnableConferencingService"=dword:00000001


For more information about deploying group policy settings, see the MOC and Microsoft LCS Server documentation.



Configuring Meeting Settings on the MOC Client

You must configure meeting information in the MOC client to initiate Cisco Unified MeetingPlace meetings. This procedure assumes that the MOC clients are configured to communicate with the Microsoft LCS Server.


Before You Begin

Log into the MOC client.


Procedure
  1. Click Actions > Options.
  2. Click the Accounts tab.
  3. In the Conferencing Information section, enter values for the following fields:


Conference ID

This field must be unique for this user across your organization to avoid conflicts when users initiate meetings, and must be entered in the format


+<numeric code>.<numeric code>


We recommend using +<Cisco Unified MeetingPlace Profile ID>.<Cisco Unified MeetingPlace Profile ID> (for example, +5551212.5551212).

Leader Code

  • This field must be unique for this user across your organization.
  • We recommend that you keep the leader code confidential to help preserve meeting security.

Participant Code

  • The participant code must match the digits after the period in the Conference ID field.
  • This field must be unique for this user across your organization.* We recommend using the Cisco Unified MeetingPlace profile ID.

Domain


4. Click OK twice.

Rating: 0.0/5 (0 votes cast)

Personal tools