DocWiki - User contributions [en]

Cisco Unified MeetingPlace, Release 6.x -- Worksheet 5-17: User Groups

2009-06-16T22:27:43Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]] >
[[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Audio Server, Release 6.x|Cisco Unified MeetingPlace Audio Server]] >
[[Cisco Unified MeetingPlace, Release 6.x -- Planning Your Audio Server Installation|Planning the installation]]
> [[Cisco Unified MeetingPlace, Release 6.x -- Database Planning Worksheets|Database Planning Worksheets]]

To quickly and easily enter default profile information for multiple users at one time, assign users to a user group.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, '' Numeric-0 to 9 '' means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, '' Numeric-1 to 32767* '' means that the field accepts the value 3102 but not 32769.

{| border = 1
|-
!Field
!Description
!Default
!Options and Field Size
!Value
|-
|<td colspan="5" rowspan="1">|''' Group Information'''
|-
|

Name
|

Name by which you want to identify group.

Recommended: A name that describes the group ('' Marketing '').

Do not include spaces. Use an underscore character (_) instead ('' Field_Sales '').
|

System
|

Alphanumeric-1 to 17
|
|-
|

Number
|

Number by which you want to identify group.
|

0
|

Numeric- 0 to 17
|
|-
|

Billing code
|

A code for generating billing reports. Can be based on your company's internal conventions (for example, department codes).
|

-
|

Alphanumeric-0 to 17
|
|-
|

Default mtg category
|

Meeting category assigned to meetings the group's users schedule.
|

"Standard"
|

Selected name
|
|-
|

Group active?
|

Whether group is active.

You can define groups now, and make them active later (for example, after the group's users complete training).
|

No
|

Yes/No
|
|-
|

Profile type
|

Whether the members of the group are users or video terminals.
|

User
|

User/Video Terminal
|
|-
|<td colspan="5" rowspan="1">|''' Group Defaults'''
|-
|

User ID of contact
|

User ID of contact or attendant who supports group's users.
|

-
|

Alphanumeric-0 to 17
|
|-
|

Time zone
|

Time zone in which the users in this group are located.

Recommended: Time zone in which user group is located.

Time zone information can vary for individual users in a group. Set time zone information for each user in individual user profiles.
|

Local-time
|

Time zone name
|
|-
|

Language
|

Language this group's users prefers.

Language information can vary for individual users in a group. Set language information for each user in individual user profiles.
|

English (USA)
|

English (USA)/ Other installed language
|
|-
|

Abbreviated prompts?
|

When '' Yes '', all users hear abbreviated prompts when they call Cisco Unified MeetingPlace. When '' No '', all users hear unabbreviated prompts.
|

No
|

Yes/No
|
|-
|

Scheduling home server?
|

The local server for users in this group.
|

0
|

Read-only
|
|-
|<td colspan="5" rowspan="1">|''' MeetingNotes Defaults'''
|-
|

Able to record mtgs?
|

Whether users in group can record meetings.
|

Yes
|

Yes/No
|
|-
|

Record meetings?
|

Whether by default meetings scheduled by group's users are recorded.
|

No
|

Yes/No
|
|-
|

Who can access
|

Who can request attachments and listen to meetings recorded by group's users. When '' None '', a recorded meeting and its attachments must be posted manually for other participants to hear.
|

Anyone
|

None/Anyone/ MeetingPlace Users/ Invited Guests
|
|-
|

Auto-start recording?
|

For meetings scheduled to be recorded, whether by default recording starts automatically when second participant enters meeting.
|

Yes
|

Yes/No
|
|-
|

Attachment access ordering
|

Order in which group's users hear list of attachments.
|

Most recent first
|

As submitted/ Most recent first
|
|-
|

Display mtg to everyone?
|

Whether by default to allow Cisco Unified MeetingPlace web guests to view meetings.
|

No
|

Yes/No
|
|-
|

Display rsvnless mtgs to everyone?
|

Whether by default to allow Cisco Unified MeetingPlace web guests to view reservationless meetings.
|

No
|

Yes/No
|
|-
|<td colspan="5" rowspan="1">|''' Outdial Meeting Defaults'''
|-
|

Can call out from mtgs?
|

Whether group's users can outdial to others while they are in a meeting.
|

No
|

Yes/No
|
|-
|

Can schedule guest outdial mtgs?
|

Whether group's users can schedule meetings that let guests join voice conference by web. This parameter is enabled only if this group has outdial privileges.

When '' No '', the Allow Outdials to Guests From Web parameter is disabled for this group. When '' Yes '', group's users can change Allow Outdials to Guests From Web for individual meetings.
|

No
|

Yes/No
|
|-
|

Allow outdials to guests from Web?
|

For meetings scheduled by this group, whether guests can join the meetings by Web.

When '' Yes '' and a meeting is scheduled, the system can outdial to guests when they click Join Voice Conference button. When '' No '', guests who click this button see the phone number to call to join meeting.
|

No
|

Yes/No
|
|-
|

Max outdials per mtg
|

Number of outdials group's users can place from within one meeting.

'''Note: ''' This field limits only the number of times this group's users can outdial from a meeting by pressing #3. It does not restrict any other method of outdialing.
|

0
|

Numeric- 0 to 500*/ Unrestricted
|
|-
|

Can call other servers?
|

Whether group's users can schedule multiserver meetings.
|

No
|

Yes/No
|
|-
|

Ask for profile password?
|

Whether an invitee who was outdialed must provide a profile password before being admitted into the meeting.
|

Yes
|

Yes/No
|
|-
|

Digit translation table
|

Translation table number to use for all outdials made by group's users. 16 translation tables are available. Default translation table is '' 0 ''.

Your installation partner will work with you to configure these tables, as needed.
|

Yes
|

Yes/No
|
|-
|<td colspan="5" rowspan="1">|''' Meeting Preferences'''
|-
|

Entry announcement
|

Announcement used when users enter meetings.
|

Beep+ Name
|

Beep only/ Beep+Name/ Silent
|
|-
|

Departure announcement
|

Announcement used when users leave meetings.
|

Beep+ Name
|

Beep only/ Beep+Name/ Silent
|
|-
|

End of mtg announcement
|

Whether the system announces the meeting will end in a set number of minutes.

For reservationless meetings, this parameter is not used. This announcement is not played for reservationless meetings.
|

Yes
|

Yes/No
|
|-
|

Mtg extension announcement
|

Whether the system announces the meeting is extended by a set number of minutes.

For reservationless meetings, this parameter is not used. This announcement is not played for reservationless meetings.
|

No
|

Yes/No
|
|-
|

Screened entry?
|

Whether meetings scheduled by this group require a meeting participant (already in the meeting) to admit people who try to join the meeting. (People wanting to enter are not admitted automatically.)
|

No
|

Yes/No
|
|-
|

Skip pre-meeting options?
|

Whether meetings scheduled by this group's users use the Short Menu feature. Eliminates meeting ID confirmation, roll call, and agenda.
|

No
|

Yes/No
|
|-
|

Disable roll call?
|

Whether meetings scheduled by this group's users may request roll call feature during a meeting.

Recommended: '' Yes '' when, for example, competitors could call into a meeting, meetings require caller anonymity, or you schedule large meetings.
|

Yes
|

Yes/No
|
|-
|

Password required?
|

Whether by default meetings scheduled by this group's users require a password.

When '' Yes '', the person who starts a reservationless meeting that is organized by this group's users can choose to create a password for the meeting. When '' No '', the person who starts the meeting does not create one.
|

No
|

Yes/No
|
|-
|

Who can attend?
|

Who can attend meetings scheduled by this group's users. For reservationless meetings, this parameter is not used. Anyone can attend reservationless meetings.
|

Anyone
|

Anyone/ MeetingPlace Users/ Invited Guests
|
|-
|

Allow Internet access?
|

When the Cisco Unified MeetingPlace system is configured with a web-conferencing server in the DMZ and another behind the DMZ. When '' Yes '', the Web portion of the meeting is held on the server in the DMZ and can be accessed by anyone. When '' No '', the Web portion of the meeting is held on the server behind the DMZ and can be accessed only by users on the company's intranet.
|

No
|

Yes/No
|
|-
|

Allow Internet Access for Reservationless
|

When '' Yes '', the Web portion of reservationless meetings is held on the server in the DMZ and can be accessed by anyone. When '' No '', the Web portion of reservationless meetings is held on the server behind the DMZ and can be accessed only by users on the company's intranet.
|

Yes
|

Yes/No
|
|-
|

Lecture mtg attend sttgs
|

For lecture-style meetings scheduled by this group's users, the way in which listen-only participants are admitted.

When '' Admit as listeners '' and '' Start callers in waiting room '', participants listen to music on hold until meeting is called to order. When '' Start mtg with floor open '', participants can talk until meeting is called to order. When '' Reservationless mtg '', lecture-style meetings scheduled by this group become reservationless meetings.
|

Admit as listeners
|

Admit as listeners/ Start callers in waiting room/ Start mtg with floor open/ Reservationless mtg
|
|-
|

Host Meetings with
|

Whether the user will see the full meeting room or just the participant list when joining web meetings.

'''Note:''' The Participant List option is not available if you are using Cisco WebEx.
|

Full Meeting Room (if there are web port licenses available.)
|

Full Meeting Room/ Participant List
|

|-
|<td colspan="5" rowspan="1">|''' Restrictions'''
|-
|

Scheduling restriction
|

Scheduling limits placed on this group's users.

When '' Unrestricted '', users may schedule unlimited number of meetings; When '' Cannot Schedule '', users can schedule no meetings; When '' Near Term Mtg Limit '', users may schedule the specified number of meetings within the next six hours.
|

Un- restricted
|

Unrestricted/ Cannot Schedule/ Near Term Mtg Limit (Numeric- 0 to 50*)
|
|-
|

Use reservationless?
|

Whether to allow users in this group to use the reservationless meeting feature.
|

Yes
|

Y/N
|
|-
|

Max mtg length (min)
|

Maximum number of minutes for which this group's users can schedule meetings.
|

240
|

Minimum 2; maximum is Max Mtg Length (Scheduling Parameters)
|
|-
|

Max # of attachments
|

Maximum number of attachments allowed for meetings scheduled by this group's users.
|

10
|

Numeric- 0 to 30*
|
|-
|

Sched only on home server?
|

Whether meetings for users in this group are restricted to the home server.
|

No
|

Read-only
|
|-
|

Sched only on NS home site?
|

Whether meetings for users in this group are restricted to the home site.
|

Yes
|

Read-only
|
|-
|

Max # teams allowed
|

Number of teams this group's users can create.
|

0
|

Numeric- 0 to 10,000*
|
|-
|

Can chg mtg ID via phone
|

Whether this group's users may assign vanity IDs for meetings they schedule by phone.

This field is available only when Allow Vanity Meeting IDs (in System Parameters) is set to '' Yes ''.
|

Yes
|

Yes/No
|
|-
|

Allow video scheduling?
|

Whether this group's users can schedule meetings with video.
|

No
|

Yes/No
|
|-
|<td colspan="5" rowspan="1">|''' Sending Notifications'''
|-
|

Enabled for this mtg?
|

Whether this group's users send notifications for meetings.

For reservationless meetings, notifications are not sent.
|

Yes
|

Yes/No
|
|-
|

Include attachments?
|

Whether this group's users send attachments as part of their notifications.
|

No
|

Yes/No
|
|-
|

Priority
|

Priority of notifications for this group's users.
|

Normal
|

Low/Normal/ Urgent
|
|-
|

Send if mtg changes?
|

Whether to send notifications when something changes in meetings (such as the time, date, password, or meeting ID), or when a message or attachments are added or deleted.
|

No
|

Yes/No
|
|-
|

Include participant list?
|

Whether this group's users send a list of names of meeting participants as part of their notifications.
|

No
|

Yes/No
|
|-
|

Include password?
|

For secure meetings where a password is specified, whether this group's users include the password in notifications.
|

No
|

Yes/No
|
|-
|<td colspan="5" rowspan="1">|''' Receiving Notifications'''
|-
|

Enable to receive?
|

Whether this group's users receive notifications about meetings they are invited to (if meeting scheduler sends them).
|

No
|

Yes/No
|
|-
|

Include attachments?
|

Whether this group's users receive attachments as part of meeting notifications.
|

No
|

Yes/No
|
|-
|

Type of e-mail system
|

E-mail system used by this group's users. (See [[Cisco Unified MeetingPlace, Release 6.x -- Worksheet 5-17: User Groups#Table: Choices for Type of E-mail System Field|Table: Choices for Type of E-mail System Field]] after this worksheet.)
|

None
|

None/cc:Mail/ Lotus Notes/ Microsoft Mail/ Microsoft Exchange/ Qualcomm Eudora/ Netscape Messenger/ Other
|
|-
|

Preferred delivery method
|

Notification delivery method for this group's users.
|

None
|

None/E-mail
|
|-
|

Alternate delivery method
|

Alternative notification delivery method to use if the preferred method fails.
|

None
|

None/E-mail
|
|-
|<td colspan="5" rowspan="1">|''' Attending Meetings'''
|-
|

Method of attending
|

This group's users' preferred method of joining meetings.
|

User will call in
|

User will call in/ Have system call user/ Have system page user/ Do not reserve space for user/ Have system find user
|
|-
|

First search method
|

First number the system tries to reach users in this group.
|

None
|

None/Main/ Alternate/Pager
|
|-
|

Second search method
|

Second number the system tries to reach users in this group.
|

None
|

None/Main/ Alternate/Pager
|
|-
|

Third search method
|

Third number the system tries to reach users in this group.
|

None
|

None/Main/ Alternate/Pager
|
|-
|

Type of pager
|

Type of pager service used by this group's users.
|

None
|

None/ Direct Dial/ Non Direct Dial
|
|-
|

Pager phone number
|

Pager phone number of this group's users.
|

-
|

Direct Dial- 32-digit pager number/ Non Direct Dial-user's pager access code (PIN)
|
|-
|<td colspan="5" rowspan="1">|''' Q&A Meetings'''
|-
|

Off at mtg startup?
|

Whether to turn on Q&A Meetings feature for this group's users at meeting startup.
|

No
|

Yes/No
|
|-
|

Notify attendees about Q&A?
|

Whether to describe Q&A feature to this group's users when they attend conferences.
|

No
|

Yes/No
|
|-
|

Q&A introduction
|

How to announce attendees being placed on the floor in meetings this group's users schedule.
|

Beep+ Name
|

Beep only/ Beep+Name/ Silent
|
|-
|

Q&A departure
|

How to announce attendees being removed from the floor in meetings this group's users schedule.
|

Beep
|

Beep only/ Beep+Name/ Silent
|
|-
|

Automatically ask next question?
|

Whether to automatically promote next waiting attendee to the floor in meetings this group's users schedule.
|

No
|

Yes/No
|
|-
|

More than one question per site?
|

Whether to allow attendees in meetings scheduled by this group's users to ask more than one question at a time.

When '' Yes '', this group's users may ask up to five questions.
|

No
|

Yes/No
|
|-
|

Tell my position in line?
|

Whether to tell attendees in meetings scheduled by this group's users their current position in line.
|

No
|

Yes/No
|
|-
|

Disable floor warning prompt?
|

Whether to tell attendees in meetings scheduled by this group's users they are next to ask a question (or speak) on the floor.
|

No
|

Yes/No
|
|-
|<td colspan="5" rowspan="1">|''' Video Meetings'''
|-
|

Endpoint bandwidth
|

Bandwidth to use when connecting to VoIP. Endpoint connections are made based on the default bandwidth. (Guest connections are established with the default guest bandwidth.)
|

384K
|

128/256/384/512/758/1472/1920 kbps
|
|-
|

Run meetings on video MCU only?
|

This value determines how the checkboxes in the Web Scheduling page are configured by default. If this is set to Yes, the web scheduling page initially has the video checkbox checked and the audio+web checkbox unchecked. The meeting scheduler can override the settings.
|

No
|

Yes/No
|
|-
|

Attend preference for video prof.
|

For video profiles, whether the preference is for Cisco Unified MeetingPlace to automatically outdial the video end point or for the end point to dial in to meetings.
|

Dial-in
|

Dial in/Outdial
|
|-
|<td colspan="5" rowspan="1">|'''Flex Fields'''
|-
|

Profile flex field 1
|

Profile field customized with your business information.
|

-
|

-
|
|-
|

Profile flex field 2
|

Profile field customized with your business information.
|

-
|

-
|
|-
|

Profile flex field 3
|

Profile field customized with your business information.
|

-
|

-
|
|-
|

Profile flex field 4
|

Profile field customized with your business information.
|

-
|

-
|
|-
|

Profile flex field 5
|

Profile field customized with your business information.
|

-
|

-
|
|-
|

Profile flex field 6
|

Profile field customized with your business information.
|

-
|

-
|
|-
|

Profile flex field 7
|

Profile field customized with your business information.
|

-
|

-
|
|}

In [[Cisco Unified MeetingPlace, Release 6.x -- Worksheet 5-17: User Groups#Table: Choices for Type of E-mail System Field|Table: Choices for Type of E-mail System Field]], for the Type of E-mail System field, choose the value that corresponds to the e-mail system installed at your company.

===== Table: Choices for Type of E-mail System Field =====

{| border = 1
|-
!E-Mail System
!Choose
|-
|

cc:Mail
|

cc:Mail
|-
|

IBM Lotus Notes
|

Lotus Notes
|-
|

Microsoft Mail
|

Microsoft Mail
|-
|

Microsoft Exchange
|

Microsoft Exchange
|-
|

SMTP
|

Microsoft Mail, Qualcomm Eudora, Netscape Messenger
|-
|

Other MAPI-compliant mail systems
|

Microsoft Mail
|}

Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator

2009-06-16T21:45:27Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x ]] > [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace for Microsoft Office Communicator, Release 6.x|Cisco Unified MeetingPlace for Microsoft Office Communicator]]

== Configuring Logging ==

If you are encountering a problem with Cisco Unified MeetingPlace for Office Communicator, it may be helpful to begin troubleshooting by configuring verbose logging, attempting to reproduce the problem, examining the eventlog, and then returning the logging level to informational.

===== To Configure Logging =====

# Open the MeetingPlace Gateway Configurations utility by right-clicking the Cisco Unified MeetingPlace icon (orange door) located in the system tray.
# Enable verbose logging for the Single Sign On Service:
## Click the '''Single Sign On''' tab.
#: '''Note: ''' The Single Sign-On tab is displayed in the Gateway Configurations utility only after the Cisco Unified MeetingPlace LCS Gateway has been installed on the server.
## Check the '''Verbose Logging''' check box.
## Click '''Apply''' to save the change.
# Enable verbose logging for the Cisco Unified MeetingPlace LCS Gateway:
## Click the '''LCS Gateway '''tab.
#: '''Note: ''' The LCS Gateway tab is displayed in the Gateway Configurations utility only after the Cisco Unified MeetingPlace LCS Gateway has been installed on the server.
## For Log Level, choose '''Verbose'''.
## Click '''Apply''' to save the change.
# Click '''OK''' to close the MeetingPlace Gateway Configurations utility.
# After changing the logging level, stop the Cisco Unified MeetingPlace LCS Gateway service, restart the Cisco Unified MeetingPlace Web Conferencing service, then start the Cisco Unified MeetingPlace LCS Gateway service:
## From the Windows Start menu, choose '''Settings''' > '''Control Panel''' > '''Administrative Tools''' > '''Services'''.
## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Stop'''.
## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Start'''.
## Close the Services control panel.
# To access an eventlog, right-click the Cisco Unified MeetingPlace icon in the system tray and choose '''Eventlog'''.

== Tracking a Conference in the Logs ==

When a user initiates a conference from Office Communicator, the LCS server assigns a unique conference ID for the conference by using the value configured for Conference ID on the Accounts tab of the Actions > Options window, and sends a conference initiation request to the Cisco Unified MeetingPlace LCS Gateway. The Cisco Unified MeetingPlace LCS Gateway then initiates a Cisco Unified MeetingPlace conference with a random unique Cisco Unified MeetingPlace meeting ID.

For troubleshooting purposes, the LCS Conference ID and Cisco Unified MeetingPlace meeting ID are both logged in the Gateway Systems Integrity Manager (Gateway SIM) log when the meeting is created. When the MOC user ends the conference, the system removes the tie between these two IDs. If the MOC user initiates another conference, the system uses the same LCS Conference ID, but it is mapped to a new Cisco Unified MeetingPlace meeting ID. If the MOC user has the "Use reservationless" parameter set to yes in the user profile, the system sets the MOC-initiated meeting ID to the user's profile ID (phone number). Otherwise, the system randomly generates the meeting ID.

== Troubleshooting Cisco Unified MeetingPlace LCS Gateway Startup Problems ==

'''Error Message''' <tt> Service cannot be started...The requested address is not valid in its context. </tt>

'''Explanation''' You entered the wrong listening IP address on the LCS Gateway tab in the Cisco Unified MeetingPlace gateway configurations utility.

'''Recommended Action''' Enter the correct IP address.

'''Problem''' If the Cisco Unified MeetingPlace LCS Gateway service fails to start, check the Gateway Systems Integrity Manager (Gateway SIM) log to see if the LCS Event Receiver Add-In has been loaded into the Cisco Unified MeetingPlace Web Conferencing service.

If the system has not loaded the LCS Event Receiver Add-In, users cannot use DTMF controls in meetings. (For example, #5 for muting and unmuting, #41 for locking or unlocking a meeting, etc.)

'''Solution''' Check the LCS Event Receiver Add-In status:

===== To Check the LCS Event Receiver Add-In Status =====

# Right-click the Cisco Unified MeetingPlace icon in the system tray and click '''Eventlog'''. The Gateway SIM log opens.
# Search for the following entries in the log:
#: <tt> Loading "LCS MPEventBroker" add-in... </tt>
#: <tt> Loaded ConferenceTechnologyProvider interface for "LCS MPEventBroker" </tt>
#: <tt> Load of "LCS MPEventBroker" add-In completed </tt>
# If the entries are not found, stop the Cisco Unified MeetingPlace LCS Gateway service, restart the Cisco Unified MeetingPlace Web Conferencing service, and then start the Cisco Unified MeetingPlace LCS Gateway service:
## From the Windows Start menu, choose '''Settings''' > '''Control Panel''' > '''Administrative Tools''' > '''Services'''.
## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Stop'''.
## Right-click '''Cisco Unified MeetingPlace Web Conferencing''' and click '''Stop'''.
## Right-click '''Cisco Unified MeetingPlace Web Conferencing''' and click '''Start'''.
## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Start'''.
## Close the Services control panel.

== Troubleshooting Office Communicator Error Messages ==

'''Error Message: ''' Cannot perform the selected action. This action may not be permitted by the conferencing service. Please try again. If the problem persists, please contact your system administrator.

'''Explanation: ''' This error message may appear when the Office Communicator client attempts to initiate a conference. It indicates that the LCS Integration option key has not been entered.

'''Recommended Action: ''' Verify that the correct option key has been entered for the LCS Integration. See the [[Cisco Unified MeetingPlace, Release 6.x -- Installing Cisco Unified MeetingPlace for Office Communicator#Enabling the LCS Integration Option Key|Enabling the LCS Integration Option Key]].

'''Error Message: ''' Cannot contact conferencing server. The conferencing service is currently unavailable. You may be having local connection problems, or your conferencing service may be experiencing temporary difficulties. If the problem persists, please contact your system administrator.

'''Explanation: ''' This error message may appear when the Office Communicator client times out while attempting to initiate a conference. It indicates a communication problem between the LCS server and the Cisco Unified MeetingPlace LCS Gateway.

'''Recommended Action: ''' Configure logging and check the eventlog to see if the Cisco Unified MeetingPlace LCS Gateway is receiving requests from the LCS server. See the [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Configuring Logging|Configuring Logging]].

'''Recommended Action: ''' If Cisco Security Agent for Cisco Unified MeetingPlace is installed on the Cisco Unified MeetingPlace LCS Gateway server, verify that a TCP port between 5060 and 5069 is in use between the Cisco Unified MeetingPlace LCS Gateway and the LCS server. See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace LCS Gateway Parameters|Configuring Cisco Unified MeetingPlace LCS Gateway Parameters]] and the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring LCS to Route Conference Requests to the Cisco Unified MeetingPlace LCS Gateway|Configuring LCS to Route Conference Requests to the Cisco Unified MeetingPlace LCS Gateway]].

'''Recommended Action: ''' If you are still encountering problems, make sure that your deployment has been verified with TCP configured rather than TLS. With TCP, you can use a network sniffer to sniff SIP packets between the LCS server and the Cisco Unified MeetingPlace LCS Gateway, to verify that conferencing messages are being sent to the gateway and replies are being sent to the LCS server. Once the deployment works with TCP, configure TLS according to the instructions in the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Enabling TLS on the Cisco Unified MeetingPlace LCS Gateway|Enabling TLS on the Cisco Unified MeetingPlace LCS Gateway]].

'''Error Message: ''' Account suspended. This account has been temporarily suspended. Please contact your conferencing service provider for additional details.

'''Explanation: ''' This error message may appear when the Office Communicator client attempts to initiate a conference. In most cases, it indicates that the Cisco Unified MeetingPlace user profile is inactive, or there is a problem with the Single Sign-on configuration settings.

'''Recommended Action: ''' Do the tasks in the [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Troubleshooting User Authentication Problems|Troubleshooting User Authentication Problems]].

'''Error Message: ''' An error has occurred (0x80ef0190). If the problem persists, contact your system administrator.

'''Explanation: ''' This message may indicate a login failure other than an unrecognized login ID.

'''Recommended Action: ''' Do the tasks in the [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Troubleshooting User Authentication Problems|Troubleshooting User Authentication Problems]].

=== Troubleshooting User Authentication Problems ===

Do the following tasks if users are unable to authenticate to initiate conferences:
# Check the Cisco Unified MeetingPlace user profile on the Audio Server by using the MeetingTime client. Verify that the profile exists, and activate the profile if it is inactive.
# If the Cisco Unified MeetingPlace user profile exists and is active, make sure the user name on the profile is the same as the user account name on the Active Directory server.
# Configure logging and check the eventlog for messages from the mpsso and mplcsgw components. See the [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Configuring Logging|Configuring Logging]]. To change a parameter, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace Web Conferencing Single Sign-On Parameters|Configuring Cisco Unified MeetingPlace Web Conferencing Single Sign-On Parameters]].
## Verify that the mpsso component is asking for the correct user-the user name request should start with username@company.com.
## If the user name is correct, verify that the mpsso component queries the correct container for the administrative account.
## Verify that the base DN is correct.
# To do additional LDAP troubleshooting, download a light-weight LDAP browser from the Internet, and use it to log on to the Active Directory server to verify the administrative account container and base DN settings.

Cisco Unified MeetingPlace Express, Release 2.x

2009-04-08T22:54:49Z

MeetingPlace Express Moderator:

This DocWiki contains information about the following releases of Cisco Unified MeetingPlace Express, Release 2.x:

* Cisco Unified MeetingPlace Express -- Provides advanced scheduled and reservationless voice, web, and video meeting features, including the option to integrate with Microsoft Outlook.

* Cisco Unified MeetingPlace Express VT -- Provides ad hoc voice, video, and web conferencing capabilities. Ad hoc conferences are initiated through the end-user interfaces of products other than Cisco Unified MeetingPlace Express. For example, you can initiate either a voice-only or a voice-and-video ad hoc conference by using the "Meet-Me" button or the "Conf" button on Cisco Unified IP Phones that are registered to Cisco Unified Communications Manager (formerly called Cisco Unified CallManager). You can also initiate voice, video, and web conferences through Cisco Unified Personal Communicator.

== Notification of New Releases ==

See the [[Cisco Unified MeetingPlace Express, Release 2.x -- Notifications|notification page]] to learn how to be notified whenever Cisco Unified MeetingPlace Express, Release 2.x is updated.

== System Documentation ==

* For information about Cisco Unified MeetingPlace Express Release 2.x, including system requirements, see the Release Notes here: http://www.cisco.com/en/US/products/ps6533/prod_release_notes_list.html

* For a roadmap of all the documentation for Cisco Unified MeetingPlace Express Release 2.x, see the documentation roadmap here: http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/b_docmap.html

* For licensing information for Cisco Unified MeetingPlace Express Release 2.x, see the this file: http://cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/mpx_licensing_information.html

== Installation and Upgrades ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Installing Cisco Unified MeetingPlace Express|Installing Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Upgrading Cisco Unified MeetingPlace Express from an Earlier Release|Upgrading Cisco Unified MeetingPlace Express from an Earlier Release]]

== Configuration and Maintenance Tasks ==

* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Getting_Started_in_the_Cisco_Unified_MeetingPlace_Express_Administration_Center|Getting Started]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Logging in to the Cisco Unified MeetingPlace Express Application as a System Administrator|Logging in to Cisco Unified MeetingPlace Express Release 2.x as an administrator]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_System_Administrator_Responsibilities_for_Cisco_Unified_MeetingPlace_Express|System Administrator Responsibilities]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_Common_Administrative_Tasks|About Common Administrative Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring_Call_Control|Configuring Call Control]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express#Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express|Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring Security Features for Cisco Unified MeetingPlace Express#Configuring Security Features for Cisco Unified MeetingPlace Express|Configuring Security Features for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Customizing the Cisco Unified MeetingPlace Express End-User Interfaces|Customizing the Cisco Unified MeetingPlace Express End-User Interfaces]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Integration Information|Integration Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Maintaining the Cisco Unified MeetingPlace Express System|Maintenance Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Running Reports and Exporting Data from Cisco Unified MeetingPlace Express|Running Reports]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Licenses|License Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Monitoring Cisco Unified MeetingPlace Express|Monitoring Cisco Unified MeetingPlace Express]]

== Troubleshooting Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Troubleshooting_Cisco_Unified_MeetingPlace_Express|Troubleshooting]]

== Reference Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Exception Codes, Module Numbers, and File Locations Used in Cisco Unified MeetingPlace Express|Reference Information]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Administration_Center_Page_References_for_Cisco_Unified_MeetingPlace_Express|Page References]]

==Documentation for End-Users==

In English: http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

In other languages: http://www.cisco.com/en/US/products/ps6533/tsd_products_support_translated_end_user_guides_list.html

[[Category:Conferencing]]

Cisco Unified MeetingPlace, Release 2.x -- Notifications

2009-04-08T22:54:09Z

MeetingPlace Express Moderator: Cisco Unified MeetingPlace, Release 2.x -- Notifications moved to Cisco Unified MeetingPlace Express, Release 2.x -- Notifications: forgot "Express" in the page title name

#REDIRECT [[Cisco Unified MeetingPlace Express, Release 2.x -- Notifications]]

Cisco Unified MeetingPlace Express, Release 2.x -- Notifications

2009-04-08T22:54:09Z

'''Return to the main page for Cisco Unified MeetingPlace Express, Release 2.x:''' [[Cisco Unified MeetingPlace Express, Release 2.x]]

To ensure that you always have the most recent version of Cisco Unified MeetingPlace Express, Release 2.x, add this page to your watch list. This page will be updated whenever there are updates to Cisco Unified MeetingPlace Express, Release 2.x. The DocWiki will send you an email whenever Cisco Unified MeetingPlace Express, Release 2.x and this page are updated.

To add this page to your watch list, follow these steps:

# Click '''log in''' in the top right corner of this DocWiki.
# Enter your Cisco.com user ID and password.
# Click the tab that says '''watch''' on the top of this DocWiki.
#: '''Note:''' This is the location of the '''watch''' tab for the default "skin". The watch feature location varies based on your skin preference.

Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0

2009-04-08T16:02:13Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]] >
[[Cisco Unified MeetingPlace, Release 6.x -- System Requirements|System Requirements]]

'''For international, non-US English deployments:'''
See the Cisco Unified MeetingPlace SMTP E-Mail Gateway requirement in the [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Integration Requirements: Cisco Unified MeetingPlace SMTP E-Mail Gateway|Integration Requirements: Cisco Unified MeetingPlace SMTP E-Mail Gateway]].

== Hardware Requirements ==

* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Web Server Requirements|Web Server Requirements]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Audio Server Requirements|Audio Server Requirements]]

=== Web Server Requirements ===

The Cisco Unified MeetingPlace Web Conferencing system is a software product loaded onto a hardware server. New installations of Web Conferencing require a Cisco MCS that is dedicated to Cisco Unified MeetingPlace applications.

For information about the Cisco MCS, go to http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/index.html. (You need your Cisco.com username and password to access this page.)

[[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Table: Supported Cisco 7800 Series MCS Models|Table: Supported Cisco 7800 Series MCS Models]] lists supported Cisco 7800 Series Media Convergence Server models. The Cisco MCS server must have a DVD-ROM drive, keyboard, mouse, and monitor.

Exact equivalent third-party servers are also supported. For information, go to http://www.cisco.com/go/swonly.

===== Table: Supported Cisco 7800 Series MCS Models =====

{| border = 1
|-
!System (Cisco MCS Model Number)
!Voice Conferencing Capacity
!Web Conferencing Capacity
|-
|

* Cisco MCS-7835-H2-RC1
* Cisco MCS-7835-I2-RC1
* Cisco MCS-7835-H1-RC1
* Cisco MCS-7835-I1-RC1
* Cisco MCS-7835-H2-RC2
* Cisco MCS-7835-I2-RC2
|

Up to 480 voice user licenses per server.
|

Up to 50 web-conferencing user licenses per server.
|-
|
* Cisco MCS-7845-H2-RC1
* Cisco MCS-7845-I2-RC1
* Cisco MCS-7845-H1-RC1
* Cisco MCS-7845-I1-RC1
* Cisco MCS-7845-H2-RC2
* Cisco MCS-7845-I2-RC2

|

Up to 1,152 voice user licenses per server.
|

Up to 500 web-conferencing user licenses per server.

If you have more than 50 web-conferencing user licenses, move your Cisco Unified MeetingPlace applications (for example, Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace SMTP E-Mail Gateway) to a MCS 7845 that is dedicated to web conferencing.

'''Note: ''' Add a dedicated Cisco MCS 7845 for each additional 500 web-conferencing user licenses.

'''Note: ''' If you host Cisco Unified MeetingPlace Web Conferencing and Cisco Unified MeetingPlace for Outlook on the same server, the system capacity for supporting web-conferencing user licenses is reduced by 20 percent. For example, if your system supports 500 web users and you add Cisco Unified MeetingPlace for Outlook on the same server, the system capacity for supporting web-conferencing user licenses is reduced by 20 percent, from 500 to 400.
|}

===== Additional Requirements =====
* NT File System (NTFS) with more than 2.5 GB free space available.
* 700 MB of additional disk space per expected hour of recording over the base level. For more information, see the "Recording Size" section in [[Cisco Unified MeetingPlace, Release 6.x -- Configuring the Web Conferencing System for Optimal Data Storage|Configuring the Web Conferencing System for Optimal Data Storage]].

=== Web Server Capacities ===

The number of ports that a Cisco Unified MeetingPlace Web Conferencing server can support depends on the following:

* The type of hardware.
* Whether SSL is used. (Cisco Unified MeetingPlace Web Conferencing systems configured with SSL support 30 percent fewer ports than systems that do not use SSL.)
* The colocation of other Cisco Unified MeetingPlace components on the hardware. Cisco Unified MeetingPlace Web Conferencing servers collocated with either Cisco Unified MeetingPlace for Microsoft Outlook or Cisco Unified MeetingPlace for IBM Lotus Notes support 20 percent fewer ports than systems without either of those components collocated.

The following table lists the number of Web Conferencing ports supported per server based on the most common configurations.

===== Table: Web Conferencing Ports Supported Per Server Type =====

{| border = 1
|-
!Number of Web Conferencing Ports Supported Per Server
!7835 H1/I1
!7835 H2/I2
!7845 H1/I1
!7845 H2/I2
|-
|

MP Web:

* without SSL
* with or without Cisco Unified MeetingPlace SMTP E-Mail Gateway
* collocated with or without Cisco Unified MeetingPlace video
|
100

|
200

|
250

|
500

|-
|

MP Web:

*with SSL
*with or without Cisco Unified MeetingPlace SMTP E-Mail Gateway
*collocated with or without Cisco Unified MeetingPlace video
|
70

|
140

|
175

|
350

|-
|

MP Web:

* without SSL
* collocated with either Cisco Unified MeetingPlace for Microsoft Outlook or Cisco Unified MeetingPlace for IBM Lotus Notes
* collocated with or without Cisco Unified MeetingPlace video
|
80

|
160

|
200

|
400

|-
|

MP Web:

* with SSL
* collocated with either Cisco Unified MeetingPlace for Microsoft Outlook or Cisco Unified MeetingPlace for IBM Lotus Notes
* collocated with or without Cisco Unified MeetingPlace video
|
50

|
110

|
140

|
280

|-
|}

Enter the values from the table aboive into the Max Concurrent Web Conference Users field on the Web Server page of the Cisco Unified MeetingPlace Administration Center.

Note that if you have a Cisco Unified MeetingPlace web cluster configuration (two or more web servers operating in cluster mode), you must enter the same value for each web server. The value that you enter is the sum of the ports supported by the cluster configuration. For example, if you have two 7845H2 servers with SSL enabled and Cisco Unified MeetingPlace for Microsoft Outlook is configured on one web server, then use the value for that configuration from the table above and multiply it by two. (You do not need to factor in that the second web server does not host Cisco Unified MeetingPlace for Microsoft Outlook.) In this example, the value for that specific configuration is 280 so you should enter 560 for the Max Concurrent Web Conference Users parameter. Enter this value for each server in your cluster.

'''NOTE:''' There is no table available showing the number of Web Conferencing ports supported for deployments involving other Cisco Unified MeetingPlace components such as Cisco Unified MeetingPlace Directory Services or the Cisco Unified MeetingPlace H.323/SIP IP Gateway. We highly recommend that you use a dedicated Cisco MCS server for these other integrations if you cannot reduce the values documented above to accommodate the colocation of these other components. Note that the Cisco Unified MeetingPlace H.323/SIP IP Gateway and Cisco Unified MeetingPlace Directory Services loads are directly connected to the size of your deployment, including the volume of voice conferencing and the number of Cisco Unified MeetingPlace end-user profiles.

=== System Capacity ===

The Cisco Unified MeetingPlace 8112 Audio Server can scale to 960 IP, 1152 T1-CAS, 960 E1-PRI, or 768 T1-PRI concurrent users, whereas the Cisco Unified MeetingPlace 8106 Audio Server can scale to half the size of the 8112 platform. A single meeting can support up to 550 participants.
Cisco Unified MeetingPlace 6.0 Web Conferencing can support up to 1000 concurrent Web conferencing users with a cluster of two Cisco MCSs. Each server in a cluster can support up to 500 concurrent Web conferencing users and 100 concurrent meetings, and the maximum meeting size is 1000 participants (refer to the Cisco Unified MeetingPlace Web Conferencing data sheet for details). Participants can join at a maximum rate of 4 connections per second per cluster.

When voice and web conferencing are deployed together, the maximum simultaneous use capacity is 1000 combined voice and Web connections per system, see system scalability table below.

===== Table: System Scalability for Cisco Unified MeetingPlace 8112 Audio Server =====

{| border = 1
|-
!
!
!
!
!
|-
|
Voice connections
|
1000

|
800

|
500

|
200

|
0

|-
|

Web connections
|
0

|
200

|
500

|
800

|
1000

|-
|

Total

|
1000

|
1000

|
1000

|
1000

|
1000

|-
|}

Cisco Unified MeetingPlace Video Integration supports up to 72 videoconferencing participants per chassis from 128 kbps to 2 Mbps per participant on the Cisco Unified Videoconferencing 3500 Series MCUs. Multiple chassis can be deployed in a single cluster, with up to 240 video participants per cluster.

=== Audio Server Requirements ===

Cisco Unified MeetingPlace Web Conferencing requires connection to a Cisco Unified MeetingPlace Audio Server system for full functionality. The Audio Server software component must reside on a Cisco Unified MeetingPlace 8112 server or Cisco Unified MeetingPlace 8106 server.

== Networking Requirements ==

Confirm that the system meets the following requirements so that the web server can communicate with the Cisco Unified MeetingPlace Audio Server system:
* TCP ports 5003 and 5005 are open bidirectional between the web server and Cisco Unified MeetingPlace Audio Server systems (primary server and shadow server, if one exists).
* The Cisco Unified MeetingPlace Audio Server system can initiate a reverse connection to the web server, thus eliminating the need for you to open port 5003 from the web server to the Audio Server. For the reverse connection to be initiated, you must enter the MeetingPlace Server name as a host name instead of an IP address during the Cisco Unified MeetingPlace Web Conferencing installation. You will also have to manually configure this web server unit on the Audio Server.
* Connectivity between the web server and its host Cisco Unified MeetingPlace Audio Server system is of high quality and not subject to interruptions because of traffic congestion. Any time the round-trip latency exceeds 100 ms or there is more than 1 percent packet loss, you should expect a noticeable reduction in service quality.
* The Cisco Unified MeetingPlace Audio Server system must be connected to a network switch port that is configured for auto-negotiate.
* Cisco Unified MeetingPlace gateways must be connected to network switch ports that are configured for 100/1000 MB Full Duplex.

The following additional networking requirements must also be met for Web Conferencing:
* The web server must be configured with two static IP addresses on the same subnet.
* TCP port 1433 must be open bidirectional between the Web Conferencing server and SQL Server if SQL is installed remotely.

== Software Requirements ==

* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Web Server Software Requirements|Web Server Software Requirements]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Integration Requirements: Cisco Unified MeetingPlace Audio Server|Integration Requirements: Cisco Unified MeetingPlace Audio Server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Integration Requirements: Cisco Unified MeetingPlace for Outlook|Integration Requirements: Cisco Unified MeetingPlace for Outlook]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Integration Requirements: Cisco Unified MeetingPlace SMTP E-Mail Gateway|Integration Requirements: Cisco Unified MeetingPlace SMTP E-Mail Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Integration Requirements: Jabber Server|Integration Requirements: Jabber Server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#(Optional) Integration Requirements: Third Party Audio Conversion and Playback|(Optional) Integration Requirements: Third Party Audio Conversion and Playback]]

=== Web Server Software Requirements ===

The Cisco Unified MeetingPlace Web Conferencing software runs on the Cisco MCS operating system. This operating system is included with the application. Cisco Unified MeetingPlace Web Conferencing Release 6.x requires Cisco MCS OS 2003.1.1 or later.

===== Additional Windows Requirements =====
* Microsoft Internet Information Server (IIS) 6.0.
: This is installed and configured on the Cisco MCS when the operating system is installed.
* All corporate fonts and standard Microsoft fonts, including Microsoft PowerPoint fonts, installed.

===== SQL Server Requirements =====

Microsoft SQL Server 2000 and Service Pack 4 are included with the Web Conferencing 6.x installer. These required components install automatically on the Cisco MCS if you choose the local SQL Server installation option.

'''For Release 6.0(417.0) (Maintenance Release 3) and later only:'''
Cisco Unified MeetingPlace Web Conferencing can now be used with Microsoft SQL Server 2005 for remote SQL Server-based deployments. Standard, local SQL Server deployments continue to use Microsoft SQL Server 2000 that can be automatically installed by the Cisco Unified MeetingPlace Web installer when you choose the local SQL Server option during installation.

To use Microsoft SQL Server 2005, you must first use the Microsoft installation program called SQLServer2005_BC.msi (Microsoft SQL Server 2005 Backward Compatibility Components) to install the version of SQL Distributed Management Objects (DMO) that is compatible with Microsoft SQL Server 2000 onto the Cisco Unified MeetingPlace Web Conferencing server. You only need to upgrade the SQL-DMO part and not the other four components covered by this installation program.

'''Notes: '''
* If you are deploying Web Conferencing by using the remote SQL Server option, you must preinstall SQL Server 2000 with Service Pack 4 before you install Web Conferencing.
* If you need to manually install SQL Server, you must install and configure your SQL Server to be case insensitive because Web Conferencing supports only SQL Server case-insensitive configurations. If you configure your SQL server to be case sensitive, Web Conferencing will not function properly.

=== Integration Requirements: Cisco Unified MeetingPlace Audio Server ===

Cisco Unified MeetingPlace Web Conferencing Release 6.x requires Cisco Unified MeetingPlace Audio Server Release 6.x, which must reside on an 8106 or 8112 server.

===== Additional Requirements =====
* Access ports (voice)
* Cisco Unified MeetingPlace WebPublisher Option Key
* Cisco Unified MeetingPlace Data Conferencing Option Key (required for application sharing and presentations)
* Cisco MeetingNotes Data Option Key (required for presentations and attachments)
* Cisco MeetingNotes Voice Option Key (required for meeting recordings)
* Cisco Unified MeetingPlace Video Integration Option Key (required for video conferencing)

=== Integration Requirements: Cisco Unified MeetingPlace for Outlook ===

Cisco Unified MeetingPlace Web Conferencing Release 6.x requires Cisco Unified MeetingPlace for Outlook Release 6.x.

You must upgrade both Web Conferencing and Cisco Unified MeetingPlace for Outlook at the same time.

=== Integration Requirements: Cisco Unified MeetingPlace SMTP E-Mail Gateway ===

Cisco Unified MeetingPlace Web Conferencing Release 6.x requires Cisco Unified MeetingPlace SMTP E-Mail Gateway Release 5.4.

=== Integration Requirements: Jabber Server ===

Cisco Unified MeetingPlace Web Conferencing Release 6.x requires Cisco Unified MeetingPlace Jabber Integration Release 6.x installed on a Jabber XCP 4.2 server with Sun Java Runtime Environment (JRE) 1.4.2.xx.

See also [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace for Jabber Release 6.x |Requirements for Cisco Unified MeetingPlace for Jabber Release 6.x]].

=== (Optional) Integration Requirements: Third Party Audio Conversion and Playback ===

===== Audio Conversion =====
* A third-party audio service is not required to convert audio files to MP3, WAV or WMA format. Cisco Unified MeetingPlace Web Conferencing uses its internal audio service component and bundled encoders to convert audio attachments into these formats.

===== Streamed Playback =====
* Windows Media Services
: For full installation and configuration instructions, refer to the "Configuring the Windows Media Server" section in [[Cisco Unified MeetingPlace, Release 6.x -- Configuring the Web Conferencing System for Optimal Data Storage|Configuring the Web Conferencing System for Optimal Data Storage]].

== (Optional) WebEx Requirements ==
WebEx functionality was introduced in Cisco Unified MeetingPlace Release 6.x maintenance release 2 (MR 2).

The following are the system requirements for a Cisco Unified MeetingPlace system integrated with WebEx:

'''WebEx '''
* WebEx WBS26 system release or higher on your WebEx site
* WebEx MeetingCenter or WebEx MeetingCenter Pro. WebEx SalesCenter is optional.

'''Cisco Unified MeetingPlace'''

* Cisco Unified MeetingPlace Audio Server Release 6.0(2.13) (MR 2)
* Cisco Unified MeetingPlace Web Conferencing Release 6.0(361.0) (MR 2)
* One Cisco Unified MeetingPlace Web Conferencing server in the DMZ and one behind your firewall.

For more information, see [[Cisco Unified MeetingPlace, Release 6.x -- How to Configure WebEx|How to Configure WebEx]]

== Load Balancing Requirements ==

Cisco Unified MeetingPlace Web Conferencing load balancing makes use of an algorithmic formula to evenly distribute web-conferencing requests within clusters of web servers. The following section lists additional requirements for load balancing configurations.

===== Audio Server Requirements =====
* All web servers within both internal and external clusters must point to the same Cisco Unified MeetingPlace Audio Server system.
* You can attach a maximum of 16 Cisco MCSs running Cisco Unified MeetingPlace applications (for example, Cisco Unified MeetingPlace Web Conferencing, Cisco Unified MeetingPlace SMTP E-Mail Gateway) to the same Cisco Unified MeetingPlace Audio Server system.

===== Internal Web Server Cluster Requirements =====

If you have an internal web server cluster in your load balancing configuration, ensure the following:
* All web servers within the internal cluster must share a single SQL Server database.
* All web servers within the internal cluster must have access to a shared storage location for attachments.
* Install Cisco Unified MeetingPlace Web Conferencing on each server sequentially (internal web server 1, internal web server 2, and so forth) with the following option: for Server Location, choose Internal (Full Access).
* Make sure that all web servers within the internal cluster have the same deployment settings and configurations (for example, the same Replication Service and Audio Service parameters).

===== External Web Server Cluster Requirements =====

If you have an external web server cluster in your load balancing configuration, ensure the following:
* All web servers within the external cluster must share a single SQL Server database.
: '''Note: ''' Make sure the internal cluster and external cluster use different databases.
* All web servers within the external cluster must have access to a shared storage location (for attachments).
* Install Cisco Unified MeetingPlace Web Conferencing on each server sequentially (external web server 1, external web server 2 and so forth) with the following option: for Server Location, choose External (Limited Access).
* Make sure that all web servers within the external cluster have the same deployment settings and configurations (for example, the same Replication Service and Audio Service parameters).

===== Mixed Cluster Requirements =====

A mixed cluster has at least one internal cluster and one external cluster. If you have a mixed cluster in your load balancing configuration, ensure the following:
* All requirements for internal web server clusters and external web server clusters are met.
* The internal cluster's database and external cluster's database must contain identical GUIDS.

===== Port Access Requirements =====
* TCP ports 8506 and 8507 must be open bidirectional between each Web Conferencing server in a load balancing cluster.

== SSL Requirements ==

Secure Sockets Layer (SSL) is not compatible with Cisco Unified IP Phone integration and is not compatible with Windows Integrated Authentication (WIA).

== Segmented Meeting Access Requirements ==

Cisco Unified MeetingPlace Web Conferencing supports Segmented Meeting Access - 2 Server (SMA-2S) deployments for external access.

'''Note: ''' The Segmented Meeting Access - 1 Server (SMA-1S) deployment is no longer supported in Release 6.x.

The following requirements are in addition to standard Cisco Unified MeetingPlace Web Conferencing hardware and software system requirements as indicated in the [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Hardware Requirements|Hardware Requirements]] and the [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Software Requirements|Software Requirements]]. Make sure that you meet the following requirements before you attempt the SMA-2S deployment.

===== Hardware Requirements =====
* Two single Cisco MCSs or clusters of Cisco MCSs (in the case of load balancing)
** One server or cluster of servers deployed inside the private corporate network functioning as internal web servers.
** One server or cluster of servers deployed in a network segment, such as a DMZ, functioning as external web servers.

===== Software Requirements =====
* On internal web servers, Cisco Unified MeetingPlace Web Conferencing Release 6.x installed with the "Internal (Full Access)" server location option.
* On external web servers, Cisco Unified MeetingPlace Web Conferencing Release 6.x installed with the "External (Limited Access)" server location option.

===== DNS Configuration Requirements =====
* For segmented DNS, the same host name must resolve to the internal web server on the internal DNS and resolve to the external web server on the external DNS.
* For information on configuring notification templates to accommodate nonsegmented DNS, see the administration guide for your particular Cisco Unified MeetingPlace notification application.
* Make sure that the internal host names and IP addresses are accessible only from the internal network.
* Make sure that the external host names or IP addresses are accessible from both the internal network and the Internet.

===== Port Access Requirements =====
* Make sure that the following ports are open between the DMZ and the internal network:
** TCP ports 5003 and 5005 are open bidirectional between the web server and the Cisco Unified MeetingPlace Audio Server systems (primary server and shadow server, if one exists).
:: If you configured your network for reverse connection, where your web servers are configured with a MeetingPlace Server hostname instead of an IP address, the Audio Server system can initiate a reverse connection to the web server in the DMZ when port 5003 inbound is blocked.
* Make sure that the following ports are open inbound from the Internet to the DMZ:
** TCP Port 80
** TCP Port 1627 (strongly recommended for higher performance of the meeting console)
** TCP Port 443(if SSL is implemented)

===== Additional Requirements =====
* Synchronized GUIDS between Internal and DMZ servers
: The database of the internal server and external server must contain identical GUIDS.

== WebConnect Requirements ==

WebConnect is used to make web scheduling and meeting attendance seamless across multiple Cisco Unified MeetingPlace systems. Make sure that your system meets the following requirements before you configure WebConnect.

'''Note: ''' We do not support the WebConnect feature on UNIX systems.

===== Cisco Unified MeetingPlace Audio Server Requirements =====
* For Cisco Unified MeetingPlace Web Conferencing Release 6.x: Cisco Unified MeetingPlace Audio Server Release 6.x
* Cisco Unified MeetingPlace MeetingTime Release 6.x with the following settings:
** User profile > Sched only on scheduling home server? > No
** User profile > Sched only on NS home site? > No
** System Parameters > Allow Vanity Mtg IDs? > Yes

===== Additional Requirements =====
* Make sure that all sites within the Cisco Unified MeetingPlace Image are running the same build-level release of Cisco Unified MeetingPlace Audio Server.
* Make sure that all systems within a site have the same system options and notification vehicles. For example, MeetingNotes, Cisco Unified MeetingPlace SMTP E-Mail Gateway, Microsoft Outlook.
* For external dedicated sites, make sure that you are using VPN (T1 or Frame Relay).
* For rollover map configurations, make sure that you assign all users to a group.
: '''Note: ''' You must assign all groups to a rollover map (even if the rollover map only has one site).
* You must have Cisco Unified MeetingPlace Directory Services or a similar profile synchronization procedure deployed on a dedicated server.

== End-User Requirements ==

Make sure that user workstations meet the client requirements in this section, or provide these requirements to your users. All client machines must have separate Internet and telephony access for attending voice and web conferences. The recommended minimum bandwidth is a 56K modem connection. A lesser connection can slow down web-conferencing performance.

Service packs (SPs) listed are required minimums, and service pack releases later than the ones listed are assumed to work unless documented otherwise.
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Client Requirements: Microsoft Windows|Client Requirements: Microsoft Windows]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Client Requirements: Apple Mac|Client Requirements: Apple Mac]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Client Requirements: Sun Solaris|Client Requirements: Sun Solaris]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Client Requirements: RedHat Linux|Client Requirements: RedHat Linux]]

=== Client Requirements: Microsoft Windows ===

===== Table: Supported Web Browsers by Microsoft Windows Operating System Version =====

{| border = 1
|-
!Operating System Version
!Supported Web Browsers
|-
|

Windows Vista
|
* Microsoft Internet Explorer 7.0 and later
* Mozilla Firefox 1.5 or 2.0
* Mozilla Firefox 3.0'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
|-
|

Windows XP (with SP1 or later)
|
* Microsoft Internet Explorer 6.0 with SP1 or SP2
* Microsoft Internet Explorer 7.0 and later
* Mozilla Firefox 1.5 or 2.0
* Mozilla Firefox 3.0'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
|-
|

Windows 2000 (with SP2 or later)
|
* Microsoft Internet Explorer 5.5 SP2
* Mozilla Firefox 1.5 or 2.0
* Netscape 7.1
|}

===== '''Requirements for Participating in a Cisco Unified MeetingPlace Web Conference''' =====
* Adobe Flash Player 6.0.79 - Release 9.x
* Adobe Flash Player 10'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
* (Optional) Audio player that plays WAV, WMA, or MP3 files.
* (Optional, but strongly recommended) TCP port 1627 open from client-to-server on your firewall for direct inbound access.
: If this port is not open, the meeting console establishes a slightly slower connection by tunneling through port 80.

===== '''Requirements for Sharing Desktop Content and Applications''' =====
* Cisco Unified Presenter Add-In (can be downloaded from the Browser Test link on the Web Conferencing home page or from within the meeting console).

* After you download and install the Cisco Unified Presenter Add-In, you must log in to Cisco Unified MeetingPlace locally and not by using a roaming profile. Cisco Unified MeetingPlace does not support roaming profiles because in that case, your settings (including the add-in) are not stored locally but on a server drive.

===== '''Additional Requirements for Video Conferencing''' =====

To make sure that your end-user system is set up for video conferencing, see [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration, Release 5.4 For Use With Release 6.x|Cisco Unified MeetingPlace Video Integration, Release 5.4 For Use With Release 6.x]].

===== Requirements for Playing Meeting Recordings =====

To listen to voice recordings, users must have a corresponding audio player installed on their end-user systems. The following table lists the audio file formats supported by Cisco Unified MeetingPlace Web Conferencing as well as the encoder used to convert the format, the player, and media server responsible for each format.

'''Table: Audio Services Compatible with Cisco Unified MeetingPlace Web Conferencing'''

{| border = 1
|-
! Media Service
! Encoder
! Player
! File Type
|-
| Windows Media
| Windows Media 9
| Requires Windows Media Player 7 or a later release.
| .wma
|-
| N/A
| LAME
| MP3 Player
| .mp3
|}

'''Note:''' See also the topics on [[Cisco Unified MeetingPlace, Release 6.x -- About Audio File Conversion|About Audio File Conversion]].

For example:
We recommend that you configure Windows Media Server to enable streaming playback of your audio recordings. See [[Cisco Unified MeetingPlace, Release 6.x -- About Audio File Conversion#To Configure the Windows Media Server|To Configure the Windows Media Server]]. You must install and configure supported services and end-user applications in order for playback to work.

Typically, WAV files are supported by common web browsers and do not require a dedicated server, encoder, and player.

'''Note:''' If the server is running out of disk space while a current recording is being made, the system notifies all users that there is no more space available. To reduce the likelihood of this occurrence, see [[Cisco Unified MeetingPlace, Release 6.x -- About Audio File Conversion|About Audio File Conversion]].

=== Client Requirements: Apple Mac ===

===== '''Operating System''' =====

OS 10.2, 10.3, 10.4, or 10.5

===== Web Browser =====
* Mozilla Firefox 1.5 or 2.0
* Mozilla Firefox 3.0'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
* Mac Safari 1.1, 1.2, or 2.0
* Mac Safari 3.0, 3.1, or 3.2'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''

===== '''Requirements for Participating in a Cisco Unified MeetingPlace Web Conference''' =====
* Adobe Flash Player 6.0.79 - Release 9.x
* Adobe Flash Player 10'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
* (Optional) Audio player that plays WAV, WMA, or MP3 files.
* (Optional, but strongly recommended) TCP port 1627 open from client-to-server on your firewall for direct inbound access.
: If this port is not open, the meeting console establishes a slightly slower connection by tunneling through port 80.

===== '''Requirements for Sharing Desktop Content and Applications''' =====
* Cisco Unified Presenter Add-In (can be downloaded from the Browser Test link on the Web Conferencing home page or from within the meeting console).

=== Client Requirements: Sun Solaris ===

===== Operating System =====

Solaris 9 or a later release

===== Web Browser =====
* Mozilla Firefox 1.5

===== '''Requirements For Participating in a Cisco Unified MeetingPlace Web Conference''' =====
* Adobe Flash Player 6.0.79 - Release 9.x
* Adobe Flash Player 10'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
: Screen sharing and file sharing from the desktop are not available on Unix systems. Users on these systems can share a whiteboard or meeting attachment, view shared files and make annotations, but they cannot share files that reside on their systems with other participants.
* (Optional) Audio player that plays WAV, WMA, or MP3 files.

=== Client Requirements: RedHat Linux ===

===== Operating System =====

RedHat 9 or a later release

===== Web Browser =====
* Mozilla Firefox 1.5 or later

===== '''Requirements For Participating in a Cisco Unified MeetingPlace Web Conference''' =====
* Adobe Flash Player 6.0.79 - Release 9.x
* Adobe Flash Player 10'' (Cisco Unified MeetingPlace Maintenance Release 4 and later only)''
: Screen sharing and file sharing from the desktop are not available on Linux systems. Users on these systems can share a whiteboard or meeting attachment, view shared files and make annotations, but they cannot share files that reside on their systems with other participants.
* (Optional) Audio player that plays WAV, WMA, or MP3 files.

== Upgrade Requirements ==

Upgrading a legacy system to Cisco Unified MeetingPlace Web Conferencing Release 6.0 requires the following:
* Either a supported Cisco MCS H1/I1 or H2/I2 series model (MCS 3.0 series is not supported), or an exact HP or IBM equivalent. For information on Cisco MCS specifications, go to http://www.cisco.com/en/US/products/hw/voiceapp/ps378/index.html.
: '''Note: ''' If you are not using a HP or IBM exact equivalent, you must install Release 6.0 as a new installation on a supported Cisco MCS. For installation requirements, see the [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Hardware Requirements|Hardware Requirements]].
* Windows Server 2003 Enterprise Edition
* Microsoft Internet Information Server (IIS) 6.0
: Microsoft IIS 6.0 is installed with Windows Server 2003
* SQL Server 2000 (SP 4)
** Cisco Unified MeetingPlace Web Conferencing requires the SQL Server Processor License option. For more information, see the Microsoft website.
* Cisco Unified MeetingPlace Web Conferencing Release 5.4 or 5.3.

'''Caution! ''' Do not delete the SQL Server database if you want to maintain your current click-to-attend links, attachments, and meeting recordings. Deleting or rebuilding your current database deletes all this information.

Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook

2009-04-07T23:17:59Z

MeetingPlace Express Moderator: CSCsy92138

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Integration|Integration]]

'''Note: ''' This page applies to Cisco Unified MeetingPlace, Release 7.0.2 only. For information about this topic for Release 7.0.1, see [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]].

== Configuring the Default Authentication Method for Microsoft Outlook Users ==

The front-end Microsoft Outlook integration provides two default user authentication methods:

* Remember me
: The first time a user tries to schedule a Cisco Unified MeetingPlace meeting from Microsoft Outlook, the user is prompted to log in to Cisco Unified MeetingPlace.
: If cookies are enabled on the browser, then the user may select the Remember Me option. The stored cookies are then used for future authentication, so the user does not need to log in each time the user clicks the MeetingPlace tab.
: If the User password expires, the user is prompted to log in to Cisco Unified MeetingPlace and change the password. The user may again select the Remember Me option.

* Single sign-on
*:As long as the following conditions are met, the user is ''not'' prompted to log in to Cisco Unified MeetingPlace after clicking the MeetingPlace tab in Microsoft Outlook:
** The user successfully logs in to Microsoft Exchange or to Active Directory.
** The username in Microsoft Outlook matches the User ID in Cisco Unified MeetingPlace.
** The domain name of the Microsoft Outlook user matches a configured Outlook Single Sign-On Domain in Cisco Unified MeetingPlace.
NOTE: The domain that is listed in the Application Server is the workgroup domain that the client PC is in, not the user domain that the user is logged into. So if your PC is in domainA.company.com and your user account is domainB\''<user name>'', then this value should be domainA.

By default, the system uses the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Remember me|Remember me]] authentication method. If the configured default authentication method fails, the user is prompted to enter the Cisco Unified MeetingPlace User ID and User password.

===== Before You Begin =====

* The [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Single sign-on|Single sign-on]] authentication method was introduced in Cisco Unified MeetingPlace Release 7.0.2.

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Scheduling From Microsoft Outlook#Prerequisites for Scheduling From Microsoft Outlook|Prerequisites for Scheduling From Microsoft Outlook]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Scheduling From Microsoft Outlook#Restrictions for Scheduling From Microsoft Outlook|Restrictions for Scheduling From Microsoft Outlook]].

===== Restrictions =====

* The [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Remember me|Remember me]] authentication method requires that users enable the use of cookies on their browsers.

* The [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Single sign-on|Single sign-on]] authentication method requires that Cisco Unified MeetingPlace users each have a unique username in Microsoft Outlook and Microsoft Exchange that is the same across the entire organization in Active Directory.
: For example, suppose that Cisco Unified MeetingPlace user "userA" is associated with two different domains, domain1.example.com and domain2.example.com, both of which you configured in Cisco Unified MeetingPlace. The [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Single sign-on|Single sign-on]] authentication method assumes that userA@domain1.example.com and userA@domain2.example.com refer to the same "userA" user profile in Cisco Unified MeetingPlace.

* If you upgrade your system from Release 7.0.1 to 7.0.2 and select the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Single sign-on|Single sign-on]] authentication method, then your users will need to install the new Cisco Unified MeetingPlace plug-in for Microsoft Outlook.

===== Procedure =====

# Log in to the Cisco Unified MeetingPlace Administration Center.
# Click '''System Configuration > Outlook Authentication Configuration'''.
# Choose between the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Remember me|Remember me]] and [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Single sign-on|Single sign-on]] authentication methods.
# If you selected [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Single sign-on|Single sign-on]], configure the domains of the Microsoft Outlook users:
## Click '''Add New''', or click an existing entry.
## Enter the domain in the Outlook Single Sign-On Domain field.
## Click '''Save'''.
## Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Step 4|Step 4]] as needed to configure all domains that are used by your Cisco Unified MeetingPlace for Microsoft Outlook users.
# Click '''Save'''.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Outlook Authentication Configuration Page|Outlook Authentication Configuration Page]]

===== What to Do Next =====

* If you want to make multiple Cisco Unified MeetingPlace systems available for meetings scheduled from Microsoft Outlook, proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook|Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook]].

* Otherwise, proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#How to Install the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook|How to Install the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook]].

== Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook ==

The Cisco Unified MeetingPlace plug-in for Microsoft Outlook enables end users to click a tab within the Microsoft Outlook calendar to access a Cisco Unified MeetingPlace scheduling form. The plug-in comes preconfigured with system information that was entered while installing Cisco Unified MeetingPlace on the Application Server. You can, however, perform this task to enable each user to use one calendar to schedule and manage meetings on multiple Cisco Unified MeetingPlace systems.

When multiple Cisco Unified MeetingPlace systems are available, the user may specify which system to use by default. This and other preferences are configured from Microsoft Outlook by clicking '''Tools > Options''' and selecting the '''MeetingPlace''' tab.

===== Before You Begin =====

* Perform this task only if you want to make multiple Cisco Unified MeetingPlace systems available for meetings scheduled from Microsoft Outlook.

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Scheduling From Microsoft Outlook|Prerequisites for Scheduling From Microsoft Outlook]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Scheduling From Microsoft Outlook|Restrictions for Scheduling From Microsoft Outlook]].

===== Procedure =====

# Log in to the Cisco Unified MeetingPlace Administration Center.
# Click '''System Configuration > Outlook Plug-In Configuration'''.
# Click '''Add New''', or click an existing entry.
# Enter the name and URL for the Application Server of the Cisco Unified MeetingPlace system.
# Click '''Save'''.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Outlook Plug-In Configuration Page|Outlook Plug-In Configuration Page]]

===== What to Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#How to Install the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook|How to Install the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook]].

== How to Install the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook ==

=== Requirements for Client Installation of the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook ===

* Install the Cisco Unified MeetingPlace plug-in for Microsoft Outlook on the PCs of all Microsoft Outlook end users that are connected to your Microsoft Exchange Server. If a Microsoft Outlook end user does not have the plug-in installed when the user clicks the MeetingPlace tab in a received meeting notification, that user may see an error. Users who are not connected to the Microsoft Exchange Server do not see the MeetingPlace tab.

* If Microsoft Outlook delegates will use the Microsoft Outlook calendar to schedule Cisco Unified MeetingPlace meetings on behalf of other users, each Microsoft Outlook delegate and each person on whose behalf meetings are scheduled must install the Cisco Unified MeetingPlace plug-in for Microsoft Outlook.
*: '''Note: ''' Microsoft Outlook delegates are completely separate from Cisco Unified MeetingPlace delegates. The type of user and user ID of delegate fields in Cisco Unified MeetingPlace user profiles do not affect the privileges and capabilities of Microsoft Outlook delegates.

=== Installing the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook Locally on the End-User PC ===

===== Before You Begin =====

* Install the msft_int license. See [[Cisco Unified MeetingPlace, Release 7.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]].

* If you want to enable each user to use one calendar to schedule and manage meetings on multiple Cisco Unified MeetingPlace systems, complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook|Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Requirements for Client Installation of the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook|Requirements for Client Installation of the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook]].

===== Restriction =====

This installation option is available only for Windows PCs. The "Download Outlook Plug-In" link on the end-user web interface does not appear for other PCs.

===== Procedure =====

# Log in to the end-user PC with administrator access.
# Sign in to the Cisco Unified MeetingPlace end-user web interface of an internal Web Server.
# Click '''Download Outlook Plug-In'''.
# Click '''Save'''.
# After the setup.exe file is downloaded, complete these steps on the client PC:
## Exit the Microsoft Outlook client software.
## Run the setup.exe file.
##: '''Note: ''' To make the Cisco Unified MeetingPlace scheduling form available to any user who logs in to a specific computer (Windows 2003, Windows 2000, or Windows XP only), use the '''-admin''' switch to install the client software. Specifically, click '''Start > Run''', then enter '''''<pathname>''setup.exe -admin'''.
## Click '''OK''' to install.
# After installation is complete, launch Microsoft Outlook.
# Verify that you can schedule meetings by clicking the MeetingPlace tab and filling out the scheduling form.
#: For details, click '''Help''' in the scheduling form.

===== What to Do Next =====

(Optional) Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Customizing the Cisco Unified MeetingPlace Scheduling Form for Microsoft Outlook|Customizing the Cisco Unified MeetingPlace Scheduling Form for Microsoft Outlook]].

=== Installing the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook By Using an Automated Distribution Tool ===

This section describes how to use an automated distribution system, such as the Microsoft Systems Management Server (SMS), to remotely distribute and install the Cisco Unified MeetingPlace plug-in for Microsoft Outlook.

You can install the Cisco Unified MeetingPlace plug-in for Microsoft Outlook using either or both of the following switches:

* Silent -- Suppresses the need for user input.

* Admin -- Installs the Cisco Unified MeetingPlace plug-in for Microsoft Outlook for access by all users of a computer.

===== Before You Begin =====

* Install the msft_int license. See [[Cisco Unified MeetingPlace, Release 7.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]].

* If you want to enable each user to use one calendar to schedule and manage meetings on multiple Cisco Unified MeetingPlace systems, complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook|Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Requirements for Client Installation of the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook|Requirements for Client Installation of the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook]].

===== Restriction =====

Cisco Systems does not provide technical support for automated distribution tools.

===== Procedure =====

# (Optional) Test that the installation switches work correctly by completing these steps from a client PC:
## Choose '''Start > Run''' and enter: '''''<path to setup.exe>''/admin /silent'''.
## Verify that no user prompts appear on the end user PC.
## Verify that the following server information exists in the registry:
##* HKCU\software\Latitude\MeetingPlace for Outlook
##* HKU\.default\software\Latitude\MeetingPlace for Outlook (admin)
# Use an automated distribution tool to distribute and install the setup.exe file on end-user PCs.
#: Refer to the documentation for your specific automated distribution tool.
# Instruct the end user to verify successful installation by completing these steps on the end-user PC:
## Restart or launch Microsoft Outlook.
## Open the calendar.
## Verify that the MeetingPlace tab works.
# Remind end users that they can click '''Help''' in the Cisco Unified MeetingPlace scheduling form.

===== What to Do Next =====

(Optional) Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- Customization Options for Scheduling from Microsoft Outlook#Customization Options for Scheduling from Microsoft Outlook|Customization Options for Scheduling from Microsoft Outlook]].

== Customizing the Cisco Unified MeetingPlace Scheduling Form for Microsoft Outlook ==

From Microsoft Outlook, users access the Cisco Unified MeetingPlace scheduling form by creating or opening a calendar appointment and then clicking the MeetingPlace tab. You can choose the information and options that users see in the Cisco Unified MeetingPlace scheduling form.

===== Procedure =====

# Log in to the Cisco Unified MeetingPlace Administration Center.
# Click '''System Configuration > Customize Outlook Interface'''.
# Choose the language.
# Customize or hide fields as desired for the scheduling form specific to that language.
# Click '''Save'''.
# Repeat this task for each language used on your system.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customize Outlook Interface|Customize Outlook Interface]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customization Options for Scheduling from Microsoft Outlook|Customization Options for Scheduling from Microsoft Outlook]]

[[Category: Integrating Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements

2009-04-07T23:14:41Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Notes Release 7.0 ==

For the IBM Lotus Notes with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server (which also hosts the integration), and an IBM Lotus Domino server.

===== Table: Requirements for IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Domino Server
|

'''Hardware'''
* Microsoft Windows computer.

'''Operating System'''
* Windows.

'''Software'''
* IBM Lotus Domino Release 6.0x, 6.5x, 7.0x, or 8.0x.
|-
|
Cisco Unified MeetingPlace Web Server

'''Note: ''' The Cisco Unified MeetingPlace for IBM Lotus Notes integration is installed on the Web Server.
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''License'''
* The Cisco Unified MeetingPlace ''lotusnotes'' license.

'''Software'''
* IBM Lotus Notes client Release 6.0.x, 6.5.x, 7.0.x, or 8.0.x.
* Microsoft Internet Information Server (IIS) Release 6.0.

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|
Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-

|

End-User System
|
''' Hardware'''
* Microsoft Windows computer.

''' Software'''
* Templates 6.0.4, 6.0.5, 6.5.4, 6.5.5, 6.5.6, 7.0.2, 7.0.3, and 8.0.
* Users of IBM Lotus Domino Server Release 6 require:
** IBM Lotus Notes Release 6.0.5 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 6.5 require:
** IBM Lotus Notes Release 6.5.6 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 7 require:
** IBM Lotus Notes Release 7.0.3 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 8 require:
** IBM Lotus Notes Release 8.0 or earlier release
** Template of the same release as the client

''' Operating System'''
* One of the following:
** Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 Server Edition (Service Pack 2 or later)
** Windows 2000 Advanced Server Edition (Service Pack 2 or later)
** Windows XP
|}

== Requirements for Cisco Unified MeetingPlace Click-to-Conference with IBM Lotus Sametime Instant Messaging Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* Cisco Unified MeetingPlace Web Server
* IBM Lotus Sametime Server

===== Table: Requirements for IBM Lotus Sametime Instant Messaging for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Software'''
* IBM Lotus Sametime Release 7.5.1 or later release
* IBM Lotus Notes Release 8.0.1 or later release
|-
|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
''' Hardware'''
* Microsoft Windows

''' Software'''
* IBM Lotus Sametime Connect Client Version 7.5.1 or later release
* Client Browsers
** Mozilla 1.7.12 on Windows XP
** Firefox 1.5 on Windows XP
** Firefox 2.0
** Internet Explorer 6.0, 7.0 on Windows XP Professional, Windows XP Professional 64-bit

''' Operating System'''
* Microsoft Windows
** Windows XP Professional Service Pack 2
** Windows XP Professional 64-bit only for Web Conferencing
** Windows 2000
** Microsoft Vista
|}

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Sametime Web Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* IBM Lotus Sametime Server.

'''Notes: '''
* Because the IBM Lotus Sametime Server cannot support multiple Telephony Conferencing Service Provider Interface (TCSPI) server-side integrations, you cannot use both of the following integrations at the same time:
** Cisco Unified MeetingPlace for IBM Lotus Sametime Web (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified MeetingPlace)
** Cisco Click to Call and Conference with IBM Lotus Sametime (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified Communications Manager)
*: These two server-side integrations are mutually exclusive and cannot both be deployed at the same time.
* You can, however, deploy Cisco Unified MeetingPlace for IBM Lotus Sametime Web with either or both of the following client-side integrations:
** Cisco Unified Messaging with IBM Lotus Sametime
** Cisco Phone Control and Presence with IBM Lotus Sametime

===== Table: Requirements for IBM Lotus Sametime Web for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Hardware'''
* Microsoft Windows computer

'''Operating System'''
* Windows Server 2003 Standard
* Windows Server 2003 Enterprise Edition Service Pack 2

'''Software'''
* IBM Lotus Sametime Server 7.5.1 CF1
: Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.
* IBM Lotus Sametime Server 8.0.1
: Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.
|-

|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
* IBM Lotus Sametime Connect Client Version 7.5.1 CF1
: Also see the client requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.
* IBM Lotus Sametime Connect Client Version 8.0
: Also see the client requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.
|}

== Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 ==

For the Jabber with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server, and a Jabber XCP server.

===== Table: Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

Jabber XCP server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Windows.

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx
|-
|
Cisco Unified MeetingPlace Web Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx

'''License'''
* Cisco Unified MeetingPlace ''jabber'' license

'''Other'''
* Microsoft Internet Information Server (IIS) Release 6.0

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|

Cisco Unified MeetingPlace Application Server

|

See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-User System
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Jabber Messenger Release 3.2, Windows version

'''Operating System'''
* Windows

'''Other'''
* End users who initiate Cisco Unified MeetingPlace meetings from Jabber Messenger must be profiled users in Cisco Unified MeetingPlace.
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) Release 7.0 ==

For the Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) integration, you need an Application Server, a Web Server (which also hosts the integration), and a Live Communications Server (LCS).

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

LCS Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Microsoft Windows 2003

'''Software'''
* Microsoft Live Communications Server (LCS) 2005 Standard or Enterprise Edition
|-
|

Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|
Cisco Unified MeetingPlace Web Server

|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''Software'''
* Windows 2003

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Other'''
* Microsoft .NET 2.0</td>
|-
|

End user
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Microsoft Office Communicator 2005

'''Operating System'''
* Microsoft Windows 2003
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0 ==

'''Note: ''' There are two options for Microsoft Outlook integrations:
* ''Front-end'' integration-Enables users to schedule, reschedule, and cancel meetings from the Microsoft Outlook calendar. For information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]].
* ''Back-end'' integration-Enables Cisco Unified MeetingPlace to send Microsoft Outlook calendar notifications for meetings that are scheduled from the Cisco Unified MeetingPlace end-user web interface. For more information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface]].

The requirements for Microsoft Outlook Integration vary by release:
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1]]

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 ===

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange Server 2003 Service Pack 2
: Enable WebDAV access from Cisco Unified MeetingPlace.
* Microsoft Exchange Server 2007 Service Pack 1
: Enable EWS access from Cisco Unified MeetingPlace and use the Client Access server role.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-user system
|

'''Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook XP, 2003, or 2007 Release 12.0.6023.x and higher.
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook.
* Cisco Unified MeetingPlace for Microsoft Outlook plugin
** Note: If you are upgrading from Cisco Unified MeetingPlace Release 7.0.1 to Release 7.0.2, you must also upgrade the Cisco Unified MeetingPlace for Microsoft Outlook plugin if you enable the Single Sign On option.

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 ===

For the Cisco Unified MeetingPlace for Microsoft Outlook integration, you need an Application Server, a Web Server (for back-end integration only), and an Exchange Server.

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange 2000 Server Service Pack 2 or Microsoft Exchange Server 2003.

'''Other'''
* A Windows user account that has an associated Microsoft Exchange mailbox. This will be the Microsoft Exchange mailbox for Cisco Unified MeetingPlace for Microsoft Outlook. Note the following:
** The Windows user account must have local administrator privileges.
** The username and password for the Windows user account must match the username and password of the Cisco Unified MeetingPlace for Microsoft Outlook mailbox.
** Log in with this account to install Cisco Unified MeetingPlace for Microsoft Outlook.
** The Windows user account should have access to the default Microsoft Outlook profile.
* Must belong to the same domain as the Integration Server unless they have a trust relationship between them.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

'''Note: ''' (Required for the optional back-end integration option) For each Application Server that is connected to one or more Web Servers, Cisco Unified MeetingPlace for Microsoft Outlook must be installed on one of the connected Web Servers.

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.
|-
|

Cisco Unified MeetingPlace Web Server

(Required only for back-end Microsoft Outlook integration)
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Note: ''' Cisco Unified MeetingPlace for Microsoft Outlook must not be installed on a domain controller.

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Software'''
* Web Conferencing must be installed as an internal (full access) installation and must be running as the primary Cisco Unified MeetingPlace Web Server.
* One of the following Microsoft Outlook clients installed and configured to log in to the Microsoft Exchange mailbox:
** Microsoft Outlook 2007 Service Pack 1 and later
** Microsoft Outlook 2003 Service Pack 3
** Microsoft Outlook 2000 (Service Release 1 and Service Pack 3)
* Collaboration Data Objects (CDO) must be installed.
** For Outlook 2007, CDO is not part of the Outlook installer; you must also install CDO 1.2.1 separately.
** For Microsoft Outlook 2003 or Microsoft Outlook 2000, select CDO as an option during setup; it is not loaded by default. The CDO version must be 6.5.7974.0 or later. This version complies with Daylight Savings Time.
* The default mail client on this computer must be set to Microsoft Outlook.
* The Microsoft Outlook client must be completely installed to the local drive. Network installations are not supported.
* Cisco Unified MeetingPlace for Microsoft Outlook does not support "thin clients" (Citrix or Terminal Server).
* Must belong to the same domain as the Microsoft Exchange Server unless they have a trust relationship between them.
|-
|

End-user system
|
''' Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook 2000 (SR 1), XP, 2003, or 2007 Release 12.0.6023.x and higher
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook
* MeetingPlace Outlook Plugin installed on the Outlook client

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

== Supported Cisco Unified IP Phones for Cisco Unified MeetingPlace PhoneView ==

The following Cisco Unified IP Phones are supported in Cisco Unified MeetingPlace Release 7.0:
* Cisco Unified IP Phone 7940 and 7941 models
* Cisco Unified IP Phone 7960 and 7961 models
* Cisco Unified IP Phone 7970 and 7971 models
* Cisco IP Communicator 1.1(5) or later

Support for the following Cisco Unified IP Phones was introduced in Cisco Unified MeetingPlace Release 7.0.2:
* Cisco Unified IP Phone 7942 and 7945 models
* Cisco Unified IP Phone 7962 and 7965 models
* Cisco Unified IP Phone 7975 model

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements

2009-04-07T23:14:03Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Notes Release 7.0 ==

For the IBM Lotus Notes with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server (which also hosts the integration), and an IBM Lotus Domino server.

===== Table: Requirements for IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Domino Server
|

'''Hardware'''
* Microsoft Windows computer.

'''Operating System'''
* Windows.

'''Software'''
* IBM Lotus Domino Release 6.0x, 6.5x, 7.0x, or 8.0x.
|-
|
Cisco Unified MeetingPlace Web Server

'''Note: ''' The Cisco Unified MeetingPlace for IBM Lotus Notes integration is installed on the Web Server.
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''License'''
* The Cisco Unified MeetingPlace ''lotusnotes'' license.

'''Software'''
* IBM Lotus Notes client Release 6.0.x, 6.5.x, 7.0.x, or 8.0.x.
* Microsoft Internet Information Server (IIS) Release 6.0.

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|
Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-

|

End-User System
|
''' Hardware'''
* Microsoft Windows computer.

''' Software'''
* Templates 6.0.4, 6.0.5, 6.5.4, 6.5.5, 6.5.6, 7.0.2, 7.0.3, and 8.0.
* Users of IBM Lotus Domino Server Release 6 require:
** IBM Lotus Notes Release 6.0.5 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 6.5 require:
** IBM Lotus Notes Release 6.5.6 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 7 require:
** IBM Lotus Notes Release 7.0.3 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 8 require:
** IBM Lotus Notes Release 8.0 or earlier release
** Template of the same release as the client

''' Operating System'''
* One of the following:
** Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 Server Edition (Service Pack 2 or later)
** Windows 2000 Advanced Server Edition (Service Pack 2 or later)
** Windows XP
|}

== Requirements for Cisco Unified MeetingPlace Click-to-Conference with IBM Lotus Sametime Instant Messaging Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* Cisco Unified MeetingPlace Web Server
* IBM Lotus Sametime Server

===== Table: Requirements for IBM Lotus Sametime Instant Messaging for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Software'''
* IBM Lotus Sametime Release 7.5.1 or later release
* IBM Lotus Notes Release 8.0.1 or later release
|-
|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
''' Hardware'''
* Microsoft Windows

''' Software'''
* IBM Lotus Sametime Connect Client Version 7.5.1 or later release
* Client Browsers
** Mozilla 1.7.12 on Windows XP
** Firefox 1.5 on Windows XP
** Firefox 2.0
** Internet Explorer 6.0, 7.0 on Windows XP Professional, Windows XP Professional 64-bit

''' Operating System'''
* Microsoft Windows
** Windows XP Professional Service Pack 2
** Windows XP Professional 64-bit only for Web Conferencing
** Windows 2000
** Microsoft Vista
|}

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Sametime Web Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* IBM Lotus Sametime Server.

'''Notes: '''
* Because the IBM Lotus Sametime Server cannot support multiple Telephony Conferencing Service Provider Interface (TCSPI) server-side integrations, you cannot use both of the following integrations at the same time:
** Cisco Unified MeetingPlace for IBM Lotus Sametime Web (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified MeetingPlace)
** Cisco Click to Call and Conference with IBM Lotus Sametime (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified Communications Manager)
*: These two server-side integrations are mutually exclusive and cannot both be deployed at the same time.
* You can, however, deploy Cisco Unified MeetingPlace for IBM Lotus Sametime Web with either or both of the following client-side integrations:
** Cisco Unified Messaging with IBM Lotus Sametime
** Cisco Phone Control and Presence with IBM Lotus Sametime

===== Table: Requirements for IBM Lotus Sametime Web for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Hardware'''
* Microsoft Windows computer

'''Operating System'''
* Windows Server 2003 Standard
* Windows Server 2003 Enterprise Edition Service Pack 2

'''Software'''
* IBM Lotus Sametime Server 7.5.1 CF1
: Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.

* IBM Lotus Sametime Server 8.0.1
: Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.
|-

|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
* IBM Lotus Sametime Connect Client Version 7.5.1 CF1
: Also see the client requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.* IBM Lotus Sametime Connect Client Version 8.0
: Also see the client requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.
|}

== Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 ==

For the Jabber with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server, and a Jabber XCP server.

===== Table: Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

Jabber XCP server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Windows.

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx
|-
|
Cisco Unified MeetingPlace Web Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx

'''License'''
* Cisco Unified MeetingPlace ''jabber'' license

'''Other'''
* Microsoft Internet Information Server (IIS) Release 6.0

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|

Cisco Unified MeetingPlace Application Server

|

See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-User System
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Jabber Messenger Release 3.2, Windows version

'''Operating System'''
* Windows

'''Other'''
* End users who initiate Cisco Unified MeetingPlace meetings from Jabber Messenger must be profiled users in Cisco Unified MeetingPlace.
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) Release 7.0 ==

For the Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) integration, you need an Application Server, a Web Server (which also hosts the integration), and a Live Communications Server (LCS).

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

LCS Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Microsoft Windows 2003

'''Software'''
* Microsoft Live Communications Server (LCS) 2005 Standard or Enterprise Edition
|-
|

Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|
Cisco Unified MeetingPlace Web Server

|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''Software'''
* Windows 2003

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Other'''
* Microsoft .NET 2.0</td>
|-
|

End user
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Microsoft Office Communicator 2005

'''Operating System'''
* Microsoft Windows 2003
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0 ==

'''Note: ''' There are two options for Microsoft Outlook integrations:
* ''Front-end'' integration-Enables users to schedule, reschedule, and cancel meetings from the Microsoft Outlook calendar. For information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]].
* ''Back-end'' integration-Enables Cisco Unified MeetingPlace to send Microsoft Outlook calendar notifications for meetings that are scheduled from the Cisco Unified MeetingPlace end-user web interface. For more information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface]].

The requirements for Microsoft Outlook Integration vary by release:
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1]]

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 ===

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange Server 2003 Service Pack 2
: Enable WebDAV access from Cisco Unified MeetingPlace.
* Microsoft Exchange Server 2007 Service Pack 1
: Enable EWS access from Cisco Unified MeetingPlace and use the Client Access server role.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-user system
|

'''Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook XP, 2003, or 2007 Release 12.0.6023.x and higher.
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook.
* Cisco Unified MeetingPlace for Microsoft Outlook plugin
** Note: If you are upgrading from Cisco Unified MeetingPlace Release 7.0.1 to Release 7.0.2, you must also upgrade the Cisco Unified MeetingPlace for Microsoft Outlook plugin if you enable the Single Sign On option.

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 ===

For the Cisco Unified MeetingPlace for Microsoft Outlook integration, you need an Application Server, a Web Server (for back-end integration only), and an Exchange Server.

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange 2000 Server Service Pack 2 or Microsoft Exchange Server 2003.

'''Other'''
* A Windows user account that has an associated Microsoft Exchange mailbox. This will be the Microsoft Exchange mailbox for Cisco Unified MeetingPlace for Microsoft Outlook. Note the following:
** The Windows user account must have local administrator privileges.
** The username and password for the Windows user account must match the username and password of the Cisco Unified MeetingPlace for Microsoft Outlook mailbox.
** Log in with this account to install Cisco Unified MeetingPlace for Microsoft Outlook.
** The Windows user account should have access to the default Microsoft Outlook profile.
* Must belong to the same domain as the Integration Server unless they have a trust relationship between them.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

'''Note: ''' (Required for the optional back-end integration option) For each Application Server that is connected to one or more Web Servers, Cisco Unified MeetingPlace for Microsoft Outlook must be installed on one of the connected Web Servers.

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.
|-
|

Cisco Unified MeetingPlace Web Server

(Required only for back-end Microsoft Outlook integration)
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Note: ''' Cisco Unified MeetingPlace for Microsoft Outlook must not be installed on a domain controller.

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Software'''
* Web Conferencing must be installed as an internal (full access) installation and must be running as the primary Cisco Unified MeetingPlace Web Server.
* One of the following Microsoft Outlook clients installed and configured to log in to the Microsoft Exchange mailbox:
** Microsoft Outlook 2007 Service Pack 1 and later
** Microsoft Outlook 2003 Service Pack 3
** Microsoft Outlook 2000 (Service Release 1 and Service Pack 3)
* Collaboration Data Objects (CDO) must be installed.
** For Outlook 2007, CDO is not part of the Outlook installer; you must also install CDO 1.2.1 separately.
** For Microsoft Outlook 2003 or Microsoft Outlook 2000, select CDO as an option during setup; it is not loaded by default. The CDO version must be 6.5.7974.0 or later. This version complies with Daylight Savings Time.
* The default mail client on this computer must be set to Microsoft Outlook.
* The Microsoft Outlook client must be completely installed to the local drive. Network installations are not supported.
* Cisco Unified MeetingPlace for Microsoft Outlook does not support "thin clients" (Citrix or Terminal Server).
* Must belong to the same domain as the Microsoft Exchange Server unless they have a trust relationship between them.
|-
|

End-user system
|
''' Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook 2000 (SR 1), XP, 2003, or 2007 Release 12.0.6023.x and higher
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook
* MeetingPlace Outlook Plugin installed on the Outlook client

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

== Supported Cisco Unified IP Phones for Cisco Unified MeetingPlace PhoneView ==

The following Cisco Unified IP Phones are supported in Cisco Unified MeetingPlace Release 7.0:
* Cisco Unified IP Phone 7940 and 7941 models
* Cisco Unified IP Phone 7960 and 7961 models
* Cisco Unified IP Phone 7970 and 7971 models
* Cisco IP Communicator 1.1(5) or later

Support for the following Cisco Unified IP Phones was introduced in Cisco Unified MeetingPlace Release 7.0.2:
* Cisco Unified IP Phone 7942 and 7945 models
* Cisco Unified IP Phone 7962 and 7965 models
* Cisco Unified IP Phone 7975 model

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements

2009-04-07T23:13:08Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Notes Release 7.0 ==

For the IBM Lotus Notes with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server (which also hosts the integration), and an IBM Lotus Domino server.

===== Table: Requirements for IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Domino Server
|

'''Hardware'''
* Microsoft Windows computer.

'''Operating System'''
* Windows.

'''Software'''
* IBM Lotus Domino Release 6.0x, 6.5x, 7.0x, or 8.0x.
|-
|
Cisco Unified MeetingPlace Web Server

'''Note: ''' The Cisco Unified MeetingPlace for IBM Lotus Notes integration is installed on the Web Server.
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''License'''
* The Cisco Unified MeetingPlace ''lotusnotes'' license.

'''Software'''
* IBM Lotus Notes client Release 6.0.x, 6.5.x, 7.0.x, or 8.0.x.
* Microsoft Internet Information Server (IIS) Release 6.0.

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|
Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-

|

End-User System
|
''' Hardware'''
* Microsoft Windows computer.

''' Software'''
* Templates 6.0.4, 6.0.5, 6.5.4, 6.5.5, 6.5.6, 7.0.2, 7.0.3, and 8.0.
* Users of IBM Lotus Domino Server Release 6 require:
** IBM Lotus Notes Release 6.0.5 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 6.5 require:
** IBM Lotus Notes Release 6.5.6 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 7 require:
** IBM Lotus Notes Release 7.0.3 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 8 require:
** IBM Lotus Notes Release 8.0 or earlier release
** Template of the same release as the client

''' Operating System'''
* One of the following:
** Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 Server Edition (Service Pack 2 or later)
** Windows 2000 Advanced Server Edition (Service Pack 2 or later)
** Windows XP
|}

== Requirements for Cisco Unified MeetingPlace Click-to-Conference with IBM Lotus Sametime Instant Messaging Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* Cisco Unified MeetingPlace Web Server
* IBM Lotus Sametime Server

===== Table: Requirements for IBM Lotus Sametime Instant Messaging for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Software'''
* IBM Lotus Sametime Release 7.5.1 or later release
* IBM Lotus Notes Release 8.0.1 or later release
|-
|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
''' Hardware'''
* Microsoft Windows

''' Software'''
* IBM Lotus Sametime Connect Client Version 7.5.1 or later release
* Client Browsers
** Mozilla 1.7.12 on Windows XP
** Firefox 1.5 on Windows XP
** Firefox 2.0
** Internet Explorer 6.0, 7.0 on Windows XP Professional, Windows XP Professional 64-bit

''' Operating System'''
* Microsoft Windows
** Windows XP Professional Service Pack 2
** Windows XP Professional 64-bit only for Web Conferencing
** Windows 2000
** Microsoft Vista
|}

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Sametime Web Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* IBM Lotus Sametime Server.

'''Notes: '''
* Because the IBM Lotus Sametime Server cannot support multiple Telephony Conferencing Service Provider Interface (TCSPI) server-side integrations, you cannot use both of the following integrations at the same time:
** Cisco Unified MeetingPlace for IBM Lotus Sametime Web (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified MeetingPlace)
** Cisco Click to Call and Conference with IBM Lotus Sametime (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified Communications Manager)
*: These two server-side integrations are mutually exclusive and cannot both be deployed at the same time.
* You can, however, deploy Cisco Unified MeetingPlace for IBM Lotus Sametime Web with either or both of the following client-side integrations:
** Cisco Unified Messaging with IBM Lotus Sametime
** Cisco Phone Control and Presence with IBM Lotus Sametime

===== Table: Requirements for IBM Lotus Sametime Web for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Hardware'''
* Microsoft Windows computer

'''Operating System'''
* Windows Server 2003 Standard
* Windows Server 2003 Enterprise Edition Service Pack 2

'''Software'''
* IBM Lotus Sametime Server 7.5.1 CF1
: Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.
* IBM Lotus Sametime Server 8.0.1
: Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.
|-

|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
* IBM Lotus Sametime Connect Client Version 7.5.1 CF1
: Also see the client requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.* IBM Lotus Sametime Connect Client Version 8.0
: Also see the client requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.
|}

== Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 ==

For the Jabber with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server, and a Jabber XCP server.

===== Table: Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

Jabber XCP server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Windows.

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx
|-
|
Cisco Unified MeetingPlace Web Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx

'''License'''
* Cisco Unified MeetingPlace ''jabber'' license

'''Other'''
* Microsoft Internet Information Server (IIS) Release 6.0

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|

Cisco Unified MeetingPlace Application Server

|

See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-User System
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Jabber Messenger Release 3.2, Windows version

'''Operating System'''
* Windows

'''Other'''
* End users who initiate Cisco Unified MeetingPlace meetings from Jabber Messenger must be profiled users in Cisco Unified MeetingPlace.
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) Release 7.0 ==

For the Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) integration, you need an Application Server, a Web Server (which also hosts the integration), and a Live Communications Server (LCS).

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

LCS Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Microsoft Windows 2003

'''Software'''
* Microsoft Live Communications Server (LCS) 2005 Standard or Enterprise Edition
|-
|

Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|
Cisco Unified MeetingPlace Web Server

|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''Software'''
* Windows 2003

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Other'''
* Microsoft .NET 2.0</td>
|-
|

End user
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Microsoft Office Communicator 2005

'''Operating System'''
* Microsoft Windows 2003
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0 ==

'''Note: ''' There are two options for Microsoft Outlook integrations:
* ''Front-end'' integration-Enables users to schedule, reschedule, and cancel meetings from the Microsoft Outlook calendar. For information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]].
* ''Back-end'' integration-Enables Cisco Unified MeetingPlace to send Microsoft Outlook calendar notifications for meetings that are scheduled from the Cisco Unified MeetingPlace end-user web interface. For more information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface]].

The requirements for Microsoft Outlook Integration vary by release:
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1]]

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 ===

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange Server 2003 Service Pack 2
: Enable WebDAV access from Cisco Unified MeetingPlace.
* Microsoft Exchange Server 2007 Service Pack 1
: Enable EWS access from Cisco Unified MeetingPlace and use the Client Access server role.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-user system
|

'''Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook XP, 2003, or 2007 Release 12.0.6023.x and higher.
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook.
* Cisco Unified MeetingPlace for Microsoft Outlook plugin
** Note: If you are upgrading from Cisco Unified MeetingPlace Release 7.0.1 to Release 7.0.2, you must also upgrade the Cisco Unified MeetingPlace for Microsoft Outlook plugin if you enable the Single Sign On option.

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 ===

For the Cisco Unified MeetingPlace for Microsoft Outlook integration, you need an Application Server, a Web Server (for back-end integration only), and an Exchange Server.

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange 2000 Server Service Pack 2 or Microsoft Exchange Server 2003.

'''Other'''
* A Windows user account that has an associated Microsoft Exchange mailbox. This will be the Microsoft Exchange mailbox for Cisco Unified MeetingPlace for Microsoft Outlook. Note the following:
** The Windows user account must have local administrator privileges.
** The username and password for the Windows user account must match the username and password of the Cisco Unified MeetingPlace for Microsoft Outlook mailbox.
** Log in with this account to install Cisco Unified MeetingPlace for Microsoft Outlook.
** The Windows user account should have access to the default Microsoft Outlook profile.
* Must belong to the same domain as the Integration Server unless they have a trust relationship between them.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

'''Note: ''' (Required for the optional back-end integration option) For each Application Server that is connected to one or more Web Servers, Cisco Unified MeetingPlace for Microsoft Outlook must be installed on one of the connected Web Servers.

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.
|-
|

Cisco Unified MeetingPlace Web Server

(Required only for back-end Microsoft Outlook integration)
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Note: ''' Cisco Unified MeetingPlace for Microsoft Outlook must not be installed on a domain controller.

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Software'''
* Web Conferencing must be installed as an internal (full access) installation and must be running as the primary Cisco Unified MeetingPlace Web Server.
* One of the following Microsoft Outlook clients installed and configured to log in to the Microsoft Exchange mailbox:
** Microsoft Outlook 2007 Service Pack 1 and later
** Microsoft Outlook 2003 Service Pack 3
** Microsoft Outlook 2000 (Service Release 1 and Service Pack 3)
* Collaboration Data Objects (CDO) must be installed.
** For Outlook 2007, CDO is not part of the Outlook installer; you must also install CDO 1.2.1 separately.
** For Microsoft Outlook 2003 or Microsoft Outlook 2000, select CDO as an option during setup; it is not loaded by default. The CDO version must be 6.5.7974.0 or later. This version complies with Daylight Savings Time.
* The default mail client on this computer must be set to Microsoft Outlook.
* The Microsoft Outlook client must be completely installed to the local drive. Network installations are not supported.
* Cisco Unified MeetingPlace for Microsoft Outlook does not support "thin clients" (Citrix or Terminal Server).
* Must belong to the same domain as the Microsoft Exchange Server unless they have a trust relationship between them.
|-
|

End-user system
|
''' Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook 2000 (SR 1), XP, 2003, or 2007 Release 12.0.6023.x and higher
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook
* MeetingPlace Outlook Plugin installed on the Outlook client

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

== Supported Cisco Unified IP Phones for Cisco Unified MeetingPlace PhoneView ==

The following Cisco Unified IP Phones are supported in Cisco Unified MeetingPlace Release 7.0:
* Cisco Unified IP Phone 7940 and 7941 models
* Cisco Unified IP Phone 7960 and 7961 models
* Cisco Unified IP Phone 7970 and 7971 models
* Cisco IP Communicator 1.1(5) or later

Support for the following Cisco Unified IP Phones was introduced in Cisco Unified MeetingPlace Release 7.0.2:
* Cisco Unified IP Phone 7942 and 7945 models
* Cisco Unified IP Phone 7962 and 7965 models
* Cisco Unified IP Phone 7975 model

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements

2009-04-07T23:11:42Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Notes Release 7.0 ==

For the IBM Lotus Notes with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server (which also hosts the integration), and an IBM Lotus Domino server.

===== Table: Requirements for IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Domino Server
|

'''Hardware'''
* Microsoft Windows computer.

'''Operating System'''
* Windows.

'''Software'''
* IBM Lotus Domino Release 6.0x, 6.5x, 7.0x, or 8.0x.
|-
|
Cisco Unified MeetingPlace Web Server

'''Note: ''' The Cisco Unified MeetingPlace for IBM Lotus Notes integration is installed on the Web Server.
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''License'''
* The Cisco Unified MeetingPlace ''lotusnotes'' license.

'''Software'''
* IBM Lotus Notes client Release 6.0.x, 6.5.x, 7.0.x, or 8.0.x.
* Microsoft Internet Information Server (IIS) Release 6.0.

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.
|-
|
Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-

|

End-User System
|
''' Hardware'''
* Microsoft Windows computer.

''' Software'''
* Templates 6.0.4, 6.0.5, 6.5.4, 6.5.5, 6.5.6, 7.0.2, 7.0.3, and 8.0.
* Users of IBM Lotus Domino Server Release 6 require:
** IBM Lotus Notes Release 6.0.5 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 6.5 require:
** IBM Lotus Notes Release 6.5.6 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 7 require:
** IBM Lotus Notes Release 7.0.3 or earlier release
** Template of the same release as the client
* Users of IBM Lotus Domino Server Release 8 require:
** IBM Lotus Notes Release 8.0 or earlier release
** Template of the same release as the client

''' Operating System'''
* One of the following:
** Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 Server Edition (Service Pack 2 or later)
** Windows 2000 Advanced Server Edition (Service Pack 2 or later)
** Windows XP
|}

== Requirements for Cisco Unified MeetingPlace Click-to-Conference with IBM Lotus Sametime Instant Messaging Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* Cisco Unified MeetingPlace Web Server
* IBM Lotus Sametime Server

===== Table: Requirements for IBM Lotus Sametime Instant Messaging for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Software'''
* IBM Lotus Sametime Release 7.5.1 or later release
* IBM Lotus Notes Release 8.0.1 or later release
|-
|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
''' Hardware'''
* Microsoft Windows

''' Software'''
* IBM Lotus Sametime Connect Client Version 7.5.1 or later release
* Client Browsers
** Mozilla 1.7.12 on Windows XP
** Firefox 1.5 on Windows XP
** Firefox 2.0
** Internet Explorer 6.0, 7.0 on Windows XP Professional, Windows XP Professional 64-bit

''' Operating System'''
* Microsoft Windows
** Windows XP Professional Service Pack 2
** Windows XP Professional 64-bit only for Web Conferencing
** Windows 2000
** Microsoft Vista
|}

== Requirements for Cisco Unified MeetingPlace for IBM Lotus Sametime Web Release 7.0 ==

For the IBM Lotus Sametime Web integration, you need the following servers:
* Cisco Unified MeetingPlace Application Server
* Cisco Unified MeetingPlace Media Server
* IBM Lotus Sametime Server.

'''Notes: '''
* Because the IBM Lotus Sametime Server cannot support multiple Telephony Conferencing Service Provider Interface (TCSPI) server-side integrations, you cannot use both of the following integrations at the same time:
** Cisco Unified MeetingPlace for IBM Lotus Sametime Web (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified MeetingPlace)
** Cisco Click to Call and Conference with IBM Lotus Sametime (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified Communications Manager)
*: These two server-side integrations are mutually exclusive and cannot both be deployed at the same time.
* You can, however, deploy Cisco Unified MeetingPlace for IBM Lotus Sametime Web with either or both of the following client-side integrations:
** Cisco Unified Messaging with IBM Lotus Sametime
** Cisco Phone Control and Presence with IBM Lotus Sametime

===== Table: Requirements for IBM Lotus Sametime Web for Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

IBM Lotus Sametime Server
|

'''Hardware'''
* Microsoft Windows computer

'''Operating System'''
* Windows Server 2003 Standard
* Windows Server 2003 Enterprise Edition Service Pack 2

'''Software'''
* IBM Lotus Sametime Server 7.5.1 CF1
: Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.
* IBM Lotus Sametime Server 8.0.1
: Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.
|-

|
Cisco Unified MeetingPlace Application Server

|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

|-
|

Cisco Unified MeetingPlace Media Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Media Server Requirements|Media Server Requirements]].
|-
|

End-User System
|
* IBM Lotus Sametime Connect Client Version 7.5.1 CF1
: Also see the client requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.* IBM Lotus Sametime Connect Client Version 8.0
: Also see the client requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.
|}

== Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 ==

For the Jabber with Cisco Unified MeetingPlace integration, you need an Application Server, a Web Server, and a Jabber XCP server.

===== Table: Requirements for Jabber with Cisco Unified MeetingPlace Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

Jabber XCP server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Windows.

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx
|-
|
Cisco Unified MeetingPlace Web Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''Software'''
* Jabber XCP server Release 5.1
* Sun Java Runtime Environment (JRE) Release 1.4.2.xx

'''License'''
* Cisco Unified MeetingPlace ''jabber'' license

'''Other'''
* Microsoft Internet Information Server (IIS) Release 6.0

'''Note: ''' Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.</td>
|-
|

Cisco Unified MeetingPlace Application Server

|

See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-User System
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Jabber Messenger Release 3.2, Windows version

'''Operating System'''
* Windows

'''Other'''
* End users who initiate Cisco Unified MeetingPlace meetings from Jabber Messenger must be profiled users in Cisco Unified MeetingPlace.
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) Release 7.0 ==

For the Cisco Unified MeetingPlace for Microsoft Office Communicator (MOC) integration, you need an Application Server, a Web Server (which also hosts the integration), and a Live Communications Server (LCS).

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Office Communicator Release 7.0 =====

{| border = 1
|-
!Component
!Requirement
|-
|

LCS Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Microsoft Windows 2003

'''Software'''
* Microsoft Live Communications Server (LCS) 2005 Standard or Enterprise Edition
|-
|

Cisco Unified MeetingPlace Application Server
|
See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|
Cisco Unified MeetingPlace Web Server

|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later.

'''Software'''
* Windows 2003

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Other'''
* Microsoft .NET 2.0</td>
|-
|

End user
|

'''Hardware'''
* Microsoft Windows computer

'''Software'''
* Microsoft Office Communicator 2005

'''Operating System'''
* Microsoft Windows 2003
|}

== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0 ==

'''Note: ''' There are two options for Microsoft Outlook integrations:
* ''Front-end'' integration-Enables users to schedule, reschedule, and cancel meetings from the Microsoft Outlook calendar. For information, see [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]].
* ''Back-end'' integration-Enables Cisco Unified MeetingPlace to send Microsoft Outlook calendar notifications for meetings that are scheduled from the Cisco Unified MeetingPlace end-user web interface. For more information, see the "Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface" module in the ''Configuration Guide for Cisco Unified MeetingPlace''.

The requirements for Microsoft Outlook Integration vary by release:
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integration Requirements#Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1|Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1]]

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 ===

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.2 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange Server 2003 Service Pack 2
: Enable WebDAV access from Cisco Unified MeetingPlace.
* Microsoft Exchange Server 2007 Service Pack 1
: Enable EWS access from Cisco Unified MeetingPlace and use the Client Access server role.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].
|-
|

End-user system
|

'''Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook XP, 2003, or 2007 Release 12.0.6023.x and higher.
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook.
* Cisco Unified MeetingPlace for Microsoft Outlook plugin
** Note: If you are upgrading from Cisco Unified MeetingPlace Release 7.0.1 to Release 7.0.2, you must also upgrade the Cisco Unified MeetingPlace for Microsoft Outlook plugin if you enable the Single Sign On option.

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

=== Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 ===

For the Cisco Unified MeetingPlace for Microsoft Outlook integration, you need an Application Server, a Web Server (for back-end integration only), and an Exchange Server.

===== Table: Requirements for Cisco Unified MeetingPlace for Microsoft Outlook Release 7.0.1 =====

{| border = 1
|-
!System
!Requirements
|-
|

Microsoft Exchange Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Software'''
* Microsoft Exchange 2000 Server Service Pack 2 or Microsoft Exchange Server 2003.

'''Other'''
* A Windows user account that has an associated Microsoft Exchange mailbox. This will be the Microsoft Exchange mailbox for Cisco Unified MeetingPlace for Microsoft Outlook. Note the following:
** The Windows user account must have local administrator privileges.
** The username and password for the Windows user account must match the username and password of the Cisco Unified MeetingPlace for Microsoft Outlook mailbox.
** Log in with this account to install Cisco Unified MeetingPlace for Microsoft Outlook.
** The Windows user account should have access to the default Microsoft Outlook profile.
* Must belong to the same domain as the Integration Server unless they have a trust relationship between them.
|-
|

Cisco Unified MeetingPlace Application Server
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Application Server Requirements|Application Server Requirements]].

'''Note: ''' (Required for the optional back-end integration option) For each Application Server that is connected to one or more Web Servers, Cisco Unified MeetingPlace for Microsoft Outlook must be installed on one of the connected Web Servers.

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.
|-
|

Cisco Unified MeetingPlace Web Server

(Required only for back-end Microsoft Outlook integration)
|

'''Hardware'''
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Hardware Requirements#Web Server Requirements|Web Server Requirements]].

'''Note: ''' Cisco Unified MeetingPlace for Microsoft Outlook must not be installed on a domain controller.

'''Operating System'''
* Cisco MCS OS 2003.1.2.a SR13 or later

'''License'''
* The Cisco Unified MeetingPlace ''msft_int'' license.

'''Software'''
* Web Conferencing must be installed as an internal (full access) installation and must be running as the primary Cisco Unified MeetingPlace Web Server.
* One of the following Microsoft Outlook clients installed and configured to log in to the Microsoft Exchange mailbox:
** Microsoft Outlook 2007 Service Pack 1 and later
** Microsoft Outlook 2003 Service Pack 3
** Microsoft Outlook 2000 (Service Release 1 and Service Pack 3)
* Collaboration Data Objects (CDO) must be installed.
** For Outlook 2007, CDO is not part of the Outlook installer; you must also install CDO 1.2.1 separately.
** For Microsoft Outlook 2003 or Microsoft Outlook 2000, select CDO as an option during setup; it is not loaded by default. The CDO version must be 6.5.7974.0 or later. This version complies with Daylight Savings Time.
* The default mail client on this computer must be set to Microsoft Outlook.
* The Microsoft Outlook client must be completely installed to the local drive. Network installations are not supported.
* Cisco Unified MeetingPlace for Microsoft Outlook does not support "thin clients" (Citrix or Terminal Server).
* Must belong to the same domain as the Microsoft Exchange Server unless they have a trust relationship between them.
|-
|

End-user system
|
''' Hardware'''
* Microsoft Windows computer

''' Software'''
* Microsoft Outlook 2000 (SR 1), XP, 2003, or 2007 Release 12.0.6023.x and higher
* An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook
* MeetingPlace Outlook Plugin installed on the Outlook client

''' Operating System'''
* One of the following:
** Microsoft Windows ME
** Windows Vista
** Windows 2000 Professional
** Windows 2000 SE with Service Pack 2
** Windows 2000 AS with Service Pack 2
** Windows XP
** Windows Server 2003
|}

== Supported Cisco Unified IP Phones for Cisco Unified MeetingPlace PhoneView ==

The following Cisco Unified IP Phones are supported in Cisco Unified MeetingPlace Release 7.0:
* Cisco Unified IP Phone 7940 and 7941 models
* Cisco Unified IP Phone 7960 and 7961 models
* Cisco Unified IP Phone 7970 and 7971 models
* Cisco IP Communicator 1.1(5) or later

Support for the following Cisco Unified IP Phones was introduced in Cisco Unified MeetingPlace Release 7.0.2:
* Cisco Unified IP Phone 7942 and 7945 models
* Cisco Unified IP Phone 7962 and 7965 models
* Cisco Unified IP Phone 7975 model

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Outlook Authentication Configuration Page

2009-04-07T23:07:28Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information| Reference Information]]

To find this page, click '''System Configuration > Outlook Authentication Configuration'''.

'''Note: ''' This page appears only when the msft_int license is installed.

Use this page to configure the default authentication method for users who schedule Cisco Unified MeetingPlace meetings from Microsoft Outlook.

If you select the Single sign-on authentication method, the following options become available:
* To add a domain, click '''Add New'''.
* To edit an existing entry, click the name of that entry.
* To delete an entry, check the item and click '''Delete Selected'''.

'''Note: ''' This page was introduced in Cisco Unified MeetingPlace Release 7.0.2.

===== Table: Field Reference: Outlook Authentication Configuration Page, Add Outlook Single Sign-On Domain Page, and Edit Outlook Single Sign-On Domain Page =====

{| border = 1
|-
!Field
!Description
|-
|

Outlook Default Authentication method
|

Choose between the Remember me and Single sign-on user authentication options.

Restriction: The Single sign-on option is available only when SSL is enabled on the Application Server.

Default: Remember me
|-
|

Outlook Single Sign-On Domain
|

Specify all domains that are used by your Cisco Unified MeetingPlace for Microsoft Outlook users.

The domain that is listed in the Application Server is the workgroup domain that the client PC is in, not the user domain that the user is logged into. So if your PC is in domainA.company.com and your user account is domainB\''<user name>'', then this value should be domainA.

'''NOTE: ''' If you enter any uppercase letters, the system automatically converts them to lowercase letters.

Default: Application Server domain, which was set during installation.
|}

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Configuring the Default Authentication Method for Microsoft Outlook Users|Configuring the Default Authentication Method for Microsoft Outlook Users]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]]

[[Category: Reference Information for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Outlook Authentication Configuration Page

2009-04-07T23:07:01Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information| Reference Information]]

To find this page, click '''System Configuration > Outlook Authentication Configuration'''.

'''Note: ''' This page appears only when the msft_int license is installed.

Use this page to configure the default authentication method for users who schedule Cisco Unified MeetingPlace meetings from Microsoft Outlook.

If you select the Single sign-on authentication method, the following options become available:
* To add a domain, click '''Add New'''.
* To edit an existing entry, click the name of that entry.
* To delete an entry, check the item and click '''Delete Selected'''.

'''Note: ''' This page was introduced in Cisco Unified MeetingPlace Release 7.0.2.

===== Table: Field Reference: Outlook Authentication Configuration Page, Add Outlook Single Sign-On Domain Page, and Edit Outlook Single Sign-On Domain Page =====

{| border = 1
|-
!Field
!Description
|-
|

Outlook Default Authentication method
|

Choose between the Remember me and Single sign-on user authentication options.

Restriction: The Single sign-on option is available only when SSL is enabled on the Application Server.

Default: Remember me
|-
|

Outlook Single Sign-On Domain
|

Specify all domains that are used by your Cisco Unified MeetingPlace for Microsoft Outlook users.

'''NOTE: ''' If you enter any uppercase letters, the system automatically converts them to lowercase letters.

The domain that is listed in the Application Server is the workgroup domain that the client PC is in, not the user domain that the user is logged into. So if your PC is in domainA.company.com and your user account is domainB\''<user name>'', then this value should be domainA.

Default: Application Server domain, which was set during installation.
|}

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Configuring the Default Authentication Method for Microsoft Outlook Users|Configuring the Default Authentication Method for Microsoft Outlook Users]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]]

[[Category: Reference Information for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Outlook Authentication Configuration Page

2009-04-07T23:03:31Z

MeetingPlace Express Moderator: CSCsy92138

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information| Reference Information]]

To find this page, click '''System Configuration > Outlook Authentication Configuration'''.

'''Note: ''' This page appears only when the msft_int license is installed.

Use this page to configure the default authentication method for users who schedule Cisco Unified MeetingPlace meetings from Microsoft Outlook.

If you select the Single sign-on authentication method, the following options become available:
* To add a domain, click '''Add New'''.
* To edit an existing entry, click the name of that entry.
* To delete an entry, check the item and click '''Delete Selected'''.

'''Note: ''' This page was introduced in Cisco Unified MeetingPlace Release 7.0.2.

===== Table: Field Reference: Outlook Authentication Configuration Page, Add Outlook Single Sign-On Domain Page, and Edit Outlook Single Sign-On Domain Page =====

{| border = 1
|-
!Field
!Description
|-
|

Outlook Default Authentication method
|

Choose between the Remember me and Single sign-on user authentication options.

Restriction: The Single sign-on option is available only when SSL is enabled on the Application Server.

Default: Remember me
|-
|

Outlook Single Sign-On Domain
|

Specify all domains that are used by your Cisco Unified MeetingPlace for Microsoft Outlook users.

If you enter any uppercase letters, the system automatically converts them to lowercase letters.

The domain that must be listed in the Application Server is the workgroup domain that the client PC is in, not the user domain that the user is logged into. So if your PC is in domainA.company.com and your user account is domainB\''<user name>'', then domainA must be listed in the SSO configuration.

Default: Application Server domain, which was set during installation.
|}

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Configuring the Default Authentication Method for Microsoft Outlook Users|Configuring the Default Authentication Method for Microsoft Outlook Users]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]]

[[Category: Reference Information for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Outlook Authentication Configuration Page

2009-04-07T22:58:02Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information| Reference Information]]

To find this page, click '''System Configuration > Outlook Authentication Configuration'''.

'''Note: ''' This page appears only when the msft_int license is installed.

Use this page to configure the default authentication method for users who schedule Cisco Unified MeetingPlace meetings from Microsoft Outlook.

If you select the Single sign-on authentication method, the following options become available:
* To add a domain, click '''Add New'''.
* To edit an existing entry, click the name of that entry.
* To delete an entry, check the item and click '''Delete Selected'''.

'''Note: ''' This page was introduced in Cisco Unified MeetingPlace Release 7.0.2.

===== Table: Field Reference: Outlook Authentication Configuration Page, Add Outlook Single Sign-On Domain Page, and Edit Outlook Single Sign-On Domain Page =====

{| border = 1
|-
!Field
!Description
|-
|

Outlook Default Authentication method
|

Choose between the Remember me and Single sign-on user authentication options.

Restriction: The Single sign-on option is available only when SSL is enabled on the Application Server.

Default: Remember me
|-
|

Outlook Single Sign-On Domain
|

Specify all domains that are used by your Cisco Unified MeetingPlace for Microsoft Outlook users.

If you enter any uppercase letters, the system automatically converts them to lowercase letters.

Default: Application Server domain, which was set during installation.
|}

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Enable Scheduling From Microsoft Outlook#Configuring the Default Authentication Method for Microsoft Outlook Users|Configuring the Default Authentication Method for Microsoft Outlook Users]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]]

[[Category: Reference Information for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- About Synchronization

2009-04-07T18:43:00Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== About Synchronization ==

Synchronizing is time consuming and may take one to two days, depending on the amount of data and the bandwidth between the two servers.

We highly recommend a bandwidth of 100 Mbps.

== Synchronized Tables ==

The following tables are synchronized:
* cscrres
* cscrresfstaccess
* csconf
* csconfatt
* csconfcatrec
* csconfpart
* csconftime
* csdidcnfg
* csdidres
* csflexfield
* csgroup
* csmtgcategory
* csnotification
* csoutdial
* cspomailbox
* cspomsgdata
* cspartnotrec
* csportres
* csportresfstaccess
* csrsconfpart
* csremoteserver
* csschedfail
* csschedparams
* cssystemconfig
* csvideoportres
* csvideoportresfstaccess
* csuser
* csuserlist
* csuserlistmem
* csvsres
* csvsresfstaccess
* uigroup
* uifield
* locale
* tzregion
* csusedpwds
* premiumaudiocodec
* videotype
* userassignedvideotype
* groupassignedvideotype
* csvideorsrcres
* csvideorsrcresfstaccess
* videobitrate
* csautoattendtranslationtable
* conferenceidmap
* csvideoterminalreservation
* notifiteminfo
* eventsubscription
* webconfadapterconfig
* webconfidmap
* webconfpartlist
* dirsync
* dirsyncconfig
* csunit
* wcproviderssametime
* csswconfig
* deletedrec

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- About Synchronization

2009-04-07T18:42:07Z

MeetingPlace Express Moderator: New page: '''Main page:''' Cisco Unified MeetingPlace, Release 7.0 '''Up one level:''' Configuration == About Synchronization ==...

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T18:38:16Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the '''net''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
#: For more information about synchronization, see [[Cisco Unified MeetingPlace, Release 7.0 -- About Synchronization|About Synchronization]].
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T18:37:39Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the '''net''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
#: For more information about synchronization, see [[Cisco Unified MeetingPlace, Release 7.0 -- About Synchronization}About Synchronization]].
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace

2009-04-07T17:51:31Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration, Release 5.4 For Use With Release 6.x|Cisco Unified MeetingPlace Video Integration]]

Procedures in this chapter must be completed before installing the Cisco Unified MeetingPlace Video Integration software on the Web Conferencing server. This chapter can also be used as a reference for adding and changing settings later.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Getting Started|Getting Started]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Resource Management|Resource Management]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Meeting Types|Meeting Types]]

== Getting Started ==

This section includes information about starting and restarting Video Administration, and logging in according to your user type.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Video Administration Configuration Workflow|Video Administration Configuration Workflow]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Starting Video Administration|Starting Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Restarting Video Administration|Restarting Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Logging In|Logging In]]

=== Video Administration Configuration Workflow ===

We recommend that Video Administration administrators configure Video Administration according to the following workflow:
* Installation
* Initial Login
* Resource Configuration
** Gatekeepers/SIP servers
** MCUs
** Gateways
** Terminals
* Configure Meeting Types
** Download/Upload Meeting Types

By default, some sections of the user interface are hidden, according to settings in the Configuration Tool; however, these sections may appear in the documentation. For details about using the Configuration Tool, see the [[Cisco Unified MeetingPlace, Release 6.x -- Video Administration Configuration Tool#Video Administration Configuration Tool|Video Administration Configuration Tool]] chapter.

=== Starting Video Administration ===

Video Administration is installed as a Windows Service on your server. Video Administration automatically starts when the server is started.

=== Restarting Video Administration ===

To restart Video Administration, you must either restart the server or the Video Administration service.

===== To Restart the Video Administration Service =====

# From the Start menu, click '''Settings > Control Panel > Administrative Tools > Services'''.
# From the list of services currently running on the server, select the '''Video Administration for Cisco Unified MeetingPlace''' service.
#: '''Note: ''' When Video Administration is restarted, it may take a few minutes for Video Administration to properly initialize before web pages can be loaded.

=== Logging In ===

After installation is complete, you can log in according to your role.

===== To Log In to Video Administration =====

# Go the location provided in your user setup notification e-mail.
# In the login screen that appears, enter the required information, and then click '''Login'''.
# If you are logging in for the first time, the User Provisioning screen appears. One of the following options is automatically selected. Do not change the selection.
#* Via Video Administration for Cisco Unified MeetingPlace-To use the internal Video Administration database.
#* Via external server only.
# Click '''OK'''.

== Resource Management ==

Use the Resource Management section to organize, assign, and monitor resources.

The following resources are currently supported by Video Administration:
* MCU
** Cisco MCU version 4.x and 5.x
** Cisco Unified Videoconferencing 35xx
* Gatekeepers/SIP servers
** Cisco GK-the internal (ECS) gatekeeper installed with the Video Administration
** Cisco Multimedia Conference Manager (MCM)-also known as the IOS H.323 Gatekeeper.
** Microsoft LCS

===== To Access Resource Management =====

# In the sidebar menu, go to '''Resource Management'''.
# The Resource Management section contains the following tabs:
#* Gatekeeper/SIP server-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Gatekeeper/SIP Server Tab|Using the Gatekeeper/SIP Server Tab]].
#* MCU-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the MCU Tab|Using the MCU Tab]].
#* Gateway-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Gateway Tab|Using the Gateway Tab]].
#* Terminals-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Terminals Tab|Using the Terminals Tab]].
#: '''Note: ''' We recommend that you configure the tabs in the order that they appear, from left to right.

=== Using the Gatekeeper/SIP Server Tab ===

On the Gatekeeper/SIP server tab you can monitor, add, delete and modify gatekeeper and SIP server information.

A gatekeeper/SIP must be listed in the Gatekeeper/SIP server tab before you can add an MCU to its registry.

Cisco GK is listed on the Gatekeeper/SIP server tab. This is an internal gatekeeper.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Access the Gatekeeper/SIP Server Tab|To Access the Gatekeeper/SIP Server Tab]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Gatekeeper/SIP Server|To Add a Gatekeeper/SIP Server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Gatekeeper/SIP Server Definition|To Modify a Gatekeeper/SIP Server Definition]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Gatekeeper/SIP server|To Delete a Gatekeeper/SIP server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Gatekeeper/SIP Server|To Search for a Gatekeeper/SIP Server]]

===== To Access the Gatekeeper/SIP Server Tab =====

# In the sidebar menu, select '''Resource Management'''.
# In Resource Management, select the '''Gatekeeper/SIP Server''' tab.

===== To Add a Gatekeeper/SIP Server =====

The procedure for adding a gatekeeper/SIP server differs slightly depending on which model you select.

When you add a gatekeeper, it is automatically defined as the neighbor of the internal gatekeeper.

# On the Gatekeeper/SIP Server tab, click '''Add'''.
#: The New Gatekeeper/SIP server screen appears.
# In the Name field, enter the name of the Gatekeeper/SIP server.
# In the IP Address field, enter an IP address for the Gatekeeper/SIP server.
# From the Model list, select the type of server that you want to add. Select "Cisco MCM 500" for a Cisco IOS H.323 Gatekeeper.
#: The screen displays options relevant to the server you select. For example, the display of the Protocol list, the Dialing Plan Information, and the Advanced section is dependent on which server you select.
# From the Location list, set the Device Island to which the device belongs.
# Do not configure anything in the Dialing Plan Information section or the Advanced section.
# Click '''OK'''.

===== To Modify a Gatekeeper/SIP Server Definition =====

# On the Gatekeeper/SIP server tab, click the name of the server that you want to modify.
# In the Modify Gatekeeper/SIP server screen, edit the details as required.
# Click '''OK'''.

===== To Delete a Gatekeeper/SIP server =====

You cannot recover a Gatekeeper/SIP server once it is deleted.

# On the Gatekeeper/SIP server tab, click the name of the server that you want to delete.
# In the Modify Gatekeeper/SIP server screen, click '''Delete'''.
# If you want to delete the IP addresses for additional gateways in the Gateway pool, click the '''Modify '''button next to the IP Address field, and then in the Modify Gateway screen, click '''Delete'''.
#: Depending on the current use of the gatekeeper/SIP server, the following events may occur:
#* If there are any meetings scheduled within two hours of the time of deletion that will use this gatekeeper/SIP server, Video Administration does not allow the deletion.
#* If the gatekeeper/SIP server has other gateways mapped as children, Video Administration reconfigures the gateway dialing plan by using those children as root gatekeeper/SIP servers and dialing accordingly.
#* If there are devices registered to the deleted gatekeeper/SIP server, after deletion, they appear as not registered to any gatekeeper/SIP server.
#: '''Note: ''' Reconfigure manually, if necessary, after a gatekeeper/SIP server is deleted.

===== To Search for a Gatekeeper/SIP Server =====

You can search for a gatekeeper/SIP server by name.

# In the Name field, enter all or part of the name of the gatekeeper or SIP server that you want to find.
# Click '''Search'''.
#: If a Gatekeeper/SIP server is found, it appears in the list.
# To view the complete list of Gatekeeper/SIP servers, clear the '''Search''' field, and then click '''Search'''.
#: The following information about connection status is available in the list of search results:
#* Authorization Connection-indicates whether the Internal Gatekeeper/Video Administration authorization link is established. This connection is established only as needed; therefore, it can appear disconnected, which is not an error.
#* Call Control Connection-indicates whether the Internal Gatekeeper/API connection is established by Video Administration.
#* SNMP Connection-indicates whether the SNMP connection between Video Administration and the Internal Gatekeeper is established.

=== Using the MCU Tab ===

On the MCU tab you can monitor, add, delete and modify MCUs.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Select a Priority for Meeting Cascading|To Select a Priority for Meeting Cascading]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]] (For older versions)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]] (For newer versions)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify an MCU|To Modify an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete an MCU|To Delete an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for an MCU|To Search for an MCU]]

===== To Select a Priority for Meeting Cascading =====

Cascading of MCUs is used to reduce potential drain on network resources and to increase the efficiency of MCU usage. The following points about cascading should be noted:
* The service representing the required meeting must be available on all participating MCUs.
* Video Administration meeting control features may not function correctly in manually cascaded meetings.
* We recommend that you not work with clustered MCUs (multiple MP units on a single MCU). Clustered MCU configurations have no control-overload balancing and may cause a single point of failure. Contact Cisco Customer Support for further information.
* Each master MCU uses one port for every slave MCU.
* Each slave MCU that is used in a cascaded meeting requires one additional port.
* Video Administration supports meeting cascading via the Prioritize field that appears in several locations in the Video Administration user interface. Cascading is conducted according to the priority you select.

To select a priority for meeting cascading, you must configure the Local MCU Prioritization Setting in MeetingTime. See Table [[Cisco Unified MeetingPlace, Release 6.x -- Configuring and Managing Cisco Unified MeetingPlace Video Integration#Table: Conference and Port Parameters|Table: Conference and Port Parameters]] for details.

===== To Add an MCU =====
''NOTE: This process is for the version of Video Administration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release (MR) 2, MR 1, or the FCS version.''

# In the MCU tab, click '''Add'''.
#: The New MCU screen opens on the Basic tab.
# From the Model list, select the model of the MCU.
# If you want to register the MCU to a gatekeeper, select from the '''Registered To''' list.
# If you want to register the MCU to an SIP server, check the '''SIP Only''' check box.
#: '''Note: ''' Verify that the MCU is registered to a SIP server and not registered to a H.323 gatekeeper. When you check the SIP Only check box, the Registered To field is inactive.
# From the Location list, select the Device Island to which the MCU belongs.
# If you want to designate a specific port via which Video Administration communicates with the MCU, or to designate SNMP Community passwords (passwords for retrieving and sending information), click the '''Advanced''' tab and edit the default entries in the fields.
#: '''Note: ''' The Advanced tab is active only for certain MCU models, and its fields vary according to the MCU model.
# On either the Basic or the Advanced tab, click '''OK'''.
#: The new MCU appears in the list on the MCU tab.
#: '''Note: ''' If Video Administration and an MCU are located on different networks, your security policy must allow SNMP and XML API connections between Video Administration and the MCU.
#: '''Note: ''' Video Administration cannot connect to a newly configured MCU. The MCU is added but its status is Offline. In this case, in the Modify MCU screen, select the '''Online''' option, and then click '''OK'''. For information about modifying an MCU, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify an MCU|To Modify an MCU]].

===== To Add an MCU =====
''NOTE: This process is for the version of Video Administration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release (MR) 3 or later.''

# Log in to Video Administration at by going to '''http://''<hostname>'':8080'''.
#: '''Note:''' The Video Administration installer defaults to 8080 but if you changed that value during the installation, you should use your custom port.
# Click '''Admin > Resource Management'''.
# Click the MCU tab.
# Click '''Add''' to open the New MCU page.
# Enter values in the required fields, which are indicated by red asterisks:
#* Name:
#* IP Address:
#* Login Name:
#* Login Password:
#* SNMP GET Community:
#* SNMP SET Community:
#* Port: (default is 3336)
#: '''Note:''' If you are unsure of SNMP values, log in to the MCU, click '''Board > Security''', and copy the values from the Security page.
# Select the model of the MCU from the Model list. Do not change the value of the "Registered To:" field. It defaults to “local_gatekeeper”. This is the ECS Gatekeeper on the Video Administration and the MCU must be registered to this value.
# If you want to register the MCU to an SIP server, check the '''SIP Only''' check box.
#: '''Note:''' Verify that the MCU is registered to a SIP server and not registered to a H.323 gatekeeper. When you check the '''SIP Only''' check box, the Registered To field is inactive.
# Click '''OK''' to save and exit the New MCU page.
#: The MCU appears in the list on the MCU tab.
#: '''Note:''' If Video Administration and the MCU are located on different networks, your security policy must allow SNMP and XML API connections between Video Administration and the MCU.

'''Note:''' The Signaling Port may or may not show a value, depending on the version of Video Administration that you are using. This field has no effect, and will automatically display the corresponding Signaling Port configured on the MCU once the MCU connects to the Video Administration.

'''Note:''' Video Administration cannot connect to a newly-configured MCU, when the MCU has been added but its status is offline. In this case, on the Modify MCU page, select the Online option, and then click '''OK'''.

===== To Modify an MCU =====

You can modify MCU information on the Basic tab and on the Advanced tab.

If the specified gatekeeper/SIP server is configured to remove prefixes, MCU service prefixes cannot begin with the same digits as the gatekeeper/SIP server prefix.

# On the MCU tab, click the name of an MCU in the list.
#: The Modify MCU screen appears.
# On the Basic tab, edit the details as required.
# In the Advanced section of the Basic tab, select from the following options:
#* Online-Default setting for all MCUs.
#* Offline Up to Date-To set the date when the MCU should be online again, click the calendar button and select a date. Video Administration does not automatically bring an MCU online; you must bring the MCU online manually on the specified date.
# If you want the MCU to be permanently set to the offline option, check the '''Permanently''' check box. This activates fields in the screen for editing that are otherwise read-only.
#: If you take an MCU offline, the following occurs:
#* Video Administration cannot schedule meetings for the offline MCU.
#* All currently in-progress meetings are terminated. Video Administration attempts to reschedule upcoming meetings for the offline MCU on other MCUs by using the same services and with sufficient, available resources. If no replacement MCUs are available, upcoming meetings are lost and not restored if the MCU status is changed to online.
#* Video Administration attempts to reschedule all meetings that are scheduled to this MCU from the time the MCU goes offline to the date specified in the Offline Up to Date field of the Modify MCU screen.
#* If the MCU is set to be Offline Permanently, Video Administration attempts to reschedule all future meetings.
#: The selection appears on the MCU tab, in the Status column.
# On the Advanced tab, edit the details as required.
# Click '''OK'''.
#: The changes appear in the MCU tab list.

===== To Delete an MCU =====

'''Caution! ''' If you delete an MCU, it cannot be recovered. Note that deleting an MCU, or taking an MCU offline, interrupts any meetings that are in progress and causes any future meetings that are scheduled for the MCU to be rescheduled. There is no guarantee of successful rescheduling.

# On the MCU tab, click the name of the MCU that you want to delete.
# In the MCU screen, select '''Offline''', and then check the '''Permanent''' check box.
# Click '''Delete'''.
# In the message that appears, click '''OK'''.
#: The MCU is deleted from the list in the MCU tab.

===== To Search for an MCU =====

You can search for an MCU by name.

# In the Name field, enter all or part of the name of an MCU.
# Click '''Search'''.
#: If the MCU is located, the MCU name and details appear in the list on the MCU tab.
#: Information in the Connection column indicates whether or not a communication connection is established between Video Administration and the MCU.

=== Using the Gateway Tab ===

Registered gateways are listed on the Gateway tab. You can monitor, add, delete, and modify gateways on the Gateway tab.

Video Administration does not control or communicate with gateways. Video Administration uses gateway setup information to determine resource allocation. It is important for gateway setup information to be accurate.

'''Note: ''' It is rare that you will need to make modifications on the Gateway Tab. When making modifications, ensure that the gateway is installed and set up prior to configuring it in the Video Administration. For details see the Administration Guide applicable to your gateway at: http://www.cisco.com/en/US/products/hw/video/ps1870/prod_maintenance_guides_list.html

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Gateway|To Add a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Gateway|To Modify a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Gateway|To Delete a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Gateway|To Search for a Gateway]]

===== To Add a Gateway =====

When you add a gateway, settings in Video Administration must be consistent with the actual gateway configuration. We recommend the following guidelines:
* If you make changes to the gateway, maintain IVR and DID numbers in Video Administration.
* To ensure that there are gateway ports available for scheduled and ad hoc calls, maintain capacity information.

# In the Resource Management section, click the '''Gateway''' tab.
# Click '''Add'''.
#: The New Gateway screen opens on the Basic tab.
# Enter information in the fields as required.
# From the Gateway Model list, if you select ViaIP-GW-S40, the IMUX field appears. Select an IMUX server for ISDN connection to the network.
# From the Registered To list, select the gatekeeper/SIP server to which the gateway is registered. A complete list of zone prefixes that are configured in Video Administration is displayed following the gatekeeper/SIP server name.
# To enable gateway pooling, modify the IP Address or add additional gateway IP addresses.
# If the gateway supports only dial-in calls, check the '''Dial-In''' check box.
# (Optional) In the Description field, enter a description for the gateway.
# In the International Access code field, enter the numeric prefix that is required to make an international long distance call.
# In the Domestic Long Distance Prefix field, enter the numeric prefix that is required to make a long distance call within the same country.
# In the Country Code field, enter the country code for the gateway phone numbers. Video Administration adds this prefix when dial-out is performed from this gateway to a terminal located in a country different from the gateway.
# If applicable, check the '''Allow Out of Area Calls''' check box.
#: If you do not check the Allow Out of Area Calls check box, only endpoints with the same area code as the gateway are allowed to reach Video Administration via the gateway. In addition, if the check box is unchecked, and you request reserved ports for a gateway, you must verify that the specified gateway has sufficient resources to provide the additional ports.
#: If you check the Allow Out of Area Calls check box, the gateway accepts incoming calls to Video Administration from endpoints with a different area code that is different from the gateway area code. By default, the check box is checked.
# In the Area Code field, enter the domestic area code of the gateway number.
# In the Telephone Number field, specify a local phone number that you assign to the specific port.
# Enter a number in the To Access an Outside Line for Local Calls, Dial field, for a gateway with no direct access to an outside line for local calls.
# Enter a number in the To Access an Outside Line for Long Distance Calls, Dial field, for a gateway with no direct access to an outside line for long distance calls.
# To add or modify an gateway service, click '''Add Service'''.
# To dele]te a gateway service, click '''Add Service''', and then click '''Delete Service'''.
# In the Bandwidth section, if you check the Restricted Mode check box, 56 appears in the Kbps list. Multiples of 56 Kbps are used instead of multiples of 64 Kbps.
# To add additional phone numbers to a gateway, click '''Add Services''', and then enter the required information.

===== To Modify a Gateway =====

Modification of the gateway is restricted to adding Service Prefixes and Bandwidth, unless you take the gateway offline.

# On the Gateway tab, click the name of a gateway in the list.
#: The Modify Gateway screen appears.
# If you want to change the gateway name, enter a new name in the Name field.
# To add a Service Prefix, click '''Add Service'''.
# If you want to edit other fields in the Modify Gateway screen, click '''Offline'''.
#: All fields become active.
# Click '''OK'''.

===== To Delete a Gateway =====

# On the Gateway tab, click the name of a gateway in the list.
#: The Modify Gateway screen appears.
# Click the '''Offline''' option.
# Check the '''Permanently''' check box.
# Click '''Delete'''.
#: The gateway is deleted.
#: All upcoming meetings that were scheduled to use the deleted gateway are rescheduled. For each meeting that is successfully rescheduled, the organizer and participants are notified of the new gateway information. If there are insufficient resources on the network to support a meeting, the meeting is cancelled and the organizer and participants are notified of the cancellation.

===== To Search for a Gateway =====

You can search for a gateway by name.

# In the Name field, enter all or part of the gateway name.
# Click '''Search'''.
#: If the gateway is located, the gateway name and details appear in the list on the Gateway tab.
#: The Connection column indicates whether Video Administration established a communication channel with the gateway.

=== Using the Terminals Tab ===

Registered terminals are listed on the Terminals tab. You can monitor, add, delete, and modify terminals on the Terminals tab.

Adding terminals to the Video Administration database is necessary in order to provide the ability to automatically outdial video participants at the start of a meeting. You can also add personal video endpoints such as Cisco Unified CallManager SCCP or SIP endpoints.

If the terminal information cannot be displayed on one screen, at the bottom of the screen, click the previous or next arrows or click a page number to move between Terminal screen pages.

The current number of terminals being used and the total number of available terminals appears at the bottom of the Terminals tab.

'''NOTE:''' By default, there is a predefined service that uses the prefix 6. If this conflicts with your current dial plan, you can change it using the Scheduling Settings tab in the Video Administration Configuration tool. See [[Cisco_Unified_MeetingPlace%2C_Release_6.x_--_Video_Administration_Configuration_Tool#Scheduling_Settings_Tab|Scheduling_Settings_Tab]] for information on the Video Administration Configuration tool.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Terminal|To Add a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Terminal|To Modify a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Terminal|To Delete a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Terminal|To Search for a Terminal]]

===== To Add a Terminal =====

# In the Terminals tab, click '''Add'''.
#: The Add Terminal screen appears.
#: '''Note: ''' Do not use the Default Users button. Users are configured on the Cisco Unified MeetingPlace Audio Server.
# In the Name field, enter the name of the terminal.
# From the Terminal Type list, select the applicable option:
#* IP(H.323)-choose this for SCCP endpoints
#* ISDN/PSTN(H.320)
#* Dual(H.320 and H.323)
#* IP(SIP)-If you select this option, in the SIP URL field, the terminal name is automatically displayed followed by the SIP server domain name and a suffix derived from the domain name of the SIP server. For example, <terminal name>@<SIP server domain name> or "user@domain_name.com."
#* Mobile-Supports 3G or non-3G terminals
# In the IP Phone number field, enter an E.164 IP phone number that is associated with the terminal. This field only appears when IP(H323) or IP(SIP) is selected in the Terminal Type field.
# From the Registered To list, select a gatekeeper/SIP server to which you want the terminal to be registered.
#: '''Note: ''' In a multi-zone dialing plan, if the terminal is registered to a gatekeeper/SIP server that is not configured to remove prefixes, you must append the zone prefix to the E.164 number.
# From the Location list, select the meeting room location of the terminal. If the terminal is not located in a meeting room within your organization, select '''None'''.
# From the Bandwidth list, select an applicable value in Kbps. Do not use the default value of "audio."
# From the Meeting Room list, select the meeting room in which the terminal is located.
# If you want to receive e-mail notifications regarding terminals, check the '''Notification E-Mail''' check box, and then click '''Browse''' to select a location for the e-mail notifications.
# If you want to change the Default Time Zone for the terminal, select a time zone from the list.
# Click '''OK'''.
#: The new terminal appears in the list on the Terminals tab.
#: '''Note: ''' When a new terminal is added to the Terminals tab, it is available to users in the Meeting Schedule section, on the Invite tab.

===== To Modify a Terminal =====

You can modify a terminal that appears in the list on the Terminals tab.

# On the Terminals tab, click the name of a terminal in the list.
# In the Modify Terminal screen that appears, complete the fields as required.
#: '''Note: ''' Tabs on the Modify Terminal screen are the same as on the Add Terminal screen. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Terminal|To Add a Terminal]].

===== To Delete a Terminal =====

You can delete a meeting room from the list on the Meeting Rooms tab.

# On the Terminals tab, click the name of a terminal in the list.
# In the Modify Terminals screen that appears, click '''Delete'''.
#: The terminal is deleted from the Meeting Rooms list.

===== To Search for a Terminal =====

You can search for a terminal by name or by dialing information.

# To search for a terminal, do one of the following:
#* In the Name field, enter all or part of a terminal name, and then click '''Search'''.
#* To search for a terminal by number, in the Dialing Info field, enter all or part of a terminal IP number or ISDN phone number, and then click '''Search'''.
#: '''Note: ''' The ISDN phone number of the terminal should be include without any dashes or spaces (available only when ISDN(H320) or Dual(H320 and H323) are selected in the Terminal Type field).
#: '''Note: ''' Both IP and ISDN numbers are displayed if the terminal is configured as a dual terminal.
#: Search results are displayed in the Terminal tab list.

== Meeting Types ==

'''Important!''' To enable proper Cisco Unified Videoconferencing MCU resource calculation, meeting types must be downloaded from the MCUs.

In Meeting Types, you can name and define the types of meetings (services) available to the organization. Meeting types include features and options for the user that are designated by the administrator. Deployment and modification of meeting types is applied across the network.

Available options for multipoint meeting types are based on the service features of the MCU. For detailed information about the services your MCU supports, see the relevant MCU manufacturer manuals.

The Meeting Types section includes the following tabs:
* Active Meeting Types-From the Active Meeting Types tab, you can add, deactivate, and upload meetings types. The Status column indicates if the meeting type is currently in use or designated for use in a scheduled meeting.
* Inactive Meeting Types-Meeting types not currently designated for use. Inactive meeting types are available for selection as active meeting types.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Meeting Type Name Display|Meeting Type Name Display]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Naming a Meeting Type|Naming a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Active Meeting Type Tab|Using the Active Meeting Type Tab]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Inactive Meeting Types Tab|Using the Inactive Meeting Types Tab]]

=== Meeting Type Name Display ===

The way a meeting type name is displayed provides useful information about that meeting type:
* Name followed by an asterisk (*)-MCU meeting type, not meeting types defined by Video Administration.
* Name in bold black characters, followed by asterisk (*)-MCU meeting type currently available to users, successfully downloaded from an MCU, or successfully uploaded to other MCUs.
* Name in bold red characters-An MCU meeting type downloaded from an MCU, modified in Video Administration but not uploaded to an MCU, and currently not available to any users.
* Name in bold red characters, followed by asterisk (*)-MCU meeting type downloaded from an MCU but no longer on network MCUs and not currently available to users.

=== Naming a Meeting Type ===

Each meeting type (service) must have a unique name. If you do not assign a name to a meeting type and try to upload it, a prompt appears requesting that you name the service.

We recommend that you make meeting type names meaningful to users in the organization.

=== Using the Active Meeting Type Tab ===

The Meeting Types section opens by default on the Active Meeting Types tab.

The first time you log in to Video Administration, no meetings appear in the Active Meeting Types tab.

Cisco MCU version 4.x and 5.x and Cisco Unified Videoconferencing 35xx contain a range of preconfigured meeting types.

===== To Access Meeting Types =====

# In the sidebar menu, click '''Meeting Types'''.
#: The Meeting Types screen opens on the Active Meeting Types tab.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an Audio Plus Video Meeting Type|To Add an Audio Plus Video Meeting Type]] (Audio + Video)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an Audio Meeting Type|To Add an Audio Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Meeting Type|To Modify a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload and Download a Meeting Type|To Upload and Download a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Resolve Meeting Type Conflicts|To Resolve Meeting Type Conflicts]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deploy a Meeting Type|To Deploy a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload Meeting Types|To Upload Meeting Types]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Define an Audio-only Meeting Type|To Define an Audio-only Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deactivate a Meeting Type|To Deactivate a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Meeting Type|To Search for a Meeting Type]]

===== To Add an Audio Plus Video Meeting Type =====

('''Audio + Video''')



Use the following procedure to define and add a new audio + video meeting type to the Available Meeting Types list.

# On the Meeting Types tab, click '''Add'''.
#: The Meeting Type Details screen opens.
#: At the top of the screen, the Audio + Video option is selected by default.
# In the Service Prefix field, enter a numerical service prefix for the meeting type. This prefix is appended to the meeting ID. The number of digits in the meeting type prefix affects the number of digits needed to dial in to a meeting.
#: '''Note: ''' The service prefix for multipoint services must match the service prefix of the corresponding MCU service.
# In the Name field, enter a name for the meeting type.
# In the Description field, enter a meaningful description of the meeting type that includes significant details for reference.
# If the meeting type is for video conferencing, click the '''Change''' button next to the Max Video Layout field. In the Select Preferred Video Layout screen, select an on-screen layout for the meeting type, and then click '''OK'''.
#: The selection appears graphically beside the Max Video Layout field. The Max Video Layout default is Single Participant.
# If the meeting type is for video conferencing, click the '''Change''' button next to the Initial Video Layout field. In the Select Preferred Video Layout screen, select an on-screen layout for the start of a meeting, and then click '''OK'''.
#: The selection appears graphically beside the Initial Video Layout field. The Initial Video Layout default is Single Participant. The other option is the Max Video Layout selection.
# From the Bit Rate list, select the maximum available video bit rate in kilobytes.
#* Symmetric-If you want incoming and outgoing bit rates to be matched, check the '''Symmetric''' check box. Terminals receive images at the highest possible bit rate, regardless of the match rate.
#* Forced CP Symmetric-If you want to use the same bit rate for all terminals in the meeting, check the '''Forced CP Symmetric''' check box.
# If you want to view the bit rate used for rate-matching, check the '''Rate-Matching''' check box.
# To add T-120 data collaboration capabilities to the meeting type, check the '''Enable T-20''' check box. At least one MCU must be T-120 enabled to use this option.
# From the Frame Rate list, select a rate (in frames per second) from the available options (7, 10, 15, 30).
# From the Picture Format list, select a format.
# From the Video Format list, select a format.
# From the Audio XCoding Priority list, select the priority you require.
# Click '''OK'''.
#: The new meeting type appears in the list on the Active Meeting Type tab.

===== To Add an Audio Meeting Type =====

Use the following procedure to define and add a new audio meeting type to the Available Meeting Types list.

# On the Meeting Types tab, click '''Add'''.
#: The Meeting Type Details screen opens.
# At the top of the screen, select the '''Audio''' option.
#: Available options for an audio-only meeting appear.
# In the Service Prefix field, enter a service prefix for the meeting type. This prefix is appended to the meeting type ID. The number of digits in the meeting type prefix affects the number of digits needed to dial in to a meeting of this type.
# In the Name field, enter a name for the meeting type.
# In the Description field, enter a meaningful description of the meeting type that includes significant details for reference.

===== To Modify a Meeting Type =====

To modify meeting type (MCU service) settings, update the service parameters in the specified MCU. In the Video Administration web interface, download this meeting type from the specified MCU and then upload to all the other MCUs in the network, if there is more than one.

Do not modify meeting types that are currently in use for any meeting.

# If the meeting you want to modify is currently active, deactivate it. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deactivate a Meeting Type|To Deactivate a Meeting Type]].
# On the Active Meeting Types tab, click the name of the meeting type you want to modify.
# In the Meeting Type Details screen, edit the fields as required. Information on the Meeting Type Details screen represents all selections and factors associated with the meeting type.
# Click '''OK'''.
#: On the Active Meeting Types tab, the modified meeting type appears in the list.

===== To Upload and Download a Meeting Type =====

# On the Active Meeting Types tab, click '''Upload'''.
#: When you upload a meeting type, it appears in the MCU Selection screen, in the Available MCUs list.
# Click the arrow buttons to move MCUs from list to list as required.
# Click '''OK'''.
#: Video Administration checks for conflicts between a new meeting type and existing meeting types, meeting types not in use, and MCU prefixes. If there are no conflicts, Video Administration deletes the original meeting type from the MCU and includes the modified meeting type.
# If a conflict is found, select a definition for the meeting type in the Download Meeting Type (Services) screen.
# To rename a meeting type, enter a new name in the Name column.
# If you need further information about the MCU or its status, click '''Detail'''.
# Click '''Download''' to download the meeting types to all other MCUs.
#: During download, Video Administration checks all MCUs for existing meeting types, updates meeting type resource factors, and then includes new and modified meeting types in the Video Administration database.
#: '''Note: ''' See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Considerations When Uploading or Downloading a Meeting Type|Considerations When Uploading or Downloading a Meeting Type]] for additional information.
# If an MCU does not support a meeting type, on the Active Meeting Types tab, select another MCU service from the list in the MCUs column.
#: If Video Administration finds new meeting types on a network MCU and the download is processed with no conflicts and no failures, the Download Meeting Types (Services) screen lists the new meeting types.
#: If meeting types are located on a network MCU and there are no conflicts or failures associated with the download, the new meeting types appear in the Download Meeting Types (Services) screen.
# In the Use Meeting Type (Service) Definition from column, select the definition you want to use for each meeting type list.
#: If there are no definitions to choose from in the Download Meeting Types (Services) screen, the meeting type cannot be downloaded. In this case, you must first modify it on the MCU, and then download it.
# In the Name column, you can rename the meeting type. By default, the meeting type is given a number for a name.
# Click '''OK'''.
#: The Video Administration uploads the meeting type definitions to all MCUs on the MCUs Selection screen, in the Selected MCUs column.

===== Considerations When Uploading or Downloading a Meeting Type =====

Note the following:
* If you are using the LDAP server, modified meeting types are included in the LDAP database.
* If there is an error or conflict during a meeting type download, a detailed warning message appears.
* If Video Administration detects an invalid prefix during the upload, no action is taken by Video Administration.
* If a new meeting type prefix is detected by Video Administration, you can create a new meeting type via the Download log screen. Meeting type names cannot be created by the MCU itself.
* If the MCU is registered to a non-stripping Internal Gatekeeper, the MCU service prefix must begin with the Internal Gatekeeper prefix.

===== To Resolve Meeting Type Conflicts =====

The Meeting Types (Service) Conflicts screen displays meeting type prefix conflicts between individual MCUs and groups of MCUs, as well as conflicts between meeting types on MCUs and meeting types in Video Administration database.

The locations of meeting types with the same prefix are grouped together in a row of the Service Prefix column.

If Invalid Prefix is displayed, that indicates that the meeting type prefix on the MCU is a subset or contains a subset of another prefix already in the Video Administration system.

# Click the '''MCU''' tab.
# Click the meeting type name, and then in the Modify MCU screen, change the meeting type prefix of the MCU.
# Click '''OK'''.
# Repeat the download process from the Meeting Types screen. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload and Download a Meeting Type|To Upload and Download a Meeting Type]].

===== To Deploy a Meeting Type =====

When an administrator deploys a meeting type, consistency in meeting type definitions is maintained across the network.

We recommend that you create all meeting types on a Cisco MCU or a Cisco Unified Videoconferencing unit.

You can deploy more than one meeting type at the same time.

# In Meeting Types, on the Active Meeting Types tab, check the check box next to the meeting type that you want to deploy.
# Click '''Download'''.
#: If appropriate MCUs are registered and online, the meeting type is downloaded to Video Administration.
# On the Active Meeting Types tab, select the same meeting type from the list, and then click '''Upload'''.
#: The MCU Selection screen appears.
# By using the arrow buttons, select the MCUs for this meeting type from the Available MCUs list, and move them to the Selected MCUs list.
# Click '''OK'''.
#: If there are no conflicts, the meeting type is uploaded to and synchronized with all other MCUs.
#: If a meeting type is not supported by the MCU, any meeting type on that MCU with the same prefix as the unsupported meeting type is deleted.
#: '''Note: ''' For details about meeting type conflicts, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Resolve Meeting Type Conflicts|To Resolve Meeting Type Conflicts]].

===== To Add an MCU =====

# In the Resource Management screen, on the MCU tab, click '''Add'''.
# In the New MCU screen, complete the details and then click '''OK'''.
#: '''Note: ''' Do not interrupt the synchronization process.
# If this is the first MCU you are adding to the network, manually synchronize the meeting types of this MCU.
# To increase the number of T.120 ports per meeting type, in the Modify Meeting Type screen, increase the T.120 ports allocated to the MCU for this meeting type.
# Click '''OK''' to update the meeting types.

===== To Upload Meeting Types =====

# In Meeting Types, on the Active Meeting Types tab, select all meeting types that you want to update, then select '''Upload''' to display them in the MCU Selection screen.
# Verify that the meeting type in the upper left section of the screen is the meeting type that you want upload.
# In the Available MCUs section, we recommend that you select all available MCUs for uploading.
# To include MCUs in the Selected MCUs list, click the '''Right Arrow'''.
#: All of the meeting types to be uploaded appear in the list.
# Click '''OK'''.
#: The meeting types are uploaded to the available MCUs. When the upload is complete, the files are updated and the Upload Log displays any failed uploads or deletions.

===== To Define an Audio-only Meeting Type =====

You can create a meeting type for multipoint audio and for multipoint audio-video. This procedure defines an audio-only meeting type.

# In the Meeting Type Detail screen, select '''Audio Only'''.
#: '''Caution! ''' Meeting type prefixes must be unique. A meeting type prefix cannot conflict with other prefixes already present in Video Administration or on network MCUs. In addition, a meeting type prefix cannot contain another meeting type prefix. For example, if a meeting type prefix "123" is defined, there can be no meeting types "1" or "12." Similarly, if a meeting type "1" is created, there can be no meeting types "12" or "123." For more information, refer to your MCU documentation.
#: '''Caution! ''' MCU service prefixes must not begin with the same digits as the gatekeeper prefix for gatekeepers which are configured to remove prefixes.

===== To Deactivate a Meeting Type =====

If a specific meeting type is no longer available or desirable, it can be deactivated.

# Check the check box in front of the meeting type name.
# Click '''Deactivate'''.
#: Users will no longer have access to this meeting type when scheduling a meeting. To avoid affecting any in-session or upcoming meetings scheduled with this meeting type, the relevant meeting type will move to the Inactive Meeting Types tab.

===== To Search for a Meeting Type =====

# In the Name box, enter the name or part of the name of the meeting type for which you are searching.
# Click '''Search'''.
#: Meeting types that are found appear in list.

=== Using the Inactive Meeting Types Tab ===

In the Meeting Types section, click the Inactive Meeting Types tab to view a list of inactive meeting types. From this tab, you can view inactive meeting type details or delete obsolete meeting types.

The following information is displayed on the Inactive Meeting Types tab:
* Name-Name of the specified meeting type.
* Description-Description of the specified meeting group.
* Prefix-Meeting type prefix for multipoint services.
* In Use-Status of the meeting type. "Yes" appears if the meeting type is in use by an in-session meeting or for an upcoming meeting. "No" appears if this meeting type is not assigned to an in-session meeting or for an upcoming meeting.

===== To Delete a Inactive Meeting Type =====

If the In Use setting indicates that the specified meeting type is not being used by any upcoming or in-session meetings, you can delete the meeting type.

# On the Inactive Meeting Types tab, from the list, select one or more meeting types.
# Click '''Clear Obsolete''' to delete these meeting types from Video Administration and from the MCU(s).

Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace

2009-04-07T17:48:11Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration, Release 5.4 For Use With Release 6.x|Cisco Unified MeetingPlace Video Integration]]

Procedures in this chapter must be completed before installing the Cisco Unified MeetingPlace Video Integration software on the Web Conferencing server. This chapter can also be used as a reference for adding and changing settings later.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Getting Started|Getting Started]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Resource Management|Resource Management]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Meeting Types|Meeting Types]]

== Getting Started ==

This section includes information about starting and restarting Video Administration, and logging in according to your user type.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Video Administration Configuration Workflow|Video Administration Configuration Workflow]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Starting Video Administration|Starting Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Restarting Video Administration|Restarting Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Logging In|Logging In]]

=== Video Administration Configuration Workflow ===

We recommend that Video Administration administrators configure Video Administration according to the following workflow:
* Installation
* Initial Login
* Resource Configuration
** Gatekeepers/SIP servers
** MCUs
** Gateways
** Terminals
* Configure Meeting Types
** Download/Upload Meeting Types

By default, some sections of the user interface are hidden, according to settings in the Configuration Tool; however, these sections may appear in the documentation. For details about using the Configuration Tool, see the [[Cisco Unified MeetingPlace, Release 6.x -- Video Administration Configuration Tool#Video Administration Configuration Tool|Video Administration Configuration Tool]] chapter.

=== Starting Video Administration ===

Video Administration is installed as a Windows Service on your server. Video Administration automatically starts when the server is started.

=== Restarting Video Administration ===

To restart Video Administration, you must either restart the server or the Video Administration service.

===== To Restart the Video Administration Service =====

# From the Start menu, click '''Settings > Control Panel > Administrative Tools > Services'''.
# From the list of services currently running on the server, select the '''Video Administration for Cisco Unified MeetingPlace''' service.
#: '''Note: ''' When Video Administration is restarted, it may take a few minutes for Video Administration to properly initialize before web pages can be loaded.

=== Logging In ===

After installation is complete, you can log in according to your role.

===== To Log In to Video Administration =====

# Go the location provided in your user setup notification e-mail.
# In the login screen that appears, enter the required information, and then click '''Login'''.
# If you are logging in for the first time, the User Provisioning screen appears. One of the following options is automatically selected. Do not change the selection.
#* Via Video Administration for Cisco Unified MeetingPlace-To use the internal Video Administration database.
#* Via external server only.
# Click '''OK'''.

== Resource Management ==

Use the Resource Management section to organize, assign, and monitor resources.

The following resources are currently supported by Video Administration:
* MCU
** Cisco MCU version 4.x and 5.x
** Cisco Unified Videoconferencing 35xx
* Gatekeepers/SIP servers
** Cisco GK-the internal (ECS) gatekeeper installed with the Video Administration
** Cisco Multimedia Conference Manager (MCM)-also known as the IOS H.323 Gatekeeper.
** Microsoft LCS

===== To Access Resource Management =====

# In the sidebar menu, go to '''Resource Management'''.
# The Resource Management section contains the following tabs:
#* Gatekeeper/SIP server-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Gatekeeper/SIP Server Tab|Using the Gatekeeper/SIP Server Tab]].
#* MCU-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the MCU Tab|Using the MCU Tab]].
#* Gateway-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Gateway Tab|Using the Gateway Tab]].
#* Terminals-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Terminals Tab|Using the Terminals Tab]].
#: '''Note: ''' We recommend that you configure the tabs in the order that they appear, from left to right.

=== Using the Gatekeeper/SIP Server Tab ===

On the Gatekeeper/SIP server tab you can monitor, add, delete and modify gatekeeper and SIP server information.

A gatekeeper/SIP must be listed in the Gatekeeper/SIP server tab before you can add an MCU to its registry.

Cisco GK is listed on the Gatekeeper/SIP server tab. This is an internal gatekeeper.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Access the Gatekeeper/SIP Server Tab|To Access the Gatekeeper/SIP Server Tab]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Gatekeeper/SIP Server|To Add a Gatekeeper/SIP Server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Gatekeeper/SIP Server Definition|To Modify a Gatekeeper/SIP Server Definition]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Gatekeeper/SIP server|To Delete a Gatekeeper/SIP server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Gatekeeper/SIP Server|To Search for a Gatekeeper/SIP Server]]

===== To Access the Gatekeeper/SIP Server Tab =====

# In the sidebar menu, select '''Resource Management'''.
# In Resource Management, select the '''Gatekeeper/SIP Server''' tab.

===== To Add a Gatekeeper/SIP Server =====

The procedure for adding a gatekeeper/SIP server differs slightly depending on which model you select.

When you add a gatekeeper, it is automatically defined as the neighbor of the internal gatekeeper.

# On the Gatekeeper/SIP Server tab, click '''Add'''.
#: The New Gatekeeper/SIP server screen appears.
# In the Name field, enter the name of the Gatekeeper/SIP server.
# In the IP Address field, enter an IP address for the Gatekeeper/SIP server.
# From the Model list, select the type of server that you want to add. Select "Cisco MCM 500" for a Cisco IOS H.323 Gatekeeper.
#: The screen displays options relevant to the server you select. For example, the display of the Protocol list, the Dialing Plan Information, and the Advanced section is dependent on which server you select.
# From the Location list, set the Device Island to which the device belongs.
# Do not configure anything in the Dialing Plan Information section or the Advanced section.
# Click '''OK'''.

===== To Modify a Gatekeeper/SIP Server Definition =====

# On the Gatekeeper/SIP server tab, click the name of the server that you want to modify.
# In the Modify Gatekeeper/SIP server screen, edit the details as required.
# Click '''OK'''.

===== To Delete a Gatekeeper/SIP server =====

You cannot recover a Gatekeeper/SIP server once it is deleted.

# On the Gatekeeper/SIP server tab, click the name of the server that you want to delete.
# In the Modify Gatekeeper/SIP server screen, click '''Delete'''.
# If you want to delete the IP addresses for additional gateways in the Gateway pool, click the '''Modify '''button next to the IP Address field, and then in the Modify Gateway screen, click '''Delete'''.
#: Depending on the current use of the gatekeeper/SIP server, the following events may occur:
#* If there are any meetings scheduled within two hours of the time of deletion that will use this gatekeeper/SIP server, Video Administration does not allow the deletion.
#* If the gatekeeper/SIP server has other gateways mapped as children, Video Administration reconfigures the gateway dialing plan by using those children as root gatekeeper/SIP servers and dialing accordingly.
#* If there are devices registered to the deleted gatekeeper/SIP server, after deletion, they appear as not registered to any gatekeeper/SIP server.
#: '''Note: ''' Reconfigure manually, if necessary, after a gatekeeper/SIP server is deleted.

===== To Search for a Gatekeeper/SIP Server =====

You can search for a gatekeeper/SIP server by name.

# In the Name field, enter all or part of the name of the gatekeeper or SIP server that you want to find.
# Click '''Search'''.
#: If a Gatekeeper/SIP server is found, it appears in the list.
# To view the complete list of Gatekeeper/SIP servers, clear the '''Search''' field, and then click '''Search'''.
#: The following information about connection status is available in the list of search results:
#* Authorization Connection-indicates whether the Internal Gatekeeper/Video Administration authorization link is established. This connection is established only as needed; therefore, it can appear disconnected, which is not an error.
#* Call Control Connection-indicates whether the Internal Gatekeeper/API connection is established by Video Administration.
#* SNMP Connection-indicates whether the SNMP connection between Video Administration and the Internal Gatekeeper is established.

=== Using the MCU Tab ===

On the MCU tab you can monitor, add, delete and modify MCUs.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Select a Priority for Meeting Cascading|To Select a Priority for Meeting Cascading]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]] (For older versions)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]] (For newer version)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify an MCU|To Modify an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete an MCU|To Delete an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for an MCU|To Search for an MCU]]

===== To Select a Priority for Meeting Cascading =====

Cascading of MCUs is used to reduce potential drain on network resources and to increase the efficiency of MCU usage. The following points about cascading should be noted:
* The service representing the required meeting must be available on all participating MCUs.
* Video Administration meeting control features may not function correctly in manually cascaded meetings.
* We recommend that you not work with clustered MCUs (multiple MP units on a single MCU). Clustered MCU configurations have no control-overload balancing and may cause a single point of failure. Contact Cisco Customer Support for further information.
* Each master MCU uses one port for every slave MCU.
* Each slave MCU that is used in a cascaded meeting requires one additional port.
* Video Administration supports meeting cascading via the Prioritize field that appears in several locations in the Video Administration user interface. Cascading is conducted according to the priority you select.

To select a priority for meeting cascading, you must configure the Local MCU Prioritization Setting in MeetingTime. See Table [[Cisco Unified MeetingPlace, Release 6.x -- Configuring and Managing Cisco Unified MeetingPlace Video Integration#Table: Conference and Port Parameters|Table: Conference and Port Parameters]] for details.

===== To Add an MCU =====
''NOTE: This process is for the version of Video Administration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release (MR) 2, MR 1, or the FCS version.''

# In the MCU tab, click '''Add'''.
#: The New MCU screen opens on the Basic tab.
# From the Model list, select the model of the MCU.
# If you want to register the MCU to a gatekeeper, select from the '''Registered To''' list.
# If you want to register the MCU to an SIP server, check the '''SIP Only''' check box.
#: '''Note: ''' Verify that the MCU is registered to a SIP server and not registered to a H.323 gatekeeper. When you check the SIP Only check box, the Registered To field is inactive.
# From the Location list, select the Device Island to which the MCU belongs.
# If you want to designate a specific port via which Video Administration communicates with the MCU, or to designate SNMP Community passwords (passwords for retrieving and sending information), click the '''Advanced''' tab and edit the default entries in the fields.
#: '''Note: ''' The Advanced tab is active only for certain MCU models, and its fields vary according to the MCU model.
# On either the Basic or the Advanced tab, click '''OK'''.
#: The new MCU appears in the list on the MCU tab.
#: '''Note: ''' If Video Administration and an MCU are located on different networks, your security policy must allow SNMP and XML API connections between Video Administration and the MCU.
#: '''Note: ''' Video Administration cannot connect to a newly configured MCU. The MCU is added but its status is Offline. In this case, in the Modify MCU screen, select the '''Online''' option, and then click '''OK'''. For information about modifying an MCU, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify an MCU|To Modify an MCU]].

===== To Add an MCU =====
''NOTE: This process is for the version of Video Administration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release (MR) 3 or later.''

# Log in to Video Administration at by going to '''http://''<hostname>'':8080'''.
#: '''Note:''' The Video Administration installer defaults to 8080 but if you changed that value during the installation, you should use your custom port.
# Click '''Admin > Resource Management'''.
# Click the MCU tab.
# Click '''Add''' to open the New MCU page.
# Enter values in the required fields, which are indicated by red asterisks:
#* Name:
#* IP Address:
#* Login Name:
#* Login Password:
#* SNMP GET Community:
#* SNMP SET Community:
#* Port: (default is 3336)
#: '''Note:''' If you are unsure of SNMP values, log in to the MCU, click '''Board > Security''', and copy the values from the Security page.
# Select the model of the MCU from the Model list. Do not change the value of the "Registered To:" field. It defaults to “local_gatekeeper”. This is the ECS Gatekeeper on the Video Administration and the MCU must be registered to this value.
# If you want to register the MCU to an SIP server, check the '''SIP Only''' check box.
#: '''Note:''' Verify that the MCU is registered to a SIP server and not registered to a H.323 gatekeeper. When you check the '''SIP Only''' check box, the Registered To field is inactive.
# Click '''OK''' to save and exit the New MCU page.
#: The MCU appears in the list on the MCU tab.
#: '''Note:''' If Video Administration and the MCU are located on different networks, your security policy must allow SNMP and XML API connections between Video Administration and the MCU.

'''Note:''' The Signaling Port may or may not show a value, depending on the version of Video Administration that you are using. This field has no effect, and will automatically display the corresponding Signaling Port configured on the MCU once the MCU connects to the Video Administration.

'''Note:''' Video Administration cannot connect to a newly-configured MCU, when the MCU has been added but its status is offline. In this case, on the Modify MCU page, select the Online option, and then click '''OK'''.

===== To Modify an MCU =====

You can modify MCU information on the Basic tab and on the Advanced tab.

If the specified gatekeeper/SIP server is configured to remove prefixes, MCU service prefixes cannot begin with the same digits as the gatekeeper/SIP server prefix.

# On the MCU tab, click the name of an MCU in the list.
#: The Modify MCU screen appears.
# On the Basic tab, edit the details as required.
# In the Advanced section of the Basic tab, select from the following options:
#* Online-Default setting for all MCUs.
#* Offline Up to Date-To set the date when the MCU should be online again, click the calendar button and select a date. Video Administration does not automatically bring an MCU online; you must bring the MCU online manually on the specified date.
# If you want the MCU to be permanently set to the offline option, check the '''Permanently''' check box. This activates fields in the screen for editing that are otherwise read-only.
#: If you take an MCU offline, the following occurs:
#* Video Administration cannot schedule meetings for the offline MCU.
#* All currently in-progress meetings are terminated. Video Administration attempts to reschedule upcoming meetings for the offline MCU on other MCUs by using the same services and with sufficient, available resources. If no replacement MCUs are available, upcoming meetings are lost and not restored if the MCU status is changed to online.
#* Video Administration attempts to reschedule all meetings that are scheduled to this MCU from the time the MCU goes offline to the date specified in the Offline Up to Date field of the Modify MCU screen.
#* If the MCU is set to be Offline Permanently, Video Administration attempts to reschedule all future meetings.
#: The selection appears on the MCU tab, in the Status column.
# On the Advanced tab, edit the details as required.
# Click '''OK'''.
#: The changes appear in the MCU tab list.

===== To Delete an MCU =====

'''Caution! ''' If you delete an MCU, it cannot be recovered. Note that deleting an MCU, or taking an MCU offline, interrupts any meetings that are in progress and causes any future meetings that are scheduled for the MCU to be rescheduled. There is no guarantee of successful rescheduling.

# On the MCU tab, click the name of the MCU that you want to delete.
# In the MCU screen, select '''Offline''', and then check the '''Permanent''' check box.
# Click '''Delete'''.
# In the message that appears, click '''OK'''.
#: The MCU is deleted from the list in the MCU tab.

===== To Search for an MCU =====

You can search for an MCU by name.

# In the Name field, enter all or part of the name of an MCU.
# Click '''Search'''.
#: If the MCU is located, the MCU name and details appear in the list on the MCU tab.
#: Information in the Connection column indicates whether or not a communication connection is established between Video Administration and the MCU.

=== Using the Gateway Tab ===

Registered gateways are listed on the Gateway tab. You can monitor, add, delete, and modify gateways on the Gateway tab.

Video Administration does not control or communicate with gateways. Video Administration uses gateway setup information to determine resource allocation. It is important for gateway setup information to be accurate.

'''Note: ''' It is rare that you will need to make modifications on the Gateway Tab. When making modifications, ensure that the gateway is installed and set up prior to configuring it in the Video Administration. For details see the Administration Guide applicable to your gateway at: http://www.cisco.com/en/US/products/hw/video/ps1870/prod_maintenance_guides_list.html

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Gateway|To Add a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Gateway|To Modify a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Gateway|To Delete a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Gateway|To Search for a Gateway]]

===== To Add a Gateway =====

When you add a gateway, settings in Video Administration must be consistent with the actual gateway configuration. We recommend the following guidelines:
* If you make changes to the gateway, maintain IVR and DID numbers in Video Administration.
* To ensure that there are gateway ports available for scheduled and ad hoc calls, maintain capacity information.

# In the Resource Management section, click the '''Gateway''' tab.
# Click '''Add'''.
#: The New Gateway screen opens on the Basic tab.
# Enter information in the fields as required.
# From the Gateway Model list, if you select ViaIP-GW-S40, the IMUX field appears. Select an IMUX server for ISDN connection to the network.
# From the Registered To list, select the gatekeeper/SIP server to which the gateway is registered. A complete list of zone prefixes that are configured in Video Administration is displayed following the gatekeeper/SIP server name.
# To enable gateway pooling, modify the IP Address or add additional gateway IP addresses.
# If the gateway supports only dial-in calls, check the '''Dial-In''' check box.
# (Optional) In the Description field, enter a description for the gateway.
# In the International Access code field, enter the numeric prefix that is required to make an international long distance call.
# In the Domestic Long Distance Prefix field, enter the numeric prefix that is required to make a long distance call within the same country.
# In the Country Code field, enter the country code for the gateway phone numbers. Video Administration adds this prefix when dial-out is performed from this gateway to a terminal located in a country different from the gateway.
# If applicable, check the '''Allow Out of Area Calls''' check box.
#: If you do not check the Allow Out of Area Calls check box, only endpoints with the same area code as the gateway are allowed to reach Video Administration via the gateway. In addition, if the check box is unchecked, and you request reserved ports for a gateway, you must verify that the specified gateway has sufficient resources to provide the additional ports.
#: If you check the Allow Out of Area Calls check box, the gateway accepts incoming calls to Video Administration from endpoints with a different area code that is different from the gateway area code. By default, the check box is checked.
# In the Area Code field, enter the domestic area code of the gateway number.
# In the Telephone Number field, specify a local phone number that you assign to the specific port.
# Enter a number in the To Access an Outside Line for Local Calls, Dial field, for a gateway with no direct access to an outside line for local calls.
# Enter a number in the To Access an Outside Line for Long Distance Calls, Dial field, for a gateway with no direct access to an outside line for long distance calls.
# To add or modify an gateway service, click '''Add Service'''.
# To dele]te a gateway service, click '''Add Service''', and then click '''Delete Service'''.
# In the Bandwidth section, if you check the Restricted Mode check box, 56 appears in the Kbps list. Multiples of 56 Kbps are used instead of multiples of 64 Kbps.
# To add additional phone numbers to a gateway, click '''Add Services''', and then enter the required information.

===== To Modify a Gateway =====

Modification of the gateway is restricted to adding Service Prefixes and Bandwidth, unless you take the gateway offline.

# On the Gateway tab, click the name of a gateway in the list.
#: The Modify Gateway screen appears.
# If you want to change the gateway name, enter a new name in the Name field.
# To add a Service Prefix, click '''Add Service'''.
# If you want to edit other fields in the Modify Gateway screen, click '''Offline'''.
#: All fields become active.
# Click '''OK'''.

===== To Delete a Gateway =====

# On the Gateway tab, click the name of a gateway in the list.
#: The Modify Gateway screen appears.
# Click the '''Offline''' option.
# Check the '''Permanently''' check box.
# Click '''Delete'''.
#: The gateway is deleted.
#: All upcoming meetings that were scheduled to use the deleted gateway are rescheduled. For each meeting that is successfully rescheduled, the organizer and participants are notified of the new gateway information. If there are insufficient resources on the network to support a meeting, the meeting is cancelled and the organizer and participants are notified of the cancellation.

===== To Search for a Gateway =====

You can search for a gateway by name.

# In the Name field, enter all or part of the gateway name.
# Click '''Search'''.
#: If the gateway is located, the gateway name and details appear in the list on the Gateway tab.
#: The Connection column indicates whether Video Administration established a communication channel with the gateway.

=== Using the Terminals Tab ===

Registered terminals are listed on the Terminals tab. You can monitor, add, delete, and modify terminals on the Terminals tab.

Adding terminals to the Video Administration database is necessary in order to provide the ability to automatically outdial video participants at the start of a meeting. You can also add personal video endpoints such as Cisco Unified CallManager SCCP or SIP endpoints.

If the terminal information cannot be displayed on one screen, at the bottom of the screen, click the previous or next arrows or click a page number to move between Terminal screen pages.

The current number of terminals being used and the total number of available terminals appears at the bottom of the Terminals tab.

'''NOTE:''' By default, there is a predefined service that uses the prefix 6. If this conflicts with your current dial plan, you can change it using the Scheduling Settings tab in the Video Administration Configuration tool. See [[Cisco_Unified_MeetingPlace%2C_Release_6.x_--_Video_Administration_Configuration_Tool#Scheduling_Settings_Tab|Scheduling_Settings_Tab]] for information on the Video Administration Configuration tool.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Terminal|To Add a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Terminal|To Modify a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Terminal|To Delete a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Terminal|To Search for a Terminal]]

===== To Add a Terminal =====

# In the Terminals tab, click '''Add'''.
#: The Add Terminal screen appears.
#: '''Note: ''' Do not use the Default Users button. Users are configured on the Cisco Unified MeetingPlace Audio Server.
# In the Name field, enter the name of the terminal.
# From the Terminal Type list, select the applicable option:
#* IP(H.323)-choose this for SCCP endpoints
#* ISDN/PSTN(H.320)
#* Dual(H.320 and H.323)
#* IP(SIP)-If you select this option, in the SIP URL field, the terminal name is automatically displayed followed by the SIP server domain name and a suffix derived from the domain name of the SIP server. For example, <terminal name>@<SIP server domain name> or "user@domain_name.com."
#* Mobile-Supports 3G or non-3G terminals
# In the IP Phone number field, enter an E.164 IP phone number that is associated with the terminal. This field only appears when IP(H323) or IP(SIP) is selected in the Terminal Type field.
# From the Registered To list, select a gatekeeper/SIP server to which you want the terminal to be registered.
#: '''Note: ''' In a multi-zone dialing plan, if the terminal is registered to a gatekeeper/SIP server that is not configured to remove prefixes, you must append the zone prefix to the E.164 number.
# From the Location list, select the meeting room location of the terminal. If the terminal is not located in a meeting room within your organization, select '''None'''.
# From the Bandwidth list, select an applicable value in Kbps. Do not use the default value of "audio."
# From the Meeting Room list, select the meeting room in which the terminal is located.
# If you want to receive e-mail notifications regarding terminals, check the '''Notification E-Mail''' check box, and then click '''Browse''' to select a location for the e-mail notifications.
# If you want to change the Default Time Zone for the terminal, select a time zone from the list.
# Click '''OK'''.
#: The new terminal appears in the list on the Terminals tab.
#: '''Note: ''' When a new terminal is added to the Terminals tab, it is available to users in the Meeting Schedule section, on the Invite tab.

===== To Modify a Terminal =====

You can modify a terminal that appears in the list on the Terminals tab.

# On the Terminals tab, click the name of a terminal in the list.
# In the Modify Terminal screen that appears, complete the fields as required.
#: '''Note: ''' Tabs on the Modify Terminal screen are the same as on the Add Terminal screen. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Terminal|To Add a Terminal]].

===== To Delete a Terminal =====

You can delete a meeting room from the list on the Meeting Rooms tab.

# On the Terminals tab, click the name of a terminal in the list.
# In the Modify Terminals screen that appears, click '''Delete'''.
#: The terminal is deleted from the Meeting Rooms list.

===== To Search for a Terminal =====

You can search for a terminal by name or by dialing information.

# To search for a terminal, do one of the following:
#* In the Name field, enter all or part of a terminal name, and then click '''Search'''.
#* To search for a terminal by number, in the Dialing Info field, enter all or part of a terminal IP number or ISDN phone number, and then click '''Search'''.
#: '''Note: ''' The ISDN phone number of the terminal should be include without any dashes or spaces (available only when ISDN(H320) or Dual(H320 and H323) are selected in the Terminal Type field).
#: '''Note: ''' Both IP and ISDN numbers are displayed if the terminal is configured as a dual terminal.
#: Search results are displayed in the Terminal tab list.

== Meeting Types ==

'''Important!''' To enable proper Cisco Unified Videoconferencing MCU resource calculation, meeting types must be downloaded from the MCUs.

In Meeting Types, you can name and define the types of meetings (services) available to the organization. Meeting types include features and options for the user that are designated by the administrator. Deployment and modification of meeting types is applied across the network.

Available options for multipoint meeting types are based on the service features of the MCU. For detailed information about the services your MCU supports, see the relevant MCU manufacturer manuals.

The Meeting Types section includes the following tabs:
* Active Meeting Types-From the Active Meeting Types tab, you can add, deactivate, and upload meetings types. The Status column indicates if the meeting type is currently in use or designated for use in a scheduled meeting.
* Inactive Meeting Types-Meeting types not currently designated for use. Inactive meeting types are available for selection as active meeting types.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Meeting Type Name Display|Meeting Type Name Display]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Naming a Meeting Type|Naming a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Active Meeting Type Tab|Using the Active Meeting Type Tab]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Inactive Meeting Types Tab|Using the Inactive Meeting Types Tab]]

=== Meeting Type Name Display ===

The way a meeting type name is displayed provides useful information about that meeting type:
* Name followed by an asterisk (*)-MCU meeting type, not meeting types defined by Video Administration.
* Name in bold black characters, followed by asterisk (*)-MCU meeting type currently available to users, successfully downloaded from an MCU, or successfully uploaded to other MCUs.
* Name in bold red characters-An MCU meeting type downloaded from an MCU, modified in Video Administration but not uploaded to an MCU, and currently not available to any users.
* Name in bold red characters, followed by asterisk (*)-MCU meeting type downloaded from an MCU but no longer on network MCUs and not currently available to users.

=== Naming a Meeting Type ===

Each meeting type (service) must have a unique name. If you do not assign a name to a meeting type and try to upload it, a prompt appears requesting that you name the service.

We recommend that you make meeting type names meaningful to users in the organization.

=== Using the Active Meeting Type Tab ===

The Meeting Types section opens by default on the Active Meeting Types tab.

The first time you log in to Video Administration, no meetings appear in the Active Meeting Types tab.

Cisco MCU version 4.x and 5.x and Cisco Unified Videoconferencing 35xx contain a range of preconfigured meeting types.

===== To Access Meeting Types =====

# In the sidebar menu, click '''Meeting Types'''.
#: The Meeting Types screen opens on the Active Meeting Types tab.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an Audio Plus Video Meeting Type|To Add an Audio Plus Video Meeting Type]] (Audio + Video)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an Audio Meeting Type|To Add an Audio Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Meeting Type|To Modify a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload and Download a Meeting Type|To Upload and Download a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Resolve Meeting Type Conflicts|To Resolve Meeting Type Conflicts]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deploy a Meeting Type|To Deploy a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload Meeting Types|To Upload Meeting Types]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Define an Audio-only Meeting Type|To Define an Audio-only Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deactivate a Meeting Type|To Deactivate a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Meeting Type|To Search for a Meeting Type]]

===== To Add an Audio Plus Video Meeting Type =====

('''Audio + Video''')



Use the following procedure to define and add a new audio + video meeting type to the Available Meeting Types list.

# On the Meeting Types tab, click '''Add'''.
#: The Meeting Type Details screen opens.
#: At the top of the screen, the Audio + Video option is selected by default.
# In the Service Prefix field, enter a numerical service prefix for the meeting type. This prefix is appended to the meeting ID. The number of digits in the meeting type prefix affects the number of digits needed to dial in to a meeting.
#: '''Note: ''' The service prefix for multipoint services must match the service prefix of the corresponding MCU service.
# In the Name field, enter a name for the meeting type.
# In the Description field, enter a meaningful description of the meeting type that includes significant details for reference.
# If the meeting type is for video conferencing, click the '''Change''' button next to the Max Video Layout field. In the Select Preferred Video Layout screen, select an on-screen layout for the meeting type, and then click '''OK'''.
#: The selection appears graphically beside the Max Video Layout field. The Max Video Layout default is Single Participant.
# If the meeting type is for video conferencing, click the '''Change''' button next to the Initial Video Layout field. In the Select Preferred Video Layout screen, select an on-screen layout for the start of a meeting, and then click '''OK'''.
#: The selection appears graphically beside the Initial Video Layout field. The Initial Video Layout default is Single Participant. The other option is the Max Video Layout selection.
# From the Bit Rate list, select the maximum available video bit rate in kilobytes.
#* Symmetric-If you want incoming and outgoing bit rates to be matched, check the '''Symmetric''' check box. Terminals receive images at the highest possible bit rate, regardless of the match rate.
#* Forced CP Symmetric-If you want to use the same bit rate for all terminals in the meeting, check the '''Forced CP Symmetric''' check box.
# If you want to view the bit rate used for rate-matching, check the '''Rate-Matching''' check box.
# To add T-120 data collaboration capabilities to the meeting type, check the '''Enable T-20''' check box. At least one MCU must be T-120 enabled to use this option.
# From the Frame Rate list, select a rate (in frames per second) from the available options (7, 10, 15, 30).
# From the Picture Format list, select a format.
# From the Video Format list, select a format.
# From the Audio XCoding Priority list, select the priority you require.
# Click '''OK'''.
#: The new meeting type appears in the list on the Active Meeting Type tab.

===== To Add an Audio Meeting Type =====

Use the following procedure to define and add a new audio meeting type to the Available Meeting Types list.

# On the Meeting Types tab, click '''Add'''.
#: The Meeting Type Details screen opens.
# At the top of the screen, select the '''Audio''' option.
#: Available options for an audio-only meeting appear.
# In the Service Prefix field, enter a service prefix for the meeting type. This prefix is appended to the meeting type ID. The number of digits in the meeting type prefix affects the number of digits needed to dial in to a meeting of this type.
# In the Name field, enter a name for the meeting type.
# In the Description field, enter a meaningful description of the meeting type that includes significant details for reference.

===== To Modify a Meeting Type =====

To modify meeting type (MCU service) settings, update the service parameters in the specified MCU. In the Video Administration web interface, download this meeting type from the specified MCU and then upload to all the other MCUs in the network, if there is more than one.

Do not modify meeting types that are currently in use for any meeting.

# If the meeting you want to modify is currently active, deactivate it. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deactivate a Meeting Type|To Deactivate a Meeting Type]].
# On the Active Meeting Types tab, click the name of the meeting type you want to modify.
# In the Meeting Type Details screen, edit the fields as required. Information on the Meeting Type Details screen represents all selections and factors associated with the meeting type.
# Click '''OK'''.
#: On the Active Meeting Types tab, the modified meeting type appears in the list.

===== To Upload and Download a Meeting Type =====

# On the Active Meeting Types tab, click '''Upload'''.
#: When you upload a meeting type, it appears in the MCU Selection screen, in the Available MCUs list.
# Click the arrow buttons to move MCUs from list to list as required.
# Click '''OK'''.
#: Video Administration checks for conflicts between a new meeting type and existing meeting types, meeting types not in use, and MCU prefixes. If there are no conflicts, Video Administration deletes the original meeting type from the MCU and includes the modified meeting type.
# If a conflict is found, select a definition for the meeting type in the Download Meeting Type (Services) screen.
# To rename a meeting type, enter a new name in the Name column.
# If you need further information about the MCU or its status, click '''Detail'''.
# Click '''Download''' to download the meeting types to all other MCUs.
#: During download, Video Administration checks all MCUs for existing meeting types, updates meeting type resource factors, and then includes new and modified meeting types in the Video Administration database.
#: '''Note: ''' See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Considerations When Uploading or Downloading a Meeting Type|Considerations When Uploading or Downloading a Meeting Type]] for additional information.
# If an MCU does not support a meeting type, on the Active Meeting Types tab, select another MCU service from the list in the MCUs column.
#: If Video Administration finds new meeting types on a network MCU and the download is processed with no conflicts and no failures, the Download Meeting Types (Services) screen lists the new meeting types.
#: If meeting types are located on a network MCU and there are no conflicts or failures associated with the download, the new meeting types appear in the Download Meeting Types (Services) screen.
# In the Use Meeting Type (Service) Definition from column, select the definition you want to use for each meeting type list.
#: If there are no definitions to choose from in the Download Meeting Types (Services) screen, the meeting type cannot be downloaded. In this case, you must first modify it on the MCU, and then download it.
# In the Name column, you can rename the meeting type. By default, the meeting type is given a number for a name.
# Click '''OK'''.
#: The Video Administration uploads the meeting type definitions to all MCUs on the MCUs Selection screen, in the Selected MCUs column.

===== Considerations When Uploading or Downloading a Meeting Type =====

Note the following:
* If you are using the LDAP server, modified meeting types are included in the LDAP database.
* If there is an error or conflict during a meeting type download, a detailed warning message appears.
* If Video Administration detects an invalid prefix during the upload, no action is taken by Video Administration.
* If a new meeting type prefix is detected by Video Administration, you can create a new meeting type via the Download log screen. Meeting type names cannot be created by the MCU itself.
* If the MCU is registered to a non-stripping Internal Gatekeeper, the MCU service prefix must begin with the Internal Gatekeeper prefix.

===== To Resolve Meeting Type Conflicts =====

The Meeting Types (Service) Conflicts screen displays meeting type prefix conflicts between individual MCUs and groups of MCUs, as well as conflicts between meeting types on MCUs and meeting types in Video Administration database.

The locations of meeting types with the same prefix are grouped together in a row of the Service Prefix column.

If Invalid Prefix is displayed, that indicates that the meeting type prefix on the MCU is a subset or contains a subset of another prefix already in the Video Administration system.

# Click the '''MCU''' tab.
# Click the meeting type name, and then in the Modify MCU screen, change the meeting type prefix of the MCU.
# Click '''OK'''.
# Repeat the download process from the Meeting Types screen. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload and Download a Meeting Type|To Upload and Download a Meeting Type]].

===== To Deploy a Meeting Type =====

When an administrator deploys a meeting type, consistency in meeting type definitions is maintained across the network.

We recommend that you create all meeting types on a Cisco MCU or a Cisco Unified Videoconferencing unit.

You can deploy more than one meeting type at the same time.

# In Meeting Types, on the Active Meeting Types tab, check the check box next to the meeting type that you want to deploy.
# Click '''Download'''.
#: If appropriate MCUs are registered and online, the meeting type is downloaded to Video Administration.
# On the Active Meeting Types tab, select the same meeting type from the list, and then click '''Upload'''.
#: The MCU Selection screen appears.
# By using the arrow buttons, select the MCUs for this meeting type from the Available MCUs list, and move them to the Selected MCUs list.
# Click '''OK'''.
#: If there are no conflicts, the meeting type is uploaded to and synchronized with all other MCUs.
#: If a meeting type is not supported by the MCU, any meeting type on that MCU with the same prefix as the unsupported meeting type is deleted.
#: '''Note: ''' For details about meeting type conflicts, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Resolve Meeting Type Conflicts|To Resolve Meeting Type Conflicts]].

===== To Add an MCU =====

# In the Resource Management screen, on the MCU tab, click '''Add'''.
# In the New MCU screen, complete the details and then click '''OK'''.
#: '''Note: ''' Do not interrupt the synchronization process.
# If this is the first MCU you are adding to the network, manually synchronize the meeting types of this MCU.
# To increase the number of T.120 ports per meeting type, in the Modify Meeting Type screen, increase the T.120 ports allocated to the MCU for this meeting type.
# Click '''OK''' to update the meeting types.

===== To Upload Meeting Types =====

# In Meeting Types, on the Active Meeting Types tab, select all meeting types that you want to update, then select '''Upload''' to display them in the MCU Selection screen.
# Verify that the meeting type in the upper left section of the screen is the meeting type that you want upload.
# In the Available MCUs section, we recommend that you select all available MCUs for uploading.
# To include MCUs in the Selected MCUs list, click the '''Right Arrow'''.
#: All of the meeting types to be uploaded appear in the list.
# Click '''OK'''.
#: The meeting types are uploaded to the available MCUs. When the upload is complete, the files are updated and the Upload Log displays any failed uploads or deletions.

===== To Define an Audio-only Meeting Type =====

You can create a meeting type for multipoint audio and for multipoint audio-video. This procedure defines an audio-only meeting type.

# In the Meeting Type Detail screen, select '''Audio Only'''.
#: '''Caution! ''' Meeting type prefixes must be unique. A meeting type prefix cannot conflict with other prefixes already present in Video Administration or on network MCUs. In addition, a meeting type prefix cannot contain another meeting type prefix. For example, if a meeting type prefix "123" is defined, there can be no meeting types "1" or "12." Similarly, if a meeting type "1" is created, there can be no meeting types "12" or "123." For more information, refer to your MCU documentation.
#: '''Caution! ''' MCU service prefixes must not begin with the same digits as the gatekeeper prefix for gatekeepers which are configured to remove prefixes.

===== To Deactivate a Meeting Type =====

If a specific meeting type is no longer available or desirable, it can be deactivated.

# Check the check box in front of the meeting type name.
# Click '''Deactivate'''.
#: Users will no longer have access to this meeting type when scheduling a meeting. To avoid affecting any in-session or upcoming meetings scheduled with this meeting type, the relevant meeting type will move to the Inactive Meeting Types tab.

===== To Search for a Meeting Type =====

# In the Name box, enter the name or part of the name of the meeting type for which you are searching.
# Click '''Search'''.
#: Meeting types that are found appear in list.

=== Using the Inactive Meeting Types Tab ===

In the Meeting Types section, click the Inactive Meeting Types tab to view a list of inactive meeting types. From this tab, you can view inactive meeting type details or delete obsolete meeting types.

The following information is displayed on the Inactive Meeting Types tab:
* Name-Name of the specified meeting type.
* Description-Description of the specified meeting group.
* Prefix-Meeting type prefix for multipoint services.
* In Use-Status of the meeting type. "Yes" appears if the meeting type is in use by an in-session meeting or for an upcoming meeting. "No" appears if this meeting type is not assigned to an in-session meeting or for an upcoming meeting.

===== To Delete a Inactive Meeting Type =====

If the In Use setting indicates that the specified meeting type is not being used by any upcoming or in-session meetings, you can delete the meeting type.

# On the Inactive Meeting Types tab, from the list, select one or more meeting types.
# Click '''Clear Obsolete''' to delete these meeting types from Video Administration and from the MCU(s).

Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace

2009-04-07T17:42:26Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration, Release 5.4 For Use With Release 6.x|Cisco Unified MeetingPlace Video Integration]]

Procedures in this chapter must be completed before installing the Cisco Unified MeetingPlace Video Integration software on the Web Conferencing server. This chapter can also be used as a reference for adding and changing settings later.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Getting Started|Getting Started]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Resource Management|Resource Management]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Meeting Types|Meeting Types]]

== Getting Started ==

This section includes information about starting and restarting Video Administration, and logging in according to your user type.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Video Administration Configuration Workflow|Video Administration Configuration Workflow]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Starting Video Administration|Starting Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Restarting Video Administration|Restarting Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Logging In|Logging In]]

=== Video Administration Configuration Workflow ===

We recommend that Video Administration administrators configure Video Administration according to the following workflow:
* Installation
* Initial Login
* Resource Configuration
** Gatekeepers/SIP servers
** MCUs
** Gateways
** Terminals
* Configure Meeting Types
** Download/Upload Meeting Types

By default, some sections of the user interface are hidden, according to settings in the Configuration Tool; however, these sections may appear in the documentation. For details about using the Configuration Tool, see the [[Cisco Unified MeetingPlace, Release 6.x -- Video Administration Configuration Tool#Video Administration Configuration Tool|Video Administration Configuration Tool]] chapter.

=== Starting Video Administration ===

Video Administration is installed as a Windows Service on your server. Video Administration automatically starts when the server is started.

=== Restarting Video Administration ===

To restart Video Administration, you must either restart the server or the Video Administration service.

===== To Restart the Video Administration Service =====

# From the Start menu, click '''Settings > Control Panel > Administrative Tools > Services'''.
# From the list of services currently running on the server, select the '''Video Administration for Cisco Unified MeetingPlace''' service.
#: '''Note: ''' When Video Administration is restarted, it may take a few minutes for Video Administration to properly initialize before web pages can be loaded.

=== Logging In ===

After installation is complete, you can log in according to your role.

===== To Log In to Video Administration =====

# Go the location provided in your user setup notification e-mail.
# In the login screen that appears, enter the required information, and then click '''Login'''.
# If you are logging in for the first time, the User Provisioning screen appears. One of the following options is automatically selected. Do not change the selection.
#* Via Video Administration for Cisco Unified MeetingPlace-To use the internal Video Administration database.
#* Via external server only.
# Click '''OK'''.

== Resource Management ==

Use the Resource Management section to organize, assign, and monitor resources.

The following resources are currently supported by Video Administration:
* MCU
** Cisco MCU version 4.x and 5.x
** Cisco Unified Videoconferencing 35xx
* Gatekeepers/SIP servers
** Cisco GK-the internal (ECS) gatekeeper installed with the Video Administration
** Cisco Multimedia Conference Manager (MCM)-also known as the IOS H.323 Gatekeeper.
** Microsoft LCS

===== To Access Resource Management =====

# In the sidebar menu, go to '''Resource Management'''.
# The Resource Management section contains the following tabs:
#* Gatekeeper/SIP server-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Gatekeeper/SIP Server Tab|Using the Gatekeeper/SIP Server Tab]].
#* MCU-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the MCU Tab|Using the MCU Tab]].
#* Gateway-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Gateway Tab|Using the Gateway Tab]].
#* Terminals-See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Terminals Tab|Using the Terminals Tab]].
#: '''Note: ''' We recommend that you configure the tabs in the order that they appear, from left to right.

=== Using the Gatekeeper/SIP Server Tab ===

On the Gatekeeper/SIP server tab you can monitor, add, delete and modify gatekeeper and SIP server information.

A gatekeeper/SIP must be listed in the Gatekeeper/SIP server tab before you can add an MCU to its registry.

Cisco GK is listed on the Gatekeeper/SIP server tab. This is an internal gatekeeper.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Access the Gatekeeper/SIP Server Tab|To Access the Gatekeeper/SIP Server Tab]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Gatekeeper/SIP Server|To Add a Gatekeeper/SIP Server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Gatekeeper/SIP Server Definition|To Modify a Gatekeeper/SIP Server Definition]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Gatekeeper/SIP server|To Delete a Gatekeeper/SIP server]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Gatekeeper/SIP Server|To Search for a Gatekeeper/SIP Server]]

===== To Access the Gatekeeper/SIP Server Tab =====

# In the sidebar menu, select '''Resource Management'''.
# In Resource Management, select the '''Gatekeeper/SIP Server''' tab.

===== To Add a Gatekeeper/SIP Server =====

The procedure for adding a gatekeeper/SIP server differs slightly depending on which model you select.

When you add a gatekeeper, it is automatically defined as the neighbor of the internal gatekeeper.

# On the Gatekeeper/SIP Server tab, click '''Add'''.
#: The New Gatekeeper/SIP server screen appears.
# In the Name field, enter the name of the Gatekeeper/SIP server.
# In the IP Address field, enter an IP address for the Gatekeeper/SIP server.
# From the Model list, select the type of server that you want to add. Select "Cisco MCM 500" for a Cisco IOS H.323 Gatekeeper.
#: The screen displays options relevant to the server you select. For example, the display of the Protocol list, the Dialing Plan Information, and the Advanced section is dependent on which server you select.
# From the Location list, set the Device Island to which the device belongs.
# Do not configure anything in the Dialing Plan Information section or the Advanced section.
# Click '''OK'''.

===== To Modify a Gatekeeper/SIP Server Definition =====

# On the Gatekeeper/SIP server tab, click the name of the server that you want to modify.
# In the Modify Gatekeeper/SIP server screen, edit the details as required.
# Click '''OK'''.

===== To Delete a Gatekeeper/SIP server =====

You cannot recover a Gatekeeper/SIP server once it is deleted.

# On the Gatekeeper/SIP server tab, click the name of the server that you want to delete.
# In the Modify Gatekeeper/SIP server screen, click '''Delete'''.
# If you want to delete the IP addresses for additional gateways in the Gateway pool, click the '''Modify '''button next to the IP Address field, and then in the Modify Gateway screen, click '''Delete'''.
#: Depending on the current use of the gatekeeper/SIP server, the following events may occur:
#* If there are any meetings scheduled within two hours of the time of deletion that will use this gatekeeper/SIP server, Video Administration does not allow the deletion.
#* If the gatekeeper/SIP server has other gateways mapped as children, Video Administration reconfigures the gateway dialing plan by using those children as root gatekeeper/SIP servers and dialing accordingly.
#* If there are devices registered to the deleted gatekeeper/SIP server, after deletion, they appear as not registered to any gatekeeper/SIP server.
#: '''Note: ''' Reconfigure manually, if necessary, after a gatekeeper/SIP server is deleted.

===== To Search for a Gatekeeper/SIP Server =====

You can search for a gatekeeper/SIP server by name.

# In the Name field, enter all or part of the name of the gatekeeper or SIP server that you want to find.
# Click '''Search'''.
#: If a Gatekeeper/SIP server is found, it appears in the list.
# To view the complete list of Gatekeeper/SIP servers, clear the '''Search''' field, and then click '''Search'''.
#: The following information about connection status is available in the list of search results:
#* Authorization Connection-indicates whether the Internal Gatekeeper/Video Administration authorization link is established. This connection is established only as needed; therefore, it can appear disconnected, which is not an error.
#* Call Control Connection-indicates whether the Internal Gatekeeper/API connection is established by Video Administration.
#* SNMP Connection-indicates whether the SNMP connection between Video Administration and the Internal Gatekeeper is established.

=== Using the MCU Tab ===

On the MCU tab you can monitor, add, delete and modify MCUs.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Select a Priority for Meeting Cascading|To Select a Priority for Meeting Cascading]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify an MCU|To Modify an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete an MCU|To Delete an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for an MCU|To Search for an MCU]]

===== To Select a Priority for Meeting Cascading =====

Cascading of MCUs is used to reduce potential drain on network resources and to increase the efficiency of MCU usage. The following points about cascading should be noted:
* The service representing the required meeting must be available on all participating MCUs.
* Video Administration meeting control features may not function correctly in manually cascaded meetings.
* We recommend that you not work with clustered MCUs (multiple MP units on a single MCU). Clustered MCU configurations have no control-overload balancing and may cause a single point of failure. Contact Cisco Customer Support for further information.
* Each master MCU uses one port for every slave MCU.
* Each slave MCU that is used in a cascaded meeting requires one additional port.
* Video Administration supports meeting cascading via the Prioritize field that appears in several locations in the Video Administration user interface. Cascading is conducted according to the priority you select.

To select a priority for meeting cascading, you must configure the Local MCU Prioritization Setting in MeetingTime. See Table [[Cisco Unified MeetingPlace, Release 6.x -- Configuring and Managing Cisco Unified MeetingPlace Video Integration#Table: Conference and Port Parameters|Table: Conference and Port Parameters]] for details.

===== To Add an MCU =====
NOTE: This process is for the version of Video Administration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release (MR) 2, MR 1, or the FCS version.

# In the MCU tab, click '''Add'''.
#: The New MCU screen opens on the Basic tab.
# From the Model list, select the model of the MCU.
# If you want to register the MCU to a gatekeeper, select from the '''Registered To''' list.
# If you want to register the MCU to an SIP server, check the '''SIP Only''' check box.
#: '''Note: ''' Verify that the MCU is registered to a SIP server and not registered to a H.323 gatekeeper. When you check the SIP Only check box, the Registered To field is inactive.
# From the Location list, select the Device Island to which the MCU belongs.
# If you want to designate a specific port via which Video Administration communicates with the MCU, or to designate SNMP Community passwords (passwords for retrieving and sending information), click the '''Advanced''' tab and edit the default entries in the fields.
#: '''Note: ''' The Advanced tab is active only for certain MCU models, and its fields vary according to the MCU model.
# On either the Basic or the Advanced tab, click '''OK'''.
#: The new MCU appears in the list on the MCU tab.
#: '''Note: ''' If Video Administration and an MCU are located on different networks, your security policy must allow SNMP and XML API connections between Video Administration and the MCU.
#: '''Note: ''' Video Administration cannot connect to a newly configured MCU. The MCU is added but its status is Offline. In this case, in the Modify MCU screen, select the '''Online''' option, and then click '''OK'''. For information about modifying an MCU, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify an MCU|To Modify an MCU]].

===== To Add an MCU =====
NOTE: This process is for the version of Video Administration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release (MR) 3 or later.

# Log in to Video Administration at by going to '''http://''<hostname>'':8080'''.
#: '''Note:''' The Video Administration installer defaults to 8080 but if you changed that value during the installation, you should use your custom port.
# Click '''Admin > Resource Management'''.
# Click the MCU tab.
# Click '''Add''' to open the New MCU page.
# Enter values in the required fields, which are indicated by red asterisks:
#* Name:
#* IP Address:
#* Login Name:
#* Login Password:
#* SNMP GET Community:
#* SNMP SET Community:
#* Port: (default is 3336)
#: '''Note:''' If you are unsure of SNMP values, log in to the MCU, click '''Board > Security''', and copy the values from the Security page.

===== To Modify an MCU =====

You can modify MCU information on the Basic tab and on the Advanced tab.

If the specified gatekeeper/SIP server is configured to remove prefixes, MCU service prefixes cannot begin with the same digits as the gatekeeper/SIP server prefix.

# On the MCU tab, click the name of an MCU in the list.
#: The Modify MCU screen appears.
# On the Basic tab, edit the details as required.
# In the Advanced section of the Basic tab, select from the following options:
#* Online-Default setting for all MCUs.
#* Offline Up to Date-To set the date when the MCU should be online again, click the calendar button and select a date. Video Administration does not automatically bring an MCU online; you must bring the MCU online manually on the specified date.
# If you want the MCU to be permanently set to the offline option, check the '''Permanently''' check box. This activates fields in the screen for editing that are otherwise read-only.
#: If you take an MCU offline, the following occurs:
#* Video Administration cannot schedule meetings for the offline MCU.
#* All currently in-progress meetings are terminated. Video Administration attempts to reschedule upcoming meetings for the offline MCU on other MCUs by using the same services and with sufficient, available resources. If no replacement MCUs are available, upcoming meetings are lost and not restored if the MCU status is changed to online.
#* Video Administration attempts to reschedule all meetings that are scheduled to this MCU from the time the MCU goes offline to the date specified in the Offline Up to Date field of the Modify MCU screen.
#* If the MCU is set to be Offline Permanently, Video Administration attempts to reschedule all future meetings.
#: The selection appears on the MCU tab, in the Status column.
# On the Advanced tab, edit the details as required.
# Click '''OK'''.
#: The changes appear in the MCU tab list.

===== To Delete an MCU =====

'''Caution! ''' If you delete an MCU, it cannot be recovered. Note that deleting an MCU, or taking an MCU offline, interrupts any meetings that are in progress and causes any future meetings that are scheduled for the MCU to be rescheduled. There is no guarantee of successful rescheduling.

# On the MCU tab, click the name of the MCU that you want to delete.
# In the MCU screen, select '''Offline''', and then check the '''Permanent''' check box.
# Click '''Delete'''.
# In the message that appears, click '''OK'''.
#: The MCU is deleted from the list in the MCU tab.

===== To Search for an MCU =====

You can search for an MCU by name.

# In the Name field, enter all or part of the name of an MCU.
# Click '''Search'''.
#: If the MCU is located, the MCU name and details appear in the list on the MCU tab.
#: Information in the Connection column indicates whether or not a communication connection is established between Video Administration and the MCU.

=== Using the Gateway Tab ===

Registered gateways are listed on the Gateway tab. You can monitor, add, delete, and modify gateways on the Gateway tab.

Video Administration does not control or communicate with gateways. Video Administration uses gateway setup information to determine resource allocation. It is important for gateway setup information to be accurate.

'''Note: ''' It is rare that you will need to make modifications on the Gateway Tab. When making modifications, ensure that the gateway is installed and set up prior to configuring it in the Video Administration. For details see the Administration Guide applicable to your gateway at: http://www.cisco.com/en/US/products/hw/video/ps1870/prod_maintenance_guides_list.html

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Gateway|To Add a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Gateway|To Modify a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Gateway|To Delete a Gateway]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Gateway|To Search for a Gateway]]

===== To Add a Gateway =====

When you add a gateway, settings in Video Administration must be consistent with the actual gateway configuration. We recommend the following guidelines:
* If you make changes to the gateway, maintain IVR and DID numbers in Video Administration.
* To ensure that there are gateway ports available for scheduled and ad hoc calls, maintain capacity information.

# In the Resource Management section, click the '''Gateway''' tab.
# Click '''Add'''.
#: The New Gateway screen opens on the Basic tab.
# Enter information in the fields as required.
# From the Gateway Model list, if you select ViaIP-GW-S40, the IMUX field appears. Select an IMUX server for ISDN connection to the network.
# From the Registered To list, select the gatekeeper/SIP server to which the gateway is registered. A complete list of zone prefixes that are configured in Video Administration is displayed following the gatekeeper/SIP server name.
# To enable gateway pooling, modify the IP Address or add additional gateway IP addresses.
# If the gateway supports only dial-in calls, check the '''Dial-In''' check box.
# (Optional) In the Description field, enter a description for the gateway.
# In the International Access code field, enter the numeric prefix that is required to make an international long distance call.
# In the Domestic Long Distance Prefix field, enter the numeric prefix that is required to make a long distance call within the same country.
# In the Country Code field, enter the country code for the gateway phone numbers. Video Administration adds this prefix when dial-out is performed from this gateway to a terminal located in a country different from the gateway.
# If applicable, check the '''Allow Out of Area Calls''' check box.
#: If you do not check the Allow Out of Area Calls check box, only endpoints with the same area code as the gateway are allowed to reach Video Administration via the gateway. In addition, if the check box is unchecked, and you request reserved ports for a gateway, you must verify that the specified gateway has sufficient resources to provide the additional ports.
#: If you check the Allow Out of Area Calls check box, the gateway accepts incoming calls to Video Administration from endpoints with a different area code that is different from the gateway area code. By default, the check box is checked.
# In the Area Code field, enter the domestic area code of the gateway number.
# In the Telephone Number field, specify a local phone number that you assign to the specific port.
# Enter a number in the To Access an Outside Line for Local Calls, Dial field, for a gateway with no direct access to an outside line for local calls.
# Enter a number in the To Access an Outside Line for Long Distance Calls, Dial field, for a gateway with no direct access to an outside line for long distance calls.
# To add or modify an gateway service, click '''Add Service'''.
# To dele]te a gateway service, click '''Add Service''', and then click '''Delete Service'''.
# In the Bandwidth section, if you check the Restricted Mode check box, 56 appears in the Kbps list. Multiples of 56 Kbps are used instead of multiples of 64 Kbps.
# To add additional phone numbers to a gateway, click '''Add Services''', and then enter the required information.

===== To Modify a Gateway =====

Modification of the gateway is restricted to adding Service Prefixes and Bandwidth, unless you take the gateway offline.

# On the Gateway tab, click the name of a gateway in the list.
#: The Modify Gateway screen appears.
# If you want to change the gateway name, enter a new name in the Name field.
# To add a Service Prefix, click '''Add Service'''.
# If you want to edit other fields in the Modify Gateway screen, click '''Offline'''.
#: All fields become active.
# Click '''OK'''.

===== To Delete a Gateway =====

# On the Gateway tab, click the name of a gateway in the list.
#: The Modify Gateway screen appears.
# Click the '''Offline''' option.
# Check the '''Permanently''' check box.
# Click '''Delete'''.
#: The gateway is deleted.
#: All upcoming meetings that were scheduled to use the deleted gateway are rescheduled. For each meeting that is successfully rescheduled, the organizer and participants are notified of the new gateway information. If there are insufficient resources on the network to support a meeting, the meeting is cancelled and the organizer and participants are notified of the cancellation.

===== To Search for a Gateway =====

You can search for a gateway by name.

# In the Name field, enter all or part of the gateway name.
# Click '''Search'''.
#: If the gateway is located, the gateway name and details appear in the list on the Gateway tab.
#: The Connection column indicates whether Video Administration established a communication channel with the gateway.

=== Using the Terminals Tab ===

Registered terminals are listed on the Terminals tab. You can monitor, add, delete, and modify terminals on the Terminals tab.

Adding terminals to the Video Administration database is necessary in order to provide the ability to automatically outdial video participants at the start of a meeting. You can also add personal video endpoints such as Cisco Unified CallManager SCCP or SIP endpoints.

If the terminal information cannot be displayed on one screen, at the bottom of the screen, click the previous or next arrows or click a page number to move between Terminal screen pages.

The current number of terminals being used and the total number of available terminals appears at the bottom of the Terminals tab.

'''NOTE:''' By default, there is a predefined service that uses the prefix 6. If this conflicts with your current dial plan, you can change it using the Scheduling Settings tab in the Video Administration Configuration tool. See [[Cisco_Unified_MeetingPlace%2C_Release_6.x_--_Video_Administration_Configuration_Tool#Scheduling_Settings_Tab|Scheduling_Settings_Tab]] for information on the Video Administration Configuration tool.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Terminal|To Add a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Terminal|To Modify a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Delete a Terminal|To Delete a Terminal]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Terminal|To Search for a Terminal]]

===== To Add a Terminal =====

# In the Terminals tab, click '''Add'''.
#: The Add Terminal screen appears.
#: '''Note: ''' Do not use the Default Users button. Users are configured on the Cisco Unified MeetingPlace Audio Server.
# In the Name field, enter the name of the terminal.
# From the Terminal Type list, select the applicable option:
#* IP(H.323)-choose this for SCCP endpoints
#* ISDN/PSTN(H.320)
#* Dual(H.320 and H.323)
#* IP(SIP)-If you select this option, in the SIP URL field, the terminal name is automatically displayed followed by the SIP server domain name and a suffix derived from the domain name of the SIP server. For example, <terminal name>@<SIP server domain name> or "user@domain_name.com."
#* Mobile-Supports 3G or non-3G terminals
# In the IP Phone number field, enter an E.164 IP phone number that is associated with the terminal. This field only appears when IP(H323) or IP(SIP) is selected in the Terminal Type field.
# From the Registered To list, select a gatekeeper/SIP server to which you want the terminal to be registered.
#: '''Note: ''' In a multi-zone dialing plan, if the terminal is registered to a gatekeeper/SIP server that is not configured to remove prefixes, you must append the zone prefix to the E.164 number.
# From the Location list, select the meeting room location of the terminal. If the terminal is not located in a meeting room within your organization, select '''None'''.
# From the Bandwidth list, select an applicable value in Kbps. Do not use the default value of "audio."
# From the Meeting Room list, select the meeting room in which the terminal is located.
# If you want to receive e-mail notifications regarding terminals, check the '''Notification E-Mail''' check box, and then click '''Browse''' to select a location for the e-mail notifications.
# If you want to change the Default Time Zone for the terminal, select a time zone from the list.
# Click '''OK'''.
#: The new terminal appears in the list on the Terminals tab.
#: '''Note: ''' When a new terminal is added to the Terminals tab, it is available to users in the Meeting Schedule section, on the Invite tab.

===== To Modify a Terminal =====

You can modify a terminal that appears in the list on the Terminals tab.

# On the Terminals tab, click the name of a terminal in the list.
# In the Modify Terminal screen that appears, complete the fields as required.
#: '''Note: ''' Tabs on the Modify Terminal screen are the same as on the Add Terminal screen. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add a Terminal|To Add a Terminal]].

===== To Delete a Terminal =====

You can delete a meeting room from the list on the Meeting Rooms tab.

# On the Terminals tab, click the name of a terminal in the list.
# In the Modify Terminals screen that appears, click '''Delete'''.
#: The terminal is deleted from the Meeting Rooms list.

===== To Search for a Terminal =====

You can search for a terminal by name or by dialing information.

# To search for a terminal, do one of the following:
#* In the Name field, enter all or part of a terminal name, and then click '''Search'''.
#* To search for a terminal by number, in the Dialing Info field, enter all or part of a terminal IP number or ISDN phone number, and then click '''Search'''.
#: '''Note: ''' The ISDN phone number of the terminal should be include without any dashes or spaces (available only when ISDN(H320) or Dual(H320 and H323) are selected in the Terminal Type field).
#: '''Note: ''' Both IP and ISDN numbers are displayed if the terminal is configured as a dual terminal.
#: Search results are displayed in the Terminal tab list.

== Meeting Types ==

'''Important!''' To enable proper Cisco Unified Videoconferencing MCU resource calculation, meeting types must be downloaded from the MCUs.

In Meeting Types, you can name and define the types of meetings (services) available to the organization. Meeting types include features and options for the user that are designated by the administrator. Deployment and modification of meeting types is applied across the network.

Available options for multipoint meeting types are based on the service features of the MCU. For detailed information about the services your MCU supports, see the relevant MCU manufacturer manuals.

The Meeting Types section includes the following tabs:
* Active Meeting Types-From the Active Meeting Types tab, you can add, deactivate, and upload meetings types. The Status column indicates if the meeting type is currently in use or designated for use in a scheduled meeting.
* Inactive Meeting Types-Meeting types not currently designated for use. Inactive meeting types are available for selection as active meeting types.

See the following sections:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Meeting Type Name Display|Meeting Type Name Display]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Naming a Meeting Type|Naming a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Active Meeting Type Tab|Using the Active Meeting Type Tab]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Using the Inactive Meeting Types Tab|Using the Inactive Meeting Types Tab]]

=== Meeting Type Name Display ===

The way a meeting type name is displayed provides useful information about that meeting type:
* Name followed by an asterisk (*)-MCU meeting type, not meeting types defined by Video Administration.
* Name in bold black characters, followed by asterisk (*)-MCU meeting type currently available to users, successfully downloaded from an MCU, or successfully uploaded to other MCUs.
* Name in bold red characters-An MCU meeting type downloaded from an MCU, modified in Video Administration but not uploaded to an MCU, and currently not available to any users.
* Name in bold red characters, followed by asterisk (*)-MCU meeting type downloaded from an MCU but no longer on network MCUs and not currently available to users.

=== Naming a Meeting Type ===

Each meeting type (service) must have a unique name. If you do not assign a name to a meeting type and try to upload it, a prompt appears requesting that you name the service.

We recommend that you make meeting type names meaningful to users in the organization.

=== Using the Active Meeting Type Tab ===

The Meeting Types section opens by default on the Active Meeting Types tab.

The first time you log in to Video Administration, no meetings appear in the Active Meeting Types tab.

Cisco MCU version 4.x and 5.x and Cisco Unified Videoconferencing 35xx contain a range of preconfigured meeting types.

===== To Access Meeting Types =====

# In the sidebar menu, click '''Meeting Types'''.
#: The Meeting Types screen opens on the Active Meeting Types tab.

See the following procedures:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an Audio Plus Video Meeting Type|To Add an Audio Plus Video Meeting Type]] (Audio + Video)
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an Audio Meeting Type|To Add an Audio Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Modify a Meeting Type|To Modify a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload and Download a Meeting Type|To Upload and Download a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Resolve Meeting Type Conflicts|To Resolve Meeting Type Conflicts]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deploy a Meeting Type|To Deploy a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Add an MCU|To Add an MCU]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload Meeting Types|To Upload Meeting Types]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Define an Audio-only Meeting Type|To Define an Audio-only Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deactivate a Meeting Type|To Deactivate a Meeting Type]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Search for a Meeting Type|To Search for a Meeting Type]]

===== To Add an Audio Plus Video Meeting Type =====

('''Audio + Video''')



Use the following procedure to define and add a new audio + video meeting type to the Available Meeting Types list.

# On the Meeting Types tab, click '''Add'''.
#: The Meeting Type Details screen opens.
#: At the top of the screen, the Audio + Video option is selected by default.
# In the Service Prefix field, enter a numerical service prefix for the meeting type. This prefix is appended to the meeting ID. The number of digits in the meeting type prefix affects the number of digits needed to dial in to a meeting.
#: '''Note: ''' The service prefix for multipoint services must match the service prefix of the corresponding MCU service.
# In the Name field, enter a name for the meeting type.
# In the Description field, enter a meaningful description of the meeting type that includes significant details for reference.
# If the meeting type is for video conferencing, click the '''Change''' button next to the Max Video Layout field. In the Select Preferred Video Layout screen, select an on-screen layout for the meeting type, and then click '''OK'''.
#: The selection appears graphically beside the Max Video Layout field. The Max Video Layout default is Single Participant.
# If the meeting type is for video conferencing, click the '''Change''' button next to the Initial Video Layout field. In the Select Preferred Video Layout screen, select an on-screen layout for the start of a meeting, and then click '''OK'''.
#: The selection appears graphically beside the Initial Video Layout field. The Initial Video Layout default is Single Participant. The other option is the Max Video Layout selection.
# From the Bit Rate list, select the maximum available video bit rate in kilobytes.
#* Symmetric-If you want incoming and outgoing bit rates to be matched, check the '''Symmetric''' check box. Terminals receive images at the highest possible bit rate, regardless of the match rate.
#* Forced CP Symmetric-If you want to use the same bit rate for all terminals in the meeting, check the '''Forced CP Symmetric''' check box.
# If you want to view the bit rate used for rate-matching, check the '''Rate-Matching''' check box.
# To add T-120 data collaboration capabilities to the meeting type, check the '''Enable T-20''' check box. At least one MCU must be T-120 enabled to use this option.
# From the Frame Rate list, select a rate (in frames per second) from the available options (7, 10, 15, 30).
# From the Picture Format list, select a format.
# From the Video Format list, select a format.
# From the Audio XCoding Priority list, select the priority you require.
# Click '''OK'''.
#: The new meeting type appears in the list on the Active Meeting Type tab.

===== To Add an Audio Meeting Type =====

Use the following procedure to define and add a new audio meeting type to the Available Meeting Types list.

# On the Meeting Types tab, click '''Add'''.
#: The Meeting Type Details screen opens.
# At the top of the screen, select the '''Audio''' option.
#: Available options for an audio-only meeting appear.
# In the Service Prefix field, enter a service prefix for the meeting type. This prefix is appended to the meeting type ID. The number of digits in the meeting type prefix affects the number of digits needed to dial in to a meeting of this type.
# In the Name field, enter a name for the meeting type.
# In the Description field, enter a meaningful description of the meeting type that includes significant details for reference.

===== To Modify a Meeting Type =====

To modify meeting type (MCU service) settings, update the service parameters in the specified MCU. In the Video Administration web interface, download this meeting type from the specified MCU and then upload to all the other MCUs in the network, if there is more than one.

Do not modify meeting types that are currently in use for any meeting.

# If the meeting you want to modify is currently active, deactivate it. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Deactivate a Meeting Type|To Deactivate a Meeting Type]].
# On the Active Meeting Types tab, click the name of the meeting type you want to modify.
# In the Meeting Type Details screen, edit the fields as required. Information on the Meeting Type Details screen represents all selections and factors associated with the meeting type.
# Click '''OK'''.
#: On the Active Meeting Types tab, the modified meeting type appears in the list.

===== To Upload and Download a Meeting Type =====

# On the Active Meeting Types tab, click '''Upload'''.
#: When you upload a meeting type, it appears in the MCU Selection screen, in the Available MCUs list.
# Click the arrow buttons to move MCUs from list to list as required.
# Click '''OK'''.
#: Video Administration checks for conflicts between a new meeting type and existing meeting types, meeting types not in use, and MCU prefixes. If there are no conflicts, Video Administration deletes the original meeting type from the MCU and includes the modified meeting type.
# If a conflict is found, select a definition for the meeting type in the Download Meeting Type (Services) screen.
# To rename a meeting type, enter a new name in the Name column.
# If you need further information about the MCU or its status, click '''Detail'''.
# Click '''Download''' to download the meeting types to all other MCUs.
#: During download, Video Administration checks all MCUs for existing meeting types, updates meeting type resource factors, and then includes new and modified meeting types in the Video Administration database.
#: '''Note: ''' See the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#Considerations When Uploading or Downloading a Meeting Type|Considerations When Uploading or Downloading a Meeting Type]] for additional information.
# If an MCU does not support a meeting type, on the Active Meeting Types tab, select another MCU service from the list in the MCUs column.
#: If Video Administration finds new meeting types on a network MCU and the download is processed with no conflicts and no failures, the Download Meeting Types (Services) screen lists the new meeting types.
#: If meeting types are located on a network MCU and there are no conflicts or failures associated with the download, the new meeting types appear in the Download Meeting Types (Services) screen.
# In the Use Meeting Type (Service) Definition from column, select the definition you want to use for each meeting type list.
#: If there are no definitions to choose from in the Download Meeting Types (Services) screen, the meeting type cannot be downloaded. In this case, you must first modify it on the MCU, and then download it.
# In the Name column, you can rename the meeting type. By default, the meeting type is given a number for a name.
# Click '''OK'''.
#: The Video Administration uploads the meeting type definitions to all MCUs on the MCUs Selection screen, in the Selected MCUs column.

===== Considerations When Uploading or Downloading a Meeting Type =====

Note the following:
* If you are using the LDAP server, modified meeting types are included in the LDAP database.
* If there is an error or conflict during a meeting type download, a detailed warning message appears.
* If Video Administration detects an invalid prefix during the upload, no action is taken by Video Administration.
* If a new meeting type prefix is detected by Video Administration, you can create a new meeting type via the Download log screen. Meeting type names cannot be created by the MCU itself.
* If the MCU is registered to a non-stripping Internal Gatekeeper, the MCU service prefix must begin with the Internal Gatekeeper prefix.

===== To Resolve Meeting Type Conflicts =====

The Meeting Types (Service) Conflicts screen displays meeting type prefix conflicts between individual MCUs and groups of MCUs, as well as conflicts between meeting types on MCUs and meeting types in Video Administration database.

The locations of meeting types with the same prefix are grouped together in a row of the Service Prefix column.

If Invalid Prefix is displayed, that indicates that the meeting type prefix on the MCU is a subset or contains a subset of another prefix already in the Video Administration system.

# Click the '''MCU''' tab.
# Click the meeting type name, and then in the Modify MCU screen, change the meeting type prefix of the MCU.
# Click '''OK'''.
# Repeat the download process from the Meeting Types screen. For details, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Upload and Download a Meeting Type|To Upload and Download a Meeting Type]].

===== To Deploy a Meeting Type =====

When an administrator deploys a meeting type, consistency in meeting type definitions is maintained across the network.

We recommend that you create all meeting types on a Cisco MCU or a Cisco Unified Videoconferencing unit.

You can deploy more than one meeting type at the same time.

# In Meeting Types, on the Active Meeting Types tab, check the check box next to the meeting type that you want to deploy.
# Click '''Download'''.
#: If appropriate MCUs are registered and online, the meeting type is downloaded to Video Administration.
# On the Active Meeting Types tab, select the same meeting type from the list, and then click '''Upload'''.
#: The MCU Selection screen appears.
# By using the arrow buttons, select the MCUs for this meeting type from the Available MCUs list, and move them to the Selected MCUs list.
# Click '''OK'''.
#: If there are no conflicts, the meeting type is uploaded to and synchronized with all other MCUs.
#: If a meeting type is not supported by the MCU, any meeting type on that MCU with the same prefix as the unsupported meeting type is deleted.
#: '''Note: ''' For details about meeting type conflicts, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Video Administration for Cisco Unified MeetingPlace#To Resolve Meeting Type Conflicts|To Resolve Meeting Type Conflicts]].

===== To Add an MCU =====

# In the Resource Management screen, on the MCU tab, click '''Add'''.
# In the New MCU screen, complete the details and then click '''OK'''.
#: '''Note: ''' Do not interrupt the synchronization process.
# If this is the first MCU you are adding to the network, manually synchronize the meeting types of this MCU.
# To increase the number of T.120 ports per meeting type, in the Modify Meeting Type screen, increase the T.120 ports allocated to the MCU for this meeting type.
# Click '''OK''' to update the meeting types.

===== To Upload Meeting Types =====

# In Meeting Types, on the Active Meeting Types tab, select all meeting types that you want to update, then select '''Upload''' to display them in the MCU Selection screen.
# Verify that the meeting type in the upper left section of the screen is the meeting type that you want upload.
# In the Available MCUs section, we recommend that you select all available MCUs for uploading.
# To include MCUs in the Selected MCUs list, click the '''Right Arrow'''.
#: All of the meeting types to be uploaded appear in the list.
# Click '''OK'''.
#: The meeting types are uploaded to the available MCUs. When the upload is complete, the files are updated and the Upload Log displays any failed uploads or deletions.

===== To Define an Audio-only Meeting Type =====

You can create a meeting type for multipoint audio and for multipoint audio-video. This procedure defines an audio-only meeting type.

# In the Meeting Type Detail screen, select '''Audio Only'''.
#: '''Caution! ''' Meeting type prefixes must be unique. A meeting type prefix cannot conflict with other prefixes already present in Video Administration or on network MCUs. In addition, a meeting type prefix cannot contain another meeting type prefix. For example, if a meeting type prefix "123" is defined, there can be no meeting types "1" or "12." Similarly, if a meeting type "1" is created, there can be no meeting types "12" or "123." For more information, refer to your MCU documentation.
#: '''Caution! ''' MCU service prefixes must not begin with the same digits as the gatekeeper prefix for gatekeepers which are configured to remove prefixes.

===== To Deactivate a Meeting Type =====

If a specific meeting type is no longer available or desirable, it can be deactivated.

# Check the check box in front of the meeting type name.
# Click '''Deactivate'''.
#: Users will no longer have access to this meeting type when scheduling a meeting. To avoid affecting any in-session or upcoming meetings scheduled with this meeting type, the relevant meeting type will move to the Inactive Meeting Types tab.

===== To Search for a Meeting Type =====

# In the Name box, enter the name or part of the name of the meeting type for which you are searching.
# Click '''Search'''.
#: Meeting types that are found appear in list.

=== Using the Inactive Meeting Types Tab ===

In the Meeting Types section, click the Inactive Meeting Types tab to view a list of inactive meeting types. From this tab, you can view inactive meeting type details or delete obsolete meeting types.

The following information is displayed on the Inactive Meeting Types tab:
* Name-Name of the specified meeting type.
* Description-Description of the specified meeting group.
* Prefix-Meeting type prefix for multipoint services.
* In Use-Status of the meeting type. "Yes" appears if the meeting type is in use by an in-session meeting or for an upcoming meeting. "No" appears if this meeting type is not assigned to an in-session meeting or for an upcoming meeting.

===== To Delete a Inactive Meeting Type =====

If the In Use setting indicates that the specified meeting type is not being used by any upcoming or in-session meetings, you can delete the meeting type.

# On the Inactive Meeting Types tab, from the list, select one or more meeting types.
# Click '''Clear Obsolete''' to delete these meeting types from Video Administration and from the MCU(s).

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:24:34Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the '''net''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:23:45Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the '''net''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:23:22Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

: The final message, which indicates if the process was successful, is:

Database Replication changes for this machine (Host = <hostname>; IP Addr = <ip addr>) is SUCCESSFUL

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the '''net''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:06:27Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the '''net''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:03:44Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#'''net|net]]''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, then perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, then perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, then you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:03:01Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.
*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#'''net|net]]''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, then perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, then perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, then you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:02:41Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

* If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

* During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

*: An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#'''net|net]]''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, then perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, then perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, then you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2009-04-07T17:02:11Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

== Setting Up Failover for Two Newly Installed Application Servers ==

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

===== Procedure =====

# Install the first Application Server (Node 1).
#: During installation, you configure the hostname and IP address of eth0, which is called "Ethernet Port 1(device eth0)" on the Network Setup page.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Install the second Application Server (Node 2), ensuring the following:
#* Node 1 and Node 2 use the exact same IP address and hostname for eth0.
#* Time is synchronized between Node 1 and Node 2.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 12|Step 12]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

During this process, you may see several error messages. These error messages are expected behavioor and informational only. The final message of the command explicitly says if the command ran successfully or not.

An example of an error message that you can ignore is:

* Error:
'/opt/cisco/meetingplace/database/versions/IIF.10.00.UC5XL/etc/sqlhosts not initialized. xxxxxx is missing'
* Forcing the fix

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Setting Up Failover for One Existing Application Server and One Newly Installed Application Server ==

In this task:

* Node 1 is the existing Application Server.

* Node 2 is the new Application Server.

===== Before You Begin =====

* Complete [[Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Application Server Failover|Prerequisites for Application Server Failover]].

* Read the [[Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Application Server Failover|Restrictions for Application Server Failover]].

* Back up and archive the data on the existing Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]].

'''Caution! ''' Performing this task temporarily brings down your Cisco Unified MeetingPlace system. Proceed only during a scheduled maintenance period.

===== Procedure =====

# Install the second Application Server (Node 2), ensuring the following:
#* To reduce system downtime during this procedure, enter the Node 2 eth0:0 (or any valid and currently unused) IP address and hostname when you configure "Ethernet Port 1(device eth0)" on the Network Setup page.
#*: This configuration is temporary; you will change the eth0 IP address and hostname to the correct value later in this procedure.
#* Node 1 and Node 2 server times must be synchronized with each other.
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0 IP address or hostname.
# Enter the following command to set up Node 1 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 1 automatically restarts and enters ''standby'' mode.
# Log in to the CLI of Node 2.
#: If you are logging in remotely, use the temporary Node 2 eth0 IP address or hostname that you entered during installation in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 1|Step 1]].
# Enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#'''net|net]]''' command to change the Node 2 eth0 IP address and hostname to match the Node 1 eth0 IP address and hostname.
#: Because Node 1 is still in standby mode, Node 2 is now the active server.
# Enter '''mpx_sys restart''' to restart Node 2.
# Log in to the CLI of Node 2, this time using the shared eth0 IP address or hostname.
# Enter the following command to set up Node 2 for failover:
#: '''failoverUtil setDeployment failover'''
# Follow the CLI prompts to configure the virtual network interface (eth0:0) with an IP address, subnet mask, default gateway, and hostname.
#: Node 2 automatically restarts and enters ''standby'' mode.
# Enter the following command to initialize database replication:
#: '''mp_replication init -s 1 -n 2 -l''' ''node2-eth0:0-hostname'' '''-r''' ''node1-eth0:0-hostname'' '''-h'''
# Log in to the CLI of Node 1.
#: If you are logging in remotely, use the Node 1 eth0:0 IP address or hostname.
# Enter the following commands to initialize and start database replication and synchronize existing data:
#: '''mp_replication init -s 1 -n 1 -l''' ''node1-eth0:0-hostname'' '''-r''' ''node2-eth0:0-hostname'' '''-h'''
#: '''mp_replication switchON -r''' ''node2-eth0:0-hostname'' '''-S -F''' ''node1-eth0:0-hostname''
# Enter the following command to change Node 1 from standby mode to active mode:
#: '''failoverUtil setServer active'''

===== Verifying =====

Using the hostname or IP address of the virtual eth0:0 interface, log in to the Administration Center of each node, and verify that the correct failover deployment mode (active or standby) appears at the top of the page.

===== Troubleshooting Tips =====

If the Administration Center in ''both'' nodes displays "Failover deployment. Standby server," something may have interrupted the process initiated in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Step 14|Step 14]]. To resolve this issue, see the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil setServer|failoverUtil setServer]] command description.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

===== What To Do Next =====

Proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Configuring the Application Servers in a Failover Deployment|Configuring the Application Servers in a Failover Deployment]].

== Configuring the Application Servers in a Failover Deployment ==

Whenever you need to configure the Application Server in a failover deployment, use this procedure to make sure that both the active and standby servers have the same configuration.

===== Before You Begin =====

* Complete one of the following tasks:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for Two Newly Installed Application Servers|Setting Up Failover for Two Newly Installed Application Servers]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover#Setting Up Failover for One Existing Application Server and One Newly Installed Application Server|Setting Up Failover for One Existing Application Server and One Newly Installed Application Server]]

* Determine the hostname or IP address of both of the following virtual network interfaces:
** eth0:0 of the active server
** eth0:0 of the standby server

===== Procedure =====

# Go to '''http://''<application-server>''/admin/'''.
#: Use the shared eth0 hostname or IP address, which always goes to the ''active'' Application Server.
# Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
# Configure the active server.
#: Take note of any changes you make on pages or fields that are labeled as:
#:* Copied
#:* Server-specific
#:* Partially replicated
# If you made changes to any ''copied'' pages or parameters, then perform the following steps:
## Log in to the CLI of the ''active'' server.
##: If you are logging in remotely, use the eth0 IP address or hostname.
## Enter the following command to compress and transfer the files from the active server to the standby server:
##: '''failoverUtil copyConfigFiles'''
## Log in to the CLI of the ''standby'' server.
##: If you are logging in remotely, use eth0:0 IP address or hostname.
## Enter the following command to decompress the transferred files and put them in the correct directories on the standby server:
##: '''failoverUtil restoreConfigFiles'''
# If you made changes to any ''server-specific'' pages or parameters, then perform the following steps.
#: '''Tip: ''' If your workstation screen is large enough to accommodate two full web browser windows without overlapping, then you can simultaneously view the Administration Center for both the active and standby servers. This may help you configure the server-specific parameters to match between the active and standby servers.
## Go to '''http://'''''standby-eth0:0'''''/admin/'''.
##: Use either the hostname or IP address of the virtual eth0:0 interface of the ''standby'' Application Server.
## Log in as a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]].
## Verify that "Failover deployment. Standby server." appears at the top of the page.
## Configure the server-specific parameters on the standby server.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Logging In to the Cisco Unified MeetingPlace Administration Center|Logging In to the Cisco Unified MeetingPlace Administration Center]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace|Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Perform Application Server Failover|How to Perform Application Server Failover]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installing Cisco Unified MeetingPlace, Release 7.0]]

[[Category: Configuring Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements

2009-04-06T16:35:25Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]

== TCP/UDP Ports for Cisco Unified MeetingPlace ==

[[Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements#Table: Incoming Ports Used by Cisco Unified MeetingPlace|Table: Incoming Ports Used by Cisco Unified MeetingPlace]] lists the incoming ports, and [[Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements#Table: Outgoing Ports Used by Cisco Unified MeetingPlace|Table: Outgoing Ports Used by Cisco Unified MeetingPlace]] lists the outgoing ports, used by Cisco Unified MeetingPlace. Use these lists to make sure that your firewalls do not block access to Cisco Unified MeetingPlace from users or integrated systems, and to make sure that you do not block communication among the Cisco Unified MeetingPlace components and servers.

'''Note: ''' The ports that you do ''not'' need to expose to system administrators or end users are used for local communication between the Cisco Unified MeetingPlace elements or between Cisco Unified MeetingPlace and local services such as Cisco Unified Communications Manager or Microsoft Exchange. Such ports should be blocked in the DMZ or external firewall, but should not be blocked between internal components of the Cisco Unified MeetingPlace solution.

===== Table: Incoming Ports Used by Cisco Unified MeetingPlace =====

{| border = 1
|-
!Protocol
!Port Type
!Ports
!Port Usage
!Special Requirements
|-
|<td colspan="5" rowspan="1">|''' Application Server'''
|-
|

SSH
|

TCP
|

22
|

Secure access
|

Expose to system administrators.
|-
|

HTTP, HTTPS
|

TCP
|

80, 443
|

Administrator web access
|

Expose to system administrators.
|-
|

NTP
|

UDP
|

123
|

Network Time Protocol communication from the Web Servers and Media Servers
|

Expose to Web Server in the DMZ.
|-
|

SNMP
|

UDP
|

161
|

SNMP configuration
|

Expose to system administrators.
|-
|

MP_REPL
|

TCP
|

2008
|

Database replication between the active and standby servers for Application Server failover
|

-
|-
|

GWSIM
|

TCP
|

5003
|

Attachments between the external Web Server and the Application Server
|

Expose to Web Server in the DMZ.

You can set up port 5003 to traverse the firewall either inbound or outbound.

'''NOTE:''' Port 5003 must be closed inbound (that is, communication from the DMZ Web Server to the Application Server must be closed) to allow the Application Server to consistently use a reverse connection successfully.

|-
|

SIP
|

TCP UDP
|

5060
|

SIP B2BUA
|

-
|-
|

HTTP
|

TCP
|

8080
|

HTTP services
|

-
|-
|

HTTP
|

TCP
|

9090
|

Media Server Administration
|

Expose to system administrators.
|-
|

SIP
|

TCP UDP
|

61002
|

Recording signaling
|

-
|-
|

Recording control
|

TCP
|

61003
|

Recording control
|

-
|-
|

HTTP
|

TCP
|

61004
|

Communication from the external Web Server to the Application Server for prompts, recordings, attachment access, and login service for remote users
|

Expose to Web Server in the DMZ.
|-
|

RTP, RTCP
|

UDP
|

16384-32767
|

Recording media
|

-
|-
|<td colspan="5" rowspan="1">|''' Media Server'''
|-
|

FTP
|

TCP
|

21
|

Retrieving log files
|

Expose to system administrators.
|-
|

Telnet
|

TCP
|

23
|

Telnet
|

Expose to system administrators.
|-
|

HTTP
|

TCP
|

80
|

Web user interface
|

Expose to system administrators.
|-
|

NTP
|

UDP
|

123
|

Network Time Protocol
|

-
|-
|

SNMP
|

UDP
|

161
|

SNMP configuration
|

Expose to system administrators.
|-
|

MPI
|

TCP
|

2010
|

MPI (Pompa control protocol)
|

-
|-
|

DCI
|

TCP
|

3333
|

DCI (DCS control protocol)
|

-
|-
|

XML control
|

TCP
|

3336
|

XML control
|

-
|-
|

XML cascading
|

TCP
|

3337
|

XML cascading
|

-
|-
|

File server
|

TCP
|

3340
|

File server
|

-
|-
|

SIP
|

TCP UDP
|

5060
|

SIP
|

-
|-
|

RTP/RTCP
|

UDP
|

16384-16683
|

Audio Blades
|

Expose to system administrators and end users.
|-
|

RTP/RTCP
|

UDP
|

20000-21799
|

Video Blades
|

Expose to system administrators and end users.
|-
|

Video Blade control
|

TCP
|

2944-2945
|

Video Blade control (H.248)
|

-
|-
|<td colspan="5" rowspan="1">|''' Web Server'''
|-
|

HTTP
|

TCP
|

80
|

User web access

Cisco Unified MeetingPlace for Microsoft Outlook client
|

Expose to system administrators and end users.

For external users to participate in web meetings, access must be granted from the Internet to the Web Server in the DMZ. However, access to port 80 may be closed if the Web Server is configured for HTTPS and you open TCP port 443.
|-
|

HTTPS
|

TCP
|

443
|

Secure user web access

Cisco Unified MeetingPlace for Microsoft Outlook client
|

(Optional) Expose to system administrators and end users. If you have external users, then grant access from the Internet to the Web Server in the DMZ.
|-
|

RTMP
|

TCP
|

1627
|

Web meeting room
|

(Optional but recommended for best performance) Expose to system administrators and end users. If you have external users, then grant access from the Internet to the Web Server in the DMZ.
|-
|

DCOM
|

TCP
|

Dynamically open 1024 to 65535
|

Cisco Unified MeetingPlace for Microsoft Outlook to Microsoft Exchange uses the CDO API
|

Required only for Release 7.0.1 systems using the ''back-end'' Microsoft Outlook integration.
|-
|

SQL
|

TCP
|

1433
|

Communication between the Web Server and the SQL Server database
|

-
|-
|

Control connection
|

TCP
|

5003
|

Control connection between Web Servers and the Application Server
|

Expose to Application Server.
|-
|<td colspan="5" rowspan="1">|''' Microsoft Office Communicator'''
|-
|

SIP/TLS
|

TCP
|

5060-5069
|

Live Communication Server (LCS) gateway service
|

-
|-
|<td colspan="5" rowspan="1">|'''IBM Lotus Sametime'''
|-
|

TCP/UDP
|

TCP UDP
|

8083
|

Java RMI1 lookup service for IBM Lotus Sametime
|

-
|-
|

TCP
|

TCP
|

8086
|

RMI calls (JRMP2) for IBM Lotus Sametime web conferencing
|

-
|}

'''Footnote 1:''' RMI = Remote Method Invocation

'''Footnote 2:''' JRMP = Java Remote Method Protocol

'''Note: ''' [[Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements#Table: Outgoing Ports Used by Cisco Unified MeetingPlace|Table: Outgoing Ports Used by Cisco Unified MeetingPlace]] contains only a partial list of outgoing ports.

===== Table: Outgoing Ports Used by Cisco Unified MeetingPlace =====

{| border = 1
|-
!Service
!Port Type
!Port
!Purpose
!Source
!Destination
|-
|<td colspan="6" rowspan="1">|'''Microsoft Exchange'''
|-
|

HTTP
|

TCP
|

80
|

Microsoft Exchange integration
|

Application Server
|

Microsoft Exchange server
|-
|

HTTPS
|

TCP
|

443
|

Microsoft Exchange integration when SSL is enabled
|

Application Server
|

Microsoft Exchange server
|-
|

SMTP
|

TCP
|

25
|

E-mail notification
|

Application Server
|

SMTP server or Microsoft Exchange server
|}

== Application Server to Media Server Connectivity ==

The Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Media Server blades that are remotely located.

== Application Server to Web Server Connectivity ==

Confirm that the system meets the following requirements so that the Web Server can communicate with the Application Server:
* The Web Server must be able to communicate with the Application Server on TCP port 5003. This can be achieved by opening port 5003 inbound from the Web Server to the Application Server, in which case the normal registration mechanism will operate. Alternately, the Application Server can initiate a reverse (outbound) connection to the Web Server. For the reverse connection to be initiated, you must enter the MeetingPlace Server name as a host name instead of an IP address during the Cisco Unified MeetingPlace Web Conferencing installation. You will also have to manually configure this Web Server unit on the Application Server.
* Connectivity between the Web Server and the Application Server is of high quality and not subject to interruptions because of traffic congestion. Any time the round-trip latency exceeds 100 ms or there is more than 1 percent packet loss, you should expect a noticeable reduction in service quality.
* TCP port 61004 must be open inbound from the Web Server to the Application Server. There is no "reverse" connection mechanism for this port.
* Cisco recommends opening UDP port 123 (NTP) bidirectionally between the Web Server and the Application Server. This is used for time synchronization. Alternate time synchronization mechanisms may be used, but any significant clock drift will result in failures.

== Failover Requirements ==

To configure failover, you need two Application Servers with a high-speed network connection (preferably 100Mpbs or better) between them.

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements

2009-04-03T23:07:36Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Previous page:''' [[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]

== TCP/UDP Ports for Cisco Unified MeetingPlace ==

[[Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements#Table: Incoming Ports Used by Cisco Unified MeetingPlace|Table: Incoming Ports Used by Cisco Unified MeetingPlace]] lists the incoming ports, and [[Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements#Table: Outgoing Ports Used by Cisco Unified MeetingPlace|Table: Outgoing Ports Used by Cisco Unified MeetingPlace]] lists the outgoing ports, used by Cisco Unified MeetingPlace. Use these lists to make sure that your firewalls do not block access to Cisco Unified MeetingPlace from users or integrated systems, and to make sure that you do not block communication among the Cisco Unified MeetingPlace components and servers.

'''Note: ''' The ports that you do ''not'' need to expose to system administrators or end users are used for local communication between the Cisco Unified MeetingPlace elements or between Cisco Unified MeetingPlace and local services such as Cisco Unified Communications Manager or Microsoft Exchange. Such ports should be blocked in the DMZ or external firewall, but should not be blocked between internal components of the Cisco Unified MeetingPlace solution.

===== Table: Incoming Ports Used by Cisco Unified MeetingPlace =====

{| border = 1
|-
!Protocol
!Port Type
!Ports
!Port Usage
!Special Requirements
|-
|<td colspan="5" rowspan="1">|''' Application Server'''
|-
|

SSH
|

TCP
|

22
|

Secure access
|

Expose to system administrators.
|-
|

HTTP, HTTPS
|

TCP
|

80, 443
|

Administrator web access
|

Expose to system administrators.
|-
|

NTP
|

UDP
|

123
|

Network Time Protocol communication from the Web Servers and Media Servers
|

Expose to Web Server in the DMZ.
|-
|

SNMP
|

UDP
|

161
|

SNMP configuration
|

Expose to system administrators.
|-
|

MP_REPL
|

TCP
|

2008
|

Database replication between the active and standby servers for Application Server failover
|

-
|-
|

GWSIM
|

TCP
|

5003
|

Attachments between the external Web Server and the Application Server
|

Expose to Web Server in the DMZ.

You can set up port 5003 to traverse the firewall either inbound or outbound.

'''NOTE:''' Port 5003 must be closed inbound (that is, communication from the DMZ Web Server to the Application Server must be closed) to allow the Application Server to do a reverse connection.

|-
|

SIP
|

TCP UDP
|

5060
|

SIP B2BUA
|

-
|-
|

HTTP
|

TCP
|

8080
|

HTTP services
|

-
|-
|

HTTP
|

TCP
|

9090
|

Media Server Administration
|

Expose to system administrators.
|-
|

SIP
|

TCP UDP
|

61002
|

Recording signaling
|

-
|-
|

Recording control
|

TCP
|

61003
|

Recording control
|

-
|-
|

HTTP
|

TCP
|

61004
|

Communication from the external Web Server to the Application Server for prompts, recordings, attachment access, and login service for remote users
|

Expose to Web Server in the DMZ.
|-
|

RTP, RTCP
|

UDP
|

16384-32767
|

Recording media
|

-
|-
|<td colspan="5" rowspan="1">|''' Media Server'''
|-
|

FTP
|

TCP
|

21
|

Retrieving log files
|

Expose to system administrators.
|-
|

Telnet
|

TCP
|

23
|

Telnet
|

Expose to system administrators.
|-
|

HTTP
|

TCP
|

80
|

Web user interface
|

Expose to system administrators.
|-
|

NTP
|

UDP
|

123
|

Network Time Protocol
|

-
|-
|

SNMP
|

UDP
|

161
|

SNMP configuration
|

Expose to system administrators.
|-
|

MPI
|

TCP
|

2010
|

MPI (Pompa control protocol)
|

-
|-
|

DCI
|

TCP
|

3333
|

DCI (DCS control protocol)
|

-
|-
|

XML control
|

TCP
|

3336
|

XML control
|

-
|-
|

XML cascading
|

TCP
|

3337
|

XML cascading
|

-
|-
|

File server
|

TCP
|

3340
|

File server
|

-
|-
|

SIP
|

TCP UDP
|

5060
|

SIP
|

-
|-
|

RTP/RTCP
|

UDP
|

16384-16683
|

Audio Blades
|

Expose to system administrators and end users.
|-
|

RTP/RTCP
|

UDP
|

20000-21799
|

Video Blades
|

Expose to system administrators and end users.
|-
|

Video Blade control
|

TCP
|

2944-2945
|

Video Blade control (H.248)
|

-
|-
|<td colspan="5" rowspan="1">|''' Web Server'''
|-
|

HTTP
|

TCP
|

80
|

User web access

Cisco Unified MeetingPlace for Microsoft Outlook client
|

Expose to system administrators and end users.

For external users to participate in web meetings, access must be granted from the Internet to the Web Server in the DMZ. However, access to port 80 may be closed if the Web Server is configured for HTTPS and you open TCP port 443.
|-
|

HTTPS
|

TCP
|

443
|

Secure user web access

Cisco Unified MeetingPlace for Microsoft Outlook client
|

(Optional) Expose to system administrators and end users. If you have external users, then grant access from the Internet to the Web Server in the DMZ.
|-
|

RTMP
|

TCP
|

1627
|

Web meeting room
|

(Optional but recommended for best performance) Expose to system administrators and end users. If you have external users, then grant access from the Internet to the Web Server in the DMZ.
|-
|

DCOM
|

TCP
|

Dynamically open 1024 to 65535
|

Cisco Unified MeetingPlace for Microsoft Outlook to Microsoft Exchange uses the CDO API
|

Required only for Release 7.0.1 systems using the ''back-end'' Microsoft Outlook integration.
|-
|

SQL
|

TCP
|

1433
|

Communication between the Web Server and the SQL Server database
|

-
|-
|

Control connection
|

TCP
|

5003
|

Control connection between Web Servers and the Application Server
|

Expose to Application Server.
|-
|<td colspan="5" rowspan="1">|''' Microsoft Office Communicator'''
|-
|

SIP/TLS
|

TCP
|

5060-5069
|

Live Communication Server (LCS) gateway service
|

-
|-
|<td colspan="5" rowspan="1">|'''IBM Lotus Sametime'''
|-
|

TCP/UDP
|

TCP UDP
|

8083
|

Java RMI1 lookup service for IBM Lotus Sametime
|

-
|-
|

TCP
|

TCP
|

8086
|

RMI calls (JRMP2) for IBM Lotus Sametime web conferencing
|

-
|}

'''Footnote 1:''' RMI = Remote Method Invocation

'''Footnote 2:''' JRMP = Java Remote Method Protocol

'''Note: ''' [[Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements#Table: Outgoing Ports Used by Cisco Unified MeetingPlace|Table: Outgoing Ports Used by Cisco Unified MeetingPlace]] contains only a partial list of outgoing ports.

===== Table: Outgoing Ports Used by Cisco Unified MeetingPlace =====

{| border = 1
|-
!Service
!Port Type
!Port
!Purpose
!Source
!Destination
|-
|<td colspan="6" rowspan="1">|'''Microsoft Exchange'''
|-
|

HTTP
|

TCP
|

80
|

Microsoft Exchange integration
|

Application Server
|

Microsoft Exchange server
|-
|

HTTPS
|

TCP
|

443
|

Microsoft Exchange integration when SSL is enabled
|

Application Server
|

Microsoft Exchange server
|-
|

SMTP
|

TCP
|

25
|

E-mail notification
|

Application Server
|

SMTP server or Microsoft Exchange server
|}

== Application Server to Media Server Connectivity ==

The Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Media Server blades that are remotely located.

== Application Server to Web Server Connectivity ==

Confirm that the system meets the following requirements so that the Web Server can communicate with the Application Server:
* The Web Server must be able to communicate with the Application Server on TCP port 5003. This can be achieved by opening port 5003 inbound from the Web Server to the Application Server, in which case the normal registration mechanism will operate. Alternately, the Application Server can initiate a reverse (outbound) connection to the Web Server. For the reverse connection to be initiated, you must enter the MeetingPlace Server name as a host name instead of an IP address during the Cisco Unified MeetingPlace Web Conferencing installation. You will also have to manually configure this Web Server unit on the Application Server.
* Connectivity between the Web Server and the Application Server is of high quality and not subject to interruptions because of traffic congestion. Any time the round-trip latency exceeds 100 ms or there is more than 1 percent packet loss, you should expect a noticeable reduction in service quality.
* TCP port 61004 must be open inbound from the Web Server to the Application Server. There is no "reverse" connection mechanism for this port.
* Cisco recommends opening UDP port 123 (NTP) bidirectionally between the Web Server and the Application Server. This is used for time synchronization. Alternate time synchronization mechanisms may be used, but any significant clock drift will result in failures.

== Failover Requirements ==

To configure failover, you need two Application Servers with a high-speed network connection (preferably 100Mpbs or better) between them.

[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database

2009-04-03T19:03:28Z

MeetingPlace Express Moderator:

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

Complete the following procedures in the order shown to detach and attach the MPWEB SQL database:

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Detaching the Database|Detaching the Database]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Examples: Detaching the Database|Examples: Detaching the Database]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Attaching the Database|Attaching the Database]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Examples: Attaching the Database|Examples: Attaching the Database]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Relocating the Database|Relocating the Database]]

== Detaching the Database ==

You must detach the MPWEB database with the sp_detach_db command from a SQL Server release that is earlier or equal to the release of the SQL Server to which you want to import the database.

===== Procedure =====

# Sign in to the end-user web interface.
# Click '''Admin'''.
# Stop the Cisco Unified MeetingPlace Web Conferencing service.
# Wait for the Cisco Unified MeetingPlace Web Conferencing services, IIS Admin service, and World Wide Web Publishing service to stop.
# Access the SQL Server.
#* If the SQL Server hosting the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt:
## Select '''Start < Run'''.
## Enter '''cmd'''.
#: or
#* If the SQL Server hosting the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and log on.
#: '''Note: ''' If you cannot log on to the separate (remote) Windows server, log on to any Windows based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can remotely connect to the SQL Server.
# Connect to SQL Server by using osql with the sa account and the appropriate password.
#* If the SQL Server runs locally, you can omit the '''-S ''<servername>''''' option.
#* If you are not allowed to connect to this SQL Server as sa, connect by using an account that has enough privileges to backup a database.
# Access the MPWEB database.
## Enter '''use mpweb'''.
## Enter '''go'''.
# Display a list of the database files.
## Enter '''sp_helpfile'''.
## Enter '''go'''.
# Access the SQL Server master database.
## Enter '''use master'''.
## Enter '''go'''.
# Detach the MPWEB database.
## Enter '''sp_detach_db 'MPWEB'''.
## Enter '''go'''.
# Decide what you should do with the physical files that you identified in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 8|Step 8]].
#: These files constitute your detached database. For example, you can archive these files or use them to attach the associated MPWEB database to another SQL Server.
# Determine the slave database name(s) on your SQL Server.
## Enter '''select name from sysdatabases where name like 'MPWEB%'''.
## Enter '''go'''.
# (Optional) For each additional database named MPWEB_XX, repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 7|Step 7]] through [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 11|Step 11]] to detach that database, replacing the database name MPWEB with MPWEB_XX.
#: '''Note: ''' The databases are logically linked; therefore, if you want to archive the detached MPWEB database, you must do the same for each MPWEB_XX database. If you want to reattach the MPWEB database to another SQL Server, you must also reattach the MPWEB_XX database(s).
# Enter '''exit''' to exit osql.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Examples: Detaching the Database|Examples: Detaching the Database]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Use the Cisco Unified MeetingPlace Web Conferencing Service#Stopping All Web Conferencing Services|Stopping All Web Conferencing Services]]

== Examples: Detaching the Database ==

In the following examples, the output is displayed for each osql command that is used in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Detaching the Database|Detaching the Database]].

===== Sample Output for Connecting to SQL Server =====

<tt> C:> osql -U sa -S SERVERNAME </tt>

<tt> Password: password </tt>

<tt> 1> </tt>

===== Sample Output for Accessing the MPWEB Database =====

<tt> 1> use mpweb </tt>

<tt> 2> go </tt>

===== Sample Output for Displaying a List of Database Files =====

In this example, the database MPWEB relies on two physical files: C:\MSSQL2K\Data\MPWEB.mdf and C:\MSSQL2K\Data\MPWEB.ldf.

<tt> 1> sp_helpfile </tt>

<tt> 2> go </tt>

<tt> name fileid filename filegroup size maxsize growth usage </tt>

<tt> ------------- ---------- --------------------------- --------- ------- --------- ------- </tt>

<tt> --------- </tt>

<tt> MPWEBData 1 C:\MSSQL2K\Data\MPWEB.mdf PRIMARY </tt>

<tt> 2432 KB Unlimited 1024 KB data only </tt>

<tt> MPWEBLog 2 C:\MSSQL2K\Data\MPWEB.ldf NULL </tt>

<tt> 1280 KB Unlimited 10% log only </tt>

===== Sample Output for Accessing the SQL Server Master Database =====

<tt> 1> use master </tt>

<tt> 2> go </tt>

===== Sample Output for Detaching the MPWEB Database =====

<tt> 1> sp_detach_db 'MPWEB' </tt>

<tt> 2> go </tt>

===== Sample Output for Determining the Slave Database Name =====

In this example, the name of the slave database is MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.

<tt> 1> select name from sysdatabases where name like 'MPWEB%' </tt>

<tt> 2> go </tt>

<tt> --------------------------------------------------- </tt>

<tt> name </tt>

<tt> [char ] </tt>

<tt> -------------------------------------------- </tt>

<tt> MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1 </tt>

===== Sample Output for Exiting osql =====

<tt> 1> exit </tt>

<tt> C:> </tt>

== Attaching the Database ==

Ensure that you have a valid detached MPWEB database, usually two files named MPWEB.mdf (data file) and MPWEB.ldf (log file) though file names may vary.

===== Procedure =====

# Access the SQL Server.
#* If the SQL Server to which you want to attach your MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.
## Select '''Start > Run'''.
## Enter '''cmd'''.
#: or
#* If the SQL Server runs on a separate (remote) Windows server, locate that Windows server and log on.
#: '''Note: ''' If you cannot log on to that Windows server, log on to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can remotely connect to the SQL Server.
# Connect to SQL Server by using osql.
#* Enter''' osql -U sa -S ''<server_name>''''', where ''<server_name>'' is the Windows SQL Server to which you want to attach the MPWEB database.
#* If the SQL Server runs locally, you can omit the '''-S ''<server-name>''''' option.
# Enter your password for the appropriate SA account.
#: '''Note: ''' If you are not allowed to connect to this SQL Server as SA, connect by using an account that has enough privileges to attach a database.
# Determine if a database named MPWEB already exists on this server.
## Enter '''select name from sysdatabases where name = 'MPWEB''''.
## Enter '''go'''.
# If no MPWEB database exists, proceed to [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 6|Step 6]].
#: or
#: If a MPWEB database exists, ensure that it is not being used by an existing Cisco Unified MeetingPlace Web Server.
#: '''Note: ''' You cannot attach a MPWEB database to this SQL Server if an active MPWEB database exists already. Before you proceed, you must detach the existing MPWEB database by completing [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Detaching the Database|Detaching the Database]].
# To verify the installation folder of the SQL Server to which you want to restore this database, check the physical location of the SQL Server master database.
## Enter '''sp_helpfile master'''.
## Enter '''go'''.
#: '''Note: ''' Unless you have a reason to restore your MPWEB database to another disk location, such as for performance and tuning or data recovery reasons, we recommend that you restore the database to the default data folder of this SQL Server installation.
# Copy the MPWEB.mdf and MPWEB.ldf files under the data folder that you identified in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 6|Step 6]].
# Attach the MPWEB database.
## Enter '''sp_attach_db 'MPWEB',''''''data path'''''\MPWEB.mdf',''''''data path'''''\MPWEB.ldf''''.
## Enter '''go'''.
# (Optional) If you have a valid set of files for the MPWEB_XX slave database(s), repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 4|Step 4]] through [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Step 9|Step 9]] for each slave database, replacing MPWEB with MPWEB_XX to attach that database.
# Enter '''exit''' to exit osql.

== Examples: Attaching the Database ==

In the following examples, the output is displayed for each osql command that is used in the [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Attaching the Database|Attaching the Database]].

The following examples use the files MPWEB.mdf and MPWEB.ldf:

===== Sample Output for Connecting to SQL Server =====

<tt> C:> osql -U sa -S SERVERNAME </tt>

<tt> Password: password </tt>

<tt> 1> </tt>

===== Sample Output for Checking if the MPWEB Database Exists =====

<tt> 1> select name from sysdatabases where name = 'MPWEB' </tt>

<tt> 2> go </tt>

<tt> name </tt>

<tt> ----------------------------------------------------- </tt>

<tt> (0 row affected) </tt>

<tt> 1> </tt>

===== Sample Output for Checking the Physical Location of the SQL Server Master Database =====

In this example, SQL Server Version 2000 is installed in C:\MSSQL2K, and the default data folder is C:\MSSQL2K\data.

<tt> 1> sp_helpfile master </tt>

<tt> 2> go </tt>

<tt> name filename filegroup size maxsize growth usage </tt>

<tt> ---------------------------------------------------------------------- </tt>

<tt> master </tt>

<tt> C:\MSSQL2K\data\master.mdf </tt>

<tt> PRIMARY </tt>

<tt> 15744 KB Unlimited 10% data only </tt>

<tt> 1> </tt>

===== Sample Output for Attaching the MPWEB Database =====

<tt> 1> sp_attach_db 'MPWEB','data path\MPWEB.mdf','data path\MPWEB.ldf' </tt>

<tt> 2> go </tt>

===== Sample Output for Exiting osql =====

<tt> 1> exit </tt>

<tt> C:> </tt>

== Relocating the Database==

You may want to relocate the database and put the Cisco Unified MeetingPlace application and databases onto different servers. Examples are if the server you are using is running out of disk space, or for performance or backup considerations.

# Detach the MPWEB SQL databases on the existing (for example, local) SQL Server:
#: Follow the instructions in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Detaching the Database|Detaching the Database]].
# Attach the MPWEB SQL databases to the new (for example, remote) SQL Server:
#: Follow the instructions in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Detach and Attach the MPWEB SQL Database#Attaching the Database|Attaching the Database]].
# Change the Database Connection settings on your Cisco Unified MeetingPlace Web Conferencing server to point to the new (in this example, remote) SQL Server:
## Double-click the orange door icon in the System Tray.
## Click '''Web Conferencing'''.
## Enter the remote SQL server name in the Server field.
## Enter the new Username and Password.
## Click '''OK'''.

[[Category: Configuring Web Conferencing for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace Express, Release 2.x -- Creating a Dedicated E-Mail Account on the Microsoft Exchange Server

2009-04-03T18:21:18Z

MeetingPlace Express Moderator:

This section describes how to create a dedicated e-mail account on the Microsoft Exchange Server to enable communication with Cisco Unified MeetingPlace Express. For details about performing each step, see the documentation for your specific Microsoft Exchange Server.

===== Restriction =====

The maximum length for the password for the dedicated e-mail account on the Microsoft Exchange Server is set by the NTLM authentication protocol. See http://support.microsoft.com/kb/102716 for more information.

===== Procedure =====

# Create a user on your Microsoft Windows domain, for example, "MeetingPlaceExpress."
# Create a mailbox for this user on the Microsoft Exchange Server.
# Ensure that the dedicated e-mail account has the "Send As" permission if the Microsoft Exchange Server is configured to disable anonymous access via SMTP.

'''Note:''' For Cisco Unified MeetingPlace Express Release 2.1 and later, we have added support for both Microsoft Exchange 2003 and Microsoft Exchange 2007. If you want to support both versions of Microsoft Exchange notification services, connect using SMTP port 25 instead of using OWA (which is what was used for Cisco Unified MeetingPlace Express Release 2.0 and earlier releases).

The following is what the connection failure (after you upgrade to Cisco Unified MeetingPlace Express Release 2.1) looks like (as seen in the System Information Capture):

[--rcms--][http-8080-Processor24] 2009-04-02 18:27:39,434 [ERROR,EmailSender 892] mail.MessagingException javax.mail.MessagingException: Could not connect to SMTP host: chqsrvr17, port: 25, response: -1

[[Category:Microsoft Outlook and Cisco Unified MeetingPlace Express, Release 2.x]]

Cisco Unified MeetingPlace Express, Release 2.x -- Creating a Dedicated E-Mail Account on the Microsoft Exchange Server

2009-04-03T18:20:35Z

MeetingPlace Express Moderator:

This section describes how to create a dedicated e-mail account on the Microsoft Exchange Server to enable communication with Cisco Unified MeetingPlace Express. For details about performing each step, see the documentation for your specific Microsoft Exchange Server.

===== Restriction =====

The maximum length for the password for the dedicated e-mail account on the Microsoft Exchange Server is set by the NTLM authentication protocol. See http://support.microsoft.com/kb/102716 for more information.

===== Procedure =====

# Create a user on your Microsoft Windows domain, for example, "MeetingPlaceExpress."
# Create a mailbox for this user on the Microsoft Exchange Server.
# Ensure that the dedicated e-mail account has the "Send As" permission if the Microsoft Exchange Server is configured to disable anonymous access via SMTP.

'''Note:''' For Cisco Unified MeetingPlace Express Release 2.1 and later, we have added support for both Microsoft Exchange 2003 and Microsoft Exchange 2007. If you want to support both versions of Microsoft Exchange notification services, connect using SMTP port 25 instead of using OWA (which is what was used for Cisco Unified MeetingPlace Express Release 2.0 and earlier releases).

The connection failure after you upgrade to Cisco Unified MeetingPlace Express Release 2.1, looks like this (as seen in the System Information Capture):

[--rcms--][http-8080-Processor24] 2009-04-02 18:27:39,434 [ERROR,EmailSender 892] mail.MessagingException javax.mail.MessagingException: Could not connect to SMTP host: chqsrvr17, port: 25, response: -1

[[Category:Microsoft Outlook and Cisco Unified MeetingPlace Express, Release 2.x]]

Cisco Unified MeetingPlace Express, Release 2.x -- Creating a Dedicated E-Mail Account on the Microsoft Exchange Server

2009-04-03T18:19:38Z

MeetingPlace Express Moderator:

This section describes how to create a dedicated e-mail account on the Microsoft Exchange Server to enable communication with Cisco Unified MeetingPlace Express. For details about performing each step, see the documentation for your specific Microsoft Exchange Server.

===== Restriction =====

The maximum length for the password for the dedicated e-mail account on the Microsoft Exchange Server is set by the NTLM authentication protocol. See http://support.microsoft.com/kb/102716 for more information.

===== Procedure =====

# Create a user on your Microsoft Windows domain, for example, "MeetingPlaceExpress."
# Create a mailbox for this user on the Microsoft Exchange Server.
# Ensure that the dedicated e-mail account has the "Send As" permission if the Microsoft Exchange Server is configured to disable anonymous access via SMTP.

'''Note:''' For Cisco Unified MeetingPlace Express Release 2.1 and later, we have added support for both Microsoft Exchange 2003 and Microsoft Exchange 2007. If you want to support both versions of Microsoft Exchange notification services, connect using SMTP port 25 instead of using OWA (which is what was used for Cisco Unified MeetingPlace Express Release 2.0 and earlier releases).

The connection failure, as seen in the System Information Capture, after you upgrade to Cisco Unified MeetingPlace Express Release 2.1, looks like this:

[--rcms--][http-8080-Processor24] 2009-04-02 18:27:39,434 [ERROR,EmailSender 892] mail.MessagingException javax.mail.MessagingException: Could not connect to SMTP host: chqsrvr17, port: 25, response: -1

[[Category:Microsoft Outlook and Cisco Unified MeetingPlace Express, Release 2.x]]

Cisco Unified MeetingPlace Express, Release 2.x -- Creating a Dedicated E-Mail Account on the Microsoft Exchange Server

2009-04-03T18:19:26Z

MeetingPlace Express Moderator:

This section describes how to create a dedicated e-mail account on the Microsoft Exchange Server to enable communication with Cisco Unified MeetingPlace Express. For details about performing each step, see the documentation for your specific Microsoft Exchange Server.

===== Restriction =====

The maximum length for the password for the dedicated e-mail account on the Microsoft Exchange Server is set by the NTLM authentication protocol. See http://support.microsoft.com/kb/102716 for more information.

===== Procedure =====

# Create a user on your Microsoft Windows domain, for example, "MeetingPlaceExpress."
# Create a mailbox for this user on the Microsoft Exchange Server.
# Ensure that the dedicated e-mail account has the "Send As" permission if the Microsoft Exchange Server is configured to disable anonymous access via SMTP.

'''Note:''' For Cisco Unified MeetingPlace Express Release 2.1 and later, we have added support for both Microsoft Exchange 2003 and Microsoft Exchange 2007. If you want to support both versions of Microsoft Exchange notification services, connect using SMTP port 25 instead of using OWA (which is what was used for Cisco Unified MeetingPlace Express Release 2.0 and earlier releases).

The connection failure, as seen in the System Information Capture, after you upgrade to Cisco Unified MeetingPlace Express Release 2.1, looks like this:

[--rcms--][http-8080-Processor24] 2009-04-02 18:27:39,434 [ERROR,EmailSender 892] mail.MessagingException javax.mail.MessagingException: Could not connect to SMTP host: chqsrvr17, port: 25, response: -1

[[Category:Microsoft Outlook and Cisco Unified MeetingPlace Express, Release 2.x]]

Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page

2009-04-01T22:36:15Z

MeetingPlace Express Moderator: CSCsy83620, changed description of "Allow Internet Access"

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information|Reference Information]]

To find this page, click '''User Configuration > User Profiles > Add New'''.

'''Note: ''' [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Table: Field Reference: Add User Profile Page and Edit User Profile Page|Table: Field Reference: Add User Profile Page and Edit User Profile Page]] also describes fields for the following:

* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Group Page|Add User Group Page]] and Edit User Group page in the Administration Center
*: For information about fields that are specific to user groups (not user profiles), see [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Group Page#Table: Field Reference: Add User Group Page and Edit User Group Page|Table: Field Reference: Add User Group Page and Edit User Group Page]].

* Add User Profile page and Edit User Profile page in MeetingPlace Conference Manager
*: For information about finding these pages in MeetingPlace Conference Manager:
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Update User Information#Adding a User Profile|Adding a User Profile]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- How to Update User Information#Updating a User Profile|Updating a User Profile]]

===== Table: Field Reference: Add User Profile Page and Edit User Profile Page =====

{| border = 1
|-
!Field
!Description
|-
|<td colspan="2" rowspan="1">|''' Identification'''
|-
|

First name
|

First name of the user. Used in meeting participant lists and reports.

The value of this field in the guest profile is applied to guest users. In the guest profile, keep the default value or choose a name that clearly indicates a guest meeting participant.

If you are creating a user profile for an auto-answer device, enter "autoanswerdevice" in this field. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Auto-Answer Devices#How to Configure Auto-Answer Devices|How to Configure Auto-Answer Devices]].

Restriction: (Cisco WebEx integration only) Do not leave this field blank.

Defaults for preconfigured user profiles: Guest (guest), Administrator (admin), Voice Recorder (recorder).
|-
|

Last name
|

Last name of the user. Used in meeting participant lists and reports.

The value of this field in the guest profile is applied to guest users. In the guest profile, keep the default value or choose a name that clearly indicates a guest meeting participant.

Defaults for preconfigured user profiles: User (guest), Cisco Unified MeetingPlace (admin), Cisco WebEx (recorder).
|-
|

User ID
|

Unique username by which the user logs in to Cisco Unified MeetingPlace from a workstation.

'''Note: ''' Users enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID|User ID]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] to log in to Cisco Unified MeetingPlace from a workstation. Users enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] to authenticate to Cisco Unified MeetingPlace from a touch-tone phone.

Restrictions:
* Unicode is not supported.
* Uppercase characters are automatically converted to lowercase characters.
* If this field is dimmed and marked with a padlock icon, the user is authenticated by an external directory, and you cannot modify this field. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Methods for Adding User Profiles|Methods for Adding User Profiles]].
* (For Cisco WebEx integration only) Do not modify this field in an existing user profile. Doing so disables future logins to Cisco WebEx by the user. This is also true for system administrator access to the Cisco WebEx Site Administration.
: Instead of modifying the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID|User ID]], create a new user profile in Cisco Unified MeetingPlace and deactivate the previous user profile through the Cisco WebEx Site Administration.

Defaults for preconfigured user profiles: guest (cannot modify), admin, recorder.
|-
|

User password

User password confirm
|

Password used to log in to Cisco Unified MeetingPlace from a workstation.

Restrictions:
* Unicode is not supported.
* If this field is dimmed and marked with a padlock icon, the user is authenticated by an external directory, and you cannot modify this field. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Methods for Adding User Profiles|Methods for Adding User Profiles]].
* (Guest profile only) Leave this field blank in the preconfigured guest profile, because this guest profile field is inherited in all new user profiles.

Default for the admin profile: cisco
|-
|

Last changed
|

''Display only.'' Date when the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] was last modified.

Restriction: This date does not apply to Directory Service users, whose passwords are stored and controlled by an external device. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]].
|-
|

Profile number
|

Unique number that identifies this user profile. Used to authenticate to Cisco Unified MeetingPlace from a touch-tone phone.

Recommendation: Use the phone extension or voice-mail number of the user.

Restrictions:
* If reservationless meetings are enabled on the system, then the following restrictions apply:
** You cannot configure a profile number that matches an existing meeting ID. Similarly, users will not be able to schedule a meeting whose meeting ID matches an existing profile number.
** If the profile number is longer than 17 digits, then the user cannot own reservationless meetings. This is because meeting IDs cannot be longer than 17 digits.
: For more information about reservationless meetings, see [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Reservationless Meetings#Configuring Reservationless Meetings|Configuring Reservationless Meetings]].
* This field is dimmed for the preconfigured recorder profile. To modify, see [[Cisco Unified MeetingPlace, Release 7.0 -- How to Integrate Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Cisco WebEx Audio Recorder|Configuring the Cisco WebEx Audio Recorder]].

Defaults for preconfigured user profiles: 0000 (guest, cannot modify), 0001 (admin), 0002 (recorder).
|-
|

Profile password

Profile password confirm
|

PIN used to authenticate to Cisco Unified MeetingPlace from a touch-tone phone.

Set this as a temporary default PIN. Users must change their profile password when they first connect to Cisco Unified MeetingPlace.

Restrictions:
* If this field is dimmed and marked with a padlock icon, the user is authenticated by an external directory, and you cannot modify this field. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Methods for Adding User Profiles|Methods for Adding User Profiles]].
* This field is dimmed for the preconfigured guest profile.
* This field is dimmed for the preconfigured recorder profile. To modify, see [[Cisco Unified MeetingPlace, Release 7.0 -- How to Integrate Cisco Unified MeetingPlace with Cisco WebEx#Configuring the Cisco WebEx Audio Recorder|Configuring the Cisco WebEx Audio Recorder]].

Default for the admin profile: 24726 (CISCO)
|-
|

Last changed
|

''Display only.'' Date when the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] was last modified.

Restriction: This date does not apply to Directory Service users, whose passwords are stored and controlled by an external device. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]].
|-
|

User status
|

Whether this profile is active, inactive, or locked.

A user with an inactive user profile cannot log in. The user may still attend meetings that are not restricted to profiled users. See [[Cisco Unified MeetingPlace, Release 7.0 -- Changing the User Status in Cisco Unified MeetingPlace User Profiles|Changing the User Status in Cisco Unified MeetingPlace User Profiles]].

Restriction: The preconfigured admin profile cannot be locked.

Default: Group default (Active)
|-
|

Type of user
|

Type of user, the configuration of which restricts the privileges and access available to that user in Cisco Unified MeetingPlace. See the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#About User Types|About User Types]].

Defaults:
* Guest profile: [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#End user|End user]] (cannot modify)
* Admin profile: [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]] (cannot modify)
* All others: [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#End user|End user]]
|-
|

Group name
|

Name of user group to which this user profile belongs.

Default: System
|-
|

E-mail address
|

E-mail address used in e-mail notifications. Must be in the following format:
# a-z, A-Z, 0-9
# Optional:
## One of these characters: _,.,-
## a-z, A-Z, 0-9
# @
# a-z, A-Z, 0-9, -
# .
# a-z, A-Z, 0-9-Only 2-4 characters are allowed at the end

Examples:
* me.myself@example.com
* someone@example.com

Restriction: (Cisco WebEx integration only) Cannot exceed 64 characters.

Recommendation: (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.
|-
|

E-mail type and format
|

Determines the following:
* Type of e-mail notification sent to this user for scheduled meetings.
* Format in which this user sends and receives e-mail notifications.

The value of this field in the guest profile is applied to guest users, who in this case are all meeting invitees that are ''not'' invited by profile.

Restriction: To enable the use of the Microsoft Exchange or IBM Lotus Notes formats, you first need to set up the integrations. See one of the following:
* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with IBM Lotus Notes|Integrating with IBM Lotus Notes]]
* (Release 7.0.2 and later) [[Cisco Unified MeetingPlace, Release 7.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface]]
* (Release 7.0.1 only) [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating with Microsoft Outlook|Integrating with Microsoft Outlook]]

Default: Group default (SMTP (HTML))
|-
|

Main phone number

Alternate phone number
|

Phone number1 for the system to dial out to the user.

Restrictions:
* Only the following characters are allowed:
** numeric
** space ( )
** (),-.
** The + character is allowed only as the first character in the field.
* (Cisco WebEx integration only) Cannot exceed 30 characters.

Recommendation: (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.
|-
|

Pager number
|

Pager number1 of user, used for dial-out features. The number you enter depends on the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Pager type|Pager type]]:
* For a direct-dial pager, enter the phone number that directly reaches the pager.
* For a non-direct-dial pager, enter the PIN used to access the specific pager.
: You configure the shared phone number that the system calls first to reach the pager system in the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Group Page#Phone number for non-direct-dial pagers|Phone number for non-direct-dial pagers]] field in the user group.

See [[Cisco Unified MeetingPlace, Release 7.0 -- About the Find Me Feature#How the Find Me Feature Works with Pagers|How the Find Me Feature Works with Pagers]].

Restrictions:
* The + character is allowed only as the first character in the field.
* Only the following characters are used to call the pager: 0-9, #, and *.
* All other characters are ignored by the system but generate INFO events in the system log.
* See [[Cisco Unified MeetingPlace, Release 7.0 -- About the Find Me Feature#Restrictions for Using the Find Me Feature with Pagers|Restrictions for Using the Find Me Feature with Pagers]].

Recommendation: (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.
|-
|

Pager type
|

Type of pager:
* Direct-dial pager-Pager is reached directly by dialing a phone number.
* Non-direct-dial pager-Pager is reached by dialing a phone number ''and'' entering a PIN that specifically identifies the pager.
: You configure the shared phone number that the system calls first to reach the pager system in the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Group Page#Phone number for non-direct-dial pagers|Phone number for non-direct-dial pagers]] field in the user group.

Default: Direct-dial pager
|-
|

Method of attending
|

The method by which this user joins meetings that are scheduled by this user, reservationless meetings that this user starts, and meetings to which this user is invited by profile.

Options:
* Have user call in-User either calls into meetings or uses the Call Me dial-out feature from the web.
* Have system find user-Enables the Find Me dial-out feature for this user.

Default: Have user call in
|-
|

Search order for find me
|

The order in which the system attempts to call the user for the Find Me dial-out feature.

See [[Cisco Unified MeetingPlace, Release 7.0 -- About the Find Me Feature|About the Find Me Feature]].

Defaults:
* First: Main phone
* Second: Alternate phone
* Third: Pager
|-
|

User ID of delegate
|

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID|User ID]] of the person who is allowed to view, reschedule, end, and delete meetings on behalf of this user. Only users of type [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Delegate|Delegate]] may be entered in this field.

If this field is left blank, then only users of type [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Attendant|Attendant]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]] can manage meetings on behalf of this user.

Restrictions:
* When a meeting is ''rescheduled'' by a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Delegate|Delegate]], [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Attendant|Attendant]], or [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]] on behalf of another user, the meeting attributes are not changed unless specifically modified through the More Options page.
* Microsoft Outlook delegates are completely separate from Cisco Unified MeetingPlace delegates. The [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Type of user|Type of user]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID of delegate|User ID of delegate]] fields in Cisco Unified MeetingPlace user profiles do not affect the privileges and capabilities of Microsoft Outlook delegates.

Default: Group default (None)
|-
|

Region
|

Geographical region that determines which options become available in the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Time zone|Time zone]] field.

Default: Other
|-
|

Time zone
|

Time zone in which the user typically conducts business. The drop-down menu options depend on which [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Region|Region]] is selected.

Recommendations:
* Do not use the default "Local time of Cisco Unified MeetingPlace server," which is configured during installation and may be modified at any time through the CLI. Time discrepancies may occur between meetings that are scheduled before and after each server time change.
* See the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#About Time Zones|About Time Zones]].

Default: Group default (Local time of Cisco Unified MeetingPlace server)
|-
|

Language
|

Choose from the languages that were previously installed and activated on the system. See the [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Languages for Cisco Unified MeetingPlace|Configuring Languages for Cisco Unified MeetingPlace]] module.

The value of this field in the guest profile is applied to guest users.

Default: Group default (English (US))
|-
|

Billing code
|

Billing code that is applied to meetings scheduled by the user. Meeting schedulers can modify the billing code for each meeting. Billing reports are sorted by billing code and then by [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID|User ID]].

'''Note: ''' If an [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Attendant|Attendant]] or [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#System administrator|System administrator]] schedules a meeting on behalf of another user, then the meeting uses the billing code of the meeting scheduler, but the system counts the minutes against the meeting owner (on whose behalf the meeting was scheduled).

Recommendations:
* Follow existing conventions at your company, such as department codes.
* (Guest profile only) Leave this field blank, because this field is inherited by all new user profiles.

Default: Group default (None)
|-
|

Default meeting category
|

Meeting category that appears by default on the scheduling page for this user.

Unless you hide the field on the end-user web interface, meeting schedulers can specify the meeting category for each meeting. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Meeting Categories#Configuring Meeting Categories|Configuring Meeting Categories]].

Default: Group default (Standard)
|-
|

Schedule home server
|

Local Cisco Unified MeetingPlace Application Server assigned to this user.

When the user schedules a meeting, the system attempts to schedule the meeting through this Application Server first. If the server does not have enough resources, then the system tries another Application Server, for example, a remote RSNA system.

Requirement: This number must match the [[Cisco Unified MeetingPlace, Release 7.0 -- Add Server Configuration Page#Home Server number|Home Server number]] that identifies this server.

'''Note: ''' If you want to assign an [[Cisco Unified MeetingPlace, Release 7.0 -- About RSNA#RSNA Reserved Meeting Server|RSNA Reserved Meeting Server]] to this user, make sure that the system has two remote server records for the reserved meeting server: one with a [[Cisco Unified MeetingPlace, Release 7.0 -- Add Server Configuration Page#Home Server number|Home Server number]] in the range 0 to 999, and one with a checked [[Cisco Unified MeetingPlace, Release 7.0 -- Add Server Configuration Page#Reserved Meeting Server|Reserved Meeting Server]] check box. For details, see [[Cisco Unified MeetingPlace, Release 7.0 -- About RSNA#RSNA Reserved Meeting Server|RSNA Reserved Meeting Server]].

Default: Group default (0)
|-
|<td colspan="2" rowspan="1">|''' Permissions '''
|-
|

Use reservationless
|

Whether the user can own reservationless meetings.

Default: Group default (Yes)
|-
|

Maximum meeting length (minutes)
|

User cannot schedule meetings longer than this number of minutes.

Restrictions:
* This field does not apply to continuous meetings.
* If this value differs from the following, then the system uses the lowest value:
** [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Maximum meeting length (minutes)|Maximum meeting length (minutes)]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting Configuration Page|Meeting Configuration Page]].
** Maximum Call Duration Timer service parameter in Cisco Unified Communications Manager.
:: See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring the Maximum Call Duration in Cisco Unified Communications Manager|Configuring the Maximum Call Duration in Cisco Unified Communications Manager]].

Default: Group default (240)
|-
|

Scheduling restriction (meetings to start within 6 hours of scheduling)
|

Scheduling restrictions for this user:
* Unrestricted-User may schedule an unlimited number of meetings.
* Cannot schedule-User cannot schedule meetings, regardless of start time.
* ''Numeric value''-Maximum number of meetings that the user may schedule to begin within six hours after the time of scheduling.
: Each time the user attempts to schedule a meeting, the system counts the number of meetings owned by the user that are scheduled to begin within the next six hours. If this number is greater than the field value, then the user cannot schedule any more meetings to begin within the next six hours. Note that the user may still schedule an unlimited number of meetings to begin more than six hours after the time of scheduling.

Default: Group default (Unrestricted)
|-
|

Maximum number of attachments
|

Maximum number of attachments the user may upload per meeting.

Default: Group default (10)
|-
|

Can change meeting ID via phone
|

Whether the user can change the meeting ID over the phone for meetings owned by the user.

Default: Group default (Yes)
|-
|

Video usage
|

Whether the user can attend, host, or reserve video ports for video meetings.
* Can attend video meetings
** User can attend video-enabled meetings as a video participant.
** User ''cannot'' schedule meetings that allow video participants.
* Can attend + host video meetings
** User can attend video-enabled meetings as a video participant.
** User schedules video-enabled meetings, which means that video participants may attend.
* Can attend + host video meetings + reserve video ports
** User can attend video-enabled meetings as a video participant.
** User schedules video-enabled meetings, which means that video participants may attend.
** While scheduling meetings, the user can reserve video resources and invite video terminals.

Default: Group default (Can attend video meetings)
|-
|

Can call out from meetings
|

Whether dial-out privileges are enabled for this user.

The value of this field in the guest profile is applied to guest users.

Restriction: ''Anyone'' may dial out from Cisco WebEx web meetings, regardless of the user profile settings.

Default: Group default (Yes)
|-
|

Maximum TUI outdial attempts per meeting
|

Maximum number of TUI (#31) dial-out calls that this user may attempt from within a meeting.
* Failed dial-out attempts from the TUI count against this number.
* Dial-out attempts from the web meeting room do ''not'' count against this number.

A value of 0 means that the user cannot press #3 to dial out from within a meeting.

Default: Group default (Unrestricted)
|-
|

Can send notifications
|

Whether notifications are sent for meetings scheduled by the user.

Restriction: Notifications are never sent for reservationless meetings.

Recommendations: Use a consistent setting across your user base. Also, avoid changing this setting once Cisco Unified MeetingPlace is in use, because users might expect and rely on the current e-mail notification behavior.

Default: Group default (Yes)
|-
|

Can receive notifications
|

Whether to send e-mail notifications to the user.

Recommendations: Use a consistent setting across your user base. Also, avoid changing this setting once Cisco Unified MeetingPlace is in use, because users might expect and rely on the current e-mail notification behavior.

Default: Group default (Yes)
|-
|

Auto attend mode
|

Enables or disables the auto attend feature for the user. When enabled, you specify whether the caller automatically joins meetings or is only authenticated.

For details, see [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring the Auto Attend Feature for Cisco Unified MeetingPlace|Configuring the Auto Attend Feature for Cisco Unified MeetingPlace]].

Default: Group default (None)
|-
|

Auto attend requires profile password
|

When the auto attend feature is enabled, this field specifies whether the user must enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] before being automatically authenticated or placed into meetings.

Default: Group default (Yes)
|-
|

Meeting password required
|

Whether scheduled and reservationless meetings owned by this user require a meeting password.

Restrictions:
* This field is ignored if the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Minimum meeting password length|Minimum meeting password length]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting Configuration Page|Meeting Configuration Page]] is set to 0.
* In reservationless meetings, meeting passwords are not required to join the web meeting room.

Default: Group default (No)
|-
|

Can record meetings
|

Whether this user has recording privileges, specifically:
* Whether this user can start and stop the recording of any meeting from the TUI, regardless of who scheduled the meeting.
* For meetings owned by this user, whether moderators can start and stop recording from the web meeting room.
* Whether this user can configure the following options after clicking '''More Options''' from the New Meeting scheduling page:
** Reserve a recording resource (if any are available for the meeting time)
** Automatically start recording the meeting

Restriction (guest profile only): When set to Yes, this field enables guest users to start and stop meeting recordings:
* From the TUI only (not from the web meeting room).
* Only if the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Guests can lock and record meetings|Guests can lock and record meetings]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Usage Configuration Page|Usage Configuration Page]] is also set to Yes.

Default: Group default (No)
|-
|<td colspan="2" rowspan="1">|''' Recordings and Attachments'''
|-
|

Who can access
|

Who can access attachments and listen to recordings for scheduled meetings owned by this user.

Restriction: This field does not apply to reservationless meetings. Anyone can access reservationless meeting recordings and attachments.

Default: Group default (Anyone)
|-
|

Reserve resource for recording
|

When set to Yes, the system attempts to reserve a recording resource for each meeting owned by this user. If a recording resource is available, then the system reserves the resource from the scheduled meeting start time until the scheduled meeting end time. If the meeting terminates before the scheduled end time, so does the resource reservation.

When set to No:
* If a recording resource is available, then a meeting participant (with recording privileges) may still start recording from the TUI, or a meeting moderator may start recording from the web meeting room. If, however, no recording resources are available at that time, then the meeting cannot be recorded until a recording resource is released.
* If the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Auto-start recording|Auto-start recording]] field is set to Yes, recording does ''not'' automatically start for meetings owned by this user. Instead, either a meeting participant (with recording privileges) starts the recording from the TUI, or a meeting moderator starts the recording from the web meeting room. If, however, all participants leave a meeting that is being recorded, then the recording will restart automatically if users rejoin the meeting.
: Both the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Reserve resource for recording|Reserve resource for recording]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Auto-start recording|Auto-start recording]] fields affect whether and how the system automatically starts recording meetings. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Recordings#Table: User Profile Field Combinations for Automatically Starting Recordings|Table: User Profile Field Combinations for Automatically Starting Recordings]].

See [[Cisco Unified MeetingPlace, Release 7.0 -- About Recordings#Recording Resources and Port Usage|Recording Resources and Port Usage]].

Restriction: This field is always set to No when the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Can record meetings|Can record meetings]] field is set to No.

Default: Group default (No)
|-
|

Auto-start recording
|

When set to No, the system never automatically starts recording meetings that are owned by this user. Instead, a meeting participant (with recording privileges) must start the recording.

When set to Yes:
* Recording begins when the first user enters the audio component of a Collaborative or Presentation meeting, or when the moderator joins a Webinar meeting. For information about these meeting templates, see the ''User Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.
* If the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Reserve resource for recording|Reserve resource for recording]] field is set to No, recording does ''not'' automatically start for meetings owned by this user. Instead, a meeting participant (with recording privileges) must start the meeting recording. If, however, all participants leave a meeting that is being recorded, then the recording will restart automatically if users rejoin the meeting.
: Both the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Reserve resource for recording|Reserve resource for recording]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Auto-start recording|Auto-start recording]] fields affect whether and how the system automatically starts recording meetings. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Recordings#Table: User Profile Field Combinations for Automatically Starting Recordings|Table: User Profile Field Combinations for Automatically Starting Recordings]].

See [[Cisco Unified MeetingPlace, Release 7.0 -- About Recordings#Options for Starting Meeting Recordings|Options for Starting Meeting Recordings]].

Restriction: This field is always set to No when the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Can record meetings|Can record meetings]] field is set to No.

Default: Group default (No)
|-
|<td colspan="2" rowspan="1">|''' Outdial Meeting Defaults'''
|-
|

Ask for profile password
|

Whether a dialed-out participant must provide a profile password before being admitted into the meeting.

Default: Group default (Yes)
|-
|<td colspan="2" rowspan="1">|''' Meeting Preferences '''
|-
|

Entry announcement
|

Announcement played when callers join meetings scheduled by this user.

Default: Group default (Beep + name)
|-
|

Departure announcement
|

Announcement played when callers leave meetings scheduled by this user.

Default: Group default (Beep + name)
|-
|

Meeting entry mode
|

Whether participants hear one, both, or none of the following items when they join meetings scheduled by this user:
* Meeting ID confirmation
* Name recording option

Restriction: Participants who automatically join a meeting through the [[Cisco Unified MeetingPlace, Release 7.0 -- Auto Attend Feature|Auto Attend Feature]] will hear the meeting ID confirmation, even if the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Meeting entry mode|Meeting entry mode]] for the meeting is configured to skip the meeting ID.

Default: Group default (Skip ID repeat)
|-
|

Who may skip password
|

Specifies who may join a meeting scheduled by this user without entering a meeting password.

Default: Group default (Nobody)
|-
|

Who can attend
|

Specifies who may attend meetings scheduled by this user.

Restrictions:
* This field is ignored for reservationless meetings, which anyone may attend.
* If meeting attendance is restricted to profiled users, then:
** Unprofiled external users (such as your customers or business partners) and users with locked profiles cannot attend meetings, even if they are invited.
** Only those who successfully authenticate to Cisco Unified MeetingPlace may attend these meetings.

Default: Group default (Anyone)
|-
|

Show meetings in public listing
|

Whether to publicly list the meetings scheduled by this user in the end-user web interface.

Unless you hide the field on the end-user web interface, meeting schedulers can override this setting.

Default: Group default (No)
|-
|

Show reservationless meetings in public listing
|

Whether to publicly display reservationless meetings owned by this user in the end-user web interface.

Default: Group default (Yes)
|-
|

Host web meetings with
|

Whether web ports are reserved when users in this group set up meetings:
* Full meeting room-Reserves web ports, if available.
* Participant list only-Does not reserve web ports. Web meeting participants see the lite web meeting room.

For information about the features available in the full web meeting room and the lite web meeting room, see the ''User Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.

'''Note: ''' This field applies to both scheduled and reservationless meetings.

Restriction: If the user is logged in when this field is modified, then the previous setting applies until the user logs out and logs back in.

Recommendation: If your system has fewer web ports than voice ports available for scheduled and reservationless meetings, then set this field to '''Participant list only (no licenses required)''' for most users. This configuration helps to keep web ports available for the users who need the full web meeting room to share files or applications. If you want all or most users to be able to schedule full web meetings, make sure that an equal number of web ports and voice parts are available on your system for scheduled and reservationless meetings. See [[Cisco Unified MeetingPlace, Release 7.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]].

Default: Group default (Full meeting room (licenses required))
|-
|

End of meeting announcement
|

Whether the end-of-meeting announcement is played in meetings scheduled by this user.

Default: Group default (No)
|-
|

Meeting extension announcement
|

Whether meeting-extension announcements are played in meetings scheduled by this user.

Default: Group default (No)
|-
|

Screened entry
|

Whether screened entry is enabled in meetings scheduled by this user.

Default: Group default (No)
|-
|

Disable roll call
|

Whether to disable roll call in meetings scheduled by this user.

Default: Group default (No)
|-
|

Allow Internet access
|

Whether this user can schedule meetings on a Web Server in the DMZ.
* Yes-User can schedule web meetings that are accessible by anyone on the Internet or intranet. By default, meetings scheduled by this user are held on the Web Server in the DMZ.
* No-User can schedule web meetings for users on the intranet only.

'''NOTE:''' This is a preference setting and not a permission setting. Users can change this value and schedule web meetings on the Internet or intranet.

Default: Group default (No)
|-
|

Reservationless allow Internet access
|

Whether this user can host reservationless meetings on a Web Server in the DMZ.
* Yes-User can host reservationless web meetings that are accessible by anyone on the Internet or intranet.
* No-User can host reservationless web meetings for users on the intranet only.

Default: Group default (Yes)
|-
|

Lecture meeting attend settings
|

How listen-only participants attend lecture-style meetings scheduled by this user:
* Admit as listeners
: Automatically enter the meeting through the meeting room with their speaking ability turned off. Video participants receive video even when their speaking ability is turned off. Meeting controllers can "Open the floor" at any time to allow for general discussion.
* Start callers in waiting room
: Automatically enter the meeting through the waiting room where they can listen to on-hold music plus any meeting announcements the moderator may have recorded. This option allows speakers to converse in private in the main meeting room before beginning the meeting. Video is blocked for video participants. However, the web portion of the meeting is visible to all web participants.
: When the moderators are ready to start the audio and video portion of the meeting, they can "Call the meeting to order" and bring all the waiting room participants into the meeting. Participants automatically have their speaking ability turned off until the moderator chooses to "Open the floor." Video participants receive video.
* Start meeting with floor open
: Automatically enter the meeting through the meeting room with their speaking ability turned on. When the meeting is set to begin, the meeting controller can "Close the floor" and turn off the speaking ability of participants. Video participants receive video throughout.

Default: Group default (Admit as listeners)
|-
|

Hide web conference provider
|

Whether the user sees the web conferencing provider field while scheduling meetings.

Restriction: This field appears only when Cisco Unified MeetingPlace is integrated with Cisco WebEx, specifically when the [[Cisco Unified MeetingPlace, Release 7.0 -- Cisco WebEx Site and Server Page#Web conference scheduling|Web conference scheduling]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Cisco WebEx Site and Server Page#Cisco WebEx Site and Server Page|Cisco WebEx Site and Server Page]] is set to Unified MP schedule, Cisco WebEx meeting.

Default: Group default (Yes)
|-
|

Default web conference provider
|

Choose between Cisco Unified MeetingPlace or Cisco WebEx.

Restriction: This field appears only when Cisco Unified MeetingPlace is integrated with Cisco WebEx, specifically when the [[Cisco Unified MeetingPlace, Release 7.0 -- Cisco WebEx Site and Server Page#Web conference scheduling|Web conference scheduling]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Cisco WebEx Site and Server Page#Cisco WebEx Site and Server Page|Cisco WebEx Site and Server Page]] is set to Unified MP schedule, Cisco WebEx meeting.

Default: Group default (Cisco Unified MeetingPlace)
|-
|<td colspan="2" rowspan="1">|''' Notifications '''
|-
|

Priority
|

Priority of e-mail notifications for meetings scheduled by the user.

Default: Group default (Normal)
|-
|

Send if meeting changes
|

Whether e-mail notifications are sent when the following parameters change for meetings scheduled by the user:
* Date or time
* Password
* Meeting ID
* List of invitees

Recommendations: Use a consistent setting across your user base. Also, avoid changing this setting once Cisco Unified MeetingPlace is in use, because users might expect and rely on the current e-mail notification behavior.

Default: Group default (Yes)
|-
|

Include invitee list when scheduled from web
|

Whether to include a list of invitees in e-mail notifications for meetings that the user schedules from the Cisco Unified MeetingPlace end-user web interface.

Note that a list of meeting invitees is ''not'' included in e-mail notifications for meetings that are scheduled from IBM Lotus Notes or the Microsoft Outlook calendar. Users can view the list of invitees through the Microsoft Outlook Scheduling tab.

Default: Group default (Yes)
|-
|

Include password
|

Whether the meeting password (if any) is included in e-mail notifications for meetings scheduled by the user.

Default: Group default (No)
|-
|

Send attachments
|

Whether to include attachments in e-mail notifications for meetings scheduled by the user.

Default: Group default (No)
|-
|

Receive attachments
|

Whether to include attachments in e-mail notifications sent to this user.

Default: Group default (No)
|-
|<td colspan="2" rowspan="1">|''' Q&A Meetings'''
|-
|

Off at meeting startup
|

Whether Cisco Unified MeetingPlace disables the Q&A feature at the start of lecture-style meetings scheduled by this user. If Q&A is disabled at the start, the moderator can enable the Q&A feature during the meeting by pressing '''#7'''.

Default: Group default (No)
|-
|

Notify attendees about Q&A
|

Whether to play an instructional Q&A prompt as people join lecture-style meetings scheduled by this user.

Default: Group default (No)
|-
|

Q&A introduction
|

Whether to announce to everyone when a participant is given the floor in lecture-style meetings scheduled by this user.

Default: Group default (Beep + name)
|-
|

Q&A departure
|

Whether to announce to everyone when a participant leaves the floor in lecture-style meetings scheduled by this user.

Default: Group default (Beep + name)
|-
|

Automatically ask next question
|

In lecture-style meetings scheduled by this user, whether participants in line to ask a question are automatically granted speaking ability at their turn.

Default: Group default (No)
|-
|

More than one question per site
|

In lecture-style meetings scheduled by this user, whether any participant may occupy multiple positions in the queue to ask a question.

This field does not limit the number of questions a participant can ask, but it does limit the number of times they can be listed in the queue to ask a question.

Default: Group default (Yes)
|-
|

Tell my position in line
|

While attending a lecture-style meeting, whether this user is informed about the position in the queue to ask a question.

Default: Group default (Yes)
|-
|

Disable floor warning prompt
|

While attending a lecture-style meeting, whether this user is warned about being next in line to be given the floor.

Default: Group default (Yes)
|-
|<td colspan="2" rowspan="1">|Flex Fields
|-
|<td colspan="2" rowspan="1">|If profile flex fields are configured, then they appear in this area. See the [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Flex Fields for Cisco Unified MeetingPlace#Configuring Flex Fields for Cisco Unified MeetingPlace|Configuring Flex Fields for Cisco Unified MeetingPlace]] module.
|}

'''Footnote 1:''' The required format for phone numbers is determined by the call-control device for your IP telephony network. Therefore, enter phone numbers in the same format used to dial similar numbers from a phone on the same IP telephony network as Cisco Unified MeetingPlace. For example, if calls within your company are made by dialing the last four digits of a phone number, then enter only the last four digits in Cisco Unified MeetingPlace for internal phone numbers. If, however, you want Cisco Unified MeetingPlace to call a phone in a different area code, then you may need to include a 9 and the complete telephone number including the area code.

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring User Profiles and User Groups for Cisco Unified MeetingPlace|Configuring User Profiles and User Groups for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Recordings for Cisco Unified MeetingPlace|Configuring Recordings for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Dial-Out Features for Cisco Unified MeetingPlace|Configuring Dial-Out Features for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Flex Fields for Cisco Unified MeetingPlace|Configuring Flex Fields for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace|Configuring Reservationless Single Number Access (RSNA) for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Moderate a Question and Answer Session|How to Moderate a Question and Answer Session]]

== Reference Information about User Profile Fields ==

=== About User Types ===

The [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Type of user|Type of user]] field in each user profile determines the user privileges and capabilities in Cisco Unified MeetingPlace. See [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Table: Types of Users|Table: Types of Users]].

===== Table: Types of Users =====

{| border = 1
|-
![[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Type of user|Type of user]]
!Description
|-
|

End user
|
* Can schedule and control meetings, attend meetings to which they have been invited, attend any publicly listed meeting, and modify preferences in their own user profiles.
* Cannot access the Administration Center or MeetingPlace Conference Manager.
|-
|

Delegate
|
* Can view, reschedule, end, or delete meetings on behalf of end users whose user profiles specify that delegate in the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID of delegate|User ID of delegate]] field.
* Cannot ''schedule'' meetings on behalf of other users, even those whose user profiles specify that delegate in the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID of delegate|User ID of delegate]] field.* Cannot access the Administration Center or MeetingPlace Conference Manager.

'''Note: ''' Microsoft Outlook delegates are completely separate from Cisco Unified MeetingPlace delegates. The [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Type of user|Type of user]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID of delegate|User ID of delegate]] fields in Cisco Unified MeetingPlace user profiles do not affect the privileges and capabilities of Microsoft Outlook delegates.
|-
|

Attendant
|
* Can view, schedule, reschedule, end, and delete meetings on behalf of all users.
* Has limited access to the Administration Center, depending on the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Attendant|Attendant]] privileges on the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Usage Configuration Page|Usage Configuration Page]].
* Can download and use MeetingPlace Conference Manager, though capabilities are affected by the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Attendant|Attendant]] privileges on the [[Cisco Unified MeetingPlace, Release 7.0 -- Usage Configuration Page#Usage Configuration Page|Usage Configuration Page]].
|-
|

System administrator
|
* Can join ''any'' meeting, even if the maximum number of ports per meeting are in use, as long as floater ports are available. Can join password-protected meetings without the meeting password, even if uninvited.
* Can view, schedule, reschedule, end, and delete meetings on behalf of all users.
* Has full access to the Administration Center.
* Can download and use MeetingPlace Conference Manager.
|}

===== Related Topics =====

* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Group Page|Add User Group Page]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Attendant Privileges|Configuring Attendant Privileges]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Using MeetingPlace Conference Manager|Using MeetingPlace Conference Manager]]

=== About Time Zones ===

Each user profile has a [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Time zone|Time zone]] setting. Things you should know about time zones in Cisco Unified MeetingPlace:

* For each meeting, Cisco Unified MeetingPlace accepts and reports the start time in the time zone of the meeting scheduler.

* All e-mail notifications use the time zone of the meeting scheduler, even those that are sent to invitees in different time zones.

* On the Find Meeting and Meeting Details pages in the end-user web interface, the meeting times appear in the time zone of the user who is logged into the end-user web interface.

* All instances of recurring meetings take place at the same time of day in the time zone configured in the user profile of the meeting scheduler. Meeting invitees must adjust for time zone differences. Remember that some locations, such as Arizona, do not use daylight savings time.

* Cisco Unified MeetingPlace schedules meetings using Greenwich Mean Time (GMT). At the time each meeting is scheduled, the system converts the meeting time to GMT from the time zone that is defined in the user profile of the meeting scheduler. If the time zone setting is changed in the user profile ''after'' a meeting is scheduled, the scheduled time of that meeting does ''not'' change to reflect the new time zone. Meetings must be rescheduled to reflect the new time zone.

===== Related Topics =====
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Group Page|Add User Group Page]]

[[Category: Reference Information for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:12:11Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]]

This document lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in release 6.x.

For upgrades, we recommend that you upgrade at the same time Audio Server and all other component software in use. Version combinations listed as supported in this document have been tested together. Although we attempt to maintain backward compatibility with new releases, it is not possible to test all version combinations. As a result, we cannot support version combinations that are not listed in this document.

If you upgrade Cisco Unified MeetingPlace components at different times, you do so at your own risk. If you call Cisco TAC with a problem, an engineer may require that you upgrade components to a supported combination if the versions are out of synchronization.

For components upgraded at different times, we recommend that you respect the logical dependency order among the Cisco Unified MeetingPlace components:
# Audio Server.
# Cisco Unified MeetingPlace components dependent on Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP Gateway, Directory Services, SMTP E-Mail Gateway.
# Cisco Unified MeetingPlace components dependent on Web Conferencing: Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace for Jabber, Video Integration.

'''Note: ''' Certain versions of some components have a hard requirement to be upgraded at the same time. Refer to the applicable readme file or release notes for each component to understand component dependencies before installing or upgrading.

To determine the version of the various software components, see [[Cisco Unified MeetingPlace, Release 6.x -- Determining the Software Version|Determining the Software Version]].

== Audio Server Version 6.x ==

===== Table: Supported Version Combinations for Audio Server 6.x and Other Cisco Unified MeetingPlace Components =====

{| border = 1 cellpadding="4" cellspacing="2"
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(4.7)'''

Also known as

Maintenance Release 4 (MR4)

Released: March 27, 2009

'''NOTE:''' Audio Server Release 6.0(4.4),

which was released on 12/12/08,

has been retired.

If you have Release 6.0(4.4),

upgrade to Release 6.0(4.7)
|
Directory Services 5.4(205.0)
|
December 16, 2008
|-
|
EMP 5.6.1.0.4
|
October 31, 2008
|-
|
Gateway SIM 5.2(0.80)
|
December 16, 2008
|-
|
H.323/SIP Gateway 5.3(1.61)
|
December 12, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(405.0)
* 5.4(109.0) 1 
|
* December 17, 2008
* July 3, 2007
|-
|
MCU 5.6(1.1.13)
|
October 31, 2008
|-
|
MeetingTime 6.0(4.6)
|
December 12, 2008
|-
|

Network Backup Gateway 5.3(0.12)
|

December 16, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0) 1
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(402.0)
|

December 16, 2008
|-
|

Video Administration 5.6(2.101)
|

December 16, 2008
|-
|

Video Integration 5.4(206.0)
|

December 16, 2008
|-
|

Web Conferencing:
* 6.0(517.0)
* 5.4(156.2) 2 
|

* December 17, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(3.5)'''

Also known as

Maintenance Release 3 (MR3)

Released May 28, 2008
|
Directory Services 5.4(114.0)
|
July 21, 2008
|-
|
EMP 5.5.2.0.2
|
June 2, 2008
|-
|
Gateway SIM 5.2(0.78)
|
June 2, 2008
|-
|
H.323/SIP Gateway 5.3(1.40)
|
June 2, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(205.0)
* 5.4(109.0) 1 
|
* June 2, 2008
* July 3, 2007
|-
|
MCU 5.5(0.0.54)
|
June 2, 2008
|-
|
MeetingTime 6.0(3.1)
|
June 2, 2008
|-
|

Network Backup Gateway 5.3(0.11)
|

June 2, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0) 1
|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(2.103)
|

June 2, 2008
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(417.0)
* 5.4(156.2) 2 
|

* June 2, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="18" valign="top"|'''6.0(2.13)'''

Also known as

Maintenance Release 2 (MR2)

Released January 31, 2008
|

Directory Services 5.4(108.0)
|

January 31, 2008
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.77)
|

January 31, 2008
|-
|

H.323/SIP Gateway 5.3(1.33)
|

January 31, 2008
|-
|

Jabber Integration 6.0(2.0)
|

May 31, 2007
|-
|

Language Pack 6.0(2.13)
|

January 31, 2008
|-
|

Lotus Notes Integration:
* 6.0(203.0)
* 5.4(109.0) 1 
|

* January 31, 2008
* July 3, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(2.4)
|

January 31, 2008
|-
|

Network Backup Gateway 5.3(0.10)
|

January 31, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0) 1
|

* January 31, 2008
* December 21, 2007
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(361.0)
* 5.4(156.2) 2
|

* January 31, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="17" valign="top"|'''6.0(1.11)'''

Also known as

Maintenance Release 1 (MR1)

Released September 7, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.74)
|

September 7, 2007
|-
|

H.323/SIP Gateway 5.3(1.29)
|

September 7, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(104.0)
|

September 7, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(1.4)
|

September 7, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(102.0)
|

September 7, 2007
|-
|

Outlook Integration 6.0(115.0)
|

September 7, 2007
|-
|

SMTP E-Mail Gateway 6.0(107.0)
|

September 7, 2007
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

September 7, 2007
|-
|

Web Conferencing

6.0(244.0)

5.4(156.2) 2
|

September 7, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="15" valign="top"|'''6.0(0.25)'''
Released May 31, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

Gateway SIM 5.2(0.71)
|

May 31, 2007
|-
|

H.323/SIP Gateway 5.3(1.8)
|

May 31, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(15.0)
|

May 31, 2007
|-
|

MeetingTime 6.0(0.23)
|

May 31, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(11.0)
|

May 31, 2007
|-
|

Outlook Integration 6.0(14.0)
|

May 31, 2007
|-
|

SMTP E-Mail Gateway 5.4(108)
|

March 30, 2007
|-
|

Video Administration 5.4(0.105)
|

March 30, 2007
|-
|

Video Integration 5.4(107.0)
|

March 30, 2007
|-
|

Web Conferencing

6.0(171.0)

5.4(156.2) 2 
|

May 31, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.

See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]

|-
|colspan="2"|Language pack appropriate for this release.
|-
|}

'''Footnote:'''

1: Requires Web Conferencing Release 5.4.(156.2).

2: This release is a hotfix and is only available by contacting Cisco TAC.

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:11:52Z

MeetingPlace Express Moderator:

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:11:17Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]]

This document lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in release 6.x.

For upgrades, we recommend that you upgrade at the same time Audio Server and all other component software in use. Version combinations listed as supported in this document have been tested together. Although we attempt to maintain backward compatibility with new releases, it is not possible to test all version combinations. As a result, we cannot support version combinations that are not listed in this document.

If you upgrade Cisco Unified MeetingPlace components at different times, you do so at your own risk. If you call Cisco TAC with a problem, an engineer may require that you upgrade components to a supported combination if the versions are out of synchronization.

For components upgraded at different times, we recommend that you respect the logical dependency order among the Cisco Unified MeetingPlace components:
# Audio Server.
# Cisco Unified MeetingPlace components dependent on Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP Gateway, Directory Services, SMTP E-Mail Gateway.
# Cisco Unified MeetingPlace components dependent on Web Conferencing: Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace for Jabber, Video Integration.

'''Note: ''' Certain versions of some components have a hard requirement to be upgraded at the same time. Refer to the applicable readme file or release notes for each component to understand component dependencies before installing or upgrading.

To determine the version of the various software components, see [[Cisco Unified MeetingPlace, Release 6.x -- Determining the Software Version|Determining the Software Version]].

== Audio Server Version 6.x ==

===== Table: Supported Version Combinations for Audio Server 6.x and Other Cisco Unified MeetingPlace Components =====

{| border = 1 cellpadding="4" cellspacing="2"
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(4.7)'''

Also known as
Maintenance Release 4 (MR4)

Released: March 27, 2009

'''NOTE:''' Audio Server Release 6.0(4.4),

which was released on 12/12/08,

has been retired.

If you have Release 6.0(4.4),

upgrade to Release 6.0(4.7)
|
Directory Services 5.4(205.0)
|
December 16, 2008
|-
|
EMP 5.6.1.0.4
|
October 31, 2008
|-
|
Gateway SIM 5.2(0.80)
|
December 16, 2008
|-
|
H.323/SIP Gateway 5.3(1.61)
|
December 12, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(405.0)
* 5.4(109.0) 1 
|
* December 17, 2008
* July 3, 2007
|-
|
MCU 5.6(1.1.13)
|
October 31, 2008
|-
|
MeetingTime 6.0(4.6)
|
December 12, 2008
|-
|

Network Backup Gateway 5.3(0.12)
|

December 16, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0) 1
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(402.0)
|

December 16, 2008
|-
|

Video Administration 5.6(2.101)
|

December 16, 2008
|-
|

Video Integration 5.4(206.0)
|

December 16, 2008
|-
|

Web Conferencing:
* 6.0(517.0)
* 5.4(156.2) 2 
|

* December 17, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(3.5)'''

Also known as

Maintenance Release 3 (MR3)

Released May 28, 2008
|
Directory Services 5.4(114.0)
|
July 21, 2008
|-
|
EMP 5.5.2.0.2
|
June 2, 2008
|-
|
Gateway SIM 5.2(0.78)
|
June 2, 2008
|-
|
H.323/SIP Gateway 5.3(1.40)
|
June 2, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(205.0)
* 5.4(109.0) 1 
|
* June 2, 2008
* July 3, 2007
|-
|
MCU 5.5(0.0.54)
|
June 2, 2008
|-
|
MeetingTime 6.0(3.1)
|
June 2, 2008
|-
|

Network Backup Gateway 5.3(0.11)
|

June 2, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0) 1
|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(2.103)
|

June 2, 2008
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(417.0)
* 5.4(156.2) 2 
|

* June 2, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="18" valign="top"|'''6.0(2.13)'''

Also known as

Maintenance Release 2 (MR2)

Released January 31, 2008
|

Directory Services 5.4(108.0)
|

January 31, 2008
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.77)
|

January 31, 2008
|-
|

H.323/SIP Gateway 5.3(1.33)
|

January 31, 2008
|-
|

Jabber Integration 6.0(2.0)
|

May 31, 2007
|-
|

Language Pack 6.0(2.13)
|

January 31, 2008
|-
|

Lotus Notes Integration:
* 6.0(203.0)
* 5.4(109.0) 1 
|

* January 31, 2008
* July 3, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(2.4)
|

January 31, 2008
|-
|

Network Backup Gateway 5.3(0.10)
|

January 31, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0) 1
|

* January 31, 2008
* December 21, 2007
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(361.0)
* 5.4(156.2) 2
|

* January 31, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="17" valign="top"|'''6.0(1.11)'''

Also known as

Maintenance Release 1 (MR1)

Released September 7, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.74)
|

September 7, 2007
|-
|

H.323/SIP Gateway 5.3(1.29)
|

September 7, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(104.0)
|

September 7, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(1.4)
|

September 7, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(102.0)
|

September 7, 2007
|-
|

Outlook Integration 6.0(115.0)
|

September 7, 2007
|-
|

SMTP E-Mail Gateway 6.0(107.0)
|

September 7, 2007
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

September 7, 2007
|-
|

Web Conferencing

6.0(244.0)

5.4(156.2) 2
|

September 7, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="15" valign="top"|'''6.0(0.25)'''
Released May 31, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

Gateway SIM 5.2(0.71)
|

May 31, 2007
|-
|

H.323/SIP Gateway 5.3(1.8)
|

May 31, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(15.0)
|

May 31, 2007
|-
|

MeetingTime 6.0(0.23)
|

May 31, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(11.0)
|

May 31, 2007
|-
|

Outlook Integration 6.0(14.0)
|

May 31, 2007
|-
|

SMTP E-Mail Gateway 5.4(108)
|

March 30, 2007
|-
|

Video Administration 5.4(0.105)
|

March 30, 2007
|-
|

Video Integration 5.4(107.0)
|

March 30, 2007
|-
|

Web Conferencing

6.0(171.0)

5.4(156.2) 2 
|

May 31, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.

See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]

|-
|colspan="2"|Language pack appropriate for this release.
|-
|}

'''Footnote:'''

1: Requires Web Conferencing Release 5.4.(156.2).

2: This release is a hotfix and is only available by contacting Cisco TAC.

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:11:01Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]]

This document lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in release 6.x.

For upgrades, we recommend that you upgrade at the same time Audio Server and all other component software in use. Version combinations listed as supported in this document have been tested together. Although we attempt to maintain backward compatibility with new releases, it is not possible to test all version combinations. As a result, we cannot support version combinations that are not listed in this document.

If you upgrade Cisco Unified MeetingPlace components at different times, you do so at your own risk. If you call Cisco TAC with a problem, an engineer may require that you upgrade components to a supported combination if the versions are out of synchronization.

For components upgraded at different times, we recommend that you respect the logical dependency order among the Cisco Unified MeetingPlace components:
# Audio Server.
# Cisco Unified MeetingPlace components dependent on Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP Gateway, Directory Services, SMTP E-Mail Gateway.
# Cisco Unified MeetingPlace components dependent on Web Conferencing: Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace for Jabber, Video Integration.

'''Note: ''' Certain versions of some components have a hard requirement to be upgraded at the same time. Refer to the applicable readme file or release notes for each component to understand component dependencies before installing or upgrading.

To determine the version of the various software components, see [[Cisco Unified MeetingPlace, Release 6.x -- Determining the Software Version|Determining the Software Version]].

== Audio Server Version 6.x ==

===== Table: Supported Version Combinations for Audio Server 6.x and Other Cisco Unified MeetingPlace Components =====

{| border = 1 cellpadding="4" cellspacing="2"
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(4.7)'''

Also known as
Maintenance Release 4 (MR4)

Released: March 27, 2009

'''NOTE:''' Audio Server Release 6.0(4.4),

which was released on 12/12/08,
has been retired.

If you have Release 6.0(4.4),

upgrade to Release 6.0(4.7)
|
Directory Services 5.4(205.0)
|
December 16, 2008
|-
|
EMP 5.6.1.0.4
|
October 31, 2008
|-
|
Gateway SIM 5.2(0.80)
|
December 16, 2008
|-
|
H.323/SIP Gateway 5.3(1.61)
|
December 12, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(405.0)
* 5.4(109.0) 1 
|
* December 17, 2008
* July 3, 2007
|-
|
MCU 5.6(1.1.13)
|
October 31, 2008
|-
|
MeetingTime 6.0(4.6)
|
December 12, 2008
|-
|

Network Backup Gateway 5.3(0.12)
|

December 16, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0) 1
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(402.0)
|

December 16, 2008
|-
|

Video Administration 5.6(2.101)
|

December 16, 2008
|-
|

Video Integration 5.4(206.0)
|

December 16, 2008
|-
|

Web Conferencing:
* 6.0(517.0)
* 5.4(156.2) 2 
|

* December 17, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(3.5)'''

Also known as

Maintenance Release 3 (MR3)

Released May 28, 2008
|
Directory Services 5.4(114.0)
|
July 21, 2008
|-
|
EMP 5.5.2.0.2
|
June 2, 2008
|-
|
Gateway SIM 5.2(0.78)
|
June 2, 2008
|-
|
H.323/SIP Gateway 5.3(1.40)
|
June 2, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(205.0)
* 5.4(109.0) 1 
|
* June 2, 2008
* July 3, 2007
|-
|
MCU 5.5(0.0.54)
|
June 2, 2008
|-
|
MeetingTime 6.0(3.1)
|
June 2, 2008
|-
|

Network Backup Gateway 5.3(0.11)
|

June 2, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0) 1
|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(2.103)
|

June 2, 2008
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(417.0)
* 5.4(156.2) 2 
|

* June 2, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="18" valign="top"|'''6.0(2.13)'''

Also known as

Maintenance Release 2 (MR2)

Released January 31, 2008
|

Directory Services 5.4(108.0)
|

January 31, 2008
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.77)
|

January 31, 2008
|-
|

H.323/SIP Gateway 5.3(1.33)
|

January 31, 2008
|-
|

Jabber Integration 6.0(2.0)
|

May 31, 2007
|-
|

Language Pack 6.0(2.13)
|

January 31, 2008
|-
|

Lotus Notes Integration:
* 6.0(203.0)
* 5.4(109.0) 1 
|

* January 31, 2008
* July 3, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(2.4)
|

January 31, 2008
|-
|

Network Backup Gateway 5.3(0.10)
|

January 31, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0) 1
|

* January 31, 2008
* December 21, 2007
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(361.0)
* 5.4(156.2) 2
|

* January 31, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="17" valign="top"|'''6.0(1.11)'''

Also known as

Maintenance Release 1 (MR1)

Released September 7, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.74)
|

September 7, 2007
|-
|

H.323/SIP Gateway 5.3(1.29)
|

September 7, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(104.0)
|

September 7, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(1.4)
|

September 7, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(102.0)
|

September 7, 2007
|-
|

Outlook Integration 6.0(115.0)
|

September 7, 2007
|-
|

SMTP E-Mail Gateway 6.0(107.0)
|

September 7, 2007
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

September 7, 2007
|-
|

Web Conferencing

6.0(244.0)

5.4(156.2) 2
|

September 7, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="15" valign="top"|'''6.0(0.25)'''
Released May 31, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

Gateway SIM 5.2(0.71)
|

May 31, 2007
|-
|

H.323/SIP Gateway 5.3(1.8)
|

May 31, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(15.0)
|

May 31, 2007
|-
|

MeetingTime 6.0(0.23)
|

May 31, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(11.0)
|

May 31, 2007
|-
|

Outlook Integration 6.0(14.0)
|

May 31, 2007
|-
|

SMTP E-Mail Gateway 5.4(108)
|

March 30, 2007
|-
|

Video Administration 5.4(0.105)
|

March 30, 2007
|-
|

Video Integration 5.4(107.0)
|

March 30, 2007
|-
|

Web Conferencing

6.0(171.0)

5.4(156.2) 2 
|

May 31, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.

See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]

|-
|colspan="2"|Language pack appropriate for this release.
|-
|}

'''Footnote:'''

1: Requires Web Conferencing Release 5.4.(156.2).

2: This release is a hotfix and is only available by contacting Cisco TAC.

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:10:19Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]]

This document lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in release 6.x.

For upgrades, we recommend that you upgrade at the same time Audio Server and all other component software in use. Version combinations listed as supported in this document have been tested together. Although we attempt to maintain backward compatibility with new releases, it is not possible to test all version combinations. As a result, we cannot support version combinations that are not listed in this document.

If you upgrade Cisco Unified MeetingPlace components at different times, you do so at your own risk. If you call Cisco TAC with a problem, an engineer may require that you upgrade components to a supported combination if the versions are out of synchronization.

For components upgraded at different times, we recommend that you respect the logical dependency order among the Cisco Unified MeetingPlace components:
# Audio Server.
# Cisco Unified MeetingPlace components dependent on Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP Gateway, Directory Services, SMTP E-Mail Gateway.
# Cisco Unified MeetingPlace components dependent on Web Conferencing: Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace for Jabber, Video Integration.

'''Note: ''' Certain versions of some components have a hard requirement to be upgraded at the same time. Refer to the applicable readme file or release notes for each component to understand component dependencies before installing or upgrading.

To determine the version of the various software components, see [[Cisco Unified MeetingPlace, Release 6.x -- Determining the Software Version|Determining the Software Version]].

== Audio Server Version 6.x ==

===== Table: Supported Version Combinations for Audio Server 6.x and Other Cisco Unified MeetingPlace Components =====

{| border = 1 cellpadding="4" cellspacing="2"
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(4.7)'''

Also known as
Maintenance Release 4 (MR4)

Released: March 27, 2009

NOTE: Audio Server Release 6.0(4.4), which was

released on 12/12/08, has been retired.

If you have Release 6.0(4.4),

upgrade to Release 6.0(4.7)
|
Directory Services 5.4(205.0)
|
December 16, 2008
|-
|
EMP 5.6.1.0.4
|
October 31, 2008
|-
|
Gateway SIM 5.2(0.80)
|
December 16, 2008
|-
|
H.323/SIP Gateway 5.3(1.61)
|
December 12, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(405.0)
* 5.4(109.0) 1 
|
* December 17, 2008
* July 3, 2007
|-
|
MCU 5.6(1.1.13)
|
October 31, 2008
|-
|
MeetingTime 6.0(4.6)
|
December 12, 2008
|-
|

Network Backup Gateway 5.3(0.12)
|

December 16, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0) 1
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(402.0)
|

December 16, 2008
|-
|

Video Administration 5.6(2.101)
|

December 16, 2008
|-
|

Video Integration 5.4(206.0)
|

December 16, 2008
|-
|

Web Conferencing:
* 6.0(517.0)
* 5.4(156.2) 2 
|

* December 17, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(3.5)'''

Also known as

Maintenance Release 3 (MR3)

Released May 28, 2008
|
Directory Services 5.4(114.0)
|
July 21, 2008
|-
|
EMP 5.5.2.0.2
|
June 2, 2008
|-
|
Gateway SIM 5.2(0.78)
|
June 2, 2008
|-
|
H.323/SIP Gateway 5.3(1.40)
|
June 2, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(205.0)
* 5.4(109.0) 1 
|
* June 2, 2008
* July 3, 2007
|-
|
MCU 5.5(0.0.54)
|
June 2, 2008
|-
|
MeetingTime 6.0(3.1)
|
June 2, 2008
|-
|

Network Backup Gateway 5.3(0.11)
|

June 2, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0) 1
|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(2.103)
|

June 2, 2008
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(417.0)
* 5.4(156.2) 2 
|

* June 2, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="18" valign="top"|'''6.0(2.13)'''

Also known as

Maintenance Release 2 (MR2)

Released January 31, 2008
|

Directory Services 5.4(108.0)
|

January 31, 2008
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.77)
|

January 31, 2008
|-
|

H.323/SIP Gateway 5.3(1.33)
|

January 31, 2008
|-
|

Jabber Integration 6.0(2.0)
|

May 31, 2007
|-
|

Language Pack 6.0(2.13)
|

January 31, 2008
|-
|

Lotus Notes Integration:
* 6.0(203.0)
* 5.4(109.0) 1 
|

* January 31, 2008
* July 3, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(2.4)
|

January 31, 2008
|-
|

Network Backup Gateway 5.3(0.10)
|

January 31, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0) 1
|

* January 31, 2008
* December 21, 2007
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(361.0)
* 5.4(156.2) 2
|

* January 31, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="17" valign="top"|'''6.0(1.11)'''

Also known as

Maintenance Release 1 (MR1)

Released September 7, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.74)
|

September 7, 2007
|-
|

H.323/SIP Gateway 5.3(1.29)
|

September 7, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(104.0)
|

September 7, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(1.4)
|

September 7, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(102.0)
|

September 7, 2007
|-
|

Outlook Integration 6.0(115.0)
|

September 7, 2007
|-
|

SMTP E-Mail Gateway 6.0(107.0)
|

September 7, 2007
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

September 7, 2007
|-
|

Web Conferencing

6.0(244.0)

5.4(156.2) 2
|

September 7, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="15" valign="top"|'''6.0(0.25)'''
Released May 31, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

Gateway SIM 5.2(0.71)
|

May 31, 2007
|-
|

H.323/SIP Gateway 5.3(1.8)
|

May 31, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(15.0)
|

May 31, 2007
|-
|

MeetingTime 6.0(0.23)
|

May 31, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(11.0)
|

May 31, 2007
|-
|

Outlook Integration 6.0(14.0)
|

May 31, 2007
|-
|

SMTP E-Mail Gateway 5.4(108)
|

March 30, 2007
|-
|

Video Administration 5.4(0.105)
|

March 30, 2007
|-
|

Video Integration 5.4(107.0)
|

March 30, 2007
|-
|

Web Conferencing

6.0(171.0)

5.4(156.2) 2 
|

May 31, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.

See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]

|-
|colspan="2"|Language pack appropriate for this release.
|-
|}

'''Footnote:'''

1: Requires Web Conferencing Release 5.4.(156.2).

2: This release is a hotfix and is only available by contacting Cisco TAC.

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:09:21Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]]

This document lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in release 6.x.

For upgrades, we recommend that you upgrade at the same time Audio Server and all other component software in use. Version combinations listed as supported in this document have been tested together. Although we attempt to maintain backward compatibility with new releases, it is not possible to test all version combinations. As a result, we cannot support version combinations that are not listed in this document.

If you upgrade Cisco Unified MeetingPlace components at different times, you do so at your own risk. If you call Cisco TAC with a problem, an engineer may require that you upgrade components to a supported combination if the versions are out of synchronization.

For components upgraded at different times, we recommend that you respect the logical dependency order among the Cisco Unified MeetingPlace components:
# Audio Server.
# Cisco Unified MeetingPlace components dependent on Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP Gateway, Directory Services, SMTP E-Mail Gateway.
# Cisco Unified MeetingPlace components dependent on Web Conferencing: Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace for Jabber, Video Integration.

'''Note: ''' Certain versions of some components have a hard requirement to be upgraded at the same time. Refer to the applicable readme file or release notes for each component to understand component dependencies before installing or upgrading.

To determine the version of the various software components, see [[Cisco Unified MeetingPlace, Release 6.x -- Determining the Software Version|Determining the Software Version]].

== Audio Server Version 6.x ==

===== Table: Supported Version Combinations for Audio Server 6.x and Other Cisco Unified MeetingPlace Components =====

{| border = 1 cellpadding="4" cellspacing="2"
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(4.7)'''

Also known as
Maintenance Release 4 (MR4)

Released: March 27, 2009

NOTE: Audio Server Release 6.0(4.4),

which was released on 12/12/08,
has been retired. If you have

Release 6.0(4.4), upgrade to Release 6.0(4.7)
|
Directory Services 5.4(205.0)
|
December 16, 2008
|-
|
EMP 5.6.1.0.4
|
October 31, 2008
|-
|
Gateway SIM 5.2(0.80)
|
December 16, 2008
|-
|
H.323/SIP Gateway 5.3(1.61)
|
December 12, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(405.0)
* 5.4(109.0) 1 
|
* December 17, 2008
* July 3, 2007
|-
|
MCU 5.6(1.1.13)
|
October 31, 2008
|-
|
MeetingTime 6.0(4.6)
|
December 12, 2008
|-
|

Network Backup Gateway 5.3(0.12)
|

December 16, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0) 1
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(402.0)
|

December 16, 2008
|-
|

Video Administration 5.6(2.101)
|

December 16, 2008
|-
|

Video Integration 5.4(206.0)
|

December 16, 2008
|-
|

Web Conferencing:
* 6.0(517.0)
* 5.4(156.2) 2 
|

* December 17, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(3.5)'''

Also known as

Maintenance Release 3 (MR3)

Released May 28, 2008
|
Directory Services 5.4(114.0)
|
July 21, 2008
|-
|
EMP 5.5.2.0.2
|
June 2, 2008
|-
|
Gateway SIM 5.2(0.78)
|
June 2, 2008
|-
|
H.323/SIP Gateway 5.3(1.40)
|
June 2, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(205.0)
* 5.4(109.0) 1 
|
* June 2, 2008
* July 3, 2007
|-
|
MCU 5.5(0.0.54)
|
June 2, 2008
|-
|
MeetingTime 6.0(3.1)
|
June 2, 2008
|-
|

Network Backup Gateway 5.3(0.11)
|

June 2, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0) 1
|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(2.103)
|

June 2, 2008
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(417.0)
* 5.4(156.2) 2 
|

* June 2, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="18" valign="top"|'''6.0(2.13)'''

Also known as

Maintenance Release 2 (MR2)

Released January 31, 2008
|

Directory Services 5.4(108.0)
|

January 31, 2008
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.77)
|

January 31, 2008
|-
|

H.323/SIP Gateway 5.3(1.33)
|

January 31, 2008
|-
|

Jabber Integration 6.0(2.0)
|

May 31, 2007
|-
|

Language Pack 6.0(2.13)
|

January 31, 2008
|-
|

Lotus Notes Integration:
* 6.0(203.0)
* 5.4(109.0) 1 
|

* January 31, 2008
* July 3, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(2.4)
|

January 31, 2008
|-
|

Network Backup Gateway 5.3(0.10)
|

January 31, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0) 1
|

* January 31, 2008
* December 21, 2007
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(361.0)
* 5.4(156.2) 2
|

* January 31, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="17" valign="top"|'''6.0(1.11)'''

Also known as

Maintenance Release 1 (MR1)

Released September 7, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.74)
|

September 7, 2007
|-
|

H.323/SIP Gateway 5.3(1.29)
|

September 7, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(104.0)
|

September 7, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(1.4)
|

September 7, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(102.0)
|

September 7, 2007
|-
|

Outlook Integration 6.0(115.0)
|

September 7, 2007
|-
|

SMTP E-Mail Gateway 6.0(107.0)
|

September 7, 2007
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

September 7, 2007
|-
|

Web Conferencing

6.0(244.0)

5.4(156.2) 2
|

September 7, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="15" valign="top"|'''6.0(0.25)'''
Released May 31, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

Gateway SIM 5.2(0.71)
|

May 31, 2007
|-
|

H.323/SIP Gateway 5.3(1.8)
|

May 31, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(15.0)
|

May 31, 2007
|-
|

MeetingTime 6.0(0.23)
|

May 31, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(11.0)
|

May 31, 2007
|-
|

Outlook Integration 6.0(14.0)
|

May 31, 2007
|-
|

SMTP E-Mail Gateway 5.4(108)
|

March 30, 2007
|-
|

Video Administration 5.4(0.105)
|

March 30, 2007
|-
|

Video Integration 5.4(107.0)
|

March 30, 2007
|-
|

Web Conferencing

6.0(171.0)

5.4(156.2) 2 
|

May 31, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.

See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]

|-
|colspan="2"|Language pack appropriate for this release.
|-
|}

'''Footnote:'''

1: Requires Web Conferencing Release 5.4.(156.2).

2: This release is a hotfix and is only available by contacting Cisco TAC.

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-03-27T23:07:56Z

MeetingPlace Express Moderator:

[[Cisco Unified MeetingPlace, Release 6.x]]

This document lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in release 6.x.

For upgrades, we recommend that you upgrade at the same time Audio Server and all other component software in use. Version combinations listed as supported in this document have been tested together. Although we attempt to maintain backward compatibility with new releases, it is not possible to test all version combinations. As a result, we cannot support version combinations that are not listed in this document.

If you upgrade Cisco Unified MeetingPlace components at different times, you do so at your own risk. If you call Cisco TAC with a problem, an engineer may require that you upgrade components to a supported combination if the versions are out of synchronization.

For components upgraded at different times, we recommend that you respect the logical dependency order among the Cisco Unified MeetingPlace components:
# Audio Server.
# Cisco Unified MeetingPlace components dependent on Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP Gateway, Directory Services, SMTP E-Mail Gateway.
# Cisco Unified MeetingPlace components dependent on Web Conferencing: Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace for Jabber, Video Integration.

'''Note: ''' Certain versions of some components have a hard requirement to be upgraded at the same time. Refer to the applicable readme file or release notes for each component to understand component dependencies before installing or upgrading.

To determine the version of the various software components, see [[Cisco Unified MeetingPlace, Release 6.x -- Determining the Software Version|Determining the Software Version]].

== Audio Server Version 6.x ==

===== Table: Supported Version Combinations for Audio Server 6.x and Other Cisco Unified MeetingPlace Components =====

{| border = 1 cellpadding="4" cellspacing="2"
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(4.7)'''

Also known as
Maintenance Release 4 (MR4)

Released March 27, 2009

NOTE: Audio Server Release 6.0(4.4)
was released on 12/12/08 and has been
retired. If you have Release 6.0(4.4)
please upgrade to Release 6.0(4.7)
|
Directory Services 5.4(205.0)
|
December 16, 2008
|-
|
EMP 5.6.1.0.4
|
October 31, 2008
|-
|
Gateway SIM 5.2(0.80)
|
December 16, 2008
|-
|
H.323/SIP Gateway 5.3(1.61)
|
December 12, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(405.0)
* 5.4(109.0) 1 
|
* December 17, 2008
* July 3, 2007
|-
|
MCU 5.6(1.1.13)
|
October 31, 2008
|-
|
MeetingTime 6.0(4.6)
|
December 12, 2008
|-
|

Network Backup Gateway 5.3(0.12)
|

December 16, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0) 1
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(402.0)
|

December 16, 2008
|-
|

Video Administration 5.6(2.101)
|

December 16, 2008
|-
|

Video Integration 5.4(206.0)
|

December 16, 2008
|-
|

Web Conferencing:
* 6.0(517.0)
* 5.4(156.2) 2 
|

* December 17, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="19" valign="top"|'''6.0(3.5)'''

Also known as

Maintenance Release 3 (MR3)

Released May 28, 2008
|
Directory Services 5.4(114.0)
|
July 21, 2008
|-
|
EMP 5.5.2.0.2
|
June 2, 2008
|-
|
Gateway SIM 5.2(0.78)
|
June 2, 2008
|-
|
H.323/SIP Gateway 5.3(1.40)
|
June 2, 2008
|-
|
Jabber Integration 6.0(2.0)
|
May 31, 2007
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration:
* 6.0(205.0)
* 5.4(109.0) 1 
|
* June 2, 2008
* July 3, 2007
|-
|
MCU 5.5(0.0.54)
|
June 2, 2008
|-
|
MeetingTime 6.0(3.1)
|
June 2, 2008
|-
|

Network Backup Gateway 5.3(0.11)
|

June 2, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0) 1
|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0
|

June 2, 2008
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(2.103)
|

June 2, 2008
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(417.0)
* 5.4(156.2) 2 
|

* June 2, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="2">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="18" valign="top"|'''6.0(2.13)'''

Also known as

Maintenance Release 2 (MR2)

Released January 31, 2008
|

Directory Services 5.4(108.0)
|

January 31, 2008
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.77)
|

January 31, 2008
|-
|

H.323/SIP Gateway 5.3(1.33)
|

January 31, 2008
|-
|

Jabber Integration 6.0(2.0)
|

May 31, 2007
|-
|

Language Pack 6.0(2.13)
|

January 31, 2008
|-
|

Lotus Notes Integration:
* 6.0(203.0)
* 5.4(109.0) 1 
|

* January 31, 2008
* July 3, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(2.4)
|

January 31, 2008
|-
|

Network Backup Gateway 5.3(0.10)
|

January 31, 2008
|-
|

Office Communicator Integration 6.0(201.0)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0) 1
|

* January 31, 2008
* December 21, 2007
|-
|

SMTP E-Mail Gateway 6.0(202.0)
|

January 31, 2008
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

July 26, 2007
|-
|

Web Conferencing:
* 6.0(361.0)
* 5.4(156.2) 2
|

* January 31, 2008
* September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]] for Cisco Security Agent.
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="17" valign="top"|'''6.0(1.11)'''

Also known as

Maintenance Release 1 (MR1)

Released September 7, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

EMP 5.1.1.0.15
|

July 26, 2007
|-
|

Gateway SIM 5.2(0.74)
|

September 7, 2007
|-
|

H.323/SIP Gateway 5.3(1.29)
|

September 7, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(104.0)
|

September 7, 2007
|-
|

MCU 5.1(2.2)
|

July 26, 2007
|-
|

MeetingTime 6.0(1.4)
|

September 7, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(102.0)
|

September 7, 2007
|-
|

Outlook Integration 6.0(115.0)
|

September 7, 2007
|-
|

SMTP E-Mail Gateway 6.0(107.0)
|

September 7, 2007
|-
|

Video Administration 5.4(0.112)
|

October 22, 2007
|-
|

Video Integration 5.4(204.0)
|

September 7, 2007
|-
|

Web Conferencing

6.0(244.0)

5.4(156.2) 2
|

September 7, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]
|-
|colspan="2"|Language pack appropriate for this release.
|-
|td colspan="3"|
|-
!style="background:#ffdead;"|Audio Server Version
!style="background:#ffdead;"|Component and Supported Version
!style="background:#ffdead;"|Component Release Date
|-
|rowspan="15" valign="top"|'''6.0(0.25)'''
Released May 31, 2007
|

Directory Services 5.4(104)
|

March 30, 2007
|-
|

Gateway SIM 5.2(0.71)
|

May 31, 2007
|-
|

H.323/SIP Gateway 5.3(1.8)
|

May 31, 2007
|-
|

Jabber Integration 6.0(102.0)
|

May 31, 2007
|-
|

Lotus Notes Integration 6.0(15.0)
|

May 31, 2007
|-
|

MeetingTime 6.0(0.23)
|

May 31, 2007
|-
|

Network Backup Gateway 5.3(0.7)
|

March 30, 2007
|-
|

Office Communicator Integration 6.0(11.0)
|

May 31, 2007
|-
|

Outlook Integration 6.0(14.0)
|

May 31, 2007
|-
|

SMTP E-Mail Gateway 5.4(108)
|

March 30, 2007
|-
|

Video Administration 5.4(0.105)
|

March 30, 2007
|-
|

Video Integration 5.4(107.0)
|

March 30, 2007
|-
|

Web Conferencing

6.0(171.0)

5.4(156.2) 2 
|

May 31, 2007

September 7, 2007
|-
|<td colspan="2" rowspan="1">|Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.

See [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements and Supported Software|Requirements and Supported Software]]

|-
|colspan="2"|Language pack appropriate for this release.
|-
|}

'''Footnote:'''

1: Requires Web Conferencing Release 5.4.(156.2).

2: This release is a hotfix and is only available by contacting Cisco TAC.

Cisco Unified MeetingPlace Express, Release 2.x

2009-03-24T16:43:48Z

MeetingPlace Express Moderator:

This DocWiki contains information about the following releases of Cisco Unified MeetingPlace Express, Release 2.x:

* Cisco Unified MeetingPlace Express -- Provides advanced scheduled and reservationless voice, web, and video meeting features, including the option to integrate with Microsoft Outlook.

* Cisco Unified MeetingPlace Express VT -- Provides ad hoc voice, video, and web conferencing capabilities. Ad hoc conferences are initiated through the end-user interfaces of products other than Cisco Unified MeetingPlace Express. For example, you can initiate either a voice-only or a voice-and-video ad hoc conference by using the "Meet-Me" button or the "Conf" button on Cisco Unified IP Phones that are registered to Cisco Unified Communications Manager (formerly called Cisco Unified CallManager). You can also initiate voice, video, and web conferences through Cisco Unified Personal Communicator.

== Notification of New Releases ==

See the [[Cisco Unified MeetingPlace, Release 2.x -- Notifications|notification page]] to learn how to be notified whenever Cisco Unified MeetingPlace Express, Release 2.x is updated.

== System Documentation ==

* For information about Cisco Unified MeetingPlace Express Release 2.x, including system requirements, see the Release Notes here: http://www.cisco.com/en/US/products/ps6533/prod_release_notes_list.html

* For a roadmap of all the documentation for Cisco Unified MeetingPlace Express Release 2.x, see the documentation roadmap here: http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/b_docmap.html

* For licensing information for Cisco Unified MeetingPlace Express Release 2.x, see the this file: http://cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/mpx_licensing_information.html

== Installation and Upgrades ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Installing Cisco Unified MeetingPlace Express|Installing Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Upgrading Cisco Unified MeetingPlace Express from an Earlier Release|Upgrading Cisco Unified MeetingPlace Express from an Earlier Release]]

== Configuration and Maintenance Tasks ==

* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Getting_Started_in_the_Cisco_Unified_MeetingPlace_Express_Administration_Center|Getting Started]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Logging in to the Cisco Unified MeetingPlace Express Application as a System Administrator|Logging in to Cisco Unified MeetingPlace Express Release 2.x as an administrator]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_System_Administrator_Responsibilities_for_Cisco_Unified_MeetingPlace_Express|System Administrator Responsibilities]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_Common_Administrative_Tasks|About Common Administrative Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring_Call_Control|Configuring Call Control]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express#Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express|Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring Security Features for Cisco Unified MeetingPlace Express#Configuring Security Features for Cisco Unified MeetingPlace Express|Configuring Security Features for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Customizing the Cisco Unified MeetingPlace Express End-User Interfaces|Customizing the Cisco Unified MeetingPlace Express End-User Interfaces]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Integration Information|Integration Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Maintaining the Cisco Unified MeetingPlace Express System|Maintenance Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Running Reports and Exporting Data from Cisco Unified MeetingPlace Express|Running Reports]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Licenses|License Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Monitoring Cisco Unified MeetingPlace Express|Monitoring Cisco Unified MeetingPlace Express]]

== Troubleshooting Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Troubleshooting_Cisco_Unified_MeetingPlace_Express|Troubleshooting]]

== Reference Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Exception Codes, Module Numbers, and File Locations Used in Cisco Unified MeetingPlace Express|Reference Information]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Administration_Center_Page_References_for_Cisco_Unified_MeetingPlace_Express|Page References]]

==Documentation for End-Users==

In English: http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

In other languages: http://www.cisco.com/en/US/products/ps6533/tsd_products_support_translated_end_user_guides_list.html

[[Category:Conferencing]]

Cisco Unified MeetingPlace Express, Release 2.x

2009-03-24T16:43:14Z

MeetingPlace Express Moderator:

This DocWiki contains information about the following releases of Cisco Unified MeetingPlace Express, Release 2.x:

* Cisco Unified MeetingPlace Express -- Provides advanced scheduled and reservationless voice, web, and video meeting features, including the option to integrate with Microsoft Outlook.

* Cisco Unified MeetingPlace Express VT -- Provides ad hoc voice, video, and web conferencing capabilities. Ad hoc conferences are initiated through the end-user interfaces of products other than Cisco Unified MeetingPlace Express. For example, you can initiate either a voice-only or a voice-and-video ad hoc conference by using the "Meet-Me" button or the "Conf" button on Cisco Unified IP Phones that are registered to Cisco Unified Communications Manager (formerly called Cisco Unified CallManager). You can also initiate voice, video, and web conferences through Cisco Unified Personal Communicator.

== Notification of New Releases ==

See the [[Cisco Unified MeetingPlace, Release 2.x -- Notifications|notification page]] to learn how to be notified whenever Cisco Unified MeetingPlace Express, Release 2.x is updated.

== System Documentation ==

* For information about Cisco Unified MeetingPlace Express Release 2.x, including system requirements, see the Release Notes here: http://www.cisco.com/en/US/products/ps6533/prod_release_notes_list.html

* For a roadmap of all the documentation for Cisco Unified MeetingPlace Express Release 2.x, see the documentation roadmap here: http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/b_docmap.html

* For licensing information for Cisco Unified MeetingPlace Express Release 2.x, see the this file: http://cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/mpx_licensing_information.html

== Installation and Upgrades ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Installing Cisco Unified MeetingPlace Express|Installing Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Upgrading Cisco Unified MeetingPlace Express from an Earlier Release|Upgrading Cisco Unified MeetingPlace Express from an Earlier Release]]

== Configuration and Maintenance Tasks ==

* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Getting_Started_in_the_Cisco_Unified_MeetingPlace_Express_Administration_Center|Getting Started]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Logging in to the Cisco Unified MeetingPlace Express Application as a System Administrator|Logging in to Cisco Unified MeetingPlace Express Release 2.x as an administrator]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_System_Administrator_Responsibilities_for_Cisco_Unified_MeetingPlace_Express|System Administrator Responsibilities]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_Common_Administrative_Tasks|About Common Administrative Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring_Call_Control|Configuring Call Control]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express#Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express|Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring Security Features for Cisco Unified MeetingPlace Express#Configuring Security Features for Cisco Unified MeetingPlace Express|Configuring Security Features for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Customizing the Cisco Unified MeetingPlace Express End-User Interfaces|Customizing the Cisco Unified MeetingPlace Express End-User Interfaces]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Integration Information|Integration Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Maintaining the Cisco Unified MeetingPlace Express System|Maintenance Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Running Reports and Exporting Data from Cisco Unified MeetingPlace Express|Running Reports]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Licenses|License Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Monitoring Cisco Unified MeetingPlace Express|Monitoring Cisco Unified MeetingPlace Express]]

== Troubleshooting Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Troubleshooting_Cisco_Unified_MeetingPlace_Express|Troubleshooting]]

== Reference Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Exception Codes, Module Numbers, and File Locations Used in Cisco Unified MeetingPlace Express|Reference Information]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Administration_Center_Page_References_for_Cisco_Unified_MeetingPlace_Express|Page References]]

==Documentation for End-Users==

In English:
* http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

In other languages:
* http://www.cisco.com/en/US/products/ps6533/tsd_products_support_translated_end_user_guides_list.html

[[Category:Conferencing]]

Cisco Unified MeetingPlace Express, Release 2.x

2009-03-24T16:40:52Z

MeetingPlace Express Moderator:

This DocWiki contains information about the following releases of Cisco Unified MeetingPlace Express, Release 2.x:

* Cisco Unified MeetingPlace Express -— Provides scheduled and reservationless voice, web, and video conferencing.

* Cisco Unified MeetingPlace Express VT -— Provides ad hoc voice, web, and video conferencing.

== Notification of New Releases ==

See the [[Cisco Unified MeetingPlace, Release 2.x -- Notifications|notification page]] to learn how to be notified whenever Cisco Unified MeetingPlace Express, Release 2.x is updated.

== System Documentation ==

* For information about Cisco Unified MeetingPlace Express Release 2.x, including system requirements, see the Release Notes here: http://www.cisco.com/en/US/products/ps6533/prod_release_notes_list.html

* For a roadmap of all the documentation for Cisco Unified MeetingPlace Express Release 2.x, see the documentation roadmap here: http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/b_docmap.html

* For licensing information for Cisco Unified MeetingPlace Express Release 2.x, see the this file: http://cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/mpx_licensing_information.html

== Installation and Upgrades ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Installing Cisco Unified MeetingPlace Express|Installing Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Upgrading Cisco Unified MeetingPlace Express from an Earlier Release|Upgrading Cisco Unified MeetingPlace Express from an Earlier Release]]

== Configuration and Maintenance Tasks ==

* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Getting_Started_in_the_Cisco_Unified_MeetingPlace_Express_Administration_Center|Getting Started]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Logging in to the Cisco Unified MeetingPlace Express Application as a System Administrator|Logging in to Cisco Unified MeetingPlace Express Release 2.x as an administrator]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_System_Administrator_Responsibilities_for_Cisco_Unified_MeetingPlace_Express|System Administrator Responsibilities]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_Common_Administrative_Tasks|About Common Administrative Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring_Call_Control|Configuring Call Control]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express#Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express|Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring Security Features for Cisco Unified MeetingPlace Express#Configuring Security Features for Cisco Unified MeetingPlace Express|Configuring Security Features for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Customizing the Cisco Unified MeetingPlace Express End-User Interfaces|Customizing the Cisco Unified MeetingPlace Express End-User Interfaces]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Integration Information|Integration Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Maintaining the Cisco Unified MeetingPlace Express System|Maintenance Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Running Reports and Exporting Data from Cisco Unified MeetingPlace Express|Running Reports]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Licenses|License Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Monitoring Cisco Unified MeetingPlace Express|Monitoring Cisco Unified MeetingPlace Express]]

== Troubleshooting Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Troubleshooting_Cisco_Unified_MeetingPlace_Express|Troubleshooting]]

== Reference Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Exception Codes, Module Numbers, and File Locations Used in Cisco Unified MeetingPlace Express|Reference Information]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Administration_Center_Page_References_for_Cisco_Unified_MeetingPlace_Express|Page References]]

==Documentation for End-Users==

In English:
* http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

In other languages:
* http://www.cisco.com/en/US/products/ps6533/tsd_products_support_translated_end_user_guides_list.html

[[Category:Conferencing]]

Cisco Unified MeetingPlace Express, Release 2.x -- Notifications

2009-03-24T16:34:39Z

MeetingPlace Express Moderator: New page: '''Return to the main page for Cisco Unified MeetingPlace Express, Release 2.x:''' Cisco Unified MeetingPlace Express, Release 2.x To ensure that you always have the most recent ...

Cisco Unified MeetingPlace Express, Release 2.x

2009-03-24T16:33:10Z

MeetingPlace Express Moderator:

== Notification of New Releases ==

See the [[Cisco Unified MeetingPlace, Release 2.x -- Notifications|notification page]] to learn how to be notified whenever Cisco Unified MeetingPlace Express, Release 2.x is updated.

== System Documentation ==

* For information about Cisco Unified MeetingPlace Express Release 2.x, including system requirements, see the Release Notes here: http://www.cisco.com/en/US/products/ps6533/prod_release_notes_list.html

* For a roadmap of all the documentation for Cisco Unified MeetingPlace Express Release 2.x, see the documentation roadmap here: http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/b_docmap.html

* For licensing information for Cisco Unified MeetingPlace Express Release 2.x, see the this file: http://cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/roadmap/mpx_licensing_information.html

== Installation and Upgrades ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Installing Cisco Unified MeetingPlace Express|Installing Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Upgrading Cisco Unified MeetingPlace Express from an Earlier Release|Upgrading Cisco Unified MeetingPlace Express from an Earlier Release]]

== Configuration and Maintenance Tasks ==

* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Getting_Started_in_the_Cisco_Unified_MeetingPlace_Express_Administration_Center|Getting Started]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Logging in to the Cisco Unified MeetingPlace Express Application as a System Administrator|Logging in to Cisco Unified MeetingPlace Express Release 2.x as an administrator]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_System_Administrator_Responsibilities_for_Cisco_Unified_MeetingPlace_Express|System Administrator Responsibilities]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_About_Common_Administrative_Tasks|About Common Administrative Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring_Call_Control|Configuring Call Control]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express#Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express|Configuring SSL and Managing Certificates for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Configuring Security Features for Cisco Unified MeetingPlace Express#Configuring Security Features for Cisco Unified MeetingPlace Express|Configuring Security Features for Cisco Unified MeetingPlace Express]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Customizing the Cisco Unified MeetingPlace Express End-User Interfaces|Customizing the Cisco Unified MeetingPlace Express End-User Interfaces]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Integration Information|Integration Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Maintaining the Cisco Unified MeetingPlace Express System|Maintenance Tasks]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Running Reports and Exporting Data from Cisco Unified MeetingPlace Express|Running Reports]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- About Licenses|License Information]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Monitoring Cisco Unified MeetingPlace Express|Monitoring Cisco Unified MeetingPlace Express]]

== Troubleshooting Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Troubleshooting_Cisco_Unified_MeetingPlace_Express|Troubleshooting]]

== Reference Information ==

* [[Cisco Unified MeetingPlace Express, Release 2.x -- Exception Codes, Module Numbers, and File Locations Used in Cisco Unified MeetingPlace Express|Reference Information]]
* [[Cisco_Unified_MeetingPlace_Express%2C_Release_2.x_--_Administration_Center_Page_References_for_Cisco_Unified_MeetingPlace_Express|Page References]]

==Documentation for End-Users==

In English:
* http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

In other languages:
* http://www.cisco.com/en/US/products/ps6533/tsd_products_support_translated_end_user_guides_list.html

[[Category:Conferencing]]

Cisco Unified MeetingPlace, Release 7.0

2009-03-23T22:33:36Z

MeetingPlace Express Moderator:

Cisco Unified MeetingPlace provides a rich-media conferencing solution that includes the following:

* Voice, web, and video-conferencing capabilities

* Centralized access

* Real-time collaboration

* Integrated-network security that uses the existing telephony or IP-based infrastructure of your organization

== Notification of New Releases ==

See the [[Cisco Unified MeetingPlace, Release 7.0 -- Notifications|notification page]] to learn how to be notified whenever Cisco Unified MeetingPlace, Release 7.0 is updated.

== Documentation for Administrators ==

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Component Compatibility Matrix|Compatibility Matrix]]''' -- Lists the components (and their release numbers) that are compatible with the Cisco Unified MeetingPlace Application Server Release 7.0.1 and 7.0.2 (Maintenance Release 1).

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Video Endpoint Compatibility|Video Endpoint Compatibility]]''' -- Provides compatibility information between Cisco Unified MeetingPlace Release 7.0 and various video terminals when using Cisco Unified Communications Manager Release 6.1(2) or higher.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- System Requirements|System Requirements]]''' -- Lists the requirements for Cisco Unified MeetingPlace, Release 7.0, including network requirements, hardware requirements, software requirements, end-user requirements for Web Conferencing, integration requirements, and migration requirements.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Planning Your Deployment|Planning Your Deployment]]''' -- Contains information to help you plan the installation of your Cisco Unified MeetingPlace Release 7.0 system.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Installation|Installation]]''' -- Includes information about how to install Cisco Unified MeetingPlace, Release 7.0.1 and Release 7.0.2 (Maintenance Release 1), as well as information about how to upgrade to MR1 and information about migrating from Cisco Unified MeetingPlace, Release 6.0 to Release 7.0.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]''' -- Describes how to configure your system, including quick start configurations, basic configuration, Web Server configuration, call configuration, Media Server configuration, security configuration, advanced configuration, MeetingPlace Conference Manager configuration, and maintenance and monitoring tasks.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Integration|Integration]]''' -- Lists information for Microsoft integrations (Microsoft Outlook and Microsoft Office Communicator), IBM Lotus integrations (IBM Lotus Notes, IBM Lotus Sametime Instant Messaging, and IBM Lotus Sametime Web Conference), and Cisco integrations (Cisco WebEx, Cisco Unified IP Phone, Cisco Unified Personal Communicator, Cisco Unified Communications Manager, Cisco Unity Connection, and Jabber.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Troubleshooting|Troubleshooting]]''' -- Contains troubleshooting information for Cisco Unified MeetingPlace, Release 7.0.

* '''[[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information|Reference Information]]''' -- Contains reference information including CLI commands, page references, and other helpful information.

* '''Release Notes''' -- http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html

== Documentation for End Users ==

End User Guides: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html

Translated End User Guides: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/tsd_products_support_translated_end_user_guides_list.html

== Information about the DocWiki ==

The first time that we release documentation for a major release (such as Cisco Unified MeetingPlace, Release 7.0), we release it in HTML onto Cisco.com. We then convert the administration documentation (except for Release Notes) into DocWiki format. We do not convert end-user documentation to DocWiki format.

All updates to the documentation will then occur on the DocWiki only. The original HTML documents on Cisco.com are not updated unless there is another major release of the product. For minor and maintenance releases, we only update the documentation on the DocWiki and not the HTML files or the online help within the application.

=== Who Can Update the Documentation on the DocWiki? ===

One advantage of the DocWiki is that anyone with a Cisco.com user ID and password (so Cisco employees, contractors, and certain customers) can update the documentation on the DocWiki. This helps to promote collaboration.

=== How Do You Update the DocWiki? ===

Updating the DocWiki is easy!

===== Before You Begin =====

Make sure that you have a Cisco.com user ID and password.

===== Procedure =====

# Click '''log in''' in the top right corner of this DocWiki.
# Enter your Cisco.com user ID and password.
# Navigate to the page that you want to update.
# On the top of the page, click the '''edit''' tab.
#: '''NOTE:''' We do not recommend clicking '''[edit]''' on the side of the page.
#: You are now in editing mode.
# Make changes.
# At the bottom of the page, in the box called "Summary" enter a short description of your changes or why you are making the changes.
# Click '''Save page'''.

The system sends a notification of the change to the documentation team. The documentation team reviews all DocWiki changes to make sure that they follow Cisco guidelines.

If you have any comments or questions about the DocWiki or Cisco Unified MeetingPlace, Release 7.0, contact the Cisco Unified MeetingPlace documentation team at docwiki-meetingplaceexpress-moderator@cisco.com.