DocWiki - User contributions [en]

Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server

2012-08-16T04:05:35Z

Dunn: /* End-User Experience During Meeting Console Failover */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.1]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.1 -- Planning Your Deployment|Planning Your Deployment]]

Load Balancing in Cisco Unified MeetingPlace Web Conferencing service is achieved when multiple Cisco Unified MeetingPlace Web Servers setup as logical cluster to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support.

When configured appropriately with remote database source and storage, the clustered capabilities can also provide for continuity of service for web conference meetings in progress if one of the clustered Cisco Unified MeetingPlace Web servers becomes unavailable or unreachable. The user experience will see an interruption for participants homed to the unavailable/unreachable Web Server node, and can attempt reconnect to the meeting.

For operations purpose an administrator can view the amount of web-conferencing load per Web Server from the Web Server administrative page. This information is displayed only on internal Web Servers.

We recommend that you load balance the Web Conferencing portion of your Cisco Unified MeetingPlace system by using clusters. In a Cisco Unified MeetingPlace load-balancing Web Server cluster, all users must enter the Cisco Unified MeetingPlace system through a designated Cisco Unified MeetingPlace Web Server. In load-balancing Web Server cluster deployments, only the designated Cisco Unified MeetingPlace Web Server needs to be configured for the chosen authentication method. All other Web Servers in the cluster use the default authentication method-MeetingPlace Web Form Authentication. If, however, you want to configure other Web Servers in the cluster to use the same authentication method as a failover strategy, you can. Depending on the type of authentication method used though, this configuration can result in undesirable SSO behaviors.

For example, if you configure HTTP Basic Authentication or Windows Integrated Authentication, Cisco Unified MeetingPlace will prompt users for login credentials each time there is a Web Server redirect. This is because you are altering the hostname in the authentication configuration each time you redirect traffic to an active Web Server through a DNS change. If you configure LDAP or MeetingPlace authentication, users will not be prompted again for login credentials during a web conferencing redirect.

Use the information in this section to determine the load balancing configuration you want for the Web Conferencing portion of your Cisco Unified MeetingPlace system.

== Understanding How the Cisco Unified MeetingPlace Application Servers and Web Servers Communicate ==

The Cisco Unified MeetingPlace Replication Service automatically synchronizes the local Web Server database with that of the Cisco Unified MeetingPlace Application Server to update meetings, user profiles, and user group information. The following occurs by default:

* Synchronization occurs every 60 seconds.

* The User Profile Update Interval updates every 20 days.

* The Group Update Interval updates every 20 days.

* Meeting information updates every 60 seconds.

The Replication Service copies attachments and recordings from the Cisco Unified MeetingPlace Application Server and stores the replicated files on the Cisco Unified MeetingPlace Web Server. Pointers to these files are then created in the database. The Replication Service downloads voice files in their native Cisco Unified MeetingPlace voice (.mp4) format. After voice files are downloaded, the Replication Service queues jobs for conversion by the Audio Service.

The Replication Service also replicates video terminal user profile information from the Application Server. By default, this replication occurs every 7 days.

In the event of a system failure, you can manually invoke the Replication Service update and purge operations. Allow up to 20 minutes for any changes made to the Replication Service to take effect. For information on how to invoke the Replication Service, see the "How to Update Meetings and User Profiles" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

== Web Conferencing Clusters ==

'''Restriction:''' When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

With Cisco Unified MeetingPlace, you can configure to have an internal and an external Web Server cluster simultaneously. The cluster can have up to three (3) Web Servers. We recommend deploying "remote" SQL 2000 or 2005 customer provided systems. Each web cluster must use its own remote SQL, the SQL cannot be shared.

'''Internal cluster'''-Places all Web Servers behind the firewall inside the private corporate network. Typically, all Web Servers in an internal cluster display the full-access Cisco Unified MeetingPlace interface.

'''External cluster'''-Places all Web Servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all Web Servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace interface.

Cisco Unified MeetingPlace Web Servers use a SQL database to store profile and meeting information. When deploying Cisco Unified MeetingPlace Web Server clusters, the internal and external clusters must use separate SQL databases; however, the two databases must have identical Globally Unique Identifiers (GUIDS). It is recommended for high availability, the SQL database instance for a cluster is installed and configured on a separate server. For more information about configuring Cisco Unified MeetingPlace Web Servers for failover, see the "Application Server Failover" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Load balancing does not affect shared storage locations. All servers in a cluster use the same shared storage location.

Web conferencing supports three potential load balancing configurations, as shown in [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: One Cluster Configuration|Figure: One Cluster Configuration]], [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: Internal and External Clusters of Web Servers|Figure: Mixed Configuration: Internal and External Clusters of Web Servers]], and [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers|Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers]].

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cisco Unified MeetingPlace Web Server cluster-This can be an internal cluster or external cluster.
|-
|
3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Internal cluster of Web Servers.
|-
|
3
|

SQL Server-All Web Servers in the internal cluster must connect to the same SQL Server.
|
4
|

External cluster of Web Servers.
|-
|
5
|

SQL Server-All Web Servers in the external cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cluster of Web Servers-This can be an internal cluster or an external cluster.
|-
|
3
|

SQL Server-All Web Servers in a cluster must connect to the same SQL Server.
|
4
|

Single Web Server-This can be an internal or external web server.
|-
|
5
|

SQL Server-The single Web Server must connect to a separate SQL Server.
|
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Web Server comprises two separate load balancing components: the original server and the second server. Meetings are hosted on the original server. Participants connect to the second server when joining a meeting. These components interact to provide load balancing and failover capability as follows:

* When a meeting starts, the designated Web Server (the Web Server that is listed in the meeting notification) assigns a primary and backup original server to the meeting room based on the current active meeting load.

* As participants join the meeting, they are load balanced across the second servers in the cluster based on the number of participants currently connected to each second server at that time. The second server internally makes a connection to the original server that is hosting the meeting.

* Each client is given the primary and backup original server information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Web Servers. Meetings are spread across the three original servers in the cluster based on the meeting load on each. Participants are spread across the three second servers based on the participant load on each. Note that participants are not necessarily connected to the second server that corresponds to the original Web Server hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web meeting by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conferencing home page. When the first meeting participant attempts to join the web meeting, the system determines if the meeting should be held on an internal Web Server or an external Web Server by checking the "Allow External Web Participants" parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

"Allow External Web Participants" is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the internal cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any internal Web Server when they join the web meeting.
|-
|

"Allow External Web Participants" is set to Yes
|

This meeting is accessible to external attendees; that is, participants attending from outside the firewall.

If the first attendee attempts to join the web meeting from an external Web Server, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any external Web Server when they join the web meeting.

If the first attendee attempts to join the web meeting from an internal Web Server, Cisco Unified MeetingPlace determines if it has an associated external Web Server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace redirects the meeting to that external server. Web Server, the designated Cisco Unified MeetingPlace external Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This Web Server (original server) now owns (hosts) the meeting. Subsequent attendees may be directed to any external Web Server (second server) when they join the web meeting
* If Cisco Unified MeetingPlace does not find an entry in the DMZ Web Server field, the system redirects the meeting to the least loaded internal Web Server. The system directs all subsequent meeting participants to an internal Web Server for their web meeting.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external Web Server.

External users can join only external meetings on external Web Servers.

== Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System ==

To ensure a robust system with operational redundancy, we recommend that your Web Conferencing deployment contain the following:

* An internal web cluster (with 2 or 3 Cisco Unified MeetingPlace Web Servers)

* An external web cluster (with 2 or 3 Cisco Unified MeetingPlace Web Servers)

* A dedicated remote SQL Server system for each Cisco Unified MeetingPlace Web Sever cluster (one for Internal cluster, one for External cluster)

* Remote storage location (Microsoft NetBIOS over TCP/IP) with an appropriately sized RAID array and a comprehensive backup policy

== End-User Experience During Meeting Console Failure and Recovery ==

The Cisco Unified MeetingPlace Web Server sends the assigned primary and backup second server information to each client when the client first connects to a web conference meeting.

When a Cisco Unified MeetingPlace Web Server service failure occurs on a system that is configured for Load Balancing, users experience the following behavior:

# The Web Server to which the participant is connected stops responding, stops updating (due to, for example, the Web Server hardware failure, or the Web Conferencing services fails to respond).
# Users who are connected on that Web Server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the participant to the server. If this attempt fails, the meeting console client attempts to connect, or can be prompted to attempt connect, to the second server designated as the backup for that meeting.

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

Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server

2012-08-16T03:56:17Z

Dunn: /* Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.1]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.1 -- Planning Your Deployment|Planning Your Deployment]]

Load Balancing in Cisco Unified MeetingPlace Web Conferencing service is achieved when multiple Cisco Unified MeetingPlace Web Servers setup as logical cluster to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support.

When configured appropriately with remote database source and storage, the clustered capabilities can also provide for continuity of service for web conference meetings in progress if one of the clustered Cisco Unified MeetingPlace Web servers becomes unavailable or unreachable. The user experience will see an interruption for participants homed to the unavailable/unreachable Web Server node, and can attempt reconnect to the meeting.

For operations purpose an administrator can view the amount of web-conferencing load per Web Server from the Web Server administrative page. This information is displayed only on internal Web Servers.

We recommend that you load balance the Web Conferencing portion of your Cisco Unified MeetingPlace system by using clusters. In a Cisco Unified MeetingPlace load-balancing Web Server cluster, all users must enter the Cisco Unified MeetingPlace system through a designated Cisco Unified MeetingPlace Web Server. In load-balancing Web Server cluster deployments, only the designated Cisco Unified MeetingPlace Web Server needs to be configured for the chosen authentication method. All other Web Servers in the cluster use the default authentication method-MeetingPlace Web Form Authentication. If, however, you want to configure other Web Servers in the cluster to use the same authentication method as a failover strategy, you can. Depending on the type of authentication method used though, this configuration can result in undesirable SSO behaviors.

For example, if you configure HTTP Basic Authentication or Windows Integrated Authentication, Cisco Unified MeetingPlace will prompt users for login credentials each time there is a Web Server redirect. This is because you are altering the hostname in the authentication configuration each time you redirect traffic to an active Web Server through a DNS change. If you configure LDAP or MeetingPlace authentication, users will not be prompted again for login credentials during a web conferencing redirect.

Use the information in this section to determine the load balancing configuration you want for the Web Conferencing portion of your Cisco Unified MeetingPlace system.

== Understanding How the Cisco Unified MeetingPlace Application Servers and Web Servers Communicate ==

The Cisco Unified MeetingPlace Replication Service automatically synchronizes the local Web Server database with that of the Cisco Unified MeetingPlace Application Server to update meetings, user profiles, and user group information. The following occurs by default:

* Synchronization occurs every 60 seconds.

* The User Profile Update Interval updates every 20 days.

* The Group Update Interval updates every 20 days.

* Meeting information updates every 60 seconds.

The Replication Service copies attachments and recordings from the Cisco Unified MeetingPlace Application Server and stores the replicated files on the Cisco Unified MeetingPlace Web Server. Pointers to these files are then created in the database. The Replication Service downloads voice files in their native Cisco Unified MeetingPlace voice (.mp4) format. After voice files are downloaded, the Replication Service queues jobs for conversion by the Audio Service.

The Replication Service also replicates video terminal user profile information from the Application Server. By default, this replication occurs every 7 days.

In the event of a system failure, you can manually invoke the Replication Service update and purge operations. Allow up to 20 minutes for any changes made to the Replication Service to take effect. For information on how to invoke the Replication Service, see the "How to Update Meetings and User Profiles" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

== Web Conferencing Clusters ==

'''Restriction:''' When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

With Cisco Unified MeetingPlace, you can configure to have an internal and an external Web Server cluster simultaneously. The cluster can have up to three (3) Web Servers. We recommend deploying "remote" SQL 2000 or 2005 customer provided systems. Each web cluster must use its own remote SQL, the SQL cannot be shared.

'''Internal cluster'''-Places all Web Servers behind the firewall inside the private corporate network. Typically, all Web Servers in an internal cluster display the full-access Cisco Unified MeetingPlace interface.

'''External cluster'''-Places all Web Servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all Web Servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace interface.

Cisco Unified MeetingPlace Web Servers use a SQL database to store profile and meeting information. When deploying Cisco Unified MeetingPlace Web Server clusters, the internal and external clusters must use separate SQL databases; however, the two databases must have identical Globally Unique Identifiers (GUIDS). It is recommended for high availability, the SQL database instance for a cluster is installed and configured on a separate server. For more information about configuring Cisco Unified MeetingPlace Web Servers for failover, see the "Application Server Failover" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Load balancing does not affect shared storage locations. All servers in a cluster use the same shared storage location.

Web conferencing supports three potential load balancing configurations, as shown in [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: One Cluster Configuration|Figure: One Cluster Configuration]], [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: Internal and External Clusters of Web Servers|Figure: Mixed Configuration: Internal and External Clusters of Web Servers]], and [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers|Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers]].

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cisco Unified MeetingPlace Web Server cluster-This can be an internal cluster or external cluster.
|-
|
3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Internal cluster of Web Servers.
|-
|
3
|

SQL Server-All Web Servers in the internal cluster must connect to the same SQL Server.
|
4
|

External cluster of Web Servers.
|-
|
5
|

SQL Server-All Web Servers in the external cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cluster of Web Servers-This can be an internal cluster or an external cluster.
|-
|
3
|

SQL Server-All Web Servers in a cluster must connect to the same SQL Server.
|
4
|

Single Web Server-This can be an internal or external web server.
|-
|
5
|

SQL Server-The single Web Server must connect to a separate SQL Server.
|
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Web Server comprises two separate load balancing components: the original server and the second server. Meetings are hosted on the original server. Participants connect to the second server when joining a meeting. These components interact to provide load balancing and failover capability as follows:

* When a meeting starts, the designated Web Server (the Web Server that is listed in the meeting notification) assigns a primary and backup original server to the meeting room based on the current active meeting load.

* As participants join the meeting, they are load balanced across the second servers in the cluster based on the number of participants currently connected to each second server at that time. The second server internally makes a connection to the original server that is hosting the meeting.

* Each client is given the primary and backup original server information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Web Servers. Meetings are spread across the three original servers in the cluster based on the meeting load on each. Participants are spread across the three second servers based on the participant load on each. Note that participants are not necessarily connected to the second server that corresponds to the original Web Server hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web meeting by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conferencing home page. When the first meeting participant attempts to join the web meeting, the system determines if the meeting should be held on an internal Web Server or an external Web Server by checking the "Allow External Web Participants" parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

"Allow External Web Participants" is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the internal cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any internal Web Server when they join the web meeting.
|-
|

"Allow External Web Participants" is set to Yes
|

This meeting is accessible to external attendees; that is, participants attending from outside the firewall.

If the first attendee attempts to join the web meeting from an external Web Server, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any external Web Server when they join the web meeting.

If the first attendee attempts to join the web meeting from an internal Web Server, Cisco Unified MeetingPlace determines if it has an associated external Web Server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace redirects the meeting to that external server. Web Server, the designated Cisco Unified MeetingPlace external Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This Web Server (original server) now owns (hosts) the meeting. Subsequent attendees may be directed to any external Web Server (second server) when they join the web meeting
* If Cisco Unified MeetingPlace does not find an entry in the DMZ Web Server field, the system redirects the meeting to the least loaded internal Web Server. The system directs all subsequent meeting participants to an internal Web Server for their web meeting.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external Web Server.

External users can join only external meetings on external Web Servers.

== Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System ==

To ensure a robust system with operational redundancy, we recommend that your Web Conferencing deployment contain the following:

* An internal web cluster (with 2 or 3 Cisco Unified MeetingPlace Web Servers)

* An external web cluster (with 2 or 3 Cisco Unified MeetingPlace Web Servers)

* A dedicated remote SQL Server system for each Cisco Unified MeetingPlace Web Sever cluster (one for Internal cluster, one for External cluster)

* Remote storage location (Microsoft NetBIOS over TCP/IP) with an appropriately sized RAID array and a comprehensive backup policy

== End-User Experience During Meeting Console Failover ==

When failover occurs on a system that is configured for Load Balancing, users experience the following behavior:
# The Web Server to which the user is connected stops responding (for example, the Web Server loses power or the Web Conferencing services fails to respond).
# Users who are connected to the second server on that Web Server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the user to the second server. If this attempt fails, the meeting console attempts to connect to the second server designated as the backup for that meeting. (The Web Server sends the assigned primary and backup second server information to each client when the client first connects to a meeting.)

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

Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server

2012-08-16T03:47:32Z

Dunn:

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.1]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.1 -- Planning Your Deployment|Planning Your Deployment]]

Load Balancing in Cisco Unified MeetingPlace Web Conferencing service is achieved when multiple Cisco Unified MeetingPlace Web Servers setup as logical cluster to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support.

When configured appropriately with remote database source and storage, the clustered capabilities can also provide for continuity of service for web conference meetings in progress if one of the clustered Cisco Unified MeetingPlace Web servers becomes unavailable or unreachable. The user experience will see an interruption for participants homed to the unavailable/unreachable Web Server node, and can attempt reconnect to the meeting.

For operations purpose an administrator can view the amount of web-conferencing load per Web Server from the Web Server administrative page. This information is displayed only on internal Web Servers.

We recommend that you load balance the Web Conferencing portion of your Cisco Unified MeetingPlace system by using clusters. In a Cisco Unified MeetingPlace load-balancing Web Server cluster, all users must enter the Cisco Unified MeetingPlace system through a designated Cisco Unified MeetingPlace Web Server. In load-balancing Web Server cluster deployments, only the designated Cisco Unified MeetingPlace Web Server needs to be configured for the chosen authentication method. All other Web Servers in the cluster use the default authentication method-MeetingPlace Web Form Authentication. If, however, you want to configure other Web Servers in the cluster to use the same authentication method as a failover strategy, you can. Depending on the type of authentication method used though, this configuration can result in undesirable SSO behaviors.

For example, if you configure HTTP Basic Authentication or Windows Integrated Authentication, Cisco Unified MeetingPlace will prompt users for login credentials each time there is a Web Server redirect. This is because you are altering the hostname in the authentication configuration each time you redirect traffic to an active Web Server through a DNS change. If you configure LDAP or MeetingPlace authentication, users will not be prompted again for login credentials during a web conferencing redirect.

Use the information in this section to determine the load balancing configuration you want for the Web Conferencing portion of your Cisco Unified MeetingPlace system.

== Understanding How the Cisco Unified MeetingPlace Application Servers and Web Servers Communicate ==

The Cisco Unified MeetingPlace Replication Service automatically synchronizes the local Web Server database with that of the Cisco Unified MeetingPlace Application Server to update meetings, user profiles, and user group information. The following occurs by default:

* Synchronization occurs every 60 seconds.

* The User Profile Update Interval updates every 20 days.

* The Group Update Interval updates every 20 days.

* Meeting information updates every 60 seconds.

The Replication Service copies attachments and recordings from the Cisco Unified MeetingPlace Application Server and stores the replicated files on the Cisco Unified MeetingPlace Web Server. Pointers to these files are then created in the database. The Replication Service downloads voice files in their native Cisco Unified MeetingPlace voice (.mp4) format. After voice files are downloaded, the Replication Service queues jobs for conversion by the Audio Service.

The Replication Service also replicates video terminal user profile information from the Application Server. By default, this replication occurs every 7 days.

In the event of a system failure, you can manually invoke the Replication Service update and purge operations. Allow up to 20 minutes for any changes made to the Replication Service to take effect. For information on how to invoke the Replication Service, see the "How to Update Meetings and User Profiles" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

== Web Conferencing Clusters ==

'''Restriction:''' When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

With Cisco Unified MeetingPlace, you can configure to have an internal and an external Web Server cluster simultaneously. The cluster can have up to three (3) Web Servers. We recommend deploying "remote" SQL 2000 or 2005 customer provided systems. Each web cluster must use its own remote SQL, the SQL cannot be shared.

'''Internal cluster'''-Places all Web Servers behind the firewall inside the private corporate network. Typically, all Web Servers in an internal cluster display the full-access Cisco Unified MeetingPlace interface.

'''External cluster'''-Places all Web Servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all Web Servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace interface.

Cisco Unified MeetingPlace Web Servers use a SQL database to store profile and meeting information. When deploying Cisco Unified MeetingPlace Web Server clusters, the internal and external clusters must use separate SQL databases; however, the two databases must have identical Globally Unique Identifiers (GUIDS). It is recommended for high availability, the SQL database instance for a cluster is installed and configured on a separate server. For more information about configuring Cisco Unified MeetingPlace Web Servers for failover, see the "Application Server Failover" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Load balancing does not affect shared storage locations. All servers in a cluster use the same shared storage location.

Web conferencing supports three potential load balancing configurations, as shown in [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: One Cluster Configuration|Figure: One Cluster Configuration]], [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: Internal and External Clusters of Web Servers|Figure: Mixed Configuration: Internal and External Clusters of Web Servers]], and [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers|Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers]].

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cisco Unified MeetingPlace Web Server cluster-This can be an internal cluster or external cluster.
|-
|
3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Internal cluster of Web Servers.
|-
|
3
|

SQL Server-All Web Servers in the internal cluster must connect to the same SQL Server.
|
4
|

External cluster of Web Servers.
|-
|
5
|

SQL Server-All Web Servers in the external cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cluster of Web Servers-This can be an internal cluster or an external cluster.
|-
|
3
|

SQL Server-All Web Servers in a cluster must connect to the same SQL Server.
|
4
|

Single Web Server-This can be an internal or external web server.
|-
|
5
|

SQL Server-The single Web Server must connect to a separate SQL Server.
|
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Web Server comprises two separate load balancing components: the original server and the second server. Meetings are hosted on the original server. Participants connect to the second server when joining a meeting. These components interact to provide load balancing and failover capability as follows:

* When a meeting starts, the designated Web Server (the Web Server that is listed in the meeting notification) assigns a primary and backup original server to the meeting room based on the current active meeting load.

* As participants join the meeting, they are load balanced across the second servers in the cluster based on the number of participants currently connected to each second server at that time. The second server internally makes a connection to the original server that is hosting the meeting.

* Each client is given the primary and backup original server information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Web Servers. Meetings are spread across the three original servers in the cluster based on the meeting load on each. Participants are spread across the three second servers based on the participant load on each. Note that participants are not necessarily connected to the second server that corresponds to the original Web Server hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web meeting by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conferencing home page. When the first meeting participant attempts to join the web meeting, the system determines if the meeting should be held on an internal Web Server or an external Web Server by checking the "Allow External Web Participants" parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

"Allow External Web Participants" is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the internal cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any internal Web Server when they join the web meeting.
|-
|

"Allow External Web Participants" is set to Yes
|

This meeting is accessible to external attendees; that is, participants attending from outside the firewall.

If the first attendee attempts to join the web meeting from an external Web Server, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any external Web Server when they join the web meeting.

If the first attendee attempts to join the web meeting from an internal Web Server, Cisco Unified MeetingPlace determines if it has an associated external Web Server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace redirects the meeting to that external server. Web Server, the designated Cisco Unified MeetingPlace external Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This Web Server (original server) now owns (hosts) the meeting. Subsequent attendees may be directed to any external Web Server (second server) when they join the web meeting
* If Cisco Unified MeetingPlace does not find an entry in the DMZ Web Server field, the system redirects the meeting to the least loaded internal Web Server. The system directs all subsequent meeting participants to an internal Web Server for their web meeting.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external Web Server.

External users can join only external meetings on external Web Servers.

== Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System ==

To ensure a robust system with redundancy and failover, we recommend that your Web Conferencing deployment contain the following:

* An internal web cluster

* An external web cluster

* A dedicated remote SQL Server system for each cluster

* Remote storage location with an appropriately sized RAID array and a comprehensive backup policy

== End-User Experience During Meeting Console Failover ==

When failover occurs on a system that is configured for Load Balancing, users experience the following behavior:
# The Web Server to which the user is connected stops responding (for example, the Web Server loses power or the Web Conferencing services fails to respond).
# Users who are connected to the second server on that Web Server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the user to the second server. If this attempt fails, the meeting console attempts to connect to the second server designated as the backup for that meeting. (The Web Server sends the assigned primary and backup second server information to each client when the client first connects to a meeting.)

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

Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server

2012-08-16T03:38:26Z

Dunn:

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.1]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.1 -- Planning Your Deployment|Planning Your Deployment]]

Load Balancing in Cisco Unified MeetingPlace Web Conferencing service is achieved when multiple Cisco Unified MeetingPlace Web Servers setup as logical cluster to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support.

When configured appropriately with remote database source and storage, the clustered capabilities can also provide for continuity of service for meetings in progress if one Cisco Unified MeetingPlace Web Server becomes unavailable or unreachable. The user experience will see an interruption for participants homed to the failed/unreachable Web Server node, and may attempt reconnect to another Web Server node in the same cluster.

You can view the amount of web-conferencing load per Web Server from the Web Server administrative page. This information is displayed only on internal Web Servers.

We recommend that you load balance the Web Conferencing portion of your Cisco Unified MeetingPlace system by using clusters. In a Cisco Unified MeetingPlace load-balancing Web Server cluster, all users must enter the Cisco Unified MeetingPlace system through a designated Cisco Unified MeetingPlace Web Server. In load-balancing Web Server cluster deployments, only the designated Cisco Unified MeetingPlace Web Server needs to be configured for the chosen authentication method. All other Web Servers in the cluster use the default authentication method-MeetingPlace Web Form Authentication. If, however, you want to configure other Web Servers in the cluster to use the same authentication method as a failover strategy, you can. Depending on the type of authentication method used though, this configuration can result in undesirable SSO behaviors.

For example, if you configure HTTP Basic Authentication or Windows Integrated Authentication, Cisco Unified MeetingPlace will prompt users for login credentials each time there is a Web Server redirect. This is because you are altering the hostname in the authentication configuration each time you redirect traffic to an active Web Server through a DNS change. If you configure LDAP or MeetingPlace authentication, users will not be prompted again for login credentials during a web conferencing redirect.

Use the information in this section to determine the load balancing configuration you want for the Web Conferencing portion of your Cisco Unified MeetingPlace system.

== Understanding How the Cisco Unified MeetingPlace Application Servers and Web Servers Communicate ==

The Cisco Unified MeetingPlace Replication Service automatically synchronizes the local Web Server database with that of the Cisco Unified MeetingPlace Application Server to update meetings, user profiles, and user group information. The following occurs by default:

* Synchronization occurs every 60 seconds.

* The User Profile Update Interval updates every 20 days.

* The Group Update Interval updates every 20 days.

* Meeting information updates every 60 seconds.

The Replication Service copies attachments and recordings from the Cisco Unified MeetingPlace Application Server and stores the replicated files on the Cisco Unified MeetingPlace Web Server. Pointers to these files are then created in the database. The Replication Service downloads voice files in their native Cisco Unified MeetingPlace voice (.mp4) format. After voice files are downloaded, the Replication Service queues jobs for conversion by the Audio Service.

The Replication Service also replicates video terminal user profile information from the Application Server. By default, this replication occurs every 7 days.

In the event of a system failure, you can manually invoke the Replication Service update and purge operations. Allow up to 20 minutes for any changes made to the Replication Service to take effect. For information on how to invoke the Replication Service, see the "How to Update Meetings and User Profiles" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

== Web Conferencing Clusters ==

'''Restriction:''' When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

With Cisco Unified MeetingPlace, you can configure to have an internal and an external Web Server cluster simultaneously. The cluster can have up to three (3) Web Servers. We recommend deploying "remote" SQL 2000 or 2005 customer provided systems. Each web cluster must use its own remote SQL, the SQL cannot be shared.

'''Internal cluster'''-Places all Web Servers behind the firewall inside the private corporate network. Typically, all Web Servers in an internal cluster display the full-access Cisco Unified MeetingPlace interface.

'''External cluster'''-Places all Web Servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all Web Servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace interface.

Cisco Unified MeetingPlace Web Servers use a SQL database to store profile and meeting information. When deploying Cisco Unified MeetingPlace Web Server clusters, the internal and external clusters must use separate SQL databases; however, the two databases must have identical Globally Unique Identifiers (GUIDS). It is recommended for high availability, the SQL database instance for a cluster is installed and configured on a separate server. For more information about configuring Cisco Unified MeetingPlace Web Servers for failover, see the "Application Server Failover" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Load balancing does not affect shared storage locations. All servers in a cluster use the same shared storage location.

Web conferencing supports three potential load balancing configurations, as shown in [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: One Cluster Configuration|Figure: One Cluster Configuration]], [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: Internal and External Clusters of Web Servers|Figure: Mixed Configuration: Internal and External Clusters of Web Servers]], and [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers|Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers]].

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cisco Unified MeetingPlace Web Server cluster-This can be an internal cluster or external cluster.
|-
|
3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Internal cluster of Web Servers.
|-
|
3
|

SQL Server-All Web Servers in the internal cluster must connect to the same SQL Server.
|
4
|

External cluster of Web Servers.
|-
|
5
|

SQL Server-All Web Servers in the external cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cluster of Web Servers-This can be an internal cluster or an external cluster.
|-
|
3
|

SQL Server-All Web Servers in a cluster must connect to the same SQL Server.
|
4
|

Single Web Server-This can be an internal or external web server.
|-
|
5
|

SQL Server-The single Web Server must connect to a separate SQL Server.
|
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Web Server comprises two separate load balancing components: the original server and the second server. Meetings are hosted on the original server. Participants connect to the second server when joining a meeting. These components interact to provide load balancing and failover capability as follows:

* When a meeting starts, the designated Web Server (the Web Server that is listed in the meeting notification) assigns a primary and backup original server to the meeting room based on the current active meeting load.

* As participants join the meeting, they are load balanced across the second servers in the cluster based on the number of participants currently connected to each second server at that time. The second server internally makes a connection to the original server that is hosting the meeting.

* Each client is given the primary and backup original server information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Web Servers. Meetings are spread across the three original servers in the cluster based on the meeting load on each. Participants are spread across the three second servers based on the participant load on each. Note that participants are not necessarily connected to the second server that corresponds to the original Web Server hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web meeting by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conferencing home page. When the first meeting participant attempts to join the web meeting, the system determines if the meeting should be held on an internal Web Server or an external Web Server by checking the "Allow External Web Participants" parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

"Allow External Web Participants" is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the internal cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any internal Web Server when they join the web meeting.
|-
|

"Allow External Web Participants" is set to Yes
|

This meeting is accessible to external attendees; that is, participants attending from outside the firewall.

If the first attendee attempts to join the web meeting from an external Web Server, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any external Web Server when they join the web meeting.

If the first attendee attempts to join the web meeting from an internal Web Server, Cisco Unified MeetingPlace determines if it has an associated external Web Server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace redirects the meeting to that external server. Web Server, the designated Cisco Unified MeetingPlace external Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This Web Server (original server) now owns (hosts) the meeting. Subsequent attendees may be directed to any external Web Server (second server) when they join the web meeting
* If Cisco Unified MeetingPlace does not find an entry in the DMZ Web Server field, the system redirects the meeting to the least loaded internal Web Server. The system directs all subsequent meeting participants to an internal Web Server for their web meeting.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external Web Server.

External users can join only external meetings on external Web Servers.

== Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System ==

To ensure a robust system with redundancy and failover, we recommend that your Web Conferencing deployment contain the following:

* An internal web cluster

* An external web cluster

* A dedicated remote SQL Server system for each cluster

* Remote storage location with an appropriately sized RAID array and a comprehensive backup policy

== End-User Experience During Meeting Console Failover ==

When failover occurs on a system that is configured for Load Balancing, users experience the following behavior:
# The Web Server to which the user is connected stops responding (for example, the Web Server loses power or the Web Conferencing services fails to respond).
# Users who are connected to the second server on that Web Server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the user to the second server. If this attempt fails, the meeting console attempts to connect to the second server designated as the backup for that meeting. (The Web Server sends the assigned primary and backup second server information to each client when the client first connects to a meeting.)

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

Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration

2012-06-28T15:53:17Z

Dunn: /* End-User Experience During Meeting Console Failover */

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x#Web Conferencing|Web Conferencing]] > [[Cisco Unified MeetingPlace, Release 6.x -- Installing and Upgrading Web Conferencing|Installing and Upgrading]] >

[[Cisco Unified MeetingPlace, Release 6.x -- Installing Web Conferencing in a Load Balancing Configuration|Installing Web Conferencing in a Load Balancing Configuration]]

--------------------------------------------------------------------------------------------

Load balancing in Cisco Unified MeetingPlace Web Conferencing makes use of a cluster of Web Conferencing servers to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support. It also provides failover capabilities for meetings-if one Cisco Unified MeetingPlace Web Conferencing server is unavailable or unreachable, meeting clients will reconnect to another server, even if they are currently connected to a meeting that is in progress when the connection is interrupted.

You can view the amount of web-conferencing load per server from the Web Server administrative page. This information is displayed only on internal web servers.

To configure load balancing, you should understand the following concepts in this section:
* [[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Restrictions for Installing Web Conferencing in a Load Balancing Configuration|Restrictions for Installing Web Conferencing in a Load Balancing Configuration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Web Conferencing Clusters|Web Conferencing Clusters]]
* [[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Web Conferencing Load Balancing and Failover Capability|Web Conferencing Load Balancing and Failover Capability]]
* [[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Load Balancing Behavior with Internal and External Clusters|Load Balancing Behavior with Internal and External Clusters]]
* [[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Recommendations for a Robust Cisco Unified MeetingPlace System|Recommendations for a Robust Cisco Unified MeetingPlace System]]
* [[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#End-User Experience During Meeting Console Failover|End-User Experience During Meeting Console Failover]]

== Restrictions for Installing Web Conferencing in a Load Balancing Configuration ==
* Microsoft Network Load Balancing is not supported.
* Third-party web server load balancing is not supported.
* When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

== Web Conferencing Clusters ==

With Cisco Unified MeetingPlace Web Conferencing, you can configure up to three web servers into a cluster, and you can configure clusters as either internal or external.

''' Internal cluster '''-Places all web servers behind the firewall inside the private corporate network. Typically, all web servers in an internal cluster display the full-access
Cisco Unified MeetingPlace Web Conferencing interface

''' External cluster '''-Places all web servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all web servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace Web Conferencing interface.

You can attach a maximum of three web servers (including both internal and external servers) to a single Cisco Unified MeetingPlace Audio Server system. The two databases (one for the internal server or cluster, one for the external server or cluster) must have identical GUIDS.

Web Conferencing supports five potential load balancing configurations, as shown in the following three figures:

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|

1
|

Cisco Unified MeetingPlace Audio Server system.
|

2
|

Cisco Unified MeetingPlace web server cluster-This can be an internal cluster or external cluster.
|-
|

3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
| 
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|

1
|

Cisco Unified MeetingPlace Audio Server system.
|

2
|

Internal cluster of web servers.
|-
|

3
|

SQL Server-All web servers in the internal cluster must connect to the same SQL Server.
|

4
|

External cluster of web servers.
|-
|

5
|

SQL Server-All web servers in the external cluster must connect to the same SQL Server.
| 
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|

1
|

Cisco Unified MeetingPlace Audio Server system.
|

2
|

Cluster of web servers-This can be an internal cluster or an external cluster.
|-
|

3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|

4
|

Single web server-This can be an internal or external web server.
|-
|

5
|

SQL Server-The single web server must connect to a separate SQL Server.
| 
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Cisco Unified MeetingPlace Web Conferencing server comprises two separate load balancing components: 1) the origin server and 2) the other server or servers in the cluster. Meetings are hosted on the origin
server. Participants connect to the other server or servers in the cluster when joining a meeting. These components interact to provide load balancing and failover capability as follows:
* When a meeting starts, the Cisco Unified MeetingPlace Web Conferencing server assigns a primary and backup origin server to the meeting room based on current active meeting load.
* As participants join the meeting, they are load balanced across the other server or servers in the cluster based on the number of participants currently connected to each other server or servers in the cluster at that time. The other server or servers in the cluster internally make a connection to the origin server that is hosting the meeting.
* Each client is given the primary origin/other and backup origin/other information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Cisco Unified MeetingPlace Web Conferencing servers. Meetings are spread across the three origin servers in the cluster based on the current meeting load on each. Participants are spread across the three other servers in the cluster based on the participant load on each. Note that participants are not necessarily connected to the other server or servers in the cluster on the machine hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

If a failure occurs on a server in the cluster, users will experience the following behavior:
* The web server to which the participant is connected stops responding (for example, the computer loses power or the Cisco Unified MeetingPlace Web Conferencing services are shut down).
* Users who are connected to that web server lose their connection to the meeting.
* Each meeting console client that lost its connection automatically tries to reconnect to the failover server. If this attempt fails, the meeting console attempts to connect to the backup failover server by using the backup information that it received when initially connecting to the meeting.

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web conference by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conference home page. When the first meeting participant attempts to join the web conference, the Cisco MeetingPlace Agent Service determines if the meeting should be held on an internal web server or external web server by checking the Allow External Web Participants parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 6.x -- About Installing Web Conferencing in a Load Balancing Configuration#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

Allow External Web Participants is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, Cisco Unified MeetingPlace Web Conferencing directs the web-conferencing session to the web server with the fewest currently active meetings in the internal cluster. This web server now owns the meeting. Subsequent attendees may be directed to any internal web server when they join the web conference.
|-
|

Allow External Web Participants is set to Yes
|

This meeting is accessible to external attendees, that is, participants attending from outside the firewall.

If the first attendee attempts to join the web conference from an external web server, Cisco Unified MeetingPlace Web Conferencing directs the web-conferencing session to the web server with the fewest currently active meetings in the external cluster. This web server now owns the meeting.

If the first attendee attempts to join the web conference from an internal web server, Cisco Unified MeetingPlace Web Conferencing determines if it has an associated external web server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace Web Conferencing performs a redirection to that external server.
* If Cisco Unified MeetingPlace Web Conferencing does not find an entry in the DMZ Web Server field, the web-conferencing session is directed to the least loaded internal server as described for internal meetings. All subsequent attendees are directed to an internal web server for their web conference.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external web server.

External users can join only external meetings on external web servers.

== Recommendations for a Robust Cisco Unified MeetingPlace System ==

To ensure a robust system with redundancy and failover, we recommend that you have the following:
* An internal web cluster.
* An external web cluster.
* A dedicated remote SQL Server system for each cluster.
* Remote storage location with an appropriately sized RAID array and a comprehensive backup policy.

== End-User Experience During Meeting Console Failover ==

When failover occurs on a system that is configured for load balancing, users will experience the following behavior:

# The web server to which the participant is connected stops responding (for example, the MPWeb Server loses power or the Web Conferencing services fails to respond).
# Users who are connected to the other server or servers in the cluster on that web server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the user to the other server or servers in the cluster. If this attempt fails, the meeting console attempts to connect to the other server or servers in the cluster designated as the backup for that meeting. (The Web Conferencing server sends the assigned primary and backup other server or servers in the cluster information to each client when the client first connects to a meeting.)

-----------------------------------------------------------------------------------------------

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x#Web Conferencing|Web Conferencing]] > [[Cisco Unified MeetingPlace, Release 6.x -- Installing and Upgrading Web Conferencing|Installing and Upgrading]] >

[[Cisco Unified MeetingPlace, Release 6.x -- Installing Web Conferencing in a Load Balancing Configuration|Installing Web Conferencing in a Load Balancing Configuration]]

Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server

2012-06-28T15:00:51Z

Dunn: Updated to show clarity that MPWeb is not configured for failover, but rather Load Balancing

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.1]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.1 -- Planning Your Deployment|Planning Your Deployment]]

Load balancing in Cisco Unified MeetingPlace Web Conferencing makes use of a cluster of Web Servers to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support. It also provides failover capabilities for meetings-if one Cisco Unified MeetingPlace Web Server is unavailable or unreachable, meeting participants reconnect to another Web Server, even if they are currently connected to a meeting that is in progress when the connection is interrupted.

You can view the amount of web-conferencing load per Web Server from the Web Server administrative page. This information is displayed only on internal Web Servers.

We recommend that you load balance the Web Conferencing portion of your Cisco Unified MeetingPlace system by using clusters. In a Cisco Unified MeetingPlace load-balancing Web Server cluster, all users must enter the Cisco Unified MeetingPlace system through a designated Cisco Unified MeetingPlace Web Server. In load-balancing Web Server cluster deployments, only the designated Cisco Unified MeetingPlace Web Server needs to be configured for the chosen authentication method. All other Web Servers in the cluster use the default authentication method-MeetingPlace Web Form Authentication. If, however, you want to configure other Web Servers in the cluster to use the same authentication method as a failover strategy, you can. Depending on the type of authentication method used though, this configuration can result in undesirable SSO behaviors.

For example, if you configure HTTP Basic Authentication or Windows Integrated Authentication, Cisco Unified MeetingPlace will prompt users for login credentials each time there is a Web Server redirect. This is because you are altering the hostname in the authentication configuration each time you redirect traffic to an active Web Server through a DNS change. If you configure LDAP or MeetingPlace authentication, users will not be prompted again for login credentials during a web conferencing redirect.

Use the information in this section to determine the load balancing configuration you want for the Web Conferencing portion of your Cisco Unified MeetingPlace system.

== Understanding How the Cisco Unified MeetingPlace Application Servers and Web Servers Communicate ==

The Cisco Unified MeetingPlace Replication Service automatically synchronizes the local Web Server database with that of the Cisco Unified MeetingPlace Application Server to update meetings, user profiles, and user group information. The following occurs by default:

* Synchronization occurs every 60 seconds.

* The User Profile Update Interval updates every 20 days.

* The Group Update Interval updates every 20 days.

* Meeting information updates every 60 seconds.

The Replication Service copies attachments and recordings from the Cisco Unified MeetingPlace Application Server and stores the replicated files on the Cisco Unified MeetingPlace Web Server. Pointers to these files are then created in the database. The Replication Service downloads voice files in their native Cisco Unified MeetingPlace voice (.mp4) format. After voice files are downloaded, the Replication Service queues jobs for conversion by the Audio Service.

The Replication Service also replicates video terminal user profile information from the Application Server. By default, this replication occurs every 7 days.

In the event of a system failure, you can manually invoke the Replication Service update and purge operations. Allow up to 20 minutes for any changes made to the Replication Service to take effect. For information on how to invoke the Replication Service, see the "How to Update Meetings and User Profiles" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

== Web Conferencing Clusters ==

'''Restriction:''' When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

With Cisco Unified MeetingPlace, you can configure to have an internal and an external Web Server cluster simultaneously. The cluster can have up to three (3) Web Servers. We recommend deploying "remote" SQL 2000 or 2005 customer provided systems. Each web cluster must use its own remote SQL, the SQL cannot be shared.

'''Internal cluster'''-Places all Web Servers behind the firewall inside the private corporate network. Typically, all Web Servers in an internal cluster display the full-access Cisco Unified MeetingPlace interface.

'''External cluster'''-Places all Web Servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all Web Servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace interface.

Cisco Unified MeetingPlace Web Servers use a SQL database to store profile and meeting information. When deploying Cisco Unified MeetingPlace Web Server clusters, the internal and external clusters must use separate SQL databases; however, the two databases must have identical Globally Unique Identifiers (GUIDS). It is recommended for high availability, the SQL database instance for a cluster is installed and configured on a separate server. For more information about configuring Cisco Unified MeetingPlace Web Servers for failover, see the "Application Server Failover" module in the ''Cisco Unified MeetingPlace Release 7.1 Configuration Guide'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Load balancing does not affect shared storage locations. All servers in a cluster use the same shared storage location.

Web conferencing supports three potential load balancing configurations, as shown in [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: One Cluster Configuration|Figure: One Cluster Configuration]], [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: Internal and External Clusters of Web Servers|Figure: Mixed Configuration: Internal and External Clusters of Web Servers]], and [[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers|Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers]].

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cisco Unified MeetingPlace Web Server cluster-This can be an internal cluster or external cluster.
|-
|
3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Internal cluster of Web Servers.
|-
|
3
|

SQL Server-All Web Servers in the internal cluster must connect to the same SQL Server.
|
4
|

External cluster of Web Servers.
|-
|
5
|

SQL Server-All Web Servers in the external cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cluster of Web Servers-This can be an internal cluster or an external cluster.
|-
|
3
|

SQL Server-All Web Servers in a cluster must connect to the same SQL Server.
|
4
|

Single Web Server-This can be an internal or external web server.
|-
|
5
|

SQL Server-The single Web Server must connect to a separate SQL Server.
|
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Web Server comprises two separate load balancing components: the original server and the second server. Meetings are hosted on the original server. Participants connect to the second server when joining a meeting. These components interact to provide load balancing and failover capability as follows:

* When a meeting starts, the designated Web Server (the Web Server that is listed in the meeting notification) assigns a primary and backup original server to the meeting room based on the current active meeting load.

* As participants join the meeting, they are load balanced across the second servers in the cluster based on the number of participants currently connected to each second server at that time. The second server internally makes a connection to the original server that is hosting the meeting.

* Each client is given the primary and backup original server information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Web Servers. Meetings are spread across the three original servers in the cluster based on the meeting load on each. Participants are spread across the three second servers based on the participant load on each. Note that participants are not necessarily connected to the second server that corresponds to the original Web Server hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web meeting by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conferencing home page. When the first meeting participant attempts to join the web meeting, the system determines if the meeting should be held on an internal Web Server or an external Web Server by checking the "Allow External Web Participants" parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 7.1 -- About Load Balancing Options for the Web Server#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

"Allow External Web Participants" is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the internal cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any internal Web Server when they join the web meeting.
|-
|

"Allow External Web Participants" is set to Yes
|

This meeting is accessible to external attendees; that is, participants attending from outside the firewall.

If the first attendee attempts to join the web meeting from an external Web Server, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any external Web Server when they join the web meeting.

If the first attendee attempts to join the web meeting from an internal Web Server, Cisco Unified MeetingPlace determines if it has an associated external Web Server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace redirects the meeting to that external server. Web Server, the designated Cisco Unified MeetingPlace external Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This Web Server (original server) now owns (hosts) the meeting. Subsequent attendees may be directed to any external Web Server (second server) when they join the web meeting
* If Cisco Unified MeetingPlace does not find an entry in the DMZ Web Server field, the system redirects the meeting to the least loaded internal Web Server. The system directs all subsequent meeting participants to an internal Web Server for their web meeting.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external Web Server.

External users can join only external meetings on external Web Servers.

== Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System ==

To ensure a robust system with redundancy and failover, we recommend that your Web Conferencing deployment contain the following:

* An internal web cluster

* An external web cluster

* A dedicated remote SQL Server system for each cluster

* Remote storage location with an appropriately sized RAID array and a comprehensive backup policy

== End-User Experience During Meeting Console Failover ==

When failover occurs on a system that is configured for Load Balancing, users experience the following behavior:
# The Web Server to which the user is connected stops responding (for example, the Web Server loses power or the Web Conferencing services fails to respond).
# Users who are connected to the second server on that Web Server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the user to the second server. If this attempt fails, the meeting console attempts to connect to the second server designated as the backup for that meeting. (The Web Server sends the assigned primary and backup second server information to each client when the client first connects to a meeting.)

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

Cisco Unified MeetingPlace, Release 7.0 -- Command Reference

2012-04-10T23:26:35Z

Dunn:

{{Template:Required Metadata}} '''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

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

 

 

== Command Syntax Conventions ==

'''CAUTION : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks and functions, and is not designed for use as a persistent operating environment monitoring tool. If you need to perform persistent continuous monitoring please consult Cisco TAC or your Cisco Professional Services partners for further guidance. ''' 

This document uses these command syntax conventions.

 

{| border="1"
|-
! Convention
! Description
|-
|
'''bold'''

|
Bold text indicates commands and parameters that you enter as shown.

|-
|
''italic''

|
Italic text indicates parameters for which you supply values.

|-
|
<x>

|
Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters.

|-
|
[x]

|
Square brackets enclose an optional parameter.

|-
|
<nowiki> | </nowiki>

|
A vertical line, called a pipe, indicates a choice within a set of parameters.

|-
|
[x | y]

|
Square brackets enclosing parameters separated by a pipe indicate an optional choice.

|-
|
{x | y}

|
Braces enclosing parameters separated by a pipe indicate a required choice.

|-
|
[x {y | z}]

|
Braces and a pipe within square brackets indicate a required choice within an optional element.

|}

 

 

== Application Commands ==

===== Table: Command Reference: Application Commands =====

{| border="1"
|-
! Command
! Description
|-
|
activity

|
Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings.

 Syntax: '''activity'''

|-
|
alarm

|
Displays the [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Alarm_Table|Alarm Table]]:

*REFNO -- Reference number used with the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#clearalarm|clearalarm]] command to clear a specific alarm table entry.
*SEV -- Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Alarm_Severity_Levels|Alarm Severity Levels]] in the [[Cisco Unified MeetingPlace, Release 7.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.
*CODE -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Code|Code]].
*COUNT -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Count|Count]].
*FIRST -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#First_Time|First Time]].
*LAST -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Last_Time|Last Time]].
*UNIT -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Unit|Unit]].
*SW MODULE -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Software_Module|Software Module]].

'''Note: ''' The brief description in the alarm table entry may contain values that are specific to one alarm occurrence, such as an IP address. These values may differ in all alarms that are combined into one table entry, but only the values for the ''first'' alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command.

 Syntax: '''alarm'''

|-
|
checklic

|
Shows the type and number of licenses installed.

'''Note: ''' The system may take up to 15 seconds to process this information.

 Syntax: '''checklic'''

|-
|
clearalarm

|
Clears either all the alarms in the alarm table or just the alarm specified.

 If there are any major alarms in the alarm table, the system can be configured to call the system administrator after every restart until all major alarms are deleted from the alarm table. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring the System to Call You if There is a Major Alarm#Configuring_the_System_to_Call_You_if_There_is_a_Major_Alarm|Configuring the System to Call You if There is a Major Alarm]].

 Running this command stops the system from calling the system administrator (if it has been configured to do so).

 Syntax: '''clearalarm''' {''reference-number'' | '''all'''}

|-
|
cleardb

|
Clears the following Application Server data:

*All user profiles except the admin and guest user profiles
*All user groups except the System group
*All user recordings
*All conference recordings

You must be signed in to the Application Server CLI as the root user to enter this command.

Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns.

'''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command.

Syntax: '''cleardb'''

|-
|
cpstatus

|
Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video.

 Syntax: '''cpstatus'''

|-
|
cptrace

|
Lists selected portions of the call processing trace log.

 Syntax: '''cptrace'''

|-
|
date

|
Displays the time and date for the Application Server.

 If you are logged in as a root user, then you can also set the date and time based on the local time zone.

 Syntax: '''date''' [''MMDDhhmm''[''YYYY'']['''.'''''ss'']]

 Parameters (available only to root users):

*''MM'' -- month, specified by two digits
*''DD'' -- day, specified by two digits
*''hh'' -- hour, specified by two digits in 24-hour format
*''mm'' -- minute, specified by two digits
*''YYYY'' -- calendar year, specified by four digits
*'''.'''''ss'' -- second, specified by two digits and a preceding period (.)

|-
|
dbupdate

|
Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group.

'''Caution! ''' Deleting all database entries is an irreversible operation. Before you run the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#dbupdate|dbupdate]] command, consider backing up and archiving the database. 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]].

 Use this command only in the following situations:

*Cisco TAC instructs you to do so.
*You configured Directory Service on your system, and you need to change the LDAP directory with which Cisco Unified Communications Manager is integrated. If you do not clear the database before switching from one LDAP directory to another, then all the user profiles from the first LDAP directory will remain in the Cisco Unified MeetingPlace database until you manually delete them.

:The automatic Directory Service deletion of user profiles does not apply when you change the LDAP directory. For details about when and how the system automatically deletes Directory Service user profiles, see [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory_Service_User_Profile_Deletion|Directory Service User Profile Deletion]].

|-
|
errorlog

|
Displays the [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output one screen at a time:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command provides the entire [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output all at once.

 Syntax: '''errorlog'''

|-
|
eventlog

|
Displays the system event log.

'''Note: ''' This command has many parameter options; only the most commonly used parameters are listed below.

 Syntax: '''eventlog''' ['''-b''' [''YY''][''MMDD'']''hhmm''] ['''-e''' [''YY''][''MMDD'']''hhmm''] ['''-G''' | '''-C'''] ['''-t'''] ['''| more''']

 Parameters:

*'''-b''' -- Specifies a start time for the log events to include in the output.
*'''-e''' -- Specifies an end time for the log events to include in the output.

'''Note: ''' To show events for the current day, you may omit the ''YY'', ''MM'', and ''DD'' parameters from the start and end times.

*''YY'' -- Calendar year, specified by two digits. Typically, this parameter is included only when troubleshooting issues around the start of a new calendar year.
*''MM'' -- month, specified by two digits
*''DD'' -- day, specified by two digits
*''hh'' -- hour, specified by two digits in 24-hour format
*''mm'' -- minute, specified by two digits
*'''-G''' -- Shows the telephony and conference events and control messages from the Call Processing-Media Control Protocol (CPMCP) component, which is a proxy for the Media Server.
*'''-C''' -- Limits log output to events for the conference scheduler (ConfSchd) component.
*'''-t''' -- Displays the log output in real time. This option is useful for troubleshooting issues in real time. For example, you can enter '''eventlog -G -t''' and then place a test call to the system to see how the system responds to the incoming call and to any subsequent user input.
*'''| more''' -- Displays the log output one screen at a time.

|-
|
exc

|
Displays the meaning of an exception code that was listed in the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] or [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command output.

 Syntax: '''exc''' ['''-v'''] ''exception-code''

|-
|
hostname

|
Displays the hostname of the Application Server.

 Syntax: '''hostname'''

|-
|
infocap

|
Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information.

 Restrictions:

*You must be logged in as the root user to run this command.
*You can also get this information by completing [[Cisco Unified MeetingPlace, Release 7.0 -- Obtaining and Viewing the System Information Capture (Infocap) Log#Obtaining_and_Viewing_the_System_Information_Capture_.28Infocap.29_Log|Obtaining and Viewing the System Information Capture (Infocap) Log]]. Use this command only if you are unable to get the information from the Cisco Unified MeetingPlace Administration Center.
*The begin and end dates and times must be in the format [YY]MMDDhhmm. The YY is optional and if not specified, the system uses the current year. For format details, see the parameters for the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#date|date]] command.

 Syntax: '''infocap -b''' ''begin-date-and-time'' '''-e''' ''end-date-and-time''

|-
|
langinfo

|
Displays information about all installed locales including the following:

*Locale ID
*Language code
*Locale order
*Locale name
*Country code
*Locale version number

 Syntax: '''langinfo'''

|-
|
mtginfo

|
Displays information about a specific meeting. Searches for a meeting based on any of these:

*Unique conference ID (such as 125). (This number is output by certain commands such as '''cptrace -C''' and '''errorlog'''. It uniquely identifies a meeting.)
*Meeting ID (such as 1278). Can optionally use any of the time arguments.
*Unique user ID (such as 0x65). (This number is output by certain commands such as [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#userinfo|userinfo]]. It uniquely identifies a user.) Searches for all meetings that a user has attended or been invited to.
*Activity. Searches only for active meetings.
*Time. Searches for all meetings valid at a certain time with the -t argument or between two times when the -s and -e arguments are used together.

 Syntax: '''mtginfo''' '''-a''' ''time'' '''-c''' ''unique-conf-id'' '''-e''' ''end-time'' '''-m''' ''meeting-id'' '''-s''' ''start-time'' '''-t''' ''time'' '''-u''' ''unique-user-id''

'''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#date|date]] command.

'''Note: ''' Start and end times in the command output are adjusted for the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting_ID_start_guard_time_.28minutes.29|Meeting ID start guard time (minutes)]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting_ID_end_guard_time_.28minutes.29|Meeting ID end guard time (minutes)]] fields on the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting_Configuration_Page|Meeting Configuration Page]].

 Examples:

 '''mtginfo -m 1234 '''Looks for the meeting with the ID of 1234 at the current time

 '''mtginfo -m 1234 -t 11 '''Looks for meeting with the ID of 1234 at 11 minutes after the current hour

 '''mtginfo -m 1234 -t 1111111111 '''Looks for meeting with the ID of 1234 at 11:11am on Nov 11, 2011

 '''mtginfo -a 1430 '''Looks for meetings that are active at 2:30pm today

 '''mtginfo -s 1430 -e 1530 '''Looks for meetings that started or ended between 2:30 and 3:30pm today

 '''mtginfo -c 123 '''Looks for meeting with the unique conference ID of 123

 '''mtginfo -u 123 -t 1111 -e 1211 '''Looks for meetings that the user with the unique user ID of 123 is invited to between 11:11 and 12:11 today

|-
|
net

|
Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

 

Use the '''net''' command to set the following:

*Port configuration parameters, including:
**Application Server (eth0) hostname, IP address, subnet mask, and default gateway
**Virtual (eth0:0) hostname, IP address, subnet mask, and default gateway-the eth0:0 virtual interface is used in [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover#Application_Server_Failover|Application Server Failover]] deployments
**MTU and link parameters (auto-negotiation, speed, duplex).

*Domain name

*DNS servers

*NTP servers
*:'''Note: ''' If you change the Application Server hostname (for eth0), then you must also perform the following actions:
**Configure the DNS server to point the old hostname to the new hostname.
**Restart the application by entering either the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]] '''restart''' operating system command or the '''reboot''' Linux command. '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.
**If you enabled SSL for the Application Server, complete [[Cisco Unified MeetingPlace, Release 7.0 -- Generating a Certificate Signing Request and Obtaining the Certificate|Generating a Certificate Signing Request and Obtaining the Certificate]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Uploading the Certificate File and Enabling SSL|Uploading the Certificate File and Enabling SSL]].
**If you installed MeetingPlace Conference Manager, complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Add, Edit, or Remove a Server#Editing_an_Existing_Server|Editing an Existing Server]].
**If your system includes a Web Server, complete [[Cisco Unified MeetingPlace, Release 7.0 -- Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM|Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM]] .
**If you integrated the system with Cisco WebEx, notify the Cisco WebEx administrator to update the Cisco Unified MeetingPlace hostname that is configured in the Cisco WebEx license manager.

 Syntax: '''net'''

|-
|
ntpdate

|
Sets the Application Server date and time to match the time obtained by polling an NTP server.

 Syntax: '''ntpdate''' ['''-u'''] ''ntp-server''

 Parameters:

*'''-u''' -- Specifies to send packets through an unprivileged port to communicate with the NTP server. Use this option when you want to reach an NTP server that is beyond a firewall.
*''ntp-server'' -- Hostname or IP address of the NTP server.

|-
|
swstatus

|
Displays information about Cisco Unified MeetingPlace, including the following:

*Version number
*System mode
*Status of the power supplies
*List of software modules loaded in to memory, their version number, and their status

 Syntax: '''swstatus'''

|-
|
techui

|
Displays statistics for the Media Server, ports, and conferences.

 This technician user interface helps to diagnose and troubleshoot media and voice quality issues of active calls.

 Syntax: '''techui'''

|-
|
userinfo

|
Displays information about a specific user. Searches for a user based on any of these:

*[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_ID|User ID]]
*[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile_number|Profile number]]
*Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user.

 Syntax: '''userinfo''' {''user-id'' | ''profile-number'' | ''unique-user-id''}

|-
|
userutil

|
Performs administrative functions for any user profile.

 Restriction: You cannot set the admin user to inactive, locked, or the group default.

 Syntax: '''userutil''' {'''-q''' | ['''-p''' | '''-P] '''['''-n''' | '''-N] '''['''-a''' | '''-i''' | '''-l''' | '''-g]'''} ''userid'' [''password'']

 Parameters:

*'''-q''' -- Displays user profile information and status.
*'''-p''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_password|User password]]. Requires a ''password'' entry.
*'''-P''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_password|User password]] and force it to expire. Requires a ''password'' entry.
*'''-n''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile_password|Profile password]] (PIN for authentication over the phone). Requires a ''password'' entry.
*'''-N''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile_password|Profile password]] and force it to expire. Requires a ''password'' entry.
*'''-a''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to active.
*'''-i''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to inactive.
*'''-l''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to locked.
*'''-g''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to group default setting.
*''userid'' -- [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_ID|User ID]].
*''pasword'' -- New [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_password|User password]] or [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile_password|Profile password]]. Required if you enter '''-p''', '''-P''', '''-n''', or '''-N'''.

|-
|
viewexlog

|
Provides the entire [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output all at once:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] command displays the [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output one screen at a time:

 Syntax: '''viewexlog'''

|}

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

*[[Cisco Unified MeetingPlace, Release 7.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]]

 

== Operating System Commands ==

In addition to the Cisco Unified MeetingPlace commands listed in [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Table:_Command_Reference:_Operating_System_Commands|Table: Command Reference: Operating System Commands]], the CLI supports the standard Linux operating system commands. You can use the '''vim''' command to view or modify text files if necessary.

 Note the following requirements and restrictions for operating system commands:

*With the exception of the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]] command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands may cause unpredictable results.

*If you are not logged in as the [[Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options#root|root]] user, you must enter '''sudo''' before you can run any of these commands. For example, to stop all application services, go to the command line and enter the following:

:'''sudo ./mpx_app stop'''
:The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, you instead enter the following:
:'''sudo /etc/init.d/mpx_app stop'''

*Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies:
**To the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_app|mpx_app]], [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]], and [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_va|mpx_va]] commands.
**If the Application Server crashes and is reloaded.
**If you enter the '''shutdown''' or '''reboot''' Linux command on the Application Server.

 

===== Table: Command Reference: Operating System Commands =====

{| border="1"
|-
! Command
! Description
|-
|
mpx_app

|
Starts, stops, or restarts all Cisco Unified MeetingPlace application services.

'''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

 Syntax: '''mpx_app''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_axlds

|
Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager.

 Syntax: '''mpx_axlds''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_db

|
Starts, stops, or restarts Cisco Unified MeetingPlace database services.

 Syntax: '''mpx_db''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_lm

|
Starts, stops, or restarts Cisco Unified MeetingPlace license manager services.

 Syntax: '''mpx_lm''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rmi

|
Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging.

 Syntax: '''mpx_rmi''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rssctrl

|
Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service.

 Syntax: '''mpx_rssctrl''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_snmp

|
Starts, stops, or restarts SNMP services.

 Syntax: '''mpx_snmp''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_sys

|
Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

'''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

 '''Note: ''' If the restart process is interrupted, you will have to reenter the '''mpx_sys restart''' command. For example, the restart process may be interrupted by a power outage, by closing the SSH connection, or by another restart process that is initiated from a different terminal.

 Syntax: '''mpx_sys''' {'''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcat

|
Starts, stops, or restarts Apache Tomcat services.

 Syntax: '''mpx_tomcat''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcatmon

|
Starts, stops, or restarts Apache Tomcat monitoring services.

 Syntax: '''mpx_tomcatmon''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_va

|
Starts, stops, or restarts Media Server services on the Application Server.

 If all other Cisco Unified MeetingPlace services continue running, entering this command does ''not'' interrupt meetings that are in session.

 Syntax: '''mpx_va''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_version

|
Lists all installed versions of Cisco Unified MeetingPlace.

 Syntax: '''mpx_version '''

|-
|
mpx_webx

|
Starts, stops, or restarts all Cisco WebEx integration services on the Application Server.

 Syntax: '''mpx_webx''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
resetmsapassword

|
Resets the Media Server Administration password to "cisco".

 Syntax: '''resetmsapassword'''

|-
|
shutdown

|
Shuts down the Application Server.

 For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters.

 Syntax: '''shutdown -h now'''

|}

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

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

*[[Cisco Unified MeetingPlace, Release 7.0 -- Changing the Media Server Administration Password|Changing the Media Server Administration Password]]

 

== Database Replication Commands ==

'''Note: ''' To enter the database replication commands in [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Table:_Command_Reference:_Database_Replication_Commands|Table: Command Reference: Database Replication Commands]]:

*The MeetingPlace Database services must be running on the Application Server.

*You must be logged in to the CLI as the [[Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options#root|root]] user.

 The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>.

 

===== Table: Command Reference: Database Replication Commands =====

{| border="1"
|-
! Command
! Description
|-
|
mp_replication init

|
Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication.

 Syntax: '''mp_replication init -s''' ''site'' '''-n''' ''node'' ['''-l''' ''local-server''] '''-r''' ''remote-server'' {'''-h''' | '''-m'''} ['''-v''']

 Parameters:

*'''-s''' ''site'' -- Specifies the site of the node on which you run this command. Valid values for ''site'' are 1 and 2.
*'''-n''' ''node'' -- Specifies the node (within the specified site) on which you run the command. Valid values for ''node'' are 1 and 2.
*'''-l''' ''local-server'' -- (Optional) Specifies the hostname or IP address of the Application Server on which you run this command.

:For intra-site replication, which is used for [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.
:By default, the (eth0 hostname) value returned by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#hostname|hostname]] command is used.

*'''-r''' ''remote-server'' -- Specifies the hostname or IP address of the other Application Server with which to establish replication.
*'''-h''' -- Specifies intra-site replication, which is used for replication between the active and standby Application Server in a single-site active/standby failover deployment.
*'''-m''' -- Specifies inter-site replication, which is used for replication between two singleServer mode Application Servers (i.e, site 1 and site 2) in Reservationless Single Number Access (RSNA) deployment.
*'''-v''' -- Specifies verbose output.

|-
|
mp_replication switchON

|
Starts replication between two Application Servers.

*Run this command on node 1 only.
*Run this command only after running the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command on each node involved in replication.

 Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v''']

 Parameters:

*'''-r''' ''remote-server'' -- Specifies the hostname or IP address of the other Application Server with which to establish replication.

:For intra-site replication, which is used for Application Server failover, specify the hostname or IP address of the virtual network interface eth0:0.

*'''-S''' '''-F''' ''data-source-server'' -- Indicates data synchronization between the two Application Servers.

:'''NOTE:''' Both Application Servers must be in standby mode when the '''-S''' '''-F''' options are used.
:For intra-site replication, which is used for [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.

*'''-v''' -- Specifies verbose output.

|-
|
mp_replication status

|
Displays the status of replication between the specified servers.

 Syntax: '''mp_replication status''' ['''-v''']

 Parameter: '''-v'''-Specifies verbose output.

|-
|
mp_replication switchOFF

|
Stops replication, but does not restore configuration changes.

*Run this command on node 1 only.
*To restart replication, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_switchON|mp_replication switchON]] command.
*To restore the configuration changes done by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_teardown|mp_replication teardown]] command.

 Syntax: '''mp_replication switchOFF''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command. Exception:

*'''-f''' -- Specifies to remove the local server from replication even in the following cases:
**Specified remote server is not part of replication.
**Local server is not in replication with any other servers.

|-
|
mp_replication teardown

|
Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes.

 Syntax: '''mp_replication teardown''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command.

|}

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

*[[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

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

 

== Failover Commands ==

'''Note: ''' You must be logged in to the CLI as the [[Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options#root|root]] user to enter the failover commands in [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Table:_Command_Reference:_Failover_Commands|Table: Command Reference: Failover Commands]].

 

===== Table: Command Reference: Failover Commands =====

{| border="1"
|-
! Command
! Description
|-
|
failoverUtil copyConfigFiles

|
Transfers configuration files from one Application Server to the other, specifically:

#Compresses the configuration files and user prompts on the local server.
#Transfers the compressed files to the remote server.

 After you enter this command on the local server, you need to enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] on the remote server.

 The following files and directories are transferred by this command:

*Directory Service:
**/opt/cisco/meetingplace/axlds/current/etc/config.properties
*Recorded user names and custom voice prompts:
**Everything under /opt/cisco/meetingplace/afs/custom
*Microsoft Outlook integration files:
**Everything under /opt/cisco/meetingplace/var/outlook
**/opt/cisco/meetingplace/var/admin/outlook.config
**Everything under /opt/cisco/meetingplace/var/mail
*Cisco WebEx integration files:
**/opt/cisco/meetingplace/web/current/etc/conf/keyinfo.properties
**/opt/cisco/meetingplace/web/current/etc/conf/keystore.jks
**/opt/cisco/meetingplace/web/current/etc/conf/cert.cer

 The script pauses to request your credentials. You must provide the following:

*The remote machine's hostname or IP address
*The administrator’s username on the remote machine (the mpxadmin username)
*The mpxadmin password

 Syntax: '''failoverUtil copyConfigFiles'''

|-
|
failoverUtil restoreConfigFiles

|
Completes the transfer of configuration files from one Application Server to the other, specifically:

#Decompresses the configuration files and user prompts that were transferred from the remote server.
#Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server.

'''Note: ''' The [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_copyConfigFiles|failoverUtil copyConfigFiles]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] commands are entered on separate Application Servers.

 Syntax: '''failoverUtil restoreConfigFiles'''

|-
|
failoverUtil setDeployment failover

|
Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway.

 Syntax: '''failoverUtil setDeployment failover'''

|-
|
failoverUtil setDeployment singleServer

|
Restores a failover-deployed Application Server to a single-server deployment.

 Syntax: '''failoverUtil setDeployment singleServer'''

|-
|
failoverUtil setServer

|
Sets a failover-deployed Application Server to either active or standby mode.

 Enter this command only after running the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_setDeployment_failover|failoverUtil setDeployment failover]] command on the server.

'''Note: ''' The mode setting may not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, log in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]] '''restart''' command, followed by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_setServer|failoverUtil setServer]] command.

'''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

 

Syntax: '''failoverUtil setServer''' {'''active''' | '''standby'''}

|-
|
failoverUtil status

|
Displays the current modes of the Application Server, specifically:

*Whether the server is deployed for failover or as a single server.
*If deployed for failover, then whether the server is in active or standby mode.

 Syntax: '''failoverUtil status'''

|}

 

 

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

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

[[Category:Reference_Information_for_Cisco_Unified_MeetingPlace,_Release_7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options

2012-04-10T23:25:07Z

Dunn:

{{Template:Required Metadata}} '''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

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

 

 

{| border="1"
|-
! CLI User Level
! Description
|-
|
mpxadmin

|
We recommend that you use this user level whenever possible.

|-
|
root

|
Highest authority, enabling you to do the following:

*Enter [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Operating_System_Commands|Operating System Commands]], though pseudo (sudo) root access may also be used.
*Enter [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Database_Replication_Commands|Database Replication Commands]] or [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Failover_Commands|Failover Commands]].
*Reset the root or mpxadmin user passwords.
*Uninstall the system.

 To get to the root user level, do one of the following:

*Log in as the mpxadmin user, and enter '''su''' at the command line.
*Log in directly as the root user-this is possibly only by [[Cisco Unified MeetingPlace, Release 7.0 -- How to Log in to the CLI#Logging_in_to_the_CLI_Using_the_Console|Logging in to the CLI Using the Console]].

'''Caution! ''' For security reasons, we do not recommend logging in directly as the root user, unless you need to reset the root user or mpxadmin user passwords or uninstall the system.

|}

 

'''CAUTION : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks and functions, and is not designed for use as a persistent operating environment monitoring tool. If you need to perform persistent continuous monitoring please consult Cisco TAC or your Cisco Professional Services partners for further guidance. ''' 

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

*[[Cisco Unified MeetingPlace, Release 7.0 -- How to Log in to the CLI#Logging_in_to_the_CLI_Using_the_Console|Logging in to the CLI Using the Console]]

*[[Cisco Unified MeetingPlace, Release 7.0 -- How to Log in to the CLI#Logging_in_to_the_CLI_Using_SSH|Logging in to the CLI Using SSH]]

*[[Cisco Unified MeetingPlace, Release 7.0 -- Password Recovery for Cisco Unified MeetingPlace|Password Recovery for Cisco Unified MeetingPlace]]

[[Category:Reference_Information_for_Cisco_Unified_MeetingPlace,_Release_7.0]]

Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server

2012-04-10T23:10:38Z

Dunn:

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

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

 

 

You can use the command-line interface (CLI) on the Application Server to perform functions that cannot be performed in the Administration Center. 

 

== '''CAUTION''' : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks and functions, and is not designed for use as a persistent operating environment monitoring tool. If you need to perform persistent continuous monitoring please consult Cisco TAC or your Cisco Professional Services partners for further guidance. ==

 

'''Note: ''' The CLI on the Application Server is not the same as the CLI on the Cisco WebEx Node for MCS. For information about the latter, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS#Using_the_Command-Line_Interface_.28CLI.29_on_the_Cisco_WebEx_Node_for_MCS|Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS]] module.

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#CLI_User_Level_Options_on_the_Application_Server|CLI User Level Options on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Restrictions_for_the_CLI_on_the_Application_Server|Restrictions for the CLI on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#How_to_Sign_in_to_the_CLI_on_the_Application_Server|How to Sign in to the CLI on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

 

== CLI User Level Options on the Application Server ==

{| border="1"
|-
! CLI User Level
! Description
|-
|
mpxadmin

|
We recommend that you use this user level whenever possible.

|-
|
root

|
Highest authority, enabling you to do the following:

*Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]], though pseudo (sudo) root access can also be used.
*Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database_Replication_Commands_for_the_Application_Server|Database Replication Commands for the Application Server]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover_Commands_for_the_Application_Server|Failover Commands for the Application Server]].
*Reset the root or mpxadmin user passwords.
*Uninstall the system.

 To get to the root user level, do one of the following:

*Sign in as the mpxadmin user, and enter '''su''' at the command line.
*Sign in directly as the root user-this is possibly only by [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]].

'''Caution! ''' For security reasons, we do not recommend signing in directly as the root user, unless you need to reset the root user or mpxadmin user passwords or uninstall the system.

|}

 

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Password Recovery for the Cisco Unified MeetingPlace Application Server#Password_Recovery_for_the_Cisco_Unified_MeetingPlace_Application_Server|Password Recovery for the Cisco Unified MeetingPlace Application Server]] module

 

== Restrictions for the CLI on the Application Server ==

*The CLI and its commands are available only in English.
*The CLI accepts only the standard 128 ASCII characters.
*Many commands you enter might prompt you for information. If the Backspace key does not delete characters in this interactive mode, use one of the following options:
**Press the '''Delete''' key to delete the previous character.
**Press '''Ctrl-W''' to delete the previous word.
**Press '''Ctrl-U''' to delete the entire line.

 

== How to Sign in to the CLI on the Application Server ==

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]

 

=== Signing in to the CLI on the Application Server By Using the Console ===

You can sign in to the CLI from the console by using either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] usernames. ''This is the only way you can sign in directly as the root user.'' You can enter operating system commands here.

 

===== Procedure =====

#Connect the monitor, keyboard, and mouse to the Application Server.
#:The Cisco Unified MeetingPlace operating system sign-in page is displayed.
#For the username, enter '''mpxadmin'''.
#Enter the password for the mpxadmin user.
#:This was established during installation.
#Right-click the desktop and select '''Open Terminal'''.
#:A command window appears. You can start entering commands. This is a Linux operating system so all commands should be either Linux commands or Cisco Unified MeetingPlace operating system commands. See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]] for information about the operating system commands.
#When you are finished with the command window, either enter '''exit''' or select the '''X''' in the top right corner.
#:'''Note: ''' Always sign out of the Cisco Unified MeetingPlace operating system when you are finished.

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

 

=== Signing in to the CLI on the Application Server By Using SSH ===

This section provides one method of signing in to the CLI by using SSH. Other methods might be available for you.

 

===== Restriction =====

Only the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] user can sign in to the CLI remotely using SSH. If needed, you can later switch to the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user by entering '''su'''.

 

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

You need a remote connection with a non-configurable terminal emulation program, such as the Windows SSH client, to sign in to the CLI remotely using SSH.

 

===== Procedure =====

#From your computer, go to '''Start > Programs > SSH Secure Shell > Secure Shell Client'''.
#Select '''Quick Connect'''.
#In the Connect to Remote Host window, enter these values:

 

{| border="1"
|-
! Field
! Value
|-
|
Host Name

|
IP address of your Cisco Unified MeetingPlace system

|-
|
User Name

|
mpxadmin

|-
|
Port Number

|
22

|-
|
Authentication Method

|
leave as <Profile Settings>

|}

 

:4. Select '''Connect'''.
:5. In the Enter Password window, enter the password for the mpxadmin user.
::This was established during installation.
:6. Select '''OK'''.
::The system displays the command line, and you can now enter commands.

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

== Application Server Command Reference ==

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Command_Syntax_Conventions|Command Syntax Conventions]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Commands_for_the_Application_Server|Application Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database_Replication_Commands_for_the_Application_Server|Database Replication Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover_Commands_for_the_Application_Server|Failover Commands for the Application Server]]

 

=== Command Syntax Conventions ===

This document uses these command syntax conventions.

 

{| border="1"
|-
! Convention
! Description
|-
|
'''bold'''

|
Bold text indicates commands and parameters that you enter as shown.

|-
|
''italic''

|
Italic text indicates parameters for which you supply values.

|-
|
<x>

|
Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters.

|-
|
[x]

|
Square brackets enclose an optional parameter.

|-
|
<nowiki> | </nowiki>

|
A vertical line, called a pipe, indicates a choice within a set of parameters.

|-
|
[x | y]

|
Square brackets enclosing parameters separated by a pipe indicate an optional choice.

|-
|
{x | y}

|
Braces enclosing parameters separated by a pipe indicate a required choice.

|-
|
[x {y | z}]

|
Braces and a pipe within square brackets indicate a required choice within an optional element.

|}

=== Application Commands for the Application Server ===

===== Table: Command Reference: Application Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
activity

|
Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings.

 Syntax: '''activity'''

|-
|
alarm

|
Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm_Table|Alarm Table]]:

*REFNO-Reference number used with the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#clearalarm|clearalarm]] command to clear a specific alarm table entry.
*SEV-Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm_Severity_Levels|Alarm Severity Levels]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.
*CODE-See Code.
*COUNT -See Count.
*FIRST-See First Time.
*LAST-See Last Time.
*UNIT-See Unit.
*SW MODULE-See Software Module.

'''Note: ''' The brief description in the alarm table entry might contain values that are specific to one alarm occurrence, such as an IP address. These values might differ in all alarms that are combined into one table entry, but only the values for the ''most recent ''alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command.

 Syntax: '''alarm'''

|-
|
ccamon

|
Monitors the Call Control Agent. Allows you to view the call statistics and set the log tracing level.

 Syntax: '''ccamon'''

|-
|
checklic

|
Shows the type and number of licenses installed.

'''Note: ''' The system can take up to 15 seconds to process this information.

 Syntax: '''checklic'''

|-
|
clearalarm

|
Clears either all the alarms in the alarm table or just the alarm specified.

 If there are any major alarms in the alarm table, the system can be configured to call the system administrator after every restart until all major alarms are deleted from the alarm table. See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Configuring_the_System_to_Call_You_If_There_is_a_Major_Alarm|Configuring the System to Call You If There is a Major Alarm]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.

 Running this command stops the system from calling the system administrator (if it has been configured to do so).

 Syntax: '''clearalarm''' {''reference-number'' | '''all'''}

|-
|
cleardb

|
Clears the following Application Server data:

*All user profiles except the admin and guest user profiles
*All user groups except the System group
*All user recordings
*All conference recordings

You must be signed in to the Application Server CLI as the root user to enter this command.

Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns.

'''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command.

Syntax: '''cleardb'''

|-
|
cpstatus

|
Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video.

 Syntax: '''cpstatus'''

|-
|
cptrace

|
Lists selected portions of the call processing trace log.

 Syntax: '''cptrace'''

|-
|
date

|
Displays the time and date for the Application Server.

 If you are signed in as a root user, you can also set the date and time based on the local time zone.

 Syntax: '''date''' [''MMDDhhmm''[''YYYY'']['''.'''''ss'']]

 Parameters (available only to root users):

*''MM''-month, specified by two digits
*''DD''-day, specified by two digits
*''hh''-hour, specified by two digits in 24-hour format
*''mm''-minute, specified by two digits
*''YYYY''-calendar year, specified by four digits
*'''.'''''ss''-second, specified by two digits and a preceding period (.)

|-
|
dbupdate

|
Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group.

'''Caution! ''' Deleting all database entries is an irreversible operation. Before you run the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#dbupdate|dbupdate]] command, consider backing up and archiving the database. See [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing_Up.2C_Archiving.2C_and_Restoring_Data_on_the_Cisco_Unified_MeetingPlace_Application_Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

 Use this command only in these situations:

*Cisco TAC instructs you to do so.
*You configured Directory Service on your system, and you need to change the LDAP directory with which Cisco Unified Communications Manager is integrated. If you do not clear the database before switching from one LDAP directory to another, all user profiles from the first LDAP directory will remain in the Cisco Unified MeetingPlace database until you manually delete them.

:The automatic Directory Service deletion of user profiles does not apply when you change the LDAP directory. For details about when and how the system automatically deletes Directory Service user profiles, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory_Service_User_Profile_Deletion|Directory Service User Profile Deletion]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring_Cisco_Unified_MeetingPlace_Directory_Service|Configuring Cisco Unified MeetingPlace Directory Service]] module.

|-
|
errorlog

|
Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output one screen at a time:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output all at once.

 Syntax: '''errorlog'''

|-
|
eventlog

|
Displays the system event log.

'''Note: ''' This command has many parameter options; only the most commonly used parameters are listed below.

 Syntax: '''eventlog''' ['''-b''' [''YY''][''MMDD'']''hhmm''] ['''-e''' [''YY''][''MMDD'']''hhmm''] ['''-G''' | '''-C'''] ['''-t'''] ['''| more''']

 Parameters:

*'''-b'''-Specifies a start time for the log events to include in the output.
*'''-e'''-Specifies an end time for the log events to include in the output.

'''Note: ''' To show events for the current day, you can omit the ''YY'', ''MM'', and ''DD'' parameters from the start and end times.

*''YY''-Calendar year, specified by two digits. Typically, this parameter is included only when troubleshooting issues around the start of a new calendar year.
*''MM''-month, specified by two digits
*''DD''-day, specified by two digits
*''hh''-hour, specified by two digits in 24-hour format
*''mm''-minute, specified by two digits
*'''-G'''-Shows the telephony and conference events and control messages from the Call Processing-Media Control Protocol (CPMCP) component, which is a proxy for the Media Server.
*'''-C'''-Limits log output to events for the conference scheduler (ConfSchd) component.
*'''-t'''-Displays the log output in real time. This option is useful for troubleshooting issues in real time. For example, you can enter '''eventlog -G -t''' and then place a test call to the system to see how the system responds to the incoming call and to any subsequent user input.
*'''| more'''-Displays the log output one screen at a time.

|-
|
exc

|
Displays the meaning of an exception code that was listed in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command output.

 Syntax: '''exc''' ['''-v'''] ''exception-code''

|-
|
hostname

|
Displays the hostname of the Application Server.

 Syntax: '''hostname'''

|-
|
infocap

|
Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information.

 Restrictions:

*You must be signed in as the root user to run this command.
*You can also get this information by completing [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Obtaining_and_Viewing_the_System_Information_Capture_.28Infocap.29_Log|Obtaining and Viewing the System Information Capture (Infocap) Log]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module. Use this command only if you are unable to get the information from the Cisco Unified MeetingPlace Administration Center.
*The begin and end dates and times must be in the format [YY]MMDDhhmm. The YY is optional and if not specified, the system uses the current year. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

 Syntax: '''infocap -b''' ''begin-date-and-time'' '''-e''' ''end-date-and-time''

|-
|
infocapmtg

|
Gathers a system information capture file around the time of a meeting.

 Syntax: '''infocapmtg''' [''meetingID''] ['''-S | -P | -B'''''minutes''] ['''-n''' ''username | '''''-p''' ''profilename''] ['''-b''' ''beginning-time'' '''-e''' ''ending-time'']

 Parameters:

*''meetingID''-Captures information about a specific meeting ID.
*'''-S'''-Captures information about the specified meeting ID when it was scheduled.
*'''-P'''-Stops the capture when the meeting was purged.
*'''-B''' ''minutes''-Adds a buffer of minutes before or after the start or stop of the capture.
*'''-n''' ''username''-Captures information about the first meeting where the specified user was a participant.
*'''-p''' ''profilename''-Captures information about the first meeting where the specified user profile was a participant.
*'''-b''' ''beginning-time'' '''-e''' ''ending-time''-Captures information about the meeting between the beginning and ending time.

 Examples:

 '''infocapmtg 1212''' Gathers a system information capture file starting at the time meeting 1212 began and ending when meeting 1212 ended.

 '''infocapmtg 1212 -S''' Gathers a system information capture file starting at the time someone scheduled meeting 1212 and ending when meeting 1212 ended.

 '''infocapmtg 1212 -B 5''' Gathers a system information capture file starting 5 minutes before meeting 1212 began and ending 5 minutes after meeting 1212 ended.

 '''infocapmtg -n''' ''username'' '''-b 0950 -e 1400''' Gathers a system information capture file starting for a meeting scheduled by or attended by ''username'' where the meeting started between 9:50 a.m. and 2:00 p.m. today.

|-
|
langinfo

|
Displays information about all installed locales including the following:

*Locale ID
*Language code
*Locale order
*Locale name
*Country code
*Locale version number

 Syntax: '''langinfo'''

|-
|
mtginfo

|
Displays information about a specific meeting. Searches for a meeting based on any of these:

*Unique conference ID (such as 125). (This number is output by certain commands such as '''cptrace -C''' and '''errorlog'''. It uniquely identifies a meeting.)
*Meeting ID (such as 1278). Can optionally use any of the time arguments.
*Unique user ID (such as 0x65). (This number is output by certain commands such as [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#userinfo|userinfo]]. It uniquely identifies a user.) Searches for all meetings that a user has attended or been invited to.
*Activity. Searches only for active meetings.
*Time. Searches for all meetings valid at a certain time with the -t argument or between two times when the -s and -e arguments are used together.

 Syntax: '''mtginfo''' '''-a''' ''time'' '''-c''' ''unique-conf-id'' '''-e''' ''end-time'' '''-m''' ''meeting-id'' '''-s''' ''start-time'' '''-t''' ''time'' '''-u''' ''unique-user-id''

'''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

'''Note: ''' Start and end times in the command output are adjusted for the Meeting ID start guard time (minutes) and Meeting ID end guard time (minutes) fields on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting_Configuration_Page|Meeting Configuration Page]].

 Examples:

 '''mtginfo -m 1234 '''Looks for the meeting with the ID of 1234 at the current time

 '''mtginfo -m 1234 -t 11 '''Looks for meeting with the ID of 1234 at 11 minutes after the current hour

 '''mtginfo -m 1234 -t 1111111111 '''Looks for meeting with the ID of 1234 at 11:11am on Nov 11, 2011

 '''mtginfo -a 1430 '''Looks for meetings that are active at 2:30pm today

 '''mtginfo -s 1430 -e 1530 '''Looks for meetings that started or ended between 2:30 and 3:30pm today

 '''mtginfo -c 123 '''Looks for meeting with the unique conference ID of 123

 '''mtginfo -u 123 -t 1111 -e 1211 '''Looks for meetings that the user with the unique user ID of 123 is invited to between 11:11 and 12:11 today

|-
|
net

|
Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system.

 You must be signed in as root before running this command.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

 Use the '''net''' command to set the following:

*Port configuration parameters, including:
**Application Server (eth0) hostname, IP address, subnet mask, and default gateway
**Virtual (eth0:0) hostname, IP address, subnet mask, and default gateway-the eth0:0 virtual interface is used in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]] deployments
**MTU and link parameters (auto-negotiation, speed, duplex).
*Domain name
*DNS servers
*NTP servers

'''Note: ''' If you change the Application Server hostname (for eth0), then you must also perform these actions:

**Configure the DNS (1) server to point the old hostname to the new hostname.
**Restart the application by entering either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#'''mpx_sys|mpx_sys]]''''''restart''' operating system command or the '''reboot''' Linux command.
**If you enabled SSL for the Application Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Generating_a_Certificate_Signing_Request_and_Obtaining_the_Certificate|Generating a Certificate Signing Request and Obtaining the Certificate]] and [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Uploading_the_Certificate_File_and_Enabling_SSL|Uploading the Certificate File and Enabling SSL]] sections in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Configuring_SSL_for_the_Cisco_Unified_MeetingPlace_Application_Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]] module.
**If you installed MeetingPlace Conference Manager, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Editing_an_Existing_Server|Editing an Existing Server]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using_MeetingPlace_Conference_Manager|Using MeetingPlace Conference Manager]] module.
**If your system includes a Web Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Changing_the_Cisco_Unified_MeetingPlace_Application_Server_Connection_Configured_in_the_Gateway_SIM|Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Configuring_the_Cisco_Unified_MeetingPlace_Gateway_System_Integrity_Manager|Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager]] module.
**If you integrated the system with Cisco WebEx, notify the Cisco WebEx administrator to update the Cisco Unified MeetingPlace hostname that is configured in the Cisco WebEx license manager.

 Syntax: '''net'''

|-
|
ntpdate

|
Sets the Application Server date and time to match the time obtained by polling an NTP (2) server.

 Syntax: '''ntpdate''' ['''-u'''] ''ntp-server''

 Parameters:

*'''-u'''-Specifies to send packets through an unprivileged port to communicate with the NTP server. Use this option when you want to reach an NTP server that is beyond a firewall.
*''ntp-server''-Hostname or IP address of the NTP server.

|-
|
swstatus

|
Displays information about Cisco Unified MeetingPlace, including the following:

*Version number
*System mode
*Status of the power supplies
*List of software modules loaded in to memory, their version number, and their status

 Syntax: '''swstatus'''

|-
|
taccli

|
Displays details on the mixer status, active meetings, participant details, and general statistics, including the following:

*Cisco Unified MeetingPlace request statistics
*Statistics or status for one or all channels
*Statistics or details for one or all conferences
*Mixer status, request failures, and mixer return code table
*Video resolution and frame rate of each connection that is made to the Express Media Server

 Also does the following:

*Resets Cisco Unified MeetingPlace request statistics
*Enables and disables tracing
*Shows the current date and time
*Starts and stops channel RTP recording

 Syntax: '''taccli'''

|-
|
techui

|
Displays statistics for the Media Server, ports, and conferences.

 This technician user interface helps to diagnose and troubleshoot media and voice quality issues of active calls.

 Syntax: '''techui'''

|-
|
userinfo

|
Displays information about a specific user. Searches for a user based on any of these:

*User ID
*Profile number
*Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user.

 Syntax: '''userinfo''' {''user-id'' | ''profile-number'' | ''unique-user-id''}

|-
|
userutil

|
Performs administrative functions for any user profile.

 Restriction: You cannot set the admin user to inactive, locked, or the group default.

 Syntax: '''userutil''' {'''-q''' | ['''-p''' | '''-P] '''['''-n''' | '''-N] '''['''-a''' | '''-i''' | '''-l''' | '''-g]'''} ''userid'' [''password'']

 Parameters:

*'''-q'''-Displays user profile information and status.
*'''-p'''-Reset the User password. Requires a ''password'' entry.
*'''-P'''-Reset the User password and force it to expire. This forces the user to change the password at the next sign-in attempt. Requires a ''password'' entry.
*'''-n'''-Reset the Profile PIN (PIN for authentication over the phone). Requires a ''password'' entry.
*'''-N'''-Reset the Profile PIN and force it to expire. Requires a ''password'' entry.
*'''-a'''-Set User status to active.
*'''-i'''-Set User status to inactive.
*'''-l'''-Set User status to locked.
*'''-g'''-Set User status to group default setting.
*''userid''-User ID.
*''pasword''-New User password or Profile PIN. Required if you enter '''-p''', '''-P''', '''-n''', or '''-N'''.

|-
|
viewexlog

|
Provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output all at once:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output one screen at a time:

 Syntax: '''viewexlog'''

|}

 

 Footnote 1: DNS = Domain Name System

 Footnote 2: NTP = Network Time Protocol

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module

=== Operating System Commands for the Application Server ===

In addition to the commands listed in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Operating_System_Commands_for_the_Application_Server|Table: Command Reference: Operating System Commands for the Application Server]], the CLI supports the standard Linux operating system commands. You can use the '''vim''' command to view or modify text files if necessary.

 These are the requirements and restrictions for operating system commands:

*With the exception of the '''mpx_sys''' command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands might cause unpredictable results.
*If you are not signed in as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user, you must enter '''sudo''' before you can run any of these commands. For example, to stop all application services, go to the command line and enter this command:

:'''sudo ./mpx_app stop'''
:The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, instead enter this command:
:'''sudo /etc/init.d/mpx_app stop'''

*Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies:
**To the '''mpx_app''', '''mpx_sys''', and '''mpx_va''' commands.
**If the Application Server crashes and is reloaded.
**If you enter the '''shutdown''' or '''reboot''' Linux command on the Application Server.

 

===== Table: Command Reference: Operating System Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
mpx_app

|
Starts, stops, or restarts all Cisco Unified MeetingPlace application services.

 Syntax: '''mpx_app''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_axlds

|
Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager.

 Syntax: '''mpx_axlds''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_db

|
Starts, stops, or restarts Cisco Unified MeetingPlace database services.

 Syntax: '''mpx_db''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_lm

|
Starts, stops, or restarts Cisco Unified MeetingPlace license manager services.

 Syntax: '''mpx_lm''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rmi

|
Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging.

 Syntax: '''mpx_rmi''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rssctrl

|
Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service.

 Syntax: '''mpx_rssctrl''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_snmp

|
Starts, stops, or restarts SNMP services.

 Syntax: '''mpx_snmp''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_sys

|
Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

'''Note: ''' If the restart process is interrupted, you will have to reenter the '''mpx_sys restart''' command. For example, the restart process might be interrupted by a power outage, by closing the SSH connection, or by another restart process that is initiated from a different terminal.

 Syntax: '''mpx_sys''' {'''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcat

|
Starts, stops, or restarts Apache Tomcat services.

 Syntax: '''mpx_tomcat''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcatmon

|
Starts, stops, or restarts Apache Tomcat monitoring services.

 Syntax: '''mpx_tomcatmon''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_va

|
Starts, stops, or restarts Media Server services on the Application Server.

 If all other Cisco Unified MeetingPlace services continue running, then entering this command does ''not'' interrupt meetings that are active.

 Syntax: '''mpx_va''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_version

|
Lists all installed versions of Cisco Unified MeetingPlace.

 Syntax: '''mpx_version '''

|-
|
mpx_webx

|
Starts, stops, or restarts all Cisco WebEx integration services on the Application Server.

 Syntax: '''mpx_webx''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
resetmsapassword

|
Resets the Hardware Media Server Administration password to "cisco".

 Syntax: '''resetmsapassword'''

|-
|
shutdown

|
Shuts down the Application Server.

 For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters.

 Syntax: '''shutdown -h now'''

|}

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module
*[[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing_the_Media_Server_Administration_Password_for_the_Hardware_Media_Server|Changing the Media Server Administration Password for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing_Values_for_the_Hardware_Media_Server|Changing Values for the Hardware Media Server]] module

=== Database Replication Commands for the Application Server ===

'''Note: ''' To enter the database replication commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Database_Replication_Commands_for_the_Application_Server|Table: Command Reference: Database Replication Commands for the Application Server]]:

*The MeetingPlace Database services must be running on the Application Server.
*You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user.

 The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>.

 

===== Table: Command Reference: Database Replication Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
mp_replication init

|
Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication.

 Syntax: '''mp_replication init -s''' ''site'' '''-n''' ''node'' ['''-l''' ''local-server''] '''-r''' ''remote-server'' {'''-h''' | '''-m'''} ['''-v''']

 Parameters:

*'''-s''' ''site''-Specifies the site of the node on which you run this command. Valid values for ''site'' are 1 and 2.
*'''-n''' ''node''-Specifies the node (within the specified site) on which you run the command. Valid values for ''node'' are 1 and 2.
*'''-l''' ''local-server''-(Optional) Specifies the hostname or IP address of the Application Server on which you run this command.

:For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.
:By default, the (eth0 hostname) value returned by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#hostname|hostname]] command is used.

*'''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.
*'''-h''' -- Specifies intra-site replication, which is used for replication between the active and standby Application Server in a single-site active/standby failover deployment.
*'''-m''' -- Specifies inter-site replication, which is used for replication between two singleServer mode Application Servers (i.e, site 1 and site 2) in Reservationless Single Number Access (RSNA) deployment.
*'''-v'''-Specifies verbose output.

|-
|
mp_replication switchON

|
Starts replication between two Application Servers.

*Run this command on node 1 only.
*Run this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command on each node involved in replication.

 Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v''']

 Parameters:

*'''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.

:For intra-site replication, which is used for Application Server failover, specify the hostname or IP address of the virtual network interface eth0:0.

*'''-S''' '''-F''' ''data-source-server''-Indicates data synchronization between the two Application Servers.

:'''NOTE:''' Both Application Servers must be in standby mode when the '''-S''' '''-F''' options are used.
:For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.

*'''-v'''-Specifies verbose output.

|-
|
mp_replication status

|
Displays the status of replication between the specified servers.

 Syntax: '''mp_replication status''' ['''-v''']

 Parameter: '''-v'''-Specifies verbose output.

 In the output, if the replication is not working, the queue size will be either a fixed value or keep increasing with database changes in any server.

 The State shows the connection status, for example, dropped, disconnected, and so forth.

|-
|
mp_replication switchOFF

|
Stops replication, but does not restore configuration changes.

*Run this command on node 1 only.
*To restart replication, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_switchON|mp_replication switchON]] command.
*To restore the configuration changes done by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_teardown|mp_replication teardown]] command.

 Syntax: '''mp_replication switchOFF''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command. Exception:

*'''-f'''-Specifies to remove the local server from replication even in the following cases:
**Specified remote server is not part of replication.
**Local server is not in replication with any other servers.

|-
|
mp_replication teardown

|
Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes.

 Syntax: '''mp_replication teardown''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command.

|}

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring_Cisco_Unified_MeetingPlace_Directory_Service|Configuring Cisco Unified MeetingPlace Directory Service]] module
*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

 

=== Failover Commands for the Application Server ===

'''Note: ''' You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user to enter the failover commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Failover_Commands_for_the_Application_Server|Table: Command Reference: Failover Commands for the Application Server]].

 

===== Table: Command Reference: Failover Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
failoverUtil copyConfigFiles

|
Transfers configuration files from one Application Server to the other, specifically:

#Compresses the configuration files and user prompts on the local server.
#Transfers the compressed files to the remote server.

 After you enter this command on the local server, you need to enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] on the remote server.

 The following files and directories are transferred by this command:

*Directory Service:
**/opt/cisco/meetingplace/axlds/current/etc/config.properties
*Recorded user names and custom voice prompts:
**Everything under /opt/cisco/meetingplace/afs/custom
*Microsoft Outlook integration files:
**Everything under /opt/cisco/meetingplace/var/outlook
**/opt/cisco/meetingplace/var/admin/outlook.config
**Everything under /opt/cisco/meetingplace/var/mail
*Cisco WebEx integration files:
**/usr/local/enrollment
**/opt/cisco/meetingplace/web/current/etc/conf/keyinfo.properties
**/opt/cisco/meetingplace/web/current/etc/conf/keystore.jks
**/opt/cisco/meetingplace/web/current/etc/conf/cert.cer
**/opt/cisco/meetingplace/web/current/bases/main/conf/server.xml

 Syntax: '''failoverUtil copyConfigFiles'''

|-
|
failoverUtil restoreConfigFiles

|
Completes the transfer of configuration files from one Application Server to the other, specifically:

#Decompresses the configuration files and user prompts that were transferred from the remote server.
#Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server.

'''Note: ''' The failoverUtil copyConfigFiles and failoverUtil restoreConfigFiles commands are entered on separate Application Servers.

 Syntax: '''failoverUtil restoreConfigFiles'''

|-
|
failoverUtil setDeployment failover

|
Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway.

 Syntax: '''failoverUtil setDeployment failover'''

|-
|
failoverUtil setDeployment singleServer

|
Restores a failover-deployed Application Server to a single-server deployment.

 Syntax: '''failoverUtil setDeployment singleServer'''

|-
|
failoverUtil setServer

|
Sets a failover-deployed Application Server to either active or standby mode.

 Enter this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil_setDeployment_failover|failoverUtil setDeployment failover]] command on the server.

'''Note: ''' The mode setting might not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, sign in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the '''mpx_sys''' '''restart''' command, followed by the '''failoverUtil setServer''' command.

 Syntax: '''failoverUtil setServer''' {'''active''' | '''standby'''}

|-
|
failoverUtil status

|
Displays the current modes of the Application Server, specifically:

*Whether the server is deployed for failover or as a single server.
*If deployed for failover, then whether the server is in active or standby mode.

 Syntax: '''failoverUtil status'''

|}

 

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

[[Category:Reference_Information_for_Cisco_Unified_MeetingPlace_Release_8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server

2012-04-10T23:09:04Z

Dunn:

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

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

 

 

You can use the command-line interface (CLI) on the Application Server to perform functions that cannot be performed in the Administration Center. 

== ==

== '''CAUTION''' : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks and functions, and is not designed for use as a persistent operating environment monitoring tool. If you need to perform persistent continuous monitoring please consult Cisco TAC or your Cisco Professional Services partners for further guidance. ==

 

'''Note: ''' The CLI on the Application Server is not the same as the CLI on the Cisco WebEx Node for MCS. For information about the latter, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS#Using_the_Command-Line_Interface_.28CLI.29_on_the_Cisco_WebEx_Node_for_MCS|Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS]] module.

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#CLI_User_Level_Options_on_the_Application_Server|CLI User Level Options on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Restrictions_for_the_CLI_on_the_Application_Server|Restrictions for the CLI on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#How_to_Sign_in_to_the_CLI_on_the_Application_Server|How to Sign in to the CLI on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

 

== CLI User Level Options on the Application Server ==

{| border="1"
|-
! CLI User Level
! Description
|-
|
mpxadmin

|
We recommend that you use this user level whenever possible.

|-
|
root

|
Highest authority, enabling you to do the following:

*Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]], though pseudo (sudo) root access can also be used.
*Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database_Replication_Commands_for_the_Application_Server|Database Replication Commands for the Application Server]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover_Commands_for_the_Application_Server|Failover Commands for the Application Server]].
*Reset the root or mpxadmin user passwords.
*Uninstall the system.

 To get to the root user level, do one of the following:

*Sign in as the mpxadmin user, and enter '''su''' at the command line.
*Sign in directly as the root user-this is possibly only by [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]].

'''Caution! ''' For security reasons, we do not recommend signing in directly as the root user, unless you need to reset the root user or mpxadmin user passwords or uninstall the system.

|}

 

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Password Recovery for the Cisco Unified MeetingPlace Application Server#Password_Recovery_for_the_Cisco_Unified_MeetingPlace_Application_Server|Password Recovery for the Cisco Unified MeetingPlace Application Server]] module

 

== Restrictions for the CLI on the Application Server ==

*The CLI and its commands are available only in English.
*The CLI accepts only the standard 128 ASCII characters.
*Many commands you enter might prompt you for information. If the Backspace key does not delete characters in this interactive mode, use one of the following options:
**Press the '''Delete''' key to delete the previous character.
**Press '''Ctrl-W''' to delete the previous word.
**Press '''Ctrl-U''' to delete the entire line.

 

== How to Sign in to the CLI on the Application Server ==

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]

 

=== Signing in to the CLI on the Application Server By Using the Console ===

You can sign in to the CLI from the console by using either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] usernames. ''This is the only way you can sign in directly as the root user.'' You can enter operating system commands here.

 

===== Procedure =====

#Connect the monitor, keyboard, and mouse to the Application Server.
#:The Cisco Unified MeetingPlace operating system sign-in page is displayed.
#For the username, enter '''mpxadmin'''.
#Enter the password for the mpxadmin user.
#:This was established during installation.
#Right-click the desktop and select '''Open Terminal'''.
#:A command window appears. You can start entering commands. This is a Linux operating system so all commands should be either Linux commands or Cisco Unified MeetingPlace operating system commands. See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]] for information about the operating system commands.
#When you are finished with the command window, either enter '''exit''' or select the '''X''' in the top right corner.
#:'''Note: ''' Always sign out of the Cisco Unified MeetingPlace operating system when you are finished.

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

 

=== Signing in to the CLI on the Application Server By Using SSH ===

This section provides one method of signing in to the CLI by using SSH. Other methods might be available for you.

 

===== Restriction =====

Only the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] user can sign in to the CLI remotely using SSH. If needed, you can later switch to the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user by entering '''su'''.

 

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

You need a remote connection with a non-configurable terminal emulation program, such as the Windows SSH client, to sign in to the CLI remotely using SSH.

 

===== Procedure =====

#From your computer, go to '''Start > Programs > SSH Secure Shell > Secure Shell Client'''.
#Select '''Quick Connect'''.
#In the Connect to Remote Host window, enter these values:

 

{| border="1"
|-
! Field
! Value
|-
|
Host Name

|
IP address of your Cisco Unified MeetingPlace system

|-
|
User Name

|
mpxadmin

|-
|
Port Number

|
22

|-
|
Authentication Method

|
leave as <Profile Settings>

|}

 

:4. Select '''Connect'''.
:5. In the Enter Password window, enter the password for the mpxadmin user.
::This was established during installation.
:6. Select '''OK'''.
::The system displays the command line, and you can now enter commands.

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

== Application Server Command Reference ==

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Command_Syntax_Conventions|Command Syntax Conventions]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Commands_for_the_Application_Server|Application Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database_Replication_Commands_for_the_Application_Server|Database Replication Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover_Commands_for_the_Application_Server|Failover Commands for the Application Server]]

 

=== Command Syntax Conventions ===

This document uses these command syntax conventions.

 

{| border="1"
|-
! Convention
! Description
|-
|
'''bold'''

|
Bold text indicates commands and parameters that you enter as shown.

|-
|
''italic''

|
Italic text indicates parameters for which you supply values.

|-
|
<x>

|
Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters.

|-
|
[x]

|
Square brackets enclose an optional parameter.

|-
|
<nowiki> | </nowiki>

|
A vertical line, called a pipe, indicates a choice within a set of parameters.

|-
|
[x | y]

|
Square brackets enclosing parameters separated by a pipe indicate an optional choice.

|-
|
{x | y}

|
Braces enclosing parameters separated by a pipe indicate a required choice.

|-
|
[x {y | z}]

|
Braces and a pipe within square brackets indicate a required choice within an optional element.

|}

=== Application Commands for the Application Server ===

===== Table: Command Reference: Application Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
activity

|
Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings.

 Syntax: '''activity'''

|-
|
alarm

|
Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm_Table|Alarm Table]]:

*REFNO-Reference number used with the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#clearalarm|clearalarm]] command to clear a specific alarm table entry.
*SEV-Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm_Severity_Levels|Alarm Severity Levels]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.
*CODE-See Code.
*COUNT -See Count.
*FIRST-See First Time.
*LAST-See Last Time.
*UNIT-See Unit.
*SW MODULE-See Software Module.

'''Note: ''' The brief description in the alarm table entry might contain values that are specific to one alarm occurrence, such as an IP address. These values might differ in all alarms that are combined into one table entry, but only the values for the ''most recent ''alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command.

 Syntax: '''alarm'''

|-
|
ccamon

|
Monitors the Call Control Agent. Allows you to view the call statistics and set the log tracing level.

 Syntax: '''ccamon'''

|-
|
checklic

|
Shows the type and number of licenses installed.

'''Note: ''' The system can take up to 15 seconds to process this information.

 Syntax: '''checklic'''

|-
|
clearalarm

|
Clears either all the alarms in the alarm table or just the alarm specified.

 If there are any major alarms in the alarm table, the system can be configured to call the system administrator after every restart until all major alarms are deleted from the alarm table. See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Configuring_the_System_to_Call_You_If_There_is_a_Major_Alarm|Configuring the System to Call You If There is a Major Alarm]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.

 Running this command stops the system from calling the system administrator (if it has been configured to do so).

 Syntax: '''clearalarm''' {''reference-number'' | '''all'''}

|-
|
cleardb

|
Clears the following Application Server data:

*All user profiles except the admin and guest user profiles
*All user groups except the System group
*All user recordings
*All conference recordings

You must be signed in to the Application Server CLI as the root user to enter this command.

Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns.

'''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command.

Syntax: '''cleardb'''

|-
|
cpstatus

|
Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video.

 Syntax: '''cpstatus'''

|-
|
cptrace

|
Lists selected portions of the call processing trace log.

 Syntax: '''cptrace'''

|-
|
date

|
Displays the time and date for the Application Server.

 If you are signed in as a root user, you can also set the date and time based on the local time zone.

 Syntax: '''date''' [''MMDDhhmm''[''YYYY'']['''.'''''ss'']]

 Parameters (available only to root users):

*''MM''-month, specified by two digits
*''DD''-day, specified by two digits
*''hh''-hour, specified by two digits in 24-hour format
*''mm''-minute, specified by two digits
*''YYYY''-calendar year, specified by four digits
*'''.'''''ss''-second, specified by two digits and a preceding period (.)

|-
|
dbupdate

|
Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group.

'''Caution! ''' Deleting all database entries is an irreversible operation. Before you run the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#dbupdate|dbupdate]] command, consider backing up and archiving the database. See [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing_Up.2C_Archiving.2C_and_Restoring_Data_on_the_Cisco_Unified_MeetingPlace_Application_Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

 Use this command only in these situations:

*Cisco TAC instructs you to do so.
*You configured Directory Service on your system, and you need to change the LDAP directory with which Cisco Unified Communications Manager is integrated. If you do not clear the database before switching from one LDAP directory to another, all user profiles from the first LDAP directory will remain in the Cisco Unified MeetingPlace database until you manually delete them.

:The automatic Directory Service deletion of user profiles does not apply when you change the LDAP directory. For details about when and how the system automatically deletes Directory Service user profiles, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory_Service_User_Profile_Deletion|Directory Service User Profile Deletion]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring_Cisco_Unified_MeetingPlace_Directory_Service|Configuring Cisco Unified MeetingPlace Directory Service]] module.

|-
|
errorlog

|
Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output one screen at a time:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output all at once.

 Syntax: '''errorlog'''

|-
|
eventlog

|
Displays the system event log.

'''Note: ''' This command has many parameter options; only the most commonly used parameters are listed below.

 Syntax: '''eventlog''' ['''-b''' [''YY''][''MMDD'']''hhmm''] ['''-e''' [''YY''][''MMDD'']''hhmm''] ['''-G''' | '''-C'''] ['''-t'''] ['''| more''']

 Parameters:

*'''-b'''-Specifies a start time for the log events to include in the output.
*'''-e'''-Specifies an end time for the log events to include in the output.

'''Note: ''' To show events for the current day, you can omit the ''YY'', ''MM'', and ''DD'' parameters from the start and end times.

*''YY''-Calendar year, specified by two digits. Typically, this parameter is included only when troubleshooting issues around the start of a new calendar year.
*''MM''-month, specified by two digits
*''DD''-day, specified by two digits
*''hh''-hour, specified by two digits in 24-hour format
*''mm''-minute, specified by two digits
*'''-G'''-Shows the telephony and conference events and control messages from the Call Processing-Media Control Protocol (CPMCP) component, which is a proxy for the Media Server.
*'''-C'''-Limits log output to events for the conference scheduler (ConfSchd) component.
*'''-t'''-Displays the log output in real time. This option is useful for troubleshooting issues in real time. For example, you can enter '''eventlog -G -t''' and then place a test call to the system to see how the system responds to the incoming call and to any subsequent user input.
*'''| more'''-Displays the log output one screen at a time.

|-
|
exc

|
Displays the meaning of an exception code that was listed in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command output.

 Syntax: '''exc''' ['''-v'''] ''exception-code''

|-
|
hostname

|
Displays the hostname of the Application Server.

 Syntax: '''hostname'''

|-
|
infocap

|
Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information.

 Restrictions:

*You must be signed in as the root user to run this command.
*You can also get this information by completing [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Obtaining_and_Viewing_the_System_Information_Capture_.28Infocap.29_Log|Obtaining and Viewing the System Information Capture (Infocap) Log]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module. Use this command only if you are unable to get the information from the Cisco Unified MeetingPlace Administration Center.
*The begin and end dates and times must be in the format [YY]MMDDhhmm. The YY is optional and if not specified, the system uses the current year. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

 Syntax: '''infocap -b''' ''begin-date-and-time'' '''-e''' ''end-date-and-time''

|-
|
infocapmtg

|
Gathers a system information capture file around the time of a meeting.

 Syntax: '''infocapmtg''' [''meetingID''] ['''-S | -P | -B'''''minutes''] ['''-n''' ''username | '''''-p''' ''profilename''] ['''-b''' ''beginning-time'' '''-e''' ''ending-time'']

 Parameters:

*''meetingID''-Captures information about a specific meeting ID.
*'''-S'''-Captures information about the specified meeting ID when it was scheduled.
*'''-P'''-Stops the capture when the meeting was purged.
*'''-B''' ''minutes''-Adds a buffer of minutes before or after the start or stop of the capture.
*'''-n''' ''username''-Captures information about the first meeting where the specified user was a participant.
*'''-p''' ''profilename''-Captures information about the first meeting where the specified user profile was a participant.
*'''-b''' ''beginning-time'' '''-e''' ''ending-time''-Captures information about the meeting between the beginning and ending time.

 Examples:

 '''infocapmtg 1212''' Gathers a system information capture file starting at the time meeting 1212 began and ending when meeting 1212 ended.

 '''infocapmtg 1212 -S''' Gathers a system information capture file starting at the time someone scheduled meeting 1212 and ending when meeting 1212 ended.

 '''infocapmtg 1212 -B 5''' Gathers a system information capture file starting 5 minutes before meeting 1212 began and ending 5 minutes after meeting 1212 ended.

 '''infocapmtg -n''' ''username'' '''-b 0950 -e 1400''' Gathers a system information capture file starting for a meeting scheduled by or attended by ''username'' where the meeting started between 9:50 a.m. and 2:00 p.m. today.

|-
|
langinfo

|
Displays information about all installed locales including the following:

*Locale ID
*Language code
*Locale order
*Locale name
*Country code
*Locale version number

 Syntax: '''langinfo'''

|-
|
mtginfo

|
Displays information about a specific meeting. Searches for a meeting based on any of these:

*Unique conference ID (such as 125). (This number is output by certain commands such as '''cptrace -C''' and '''errorlog'''. It uniquely identifies a meeting.)
*Meeting ID (such as 1278). Can optionally use any of the time arguments.
*Unique user ID (such as 0x65). (This number is output by certain commands such as [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#userinfo|userinfo]]. It uniquely identifies a user.) Searches for all meetings that a user has attended or been invited to.
*Activity. Searches only for active meetings.
*Time. Searches for all meetings valid at a certain time with the -t argument or between two times when the -s and -e arguments are used together.

 Syntax: '''mtginfo''' '''-a''' ''time'' '''-c''' ''unique-conf-id'' '''-e''' ''end-time'' '''-m''' ''meeting-id'' '''-s''' ''start-time'' '''-t''' ''time'' '''-u''' ''unique-user-id''

'''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

'''Note: ''' Start and end times in the command output are adjusted for the Meeting ID start guard time (minutes) and Meeting ID end guard time (minutes) fields on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting_Configuration_Page|Meeting Configuration Page]].

 Examples:

 '''mtginfo -m 1234 '''Looks for the meeting with the ID of 1234 at the current time

 '''mtginfo -m 1234 -t 11 '''Looks for meeting with the ID of 1234 at 11 minutes after the current hour

 '''mtginfo -m 1234 -t 1111111111 '''Looks for meeting with the ID of 1234 at 11:11am on Nov 11, 2011

 '''mtginfo -a 1430 '''Looks for meetings that are active at 2:30pm today

 '''mtginfo -s 1430 -e 1530 '''Looks for meetings that started or ended between 2:30 and 3:30pm today

 '''mtginfo -c 123 '''Looks for meeting with the unique conference ID of 123

 '''mtginfo -u 123 -t 1111 -e 1211 '''Looks for meetings that the user with the unique user ID of 123 is invited to between 11:11 and 12:11 today

|-
|
net

|
Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system.

 You must be signed in as root before running this command.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

 Use the '''net''' command to set the following:

*Port configuration parameters, including:
**Application Server (eth0) hostname, IP address, subnet mask, and default gateway
**Virtual (eth0:0) hostname, IP address, subnet mask, and default gateway-the eth0:0 virtual interface is used in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]] deployments
**MTU and link parameters (auto-negotiation, speed, duplex).
*Domain name
*DNS servers
*NTP servers

'''Note: ''' If you change the Application Server hostname (for eth0), then you must also perform these actions:

**Configure the DNS (1) server to point the old hostname to the new hostname.
**Restart the application by entering either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#'''mpx_sys|mpx_sys]]''''''restart''' operating system command or the '''reboot''' Linux command.
**If you enabled SSL for the Application Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Generating_a_Certificate_Signing_Request_and_Obtaining_the_Certificate|Generating a Certificate Signing Request and Obtaining the Certificate]] and [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Uploading_the_Certificate_File_and_Enabling_SSL|Uploading the Certificate File and Enabling SSL]] sections in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Configuring_SSL_for_the_Cisco_Unified_MeetingPlace_Application_Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]] module.
**If you installed MeetingPlace Conference Manager, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Editing_an_Existing_Server|Editing an Existing Server]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using_MeetingPlace_Conference_Manager|Using MeetingPlace Conference Manager]] module.
**If your system includes a Web Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Changing_the_Cisco_Unified_MeetingPlace_Application_Server_Connection_Configured_in_the_Gateway_SIM|Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Configuring_the_Cisco_Unified_MeetingPlace_Gateway_System_Integrity_Manager|Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager]] module.
**If you integrated the system with Cisco WebEx, notify the Cisco WebEx administrator to update the Cisco Unified MeetingPlace hostname that is configured in the Cisco WebEx license manager.

 Syntax: '''net'''

|-
|
ntpdate

|
Sets the Application Server date and time to match the time obtained by polling an NTP (2) server.

 Syntax: '''ntpdate''' ['''-u'''] ''ntp-server''

 Parameters:

*'''-u'''-Specifies to send packets through an unprivileged port to communicate with the NTP server. Use this option when you want to reach an NTP server that is beyond a firewall.
*''ntp-server''-Hostname or IP address of the NTP server.

|-
|
swstatus

|
Displays information about Cisco Unified MeetingPlace, including the following:

*Version number
*System mode
*Status of the power supplies
*List of software modules loaded in to memory, their version number, and their status

 Syntax: '''swstatus'''

|-
|
taccli

|
Displays details on the mixer status, active meetings, participant details, and general statistics, including the following:

*Cisco Unified MeetingPlace request statistics
*Statistics or status for one or all channels
*Statistics or details for one or all conferences
*Mixer status, request failures, and mixer return code table
*Video resolution and frame rate of each connection that is made to the Express Media Server

 Also does the following:

*Resets Cisco Unified MeetingPlace request statistics
*Enables and disables tracing
*Shows the current date and time
*Starts and stops channel RTP recording

 Syntax: '''taccli'''

|-
|
techui

|
Displays statistics for the Media Server, ports, and conferences.

 This technician user interface helps to diagnose and troubleshoot media and voice quality issues of active calls.

 Syntax: '''techui'''

|-
|
userinfo

|
Displays information about a specific user. Searches for a user based on any of these:

*User ID
*Profile number
*Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user.

 Syntax: '''userinfo''' {''user-id'' | ''profile-number'' | ''unique-user-id''}

|-
|
userutil

|
Performs administrative functions for any user profile.

 Restriction: You cannot set the admin user to inactive, locked, or the group default.

 Syntax: '''userutil''' {'''-q''' | ['''-p''' | '''-P] '''['''-n''' | '''-N] '''['''-a''' | '''-i''' | '''-l''' | '''-g]'''} ''userid'' [''password'']

 Parameters:

*'''-q'''-Displays user profile information and status.
*'''-p'''-Reset the User password. Requires a ''password'' entry.
*'''-P'''-Reset the User password and force it to expire. This forces the user to change the password at the next sign-in attempt. Requires a ''password'' entry.
*'''-n'''-Reset the Profile PIN (PIN for authentication over the phone). Requires a ''password'' entry.
*'''-N'''-Reset the Profile PIN and force it to expire. Requires a ''password'' entry.
*'''-a'''-Set User status to active.
*'''-i'''-Set User status to inactive.
*'''-l'''-Set User status to locked.
*'''-g'''-Set User status to group default setting.
*''userid''-User ID.
*''pasword''-New User password or Profile PIN. Required if you enter '''-p''', '''-P''', '''-n''', or '''-N'''.

|-
|
viewexlog

|
Provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output all at once:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output one screen at a time:

 Syntax: '''viewexlog'''

|}

 

 Footnote 1: DNS = Domain Name System

 Footnote 2: NTP = Network Time Protocol

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module

=== Operating System Commands for the Application Server ===

In addition to the commands listed in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Operating_System_Commands_for_the_Application_Server|Table: Command Reference: Operating System Commands for the Application Server]], the CLI supports the standard Linux operating system commands. You can use the '''vim''' command to view or modify text files if necessary.

 These are the requirements and restrictions for operating system commands:

*With the exception of the '''mpx_sys''' command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands might cause unpredictable results.
*If you are not signed in as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user, you must enter '''sudo''' before you can run any of these commands. For example, to stop all application services, go to the command line and enter this command:

:'''sudo ./mpx_app stop'''
:The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, instead enter this command:
:'''sudo /etc/init.d/mpx_app stop'''

*Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies:
**To the '''mpx_app''', '''mpx_sys''', and '''mpx_va''' commands.
**If the Application Server crashes and is reloaded.
**If you enter the '''shutdown''' or '''reboot''' Linux command on the Application Server.

 

===== Table: Command Reference: Operating System Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
mpx_app

|
Starts, stops, or restarts all Cisco Unified MeetingPlace application services.

 Syntax: '''mpx_app''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_axlds

|
Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager.

 Syntax: '''mpx_axlds''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_db

|
Starts, stops, or restarts Cisco Unified MeetingPlace database services.

 Syntax: '''mpx_db''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_lm

|
Starts, stops, or restarts Cisco Unified MeetingPlace license manager services.

 Syntax: '''mpx_lm''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rmi

|
Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging.

 Syntax: '''mpx_rmi''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rssctrl

|
Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service.

 Syntax: '''mpx_rssctrl''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_snmp

|
Starts, stops, or restarts SNMP services.

 Syntax: '''mpx_snmp''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_sys

|
Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

'''Note: ''' If the restart process is interrupted, you will have to reenter the '''mpx_sys restart''' command. For example, the restart process might be interrupted by a power outage, by closing the SSH connection, or by another restart process that is initiated from a different terminal.

 Syntax: '''mpx_sys''' {'''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcat

|
Starts, stops, or restarts Apache Tomcat services.

 Syntax: '''mpx_tomcat''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcatmon

|
Starts, stops, or restarts Apache Tomcat monitoring services.

 Syntax: '''mpx_tomcatmon''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_va

|
Starts, stops, or restarts Media Server services on the Application Server.

 If all other Cisco Unified MeetingPlace services continue running, then entering this command does ''not'' interrupt meetings that are active.

 Syntax: '''mpx_va''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_version

|
Lists all installed versions of Cisco Unified MeetingPlace.

 Syntax: '''mpx_version '''

|-
|
mpx_webx

|
Starts, stops, or restarts all Cisco WebEx integration services on the Application Server.

 Syntax: '''mpx_webx''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
resetmsapassword

|
Resets the Hardware Media Server Administration password to "cisco".

 Syntax: '''resetmsapassword'''

|-
|
shutdown

|
Shuts down the Application Server.

 For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters.

 Syntax: '''shutdown -h now'''

|}

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module
*[[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing_the_Media_Server_Administration_Password_for_the_Hardware_Media_Server|Changing the Media Server Administration Password for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing_Values_for_the_Hardware_Media_Server|Changing Values for the Hardware Media Server]] module

=== Database Replication Commands for the Application Server ===

'''Note: ''' To enter the database replication commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Database_Replication_Commands_for_the_Application_Server|Table: Command Reference: Database Replication Commands for the Application Server]]:

*The MeetingPlace Database services must be running on the Application Server.
*You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user.

 The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>.

 

===== Table: Command Reference: Database Replication Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
mp_replication init

|
Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication.

 Syntax: '''mp_replication init -s''' ''site'' '''-n''' ''node'' ['''-l''' ''local-server''] '''-r''' ''remote-server'' {'''-h''' | '''-m'''} ['''-v''']

 Parameters:

*'''-s''' ''site''-Specifies the site of the node on which you run this command. Valid values for ''site'' are 1 and 2.
*'''-n''' ''node''-Specifies the node (within the specified site) on which you run the command. Valid values for ''node'' are 1 and 2.
*'''-l''' ''local-server''-(Optional) Specifies the hostname or IP address of the Application Server on which you run this command.

:For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.
:By default, the (eth0 hostname) value returned by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#hostname|hostname]] command is used.

*'''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.
*'''-h''' -- Specifies intra-site replication, which is used for replication between the active and standby Application Server in a single-site active/standby failover deployment.
*'''-m''' -- Specifies inter-site replication, which is used for replication between two singleServer mode Application Servers (i.e, site 1 and site 2) in Reservationless Single Number Access (RSNA) deployment.
*'''-v'''-Specifies verbose output.

|-
|
mp_replication switchON

|
Starts replication between two Application Servers.

*Run this command on node 1 only.
*Run this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command on each node involved in replication.

 Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v''']

 Parameters:

*'''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.

:For intra-site replication, which is used for Application Server failover, specify the hostname or IP address of the virtual network interface eth0:0.

*'''-S''' '''-F''' ''data-source-server''-Indicates data synchronization between the two Application Servers.

:'''NOTE:''' Both Application Servers must be in standby mode when the '''-S''' '''-F''' options are used.
:For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.

*'''-v'''-Specifies verbose output.

|-
|
mp_replication status

|
Displays the status of replication between the specified servers.

 Syntax: '''mp_replication status''' ['''-v''']

 Parameter: '''-v'''-Specifies verbose output.

 In the output, if the replication is not working, the queue size will be either a fixed value or keep increasing with database changes in any server.

 The State shows the connection status, for example, dropped, disconnected, and so forth.

|-
|
mp_replication switchOFF

|
Stops replication, but does not restore configuration changes.

*Run this command on node 1 only.
*To restart replication, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_switchON|mp_replication switchON]] command.
*To restore the configuration changes done by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_teardown|mp_replication teardown]] command.

 Syntax: '''mp_replication switchOFF''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command. Exception:

*'''-f'''-Specifies to remove the local server from replication even in the following cases:
**Specified remote server is not part of replication.
**Local server is not in replication with any other servers.

|-
|
mp_replication teardown

|
Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes.

 Syntax: '''mp_replication teardown''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command.

|}

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring_Cisco_Unified_MeetingPlace_Directory_Service|Configuring Cisco Unified MeetingPlace Directory Service]] module
*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

 

=== Failover Commands for the Application Server ===

'''Note: ''' You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user to enter the failover commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Failover_Commands_for_the_Application_Server|Table: Command Reference: Failover Commands for the Application Server]].

 

===== Table: Command Reference: Failover Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
failoverUtil copyConfigFiles

|
Transfers configuration files from one Application Server to the other, specifically:

#Compresses the configuration files and user prompts on the local server.
#Transfers the compressed files to the remote server.

 After you enter this command on the local server, you need to enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] on the remote server.

 The following files and directories are transferred by this command:

*Directory Service:
**/opt/cisco/meetingplace/axlds/current/etc/config.properties
*Recorded user names and custom voice prompts:
**Everything under /opt/cisco/meetingplace/afs/custom
*Microsoft Outlook integration files:
**Everything under /opt/cisco/meetingplace/var/outlook
**/opt/cisco/meetingplace/var/admin/outlook.config
**Everything under /opt/cisco/meetingplace/var/mail
*Cisco WebEx integration files:
**/usr/local/enrollment
**/opt/cisco/meetingplace/web/current/etc/conf/keyinfo.properties
**/opt/cisco/meetingplace/web/current/etc/conf/keystore.jks
**/opt/cisco/meetingplace/web/current/etc/conf/cert.cer
**/opt/cisco/meetingplace/web/current/bases/main/conf/server.xml

 Syntax: '''failoverUtil copyConfigFiles'''

|-
|
failoverUtil restoreConfigFiles

|
Completes the transfer of configuration files from one Application Server to the other, specifically:

#Decompresses the configuration files and user prompts that were transferred from the remote server.
#Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server.

'''Note: ''' The failoverUtil copyConfigFiles and failoverUtil restoreConfigFiles commands are entered on separate Application Servers.

 Syntax: '''failoverUtil restoreConfigFiles'''

|-
|
failoverUtil setDeployment failover

|
Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway.

 Syntax: '''failoverUtil setDeployment failover'''

|-
|
failoverUtil setDeployment singleServer

|
Restores a failover-deployed Application Server to a single-server deployment.

 Syntax: '''failoverUtil setDeployment singleServer'''

|-
|
failoverUtil setServer

|
Sets a failover-deployed Application Server to either active or standby mode.

 Enter this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil_setDeployment_failover|failoverUtil setDeployment failover]] command on the server.

'''Note: ''' The mode setting might not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, sign in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the '''mpx_sys''' '''restart''' command, followed by the '''failoverUtil setServer''' command.

 Syntax: '''failoverUtil setServer''' {'''active''' | '''standby'''}

|-
|
failoverUtil status

|
Displays the current modes of the Application Server, specifically:

*Whether the server is deployed for failover or as a single server.
*If deployed for failover, then whether the server is in active or standby mode.

 Syntax: '''failoverUtil status'''

|}

 

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

[[Category:Reference_Information_for_Cisco_Unified_MeetingPlace_Release_8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server

2012-04-10T22:59:50Z

Dunn:

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

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

 

 

== You can use the command-line interface (CLI) on the Application Server to perform functions that cannot be performed in the Administration Center. ==

== ==

== '''CAUTION''' : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks, and is not designed for use as persistent operating environment monitoring tool. If such a need exists please consult Cisco TAC or your Cisco Professional Services partners for further guidance. ==

'''Note: ''' The CLI on the Application Server is not the same as the CLI on the Cisco WebEx Node for MCS. For information about the latter, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS#Using_the_Command-Line_Interface_.28CLI.29_on_the_Cisco_WebEx_Node_for_MCS|Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS]] module.

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#CLI_User_Level_Options_on_the_Application_Server|CLI User Level Options on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Restrictions_for_the_CLI_on_the_Application_Server|Restrictions for the CLI on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#How_to_Sign_in_to_the_CLI_on_the_Application_Server|How to Sign in to the CLI on the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

 

== CLI User Level Options on the Application Server ==

{| border="1"
|-
! CLI User Level
! Description
|-
|
mpxadmin

|
We recommend that you use this user level whenever possible.

|-
|
root

|
Highest authority, enabling you to do the following:

*Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]], though pseudo (sudo) root access can also be used.
*Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database_Replication_Commands_for_the_Application_Server|Database Replication Commands for the Application Server]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover_Commands_for_the_Application_Server|Failover Commands for the Application Server]].
*Reset the root or mpxadmin user passwords.
*Uninstall the system.

 To get to the root user level, do one of the following:

*Sign in as the mpxadmin user, and enter '''su''' at the command line.
*Sign in directly as the root user-this is possibly only by [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]].

'''Caution! ''' For security reasons, we do not recommend signing in directly as the root user, unless you need to reset the root user or mpxadmin user passwords or uninstall the system.

|}

 

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Password Recovery for the Cisco Unified MeetingPlace Application Server#Password_Recovery_for_the_Cisco_Unified_MeetingPlace_Application_Server|Password Recovery for the Cisco Unified MeetingPlace Application Server]] module

 

== Restrictions for the CLI on the Application Server ==

*The CLI and its commands are available only in English.
*The CLI accepts only the standard 128 ASCII characters.
*Many commands you enter might prompt you for information. If the Backspace key does not delete characters in this interactive mode, use one of the following options:
**Press the '''Delete''' key to delete the previous character.
**Press '''Ctrl-W''' to delete the previous word.
**Press '''Ctrl-U''' to delete the entire line.

 

== How to Sign in to the CLI on the Application Server ==

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]

 

=== Signing in to the CLI on the Application Server By Using the Console ===

You can sign in to the CLI from the console by using either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] usernames. ''This is the only way you can sign in directly as the root user.'' You can enter operating system commands here.

 

===== Procedure =====

#Connect the monitor, keyboard, and mouse to the Application Server.
#:The Cisco Unified MeetingPlace operating system sign-in page is displayed.
#For the username, enter '''mpxadmin'''.
#Enter the password for the mpxadmin user.
#:This was established during installation.
#Right-click the desktop and select '''Open Terminal'''.
#:A command window appears. You can start entering commands. This is a Linux operating system so all commands should be either Linux commands or Cisco Unified MeetingPlace operating system commands. See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]] for information about the operating system commands.
#When you are finished with the command window, either enter '''exit''' or select the '''X''' in the top right corner.
#:'''Note: ''' Always sign out of the Cisco Unified MeetingPlace operating system when you are finished.

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_SSH|Signing in to the CLI on the Application Server By Using SSH]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

 

=== Signing in to the CLI on the Application Server By Using SSH ===

This section provides one method of signing in to the CLI by using SSH. Other methods might be available for you.

 

===== Restriction =====

Only the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] user can sign in to the CLI remotely using SSH. If needed, you can later switch to the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user by entering '''su'''.

 

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

You need a remote connection with a non-configurable terminal emulation program, such as the Windows SSH client, to sign in to the CLI remotely using SSH.

 

===== Procedure =====

#From your computer, go to '''Start > Programs > SSH Secure Shell > Secure Shell Client'''.
#Select '''Quick Connect'''.
#In the Connect to Remote Host window, enter these values:

 

{| border="1"
|-
! Field
! Value
|-
|
Host Name

|
IP address of your Cisco Unified MeetingPlace system

|-
|
User Name

|
mpxadmin

|-
|
Port Number

|
22

|-
|
Authentication Method

|
leave as <Profile Settings>

|}

 

:4. Select '''Connect'''.
:5. In the Enter Password window, enter the password for the mpxadmin user.
::This was established during installation.
:6. Select '''OK'''.
::The system displays the command line, and you can now enter commands.

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing_in_to_the_CLI_on_the_Application_Server_By_Using_the_Console|Signing in to the CLI on the Application Server By Using the Console]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Server_Command_Reference|Application Server Command Reference]]

== Application Server Command Reference ==

*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Command_Syntax_Conventions|Command Syntax Conventions]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application_Commands_for_the_Application_Server|Application Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating_System_Commands_for_the_Application_Server|Operating System Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database_Replication_Commands_for_the_Application_Server|Database Replication Commands for the Application Server]]
*[[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover_Commands_for_the_Application_Server|Failover Commands for the Application Server]]

 

=== Command Syntax Conventions ===

This document uses these command syntax conventions.

 

{| border="1"
|-
! Convention
! Description
|-
|
'''bold'''

|
Bold text indicates commands and parameters that you enter as shown.

|-
|
''italic''

|
Italic text indicates parameters for which you supply values.

|-
|
<x>

|
Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters.

|-
|
[x]

|
Square brackets enclose an optional parameter.

|-
|
<nowiki> | </nowiki>

|
A vertical line, called a pipe, indicates a choice within a set of parameters.

|-
|
[x | y]

|
Square brackets enclosing parameters separated by a pipe indicate an optional choice.

|-
|
{x | y}

|
Braces enclosing parameters separated by a pipe indicate a required choice.

|-
|
[x {y | z}]

|
Braces and a pipe within square brackets indicate a required choice within an optional element.

|}

=== Application Commands for the Application Server ===

===== Table: Command Reference: Application Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
activity

|
Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings.

 Syntax: '''activity'''

|-
|
alarm

|
Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm_Table|Alarm Table]]:

*REFNO-Reference number used with the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#clearalarm|clearalarm]] command to clear a specific alarm table entry.
*SEV-Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm_Severity_Levels|Alarm Severity Levels]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.
*CODE-See Code.
*COUNT -See Count.
*FIRST-See First Time.
*LAST-See Last Time.
*UNIT-See Unit.
*SW MODULE-See Software Module.

'''Note: ''' The brief description in the alarm table entry might contain values that are specific to one alarm occurrence, such as an IP address. These values might differ in all alarms that are combined into one table entry, but only the values for the ''most recent ''alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command.

 Syntax: '''alarm'''

|-
|
ccamon

|
Monitors the Call Control Agent. Allows you to view the call statistics and set the log tracing level.

 Syntax: '''ccamon'''

|-
|
checklic

|
Shows the type and number of licenses installed.

'''Note: ''' The system can take up to 15 seconds to process this information.

 Syntax: '''checklic'''

|-
|
clearalarm

|
Clears either all the alarms in the alarm table or just the alarm specified.

 If there are any major alarms in the alarm table, the system can be configured to call the system administrator after every restart until all major alarms are deleted from the alarm table. See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Configuring_the_System_to_Call_You_If_There_is_a_Major_Alarm|Configuring the System to Call You If There is a Major Alarm]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.

 Running this command stops the system from calling the system administrator (if it has been configured to do so).

 Syntax: '''clearalarm''' {''reference-number'' | '''all'''}

|-
|
cleardb

|
Clears the following Application Server data:

*All user profiles except the admin and guest user profiles
*All user groups except the System group
*All user recordings
*All conference recordings

You must be signed in to the Application Server CLI as the root user to enter this command.

Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns.

'''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command.

Syntax: '''cleardb'''

|-
|
cpstatus

|
Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video.

 Syntax: '''cpstatus'''

|-
|
cptrace

|
Lists selected portions of the call processing trace log.

 Syntax: '''cptrace'''

|-
|
date

|
Displays the time and date for the Application Server.

 If you are signed in as a root user, you can also set the date and time based on the local time zone.

 Syntax: '''date''' [''MMDDhhmm''[''YYYY'']['''.'''''ss'']]

 Parameters (available only to root users):

*''MM''-month, specified by two digits
*''DD''-day, specified by two digits
*''hh''-hour, specified by two digits in 24-hour format
*''mm''-minute, specified by two digits
*''YYYY''-calendar year, specified by four digits
*'''.'''''ss''-second, specified by two digits and a preceding period (.)

|-
|
dbupdate

|
Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group.

'''Caution! ''' Deleting all database entries is an irreversible operation. Before you run the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#dbupdate|dbupdate]] command, consider backing up and archiving the database. See [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing_Up.2C_Archiving.2C_and_Restoring_Data_on_the_Cisco_Unified_MeetingPlace_Application_Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

 Use this command only in these situations:

*Cisco TAC instructs you to do so.
*You configured Directory Service on your system, and you need to change the LDAP directory with which Cisco Unified Communications Manager is integrated. If you do not clear the database before switching from one LDAP directory to another, all user profiles from the first LDAP directory will remain in the Cisco Unified MeetingPlace database until you manually delete them.

:The automatic Directory Service deletion of user profiles does not apply when you change the LDAP directory. For details about when and how the system automatically deletes Directory Service user profiles, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory_Service_User_Profile_Deletion|Directory Service User Profile Deletion]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring_Cisco_Unified_MeetingPlace_Directory_Service|Configuring Cisco Unified MeetingPlace Directory Service]] module.

|-
|
errorlog

|
Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output one screen at a time:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output all at once.

 Syntax: '''errorlog'''

|-
|
eventlog

|
Displays the system event log.

'''Note: ''' This command has many parameter options; only the most commonly used parameters are listed below.

 Syntax: '''eventlog''' ['''-b''' [''YY''][''MMDD'']''hhmm''] ['''-e''' [''YY''][''MMDD'']''hhmm''] ['''-G''' | '''-C'''] ['''-t'''] ['''| more''']

 Parameters:

*'''-b'''-Specifies a start time for the log events to include in the output.
*'''-e'''-Specifies an end time for the log events to include in the output.

'''Note: ''' To show events for the current day, you can omit the ''YY'', ''MM'', and ''DD'' parameters from the start and end times.

*''YY''-Calendar year, specified by two digits. Typically, this parameter is included only when troubleshooting issues around the start of a new calendar year.
*''MM''-month, specified by two digits
*''DD''-day, specified by two digits
*''hh''-hour, specified by two digits in 24-hour format
*''mm''-minute, specified by two digits
*'''-G'''-Shows the telephony and conference events and control messages from the Call Processing-Media Control Protocol (CPMCP) component, which is a proxy for the Media Server.
*'''-C'''-Limits log output to events for the conference scheduler (ConfSchd) component.
*'''-t'''-Displays the log output in real time. This option is useful for troubleshooting issues in real time. For example, you can enter '''eventlog -G -t''' and then place a test call to the system to see how the system responds to the incoming call and to any subsequent user input.
*'''| more'''-Displays the log output one screen at a time.

|-
|
exc

|
Displays the meaning of an exception code that was listed in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command output.

 Syntax: '''exc''' ['''-v'''] ''exception-code''

|-
|
hostname

|
Displays the hostname of the Application Server.

 Syntax: '''hostname'''

|-
|
infocap

|
Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information.

 Restrictions:

*You must be signed in as the root user to run this command.
*You can also get this information by completing [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Obtaining_and_Viewing_the_System_Information_Capture_.28Infocap.29_Log|Obtaining and Viewing the System Information Capture (Infocap) Log]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module. Use this command only if you are unable to get the information from the Cisco Unified MeetingPlace Administration Center.
*The begin and end dates and times must be in the format [YY]MMDDhhmm. The YY is optional and if not specified, the system uses the current year. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

 Syntax: '''infocap -b''' ''begin-date-and-time'' '''-e''' ''end-date-and-time''

|-
|
infocapmtg

|
Gathers a system information capture file around the time of a meeting.

 Syntax: '''infocapmtg''' [''meetingID''] ['''-S | -P | -B'''''minutes''] ['''-n''' ''username | '''''-p''' ''profilename''] ['''-b''' ''beginning-time'' '''-e''' ''ending-time'']

 Parameters:

*''meetingID''-Captures information about a specific meeting ID.
*'''-S'''-Captures information about the specified meeting ID when it was scheduled.
*'''-P'''-Stops the capture when the meeting was purged.
*'''-B''' ''minutes''-Adds a buffer of minutes before or after the start or stop of the capture.
*'''-n''' ''username''-Captures information about the first meeting where the specified user was a participant.
*'''-p''' ''profilename''-Captures information about the first meeting where the specified user profile was a participant.
*'''-b''' ''beginning-time'' '''-e''' ''ending-time''-Captures information about the meeting between the beginning and ending time.

 Examples:

 '''infocapmtg 1212''' Gathers a system information capture file starting at the time meeting 1212 began and ending when meeting 1212 ended.

 '''infocapmtg 1212 -S''' Gathers a system information capture file starting at the time someone scheduled meeting 1212 and ending when meeting 1212 ended.

 '''infocapmtg 1212 -B 5''' Gathers a system information capture file starting 5 minutes before meeting 1212 began and ending 5 minutes after meeting 1212 ended.

 '''infocapmtg -n''' ''username'' '''-b 0950 -e 1400''' Gathers a system information capture file starting for a meeting scheduled by or attended by ''username'' where the meeting started between 9:50 a.m. and 2:00 p.m. today.

|-
|
langinfo

|
Displays information about all installed locales including the following:

*Locale ID
*Language code
*Locale order
*Locale name
*Country code
*Locale version number

 Syntax: '''langinfo'''

|-
|
mtginfo

|
Displays information about a specific meeting. Searches for a meeting based on any of these:

*Unique conference ID (such as 125). (This number is output by certain commands such as '''cptrace -C''' and '''errorlog'''. It uniquely identifies a meeting.)
*Meeting ID (such as 1278). Can optionally use any of the time arguments.
*Unique user ID (such as 0x65). (This number is output by certain commands such as [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#userinfo|userinfo]]. It uniquely identifies a user.) Searches for all meetings that a user has attended or been invited to.
*Activity. Searches only for active meetings.
*Time. Searches for all meetings valid at a certain time with the -t argument or between two times when the -s and -e arguments are used together.

 Syntax: '''mtginfo''' '''-a''' ''time'' '''-c''' ''unique-conf-id'' '''-e''' ''end-time'' '''-m''' ''meeting-id'' '''-s''' ''start-time'' '''-t''' ''time'' '''-u''' ''unique-user-id''

'''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

'''Note: ''' Start and end times in the command output are adjusted for the Meeting ID start guard time (minutes) and Meeting ID end guard time (minutes) fields on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting_Configuration_Page|Meeting Configuration Page]].

 Examples:

 '''mtginfo -m 1234 '''Looks for the meeting with the ID of 1234 at the current time

 '''mtginfo -m 1234 -t 11 '''Looks for meeting with the ID of 1234 at 11 minutes after the current hour

 '''mtginfo -m 1234 -t 1111111111 '''Looks for meeting with the ID of 1234 at 11:11am on Nov 11, 2011

 '''mtginfo -a 1430 '''Looks for meetings that are active at 2:30pm today

 '''mtginfo -s 1430 -e 1530 '''Looks for meetings that started or ended between 2:30 and 3:30pm today

 '''mtginfo -c 123 '''Looks for meeting with the unique conference ID of 123

 '''mtginfo -u 123 -t 1111 -e 1211 '''Looks for meetings that the user with the unique user ID of 123 is invited to between 11:11 and 12:11 today

|-
|
net

|
Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system.

 You must be signed in as root before running this command.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

 Use the '''net''' command to set the following:

*Port configuration parameters, including:
**Application Server (eth0) hostname, IP address, subnet mask, and default gateway
**Virtual (eth0:0) hostname, IP address, subnet mask, and default gateway-the eth0:0 virtual interface is used in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]] deployments
**MTU and link parameters (auto-negotiation, speed, duplex).
*Domain name
*DNS servers
*NTP servers

'''Note: ''' If you change the Application Server hostname (for eth0), then you must also perform these actions:

**Configure the DNS (1) server to point the old hostname to the new hostname.
**Restart the application by entering either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#'''mpx_sys|mpx_sys]]''''''restart''' operating system command or the '''reboot''' Linux command.
**If you enabled SSL for the Application Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Generating_a_Certificate_Signing_Request_and_Obtaining_the_Certificate|Generating a Certificate Signing Request and Obtaining the Certificate]] and [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Uploading_the_Certificate_File_and_Enabling_SSL|Uploading the Certificate File and Enabling SSL]] sections in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Configuring_SSL_for_the_Cisco_Unified_MeetingPlace_Application_Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]] module.
**If you installed MeetingPlace Conference Manager, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Editing_an_Existing_Server|Editing an Existing Server]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using_MeetingPlace_Conference_Manager|Using MeetingPlace Conference Manager]] module.
**If your system includes a Web Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Changing_the_Cisco_Unified_MeetingPlace_Application_Server_Connection_Configured_in_the_Gateway_SIM|Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Configuring_the_Cisco_Unified_MeetingPlace_Gateway_System_Integrity_Manager|Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager]] module.
**If you integrated the system with Cisco WebEx, notify the Cisco WebEx administrator to update the Cisco Unified MeetingPlace hostname that is configured in the Cisco WebEx license manager.

 Syntax: '''net'''

|-
|
ntpdate

|
Sets the Application Server date and time to match the time obtained by polling an NTP (2) server.

 Syntax: '''ntpdate''' ['''-u'''] ''ntp-server''

 Parameters:

*'''-u'''-Specifies to send packets through an unprivileged port to communicate with the NTP server. Use this option when you want to reach an NTP server that is beyond a firewall.
*''ntp-server''-Hostname or IP address of the NTP server.

|-
|
swstatus

|
Displays information about Cisco Unified MeetingPlace, including the following:

*Version number
*System mode
*Status of the power supplies
*List of software modules loaded in to memory, their version number, and their status

 Syntax: '''swstatus'''

|-
|
taccli

|
Displays details on the mixer status, active meetings, participant details, and general statistics, including the following:

*Cisco Unified MeetingPlace request statistics
*Statistics or status for one or all channels
*Statistics or details for one or all conferences
*Mixer status, request failures, and mixer return code table
*Video resolution and frame rate of each connection that is made to the Express Media Server

 Also does the following:

*Resets Cisco Unified MeetingPlace request statistics
*Enables and disables tracing
*Shows the current date and time
*Starts and stops channel RTP recording

 Syntax: '''taccli'''

|-
|
techui

|
Displays statistics for the Media Server, ports, and conferences.

 This technician user interface helps to diagnose and troubleshoot media and voice quality issues of active calls.

 Syntax: '''techui'''

|-
|
userinfo

|
Displays information about a specific user. Searches for a user based on any of these:

*User ID
*Profile number
*Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user.

 Syntax: '''userinfo''' {''user-id'' | ''profile-number'' | ''unique-user-id''}

|-
|
userutil

|
Performs administrative functions for any user profile.

 Restriction: You cannot set the admin user to inactive, locked, or the group default.

 Syntax: '''userutil''' {'''-q''' | ['''-p''' | '''-P] '''['''-n''' | '''-N] '''['''-a''' | '''-i''' | '''-l''' | '''-g]'''} ''userid'' [''password'']

 Parameters:

*'''-q'''-Displays user profile information and status.
*'''-p'''-Reset the User password. Requires a ''password'' entry.
*'''-P'''-Reset the User password and force it to expire. This forces the user to change the password at the next sign-in attempt. Requires a ''password'' entry.
*'''-n'''-Reset the Profile PIN (PIN for authentication over the phone). Requires a ''password'' entry.
*'''-N'''-Reset the Profile PIN and force it to expire. Requires a ''password'' entry.
*'''-a'''-Set User status to active.
*'''-i'''-Set User status to inactive.
*'''-l'''-Set User status to locked.
*'''-g'''-Set User status to group default setting.
*''userid''-User ID.
*''pasword''-New User password or Profile PIN. Required if you enter '''-p''', '''-P''', '''-n''', or '''-N'''.

|-
|
viewexlog

|
Provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output all at once:

*Date of the event
*Time of the event
*Severity (major, minor, informational, or warning)
*Exception code
*Brief description

 In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception_Log|Exception Log]] output one screen at a time:

 Syntax: '''viewexlog'''

|}

 

 Footnote 1: DNS = Domain Name System

 Footnote 2: NTP = Network Time Protocol

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module

=== Operating System Commands for the Application Server ===

In addition to the commands listed in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Operating_System_Commands_for_the_Application_Server|Table: Command Reference: Operating System Commands for the Application Server]], the CLI supports the standard Linux operating system commands. You can use the '''vim''' command to view or modify text files if necessary.

 These are the requirements and restrictions for operating system commands:

*With the exception of the '''mpx_sys''' command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands might cause unpredictable results.
*If you are not signed in as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user, you must enter '''sudo''' before you can run any of these commands. For example, to stop all application services, go to the command line and enter this command:

:'''sudo ./mpx_app stop'''
:The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, instead enter this command:
:'''sudo /etc/init.d/mpx_app stop'''

*Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies:
**To the '''mpx_app''', '''mpx_sys''', and '''mpx_va''' commands.
**If the Application Server crashes and is reloaded.
**If you enter the '''shutdown''' or '''reboot''' Linux command on the Application Server.

 

===== Table: Command Reference: Operating System Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
mpx_app

|
Starts, stops, or restarts all Cisco Unified MeetingPlace application services.

 Syntax: '''mpx_app''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_axlds

|
Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager.

 Syntax: '''mpx_axlds''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_db

|
Starts, stops, or restarts Cisco Unified MeetingPlace database services.

 Syntax: '''mpx_db''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_lm

|
Starts, stops, or restarts Cisco Unified MeetingPlace license manager services.

 Syntax: '''mpx_lm''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rmi

|
Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging.

 Syntax: '''mpx_rmi''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_rssctrl

|
Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service.

 Syntax: '''mpx_rssctrl''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_snmp

|
Starts, stops, or restarts SNMP services.

 Syntax: '''mpx_snmp''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_sys

|
Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

'''Note: ''' If the restart process is interrupted, you will have to reenter the '''mpx_sys restart''' command. For example, the restart process might be interrupted by a power outage, by closing the SSH connection, or by another restart process that is initiated from a different terminal.

 Syntax: '''mpx_sys''' {'''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcat

|
Starts, stops, or restarts Apache Tomcat services.

 Syntax: '''mpx_tomcat''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_tomcatmon

|
Starts, stops, or restarts Apache Tomcat monitoring services.

 Syntax: '''mpx_tomcatmon''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_va

|
Starts, stops, or restarts Media Server services on the Application Server.

 If all other Cisco Unified MeetingPlace services continue running, then entering this command does ''not'' interrupt meetings that are active.

 Syntax: '''mpx_va''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
mpx_version

|
Lists all installed versions of Cisco Unified MeetingPlace.

 Syntax: '''mpx_version '''

|-
|
mpx_webx

|
Starts, stops, or restarts all Cisco WebEx integration services on the Application Server.

 Syntax: '''mpx_webx''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']

|-
|
resetmsapassword

|
Resets the Hardware Media Server Administration password to "cisco".

 Syntax: '''resetmsapassword'''

|-
|
shutdown

|
Shuts down the Application Server.

 For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters.

 Syntax: '''shutdown -h now'''

|}

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module
*[[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing_the_Media_Server_Administration_Password_for_the_Hardware_Media_Server|Changing the Media Server Administration Password for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing_Values_for_the_Hardware_Media_Server|Changing Values for the Hardware Media Server]] module

=== Database Replication Commands for the Application Server ===

'''Note: ''' To enter the database replication commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Database_Replication_Commands_for_the_Application_Server|Table: Command Reference: Database Replication Commands for the Application Server]]:

*The MeetingPlace Database services must be running on the Application Server.
*You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user.

 The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>.

 

===== Table: Command Reference: Database Replication Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
mp_replication init

|
Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication.

 Syntax: '''mp_replication init -s''' ''site'' '''-n''' ''node'' ['''-l''' ''local-server''] '''-r''' ''remote-server'' {'''-h''' | '''-m'''} ['''-v''']

 Parameters:

*'''-s''' ''site''-Specifies the site of the node on which you run this command. Valid values for ''site'' are 1 and 2.
*'''-n''' ''node''-Specifies the node (within the specified site) on which you run the command. Valid values for ''node'' are 1 and 2.
*'''-l''' ''local-server''-(Optional) Specifies the hostname or IP address of the Application Server on which you run this command.

:For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.
:By default, the (eth0 hostname) value returned by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#hostname|hostname]] command is used.

*'''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.
*'''-h''' -- Specifies intra-site replication, which is used for replication between the active and standby Application Server in a single-site active/standby failover deployment.
*'''-m''' -- Specifies inter-site replication, which is used for replication between two singleServer mode Application Servers (i.e, site 1 and site 2) in Reservationless Single Number Access (RSNA) deployment.
*'''-v'''-Specifies verbose output.

|-
|
mp_replication switchON

|
Starts replication between two Application Servers.

*Run this command on node 1 only.
*Run this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command on each node involved in replication.

 Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v''']

 Parameters:

*'''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.

:For intra-site replication, which is used for Application Server failover, specify the hostname or IP address of the virtual network interface eth0:0.

*'''-S''' '''-F''' ''data-source-server''-Indicates data synchronization between the two Application Servers.

:'''NOTE:''' Both Application Servers must be in standby mode when the '''-S''' '''-F''' options are used.
:For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.

*'''-v'''-Specifies verbose output.

|-
|
mp_replication status

|
Displays the status of replication between the specified servers.

 Syntax: '''mp_replication status''' ['''-v''']

 Parameter: '''-v'''-Specifies verbose output.

 In the output, if the replication is not working, the queue size will be either a fixed value or keep increasing with database changes in any server.

 The State shows the connection status, for example, dropped, disconnected, and so forth.

|-
|
mp_replication switchOFF

|
Stops replication, but does not restore configuration changes.

*Run this command on node 1 only.
*To restart replication, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_switchON|mp_replication switchON]] command.
*To restore the configuration changes done by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_teardown|mp_replication teardown]] command.

 Syntax: '''mp_replication switchOFF''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command. Exception:

*'''-f'''-Specifies to remove the local server from replication even in the following cases:
**Specified remote server is not part of replication.
**Local server is not in replication with any other servers.

|-
|
mp_replication teardown

|
Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes.

 Syntax: '''mp_replication teardown''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

 Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication_init|mp_replication init]] command.

|}

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring_Cisco_Unified_MeetingPlace_Directory_Service|Configuring Cisco Unified MeetingPlace Directory Service]] module
*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

 

=== Failover Commands for the Application Server ===

'''Note: ''' You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user to enter the failover commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table:_Command_Reference:_Failover_Commands_for_the_Application_Server|Table: Command Reference: Failover Commands for the Application Server]].

 

===== Table: Command Reference: Failover Commands for the Application Server =====

{| border="1"
|-
! Command
! Description
|-
|
failoverUtil copyConfigFiles

|
Transfers configuration files from one Application Server to the other, specifically:

#Compresses the configuration files and user prompts on the local server.
#Transfers the compressed files to the remote server.

 After you enter this command on the local server, you need to enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] on the remote server.

 The following files and directories are transferred by this command:

*Directory Service:
**/opt/cisco/meetingplace/axlds/current/etc/config.properties
*Recorded user names and custom voice prompts:
**Everything under /opt/cisco/meetingplace/afs/custom
*Microsoft Outlook integration files:
**Everything under /opt/cisco/meetingplace/var/outlook
**/opt/cisco/meetingplace/var/admin/outlook.config
**Everything under /opt/cisco/meetingplace/var/mail
*Cisco WebEx integration files:
**/usr/local/enrollment
**/opt/cisco/meetingplace/web/current/etc/conf/keyinfo.properties
**/opt/cisco/meetingplace/web/current/etc/conf/keystore.jks
**/opt/cisco/meetingplace/web/current/etc/conf/cert.cer
**/opt/cisco/meetingplace/web/current/bases/main/conf/server.xml

 Syntax: '''failoverUtil copyConfigFiles'''

|-
|
failoverUtil restoreConfigFiles

|
Completes the transfer of configuration files from one Application Server to the other, specifically:

#Decompresses the configuration files and user prompts that were transferred from the remote server.
#Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server.

'''Note: ''' The failoverUtil copyConfigFiles and failoverUtil restoreConfigFiles commands are entered on separate Application Servers.

 Syntax: '''failoverUtil restoreConfigFiles'''

|-
|
failoverUtil setDeployment failover

|
Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway.

 Syntax: '''failoverUtil setDeployment failover'''

|-
|
failoverUtil setDeployment singleServer

|
Restores a failover-deployed Application Server to a single-server deployment.

 Syntax: '''failoverUtil setDeployment singleServer'''

|-
|
failoverUtil setServer

|
Sets a failover-deployed Application Server to either active or standby mode.

 Enter this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil_setDeployment_failover|failoverUtil setDeployment failover]] command on the server.

'''Note: ''' The mode setting might not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, sign in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the '''mpx_sys''' '''restart''' command, followed by the '''failoverUtil setServer''' command.

 Syntax: '''failoverUtil setServer''' {'''active''' | '''standby'''}

|-
|
failoverUtil status

|
Displays the current modes of the Application Server, specifically:

*Whether the server is deployed for failover or as a single server.
*If deployed for failover, then whether the server is in active or standby mode.

 Syntax: '''failoverUtil status'''

|}

 

 

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

*[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring_Application_Server_Failover_for_Cisco_Unified_MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

[[Category:Reference_Information_for_Cisco_Unified_MeetingPlace_Release_8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server

2012-04-10T22:53:16Z

Dunn:

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

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

== You can use the command-line interface (CLI) on the Application Server to perform functions that cannot be performed in the Administration Center. ==

== CAUTION : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks, and is not designed for use as persistent operating environment monitoring tool. If such a need exists please consult Cisco TAC or your Cisco Professional Services partners for further guidance ==

'''Note: ''' The CLI on the Application Server is not the same as the CLI on the Cisco WebEx Node for MCS. For information about the latter, see the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS#Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS|Using the Command-Line Interface (CLI) on the Cisco WebEx Node for MCS]] module.
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#CLI User Level Options on the Application Server|CLI User Level Options on the Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Restrictions for the CLI on the Application Server|Restrictions for the CLI on the Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#How to Sign in to the CLI on the Application Server|How to Sign in to the CLI on the Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application Server Command Reference|Application Server Command Reference]]

== CLI User Level Options on the Application Server ==

{| border = 1
|-
!CLI User Level
!Description
|-
|

mpxadmin
|

We recommend that you use this user level whenever possible.
|-
|

root
|

Highest authority, enabling you to do the following:
* Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating System Commands for the Application Server|Operating System Commands for the Application Server]], though pseudo (sudo) root access can also be used.
* Enter [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database Replication Commands for the Application Server|Database Replication Commands for the Application Server]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover Commands for the Application Server|Failover Commands for the Application Server]].
* Reset the root or mpxadmin user passwords.
* Uninstall the system.

To get to the root user level, do one of the following:
* Sign in as the mpxadmin user, and enter '''su''' at the command line.
* Sign in directly as the root user-this is possibly only by [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using the Console|Signing in to the CLI on the Application Server By Using the Console]].

'''Caution! ''' For security reasons, we do not recommend signing in directly as the root user, unless you need to reset the root user or mpxadmin user passwords or uninstall the system.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using the Console|Signing in to the CLI on the Application Server By Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using SSH|Signing in to the CLI on the Application Server By Using SSH]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Password Recovery for the Cisco Unified MeetingPlace Application Server#Password Recovery for the Cisco Unified MeetingPlace Application Server|Password Recovery for the Cisco Unified MeetingPlace Application Server]] module

== Restrictions for the CLI on the Application Server ==
* The CLI and its commands are available only in English.
* The CLI accepts only the standard 128 ASCII characters.
* Many commands you enter might prompt you for information. If the Backspace key does not delete characters in this interactive mode, use one of the following options:
** Press the '''Delete''' key to delete the previous character.
** Press '''Ctrl-W''' to delete the previous word.
** Press '''Ctrl-U''' to delete the entire line.

== How to Sign in to the CLI on the Application Server ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using the Console|Signing in to the CLI on the Application Server By Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using SSH|Signing in to the CLI on the Application Server By Using SSH]]

=== Signing in to the CLI on the Application Server By Using the Console ===

You can sign in to the CLI from the console by using either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] usernames. ''This is the only way you can sign in directly as the root user.'' You can enter operating system commands here.

===== Procedure =====

# Connect the monitor, keyboard, and mouse to the Application Server.
#: The Cisco Unified MeetingPlace operating system sign-in page is displayed.
# For the username, enter '''mpxadmin'''.
# Enter the password for the mpxadmin user.
#: This was established during installation.
# Right-click the desktop and select '''Open Terminal'''.
#: A command window appears. You can start entering commands. This is a Linux operating system so all commands should be either Linux commands or Cisco Unified MeetingPlace operating system commands. See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating System Commands for the Application Server|Operating System Commands for the Application Server]] for information about the operating system commands.
# When you are finished with the command window, either enter '''exit''' or select the '''X''' in the top right corner.
#: '''Note: ''' Always sign out of the Cisco Unified MeetingPlace operating system when you are finished.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using SSH|Signing in to the CLI on the Application Server By Using SSH]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application Server Command Reference|Application Server Command Reference]]

=== Signing in to the CLI on the Application Server By Using SSH ===

This section provides one method of signing in to the CLI by using SSH. Other methods might be available for you.

===== Restriction =====

Only the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mpxadmin|mpxadmin]] user can sign in to the CLI remotely using SSH. If needed, you can later switch to the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user by entering '''su'''.

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

You need a remote connection with a non-configurable terminal emulation program, such as the Windows SSH client, to sign in to the CLI remotely using SSH.

===== Procedure =====

# From your computer, go to '''Start > Programs > SSH Secure Shell > Secure Shell Client'''.
# Select '''Quick Connect'''.
# In the Connect to Remote Host window, enter these values:

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

Host Name
|

IP address of your Cisco Unified MeetingPlace system
|-
|

User Name
|

mpxadmin
|-
|

Port Number
|

22
|-
|

Authentication Method
|

leave as <Profile Settings>
|}

:4. Select '''Connect'''.
:5. In the Enter Password window, enter the password for the mpxadmin user.
:: This was established during installation.
:6. Select '''OK'''.
:: The system displays the command line, and you can now enter commands.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Signing in to the CLI on the Application Server By Using the Console|Signing in to the CLI on the Application Server By Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application Server Command Reference|Application Server Command Reference]]

== Application Server Command Reference ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Command Syntax Conventions|Command Syntax Conventions]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Application Commands for the Application Server|Application Commands for the Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Operating System Commands for the Application Server|Operating System Commands for the Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Database Replication Commands for the Application Server|Database Replication Commands for the Application Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Failover Commands for the Application Server|Failover Commands for the Application Server]]

=== Command Syntax Conventions ===

This document uses these command syntax conventions.

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

'''bold'''
|

Bold text indicates commands and parameters that you enter as shown.
|-
|

''italic''
|

Italic text indicates parameters for which you supply values.
|-
|

<x>
|

Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters.
|-
|

[x]
|

Square brackets enclose an optional parameter.
|-
|

<nowiki> | </nowiki>
|

A vertical line, called a pipe, indicates a choice within a set of parameters.
|-
|

[x | y]
|

Square brackets enclosing parameters separated by a pipe indicate an optional choice.
|-
|

{x | y}
|

Braces enclosing parameters separated by a pipe indicate a required choice.
|-
|

[x {y | z}]
|

Braces and a pipe within square brackets indicate a required choice within an optional element.
|}

=== Application Commands for the Application Server ===

===== Table: Command Reference: Application Commands for the Application Server =====

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

activity
|

Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings.

Syntax: '''activity'''
|-
|

alarm
|

Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm Table|Alarm Table]]:
* REFNO-Reference number used with the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#clearalarm|clearalarm]] command to clear a specific alarm table entry.
* SEV-Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Alarm Severity Levels|Alarm Severity Levels]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.
* CODE-See Code.
* COUNT -See Count.
* FIRST-See First Time.
* LAST-See Last Time.
* UNIT-See Unit.
* SW MODULE-See Software Module.

'''Note: ''' The brief description in the alarm table entry might contain values that are specific to one alarm occurrence, such as an IP address. These values might differ in all alarms that are combined into one table entry, but only the values for the ''most recent ''alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command.

Syntax: '''alarm'''
|-
|

ccamon
|

Monitors the Call Control Agent. Allows you to view the call statistics and set the log tracing level.

Syntax: '''ccamon'''
|-
|

checklic
|

Shows the type and number of licenses installed.

'''Note: ''' The system can take up to 15 seconds to process this information.

Syntax: '''checklic'''
|-
|

clearalarm
|

Clears either all the alarms in the alarm table or just the alarm specified.

If there are any major alarms in the alarm table, the system can be configured to call the system administrator after every restart until all major alarms are deleted from the alarm table. See [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Configuring the System to Call You If There is a Major Alarm|Configuring the System to Call You If There is a Major Alarm]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module.

Running this command stops the system from calling the system administrator (if it has been configured to do so).

Syntax: '''clearalarm''' {''reference-number'' | '''all'''}
|-

|

cleardb
|

Clears the following Application Server data:
*All user profiles except the admin and guest user profiles
*All user groups except the System group
*All user recordings
*All conference recordings

You must be signed in to the Application Server CLI as the root user to enter this command.

Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns.

'''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command.

Syntax: '''cleardb'''

|-

|

cpstatus
|

Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video.

Syntax: '''cpstatus'''
|-
|

cptrace
|

Lists selected portions of the call processing trace log.

Syntax: '''cptrace'''
|-
|

date
|

Displays the time and date for the Application Server.

If you are signed in as a root user, you can also set the date and time based on the local time zone.

Syntax: '''date''' [''MMDDhhmm''[''YYYY'']['''.'''''ss'']]

Parameters (available only to root users):
* ''MM''-month, specified by two digits
* ''DD''-day, specified by two digits
* ''hh''-hour, specified by two digits in 24-hour format
* ''mm''-minute, specified by two digits
* ''YYYY''-calendar year, specified by four digits
* '''.'''''ss''-second, specified by two digits and a preceding period (.)
|-
|

dbupdate
|

Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group.

'''Caution! ''' Deleting all database entries is an irreversible operation. Before you run the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#dbupdate|dbupdate]] command, consider backing up and archiving the database. See [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

Use this command only in these situations:
* Cisco TAC instructs you to do so.
* You configured Directory Service on your system, and you need to change the LDAP directory with which Cisco Unified Communications Manager is integrated. If you do not clear the database before switching from one LDAP directory to another, all user profiles from the first LDAP directory will remain in the Cisco Unified MeetingPlace database until you manually delete them.
: The automatic Directory Service deletion of user profiles does not apply when you change the LDAP directory. For details about when and how the system automatically deletes Directory Service user profiles, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Directory Service User Profile Deletion|Directory Service User Profile Deletion]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] module.
|-
|

errorlog
|

Displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception Log|Exception Log]] output one screen at a time:
* Date of the event
* Time of the event
* Severity (major, minor, informational, or warning)
* Exception code
* Brief description

In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception Log|Exception Log]] output all at once.

Syntax: '''errorlog'''
|-
|

eventlog
|

Displays the system event log.

'''Note: ''' This command has many parameter options; only the most commonly used parameters are listed below.

Syntax: '''eventlog''' ['''-b''' [''YY''][''MMDD'']''hhmm''] ['''-e''' [''YY''][''MMDD'']''hhmm''] ['''-G''' | '''-C'''] ['''-t'''] ['''| more''']

Parameters:
* '''-b'''-Specifies a start time for the log events to include in the output.
* '''-e'''-Specifies an end time for the log events to include in the output.

'''Note: ''' To show events for the current day, you can omit the ''YY'', ''MM'', and ''DD'' parameters from the start and end times.
* ''YY''-Calendar year, specified by two digits. Typically, this parameter is included only when troubleshooting issues around the start of a new calendar year.
* ''MM''-month, specified by two digits
* ''DD''-day, specified by two digits
* ''hh''-hour, specified by two digits in 24-hour format
* ''mm''-minute, specified by two digits
* '''-G'''-Shows the telephony and conference events and control messages from the Call Processing-Media Control Protocol (CPMCP) component, which is a proxy for the Media Server.
* '''-C'''-Limits log output to events for the conference scheduler (ConfSchd) component.
* '''-t'''-Displays the log output in real time. This option is useful for troubleshooting issues in real time. For example, you can enter '''eventlog -G -t''' and then place a test call to the system to see how the system responds to the incoming call and to any subsequent user input.
* '''| more'''-Displays the log output one screen at a time.
|-
|

exc
|

Displays the meaning of an exception code that was listed in the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] or [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#viewexlog|viewexlog]] command output.

Syntax: '''exc''' ['''-v'''] ''exception-code''
|-
|

hostname
|

Displays the hostname of the Application Server.

Syntax: '''hostname'''
|-
|

infocap
|

Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information.

Restrictions:
* You must be signed in as the root user to run this command.
* You can also get this information by completing [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Obtaining and Viewing the System Information Capture (Infocap) Log|Obtaining and Viewing the System Information Capture (Infocap) Log]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module. Use this command only if you are unable to get the information from the Cisco Unified MeetingPlace Administration Center.
* The begin and end dates and times must be in the format [YY]MMDDhhmm. The YY is optional and if not specified, the system uses the current year. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

Syntax: '''infocap -b''' ''begin-date-and-time'' '''-e''' ''end-date-and-time''
|-
|

infocapmtg
|

Gathers a system information capture file around the time of a meeting.

Syntax: '''infocapmtg''' [''meetingID''] ['''-S | -P | -B''''' minutes''] ['''-n''' ''username | '''''-p''' ''profilename''] ['''-b''' ''beginning-time'' '''-e''' ''ending-time'']

Parameters:
* ''meetingID''-Captures information about a specific meeting ID.
* '''-S'''-Captures information about the specified meeting ID when it was scheduled.
* '''-P'''-Stops the capture when the meeting was purged.
* '''-B''' ''minutes''-Adds a buffer of minutes before or after the start or stop of the capture.
* '''-n''' ''username''-Captures information about the first meeting where the specified user was a participant.
* '''-p''' ''profilename''-Captures information about the first meeting where the specified user profile was a participant.
* '''-b''' ''beginning-time'' '''-e''' ''ending-time''-Captures information about the meeting between the beginning and ending time.

Examples:

'''infocapmtg 1212''' Gathers a system information capture file starting at the time meeting 1212 began and ending when meeting 1212 ended.

'''infocapmtg 1212 -S''' Gathers a system information capture file starting at the time someone scheduled meeting 1212 and ending when meeting 1212 ended.

'''infocapmtg 1212 -B 5''' Gathers a system information capture file starting 5 minutes before meeting 1212 began and ending 5 minutes after meeting 1212 ended.

'''infocapmtg -n''' ''username'' '''-b 0950 -e 1400''' Gathers a system information capture file starting for a meeting scheduled by or attended by ''username'' where the meeting started between 9:50 a.m. and 2:00 p.m. today.
|-
|

langinfo
|

Displays information about all installed locales including the following:
* Locale ID
* Language code
* Locale order
* Locale name
* Country code
* Locale version number

Syntax: '''langinfo'''
|-
|

mtginfo
|

Displays information about a specific meeting. Searches for a meeting based on any of these:
* Unique conference ID (such as 125). (This number is output by certain commands such as '''cptrace -C''' and '''errorlog'''. It uniquely identifies a meeting.)
* Meeting ID (such as 1278). Can optionally use any of the time arguments.
* Unique user ID (such as 0x65). (This number is output by certain commands such as [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#userinfo|userinfo]]. It uniquely identifies a user.) Searches for all meetings that a user has attended or been invited to.
* Activity. Searches only for active meetings.
* Time. Searches for all meetings valid at a certain time with the -t argument or between two times when the -s and -e arguments are used together.

Syntax: '''mtginfo''' '''-a''' ''time'' '''-c''' ''unique-conf-id'' '''-e''' ''end-time'' '''-m''' ''meeting-id'' '''-s''' ''start-time'' '''-t''' ''time'' '''-u''' ''unique-user-id''

'''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#date|date]] command.

'''Note: ''' Start and end times in the command output are adjusted for the Meeting ID start guard time (minutes) and Meeting ID end guard time (minutes) fields on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Meeting Configuration Page|Meeting Configuration Page]].

Examples:

'''mtginfo -m 1234 '''Looks for the meeting with the ID of 1234 at the current time

'''mtginfo -m 1234 -t 11 '''Looks for meeting with the ID of 1234 at 11 minutes after the current hour

'''mtginfo -m 1234 -t 1111111111 '''Looks for meeting with the ID of 1234 at 11:11am on Nov 11, 2011

'''mtginfo -a 1430 '''Looks for meetings that are active at 2:30pm today

'''mtginfo -s 1430 -e 1530 '''Looks for meetings that started or ended between 2:30 and 3:30pm today

'''mtginfo -c 123 '''Looks for meeting with the unique conference ID of 123

'''mtginfo -u 123 -t 1111 -e 1211 '''Looks for meetings that the user with the unique user ID of 123 is invited to between 11:11 and 12:11 today
|-
|

net
|

Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system.

You must be signed in as root before running this command.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

Use the '''net''' command to set the following:
* Port configuration parameters, including:
** Application Server (eth0) hostname, IP address, subnet mask, and default gateway
** Virtual (eth0:0) hostname, IP address, subnet mask, and default gateway-the eth0:0 virtual interface is used in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|Application Server Failover]] deployments
** MTU and link parameters (auto-negotiation, speed, duplex).
* Domain name
* DNS servers
* NTP servers

'''Note: ''' If you change the Application Server hostname (for eth0), then you must also perform these actions:
** Configure the DNS (1) server to point the old hostname to the new hostname.
** Restart the application by entering either the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#'''mpx_sys|mpx_sys]]'''''' restart''' operating system command or the '''reboot''' Linux command.
** If you enabled SSL for the Application Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Generating a Certificate Signing Request and Obtaining the Certificate|Generating a Certificate Signing Request and Obtaining the Certificate]] and [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Uploading the Certificate File and Enabling SSL|Uploading the Certificate File and Enabling SSL]] sections in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Configuring SSL for the Cisco Unified MeetingPlace Application Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]] module.
** If you installed MeetingPlace Conference Manager, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Editing an Existing Server|Editing an Existing Server]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Using MeetingPlace Conference Manager#Using MeetingPlace Conference Manager|Using MeetingPlace Conference Manager]] module.
** If your system includes a Web Server, complete the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM|Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM]] section in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager#Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager|Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager]] module.
** If you integrated the system with Cisco WebEx, notify the Cisco WebEx administrator to update the Cisco Unified MeetingPlace hostname that is configured in the Cisco WebEx license manager.

Syntax: '''net'''
|-
|

ntpdate
|

Sets the Application Server date and time to match the time obtained by polling an NTP (2) server.

Syntax: '''ntpdate''' ['''-u'''] ''ntp-server''

Parameters:
* '''-u'''-Specifies to send packets through an unprivileged port to communicate with the NTP server. Use this option when you want to reach an NTP server that is beyond a firewall.
* ''ntp-server''-Hostname or IP address of the NTP server.
|-
|

swstatus
|

Displays information about Cisco Unified MeetingPlace, including the following:
* Version number
* System mode
* Status of the power supplies
* List of software modules loaded in to memory, their version number, and their status

Syntax: '''swstatus'''
|-
|

taccli
|

Displays details on the mixer status, active meetings, participant details, and general statistics, including the following:
* Cisco Unified MeetingPlace request statistics
* Statistics or status for one or all channels
* Statistics or details for one or all conferences
* Mixer status, request failures, and mixer return code table
* Video resolution and frame rate of each connection that is made to the Express Media Server

Also does the following:
* Resets Cisco Unified MeetingPlace request statistics
* Enables and disables tracing
* Shows the current date and time
* Starts and stops channel RTP recording

Syntax: '''taccli'''
|-
|

techui
|

Displays statistics for the Media Server, ports, and conferences.

This technician user interface helps to diagnose and troubleshoot media and voice quality issues of active calls.

Syntax: '''techui'''
|-
|

userinfo
|

Displays information about a specific user. Searches for a user based on any of these:
* User ID
* Profile number
* Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user.

Syntax: '''userinfo''' {''user-id'' | ''profile-number'' | ''unique-user-id''}
|-
|

userutil
|

Performs administrative functions for any user profile.

Restriction: You cannot set the admin user to inactive, locked, or the group default.

Syntax: '''userutil''' {'''-q''' | ['''-p''' | '''-P] '''['''-n''' | '''-N] '''['''-a''' | '''-i''' | '''-l''' | '''-g]'''} ''userid'' [''password'']

Parameters:
* '''-q'''-Displays user profile information and status.
* '''-p'''-Reset the User password. Requires a ''password'' entry.
* '''-P'''-Reset the User password and force it to expire. This forces the user to change the password at the next sign-in attempt. Requires a ''password'' entry.
* '''-n'''-Reset the Profile PIN (PIN for authentication over the phone). Requires a ''password'' entry.
* '''-N'''-Reset the Profile PIN and force it to expire. Requires a ''password'' entry.
* '''-a'''-Set User status to active.
* '''-i'''-Set User status to inactive.
* '''-l'''-Set User status to locked.
* '''-g'''-Set User status to group default setting.
* ''userid''-User ID.
* ''pasword''-New User password or Profile PIN. Required if you enter '''-p''', '''-P''', '''-n''', or '''-N'''.
|-
|

viewexlog
|

Provides the entire [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception Log|Exception Log]] output all at once:
* Date of the event
* Time of the event
* Severity (major, minor, informational, or warning)
* Exception code
* Brief description

In contrast, the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#errorlog|errorlog]] command displays the [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Exception Log|Exception Log]] output one screen at a time:

Syntax: '''viewexlog'''
|}

Footnote 1: DNS = Domain Name System

Footnote 2: NTP = Network Time Protocol

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module

=== Operating System Commands for the Application Server ===

In addition to the commands listed in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table: Command Reference: Operating System Commands for the Application Server|Table: Command Reference: Operating System Commands for the Application Server]], the CLI supports the standard Linux operating system commands. You can use the '''vim''' command to view or modify text files if necessary.

These are the requirements and restrictions for operating system commands:
* With the exception of the '''mpx_sys''' command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands might cause unpredictable results.
* If you are not signed in as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user, you must enter '''sudo''' before you can run any of these commands. For example, to stop all application services, go to the command line and enter this command:
: '''sudo ./mpx_app stop'''
: The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, instead enter this command:
: '''sudo /etc/init.d/mpx_app stop'''
* Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies:
** To the '''mpx_app''', '''mpx_sys''', and '''mpx_va''' commands.
** If the Application Server crashes and is reloaded.
** If you enter the '''shutdown''' or '''reboot''' Linux command on the Application Server.

===== Table: Command Reference: Operating System Commands for the Application Server =====

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

mpx_app
|

Starts, stops, or restarts all Cisco Unified MeetingPlace application services.

Syntax: '''mpx_app''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_axlds
|

Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager.

Syntax: '''mpx_axlds''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_db
|

Starts, stops, or restarts Cisco Unified MeetingPlace database services.

Syntax: '''mpx_db''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_lm
|

Starts, stops, or restarts Cisco Unified MeetingPlace license manager services.

Syntax: '''mpx_lm''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_rmi
|

Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging.

Syntax: '''mpx_rmi''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_rssctrl
|

Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service.

Syntax: '''mpx_rssctrl''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_snmp
|

Starts, stops, or restarts SNMP services.

Syntax: '''mpx_snmp''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_sys
|

Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services.

'''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage.

'''Note: ''' If the restart process is interrupted, you will have to reenter the '''mpx_sys restart''' command. For example, the restart process might be interrupted by a power outage, by closing the SSH connection, or by another restart process that is initiated from a different terminal.

Syntax: '''mpx_sys''' {'''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_tomcat
|

Starts, stops, or restarts Apache Tomcat services.

Syntax: '''mpx_tomcat''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_tomcatmon
|

Starts, stops, or restarts Apache Tomcat monitoring services.

Syntax: '''mpx_tomcatmon''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_va
|

Starts, stops, or restarts Media Server services on the Application Server.

If all other Cisco Unified MeetingPlace services continue running, then entering this command does ''not'' interrupt meetings that are active.

Syntax: '''mpx_va''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

mpx_version
|

Lists all installed versions of Cisco Unified MeetingPlace.

Syntax: '''mpx_version '''
|-
|

mpx_webx
|

Starts, stops, or restarts all Cisco WebEx integration services on the Application Server.

Syntax: '''mpx_webx''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v''']
|-
|

resetmsapassword
|

Resets the Hardware Media Server Administration password to "cisco".

Syntax: '''resetmsapassword'''
|-
|

shutdown
|

Shuts down the Application Server.

For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters.

Syntax: '''shutdown -h now'''
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Media Server Administration Password for the Hardware Media Server|Changing the Media Server Administration Password for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Database Replication Commands for the Application Server ===

'''Note: ''' To enter the database replication commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table: Command Reference: Database Replication Commands for the Application Server|Table: Command Reference: Database Replication Commands for the Application Server]]:
* The MeetingPlace Database services must be running on the Application Server.
* You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user.

The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>.

===== Table: Command Reference: Database Replication Commands for the Application Server =====

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

mp_replication init
|

Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication.

Syntax: '''mp_replication init -s''' ''site'' '''-n''' ''node'' ['''-l''' ''local-server''] '''-r''' ''remote-server'' {'''-h''' | '''-m'''} ['''-v''']

Parameters:
* '''-s''' ''site''-Specifies the site of the node on which you run this command. Valid values for ''site'' are 1 and 2.
* '''-n''' ''node''-Specifies the node (within the specified site) on which you run the command. Valid values for ''node'' are 1 and 2.
* '''-l''' ''local-server''-(Optional) Specifies the hostname or IP address of the Application Server on which you run this command.
: For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.
: By default, the (eth0 hostname) value returned by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#hostname|hostname]] command is used.
* '''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.
* '''-h''' -- Specifies intra-site replication, which is used for replication between the active and standby Application Server in a single-site active/standby failover deployment.
* '''-m''' -- Specifies inter-site replication, which is used for replication between two singleServer mode Application Servers (i.e, site 1 and site 2) in Reservationless Single Number Access (RSNA) deployment.
* '''-v'''-Specifies verbose output.
|-
|

mp_replication switchON
|

Starts replication between two Application Servers.
* Run this command on node 1 only.
* Run this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication init|mp_replication init]] command on each node involved in replication.

Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v''']

Parameters:
* '''-r''' ''remote-server''-Specifies the hostname or IP address of the other Application Server with which to establish replication.
: For intra-site replication, which is used for Application Server failover, specify the hostname or IP address of the virtual network interface eth0:0.
* '''-S''' '''-F''' ''data-source-server''-Indicates data synchronization between the two Application Servers.
:'''NOTE:''' Both Application Servers must be in standby mode when the '''-S''' '''-F''' options are used.
: For intra-site replication, which is used for [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Application Server Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0.
* '''-v'''-Specifies verbose output.
|-
|

mp_replication status
|

Displays the status of replication between the specified servers.

Syntax: '''mp_replication status''' ['''-v''']

Parameter: '''-v'''-Specifies verbose output.

In the output, if the replication is not working, the queue size will be either a fixed value or keep increasing with database changes in any server.

The State shows the connection status, for example, dropped, disconnected, and so forth.
|-
|

mp_replication switchOFF
|

Stops replication, but does not restore configuration changes.
* Run this command on node 1 only.
* To restart replication, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication switchON|mp_replication switchON]] command.
* To restore the configuration changes done by the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication init|mp_replication init]] command, use the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication teardown|mp_replication teardown]] command.

Syntax: '''mp_replication switchOFF''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication init|mp_replication init]] command. Exception:
* '''-f'''-Specifies to remove the local server from replication even in the following cases:
** Specified remote server is not part of replication.
** Local server is not in replication with any other servers.
|-
|

mp_replication teardown
|

Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes.

Syntax: '''mp_replication teardown''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f''']

Parameters: See the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#mp_replication init|mp_replication init]] command.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Cisco Unified MeetingPlace Directory Service#Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

=== Failover Commands for the Application Server ===

'''Note: ''' You must be signed in to the Application Server CLI as the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#root|root]] user to enter the failover commands in [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Table: Command Reference: Failover Commands for the Application Server|Table: Command Reference: Failover Commands for the Application Server]].

===== Table: Command Reference: Failover Commands for the Application Server =====

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

failoverUtil copyConfigFiles
|

Transfers configuration files from one Application Server to the other, specifically:
# Compresses the configuration files and user prompts on the local server.
# Transfers the compressed files to the remote server.

After you enter this command on the local server, you need to enter the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil restoreConfigFiles|failoverUtil restoreConfigFiles]] on the remote server.

The following files and directories are transferred by this command:
* Directory Service:
** /opt/cisco/meetingplace/axlds/current/etc/config.properties
* Recorded user names and custom voice prompts:
** Everything under /opt/cisco/meetingplace/afs/custom
* Microsoft Outlook integration files:
** Everything under /opt/cisco/meetingplace/var/outlook
** /opt/cisco/meetingplace/var/admin/outlook.config
** Everything under /opt/cisco/meetingplace/var/mail
* Cisco WebEx integration files:
** /usr/local/enrollment
** /opt/cisco/meetingplace/web/current/etc/conf/keyinfo.properties
** /opt/cisco/meetingplace/web/current/etc/conf/keystore.jks
** /opt/cisco/meetingplace/web/current/etc/conf/cert.cer
** /opt/cisco/meetingplace/web/current/bases/main/conf/server.xml

Syntax: '''failoverUtil copyConfigFiles'''
|-
|

failoverUtil restoreConfigFiles
|

Completes the transfer of configuration files from one Application Server to the other, specifically:
# Decompresses the configuration files and user prompts that were transferred from the remote server.
# Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server.

'''Note: ''' The failoverUtil copyConfigFiles and failoverUtil restoreConfigFiles commands are entered on separate Application Servers.

Syntax: '''failoverUtil restoreConfigFiles'''
|-
|

failoverUtil setDeployment failover
|

Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway.

Syntax: '''failoverUtil setDeployment failover'''
|-
|

failoverUtil setDeployment singleServer
|

Restores a failover-deployed Application Server to a single-server deployment.

Syntax: '''failoverUtil setDeployment singleServer'''
|-
|

failoverUtil setServer
|

Sets a failover-deployed Application Server to either active or standby mode.

Enter this command only after running the [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#failoverUtil setDeployment failover|failoverUtil setDeployment failover]] command on the server.

'''Note: ''' The mode setting might not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, sign in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the '''mpx_sys''' ''' restart''' command, followed by the '''failoverUtil setServer''' command.

Syntax: '''failoverUtil setServer''' {'''active''' | '''standby'''}
|-
|

failoverUtil status
|

Displays the current modes of the Application Server, specifically:
* Whether the server is deployed for failover or as a single server.
* If deployed for failover, then whether the server is in active or standby mode.

Syntax: '''failoverUtil status'''
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module

[[Category: Reference Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0

2012-02-09T00:26:04Z

Dunn:

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

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Installation, Upgrade and Migration|Installation, Upgrade and Migration]]

* You can upgrade to Cisco Unified MeetingPlace Release 8.0 Maintenance Release 1 (MR1) from Cisco Unified MeetingPlace:
:* Release 7.0.1.4 (the FCS version)
:* Release 7.0.2.14 (the Maintenance Release 1 version)
:* Release 7.0.3.4 (the Maintenance Release 2 version)
:* Release 8.0.1.3 (the FCS version)
:* Release 8.0.1.229 (the Patch 1 version)

'''Note:''' If you are upgrading from Release 8.0 FCS or Release 8.0 Patch 1 to Release 8.0 MR 1, then complete the upgrade procedure in this module.

* You can upgrade to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace:
:* Release 7.0.1.4 (the FCS version)
:* Release 7.0.2.14 (the Maintenance Release 1 version)

* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading|About Upgrading]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Web Server Software|How to Upgrade the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading Cisco WebEx|About Upgrading Cisco WebEx]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Change from a Hardware Media Server to an Express Media Server|How to Change from a Hardware Media Server to an Express Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Microsoft Outlook for Cisco Unified MeetingPlace|Upgrading Microsoft Outlook for Cisco Unified MeetingPlace]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Testing that the Upgraded System Works Correctly|Testing that the Upgraded System Works Correctly]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Upgrade|Completing the Upgrade]]

== About Upgrading ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Changes between Release 7.0 and Release 8.0|Changes between Release 7.0 and Release 8.0]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Recommendations|Recommendations]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrade Procedure|Upgrade Procedure]]

=== Changes between Release 7.0 and Release 8.0 ===

* (Release 8.0 MR1 only) Existing Release 7.0 MR1 and MR2 audio-only deployments, or deployments with Cisco Unified MeetingPlace scheduling and Cisco Unified MeetingPlace meetings, are automatically converted to deployments with Cisco Unified MeetingPlace scheduling and Cisco WebEx meetings, following an upgrade to Release 8.0 MR1. Sign in to the Administration Center and select '''System Configuration > Cisco WebEx Configuration > Cisco WebEx Site and Server '''. Change your configuration back to your original deployment type.
* The Cisco Unified MeetingPlace Release 7.0 system had two options for web conferencing: using the Cisco Unified MeetingPlace meeting room and using the Cisco WebEx meeting room. In Release 8.0, Cisco Unified MeetingPlace only offers the Cisco WebEx meeting room.
* For systems that are upgraded, the software that ran the Cisco Unified MeetingPlace meeting room will remain on the upgraded system in order to allow users to play back meetings that were recorded in Release 7.0. The old software cannot be used for scheduling or attending meetings.
* In upgraded systems, the SSL/TLS page in the Administration Center shows two SSL configuration fields. The second SSL configuration field is required to play back meeting recordings from Cisco Unified MeetingPlace Release 7.0.
* Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0 will continue to use two NICs (IP addresses); however, new Cisco Unified MeetingPlace Release 8.0 systems only use one NIC.
* In Cisco Unified MeetingPlace Release 7.0, there were two fields to describe licensed capacity: '''Use licensed audio capacity''' and '''Use licensed video capacity'''. In Cisco Unified MeetingPlace Release 8.0, these two fields are combined into one field called '''Use licensed capacity'''. The value of the new field in Cisco Unified MeetingPlace Release 8.0 is set to the value of the '''Use licensed audio capacity''' in Cisco Unified MeetingPlace Release 7.0.
* For Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0, you must ensure that the remote storage location is accessible; otherwise, some of the web master services may fail to start properly which can cause the system to try to restart all the services.
* Cisco Unified MeetingPlace Release 7.0 meetings describe meeting attendees using the terms moderators, presenters, and audience. Cisco Unified MeetingPlace Release 8.0 meetings use the terms host, alternate host, and attendee. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Upgrade|Completing the Upgrade]] for more information about how user types in Release 7.0 are converted for Release 8.0.
* Cisco Unified MeetingPlace Release 8.0 does not have lecture-style meetings.
* Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0 will keep the current setting for the "Dial-out calls enabled via guest profile" parameter; however, new Cisco Unified MeetingPlace Release 8.0 systems will set the default value for that parameter to '''Yes'''. This means that systems that are upgraded to Release 8.0 may not allow guest users to dial out from the meeting room automatically even though new installations will allow this.

=== Recommendations ===

We recommend that you upgrade your Cisco Unified MeetingPlace system during a time when there is not much meeting traffic, for example, over a weekend or a period of extended downtime.

=== Upgrade Procedure ===

Follow these steps to upgrade to Cisco Unified MeetingPlace Release 8.0.

===== Procedure =====

{| border = 1
|-
!Step
!Step Description
!Related Topics
|-
|

1
|

Notify end users of the planned upgrade and system downtime.
|
|-
|

2
|

Upgrade the Application Server software.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]
|-
|

3
|

Upgrade the Web Server software.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Web Server Software|How to Upgrade the Web Server Software]]
|-
|

4
|

(Optional) Upgrade Cisco WebEx.

'''Note: ''' Only applies to Cisco Unified MeetingPlace Release 7.0 systems that use Cisco WebEx.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading Cisco WebEx|About Upgrading Cisco WebEx]]
|-
|

5
|

Upgrade the Hardware Media Server software.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
|-
|

6
|

(Optional) Convert the Hardware Media Server to an Express Media Server.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Change from a Hardware Media Server to an Express Media Server|How to Change from a Hardware Media Server to an Express Media Server]]
|-
|

7
|

Install the Cisco WebEx Node for MCS.

'''Note: ''' Technically, installing the Cisco WebEx Node for MCS is optional. It is not required if your system is audio only. However, if your system will include web functionality, you must install the Cisco WebEx Node for MCS.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco WebEx Node for MCS#Installing the Cisco WebEx Node for MCS|Installing the Cisco WebEx Node for MCS]] module
|-
|

8
|

Configure your system to use Cisco WebEx.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module
|-
|

9
|

(Optional) Upgrade the Microsoft Outlook for Cisco Unified MeetingPlace integration.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Microsoft Outlook for Cisco Unified MeetingPlace|Upgrading Microsoft Outlook for Cisco Unified MeetingPlace]]
|-
|

10
|

Test that the upgraded system works correctly.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Testing that the Upgraded System Works Correctly|Testing that the Upgraded System Works Correctly]]
|-
|

11
|

Inform end users that the system has been successfully upgraded.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Upgrade|Completing the Upgrade]]
|}

== How to Upgrade the Application Server Software ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading the Application Server Software|About Upgrading the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Preparing to Upgrade the Application Server Software|Preparing to Upgrade the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restrictions and Recommendations for Upgrading the Application Server Software|Restrictions and Recommendations for Upgrading the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Determining Which Procedure to Follow|Determining Which Procedure to Follow]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment|Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Application Server Software Upgrade|Completing the Application Server Software Upgrade]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Test the Application Server Software Upgrade|How to Test the Application Server Software Upgrade]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting the Application Server Software Upgrade|Troubleshooting the Application Server Software Upgrade]]

=== About Upgrading the Application Server Software ===
* To upgrade the Application Server software, you must already have an existing version of the Application Server software installed on your server.
* When you upgrade the Application Server software, the upgrade program moves the existing files to a backup directory and installs the new files in the current directory.
* A fresh installation of the Application Server software erases the database that holds the Hardware Media Server configuration information; however, ''upgrading'' the Application Server software does not erase the database.
* The upgrade program backs up any Microsoft Outlook notification templates and copies them to /opt/cisco/meetingplace/var.
* We support using Integrated Lights-Out (iLO) to install and upgrade the Application Server software. This standard only applies to the Cisco MCS 7835-H2 and Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.

=== Preparing to Upgrade the Application Server Software ===
* Do ''not'' uninstall the Application Server software before you upgrade.
* The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.
* Back up all your data files. See the [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

=== Restrictions and Recommendations for Upgrading the Application Server Software ===
* (Upgrading to Release 8.0 from Release 7.0.1.4 FCS or from Release 7.0.2.14 MR1 version only.) If your Application Server is on a Cisco MCS 7835-I2 or a Cisco MCS 7835-H2, then we recommend you run the upgrade script from the /mpx-record directory. Enter '''df -h''' to determine the amount of available space. There should be a minimum of 6 GB available in the /mpx-record directory, when you run the upgrade script here. If you prefer to run the upgrade script from the /tmp directory, then there must be a minimum of 8 GB available in the /mpx-record directory.
* We recommend that the server that you are upgrading have 4 GB of memory. See the ''System Requirements for Cisco Unified MeetingPlace Release 8.0'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html
* Ensure that the system is not performing a database backup when you upgrade the Application Server software.
* The system must have a functional database. To ensure that the database is functional, go to the Command-Line Interface and run the '''/sbin/service mpx_db status''' command. See [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
* Have a valid DNS service configuration.
:This is mandatory for correct operation of the Cisco Unified MeetingPlace system.You need to enter a valid IP address for a DNS service during the installation of the Application Server. Without this, your upgrade may fail.
:You can test your DNS service by entering on the command-line interface, '''ping <''DNS_IP_Address''>'''. You should get a response in under 200 milliseconds.

=== Determining Which Procedure to Follow ===

Depending on the configuration of your Application Server, follow one of these steps:
* If your Application Server is in a failover deployment, follow the procedure in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]]. After the upgrade, reconfigure the system for database replication.
* If your Application Server is in a Reservationless Single Number Access (RSNA) deployment, follow the procedure in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment|Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment]].
* If your Application Server does not meet either of the above conditions, follow the procedure in either the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]] or the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]].

=== Upgrading the Application Server by Using the Console ===

'''Note: ''' Only perform this procedure if your system does not use failover or RSNA. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Determining Which Procedure to Follow|Determining Which Procedure to Follow]].

===== Before You Begin =====
* Take the Audio Blade offline.

===== Procedure =====

#Go to Cisco.com and find the upgrade file. The naming convention will be similar to upgrade_mp_''<version_number''>.bin, where <''version_number> ''is the version number to which you are upgrading.
#:'''Note: ''' The file is located near http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
#Save the file to a convenient location.
#Enter '''md5sum upgrade_mp_<''''''version_number>''''''.bin''' to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.
#From the console, go to the Cisco Unified MeetingPlace operating system sign-in page and sign in as the user called root.
#Right-click on the desktop and select '''New Terminal'''.
#:The upgrade program displays the command line.
#Navigate to the directory where you saved the upgrade file.
#Enter '''sh upgrade_mp_<version_number>.bin &''' to execute the upgrade program.
#:The upgrade program displays the Introduction page.
#Select '''Next'''.
#:The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous versions found on the system.
#:'''Note: ''' If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.
#Select '''Next''' to begin the upgrade.
#:The upgrade program displays a pre-installation summary.
#Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.
#Select '''Install''' if all the values are correct.
#:The upgrade program upgrades all the required components associated with the Application Server software.
#:The upgrade program displays a message stating that the upgrade is complete.
#Select '''Done''' to restart the system.
#Synchronize the Hardware Media Server and meeting types.
#Put the Audio Blade back online.

===== Troubleshooting Tips =====
* See [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting the Application Server Software Upgrade|Troubleshooting the Application Server Software Upgrade]].

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Synchronizing Audio Blade Meeting Types with the Template Audio Blade|Synchronizing Audio Blade Meeting Types with the Template Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Upgrading the Application Server Remotely ===

'''Note: ''' Only perform this procedure if your system does not use failover or RSNA. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Determining Which Procedure to Follow|Determining Which Procedure to Follow]].

When you upgrade the Application Server software remotely, the upgrade status is limited. We recommend that you upgrade the Application Server at the console if possible.

===== Restrictions =====
* You must use the screen to perform a remote upgrade.

===== Before You Begin =====
* Take the Audio Blade offline.

===== Procedure =====

# Go to Cisco.com and find the upgrade file. The naming convention will be similar to upgrade_mp_<''version_number>''.bin, where <''version_number> ''is the version number to which you are upgrading.
#: '''Note: ''' The file is located near http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
# Save the file to a convenient, local location.
# Enter '''md5sum upgrade_mp_<''''''version_number''''''>.bin''' to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.
# Transfer the upgrade or patch file to Cisco Unified MeetingPlace using SCP file transfer.
# Using an SSH client, sign in as the user called mpxadmin.
# Enter '''screen -S mp_upgrade''' to create and attach to a screen named mp_upgrade.
# Change to the root user by entering '''su -''' and enter the root password.
# From the CLI, navigate to the directory where you saved the upgrade file.
# Enter '''sh ./upgrade_mp_<''''''version_number>''''''.bin -i console''' to execute the upgrade program.
#: The upgrade program displays an introduction message.
# Press '''Enter''' to continue.
#: The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous versions found on the system.
#: '''Note: ''' If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.
# Press '''Enter''' to continue.
# Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.
# Press '''Enter''' to begin the upgrade.
#: The upgrade program installs the Application Server upgrade.
#: When the upgrade is complete, the upgrade program displays the Install Complete page and a message stating that the upgrade is complete.
# Press '''Enter''' to restart the system.
#: '''Note: ''' When you restart the system, all existing screens are removed.
# Synchronize the Hardware Media Server and meeting types.
# Put the Audio Blade back online.

===== Troubleshooting =====

If the SSH remote session disconnects while you are upgrading the Application Server, follow these steps to reattach to the installation screen and continue the upgrade:
# Using an SSH client, sign in as the user called mpxadmin.
# Enter '''screen -ls '''to find out the full name of the screen created in Step 6 of the "Upgrading the Application Server Remotely" procedure. The full name of the screen consists of an identifier followed by a dot and then the name that you used in Step 6 of the "Upgrading the Application Server Remotely" procedure. For example, the full screen name might be 1665.mp_upgrade.
# Enter '''screen -rD '''''full_screen_name'' to reattach to the installation screen.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Synchronizing Audio Blade Meeting Types with the Template Audio Blade|Synchronizing Audio Blade Meeting Types with the Template Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Upgrading Application Servers that are Used in a Failover Deployment ===

===== Before You Begin =====
* Note the following nomenclature that is used for clarity: node 1 is the server that originally is the active Application Server and node 2 is the server that originally is the standby Application Server.
* Turn off failover before you begin.

===== Procedure =====

#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''su - '''to switch to the root user.
#Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.
#:The system displays the queue column as zeroes.
#Enter '''mp_replication switchOFF -r'''''node_2_eth0:0 ''on node 1, to switch off replication between the two Application Servers, where ''node_2_eth0:0''is the eth0:0 address for node 2.
#Enter '''mp_replication teardown -r '''''node_2_eth0:0 ''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_eth0:0''is the eth0:0 address for node 2.
#Archive and save the configuration data on node 1.
#Enter '''failoverUtil setDeployment singleServer '''to change the mode of node 1 to SingleServer.
#Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console|Upgrading the Application Server by Using the Console]].
#Enter '''failoverUtil setDeployment failover '''on node 1 to change the mode of node 1 to failover.
#:'''Note: ''' This disables the eth0 interface of node 1, so that node 2 can become active.
#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''su - '''to switch to the root user.
#Enter '''failoverUtil setServer active''' on node 2 to change its mode from standby to active.
#Enter '''mp_replication teardown -r '''''node_1_eth0:0 ''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_eth0:0''is the eth0:0 address for node 1.
#Enter '''failoverUtil setDeployment singleServer''' on node 2 to change its mode to SingleServer.
#Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console|Upgrading the Application Server by Using the Console]].
#Enter '''failoverUtil setDeployment failover''' on node 2 to change its mode to failover.

 At this point, both Application Servers are in standby mode.

#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Initialize database replication:
#*Release 8.0 MR1--Enter '''mp_replication init -n 2 -r <''node1-eth0:0-hostname''> [-v]'''
#*Release 8.0 FCS-- Enter'''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h'''
#Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
#Enter the following to initialize and start database replication:
#*Release 8.0 MR1
#::'''mp_replication init -n 1 -r <''node2-eth0:0-hostname''> [-v]'''
#::'''mp_replication switchON '''
#*Release 8.0 FCS
#::'''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''
#::'''mp_replication switchON -r node2-eth0:0'''
#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.
#:Node 1 is the active Application Server and node 2 is the standby Application Server.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]

=== Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment ===

RSNA is typically used with Directory Service, which uses user database replication to enable two Cisco Unified MeetingPlace Application Servers in different sites to have synchronized user profiles and user groups.

===== Restriction =====

During the upgrade process, do not make any user or group configuration changes on any of the Application Servers. If you make configuration changes on one Application Server, they will not be ported to the other Application Server, because you turned off database replication.

If you do make any user or group configuration changes, follow the procedure below and then perform the initial setup procedures to synchronize the data between the two Application Servers. To synchronize the data, you will need to erase the database from one server and synchronize the data from the other server.

See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Configure Application Server Failover|How to Configure Application Server Failover]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module.

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

The instructions for upgrading Application Servers that are used in an RSNA deployment include the following prerequisite actions, which avoids the creation of duplicate or unsynchronized user profiles of type ''delegate'', ''attendant'', or ''system administrator'' on the Application Servers.
# If you created any identical user profiles of type delegate, attendant, or system administrator on both Application Servers, then delete those user profiles from ''one'' of the servers.
#: For example, if you created a system administrator profile A1 in each of the two servers S1 and S2, then delete A1 from either S1 or S2.
# Synchronize the user data in both Application Servers by using ''one'' of the following methods:
#* For each user profile you deleted from one Application Server, update the identical user profile on the ''other'' Application Server.
#*: Updating a user profile automatically causes the profile record to be replicated to the other Application Server.
#* Enter the following command in the Application Server CLI, specifying the hostnames of the Application Servers:
#*: '''mp_replication switchON -r''' ''hostname-remote'' '''-S -F''' ''hostname-local''
: This process may take a long time, depending on the total number of user profiles on the Application Servers and the network bandwidth between them.

'''Note: ''' Note the following nomenclature that is used for clarity: node 1 is the server that is in site 1 and node 2 is the server that is in site 2.

===== Procedure =====

# Sign in to the CLI of node 1.
# Enter '''su - '''to switch to the root user.
# Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.
#: The system displays the queue column as zeroes.
# Enter '''mp_replication switchOFF -r ''''''node_2'''''_IP_address'' on node 1, to switch off replication between the two Application Servers, where ''node_2_IP_address''''' '''is the IP address for node 2.
# Enter '''mp_replication teardown -r ''''''node_2_IP_address '''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_IP_address''''' '''is the IP address for node 2.
# Archive and save the configuration data on node 1.
# Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]].
# Sign in to the CLI of node 2.
# Enter '''su - '''to switch to the root user.
# Enter '''mp_replication teardown -r ''''''node 1_IP_address '''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_IP_address''''' '''is the IP address for node 1.
# Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]].
#: Both Application Servers have been upgraded.
# Sign in to the CLI of node 2.
# Enter '''su - '''to switch to the root user.
# Enter the following command using the hostname of node 1:
#* Release 8.0 MR1
#: '''mp_replication init -n 2 -r''' <''node1-eth0:0-hostname''> '''[-v]'''
#* Release 8.0 FCS
#: '''mp_replication init -s 2 -n 1 -r ''''''hostname_of_node_1'''''' -m '''
# Sign in to the CLI of node 1.
# Enter '''su - '''to switch to the root user.
# Enter the following commands using the hostname of node 2:
#* Release 8.0 MR1
#:: '''mp_replication init -n 1 -r''' <''node2-eth0:0-hostname''> '''[-v]'''
#:: '''mp_replication switchON '''
#* Release 8.0 FCS
#:: '''mp_replication init -s 1 -n 1 -r ''''''hostname_of_node_2'''''' -m '''
#:: '''mp_replication switchON -r '''''hostname_of_node_2''

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]

=== Completing the Application Server Software Upgrade ===
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Merging Email Notification Templates|Merging Email Notification Templates]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restoring Email Notification Values|Restoring Email Notification Values]]

==== Merging Email Notification Templates ====

When you upgrade the Application Server software from an earlier release, the upgrade program overwrites all custom email notification templates and replaces them with the standard email notification templates for the release to which you are upgrading. However, before the upgrade process begins, the upgrade program moves all of the email notification templates for the original release to a backup directory under /opt/cisco/meetingplace/var.

After upgrading the Application Server software, merge the new email notification templates with the templates from the previous release. See the [[Cisco Unified MeetingPlace Release 8.0 -- Customizing Email Notifications for Cisco Unified MeetingPlace#Customizing Email Notifications for Cisco Unified MeetingPlace|Customizing Email Notifications for Cisco Unified MeetingPlace]] module for complete information on customizing your email notification templates.

==== Restoring Email Notification Values ====

The upgrade process also overwrites all the configuration values for the SMTP and Exchange servers. After upgrading the Application Server software, you must manually restore the SMTP and Exchange server values.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''System Configuration > Email Notifications > SMTP Server Configuration'''.
# Enter values in all fields.
# Select '''Save'''.
# Select '''System Configuration > Email Notifications > Exchange Server Configuration'''.
# Enter values in all fields.
# Select '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#SMTP Server Configuration Page|SMTP Server Configuration Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Exchange Server Configuration Page|Exchange Server Configuration Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]] module

=== How to Test the Application Server Software Upgrade ===

After upgrading the Application Server software, perform these tests to ensure that the upgrade was successful.
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Checking the System Status|Checking the System Status]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Testing the Basic Installation|Testing the Basic Installation]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Validating the Ethernet Connection|Validating the Ethernet Connection]]

==== Checking the System Status ====

===== Procedure =====

# Go to the Application Server operating system sign-in page.
# Sign in as the user called '''root'''.
# Enter the password associated with this username.
#: The system displays the operating system desktop.
# Choose '''Application > System Tools > Terminal'''.
#: The system displays the command line.
# Enter '''mpx_version''' and verify that the Application Server version on your system matches the version to which you upgraded.
#: '''Note: ''' To ensure that your server has adequate disk space, the upgrade program removes many of the older versions of the Application Server software that are on your system. Therefore, when you run the''' mpx_version''' command, you may not see every version that you have ever installed.
# Enter '''mpx_sys status''' and ensure that most services are running:
#* The license service will not be running.
#* If you chose to install an Express Media Server, the video administration and SIP server services will not be running.
#* All other services should be running.

==== Testing the Basic Installation ====

===== Procedure =====

# Go to the Application Server operating system sign-in page.
# Sign in as the user called '''mpxadmin'''.
# Enter the password associated with this username.
#: The system displays the operating system desktop.
# Choose '''Application > Internet > Firefox Web Browser''' to go to the Internet.
# Enter the hostname for the Application Server.
#: The system displays the Cisco Unified MeetingPlace Administration Center sign in page.
# Ensure that the version number on the bottom of the page is the correct version.

==== Validating the Ethernet Connection ====

Follow this procedure to ensure that the Application Server is properly connected to the network.

===== Restriction =====
* This procedure assumes that you have an Ethernet cable connected from the Application Server to your company network.

===== Procedure =====

# Go to the Application Server operating system sign-in page.
# Sign in as the user called '''root'''.
# Enter the password associated with this username.
#: The system displays the operating system desktop.
# Choose '''Application > System Tools > Terminal'''.
#: The system displays the command line.
# Enter '''ethtool eth0''' to see the Ethernet port status.
#: The system displays a status of the network.
# Ensure that the "link detected" parameter at the bottom says '''yes'''.
#: '''Note: ''' If it says no, the Application Server is not connected to the network. Contact your network administrator to determine why it is not connected to the network.

=== Troubleshooting the Application Server Software Upgrade ===

'''Problem: ''' There is not enough disk space to update the Application Server software.

'''Explanation: ''' Unneeded files are in the /opt and other directories, taking up space.

'''Recommended Action: ''' Contact Cisco TAC, who can help you identify and remove unnecessary files from the relevant partitions.

'''Problem: ''' The upgrade installer does not have enough space in the / directory.

'''Explanation: ''' You downloaded the upgrade file onto your desktop, which stores it in the /home/''user_name''/Desktop directory. That directory uses the space from the / directory.

'''Solution: ''' Remove the downloaded file from the /home/''user_name''/Desktop directory to free up space.

'''Error Message: ''' There is not enough space to extract the upgrade installer file.

'''Recommended Action: ''' Ensure that there are no large, extraneous files in the /opt partition.

'''Error Message: ''' Cannot upgrade the Application Server software because there is no earlier version already installed on the server.

'''Explanation: ''' You must have at least one previous version on your system before you can upgrade.

'''Recommended Action: ''' Install the Application Server software.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module

'''Error Message: ''' The installer has found an equal or newer version this update.

'''Explanation: ''' You must have at least one older version of the Application Server software on your system before you can upgrade.

'''Recommended Action: ''' Install a newer version of the Application Server software.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module

'''Problem: ''' The upgrade is taking several hours.

'''Solution: ''' The upgrade takes approximately two hours, because it backs up the operating system and database. If it takes significantly longer, restart the upgrade process.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]

'''Error Message: ''' Warning - Not enough memory. If you continue, system performance may be impacted. It is highly recommended that you exit the installation and install more memory.

'''Explanation: ''' We recommend that the server that you upgrade have 4 GB of memory. However, you can still upgrade a server with only 2 GB of memory.

'''Recommended Action: ''' Install more memory.

===== Related Topics =====
* ''System Requirements for Cisco Unified MeetingPlace Release 8.0'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.0_--_System_Requirements_for_Cisco_Unified_MeetingPlace_Release_8.0

'''Problem: ''' The upgrade program says that the database is corrupted.

'''Solution: ''' Run the mpx_db command to check the status of the database.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]

== How to Upgrade the Web Server Software ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restrictions for Upgrading the Web Server Software|Restrictions for Upgrading the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Recommendations for Upgrading the Web Server Software|Recommendations for Upgrading the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Backing Up Data|Backing Up Data]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Working with the Cisco Security Agent (CSA)|Working with the Cisco Security Agent (CSA)]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Web Server Software|Upgrading the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Allowing Guest Users to Dial Out|Allowing Guest Users to Dial Out]]

=== Restrictions for Upgrading the Web Server Software ===
* Upgrade the Application Server before you upgrade the web server software.
* Do not interrupt the upgrade during the automatic system shutdown or reboot.
* If your system has multiple web servers, you must upgrade them all to the same version. You can upgrade them in any order.

=== Recommendations for Upgrading the Web Server Software ===
* We recommend that you only upgrade the Web Server software after hours. To avoid losing recordings, do not upgrade the Web Server software if there are any meetings that are currently in session that have recordings or if any meetings with recordings have recently ended, because the system may not have posted the recording yet posted to the attachment and recording page.
* We do not support upgrading the Cisco Unified MeetingPlace Web Server software by using Terminal Services.

=== Backing Up Data ===

Follow the instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server#How to Back Up and Restore MPWEB SQL Database|How to Back Up and Restore MPWEB SQL Database]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server#Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server|Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server]] module for information on backing up the data on the Web Server.

Manually back up the notification templates for the Microsoft Outlook back-end deployment; however, you do not have to back up the notification templates for SMTP and the Microsoft Outlook front-end deployment because the system copies all of the notification templates for SMTP and the Microsoft Outlook front-end deployment to a backup directory under /opt/cisco/meetingplace/var.

=== Working with the Cisco Security Agent (CSA) ===

If the Cisco Security Agent (CSA) is installed on your system, before you upgrade the web server, you must stop CSA, uninstall it, and install the version of CSA that is on the Cisco Unified MeetingPlace Web Server DVD.
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Uninstalling the Cisco Security Agent (CSA)|Uninstalling the Cisco Security Agent (CSA)]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Reinstalling the Cisco Security Agent (CSA)|Reinstalling the Cisco Security Agent (CSA)]]

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

''Release Notes for Cisco Security Agent for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/secursw/ps5057/prod_release_notes_list.html.

==== Uninstalling the Cisco Security Agent (CSA) ====

===== Procedure =====

# Sign into the Web Server.
# Choose '''Start > Control Panel > Add or Remove Programs'''.
# Highlight '''Cisco Security Agent'''.
# Select '''Change/Remove'''.
# Follow the prompts to remove the program.
# Reboot the system.

==== Reinstalling the Cisco Security Agent (CSA) ====

See [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Web Server Software#Installing the Cisco Security Agent on the Web Server|Installing the Cisco Security Agent on the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Web Server Software#Installing the Cisco Unified MeetingPlace Web Server Software|Installing the Cisco Unified MeetingPlace Web Server Software]] module.

===== Troubleshooting =====

If you run into problems while installing the CSA, contact Cisco TAC. Examples of problems include if you are installing the CSA and the system aborts the installation or if the system does not let you reinstall or uninstall the CSA.

=== Upgrading the Web Server Software ===

===== Procedure =====

# Exit any open applications.
# Insert the Cisco Unified MeetingPlace Web Server DVD into the DVD-ROM drive.
# Double-click the '''CiscoUnifiedMeetingPlaceWebServer.exe''' file to begin the upgrade.
#: The system displays informational screens. The system stops the web master service and the Gateway SIM service.
# Select '''Next'''.
#: The system copies files.
# Select '''Finish''' when done.
#: The system finishes the Gateway SIM upgrade.
# Select '''OK''' when it is done.
#: The installation wizard continues to install the Cisco Unified MeetingPlace Web Server software.
# Select '''Next'''.
#: The system starts copying the files.
# Choose the option to restart the Web Server on the Web Server InstallShield Wizard Complete window.
# Select '''Finish'''.
#: The upgrade finishes with a single system reboot.
# Ensure that the Windows Time Service is up and running.

===== Related Topics =====
* For information about configuring the Web Server to synchronize with an NTP server, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring the Time for the Web Server|Configuring the Time for the Web Server]] in the'' ''[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring Time and Time Zones for Cisco Unified MeetingPlace|Configuring Time and Time Zones for Cisco Unified MeetingPlace]] module.

=== Allowing Guest Users to Dial Out ===

After you have upgraded the Web Server on your system, if you want to allow guests to be able to dial out to other users, set the following parameters ''for the guest profile'':

{| border = 1
|-
!'''Can dial out''' parameter in the Administration Center
!Call-in teleconferencing checkbox in Cisco WebEx (1)
!Result
|-
|

Yes
|

checked
|
* Guests can dial out from the telephone
* Guests cannot dial out from the meeting room
|-
|

Yes
|

not checked
|
* Guests can dial out from the telephone
* Guests can dial out from the meeting room
|-
|

No
|

checked
|
* Guests cannot dial out from the telephone
* Guests cannot dial out from the meeting room
|-
|

No
|

not checked
|

Not recommended.
|}

Footnote 1: To find this parameter, in Cisco WebEx go to '''Site Administration > Manage Site > Site Settings > Default site audio options'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting Dial-Out Privileges for Guest Users|Restricting Dial-Out Privileges for Guest Users]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Overview of Security Tasks|Overview of Security Tasks]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

== About Upgrading Cisco WebEx ==

This section only applies to Cisco Unified MeetingPlace Release 7.0 systems that use Cisco WebEx.

=== Upgrading the Cisco WebEx Release ===

When you upgrade from Cisco Unified MeetingPlace Release 7.0 to Cisco Unified MeetingPlace Release 8.0, you must also upgrade from the Cisco WebEx WBS26 Release to the Cisco WebEx WBS27 Release.

You cannot upgrade Cisco WebEx yourself. To upgrade to the Cisco WebEx WBS27 Release, you must notify the Cisco WebEx Customer Support Engineer (CSE) that you plan to upgrade Cisco Unified MeetingPlace from Release 7.0 to Release 8.0 and then ask the CSE to upgrade your release of Cisco WebEx. In order to avoid a delay in implementing your upgrade, we recommend that you schedule the Cisco WebEx upgrade as far in advance as possible of your Cisco Unified MeetingPlace upgrade.

=== Making Recordings Accessible to Users ===

Recordings that were created using Cisco Unified MeetingPlace Release 7.0 must be moved to a location where they can be accessed by Cisco Unified MeetingPlace Release 8.0 users.

This procedure only applies if both the following are true:
* You are upgrading your system from Release 7.0 to Release 8.0
* The Cisco WebEx site name for your Release 8.0 system is different from the Cisco WebEx site name for your Release 7.0 system.

===== Procedure =====

# Navigate to the Cisco WebEx Site Administration page for the Release 7.0 system.
# Sign in with the credentials that you use to sign into the Application Server.
# Navigate to the user page for the admin user.
# Select '''My WebEx'''.
# Select '''My Files''' on the left.
# Select the '''My Recordings''' tab.
# If there are any recordings, delete them by doing the following:
## On the line with the recording name, click the down arrow on the right.
## Select '''Delete'''.
## Select '''OK''' in the confirmation dialog box.
## Continue until you have deleted all the recordings.
# Select '''Site Administration'''.
# Select '''Edit User List''' on the left.
# In the User name field, enter the user name for the user who has recordings that need to be moved to the new server.
# Select '''Search'''.
# Select the name of the user to go to the account for this user on the Release 7.0 system.
# Select '''Re-assign NBR Recordings'''.
#: The system displays a dialog box where you can reassign the recordings for the user.
# In the Search field, enter '''admin'''.
# Select '''Search'''.
# Select '''Yes''' in the confirmation dialog box.
#: The system moves all the recordings for that user to the admin user's account.
# Continue Step 9 to Step 16 for all users on the Release 7.0 system who have recordings.
# Navigate to the user page for the admin user.
# Select '''My WebEx'''.
# Select '''My Files''' on the left.
# Select the '''My Recordings''' tab.
# For each meeting, select the name of the meeting, which is displayed under the "Topic" header.
# Download the recording by doing the following:
## On the line with the recording name, click the down arrow on the right.
## Select '''Download'''.
## Save the file to a convenient location.
## Continue until you have downloaded all the recordings.

== How to Upgrade the Software for the Hardware Media Server ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Hardware Media Server Software Upgrade Utility|Hardware Media Server Software Upgrade Utility]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting Errors When Upgrading the Software for the Hardware Media Server|Troubleshooting Errors When Upgrading the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Recommendations for Moving an Audio Blade to a Different Hardware Media Server|Recommendations for Moving an Audio Blade to a Different Hardware Media Server]]

=== Hardware Media Server Software Upgrade Utility ===

Use the Hardware Media Server Software upgrade utilities to upgrade the Hardware Media Server software. The utilities upload files via a network connection to the Hardware Media Server. You can choose to perform a typical upgrade (which includes all the new files) or a customized upgrade (which enables you to select which files to upload). You can upgrade either the Audio Blade software or the Video Blade software depending on your deployment. You may need both the Audio Blade and Video Blade upgrade utilities.

The software upgrade utility resets the Audio Blade password and SNMP community names back to the factory default settings. To restore the previous Audio Blade password and SNMP community names, either put the Audio Blade online or synchronize the Audio Blade. Note that the synchronization process will not overwrite a set password; it will only overwrite a factory default password.

Information for any other administrative users in the Media Server Administration for the Hardware Media Server is lost during an upgrade.

=== How to Upgrade the Software for the Hardware Media Server ===
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restrictions for Upgrading the Software for the Hardware Media Server|Restrictions for Upgrading the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Launching the Upgrade Utility|Launching the Upgrade Utility]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Audio Blades|Upgrading the Software for Audio Blades]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Video Blades|Upgrading the Software for Video Blades]]

==== Restrictions for Upgrading the Software for the Hardware Media Server ====
* Upgrade the Application Server before you upgrade the Hardware Media Server.
* When you upgrade the Hardware Media Server software, the system resets all of the Audio Blade configuration settings (except for the network interface configuration). You must reapply any custom settings that you have previously made to the Audio and Video Blades after the upgrade procedure is complete.

==== Launching the Upgrade Utility ====

===== Procedure =====

# Download the'' ''executable file from the Cisco Unified MeetingPlace 3500 Series Media Server Software CD-ROM:
#* To upgrade the software for Audio Blades, the file is called AudioBladeUpgrade.exe.
#* To upgrade the software for Video Blades, the file is called VideoBladeUpgrade.exe.
# Double click the file to run the upgrade utility.
#: The system extracts the upgrade files and displays the Upgrade Utility dialog box.

===== What To Do Next =====
* To upgrade the software for the Audio Blades, go to [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Audio Blades|Upgrading the Software for Audio Blades]].
* To upgrade the software for the Video Blades, go to [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Video Blades|Upgrading the Software for Video Blades]].

==== Upgrading the Software for Audio Blades ====

===== Before You Begin =====
* Make sure that no meetings are active.

===== Procedure =====

# Sign in as an administrator to the Media Server Administration for the Hardware Media Server.
# Take the Audio Blade offline.
#: '''Note: ''' Failure to take the Audio Blade offline before the upgrade can result in an inconsistent state, with a variety of possible symptoms including dead air when dialing into the system.
# Enter the IP address of the Audio Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.
# Enter the administrator user name and password for the Audio Blade, as configured in the device network configuration settings, in the Login Information section.
# (Optional) Modify the read and write community settings for the Audio Blade as follows:
## Select '''Customize SNMP Settings...'''.
## Enter the required read community and write community values.
##: '''Note: ''' We recommend that you modify the default settings for security purposes.
## Select '''OK''' to return to the Upgrade Utility dialog box.
# (Optional) Select the components of the Audio Blade that you want to upgrade as follows:
## Select '''Customize...''' in the Upgrade Information section.
## Check the components that you want to upgrade.
##: '''Note: ''' The components displayed vary according to the hardware that is upgraded.
## Select '''OK''' to return to the Upgrade Utility dialog box.
# Select '''Upgrade''' to upgrade all components of the software (or only those components you manually selected via the Customize option).
#: The upgrade utility informs you whether the upgrade is successful.
#: '''Note: ''' When the upgrade is complete, the Audio Blade automatically resets itself and starts operation with the new software version.
# Upgrading the Audio Blades resets the user credentials. Sign in to the Media Server Administration for the Hardware Media Server by using the user name of "admin" and the password of "password".
# To improve security, we recommend that you change the user name and password.
# Repeat steps 3 to 7 for any other Audio Blades that need to be upgraded.
# Put the Audio Blade online.
#: '''Note: ''' Putting the Audio Blade online restores the password and SNMP community names that were in effect before the upgrade. It also synchronizes the Application Server with the Audio Blade except for the meeting types.
# Repeat steps [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#2|2]] to [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#11|11]] for each blade that was upgraded.
# Go to '''Resource Management > Meeting Types'''.
# Select '''Synchronize'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Signing in to the Media Server Administration for the Hardware Media Server|Signing in to the Media Server Administration for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Media Server Administration Password for the Hardware Media Server|Changing the Media Server Administration Password for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

===== What To Do Next =====
* If you previously customized your Audio Blades, manually reapply those customizations.

==== Upgrading the Software for Video Blades ====

===== Before You Begin =====
* Make sure that no meetings are active.

===== Procedure =====

# Sign in as an administrator to the Media Server Administration for the Hardware Media Server.
# Enter the IP address of the Video Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.
# Enter the administrator user name and password for the Video Blade, as configured in the device network configuration settings, in the Login Information section.
# (Optional) Select the components of the Video Blade that you want to upgrade as follows:
## Select '''Customize...''' in the Upgrade Information section.
## Check the components that you want to upgrade.
##: '''Note: ''' The components displayed vary according to the hardware that is upgraded.
## Select '''OK''' to return to the Upgrade Utility dialog box.
# Select '''Upgrade''' to upgrade all components of the software (or only those components you manually selected via the Customize option).
#: The software upgrade utility informs you whether the upgrade is successful.
#: '''Note: ''' When the upgrade is complete, the Video Blade automatically resets itself and starts operation with the new software version.
# Repeat steps 2 to 5 for any other Video Blades that need to be upgraded.
# Put the Video Blade online.
# Repeat steps 2 to 7 for each blade that was upgraded.
# Go to '''Resource Management > Meeting Types'''.
# Select '''Synchronize'''.
# Upgrading the Video Blades resets the user credentials. Sign in to the Media Server Administration for the Hardware Media Server by using the user name of "admin" and the password of "password".
# To improve security, we recommend that you change the user name and password.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Signing in to the Media Server Administration for the Hardware Media Server|Signing in to the Media Server Administration for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Audio and Video Blades for the Hardware Media Server#How to Configure Administrators for the Hardware Media Server|How to Configure Administrators for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Audio and Video Blades for the Hardware Media Server#Configuring the Audio and Video Blades for the Hardware Media Server|Configuring the Audio and Video Blades for the Hardware Media Server]] module

===== What To Do Next =====
* If you previously customized your Video Blades, manually reapply those customizations.

=== Troubleshooting Errors When Upgrading the Software for the Hardware Media Server ===

Use the following recovery procedure if the Hardware Media Server upgrade procedure fails and any further attempts to upgrade it are blocked by the following three error messages:

'''Error Message: '''Could not retrieve the target information. Your SNMP community settings might be incorrect. Click OK to continue the upgrade, or Cancel to review your SNMP community settings.

If you press OK, you see this error message:

'''Error Message: '''Setup cannot continue without obtaining target information through SNMP. Please reset the target manually or contact customer support for more help.

After that message, the system displays this error message:

'''Error Message: '''Upgrade process failed.

===== Procedure =====

# Sign in as an administrator to the Media Server Administration for the Hardware Media Server.
# Take the Audio Blade offline.
#: '''Note: ''' Failure to take the Audio Blade offline before the upgrade can result in an inconsistent state, with a variety of possible symptoms including dead air when dialing into the system.
# Enter the IP address of the Audio Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.
# Enter the administrator user name and password for the Audio Blade, as configured in the device network configuration settings, in the Login Information section.
# Select '''Customize''' from inside the Upgrade Information section.
#: The system displays the following message:
#::'''Error Message: '''The SNMP community settings do not match the target community. Press Retry to change the Read Community name.
# Select '''Ignore'''.
# In the Customize dialog box, ensure that only the following boxes are checked: MCU WEB Interface, MCU Config File, and MCU Factory Default Config File.
# Select '''OK'''.
# Select Upgrade.
# Select '''OK''' when the system displays the error message.
#: The system begins updating the three processes that you checked in step 7.
# When the upgrade is complete, run the upgrade utility again, without the customized settings.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Signing in to the Media Server Administration for the Hardware Media Server|Signing in to the Media Server Administration for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Recommendations for Moving an Audio Blade to a Different Hardware Media Server ===

When moving an Audio Blade from one Hardware Media Server to another (except when doing so for failover), we recommend the following best practices:
* Use different Audio Blade passwords and SNMP community names for each Hardware Media Server.
* Set the Audio Blade to permanently offline on the Hardware Media Server from which you are moving the Audio Blade. See [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module.

== How to Change from a Hardware Media Server to an Express Media Server ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About the Express Media Server|About the Express Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Changing the Type of Media Server that Your System Uses|Changing the Type of Media Server that Your System Uses]]

=== About the Express Media Server ===

Cisco Unified MeetingPlace Release 8.0 introduces an Express Media Server, a software version of the Hardware Media Server that was used in previous releases of Cisco Unified MeetingPlace. All systems that will use audio or video need a media server and the media server can be either a Hardware Media Server or an Express Media Server.
* The Express Media Server is a set of software modules, including an audio mixer and a video switcher, that resides on the Application Server. The Express Media Server creates a single box, software-only solution for Cisco Unified MeetingPlace.
* The Hardware Media Server is comprised of Audio and Video Blades.

All Cisco Unified MeetingPlace Release 8.0 systems automatically come with an Express Media Server.

=== Changing the Type of Media Server that Your System Uses ===

Follow these steps to change the type of media server that your system uses from a Hardware Media Server to an Express Media Server.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''System Configuration > Media Resource Configuration'''.
# Select '''Software''' for the System media mode field.
# Select '''Save'''.
#: The system reboots. When the system comes back up, it will be using an Express Media Server instead of a Hardware Media Server.

===== What To Do Next =====
* Configure the system for the Express Media Server. See the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module.

== Upgrading Microsoft Outlook for Cisco Unified MeetingPlace ==

'''Note: ''' The Microsoft Outlook for Cisco Unified MeetingPlace integration is the same for Cisco Unified MeetingPlace Release 7.0 Maintenance Release 1 and Cisco Unified MeetingPlace Release 8.0. Therefore, if you have already upgraded your Microsoft Outlook for Cisco Unified MeetingPlace integration to Release 7.0 Maintenance Release 1 or later, then you do not need to follow this procedure. Your integration is already upgraded.

To upgrade from Cisco Unified MeetingPlace Release 7.0 to Cisco Unified MeetingPlace Release 8.0, follow these steps:

{| border = 1
|-
!Step
!Step Description
!For more information, see
|-
|

1
|

Upgrade your Cisco Unified MeetingPlace Release 7.0 system to Cisco Unified MeetingPlace Release 8.0
|
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Web Server Software|How to Upgrade the Web Server Software]]* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
|-
|

2
|

Uninstall the Microsoft Outlook for Cisco Unified MeetingPlace integration Release 7.0 from the Web Server.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Uninstalling Cisco Unified MeetingPlace for Microsoft Outlook Gateway From the Web Server|Uninstalling Cisco Unified MeetingPlace for Microsoft Outlook Gateway From the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module
|-
|

3
|

Configure the Microsoft Exchange Server.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Configuring the Cisco Unified MeetingPlace Connection to the Microsoft Exchange Server|Configuring the Cisco Unified MeetingPlace Connection to the Microsoft Exchange Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module
|-
|

4
|

From the Application Server, run the following Cisco Unified MeetingPlace-Microsoft Exchange migration script: /opt/cisco/meetingplace/migrationtools/current/notifications/migrateExchangeForICAL.sh.
|
|}

'''Note: ''' The upgrade process may take a long time if many meetings need to be migrated. To speed up the upgrade, purge old meetings from the Cisco Unified MeetingPlace-dedicated mailbox and empty the Deleted Items folder. We recommend that the mailbox have fewer than 1360 appointment items or 32 KB of appointment data before you run the upgrade script.

===== What To Do Next =====

After you complete the upgrade process, have your users upgrade the Cisco Unified MeetingPlace plug-in for Microsoft Outlook on their PCs. They can do this themselves by doing one of the following:
* Select '''Download Outlook Plug-In''' from the Cisco Unified MeetingPlace web user portal.
* Select '''Upgrade to newer version''' from the MeetingPlace tab in a Microsoft Outlook calendar appointment.

== Testing that the Upgraded System Works Correctly ==

Verify the following after you upgrade and configure the entire Cisco Unified MeetingPlace system:

===== Licenses =====
* Your system has all the necessary licenses installed. See the ''Planning Guide for Cisco Unified MeetingPlace Release 8.0'' at: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment for information about Cisco Unified MeetingPlace Release 8.0 licenses.

===== Database Import =====
* Ensure that the following information imported correctly: user groups, user profiles, video terminal profiles, video types, video usage assignments, meeting categories, and password expirations.
* Ensure that all recorded names for user profiles were imported correctly.
* Ensure that all scheduled meetings, both past and recurring, imported correctly.
* Ensure that the default video mode assigned to user profiles matches the global video mode that was previously assigned to the user profile.

===== Scheduling =====
* Ensure that you can schedule a meeting.
* Ensure that the system sends an email notification for the meeting that you scheduled.
* Ensure that you can join and attend the meeting via audio, video, and web.
* Test that the dial in and dial out features work.

===== System Access =====
* Ensure that you have access to all of the Administration Center pages, including Conference Manager. To access the Administration Center, go to a web browser and enter http://''your-app-server''

===== Recordings =====
* Ensure that you can record a meeting.
* Ensure that you can play back the meeting recording.

== Completing the Upgrade ==

* Inform end users that the system has been successfully upgraded.
* During the upgrade process, only users who were ''moderators'' for a Cisco Unified MeetingPlace Release 7.0 meeting are converted to alternate hosts in Cisco Unified MeetingPlace Release 8.0. Meeting attendees or presenters for Cisco Unified MeetingPlace Release 7.0 meetings are only converted to meeting attendees in Cisco Unified MeetingPlace Release 8.0.
: In Cisco Unified MeetingPlace Release 8.0, only a host or an alternate host can start a meeting. After an upgrade, users may find that meetings only have one host and no alternate host and may experience not being able to start a meeting.
: We recommend that after you upgrade your system, you inform end user about this restriction and suggest that meeting owners designate alternate hosts for their meetings. This must be done before the meeting begins and only the meeting owner or delegate can modify a meeting.
* If you have upgraded your system to a Release 8.0 system with Cisco WebEx scheduling and without directory services integration, then the user passwords are not recognized after you import your user profiles into Cisco WebEx. (Cisco Unified MeetingPlace passwords are encrypted whereas Cisco WebEx uses plain text passwords.)
: When they next log in to Cisco WebEx, ask your users to select '''Forgot your password''' and have them reset their password.

[[Category: Installation Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0

2012-02-09T00:24:22Z

Dunn: /* Procedure */ edit text bold/italics

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

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Installation, Upgrade and Migration|Installation, Upgrade and Migration]]

* You can upgrade to Cisco Unified MeetingPlace Release 8.0 Maintenance Release 1 (MR1) from Cisco Unified MeetingPlace:
:* Release 7.0.1.4 (the FCS version)
:* Release 7.0.2.14 (the Maintenance Release 1 version)
:* Release 7.0.3.4 (the Maintenance Release 2 version)
:* Release 8.0.1.3 (the FCS version)
:* Release 8.0.1.229 (the Patch 1 version)

'''Note:''' If you are upgrading from Release 8.0 FCS or Release 8.0 Patch 1 to Release 8.0 MR 1, then complete the upgrade procedure in this module.

* You can upgrade to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace:
:* Release 7.0.1.4 (the FCS version)
:* Release 7.0.2.14 (the Maintenance Release 1 version)

* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading|About Upgrading]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Web Server Software|How to Upgrade the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading Cisco WebEx|About Upgrading Cisco WebEx]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Change from a Hardware Media Server to an Express Media Server|How to Change from a Hardware Media Server to an Express Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Microsoft Outlook for Cisco Unified MeetingPlace|Upgrading Microsoft Outlook for Cisco Unified MeetingPlace]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Testing that the Upgraded System Works Correctly|Testing that the Upgraded System Works Correctly]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Upgrade|Completing the Upgrade]]

== About Upgrading ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Changes between Release 7.0 and Release 8.0|Changes between Release 7.0 and Release 8.0]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Recommendations|Recommendations]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrade Procedure|Upgrade Procedure]]

=== Changes between Release 7.0 and Release 8.0 ===

* (Release 8.0 MR1 only) Existing Release 7.0 MR1 and MR2 audio-only deployments, or deployments with Cisco Unified MeetingPlace scheduling and Cisco Unified MeetingPlace meetings, are automatically converted to deployments with Cisco Unified MeetingPlace scheduling and Cisco WebEx meetings, following an upgrade to Release 8.0 MR1. Sign in to the Administration Center and select '''System Configuration > Cisco WebEx Configuration > Cisco WebEx Site and Server '''. Change your configuration back to your original deployment type.
* The Cisco Unified MeetingPlace Release 7.0 system had two options for web conferencing: using the Cisco Unified MeetingPlace meeting room and using the Cisco WebEx meeting room. In Release 8.0, Cisco Unified MeetingPlace only offers the Cisco WebEx meeting room.
* For systems that are upgraded, the software that ran the Cisco Unified MeetingPlace meeting room will remain on the upgraded system in order to allow users to play back meetings that were recorded in Release 7.0. The old software cannot be used for scheduling or attending meetings.
* In upgraded systems, the SSL/TLS page in the Administration Center shows two SSL configuration fields. The second SSL configuration field is required to play back meeting recordings from Cisco Unified MeetingPlace Release 7.0.
* Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0 will continue to use two NICs (IP addresses); however, new Cisco Unified MeetingPlace Release 8.0 systems only use one NIC.
* In Cisco Unified MeetingPlace Release 7.0, there were two fields to describe licensed capacity: '''Use licensed audio capacity''' and '''Use licensed video capacity'''. In Cisco Unified MeetingPlace Release 8.0, these two fields are combined into one field called '''Use licensed capacity'''. The value of the new field in Cisco Unified MeetingPlace Release 8.0 is set to the value of the '''Use licensed audio capacity''' in Cisco Unified MeetingPlace Release 7.0.
* For Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0, you must ensure that the remote storage location is accessible; otherwise, some of the web master services may fail to start properly which can cause the system to try to restart all the services.
* Cisco Unified MeetingPlace Release 7.0 meetings describe meeting attendees using the terms moderators, presenters, and audience. Cisco Unified MeetingPlace Release 8.0 meetings use the terms host, alternate host, and attendee. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Upgrade|Completing the Upgrade]] for more information about how user types in Release 7.0 are converted for Release 8.0.
* Cisco Unified MeetingPlace Release 8.0 does not have lecture-style meetings.
* Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0 will keep the current setting for the "Dial-out calls enabled via guest profile" parameter; however, new Cisco Unified MeetingPlace Release 8.0 systems will set the default value for that parameter to '''Yes'''. This means that systems that are upgraded to Release 8.0 may not allow guest users to dial out from the meeting room automatically even though new installations will allow this.

=== Recommendations ===

We recommend that you upgrade your Cisco Unified MeetingPlace system during a time when there is not much meeting traffic, for example, over a weekend or a period of extended downtime.

=== Upgrade Procedure ===

Follow these steps to upgrade to Cisco Unified MeetingPlace Release 8.0.

===== Procedure =====

{| border = 1
|-
!Step
!Step Description
!Related Topics
|-
|

1
|

Notify end users of the planned upgrade and system downtime.
|
|-
|

2
|

Upgrade the Application Server software.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]
|-
|

3
|

Upgrade the Web Server software.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Web Server Software|How to Upgrade the Web Server Software]]
|-
|

4
|

(Optional) Upgrade Cisco WebEx.

'''Note: ''' Only applies to Cisco Unified MeetingPlace Release 7.0 systems that use Cisco WebEx.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading Cisco WebEx|About Upgrading Cisco WebEx]]
|-
|

5
|

Upgrade the Hardware Media Server software.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
|-
|

6
|

(Optional) Convert the Hardware Media Server to an Express Media Server.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Change from a Hardware Media Server to an Express Media Server|How to Change from a Hardware Media Server to an Express Media Server]]
|-
|

7
|

Install the Cisco WebEx Node for MCS.

'''Note: ''' Technically, installing the Cisco WebEx Node for MCS is optional. It is not required if your system is audio only. However, if your system will include web functionality, you must install the Cisco WebEx Node for MCS.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco WebEx Node for MCS#Installing the Cisco WebEx Node for MCS|Installing the Cisco WebEx Node for MCS]] module
|-
|

8
|

Configure your system to use Cisco WebEx.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco WebEx#Integrating Cisco Unified MeetingPlace with Cisco WebEx|Integrating Cisco Unified MeetingPlace with Cisco WebEx]] module
|-
|

9
|

(Optional) Upgrade the Microsoft Outlook for Cisco Unified MeetingPlace integration.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Microsoft Outlook for Cisco Unified MeetingPlace|Upgrading Microsoft Outlook for Cisco Unified MeetingPlace]]
|-
|

10
|

Test that the upgraded system works correctly.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Testing that the Upgraded System Works Correctly|Testing that the Upgraded System Works Correctly]]
|-
|

11
|

Inform end users that the system has been successfully upgraded.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Upgrade|Completing the Upgrade]]
|}

== How to Upgrade the Application Server Software ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About Upgrading the Application Server Software|About Upgrading the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Preparing to Upgrade the Application Server Software|Preparing to Upgrade the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restrictions and Recommendations for Upgrading the Application Server Software|Restrictions and Recommendations for Upgrading the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Determining Which Procedure to Follow|Determining Which Procedure to Follow]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment|Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Completing the Application Server Software Upgrade|Completing the Application Server Software Upgrade]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Test the Application Server Software Upgrade|How to Test the Application Server Software Upgrade]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting the Application Server Software Upgrade|Troubleshooting the Application Server Software Upgrade]]

=== About Upgrading the Application Server Software ===
* To upgrade the Application Server software, you must already have an existing version of the Application Server software installed on your server.
* When you upgrade the Application Server software, the upgrade program moves the existing files to a backup directory and installs the new files in the current directory.
* A fresh installation of the Application Server software erases the database that holds the Hardware Media Server configuration information; however, ''upgrading'' the Application Server software does not erase the database.
* The upgrade program backs up any Microsoft Outlook notification templates and copies them to /opt/cisco/meetingplace/var.
* We support using Integrated Lights-Out (iLO) to install and upgrade the Application Server software. This standard only applies to the Cisco MCS 7835-H2 and Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.

=== Preparing to Upgrade the Application Server Software ===
* Do ''not'' uninstall the Application Server software before you upgrade.
* The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.
* Back up all your data files. See the [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module.

=== Restrictions and Recommendations for Upgrading the Application Server Software ===
* (Upgrading to Release 8.0 from Release 7.0.1.4 FCS or from Release 7.0.2.14 MR1 version only.) If your Application Server is on a Cisco MCS 7835-I2 or a Cisco MCS 7835-H2, then we recommend you run the upgrade script from the /mpx-record directory. Enter '''df -h''' to determine the amount of available space. There should be a minimum of 6 GB available in the /mpx-record directory, when you run the upgrade script here. If you prefer to run the upgrade script from the /tmp directory, then there must be a minimum of 8 GB available in the /mpx-record directory.
* We recommend that the server that you are upgrading have 4 GB of memory. See the ''System Requirements for Cisco Unified MeetingPlace Release 8.0'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html
* Ensure that the system is not performing a database backup when you upgrade the Application Server software.
* The system must have a functional database. To ensure that the database is functional, go to the Command-Line Interface and run the '''/sbin/service mpx_db status''' command. See [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module.
* Have a valid DNS service configuration.
:This is mandatory for correct operation of the Cisco Unified MeetingPlace system.You need to enter a valid IP address for a DNS service during the installation of the Application Server. Without this, your upgrade may fail.
:You can test your DNS service by entering on the command-line interface, '''ping <''DNS_IP_Address''>'''. You should get a response in under 200 milliseconds.

=== Determining Which Procedure to Follow ===

Depending on the configuration of your Application Server, follow one of these steps:
* If your Application Server is in a failover deployment, follow the procedure in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Failover Deployment|Upgrading Application Servers that are Used in a Failover Deployment]]. After the upgrade, reconfigure the system for database replication.
* If your Application Server is in a Reservationless Single Number Access (RSNA) deployment, follow the procedure in the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment|Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment]].
* If your Application Server does not meet either of the above conditions, follow the procedure in either the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]] or the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]].

=== Upgrading the Application Server by Using the Console ===

'''Note: ''' Only perform this procedure if your system does not use failover or RSNA. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Determining Which Procedure to Follow|Determining Which Procedure to Follow]].

===== Before You Begin =====
* Take the Audio Blade offline.

===== Procedure =====

# Go to Cisco.com and find the upgrade file. The naming convention will be similar to upgrade_mp_''<version_number''>.bin, where <''version_number> ''is the version number to which you are upgrading.
#: '''Note: ''' The file is located near http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
# Save the file to a convenient location.
# Enter '''md5sum upgrade_mp_<''''''version_number>''''''.bin''' to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.
# From the console, go to the Cisco Unified MeetingPlace operating system sign-in page and sign in as the user called root.
# Right-click on the desktop and select '''New Terminal'''.
#: The upgrade program displays the command line.
# Navigate to the directory where you saved the upgrade file.
# Enter''' sh''' '''upgrade_mp_<'''''version_number'''''>''''''.bin''' '''&''' to execute the upgrade program.
#: The upgrade program displays the Introduction page.
# Select '''Next'''.
#: The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous versions found on the system.
#: '''Note: ''' If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.
# Select '''Next''' to begin the upgrade.
#: The upgrade program displays a pre-installation summary.
# Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.
# Select '''Install''' if all the values are correct.
#: The upgrade program upgrades all the required components associated with the Application Server software.
#: The upgrade program displays a message stating that the upgrade is complete.
# Select '''Done''' to restart the system.
# Synchronize the Hardware Media Server and meeting types.
# Put the Audio Blade back online.

===== Troubleshooting Tips =====
* See [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting the Application Server Software Upgrade|Troubleshooting the Application Server Software Upgrade]].

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Synchronizing Audio Blade Meeting Types with the Template Audio Blade|Synchronizing Audio Blade Meeting Types with the Template Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Upgrading the Application Server Remotely ===

'''Note: ''' Only perform this procedure if your system does not use failover or RSNA. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Determining Which Procedure to Follow|Determining Which Procedure to Follow]].

When you upgrade the Application Server software remotely, the upgrade status is limited. We recommend that you upgrade the Application Server at the console if possible.

===== Restrictions =====
* You must use the screen to perform a remote upgrade.

===== Before You Begin =====
* Take the Audio Blade offline.

===== Procedure =====

# Go to Cisco.com and find the upgrade file. The naming convention will be similar to upgrade_mp_<''version_number>''.bin, where <''version_number> ''is the version number to which you are upgrading.
#: '''Note: ''' The file is located near http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
# Save the file to a convenient, local location.
# Enter '''md5sum upgrade_mp_<''''''version_number''''''>.bin''' to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.
# Transfer the upgrade or patch file to Cisco Unified MeetingPlace using SCP file transfer.
# Using an SSH client, sign in as the user called mpxadmin.
# Enter '''screen -S mp_upgrade''' to create and attach to a screen named mp_upgrade.
# Change to the root user by entering '''su -''' and enter the root password.
# From the CLI, navigate to the directory where you saved the upgrade file.
# Enter '''sh ./upgrade_mp_<''''''version_number>''''''.bin -i console''' to execute the upgrade program.
#: The upgrade program displays an introduction message.
# Press '''Enter''' to continue.
#: The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous versions found on the system.
#: '''Note: ''' If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.
# Press '''Enter''' to continue.
# Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.
# Press '''Enter''' to begin the upgrade.
#: The upgrade program installs the Application Server upgrade.
#: When the upgrade is complete, the upgrade program displays the Install Complete page and a message stating that the upgrade is complete.
# Press '''Enter''' to restart the system.
#: '''Note: ''' When you restart the system, all existing screens are removed.
# Synchronize the Hardware Media Server and meeting types.
# Put the Audio Blade back online.

===== Troubleshooting =====

If the SSH remote session disconnects while you are upgrading the Application Server, follow these steps to reattach to the installation screen and continue the upgrade:
# Using an SSH client, sign in as the user called mpxadmin.
# Enter '''screen -ls '''to find out the full name of the screen created in Step 6 of the "Upgrading the Application Server Remotely" procedure. The full name of the screen consists of an identifier followed by a dot and then the name that you used in Step 6 of the "Upgrading the Application Server Remotely" procedure. For example, the full screen name might be 1665.mp_upgrade.
# Enter '''screen -rD '''''full_screen_name'' to reattach to the installation screen.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Synchronizing Audio Blade Meeting Types with the Template Audio Blade|Synchronizing Audio Blade Meeting Types with the Template Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Upgrading Application Servers that are Used in a Failover Deployment ===

===== Before You Begin =====
* Note the following nomenclature that is used for clarity: node 1 is the server that originally is the active Application Server and node 2 is the server that originally is the standby Application Server.
* Turn off failover before you begin.

===== Procedure =====

#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''su - '''to switch to the root user.
#Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.
#:The system displays the queue column as zeroes.
#Enter '''mp_replication switchOFF -r'''''node_2_eth0:0 ''on node 1, to switch off replication between the two Application Servers, where ''node_2_eth0:0''is the eth0:0 address for node 2.
#Enter '''mp_replication teardown -r '''''node_2_eth0:0 ''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_eth0:0''is the eth0:0 address for node 2.
#Archive and save the configuration data on node 1.
#Enter '''failoverUtil setDeployment singleServer '''to change the mode of node 1 to SingleServer.
#Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console|Upgrading the Application Server by Using the Console]].
#Enter '''failoverUtil setDeployment failover '''on node 1 to change the mode of node 1 to failover.
#:'''Note: ''' This disables the eth0 interface of node 1, so that node 2 can become active.
#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''su - '''to switch to the root user.
#Enter '''failoverUtil setServer active''' on node 2 to change its mode from standby to active.
#Enter '''mp_replication teardown -r '''''node_1_eth0:0 ''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_eth0:0''is the eth0:0 address for node 1.
#Enter '''failoverUtil setDeployment singleServer''' on node 2 to change its mode to SingleServer.
#Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console|Upgrading the Application Server by Using the Console]].
#Enter '''failoverUtil setDeployment failover''' on node 2 to change its mode to failover.

 At this point, both Application Servers are in standby mode.

#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Initialize database replication:
#*Release 8.0 MR1--Enter '''mp_replication init -n 2 -r <''node1-eth0:0-hostname''> [-v]'''
#*Release 8.0 FCS-- Enter'''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h'''
#Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
#Enter the following to initialize and start database replication:
#*Release 8.0 MR1
#::'''mp_replication init -n 1 -r <''node2-eth0:0-hostname''> [-v]'''
#::'''mp_replication switchON '''
#*Release 8.0 FCS
#::'''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''
#::'''mp_replication switchON -r node2-eth0:0'''
#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
#Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.
#:Node 1 is the active Application Server and node 2 is the standby Application Server.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]

=== Upgrading Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment ===

RSNA is typically used with Directory Service, which uses user database replication to enable two Cisco Unified MeetingPlace Application Servers in different sites to have synchronized user profiles and user groups.

===== Restriction =====

During the upgrade process, do not make any user or group configuration changes on any of the Application Servers. If you make configuration changes on one Application Server, they will not be ported to the other Application Server, because you turned off database replication.

If you do make any user or group configuration changes, follow the procedure below and then perform the initial setup procedures to synchronize the data between the two Application Servers. To synchronize the data, you will need to erase the database from one server and synchronize the data from the other server.

See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#How to Configure Application Server Failover|How to Configure Application Server Failover]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace#Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] module.

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

The instructions for upgrading Application Servers that are used in an RSNA deployment include the following prerequisite actions, which avoids the creation of duplicate or unsynchronized user profiles of type ''delegate'', ''attendant'', or ''system administrator'' on the Application Servers.
# If you created any identical user profiles of type delegate, attendant, or system administrator on both Application Servers, then delete those user profiles from ''one'' of the servers.
#: For example, if you created a system administrator profile A1 in each of the two servers S1 and S2, then delete A1 from either S1 or S2.
# Synchronize the user data in both Application Servers by using ''one'' of the following methods:
#* For each user profile you deleted from one Application Server, update the identical user profile on the ''other'' Application Server.
#*: Updating a user profile automatically causes the profile record to be replicated to the other Application Server.
#* Enter the following command in the Application Server CLI, specifying the hostnames of the Application Servers:
#*: '''mp_replication switchON -r''' ''hostname-remote'' '''-S -F''' ''hostname-local''
: This process may take a long time, depending on the total number of user profiles on the Application Servers and the network bandwidth between them.

'''Note: ''' Note the following nomenclature that is used for clarity: node 1 is the server that is in site 1 and node 2 is the server that is in site 2.

===== Procedure =====

# Sign in to the CLI of node 1.
# Enter '''su - '''to switch to the root user.
# Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.
#: The system displays the queue column as zeroes.
# Enter '''mp_replication switchOFF -r ''''''node_2'''''_IP_address'' on node 1, to switch off replication between the two Application Servers, where ''node_2_IP_address''''' '''is the IP address for node 2.
# Enter '''mp_replication teardown -r ''''''node_2_IP_address '''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_IP_address''''' '''is the IP address for node 2.
# Archive and save the configuration data on node 1.
# Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]].
# Sign in to the CLI of node 2.
# Enter '''su - '''to switch to the root user.
# Enter '''mp_replication teardown -r ''''''node 1_IP_address '''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_IP_address''''' '''is the IP address for node 1.
# Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]].
#: Both Application Servers have been upgraded.
# Sign in to the CLI of node 2.
# Enter '''su - '''to switch to the root user.
# Enter the following command using the hostname of node 1:
#* Release 8.0 MR1
#: '''mp_replication init -n 2 -r''' <''node1-eth0:0-hostname''> '''[-v]'''
#* Release 8.0 FCS
#: '''mp_replication init -s 2 -n 1 -r ''''''hostname_of_node_1'''''' -m '''
# Sign in to the CLI of node 1.
# Enter '''su - '''to switch to the root user.
# Enter the following commands using the hostname of node 2:
#* Release 8.0 MR1
#:: '''mp_replication init -n 1 -r''' <''node2-eth0:0-hostname''> '''[-v]'''
#:: '''mp_replication switchON '''
#* Release 8.0 FCS
#:: '''mp_replication init -s 1 -n 1 -r ''''''hostname_of_node_2'''''' -m '''
#:: '''mp_replication switchON -r '''''hostname_of_node_2''

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server#Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server|Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.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|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console|Upgrading the Application Server by Using the Console]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server Remotely|Upgrading the Application Server Remotely]]

=== Completing the Application Server Software Upgrade ===
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Merging Email Notification Templates|Merging Email Notification Templates]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restoring Email Notification Values|Restoring Email Notification Values]]

==== Merging Email Notification Templates ====

When you upgrade the Application Server software from an earlier release, the upgrade program overwrites all custom email notification templates and replaces them with the standard email notification templates for the release to which you are upgrading. However, before the upgrade process begins, the upgrade program moves all of the email notification templates for the original release to a backup directory under /opt/cisco/meetingplace/var.

After upgrading the Application Server software, merge the new email notification templates with the templates from the previous release. See the [[Cisco Unified MeetingPlace Release 8.0 -- Customizing Email Notifications for Cisco Unified MeetingPlace#Customizing Email Notifications for Cisco Unified MeetingPlace|Customizing Email Notifications for Cisco Unified MeetingPlace]] module for complete information on customizing your email notification templates.

==== Restoring Email Notification Values ====

The upgrade process also overwrites all the configuration values for the SMTP and Exchange servers. After upgrading the Application Server software, you must manually restore the SMTP and Exchange server values.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''System Configuration > Email Notifications > SMTP Server Configuration'''.
# Enter values in all fields.
# Select '''Save'''.
# Select '''System Configuration > Email Notifications > Exchange Server Configuration'''.
# Enter values in all fields.
# Select '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#SMTP Server Configuration Page|SMTP Server Configuration Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Exchange Server Configuration Page|Exchange Server Configuration Page]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]] module

=== How to Test the Application Server Software Upgrade ===

After upgrading the Application Server software, perform these tests to ensure that the upgrade was successful.
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Checking the System Status|Checking the System Status]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Testing the Basic Installation|Testing the Basic Installation]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Validating the Ethernet Connection|Validating the Ethernet Connection]]

==== Checking the System Status ====

===== Procedure =====

# Go to the Application Server operating system sign-in page.
# Sign in as the user called '''root'''.
# Enter the password associated with this username.
#: The system displays the operating system desktop.
# Choose '''Application > System Tools > Terminal'''.
#: The system displays the command line.
# Enter '''mpx_version''' and verify that the Application Server version on your system matches the version to which you upgraded.
#: '''Note: ''' To ensure that your server has adequate disk space, the upgrade program removes many of the older versions of the Application Server software that are on your system. Therefore, when you run the''' mpx_version''' command, you may not see every version that you have ever installed.
# Enter '''mpx_sys status''' and ensure that most services are running:
#* The license service will not be running.
#* If you chose to install an Express Media Server, the video administration and SIP server services will not be running.
#* All other services should be running.

==== Testing the Basic Installation ====

===== Procedure =====

# Go to the Application Server operating system sign-in page.
# Sign in as the user called '''mpxadmin'''.
# Enter the password associated with this username.
#: The system displays the operating system desktop.
# Choose '''Application > Internet > Firefox Web Browser''' to go to the Internet.
# Enter the hostname for the Application Server.
#: The system displays the Cisco Unified MeetingPlace Administration Center sign in page.
# Ensure that the version number on the bottom of the page is the correct version.

==== Validating the Ethernet Connection ====

Follow this procedure to ensure that the Application Server is properly connected to the network.

===== Restriction =====
* This procedure assumes that you have an Ethernet cable connected from the Application Server to your company network.

===== Procedure =====

# Go to the Application Server operating system sign-in page.
# Sign in as the user called '''root'''.
# Enter the password associated with this username.
#: The system displays the operating system desktop.
# Choose '''Application > System Tools > Terminal'''.
#: The system displays the command line.
# Enter '''ethtool eth0''' to see the Ethernet port status.
#: The system displays a status of the network.
# Ensure that the "link detected" parameter at the bottom says '''yes'''.
#: '''Note: ''' If it says no, the Application Server is not connected to the network. Contact your network administrator to determine why it is not connected to the network.

=== Troubleshooting the Application Server Software Upgrade ===

'''Problem: ''' There is not enough disk space to update the Application Server software.

'''Explanation: ''' Unneeded files are in the /opt and other directories, taking up space.

'''Recommended Action: ''' Contact Cisco TAC, who can help you identify and remove unnecessary files from the relevant partitions.

'''Problem: ''' The upgrade installer does not have enough space in the / directory.

'''Explanation: ''' You downloaded the upgrade file onto your desktop, which stores it in the /home/''user_name''/Desktop directory. That directory uses the space from the / directory.

'''Solution: ''' Remove the downloaded file from the /home/''user_name''/Desktop directory to free up space.

'''Error Message: ''' There is not enough space to extract the upgrade installer file.

'''Recommended Action: ''' Ensure that there are no large, extraneous files in the /opt partition.

'''Error Message: ''' Cannot upgrade the Application Server software because there is no earlier version already installed on the server.

'''Explanation: ''' You must have at least one previous version on your system before you can upgrade.

'''Recommended Action: ''' Install the Application Server software.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module

'''Error Message: ''' The installer has found an equal or newer version this update.

'''Explanation: ''' You must have at least one older version of the Application Server software on your system before you can upgrade.

'''Recommended Action: ''' Install a newer version of the Application Server software.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Application Server Software#Installing the Cisco Unified MeetingPlace Application Server Software|Installing the Cisco Unified MeetingPlace Application Server Software]] module

'''Problem: ''' The upgrade is taking several hours.

'''Solution: ''' The upgrade takes approximately two hours, because it backs up the operating system and database. If it takes significantly longer, restart the upgrade process.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]

'''Error Message: ''' Warning - Not enough memory. If you continue, system performance may be impacted. It is highly recommended that you exit the installation and install more memory.

'''Explanation: ''' We recommend that the server that you upgrade have 4 GB of memory. However, you can still upgrade a server with only 2 GB of memory.

'''Recommended Action: ''' Install more memory.

===== Related Topics =====
* ''System Requirements for Cisco Unified MeetingPlace Release 8.0'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.0_--_System_Requirements_for_Cisco_Unified_MeetingPlace_Release_8.0

'''Problem: ''' The upgrade program says that the database is corrupted.

'''Solution: ''' Run the mpx_db command to check the status of the database.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]

== How to Upgrade the Web Server Software ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restrictions for Upgrading the Web Server Software|Restrictions for Upgrading the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Recommendations for Upgrading the Web Server Software|Recommendations for Upgrading the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Backing Up Data|Backing Up Data]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Working with the Cisco Security Agent (CSA)|Working with the Cisco Security Agent (CSA)]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Web Server Software|Upgrading the Web Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Allowing Guest Users to Dial Out|Allowing Guest Users to Dial Out]]

=== Restrictions for Upgrading the Web Server Software ===
* Upgrade the Application Server before you upgrade the web server software.
* Do not interrupt the upgrade during the automatic system shutdown or reboot.
* If your system has multiple web servers, you must upgrade them all to the same version. You can upgrade them in any order.

=== Recommendations for Upgrading the Web Server Software ===
* We recommend that you only upgrade the Web Server software after hours. To avoid losing recordings, do not upgrade the Web Server software if there are any meetings that are currently in session that have recordings or if any meetings with recordings have recently ended, because the system may not have posted the recording yet posted to the attachment and recording page.
* We do not support upgrading the Cisco Unified MeetingPlace Web Server software by using Terminal Services.

=== Backing Up Data ===

Follow the instructions in [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server#How to Back Up and Restore MPWEB SQL Database|How to Back Up and Restore MPWEB SQL Database]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server#Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server|Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server]] module for information on backing up the data on the Web Server.

Manually back up the notification templates for the Microsoft Outlook back-end deployment; however, you do not have to back up the notification templates for SMTP and the Microsoft Outlook front-end deployment because the system copies all of the notification templates for SMTP and the Microsoft Outlook front-end deployment to a backup directory under /opt/cisco/meetingplace/var.

=== Working with the Cisco Security Agent (CSA) ===

If the Cisco Security Agent (CSA) is installed on your system, before you upgrade the web server, you must stop CSA, uninstall it, and install the version of CSA that is on the Cisco Unified MeetingPlace Web Server DVD.
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Uninstalling the Cisco Security Agent (CSA)|Uninstalling the Cisco Security Agent (CSA)]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Reinstalling the Cisco Security Agent (CSA)|Reinstalling the Cisco Security Agent (CSA)]]

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

''Release Notes for Cisco Security Agent for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/secursw/ps5057/prod_release_notes_list.html.

==== Uninstalling the Cisco Security Agent (CSA) ====

===== Procedure =====

# Sign into the Web Server.
# Choose '''Start > Control Panel > Add or Remove Programs'''.
# Highlight '''Cisco Security Agent'''.
# Select '''Change/Remove'''.
# Follow the prompts to remove the program.
# Reboot the system.

==== Reinstalling the Cisco Security Agent (CSA) ====

See [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Web Server Software#Installing the Cisco Security Agent on the Web Server|Installing the Cisco Security Agent on the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Installing the Cisco Unified MeetingPlace Web Server Software#Installing the Cisco Unified MeetingPlace Web Server Software|Installing the Cisco Unified MeetingPlace Web Server Software]] module.

===== Troubleshooting =====

If you run into problems while installing the CSA, contact Cisco TAC. Examples of problems include if you are installing the CSA and the system aborts the installation or if the system does not let you reinstall or uninstall the CSA.

=== Upgrading the Web Server Software ===

===== Procedure =====

# Exit any open applications.
# Insert the Cisco Unified MeetingPlace Web Server DVD into the DVD-ROM drive.
# Double-click the '''CiscoUnifiedMeetingPlaceWebServer.exe''' file to begin the upgrade.
#: The system displays informational screens. The system stops the web master service and the Gateway SIM service.
# Select '''Next'''.
#: The system copies files.
# Select '''Finish''' when done.
#: The system finishes the Gateway SIM upgrade.
# Select '''OK''' when it is done.
#: The installation wizard continues to install the Cisco Unified MeetingPlace Web Server software.
# Select '''Next'''.
#: The system starts copying the files.
# Choose the option to restart the Web Server on the Web Server InstallShield Wizard Complete window.
# Select '''Finish'''.
#: The upgrade finishes with a single system reboot.
# Ensure that the Windows Time Service is up and running.

===== Related Topics =====
* For information about configuring the Web Server to synchronize with an NTP server, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring the Time for the Web Server|Configuring the Time for the Web Server]] in the'' ''[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring Time and Time Zones for Cisco Unified MeetingPlace|Configuring Time and Time Zones for Cisco Unified MeetingPlace]] module.

=== Allowing Guest Users to Dial Out ===

After you have upgraded the Web Server on your system, if you want to allow guests to be able to dial out to other users, set the following parameters ''for the guest profile'':

{| border = 1
|-
!'''Can dial out''' parameter in the Administration Center
!Call-in teleconferencing checkbox in Cisco WebEx (1)
!Result
|-
|

Yes
|

checked
|
* Guests can dial out from the telephone
* Guests cannot dial out from the meeting room
|-
|

Yes
|

not checked
|
* Guests can dial out from the telephone
* Guests can dial out from the meeting room
|-
|

No
|

checked
|
* Guests cannot dial out from the telephone
* Guests cannot dial out from the meeting room
|-
|

No
|

not checked
|

Not recommended.
|}

Footnote 1: To find this parameter, in Cisco WebEx go to '''Site Administration > Manage Site > Site Settings > Default site audio options'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Restricting Dial-Out Privileges for Guest Users|Restricting Dial-Out Privileges for Guest Users]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Overview of Security Tasks|Overview of Security Tasks]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Securing the Cisco Unified MeetingPlace System#Securing the Cisco Unified MeetingPlace System|Securing the Cisco Unified MeetingPlace System]] module

== About Upgrading Cisco WebEx ==

This section only applies to Cisco Unified MeetingPlace Release 7.0 systems that use Cisco WebEx.

=== Upgrading the Cisco WebEx Release ===

When you upgrade from Cisco Unified MeetingPlace Release 7.0 to Cisco Unified MeetingPlace Release 8.0, you must also upgrade from the Cisco WebEx WBS26 Release to the Cisco WebEx WBS27 Release.

You cannot upgrade Cisco WebEx yourself. To upgrade to the Cisco WebEx WBS27 Release, you must notify the Cisco WebEx Customer Support Engineer (CSE) that you plan to upgrade Cisco Unified MeetingPlace from Release 7.0 to Release 8.0 and then ask the CSE to upgrade your release of Cisco WebEx. In order to avoid a delay in implementing your upgrade, we recommend that you schedule the Cisco WebEx upgrade as far in advance as possible of your Cisco Unified MeetingPlace upgrade.

=== Making Recordings Accessible to Users ===

Recordings that were created using Cisco Unified MeetingPlace Release 7.0 must be moved to a location where they can be accessed by Cisco Unified MeetingPlace Release 8.0 users.

This procedure only applies if both the following are true:
* You are upgrading your system from Release 7.0 to Release 8.0
* The Cisco WebEx site name for your Release 8.0 system is different from the Cisco WebEx site name for your Release 7.0 system.

===== Procedure =====

# Navigate to the Cisco WebEx Site Administration page for the Release 7.0 system.
# Sign in with the credentials that you use to sign into the Application Server.
# Navigate to the user page for the admin user.
# Select '''My WebEx'''.
# Select '''My Files''' on the left.
# Select the '''My Recordings''' tab.
# If there are any recordings, delete them by doing the following:
## On the line with the recording name, click the down arrow on the right.
## Select '''Delete'''.
## Select '''OK''' in the confirmation dialog box.
## Continue until you have deleted all the recordings.
# Select '''Site Administration'''.
# Select '''Edit User List''' on the left.
# In the User name field, enter the user name for the user who has recordings that need to be moved to the new server.
# Select '''Search'''.
# Select the name of the user to go to the account for this user on the Release 7.0 system.
# Select '''Re-assign NBR Recordings'''.
#: The system displays a dialog box where you can reassign the recordings for the user.
# In the Search field, enter '''admin'''.
# Select '''Search'''.
# Select '''Yes''' in the confirmation dialog box.
#: The system moves all the recordings for that user to the admin user's account.
# Continue Step 9 to Step 16 for all users on the Release 7.0 system who have recordings.
# Navigate to the user page for the admin user.
# Select '''My WebEx'''.
# Select '''My Files''' on the left.
# Select the '''My Recordings''' tab.
# For each meeting, select the name of the meeting, which is displayed under the "Topic" header.
# Download the recording by doing the following:
## On the line with the recording name, click the down arrow on the right.
## Select '''Download'''.
## Save the file to a convenient location.
## Continue until you have downloaded all the recordings.

== How to Upgrade the Software for the Hardware Media Server ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Hardware Media Server Software Upgrade Utility|Hardware Media Server Software Upgrade Utility]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting Errors When Upgrading the Software for the Hardware Media Server|Troubleshooting Errors When Upgrading the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Recommendations for Moving an Audio Blade to a Different Hardware Media Server|Recommendations for Moving an Audio Blade to a Different Hardware Media Server]]

=== Hardware Media Server Software Upgrade Utility ===

Use the Hardware Media Server Software upgrade utilities to upgrade the Hardware Media Server software. The utilities upload files via a network connection to the Hardware Media Server. You can choose to perform a typical upgrade (which includes all the new files) or a customized upgrade (which enables you to select which files to upload). You can upgrade either the Audio Blade software or the Video Blade software depending on your deployment. You may need both the Audio Blade and Video Blade upgrade utilities.

The software upgrade utility resets the Audio Blade password and SNMP community names back to the factory default settings. To restore the previous Audio Blade password and SNMP community names, either put the Audio Blade online or synchronize the Audio Blade. Note that the synchronization process will not overwrite a set password; it will only overwrite a factory default password.

Information for any other administrative users in the Media Server Administration for the Hardware Media Server is lost during an upgrade.

=== How to Upgrade the Software for the Hardware Media Server ===
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Restrictions for Upgrading the Software for the Hardware Media Server|Restrictions for Upgrading the Software for the Hardware Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Launching the Upgrade Utility|Launching the Upgrade Utility]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Audio Blades|Upgrading the Software for Audio Blades]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Video Blades|Upgrading the Software for Video Blades]]

==== Restrictions for Upgrading the Software for the Hardware Media Server ====
* Upgrade the Application Server before you upgrade the Hardware Media Server.
* When you upgrade the Hardware Media Server software, the system resets all of the Audio Blade configuration settings (except for the network interface configuration). You must reapply any custom settings that you have previously made to the Audio and Video Blades after the upgrade procedure is complete.

==== Launching the Upgrade Utility ====

===== Procedure =====

# Download the'' ''executable file from the Cisco Unified MeetingPlace 3500 Series Media Server Software CD-ROM:
#* To upgrade the software for Audio Blades, the file is called AudioBladeUpgrade.exe.
#* To upgrade the software for Video Blades, the file is called VideoBladeUpgrade.exe.
# Double click the file to run the upgrade utility.
#: The system extracts the upgrade files and displays the Upgrade Utility dialog box.

===== What To Do Next =====
* To upgrade the software for the Audio Blades, go to [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Audio Blades|Upgrading the Software for Audio Blades]].
* To upgrade the software for the Video Blades, go to [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Software for Video Blades|Upgrading the Software for Video Blades]].

==== Upgrading the Software for Audio Blades ====

===== Before You Begin =====
* Make sure that no meetings are active.

===== Procedure =====

# Sign in as an administrator to the Media Server Administration for the Hardware Media Server.
# Take the Audio Blade offline.
#: '''Note: ''' Failure to take the Audio Blade offline before the upgrade can result in an inconsistent state, with a variety of possible symptoms including dead air when dialing into the system.
# Enter the IP address of the Audio Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.
# Enter the administrator user name and password for the Audio Blade, as configured in the device network configuration settings, in the Login Information section.
# (Optional) Modify the read and write community settings for the Audio Blade as follows:
## Select '''Customize SNMP Settings...'''.
## Enter the required read community and write community values.
##: '''Note: ''' We recommend that you modify the default settings for security purposes.
## Select '''OK''' to return to the Upgrade Utility dialog box.
# (Optional) Select the components of the Audio Blade that you want to upgrade as follows:
## Select '''Customize...''' in the Upgrade Information section.
## Check the components that you want to upgrade.
##: '''Note: ''' The components displayed vary according to the hardware that is upgraded.
## Select '''OK''' to return to the Upgrade Utility dialog box.
# Select '''Upgrade''' to upgrade all components of the software (or only those components you manually selected via the Customize option).
#: The upgrade utility informs you whether the upgrade is successful.
#: '''Note: ''' When the upgrade is complete, the Audio Blade automatically resets itself and starts operation with the new software version.
# Upgrading the Audio Blades resets the user credentials. Sign in to the Media Server Administration for the Hardware Media Server by using the user name of "admin" and the password of "password".
# To improve security, we recommend that you change the user name and password.
# Repeat steps 3 to 7 for any other Audio Blades that need to be upgraded.
# Put the Audio Blade online.
#: '''Note: ''' Putting the Audio Blade online restores the password and SNMP community names that were in effect before the upgrade. It also synchronizes the Application Server with the Audio Blade except for the meeting types.
# Repeat steps [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#2|2]] to [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#11|11]] for each blade that was upgraded.
# Go to '''Resource Management > Meeting Types'''.
# Select '''Synchronize'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Signing in to the Media Server Administration for the Hardware Media Server|Signing in to the Media Server Administration for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Media Server Administration Password for the Hardware Media Server|Changing the Media Server Administration Password for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

===== What To Do Next =====
* If you previously customized your Audio Blades, manually reapply those customizations.

==== Upgrading the Software for Video Blades ====

===== Before You Begin =====
* Make sure that no meetings are active.

===== Procedure =====

# Sign in as an administrator to the Media Server Administration for the Hardware Media Server.
# Enter the IP address of the Video Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.
# Enter the administrator user name and password for the Video Blade, as configured in the device network configuration settings, in the Login Information section.
# (Optional) Select the components of the Video Blade that you want to upgrade as follows:
## Select '''Customize...''' in the Upgrade Information section.
## Check the components that you want to upgrade.
##: '''Note: ''' The components displayed vary according to the hardware that is upgraded.
## Select '''OK''' to return to the Upgrade Utility dialog box.
# Select '''Upgrade''' to upgrade all components of the software (or only those components you manually selected via the Customize option).
#: The software upgrade utility informs you whether the upgrade is successful.
#: '''Note: ''' When the upgrade is complete, the Video Blade automatically resets itself and starts operation with the new software version.
# Repeat steps 2 to 5 for any other Video Blades that need to be upgraded.
# Put the Video Blade online.
# Repeat steps 2 to 7 for each blade that was upgraded.
# Go to '''Resource Management > Meeting Types'''.
# Select '''Synchronize'''.
# Upgrading the Video Blades resets the user credentials. Sign in to the Media Server Administration for the Hardware Media Server by using the user name of "admin" and the password of "password".
# To improve security, we recommend that you change the user name and password.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Signing in to the Media Server Administration for the Hardware Media Server|Signing in to the Media Server Administration for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Audio and Video Blades for the Hardware Media Server#How to Configure Administrators for the Hardware Media Server|How to Configure Administrators for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring the Audio and Video Blades for the Hardware Media Server#Configuring the Audio and Video Blades for the Hardware Media Server|Configuring the Audio and Video Blades for the Hardware Media Server]] module

===== What To Do Next =====
* If you previously customized your Video Blades, manually reapply those customizations.

=== Troubleshooting Errors When Upgrading the Software for the Hardware Media Server ===

Use the following recovery procedure if the Hardware Media Server upgrade procedure fails and any further attempts to upgrade it are blocked by the following three error messages:

'''Error Message: '''Could not retrieve the target information. Your SNMP community settings might be incorrect. Click OK to continue the upgrade, or Cancel to review your SNMP community settings.

If you press OK, you see this error message:

'''Error Message: '''Setup cannot continue without obtaining target information through SNMP. Please reset the target manually or contact customer support for more help.

After that message, the system displays this error message:

'''Error Message: '''Upgrade process failed.

===== Procedure =====

# Sign in as an administrator to the Media Server Administration for the Hardware Media Server.
# Take the Audio Blade offline.
#: '''Note: ''' Failure to take the Audio Blade offline before the upgrade can result in an inconsistent state, with a variety of possible symptoms including dead air when dialing into the system.
# Enter the IP address of the Audio Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.
# Enter the administrator user name and password for the Audio Blade, as configured in the device network configuration settings, in the Login Information section.
# Select '''Customize''' from inside the Upgrade Information section.
#: The system displays the following message:
#::'''Error Message: '''The SNMP community settings do not match the target community. Press Retry to change the Read Community name.
# Select '''Ignore'''.
# In the Customize dialog box, ensure that only the following boxes are checked: MCU WEB Interface, MCU Config File, and MCU Factory Default Config File.
# Select '''OK'''.
# Select Upgrade.
# Select '''OK''' when the system displays the error message.
#: The system begins updating the three processes that you checked in step 7.
# When the upgrade is complete, run the upgrade utility again, without the customized settings.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Signing in to the Media Server Administration for the Hardware Media Server|Signing in to the Media Server Administration for the Hardware Media Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module

=== Recommendations for Moving an Audio Blade to a Different Hardware Media Server ===

When moving an Audio Blade from one Hardware Media Server to another (except when doing so for failover), we recommend the following best practices:
* Use different Audio Blade passwords and SNMP community names for each Hardware Media Server.
* Set the Audio Blade to permanently offline on the Hardware Media Server from which you are moving the Audio Blade. See [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing the Online and Offline Status of an Audio Blade|Changing the Online and Offline Status of an Audio Blade]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Changing Values for the Hardware Media Server#Changing Values for the Hardware Media Server|Changing Values for the Hardware Media Server]] module.

== How to Change from a Hardware Media Server to an Express Media Server ==
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#About the Express Media Server|About the Express Media Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Changing the Type of Media Server that Your System Uses|Changing the Type of Media Server that Your System Uses]]

=== About the Express Media Server ===

Cisco Unified MeetingPlace Release 8.0 introduces an Express Media Server, a software version of the Hardware Media Server that was used in previous releases of Cisco Unified MeetingPlace. All systems that will use audio or video need a media server and the media server can be either a Hardware Media Server or an Express Media Server.
* The Express Media Server is a set of software modules, including an audio mixer and a video switcher, that resides on the Application Server. The Express Media Server creates a single box, software-only solution for Cisco Unified MeetingPlace.
* The Hardware Media Server is comprised of Audio and Video Blades.

All Cisco Unified MeetingPlace Release 8.0 systems automatically come with an Express Media Server.

=== Changing the Type of Media Server that Your System Uses ===

Follow these steps to change the type of media server that your system uses from a Hardware Media Server to an Express Media Server.

===== Procedure =====

# Sign in to the Administration Center.
# Select '''System Configuration > Media Resource Configuration'''.
# Select '''Software''' for the System media mode field.
# Select '''Save'''.
#: The system reboots. When the system comes back up, it will be using an Express Media Server instead of a Hardware Media Server.

===== What To Do Next =====
* Configure the system for the Express Media Server. See the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module.

== Upgrading Microsoft Outlook for Cisco Unified MeetingPlace ==

'''Note: ''' The Microsoft Outlook for Cisco Unified MeetingPlace integration is the same for Cisco Unified MeetingPlace Release 7.0 Maintenance Release 1 and Cisco Unified MeetingPlace Release 8.0. Therefore, if you have already upgraded your Microsoft Outlook for Cisco Unified MeetingPlace integration to Release 7.0 Maintenance Release 1 or later, then you do not need to follow this procedure. Your integration is already upgraded.

To upgrade from Cisco Unified MeetingPlace Release 7.0 to Cisco Unified MeetingPlace Release 8.0, follow these steps:

{| border = 1
|-
!Step
!Step Description
!For more information, see
|-
|

1
|

Upgrade your Cisco Unified MeetingPlace Release 7.0 system to Cisco Unified MeetingPlace Release 8.0
|
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Application Server Software|How to Upgrade the Application Server Software]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Web Server Software|How to Upgrade the Web Server Software]]* [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#How to Upgrade the Software for the Hardware Media Server|How to Upgrade the Software for the Hardware Media Server]]
|-
|

2
|

Uninstall the Microsoft Outlook for Cisco Unified MeetingPlace integration Release 7.0 from the Web Server.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Uninstalling Cisco Unified MeetingPlace for Microsoft Outlook Gateway From the Web Server|Uninstalling Cisco Unified MeetingPlace for Microsoft Outlook Gateway From the Web Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module
|-
|

3
|

Configure the Microsoft Exchange Server.
|

[[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Configuring the Cisco Unified MeetingPlace Connection to the Microsoft Exchange Server|Configuring the Cisco Unified MeetingPlace Connection to the Microsoft Exchange Server]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal#Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal|Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace Web User Portal]] module
|-
|

4
|

From the Application Server, run the following Cisco Unified MeetingPlace-Microsoft Exchange migration script: /opt/cisco/meetingplace/migrationtools/current/notifications/migrateExchangeForICAL.sh.
|
|}

'''Note: ''' The upgrade process may take a long time if many meetings need to be migrated. To speed up the upgrade, purge old meetings from the Cisco Unified MeetingPlace-dedicated mailbox and empty the Deleted Items folder. We recommend that the mailbox have fewer than 1360 appointment items or 32 KB of appointment data before you run the upgrade script.

===== What To Do Next =====

After you complete the upgrade process, have your users upgrade the Cisco Unified MeetingPlace plug-in for Microsoft Outlook on their PCs. They can do this themselves by doing one of the following:
* Select '''Download Outlook Plug-In''' from the Cisco Unified MeetingPlace web user portal.
* Select '''Upgrade to newer version''' from the MeetingPlace tab in a Microsoft Outlook calendar appointment.

== Testing that the Upgraded System Works Correctly ==

Verify the following after you upgrade and configure the entire Cisco Unified MeetingPlace system:

===== Licenses =====
* Your system has all the necessary licenses installed. See the ''Planning Guide for Cisco Unified MeetingPlace Release 8.0'' at: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment for information about Cisco Unified MeetingPlace Release 8.0 licenses.

===== Database Import =====
* Ensure that the following information imported correctly: user groups, user profiles, video terminal profiles, video types, video usage assignments, meeting categories, and password expirations.
* Ensure that all recorded names for user profiles were imported correctly.
* Ensure that all scheduled meetings, both past and recurring, imported correctly.
* Ensure that the default video mode assigned to user profiles matches the global video mode that was previously assigned to the user profile.

===== Scheduling =====
* Ensure that you can schedule a meeting.
* Ensure that the system sends an email notification for the meeting that you scheduled.
* Ensure that you can join and attend the meeting via audio, video, and web.
* Test that the dial in and dial out features work.

===== System Access =====
* Ensure that you have access to all of the Administration Center pages, including Conference Manager. To access the Administration Center, go to a web browser and enter http://''your-app-server''

===== Recordings =====
* Ensure that you can record a meeting.
* Ensure that you can play back the meeting recording.

== Completing the Upgrade ==

* Inform end users that the system has been successfully upgraded.
* During the upgrade process, only users who were ''moderators'' for a Cisco Unified MeetingPlace Release 7.0 meeting are converted to alternate hosts in Cisco Unified MeetingPlace Release 8.0. Meeting attendees or presenters for Cisco Unified MeetingPlace Release 7.0 meetings are only converted to meeting attendees in Cisco Unified MeetingPlace Release 8.0.
: In Cisco Unified MeetingPlace Release 8.0, only a host or an alternate host can start a meeting. After an upgrade, users may find that meetings only have one host and no alternate host and may experience not being able to start a meeting.
: We recommend that after you upgrade your system, you inform end user about this restriction and suggest that meeting owners designate alternate hosts for their meetings. This must be done before the meeting begins and only the meeting owner or delegate can modify a meeting.
* If you have upgraded your system to a Release 8.0 system with Cisco WebEx scheduling and without directory services integration, then the user passwords are not recognized after you import your user profiles into Cisco WebEx. (Cisco Unified MeetingPlace passwords are encrypted whereas Cisco WebEx uses plain text passwords.)
: When they next log in to Cisco WebEx, ask your users to select '''Forgot your password''' and have them reset their password.

[[Category: Installation Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace, Release 7.0 -- System Capacity Quick Reference Tables

2012-01-24T23:16:03Z

Dunn: /* Capacity */ -- edit as Footnote numbering was incorrect..

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Navigation:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Planning Your Deployment|Planning Your Deployment]] > [[Cisco Unified MeetingPlace, Release 7.0 -- Planning the Capacity of your Cisco Unified MeetingPlace System|Planning the Capacity of your Cisco Unified MeetingPlace System]]

This section provides a series of quick reference tables that describe the different capacity limits for several key configurations of Cisco Unified MeetingPlace Release 7.0.

For more detailed information, see [[Cisco Unified MeetingPlace, Release 7.0 -- System Capacity#System Capacity|System Capacity]].

==Release 7.0.3 (MR2) with Cisco Unified MeetingPlace Web Conferencing==

====Configuration Details====

This configuration assumes the following:

* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
* Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
* Six Audio blades
*Six Video blades
*Single node configuration using the Hardware Media Server and Cisco Unified MeetingPlace web conferencing
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
*Does not support Cisco WebEx-scheduled meetings

====Capacity ====

{| border = 1
|-
!Maximum Number
!Details
|-
|

1500
|

Audio ports using G.711 or G.729 (without LEC)1
|-
|

996
|

Audio ports using G.729 (with LEC), G.722, or iLBC1
|-
|

240

|

Video ports using standard rate video
|-
|

1000

|

Web sessions per Application Server when not using SSL or recording
|-
|

1000

|

Web sessions per Application Server when using SSL or recording
|-
|

500

|

Number of concurrent audio and web meetings per Application Server
|-
|
3000

|

Total meetings per day
|-
|
1000

|

Continuous meetings
|-
|

50

|

Simultaneous meetings that can be recorded
|-
|

500

|

Largest possible audio meeting 2

|-
|

500

|

Largest possible web meeting when not using SSL or recording3
|-
|

500

|

Largest possible web meeting when using SSL or recording3
|-
|

5

|

Simultaneous Conference Manager sessions

|-
|

200

|

Largest possible number of instances of the recurrence meeting 2

|-
|

500

|

Largest possible number of invitees on single meeting 4

|-
|

1

|

Database replication connection per Windows cluster (internal and external).

Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.
|}

'''Footnote 1:''' When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.

'''Footnote 2:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

'''Footnote 3:''' The Cisco MCS 7845-I3 Web Server supports a maximum of 600 web ports per server. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 500 ports due to the rate at which a single Audio blade can accept traffic.

'''Footnote 4:''' Largest possible number of invitees on MPWeb is 450.

====Sizes====

{| border = 1
|-
!Maximum Size
!Component
|-
|

250,000
|

User profiles in the database
|-
|

400,000
|

Meetings in the database

|}

====Call Rate====

{| border = 1
|-
!Maximum
!Details
|-
|

180 seconds
|

Time to get all ports into meetings (includes the time to disconnect from previous meetings)
|-
|

20 seconds
|

Time to get the meetings started
|-
|

15 CPS

|

Maximum call rate for inbound calls
|}

====Redundancy====

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Unified MeetingPlace web servers can be clustered for 3 internal and/or 3 external web meetings.

====Recommended Practices====

* Scheduling and rescheduling of recurring meetings with more than 60 instances and 20 invitees should be performed during off-peak times to minimize delays perceived by users joining meetings. 5 Conference Manager limit is including 1 rescheduling session and 4 schedule/monitoring sessions of such meeting chain.

* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.

==Release 7.0.3 (MR2) with Cisco WebEx Web Conferencing==

====Configuration Details====

This configuration assumes the following:

* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
* Two Windows web servers
* Six Audio blades
* Six Video blades
*Single node configuration using the Hardware Media Server and Cisco WebEx web conferencing
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
*Does not support Cisco WebEx-scheduled meetings

====Capacity ====

{| border = 1
|-
!Maximum Number
!Details
|-
|

1500
|

Audio ports using G.711 or G.729 (without LEC)1
|-
|

996
|

Audio ports using G.729 (with LEC), G.722, or iLBC1
|-
|

240

|

Video ports using standard rate video
|-
|

1000

|

Web sessions per Application Server
|-
|

500

|

Number of concurrent audio and web meetings per Application Server
|-
|

50

|

Simultaneous meetings that can be recorded
|-
|

500

|

Largest possible audio meeting 2

|-
|

500

|

Largest possible web meeting using Meeting Center meetings
|-
|

200

|

Largest possible number of instances of the recurrence meeting 2

|-
|

500

|

Largest possible number of invitees on single meeting 4

|-
|

5

|

Simultaneous Conference Manager sessions

|}

'''Footnote 1:''' When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.

'''Footnote 2:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

'''Footnote 3:''' Largest possible number of invitees on MPWeb is 450.

====Sizes====

{| border = 1
|-
!Maximum Size
!Component
|-
|

250,000
|

User profiles in the database
|-
|

400,000
|

Meetings in the database

|}

====Call Rate====

{| border = 1
|-
!Maximum
!Details
|-
|

180 seconds
|

Time to get all ports into meetings (includes the time to disconnect from previous meetings)
|-
|

20 seconds
|

Time to get the meetings started
|-
|

15 CPS

|

Maximum call rate for inbound calls
|}

====Redundancy====

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.

====Recommended Practices====

* Scheduling and rescheduling of recurring meetings with more than 60 instances and 20 invitees should be performed during off-peak times to minimize delays perceived by users joining meetings. 5 Conference Manager limit is including 1 rescheduling session and 4 schedule/monitoring sessions of such meeting chain.

* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.

==Release 7.0.2 (MR1) with Cisco Unified MeetingPlace Web Conferencing==

====Configuration Details====

This configuration assumes the following:

* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
* Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
* Six Audio blades
* Six Video blades
*Single node configuration using the Hardware Media Server and Cisco Unified MeetingPlace web conferencing
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
*Does not support Cisco WebEx-scheduled meetings

====Capacity ====

{| border = 1
|-
!Maximum Number
!Details
|-
|

1500
|

Audio ports using G.711 or G.729 (without LEC)
|-
|

996
|

Audio ports using G.729 (with LEC), G.722, or iLBC
|-
|

240

|

Video ports using standard rate video
|-
|

1000

|

Web sessions per Application Server when not using SSL or recording
|-
|

700

|

Web sessions per Application Server when using SSL or recording
|-
|

500

|

Number of concurrent audio and web meetings per Application Server
|-
|

50

|

Simultaneous meetings that can be recorded
|-
|

500

|

Largest possible audio meeting 1

|-
|

500

|

Largest possible web meeting when not using SSL or recording
|-
|
500

|

Largest possible web meeting when using SSL or recording
|-
|
5

|

Simultaneous Conference Manager sessions

|-
|

1

|

Database replication connection per Windows cluster (internal and external).

Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.
|}

'''Footnote 1:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

====Sizes====

{| border = 1
|-
!Maximum Size
!Component
|-
|

250,000
|

User profiles in the database
|-
|

400,000
|

Meetings in the database

|}

====Call Rate====

{| border = 1
|-
!Maximum
!Details
|-
|

180 seconds
|

Time to get all ports into meetings (includes the time to disconnect from previous meetings)
|-
|

20 seconds
|

Time to get the meetings started
|-
|

15 CPS

|

Maximum call rate for inbound calls
|}

====Redundancy====

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Unified MeetingPlace web servers can be clustered for 3 internal and/or 3 external web meetings.

====Recommended Practices====

* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.

* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.

==Release 7.0.2 (MR1) with Cisco WebEx Web Conferencing==

====Configuration Details====

This configuration assumes the following:

* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
* One or two Windows web servers
* Six Audio blades
* Six Video blades
*Single node configuration using the Hardware Media Server and Cisco WebEx web conferencing
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
*Does not support Cisco WebEx-scheduled meetings

====Capacity ====

{| border = 1
|-
!Maximum Number
!Details
|-
|

1500
|

Audio ports using G.711 or G.729 (without LEC)
|-
|

996
|

Audio ports using G.729 (with LEC), G.722, or iLBC
|-
|

240

|

Video ports using standard rate video
|-
|

1000

|

Web sessions per Application Server
|-
|

500

|

Number of concurrent audio and web meetings per Application Server
|-
|

50

|

Simultaneous meetings that can be recorded
|-
|

500

|

Largest possible audio meeting 1

|-
|

500

|

Largest possible web meeting using Meeting Center meetings1

|}

'''Footnote 1:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

====Sizes====

{| border = 1
|-
!Maximum Size
!Component
|-
|

250,000
|

User profiles in the database
|-
|

400,000
|

Meetings in the database

|}

====Call Rate====

{| border = 1
|-
!Maximum
!Details
|-
|

180 seconds
|

Time to get all ports into meetings (includes the time to disconnect from previous meetings)
|-
|

20 seconds
|

Time to get the meetings started
|-
|

15 CPS

|

Maximum call rate for inbound calls
|}

====Redundancy====

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.

====Recommended Practices====

* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.

* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.

==Release 7.0.2 (MR1) Using RSNA==

====Configuration Details====

This configuration assumes the following:

* Two Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
* 12 Audio blades
* 12 Video blades
*Two nodes using the Hardware Media Server
*Supports audio/video-only reservationless meetings
*Supports Outlook Scheduling interface
*There is no web conferencing with RSNA deployments

====Capacity ====

{| border = 1
|-
!Maximum Number
!Details
|-
|

2x1500
|

Audio ports using G.711 or G.729 (without LEC)
|-
|

2x996
|

Audio ports using G.729 (with LEC), G.722, or iLBC
|-
|

2x240

|

Video ports using standard rate video
|-
|

1000

|

Simultaneous audio meetings
|-
|

500

|

Largest possible audio meeting1

|}

'''Footnote 1:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

====Sizes====

{| border = 1
|-
!Maximum Size
!Component
|-
|

250,000
|

User profiles in the database
|-
|

400,000
|

Meetings in the database

|}

====Call Rate====

{| border = 1
|-
!Maximum
!Details
|-
|

180 seconds
|

Time to get all ports into meetings (includes the time to disconnect from previous meetings)
|-
|

20 seconds
|

Time to get the meetings started
|-
|

30 CPS

|

Maximum call rate for inbound calls
|}

====Recommended Practices====

* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.

* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.

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

Cisco Unified MeetingPlace Release 6.1 -- Compatibility Matrix

2011-05-04T15:57:49Z

Dunn: /* Table: Supported Version Combinations for Audio Server Release 6.1 and Other Cisco Unified MeetingPlace Components */

[[Cisco Unified MeetingPlace Release 6.1]] > [[Cisco Unified MeetingPlace Release 6.1#System/Solution|System/Solution]]

'''Custom Search:'''
<html>
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="007771824002417948961:q0te3ntvco0" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<input type="submit" name="sa" value="Search" />
</div>
</form>

<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</html>
 

 

This page lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in Release 6.1.

 

== Upgrade Information ==

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 on this page.

 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 the Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP IP 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.1 -- Determining the Software Version|Determining the Software Version]].

 

== Compatibility Matrix ==

===== Table: Supported Version Combinations for Audio Server Release 6.1 and Other Cisco Unified MeetingPlace Components =====

{| border="1" cellspacing="2" cellpadding="4"
|-
! style="background: #ffdead" | Audio Server Version
! style="background: #ffdead" | Component and Supported Version
! style="background: #ffdead" | Component Release Date
|-
| valign="top" rowspan="60" | '''6.1.0.6'''

 Released March 29, 2011

|
Directory Services 6.1.1.0

|
March 29, 2011

|-
|
Gateway SIM 6.1.2.0

|
March 29, 2011

|-
|
H.323/SIP IP Gateway 6.0.5.10

|
March 29, 2011

|-
|
Jabber Integration 6.0.600.0

|
July 15, 2009

|-
|
Language Pack 6.0(MR5)

|
January 31, 2008

|-
|
Lotus Notes Integration 6.1.7.0

|
March 29, 2011

|-
|
MCU 5.7.0.0.21

|
July 15, 2009

|-
|
EMP 5.7.0.0.4

|
July 15, 2009

|-
|
MeetingTime 6.1.0.3

|
March 29, 2011

|-
|
Network Backup Gateway 6.1.2.0

|
March 29, 2011

|-
|
Microsoft Office Communicator (MOC/LCS 2005) Integration 6.1.1.0

|
March 29, 2011

|-
|
Outlook Integration 6.1.16.0

|
March 29, 2011

|-
|
Password Utility Patch 1.0

''Note: Optional. This feature is intended for Government use and is only available by contacting Cisco TAC.''

|
June 2, 2008

|-
|
SMTP E-Mail Gateway 6.1.1.0

|
March 30, 2011

|-
|
Video Administration 5.6.2.104

|
July 15, 2009

|-
|
Video Integration 6.0.5.6

|
March 29, 2009

|-
|
Web Conferencing 6.1.8.1

|
March 29, 2011

|-
|
Cisco IP Telephony OS

*Windows 2003.1.4 through 2003.1.5a supported
*Windows 2003.1.4a-SR15 & Windows 2003.1.5a-SR14 are the latest service releases.
*OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
*Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
*Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm

|
October 20, 2009

|-
| colspan="2" | Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace Release 6.1 -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements_and_Supported_Software|Requirements and Supported Software]] for Cisco Security Agent.

|-
| colspan="3" |
|-

[[Category:Unified MeetingPlace Release 6.1]]

Cisco Unified MeetingPlace Release 6.1 -- Compatibility Matrix

2011-05-04T15:50:27Z

Dunn: /* Table: Supported Version Combinations for Audio Server Release 6.1 and Other Cisco Unified MeetingPlace Components */

[[Cisco Unified MeetingPlace Release 6.1]] > [[Cisco Unified MeetingPlace Release 6.1#System/Solution|System/Solution]]

'''Custom Search:'''
<html>
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="007771824002417948961:q0te3ntvco0" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<input type="submit" name="sa" value="Search" />
</div>
</form>

<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</html>
 

 

This page lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in Release 6.1.

 

== Upgrade Information ==

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 on this page.

 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 the Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP IP 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.1 -- Determining the Software Version|Determining the Software Version]].

 

== Compatibility Matrix ==

===== Table: Supported Version Combinations for Audio Server Release 6.1 and Other Cisco Unified MeetingPlace Components =====

{| border="1" cellspacing="2" cellpadding="4"
|-
! style="background: #ffdead" | Audio Server Version
! style="background: #ffdead" | Component and Supported Version
! style="background: #ffdead" | Component Release Date
|-
| valign="top" rowspan="19" | '''6.1.0.6'''

 Released March 29, 2011

|
Directory Services 6.1.1.0

|
March 29, 2011

|-
|
Gateway SIM 6.1.2.0

|
March 29, 2011

|-
|
H.323/SIP IP Gateway 6.0.5.10

|
March 29, 2011

|-
|
Jabber Integration 6.0.600.0

|
July 15, 2009

|-
|
Language Pack 6.0(MR5)

|
January 31, 2008

|-
|
Lotus Notes Integration 6.1.7.0

|
March 29, 2011

|-
|
MCU 5.7.0.0.21

|
July 15, 2009

|-
|
EMP 5.7.0.0.4

|
July 15, 2009

|-
|
MeetingTime 6.1.0.3

|
March 29, 2011

|-
|
Network Backup Gateway 6.1.2.0

|
March 29, 2011

|-
|
Microsoft Office Communicator (MOC/LCS 2005) Integration 6.1.1.0

|
March 29, 2011

|-
|
Outlook Integration 6.1.16.0

|
March 29, 2011

|-
|
Password Utility Patch 1.0

''Note: Optional. This feature is intended for Government use and is only available by contacting Cisco TAC.''

|
June 2, 2008

|-
|
SMTP E-Mail Gateway 6.1.1.0

|
March 30, 2011

|-
|
Video Administration 5.6.2.104

|
July 15, 2009

|-
|
Video Integration 6.0.5.6

|
March 29, 2009

|-
|
Web Conferencing 6.1.8.1

|
March 29, 2011

|-
|
Cisco IP Telephony OS

*Windows 2003.1.4 through 2003.1.5 supported
*Windows 2003.1.4asr15 & Windows 2003.1.5sr5 are the latest service releases.
*OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
*Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
*Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm

|
October 20, 2009

|-
| colspan="2" | Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace Release 6.1 -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements_and_Supported_Software|Requirements and Supported Software]] for Cisco Security Agent.

|-
| colspan="3" |
|-

[[Category:Unified MeetingPlace Release 6.1]]

Cisco Unified MeetingPlace Release 6.1 -- Compatibility Matrix

2011-05-04T15:49:25Z

Dunn: /* Table: Supported Version Combinations for Audio Server Release 6.1 and Other Cisco Unified MeetingPlace Components */

[[Cisco Unified MeetingPlace Release 6.1]] > [[Cisco Unified MeetingPlace Release 6.1#System/Solution|System/Solution]]

'''Custom Search:'''
<html>
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="007771824002417948961:q0te3ntvco0" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<input type="submit" name="sa" value="Search" />
</div>
</form>

<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</html>
 

 

This page lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in Release 6.1.

 

== Upgrade Information ==

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 on this page.

 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 the Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP IP 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.1 -- Determining the Software Version|Determining the Software Version]].

 

== Compatibility Matrix ==

===== Table: Supported Version Combinations for Audio Server Release 6.1 and Other Cisco Unified MeetingPlace Components =====

{| border="1" cellspacing="2" cellpadding="4"
|-
! style="background: #ffdead" | Audio Server Version
! style="background: #ffdead" | Component and Supported Version
! style="background: #ffdead" | Component Release Date
|-
| valign="top" rowspan="19" | '''6.1.0.6'''

 Released March 29, 2011

|
Directory Services 6.1.1.0

|
March 29, 2011

|-
|
Gateway SIM 6.1.2.0

|
March 29, 2011

|-
|
H.323/SIP IP Gateway 6.0.5.10

|
March 29, 2011

|-
|
Jabber Integration 6.0.600.0

|
July 15, 2009

|-
|
Language Pack 6.0(MR5)

|
January 31, 2008

|-
|
Lotus Notes Integration 6.1.7.0

|
March 29, 2011

|-
|
MCU 5.7.0.0.21

|
July 15, 2009

|-
|
EMP 5.7.0.0.4

|
July 15, 2009

|-
|
MeetingTime 6.1.0.3

|
March 29, 2011

|-
|
Network Backup Gateway 6.1.2.0

|
March 29, 2011

|-
|
Microsoft Office Communicator (MOC/LCS 2005) Integration 6.1.1.0

|
March 29, 2011

|-
|
Outlook Integration:

6.1.16.0

|
March 29, 2011

|-
|
Password Utility Patch 1.0

''Note: Optional. This feature is intended for Government use and is only available by contacting Cisco TAC.''

|
June 2, 2008

|-
|
SMTP E-Mail Gateway 6.1.1.0

|
March 30, 2011

|-
|
Video Administration 5.6.2.104

|
July 15, 2009

|-
|
Video Integration 6.0.5.6

|
March 29, 2009

|-
|
Web Conferencing:

6.1.8.1

|
March 29, 2011

|-
|
Cisco IP Telephony OS

*Windows 2003.1.4 through 2003.1.5 supported
*Windows 2003.1.4asr15 & Windows 2003.1.5sr5 are the latest service releases.
*OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
*Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
*Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm

|
October 20, 2009

|-
| colspan="2" | Cisco Security Agent for Cisco Unified MeetingPlace is supported with certain versions of most components.
See [[Cisco Unified MeetingPlace Release 6.1 -- Cisco Security Agent for Cisco Unified MeetingPlace#Requirements_and_Supported_Software|Requirements and Supported Software]] for Cisco Security Agent.

|-
| colspan="3" |
|-

[[Category:Unified MeetingPlace Release 6.1]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Application Server Failover

2011-02-04T23:29:19Z

Dunn: /* Before You Begin */ added extra sentence to ensure pre-flight state of servers

{{Template:Required Metadata}}
'''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]].

In summary both servers should be ready for failover, but left in Standby status. If the primary server is in failover Active then use 'failoverUtil setServer standby' command to bring it to standby status.

===== 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.
# Install any licenses on the first Application Server (Node 1). See [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses|About Licenses]] for information about licenses.
# 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.
# Install any licenses on the second Application Server (Node 2) in active mode and reboot the system. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Licenses|About Licenses]] for information about licenses.
# 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'''

'''Note:''' Node must be active to add licenses (step 7)

===== 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.

To verify that the replication was successful, log in to both nodes (eth0:0 interface) as root user and enter the '''mp_replication status''' command. The following should display in your output:

{| border = 1
|-
!Local Server
!Remote Server
|-
|

*Replication Type: Local
*Site: 1
*Node: 1
*State: Active
*Status: Local
|

*Replication Type: Intra-site
*Site: 1
*Node: 2
*State: Active
*Status: Connected

|-
|
|}

===== 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.

* If you switch on replication with sync via the mp_replication switchON command and replication fails, it is possible that a table is locking due to the processes on an active server. To resolve this issue, run the mp_replication switchON with sync command again.

* During this process, you may see several error messages. These error messages are expected behavior 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.

To verify that the replication was successful, log in to both nodes (eth0:0 interface) as root user and enter the '''mp_replication status''' command. The following should display in your output:

{| border = 1
|-
!Local Server
!Remote Server
|-
|

*Replication Type: Local
*Site: 1
*Node: 1
*State: Active
*Status: Local
|

*Replication Type: Intra-site
*Site: 1
*Node: 2
*State: Active
*Status: Connected

|-
|
|}

===== 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.

* If you switch on replication with sync via the mp_replication switchON command and replication fails, it is possible that a table is locking due to the processes on an active server. To resolve this issue, run the mp_replication switchON with sync command again.

* During this process, you may see several error messages. These error messages are expected behavior 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 -- About Load Balancing Options for the Web Server

2010-11-02T11:53:35Z

Dunn: /* Web Conferencing Clusters */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Planning Your Deployment|Planning Your Deployment]]

Load balancing in Cisco Unified MeetingPlace Web Conferencing makes use of a cluster of Web Servers to spread the active meeting load, allowing you to scale the number and size of meetings that your deployment can support. It also provides failover capabilities for meetings-if one Cisco Unified MeetingPlace Web Server is unavailable or unreachable, meeting participants reconnect to another Web Server, even if they are currently connected to a meeting that is in progress when the connection is interrupted.

You can view the amount of web-conferencing load per Web Server from the Web Server administrative page. This information is displayed only on internal Web Servers.

We recommend that you load balance the Web Conferencing portion of your Cisco Unified MeetingPlace system by using clusters. In a Cisco Unified MeetingPlace load-balancing Web Server cluster, all users must enter the Cisco Unified MeetingPlace system through a designated Cisco Unified MeetingPlace Web Server. In load-balancing Web Server cluster deployments, only the designated Cisco Unified MeetingPlace Web Server needs to be configured for the chosen authentication method. All other Web Servers in the cluster use the default authentication method-MeetingPlace Web Form Authentication. If, however, you want to configure other Web Servers in the cluster to use the same authentication method as a failover strategy, you can. Depending on the type of authentication method used though, this configuration can result in undesirable SSO behaviors.

For example, if you configure HTTP Basic Authentication or Windows Integrated Authentication, Cisco Unified MeetingPlace will prompt users for login credentials each time there is a Web Server redirect. This is because you are altering the hostname in the authentication configuration each time you redirect traffic to an active Web Server through a DNS change. If you configure LDAP or MeetingPlace authentication, users will not be prompted again for login credentials during a web conferencing redirect.

Use the information in this section to determine the load balancing configuration you want for the Web Conferencing portion of your Cisco Unified MeetingPlace system.

== Understanding How the Cisco Unified MeetingPlace Application Servers and Web Servers Communicate ==

The Cisco Unified MeetingPlace Replication Service automatically synchronizes the local Web Server database with that of the Cisco Unified MeetingPlace Application Server to update meetings, user profiles, and user group information. The following occurs by default:

* Synchronization occurs every 60 seconds.

* The User Profile Update Interval updates every 20 days.

* The Group Update Interval updates every 20 days.

* Meeting information updates every 60 seconds.

The Replication Service copies attachments and recordings from the Cisco Unified MeetingPlace Application Server and stores the replicated files on the Cisco Unified MeetingPlace Web Server. Pointers to these files are then created in the database. The Replication Service downloads voice files in their native Cisco Unified MeetingPlace voice (.mp4) format. After voice files are downloaded, the Replication Service queues jobs for conversion by the Audio Service.

The Replication Service also replicates video terminal user profile information from the Application Server. By default, this replication occurs every 7 days.

In the event of a system failure, you can manually invoke the Replication Service update and purge operations. Allow up to 20 minutes for any changes made to the Replication Service to take effect. For information on how to invoke the Replication Service, see [[Cisco Unified MeetingPlace, Release 7.0 -- How to Update Meetings and User Profiles|How to Update Meetings and User Profiles]].

== Web Conferencing Clusters ==

'''Restriction:''' When your system is configured for load-balancing, ensure that all web servers in the load-balanced system have the same permissions.

With Cisco Unified MeetingPlace, you can configure to have an internal and an external Web Server cluster simultaneously. The cluster can have up to three (3) Web Servers.

'''Internal cluster'''-Places all Web Servers behind the firewall inside the private corporate network. Typically, all Web Servers in an internal cluster display the full-access Cisco Unified MeetingPlace interface.

'''External cluster'''-Places all Web Servers between the private corporate network and the Internet, such as in a DMZ. For increased security, all Web Servers in an external cluster typically display the attend-only Cisco Unified MeetingPlace interface.

Cisco Unified MeetingPlace Web Servers use a SQL database to store profile and meeting information. When deploying Cisco Unified MeetingPlace Web Server clusters, the internal and external clusters must use separate SQL databases; however, the two databases must have identical Globally Unique Identifiers (GUIDS). It is recommended for high availability, the SQL database instance for a cluster is installed and configured on a separate server. For more information about configuring Cisco Unified MeetingPlace Web Servers for failover, see [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover|Application Server Failover]].

Load balancing does not affect shared storage locations. All servers in a cluster use the same shared storage location.

Web conferencing supports three potential load balancing configurations, as shown in [[Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server#Figure: One Cluster Configuration|Figure: One Cluster Configuration]], [[Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: Internal and External Clusters of Web Servers|Figure: Mixed Configuration: Internal and External Clusters of Web Servers]], and [[Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server#Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers|Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers]].

===== Figure: One Cluster Configuration=====

[[Image:121507.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cisco Unified MeetingPlace Web Server cluster-This can be an internal cluster or external cluster.
|-
|
3
|

SQL Server-All web servers in a cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: Internal and External Clusters of Web Servers=====

[[Image:121508.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Internal cluster of Web Servers.
|-
|
3
|

SQL Server-All Web Servers in the internal cluster must connect to the same SQL Server.
|
4
|

External cluster of Web Servers.
|-
|
5
|

SQL Server-All Web Servers in the external cluster must connect to the same SQL Server.
|
|

-
|}

===== Figure: Mixed Configuration: One Web Server and a Cluster of Web Servers=====

[[Image:121506.jpg]]

{| border = 1
|-
|
1
|

Cisco Unified MeetingPlace system.
|
2
|

Cluster of Web Servers-This can be an internal cluster or an external cluster.
|-
|
3
|

SQL Server-All Web Servers in a cluster must connect to the same SQL Server.
|
4
|

Single Web Server-This can be an internal or external web server.
|-
|
5
|

SQL Server-The single Web Server must connect to a separate SQL Server.
|
|

-
|}

== Web Conferencing Load Balancing and Failover Capability ==

Each Web Server comprises two separate load balancing components: the original server and the second server. Meetings are hosted on the original server. Participants connect to the second server when joining a meeting. These components interact to provide load balancing and failover capability as follows:

* When a meeting starts, the designated Web Server (the Web Server that is listed in the meeting notification) assigns a primary and backup original server to the meeting room based on the current active meeting load.

* As participants join the meeting, they are load balanced across the second servers in the cluster based on the number of participants currently connected to each second server at that time. The second server internally makes a connection to the original server that is hosting the meeting.

* Each client is given the primary and backup original server information by the server when the meeting room is launched. No configuration is needed on the clients.

[[Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server#Figure: Web Conferencing Load Balancing for Meetings and Participants|Figure: Web Conferencing Load Balancing for Meetings and Participants]] shows an example load balancing topology with a cluster of Web Servers. Meetings are spread across the three original servers in the cluster based on the meeting load on each. Participants are spread across the three second servers based on the participant load on each. Note that participants are not necessarily connected to the second server that corresponds to the original Web Server hosting the meeting they are attending.

===== Figure: Web Conferencing Load Balancing for Meetings and Participants=====
[[Image:191875.jpg]]

== Load Balancing Behavior with Internal and External Clusters ==

All users attend a Cisco Unified MeetingPlace web meeting by opening their browsers and signing in through the Cisco Unified MeetingPlace Web Conferencing home page. When the first meeting participant attempts to join the web meeting, the system determines if the meeting should be held on an internal Web Server or an external Web Server by checking the "Allow External Web Participants" parameter. This parameter is visible only if the Cisco Unified MeetingPlace system has an external site or cluster configured.

[[Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server#Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing|Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing]] describes load-balancing behavior for load-balancing configuration options.

===== Table: Load Balancing Behavior in Cisco Unified MeetingPlace Web Conferencing=====

{| border = 1
|-
!If...
!Then...
|-
|

"Allow External Web Participants" is set to No
|

This meeting is reserved for internal attendees only. When the first attendee launches the meeting console, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the internal cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any internal Web Server when they join the web meeting.
|-
|

"Allow External Web Participants" is set to Yes
|

This meeting is accessible to external attendees; that is, participants attending from outside the firewall.

If the first attendee attempts to join the web meeting from an external Web Server, the designated Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This new Web Server now hosts the meeting. Subsequent attendees may be directed to any external Web Server when they join the web meeting.

If the first attendee attempts to join the web meeting from an internal Web Server, Cisco Unified MeetingPlace determines if it has an associated external Web Server. Such information is found on the Web Server Properties administrative page in the DMZ Web Server field.
* If there is an entry in the DMZ Web Server field, Cisco Unified MeetingPlace redirects the meeting to that external server. Web Server, the designated Cisco Unified MeetingPlace external Web Server directs the web-meeting session to the Web Server with the fewest currently active meetings in the external cluster. This Web Server (original server) now owns (hosts) the meeting. Subsequent attendees may be directed to any external Web Server (second server) when they join the web meeting
* If Cisco Unified MeetingPlace does not find an entry in the DMZ Web Server field, the system redirects the meeting to the least loaded internal Web Server. The system directs all subsequent meeting participants to an internal Web Server for their web meeting.
|}

Internal users can join both internal meetings and external meetings. If a meeting is designated as external, internal users who log in to an internal web server are redirected to an external Web Server.

External users can join only external meetings on external Web Servers.

== Recommendations for a Robust Cisco Unified MeetingPlace Web Conferencing System ==

To ensure a robust system with redundancy and failover, we recommend that your Web Conferencing deployment contain the following:

* An internal web cluster

* An external web cluster

* A dedicated remote SQL Server system for each cluster

* Remote storage location with an appropriately sized RAID array and a comprehensive backup policy

== End-User Experience During Meeting Console Failover ==

When failover occurs on a system that is configured for redundancy and failover, users experience the following behavior:
# The Web Server to which the user is connected stops responding (for example, the Web Server loses power or the Web Conferencing services are shut down).
# Users who are connected to the second server on that Web Server lose their connection to the meeting.
# Each meeting console client automatically tries to reconnect the user to the second server. If this attempt fails, the meeting console attempts to connect to the second server designated as the backup for that meeting. (The Web Server sends the assigned primary and backup second server information to each client when the client first connects to a meeting.)

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

Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server

2010-11-02T11:53:04Z

Dunn: /* Web Conferencing Clusters */

Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server

2010-11-02T11:52:29Z

Dunn: /* Web Conferencing Clusters */ re-written sentence on Web Server cluster definitions

Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x

2010-10-30T23:39:47Z

Dunn: /* Suppressing Music-On-Hold */ additional note to mention CSCtg45036

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3|Cisco Unified MeetingPlace H.323/SIP IP Gateway]]

== About Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway ==

'''Notes: '''

* Use Cisco Unified MeetingPlace H.323/SIP IP Gateway software Release 5.3 or Release 6.0 with IP PBX systems that are running standard H.323 or SIP call control-such as Avaya, Nortel, Alcatel, and Pingtel systems.

* For information about configuring third-party call-control applications: If you are using an IP PBX that runs standard H.323 or SIP call control, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#About Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway|About Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway]] page for required system settings and see your IP PBX documentation for information about how to configure those settings.

* For more information about installing Multi Access (MA) blades or configuring the Cisco Unified MeetingPlace Audio Server system for IP, see the [[Cisco Unified MeetingPlace, Release 6.x -- About Using Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 With Release 6.x#Additional References for Working with Cisco Unified MeetingPlace H.323/SIP IP Gateway Software|Additional References for Working with Cisco Unified MeetingPlace H.323/SIP IP Gateway Software]] page.

Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with one of the following servers:
* Cisco Unified Communications Manager
* Cisco SIP Proxy Server
* (Optional) H.323 gatekeeper

'''Note: ''' If you are using an IP PBX that runs standard H.323 or SIP call control, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#How to Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway|How to Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway]] page for the required system settings and see your IP PBX documentation for information about how to configure those settings.

The following tables describe the Cisco Unified MeetingPlace H.323/SIP IP Gateway Management Console fields and list the default settings:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: General Settings|Table: General Settings]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: H.323 Settings|Table: H.323 Settings]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: SIP Settings|Table: SIP Settings]]

'''Note:''' Starting with Cisco Unified MeetingPlace Release 6.0 Maintenance Release 3 (MR3), the Cisco Unified MeetingPlace H.323/SIP IP Gateway no longer uses the Management Console. Instead, to configure the gateway, use the Cisco Unified MeetingPlace Gateway Configuration utility. Access the utility by double-clicking the orange door icon in the system tray.

===== Table: General Settings=====

{| border = 1
|-
!Setting
!Description
!Default
|-
|

Max Number of Callers
|

Maximum number of callers Cisco Unified MeetingPlace H.323/SIP IP Gateway will accept. This maximum number can be a combination of H.323 and SIP callers.
|

960
|-
|

Outdial Protocol
|

Controls whether outdials from the IP-gateway server are placed by using H.323 or SIP.

'''Note: ''' In mixed H.323-SIP, call-control environments, you must select one protocol for outdials; otherwise, the default protocol will be used.
|

H.323
|-
|

Verbose Logging
|

Sets the level of logging information.
|

Normal
|}

===== Table: H.323 Settings =====

{| border = 1
|-
!Setting
!Description
!Default
|-
|

Enabled
|

Enables or disables the H.323 protocol.
|

Yes
|-
|

Max Number of Callers
|

Maximum number of H.323 callers Cisco Unified MeetingPlace H.323/SIP IP Gateway accepts.
|

960
|-
|

E.164 Address
|

A dialable number for the IP-gateway server.
|

-
|-
|

H323 ID
|

Caller ID name that is used by Cisco Unified MeetingPlace H.323/SIP IP Gateway.
|

MeetingPlace
|-
|

Gateway Address and Gateway Port
|

IP address and port number of the server responsible for routing H.323 calls. Outdials using H.323 are directed to this IP address and port if an H.323 gatekeeper is not used.

'''Note: ''' You must enter this gateway information if you are using H.323 without a gatekeeper.
|

Address: -

Port: 1720
|-
|

Use Gatekeeper
|

Enables the IP-gateway server to register with an H.323 gatekeeper.
|

No
|-
|

Gatekeeper Address and Gatekeeper Port
|

IP address and port number of the H.323 gatekeeper. If an H.323 gatekeeper is used, Cisco Unified MeetingPlace H.323/SIP IP Gateway registers with the server and directs H.323 outdials to the server.

'''Note: ''' If using an H.323 gatekeeper, ensure that your system allows traffic to pass through ports 1024-65535 because MeetingPlace H.323/SIP IPGW uses these ports for dynamic TCP and UDP traffic.
|

Address: -

Port: 1719
|-
|

QOS DSCP
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

Differentiated Services Code Point value for the Quality of Service configuration setting.
|

26
|-

|}

===== Table: SIP Settings =====

{| border = 1
|-
!Setting
!Description
!Default
|-
|

Enabled
|

Enables or disables the SIP protocol.
|

Yes
|-
|

Max Number of Callers
|

Maximum number of SIP callers Cisco Unified MeetingPlace H.323/SIP IP Gateway accepts.
|

960
|-
|

Display Name
|

Display name of the IP-gateway server that is used for SIP messages.
|

MeetingPlace
|-
|

User Name
|

A dialable number for the IP-gateway server.
|

(blank)
|-
|

Session Name
|

Session name used in Session Description Protocol (SDP) body.
|

MeetingPlace IP Call
|-
|

RSNA Prefix
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

The prefix used for RSNA transfers used to identify the referring system to the voice gateway.
|

(blank)
|-
|

Proxy Server Address and Proxy Server Port
|

IP address and port number of the Cisco SIP Proxy Server. Cisco Unified MeetingPlace system outdials placed by using SIP are directed to this IP address and port.

'''Note: ''' If using Cisco SIP Proxy Server, ensure that your system allows traffic to pass through ports 1024-65535 because Cisco Unified MeetingPlace H.323/SIP IP Gateway uses these ports for dynamic TCP and UDP traffic.
|

Address: -

Port: 5060

|-
|
Stack Log Directory
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

The SIP stack logging folder.

|

(blank)

|-
|
Stack Log Level
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

The SIP stack logging verbosity level.

|

3

|}

== How to Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway ==

You must configure Cisco Unified MeetingPlace H.323/SIP IP Gateway to dial out by using one of the following servers:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco Unified Communications Manager|Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco Unified Communications Manager]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco SIP Proxy Server|Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco SIP Proxy Server]]
* (Optional) [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With an H.323 Gatekeeper|Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With an H.323 Gatekeeper]]
* (Optional) [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Verifying MeetingPlace H.323/SIP IP Gateway Configuration|Verifying MeetingPlace H.323/SIP IP Gateway Configuration]]

'''Note: ''' Cisco Unified MeetingPlace H.323/SIP IP Gateway supports concurrent incoming H.323 and SIP calls; however, you must configure the Cisco Unified MeetingPlace H.323/SIP IP Gateway to use one protocol, either H.323 or SIP, to dial out.

=== Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco Unified Communications Manager ===

'''Note:''' If you are configuring the Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with Cisco Unified Communications Manager on a system that also hosts the Cisco Unified MeetingPlace Web Server, you need to configure a separate gateway in Cisco Unified Communications Manager for each of the two IP addresses that the Cisco Unified MeetingPlace Web Server uses.

# Access the server(s) Cisco Unified MeetingPlace H.323/SIP IP Gateway is installed on
# '''For Cisco Unified MeetingPlace Release 6.0 MR3 and above'''
## Double-click the orange door icon in the system tray or go to Start > Programs > MeetingPlace Applications > MeetingPlace Gateway Configuration
#; For Cisco Unified MeetingPlace Release 6.0 MR2 and below
## Go to Start, Run, and type "mmc"
## Go to File, Add/Remove Snap-in
## In the Standalone Snap-ins window select MeetingPlace IP Gateway & MeetingPlace Management Console
## Click on Add, and then OK
#: '''Tip: ''' You can also access Cisco Unified MeetingPlace H.323/SIP IP Gateway configuration settings through the Registry Editor by navigating to \\HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace IP Gateway.
# Use the settings in [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: Configuration Settings for Use with Cisco Unified Communications Manager|Table: Configuration Settings for Use with Cisco Unified Communications Manager]] to configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with Cisco Unified Communications Manager:

===== Table: Configuration Settings for Use with Cisco Unified Communications Manager =====

{| border = 1
|-
!Setting Type
!Field Name
!Setting
|-
|

General
|

Outdial Protocol
|

H.323
|-
|

H.323
|

Enabled
|

Yes
|-
|

H.323
|

E.164 Address
|

Dialable number for the MeetingPlace H.323/SIP IPGW
|-
|

H.323
|

H.323 ID
|

MeetingPlace
|-
|

H.323
|

Gateway Address
|

IP address of Cisco Unified Communications Manager
|-
|

H.323
|

Gateway Port
|

1720
|-
|

H.323
|

Use Gatekeeper
|

No
|}

4. To accept the settings, click '''Submit'''.

5. Restart the IP-gateway server.

=== Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco SIP Proxy Server ===

'''Note: ''' Cisco Unified MeetingPlace H.323/SIP IP Gateway does not support out-of-band digit detection with SIP.

# Access the server(s) Cisco Unified MeetingPlace H.323/SIP IP Gateway is installed on
# '''For Cisco Unified MeetingPlace Release 6.0 MR3 and above'''
## Double-click the orange door icon in the system tray or go to Start > Programs > MeetingPlace Applications > MeetingPlace Gateway Configuration
#; For Cisco Unified MeetingPlace Release 6.0 MR2 and below
## Go to Start, Run, and type "mmc"
## Go to File, Add/Remove Snap-in
## In the Standalone Snap-ins window select MeetingPlace IP Gateway & MeetingPlace Management Console
## Click on Add, and then OK
#: '''Tip: ''' You can also access Cisco Unified MeetingPlace H.323/SIP IP Gateway configuration settings through the Registry Editor by navigating to \\HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace IP Gateway.
# Use the settings in the following table to configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with Cisco SIP Proxy Server: .

===== Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 and Release 6.0 Configuration Settings for Use With Cisco SIP Proxy Server=====

{| border = 1
|-
!Setting Type
!Field Name
!Setting
|-
|

General
|

Outdial Protocol
|

SIP
|-
|

SIP
|

Enabled
|

Yes
|-
|

SIP
|

Display Name
|

MeetingPlace
|-
|

SIP
|

User Name
|

Dialable number for the MeetingPlace H.323/SIP IPGW
|-
|

SIP
|

Session Name
|

MeetingPlace IP Call
|-
|

SIP
|

Proxy Server Address
|

IP address of the Cisco SIP Proxy Server
|-
|

SIP
|

Proxy Server Port
|

5060
|}

4. To accept the settings, click '''Submit'''.

5. Restart the IP-gateway server.

=== Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With an H.323 Gatekeeper ===

'''Note: ''' Cisco Unified MeetingPlace H.323/SIP IP Gateway registers to the gatekeeper as a terminal device.

# Access the server(s) Cisco Unified MeetingPlace H.323/SIP IP Gateway is installed on
# '''For Cisco Unified MeetingPlace Release 6.0 MR3 and above'''
## Double-click the orange door icon in the system tray or go to Start > Programs > MeetingPlace Applications > MeetingPlace Gateway Configuration
#; For Cisco Unified MeetingPlace Release 6.0 MR2 and below
## Go to Start, Run, and type "mmc"
## Go to File, Add/Remove Snap-in
## In the Standalone Snap-ins window select MeetingPlace IP Gateway & MeetingPlace Management Console
## Click on Add, and then OK
#: '''Tip: ''' You can also access Cisco Unified MeetingPlace H.323/SIP IP Gateway configuration settings through the Registry Editor by navigating to \\HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace IP Gateway.
# Use the settings in [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway software Release 5.3 and Release 6.0 Configuration Settings for Use With an H.323 Gatekeeper|Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway software Release 5.3 Configuration Settings for Use With an H.323 Gatekeeper]] to configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with an H.323 gatekeeper.

===== Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 and Release 6.0 Configuration Settings for Use With an H.323 Gatekeeper=====

{| border = 1
|-
!Setting Type
!Field Name
!Setting
|-
|

General
|

Outdial Protocol
|

H.323
|-
|

H.323
|

Enabled
|

Yes
|-
|

H.323
|

E.164 Address
|

Dialable number for the MeetingPlace H.323/SIP IPGW
|-
|

H.323
|

H.323 ID
|

MeetingPlace
|-
|

H.323
|

Gateway Port
|

1720
|-
|

H.323
|

Gatekeeper Address
|

IP address of the H.323 Gatekeeper
|-
|

H.323
|

Gatekeeper Port
|

1719
|-
|

H.323
|

Use Gatekeeper
|

Yes
|}

4. To accept the settings, click '''Submit'''.

5. Restart the IP-gateway server.

=== Verifying MeetingPlace H.323/SIP IP Gateway Configuration ===

# To verify that Cisco Unified MeetingPlace H.323/SIP IP Gateway services are running, choose '''Start''' '''> Settings > Control Panel''' from the IP-gateway server; then, select '''Services'''.
# Make sure that the following services are running:
#* Cisco Unified MeetingPlace Gateway SIM
#* Cisco Unified MeetingPlace IP Gateway
# To verify that the IP-gateway server is logging in, telnet to the Cisco Unified MeetingPlace Audio Server.
# To verify that the IP-gateway server status is OK, enter '''gwstatus'''.
#: '''Note: ''' It can take up to five minutes for '''gwstatus''' to update; therefore, any recent changes to the gateway may not be reflected.
# Verify that you can access the Cisco Unified MeetingPlace Audio Server system by using a Cisco IP Phone.
# Verify that you can access Cisco Unified MeetingPlace Audio Server system by using a PSTN phone.

== About Configuring Multiple Cisco Unified MeetingPlace H.323/SIP IP Gateway Servers for Load Balancing and Redundancy ==

If you have deployed multiple IP-gateway servers to route IP calls, you can configure Cisco Unified Communications Manager or your IP PBX to load balance and to provide Cisco Unified MeetingPlace system redundancy by creating route groups that send calls to other IP-gateway servers if gateway failure occurs. A route group allows you to designate the order in which IP-gateway servers are selected and to prioritize a list of IP-gateways and ports for outgoing trunk selection.

All IP-gateway servers actively handle calls, and calls are routed round-robin among the IP-gateway servers. Therefore, in-session calls that are connected to an IP-gateway server that has failed are disconnected, and those callers must call again to be reconnected to the Cisco Unified MeetingPlace Audio Server system. New callers, however, are routed to another IP-gateway server.

For information about configuring route groups, see the Redundancy Chapter in the ''Cisco Unified Communications Manager System Guide ''for your software release at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

== About Configuring a Dialing Group ==

'''Note:''' The prompt menu that is configured to be played in a dialing group entry is also referred to as an "application type". Any references to a configurable application type in this documentation is functionally equivalent to the prompt menu in the following section.

Dialing groups customize the Cisco Unified MeetingPlace Audio Server by presenting specific voice prompts to callers who dial in to a meeting by using a particular IP phone number. For example, you can configure a dialing group to immediately place callers who dial extension 2121 into meeting ID 656565.

You configure dialing groups by editing the dialgroups.txt file to include the dial pattern with which to associate a specific dialing group; the application, or prompt, to play for the dialing group callers; and the meeting number to present to the Cisco Unified MeetingPlace Audio Server. Entries in dialgroups.txt are processed in order from top to bottom. If a match is not found, the caller is placed at the CombinedAccess menu, and the dialed digits are presented to the Cisco Unified MeetingPlace Audio Server.

== How to Configure a Dialing Group ==

# Open the Cisco Unified MeetingPlace H.232/SIP IP Gateway folder on your IP-gateway server.
# By using a text editor, open the dialgroups.txt file.
# Read the comment lines that start with the # symbol.
# Enter the dial pattern that you want to customize; then, enter a space. Valid selections are the following:
#* [0-9] [ A-D]-Presents the digits to the MeetingPlace audio server.
#* [.]-Matches any valid digit.
#* [*]-Matches 0 or more occurrences of the preceding digit.
# Enter the type of prompt menu to play to the caller; then, enter a space. Valid selections are the following:
#* CombinedAccess-Selects the Main menu.
#* DIDMeeting-Prompts the caller for the meeting ID to join. This option can be used to place the caller directly into a meeting if the digits match an existing meeting ID on the Cisco Unified MeetingPlace Audio Server system.
#* Profile-Prompts the caller for a profile number, which is not passed along to the Cisco Unified MeetingPlace server for user authentication.
#* MeetingNotes-Prompts the caller to retrieve meeting notes.
# Enter the digits to present to the Cisco Unified MeetingPlace Audio Server system. Valid selections are the following:
#* [0-9] [ A-D]-Presents the entered digits to the Cisco Unified MeetingPlace Audio Server system.
#* KEEP-Preserves the dialed digits.
#* NONE-Presents no digits to the server.
# Repeat Step [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#4|4]] through Step [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#6|6]] until the file contains one line for each dialing group that you want to configure.
# Save and close the dialgroups.txt file.
# Restart the IP-gateway server.
Caution: Do not enter any blank lines when editing the dialgroups.txt file. If there are any extra lines anywhere in the dialgroups.txt file (except for the normal blank line after the # symbols if dialgroups are not configured), the IP Gateway service will not start.

=== Configuring a Dialing Group Example ===

The following is a sample dialgroups.txt file that shows callers who dial extension 2121 are forwarded to meeting ID 656565. Callers who dial any other valid number are prompted to enter a profile number, and those digits are forwarded to the Cisco Unified MeetingPlace Audio Server.

<tt> 2121 DIDMeeting 656565 </tt>

<tt> .* Profile KEEP </tt>

== About Reservationless Single Number Access Configuration ==

With Reservationless Single Number Access (RSNA), profiled users who host or attend a reservationless meeting as either profile users or guests can access their meetings by dialing the same phone number, regardless of which Cisco Unified MeetingPlace Audio Server is hosting the meeting. With RSNA, users always dial the number of their home server, which then transfers the call to the scheduler or host's home server.

For information about configuring Reservationless Single Number Access, see [[Cisco Unified MeetingPlace, Release 6.x -- About RSNA|About RSNA]].

'''Note: ''' Gateways must support the Session Initiation Protocol (SIP) Refer Method, RFC 3515, to use RSNA.

== Allowing Reverse Connections to the MeetingPlace Audio Server ==

The Cisco Unified MeetingPlace Audio Server can initiate a reverse connection, eliminating the need for incoming port 5003 to be open on the Cisco Unified MeetingPlace Audio Server. To initiate the reverse connection, you must open port 5003 on the Cisco Unified MeetingPlace H.323/SIP IP Gateway.

== Suppressing Music-On-Hold ==

You can configure Cisco Unified Communications Manager to play music for the held party when users put a call on hold. However, if a user places a meeting on hold, the music plays into the meeting until the user retrieves the held call. To prevent this, you can configure Cisco Unified Communications Manager not to play music on hold for calls routed through Cisco Unified MeetingPlace H.323/SIP IP Gateway.

Specifically, make sure you do not assign to the Cisco Unified MeetingPlace H.323/SIP IP Gateway a Media Resource Group List that includes any Media Resource Group that includes Music on Hold servers, as the MeetingPlace IP Gateway can join a multicast Music-On-Hold (MoH) group. Since MeetingPlace is a transmit/receive environment, being put on hold can mean meeting participants listen to MoH, as well meetings in progress to devices configured to participate in the multicast group, resulting unexpected and undesirable privacy breaches.

As an additional workaround/resolution, if the customer is using Cisco Unified Communications Manager (CUCM) Version 6.1 and later, verify the CUCM Service Parameter "Send Multicast MOH in H.245 OLC Message" is set to False.

For information on configuring Media Resource Groups and Media Resource Group Lists, and associating these lists with endpoints, see the documentation for your release of Cisco Unified Communications Manager.

'''Note: ''' This solution does not suppress music on hold for remote endpoints which are registered to a different Cisco Unified Communications Manager cluster than Cisco Unified MeetingPlace. If the CUCM cluster connecting to MeetingPlace is v7.1.2 please also note of defect CSCtg45036.

Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x

2010-10-29T12:21:06Z

Dunn: /* Suppressing Music-On-Hold */ adding information about caveat when having MRGL that can join multicast group. Refer to TAC SR 614208939

[[Cisco Unified MeetingPlace, Release 6.x]] > [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3|Cisco Unified MeetingPlace H.323/SIP IP Gateway]]

== About Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway ==

'''Notes: '''

* Use Cisco Unified MeetingPlace H.323/SIP IP Gateway software Release 5.3 or Release 6.0 with IP PBX systems that are running standard H.323 or SIP call control-such as Avaya, Nortel, Alcatel, and Pingtel systems.

* For information about configuring third-party call-control applications: If you are using an IP PBX that runs standard H.323 or SIP call control, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#About Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway|About Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway]] page for required system settings and see your IP PBX documentation for information about how to configure those settings.

* For more information about installing Multi Access (MA) blades or configuring the Cisco Unified MeetingPlace Audio Server system for IP, see the [[Cisco Unified MeetingPlace, Release 6.x -- About Using Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 With Release 6.x#Additional References for Working with Cisco Unified MeetingPlace H.323/SIP IP Gateway Software|Additional References for Working with Cisco Unified MeetingPlace H.323/SIP IP Gateway Software]] page.

Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with one of the following servers:
* Cisco Unified Communications Manager
* Cisco SIP Proxy Server
* (Optional) H.323 gatekeeper

'''Note: ''' If you are using an IP PBX that runs standard H.323 or SIP call control, see the [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#How to Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway|How to Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway]] page for the required system settings and see your IP PBX documentation for information about how to configure those settings.

The following tables describe the Cisco Unified MeetingPlace H.323/SIP IP Gateway Management Console fields and list the default settings:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: General Settings|Table: General Settings]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: H.323 Settings|Table: H.323 Settings]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: SIP Settings|Table: SIP Settings]]

'''Note:''' Starting with Cisco Unified MeetingPlace Release 6.0 Maintenance Release 3 (MR3), the Cisco Unified MeetingPlace H.323/SIP IP Gateway no longer uses the Management Console. Instead, to configure the gateway, use the Cisco Unified MeetingPlace Gateway Configuration utility. Access the utility by double-clicking the orange door icon in the system tray.

===== Table: General Settings=====

{| border = 1
|-
!Setting
!Description
!Default
|-
|

Max Number of Callers
|

Maximum number of callers Cisco Unified MeetingPlace H.323/SIP IP Gateway will accept. This maximum number can be a combination of H.323 and SIP callers.
|

960
|-
|

Outdial Protocol
|

Controls whether outdials from the IP-gateway server are placed by using H.323 or SIP.

'''Note: ''' In mixed H.323-SIP, call-control environments, you must select one protocol for outdials; otherwise, the default protocol will be used.
|

H.323
|-
|

Verbose Logging
|

Sets the level of logging information.
|

Normal
|}

===== Table: H.323 Settings =====

{| border = 1
|-
!Setting
!Description
!Default
|-
|

Enabled
|

Enables or disables the H.323 protocol.
|

Yes
|-
|

Max Number of Callers
|

Maximum number of H.323 callers Cisco Unified MeetingPlace H.323/SIP IP Gateway accepts.
|

960
|-
|

E.164 Address
|

A dialable number for the IP-gateway server.
|

-
|-
|

H323 ID
|

Caller ID name that is used by Cisco Unified MeetingPlace H.323/SIP IP Gateway.
|

MeetingPlace
|-
|

Gateway Address and Gateway Port
|

IP address and port number of the server responsible for routing H.323 calls. Outdials using H.323 are directed to this IP address and port if an H.323 gatekeeper is not used.

'''Note: ''' You must enter this gateway information if you are using H.323 without a gatekeeper.
|

Address: -

Port: 1720
|-
|

Use Gatekeeper
|

Enables the IP-gateway server to register with an H.323 gatekeeper.
|

No
|-
|

Gatekeeper Address and Gatekeeper Port
|

IP address and port number of the H.323 gatekeeper. If an H.323 gatekeeper is used, Cisco Unified MeetingPlace H.323/SIP IP Gateway registers with the server and directs H.323 outdials to the server.

'''Note: ''' If using an H.323 gatekeeper, ensure that your system allows traffic to pass through ports 1024-65535 because MeetingPlace H.323/SIP IPGW uses these ports for dynamic TCP and UDP traffic.
|

Address: -

Port: 1719
|-
|

QOS DSCP
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

Differentiated Services Code Point value for the Quality of Service configuration setting.
|

26
|-

|}

===== Table: SIP Settings =====

{| border = 1
|-
!Setting
!Description
!Default
|-
|

Enabled
|

Enables or disables the SIP protocol.
|

Yes
|-
|

Max Number of Callers
|

Maximum number of SIP callers Cisco Unified MeetingPlace H.323/SIP IP Gateway accepts.
|

960
|-
|

Display Name
|

Display name of the IP-gateway server that is used for SIP messages.
|

MeetingPlace
|-
|

User Name
|

A dialable number for the IP-gateway server.
|

(blank)
|-
|

Session Name
|

Session name used in Session Description Protocol (SDP) body.
|

MeetingPlace IP Call
|-
|

RSNA Prefix
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

The prefix used for RSNA transfers used to identify the referring system to the voice gateway.
|

(blank)
|-
|

Proxy Server Address and Proxy Server Port
|

IP address and port number of the Cisco SIP Proxy Server. Cisco Unified MeetingPlace system outdials placed by using SIP are directed to this IP address and port.

'''Note: ''' If using Cisco SIP Proxy Server, ensure that your system allows traffic to pass through ports 1024-65535 because Cisco Unified MeetingPlace H.323/SIP IP Gateway uses these ports for dynamic TCP and UDP traffic.
|

Address: -

Port: 5060

|-
|
Stack Log Directory
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

The SIP stack logging folder.

|

(blank)

|-
|
Stack Log Level
|

'''Note:''' This field is only used for Cisco Unified MeetingPlace Release 6.0 MR3 and later.

The SIP stack logging verbosity level.

|

3

|}

== How to Configure Cisco Unified MeetingPlace H.323/SIP IP Gateway ==

You must configure Cisco Unified MeetingPlace H.323/SIP IP Gateway to dial out by using one of the following servers:
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco Unified Communications Manager|Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco Unified Communications Manager]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco SIP Proxy Server|Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco SIP Proxy Server]]
* (Optional) [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With an H.323 Gatekeeper|Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With an H.323 Gatekeeper]]
* (Optional) [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Verifying MeetingPlace H.323/SIP IP Gateway Configuration|Verifying MeetingPlace H.323/SIP IP Gateway Configuration]]

'''Note: ''' Cisco Unified MeetingPlace H.323/SIP IP Gateway supports concurrent incoming H.323 and SIP calls; however, you must configure the Cisco Unified MeetingPlace H.323/SIP IP Gateway to use one protocol, either H.323 or SIP, to dial out.

=== Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco Unified Communications Manager ===

'''Note:''' If you are configuring the Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with Cisco Unified Communications Manager on a system that also hosts the Cisco Unified MeetingPlace Web Server, you need to configure a separate gateway in Cisco Unified Communications Manager for each of the two IP addresses that the Cisco Unified MeetingPlace Web Server uses.

# Access the server(s) Cisco Unified MeetingPlace H.323/SIP IP Gateway is installed on
# '''For Cisco Unified MeetingPlace Release 6.0 MR3 and above'''
## Double-click the orange door icon in the system tray or go to Start > Programs > MeetingPlace Applications > MeetingPlace Gateway Configuration
#; For Cisco Unified MeetingPlace Release 6.0 MR2 and below
## Go to Start, Run, and type "mmc"
## Go to File, Add/Remove Snap-in
## In the Standalone Snap-ins window select MeetingPlace IP Gateway & MeetingPlace Management Console
## Click on Add, and then OK
#: '''Tip: ''' You can also access Cisco Unified MeetingPlace H.323/SIP IP Gateway configuration settings through the Registry Editor by navigating to \\HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace IP Gateway.
# Use the settings in [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: Configuration Settings for Use with Cisco Unified Communications Manager|Table: Configuration Settings for Use with Cisco Unified Communications Manager]] to configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with Cisco Unified Communications Manager:

===== Table: Configuration Settings for Use with Cisco Unified Communications Manager =====

{| border = 1
|-
!Setting Type
!Field Name
!Setting
|-
|

General
|

Outdial Protocol
|

H.323
|-
|

H.323
|

Enabled
|

Yes
|-
|

H.323
|

E.164 Address
|

Dialable number for the MeetingPlace H.323/SIP IPGW
|-
|

H.323
|

H.323 ID
|

MeetingPlace
|-
|

H.323
|

Gateway Address
|

IP address of Cisco Unified Communications Manager
|-
|

H.323
|

Gateway Port
|

1720
|-
|

H.323
|

Use Gatekeeper
|

No
|}

4. To accept the settings, click '''Submit'''.

5. Restart the IP-gateway server.

=== Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With Cisco SIP Proxy Server ===

'''Note: ''' Cisco Unified MeetingPlace H.323/SIP IP Gateway does not support out-of-band digit detection with SIP.

# Access the server(s) Cisco Unified MeetingPlace H.323/SIP IP Gateway is installed on
# '''For Cisco Unified MeetingPlace Release 6.0 MR3 and above'''
## Double-click the orange door icon in the system tray or go to Start > Programs > MeetingPlace Applications > MeetingPlace Gateway Configuration
#; For Cisco Unified MeetingPlace Release 6.0 MR2 and below
## Go to Start, Run, and type "mmc"
## Go to File, Add/Remove Snap-in
## In the Standalone Snap-ins window select MeetingPlace IP Gateway & MeetingPlace Management Console
## Click on Add, and then OK
#: '''Tip: ''' You can also access Cisco Unified MeetingPlace H.323/SIP IP Gateway configuration settings through the Registry Editor by navigating to \\HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace IP Gateway.
# Use the settings in the following table to configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with Cisco SIP Proxy Server: .

===== Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 and Release 6.0 Configuration Settings for Use With Cisco SIP Proxy Server=====

{| border = 1
|-
!Setting Type
!Field Name
!Setting
|-
|

General
|

Outdial Protocol
|

SIP
|-
|

SIP
|

Enabled
|

Yes
|-
|

SIP
|

Display Name
|

MeetingPlace
|-
|

SIP
|

User Name
|

Dialable number for the MeetingPlace H.323/SIP IPGW
|-
|

SIP
|

Session Name
|

MeetingPlace IP Call
|-
|

SIP
|

Proxy Server Address
|

IP address of the Cisco SIP Proxy Server
|-
|

SIP
|

Proxy Server Port
|

5060
|}

4. To accept the settings, click '''Submit'''.

5. Restart the IP-gateway server.

=== Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway for Use With an H.323 Gatekeeper ===

'''Note: ''' Cisco Unified MeetingPlace H.323/SIP IP Gateway registers to the gatekeeper as a terminal device.

# Access the server(s) Cisco Unified MeetingPlace H.323/SIP IP Gateway is installed on
# '''For Cisco Unified MeetingPlace Release 6.0 MR3 and above'''
## Double-click the orange door icon in the system tray or go to Start > Programs > MeetingPlace Applications > MeetingPlace Gateway Configuration
#; For Cisco Unified MeetingPlace Release 6.0 MR2 and below
## Go to Start, Run, and type "mmc"
## Go to File, Add/Remove Snap-in
## In the Standalone Snap-ins window select MeetingPlace IP Gateway & MeetingPlace Management Console
## Click on Add, and then OK
#: '''Tip: ''' You can also access Cisco Unified MeetingPlace H.323/SIP IP Gateway configuration settings through the Registry Editor by navigating to \\HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace IP Gateway.
# Use the settings in [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway software Release 5.3 and Release 6.0 Configuration Settings for Use With an H.323 Gatekeeper|Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway software Release 5.3 Configuration Settings for Use With an H.323 Gatekeeper]] to configure Cisco Unified MeetingPlace H.323/SIP IP Gateway for use with an H.323 gatekeeper.

===== Table: Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 and Release 6.0 Configuration Settings for Use With an H.323 Gatekeeper=====

{| border = 1
|-
!Setting Type
!Field Name
!Setting
|-
|

General
|

Outdial Protocol
|

H.323
|-
|

H.323
|

Enabled
|

Yes
|-
|

H.323
|

E.164 Address
|

Dialable number for the MeetingPlace H.323/SIP IPGW
|-
|

H.323
|

H.323 ID
|

MeetingPlace
|-
|

H.323
|

Gateway Port
|

1720
|-
|

H.323
|

Gatekeeper Address
|

IP address of the H.323 Gatekeeper
|-
|

H.323
|

Gatekeeper Port
|

1719
|-
|

H.323
|

Use Gatekeeper
|

Yes
|}

4. To accept the settings, click '''Submit'''.

5. Restart the IP-gateway server.

=== Verifying MeetingPlace H.323/SIP IP Gateway Configuration ===

# To verify that Cisco Unified MeetingPlace H.323/SIP IP Gateway services are running, choose '''Start''' '''> Settings > Control Panel''' from the IP-gateway server; then, select '''Services'''.
# Make sure that the following services are running:
#* Cisco Unified MeetingPlace Gateway SIM
#* Cisco Unified MeetingPlace IP Gateway
# To verify that the IP-gateway server is logging in, telnet to the Cisco Unified MeetingPlace Audio Server.
# To verify that the IP-gateway server status is OK, enter '''gwstatus'''.
#: '''Note: ''' It can take up to five minutes for '''gwstatus''' to update; therefore, any recent changes to the gateway may not be reflected.
# Verify that you can access the Cisco Unified MeetingPlace Audio Server system by using a Cisco IP Phone.
# Verify that you can access Cisco Unified MeetingPlace Audio Server system by using a PSTN phone.

== About Configuring Multiple Cisco Unified MeetingPlace H.323/SIP IP Gateway Servers for Load Balancing and Redundancy ==

If you have deployed multiple IP-gateway servers to route IP calls, you can configure Cisco Unified Communications Manager or your IP PBX to load balance and to provide Cisco Unified MeetingPlace system redundancy by creating route groups that send calls to other IP-gateway servers if gateway failure occurs. A route group allows you to designate the order in which IP-gateway servers are selected and to prioritize a list of IP-gateways and ports for outgoing trunk selection.

All IP-gateway servers actively handle calls, and calls are routed round-robin among the IP-gateway servers. Therefore, in-session calls that are connected to an IP-gateway server that has failed are disconnected, and those callers must call again to be reconnected to the Cisco Unified MeetingPlace Audio Server system. New callers, however, are routed to another IP-gateway server.

For information about configuring route groups, see the Redundancy Chapter in the ''Cisco Unified Communications Manager System Guide ''for your software release at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

== About Configuring a Dialing Group ==

'''Note:''' The prompt menu that is configured to be played in a dialing group entry is also referred to as an "application type". Any references to a configurable application type in this documentation is functionally equivalent to the prompt menu in the following section.

Dialing groups customize the Cisco Unified MeetingPlace Audio Server by presenting specific voice prompts to callers who dial in to a meeting by using a particular IP phone number. For example, you can configure a dialing group to immediately place callers who dial extension 2121 into meeting ID 656565.

You configure dialing groups by editing the dialgroups.txt file to include the dial pattern with which to associate a specific dialing group; the application, or prompt, to play for the dialing group callers; and the meeting number to present to the Cisco Unified MeetingPlace Audio Server. Entries in dialgroups.txt are processed in order from top to bottom. If a match is not found, the caller is placed at the CombinedAccess menu, and the dialed digits are presented to the Cisco Unified MeetingPlace Audio Server.

== How to Configure a Dialing Group ==

# Open the Cisco Unified MeetingPlace H.232/SIP IP Gateway folder on your IP-gateway server.
# By using a text editor, open the dialgroups.txt file.
# Read the comment lines that start with the # symbol.
# Enter the dial pattern that you want to customize; then, enter a space. Valid selections are the following:
#* [0-9] [ A-D]-Presents the digits to the MeetingPlace audio server.
#* [.]-Matches any valid digit.
#* [*]-Matches 0 or more occurrences of the preceding digit.
# Enter the type of prompt menu to play to the caller; then, enter a space. Valid selections are the following:
#* CombinedAccess-Selects the Main menu.
#* DIDMeeting-Prompts the caller for the meeting ID to join. This option can be used to place the caller directly into a meeting if the digits match an existing meeting ID on the Cisco Unified MeetingPlace Audio Server system.
#* Profile-Prompts the caller for a profile number, which is not passed along to the Cisco Unified MeetingPlace server for user authentication.
#* MeetingNotes-Prompts the caller to retrieve meeting notes.
# Enter the digits to present to the Cisco Unified MeetingPlace Audio Server system. Valid selections are the following:
#* [0-9] [ A-D]-Presents the entered digits to the Cisco Unified MeetingPlace Audio Server system.
#* KEEP-Preserves the dialed digits.
#* NONE-Presents no digits to the server.
# Repeat Step [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#4|4]] through Step [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace H.323/SIP IP Gateway Software Release 5.3 for Use With Release 6.x#6|6]] until the file contains one line for each dialing group that you want to configure.
# Save and close the dialgroups.txt file.
# Restart the IP-gateway server.
Caution: Do not enter any blank lines when editing the dialgroups.txt file. If there are any extra lines anywhere in the dialgroups.txt file (except for the normal blank line after the # symbols if dialgroups are not configured), the IP Gateway service will not start.

=== Configuring a Dialing Group Example ===

The following is a sample dialgroups.txt file that shows callers who dial extension 2121 are forwarded to meeting ID 656565. Callers who dial any other valid number are prompted to enter a profile number, and those digits are forwarded to the Cisco Unified MeetingPlace Audio Server.

<tt> 2121 DIDMeeting 656565 </tt>

<tt> .* Profile KEEP </tt>

== About Reservationless Single Number Access Configuration ==

With Reservationless Single Number Access (RSNA), profiled users who host or attend a reservationless meeting as either profile users or guests can access their meetings by dialing the same phone number, regardless of which Cisco Unified MeetingPlace Audio Server is hosting the meeting. With RSNA, users always dial the number of their home server, which then transfers the call to the scheduler or host's home server.

For information about configuring Reservationless Single Number Access, see [[Cisco Unified MeetingPlace, Release 6.x -- About RSNA|About RSNA]].

'''Note: ''' Gateways must support the Session Initiation Protocol (SIP) Refer Method, RFC 3515, to use RSNA.

== Allowing Reverse Connections to the MeetingPlace Audio Server ==

The Cisco Unified MeetingPlace Audio Server can initiate a reverse connection, eliminating the need for incoming port 5003 to be open on the Cisco Unified MeetingPlace Audio Server. To initiate the reverse connection, you must open port 5003 on the Cisco Unified MeetingPlace H.323/SIP IP Gateway.

== Suppressing Music-On-Hold ==

You can configure Cisco Unified Communications Manager to play music for the held party when users put a call on hold. However, if a user places a meeting on hold, the music plays into the meeting until the user retrieves the held call. To prevent this, you can configure Cisco Unified Communications Manager not to play music on hold for calls routed through Cisco Unified MeetingPlace H.323/SIP IP Gateway.

Specifically, make sure you do not assign to the Cisco Unified MeetingPlace H.323/SIP IP Gateway a Media Resource Group List that includes any Media Resource Group that includes Music on Hold servers, as the MeetingPlace IP Gateway can join a multicast Music-On-Hold (MoH) group. Since MeetingPlace is a transmit/receive environment, being put on hold can mean meeting participants listen to MoH, as well meetings in progress to devices configured to participate in the multicast group, resulting unexpected and undesirable privacy breaches.

As an additional workaround/resolution, if the customer is using Cisco Unified Communications Manager (CUCM) Version 6.0 and later, verify the CUCM Service Parameter "Send Multicast MOH in H.245 OLC Message" is set to True.

For information on configuring Media Resource Groups and Media Resource Group Lists, and associating these lists with endpoints, see the documentation for your release of Cisco Unified Communications Manager.

'''Note: ''' This solution does not suppress music on hold for remote endpoints which are registered to a different Cisco Unified Communications Manager cluster than Cisco Unified MeetingPlace.

Cisco Unified MeetingPlace, Release 6.x -- About Continuous Meetings

2010-05-24T16:53:58Z

Dunn: /* To Schedule a Continuous Meeting */ Removed statement that continuous meetings only lasts 24 hours. Cleared with DE it was erroneous and incorrect.

[[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 -- Scheduling and Attending Meetings|Scheduling and Attending Meetings]]

A continuous meeting is a permanent meeting that is always in session, even if everyone leaves and hangs up.

Schedule a continuous meeting, for example, for an all-day meeting during which users will take breaks. Also schedule a continuous meeting for groups or individuals who are involved in managing crisis situations and must be able to meet immediately whenever a problem arises.

===== To Schedule a Continuous Meeting =====

# Make sure you have system manager access through MeetingTime.
#: '''Note: ''' Continuous meetings can also be scheduled through the Cisco Unified MeetingPlace web interface. However, system managers cannot schedule continuous meetings through the phone interface.
# In the MeetingTime Schedule tab, for the Frequency attribute, choose ''' Continuous '''.
# Set additional meeting attributes, then click ''' Schedule Meeting '''.

Remember the following information:
* To cancel a continuous meeting, in the In Session tab, click ''' End Mtg '''. Up to 1000 continuous meetings can be scheduled on each Cisco Unified MeetingPlace system.
* After the last participant leaves a continuous meeting, the meeting data is moved to the database. This data appears when you generate a Raw Participant Join Leave report. (For more information, see the [[Cisco Unified MeetingPlace, Release 6.x -- Raw Participant Join Leave Information#Raw Participant Join Leave Information|Raw Participant Join Leave Information]].)
* To have the system outdial to all participants when the first participant joins a continuous meeting, set the Outdial Invitees on First Caller attribute in the Schedule tab to Yes. (For more information, see the table in the [[Cisco Unified MeetingPlace, Release 6.x -- About Using Features During Meetings#Dialing Out to Participants|Dialing Out to Participants]].)
* The Cisco Unified MeetingPlace Audio Server system does not allow entire continuous meetings to be recorded. Meeting comments, agenda messages, and meeting messages are fully supported on continuous meetings. If you want team members to be able to leave meeting messages for updates, then during a meeting the caller presses #6-5 and can listen, record, delete, re-record, or append a meeting message. During a meeting team members can listen to the meeting messages by dialing #6-5-1.
* Video terminals cannot be invited to continuous meetings.
* '''For Cisco Unified MeetingPlace Release 6.0 Maintenance Release 3 and earlier:''' If you mute everyone in the meeting using the "mute all" feature, meeting participants remain muted for the life of the meeting or until the next time the Audio Server is restarted.
* '''For Cisco Unified MeetingPlace Release 6.0 Maintenance Release 4 and later:''' If you mute everyone in the meeting using the "mute all" feature, meeting participants remain muted only until everyone leaves the meeting, including the web portion of the meeting.
* To see if a continuous meeting currently has any participants, use the polling feature. The polling feature pings the server every minute to see all the active meetings. Continuous meetings that are active (that is, that have participants currently in the meeting) are displayed in bold on the In Session tab. To enable this feature (which can only be done by attendants and above), go in to MeetingTime and select '''Options > Edit Settings''' and check Enable polling for active meetings.

== Using Video Conferencing During Continuous Meetings ==

If video resources are available, video conferences are started in a continuous meeting after the first video user joins the video conference. The video conference and video link remain active as long as there are video participants in the meeting. When no more video participants are in the meeting, the video link drops soon afterward. Later, when video participants again join, the video link is re-established if video resources are available.

Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service

2010-04-24T14:24:07Z

Dunn: re-add User ID for profile mandatory fields, comments /* Table: User Profile Field Configuration Through Directory Service */

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

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

== Directory Service ==

Directory Service enables the system to populate and synchronize the Cisco Unified MeetingPlace user database with the Cisco Unified Communications Manager user database, which is typically integrated with an LDAP directory.

'''Note: ''' For information about LDAP integration, see the ''Cisco Unified Communications Solution Reference Network Design (SRND)'' that applies to your version of Cisco Unified Communications Manager at http://www.cisco.com/go/designzone.

Specifically, Directory Service simplifies user profile administration by doing the following:

* Imports user profiles from Cisco Unified Communications Manager to Cisco Unified MeetingPlace.

* Periodically updates the Cisco Unified MeetingPlace database with new or modified user entries in the Cisco Unified Communications Manager database.

* Periodically checks the Cisco Unified Communications Manager database for inactive user entries, and deletes those user profiles from the Cisco Unified MeetingPlace database.

* Enables the system to use AXL authentication to authenticate Cisco Unified MeetingPlace Directory Service users against the external directory.

* Supports fully encrypted LDAP integration when Secure LDAP (SLDAP) is enabled on Cisco Unified Communications Manager and the LDAP server.
*: '''Note: ''' SSL for the Cisco Unified MeetingPlace Application Server is not required to support Secure LDAP integration. You must, however, make sure that the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#AXL URL|AXL URL]] begins with "https" instead of "http."

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

== Directory Service User Profile Configuration ==

During the initial Directory Service import of a user profile, the fields are configured as described in [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Table: User Profile Field Configuration Through Directory Service|Table: User Profile Field Configuration Through Directory Service]]. If the corresponding Cisco Unified Communications Manager user profile is modified, the next Directory Service user profile update or full synchronization reconfigures the Cisco Unified MeetingPlace user profile fields as specified in [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Table: User Profile Field Configuration Through Directory Service|Table: User Profile Field Configuration Through Directory Service]].

'''Note: ''' To change any of the [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#User Profile Fields|User Profile Fields]] in [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Table: User Profile Field Configuration Through Directory Service|Table: User Profile Field Configuration Through Directory Service]], you must configure the corresponding [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Source|Source]].

===== Table: User Profile Field Configuration Through Directory Service =====

{| border = 1
|-
!Source
!User Profile Fields
|-
|

Directory Service import process
|

[[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] -- This is always set to No in each Directory Service user profile.
|-
|

Cisco Unified Communications Manager user database
|

Below are mandatory fields for User Profile creation. Click on each field name for their detailed explanation:

* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User ID|User ID]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#First name|First name]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Last name|Last name]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]]
** Release 7.0.2 and later releases -- See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Cisco Unified MeetingPlace for Directory Service#Assigning Profile Numbers to Directory Service Users|Assigning Profile Numbers to Directory Service Users]].
** Release 7.0.1 -- Unique number based on the Telephone Number in Cisco Unified Communications Manager. If the Telephone Number is not available in Cisco Unified Communications Manager, Cisco Unified MeetingPlace randomly generates a unique [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] during the initial import of the user profile. As long as the phone number remains unavailable in Cisco Unified Communications Manager, the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] is not overwritten by Directory Service user profile updates or full synchronizations.
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User status|User status]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#E-mail address|E-mail address]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Main phone number|Main phone number]]

The User ID field cannot be an empty value. Unless otherwise specified, the field in Cisco Unified MeetingPlace User Profile is left blank if the corresponding field in Cisco Unified Communications Manager is empty.

|-
|

User group filters

or

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Group name|Group name]] in user profile
|

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Group name|Group name]] -- See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Cisco Unified MeetingPlace for Directory Service#Assigning User Groups for Directory Service Users|Assigning User Groups for Directory Service Users]].
|-
|

Time zone filters

or

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Time zone|Time zone]] in user group or user profile
|

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Time zone|Time zone]] -- See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Cisco Unified MeetingPlace for Directory Service#Assigning Time Zones to Directory Service Users|Assigning Time Zones to Directory Service Users]].
|-
|

Guest Profile (first import only)
|

All user profile fields ''not'' mentioned previously in this table are initially populated with the values configured in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Guest Profile|Guest Profile]]. You can then modify the individual user profile fields through the Administration Center. The values will ''not'' be overwritten by Directory Service user profile updates or full synchronizations.

Restrictions:
* Remember that all user profile fields set to "Group default" inherit their value from the user group. If the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Group name|Group name]] is modified through Directory Service filters or department number changes, the user profile fields will be modified accordingly.
* The following fields are not populated at all through Directory Service. Because Directory Service users are ''not'' authenticated by Cisco Unified MeetingPlace, these password fields are not imported and cannot be modified through Cisco Unified MeetingPlace:
** [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password confirm|User password confirm]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile password confirm|Profile password confirm]]
|}

===== 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 Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

== Directory Service User Profile Deletion ==

The system periodically checks Cisco Unified Communications Manager for inactive user entries and deletes those user profiles from Cisco Unified MeetingPlace. Specifically:

* (For Cisco Unified Communications Manager with LDAP integration) When a user is deleted or disabled in the LDAP directory, the corresponding user entry in Cisco Unified Communications Manager becomes ''inactive''.
: Every 24 hours, Cisco Unified Communications Manager ''deletes'' user entries that have been inactive for more than 24 hours.

* Every 8 hours, Cisco Unified MeetingPlace checks the value of the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Directory Service Configuration Page|Directory Service Configuration Page]].
** If the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]] field value is less than 24 hours, then no action is taken.
** If the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]] field value is 24 hours or more, then the system checks Cisco Unified Communications Manager for any inactive users, and ''deactivates'' those users in Cisco Unified MeetingPlace by setting the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User status|User status]] user profile field to Inactive.
: The system does ''not'' import or update user profiles using this 8-hour cycle. Instead, the importing and updating of user profiles occurs at the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]].
* According to the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]], the system ''deletes'' the following user profiles from Cisco Unified MeetingPlace:
** Users that are inactive in Cisco Unified Communications Manager.
** Directory Service users that are inactive in Cisco Unified MeetingPlace.
: The system also imports and updates user profiles at the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]].

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

== Directory Service [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] Setting In User Profiles ==

Each user profile in Cisco Unified MeetingPlace includes an [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] setting, which determines:

* Whether the user is authenticated externally through AXL authentication.

* How the user profile settings are configured.

{| border = 1
|-
![[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]]Setting
!Description
|-
|

Yes
|
* User is authenticated locally against the Cisco Unified MeetingPlace database.
* User profile settings can be modified through Cisco Unified MeetingPlace user interfaces.1
* Yes is the default value for user profiles that are manually imported or created through the Administration Center.
|-
|

No
|
* Identifies a Directory Service user.
* User is authenticated externally through AXL authentication. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#External AXL Authentication for Directory Service Users|External AXL Authentication for Directory Service Users]].
* User profile changes that are made through Cisco Unified MeetingPlace user interfaces1 may be overwritten by the next Directory Service user profile update. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]].
* No is the default value for user profiles that are imported through Directory Service.
|}

'''Footnote 1:''' Cisco Unified MeetingPlace user interfaces include the end-user web interface on the Web Server, the Cisco WebEx integration end-user interface on the Application Server, and the Administration Center (both the User Profiles Page and the Import User Profiles Page).

'''Note: ''' The [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] setting ''cannot'' be configured through the Administration Center. If you manually set [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] to No by adding or editing user profiles by import, note that the user profiles may be affected during the next Directory Service user update:

* Any ''inactive'' user entries found in Cisco Unified Communications Manager will be deleted from the Cisco Unified MeetingPlace database.

* Some user profile fields will be overwritten by data from Cisco Unified Communications Manager and by Directory Service filters.

See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]].

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- How To Import Data#Adding or Editing User Profiles by Import|Adding or Editing User Profiles by Import]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Methods for Adding User Profiles|Methods for Adding User Profiles]]

== External AXL Authentication for Directory Service Users ==

Directory Service users are those whose [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] user profile field is set to No. Which external device authenticates a Directory Service user depends on:

* Whether the user logs in over the phone or web.

* Whether Cisco Unified Communications Manager uses LDAP directory integration.

===== Table: Directory Service User Authentication =====

{| border = 1
|-
!Directory Service User Login Method
!Device Used to Authenticate the Directory Service User (With LDAP Integration)
!Device Used to Authenticate the Directory Service User (Without LDAP Integration)
|-
|

Phone
|

Cisco Unified Communications Manager
|

Cisco Unified Communications Manager
|-
|

Web
|

LDAP directory
|

Cisco Unified Communications Manager
|}

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service isLocalUser Setting In User Profiles|Directory Service isLocalUser Setting In User Profiles]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- User Authentication for Cisco Unified MeetingPlace|User Authentication for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

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

Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service

2010-04-22T01:37:49Z

Dunn: Edited : /* Table: User Profile Field Configuration Through Directory Service */ - remove userID line

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

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

== Directory Service ==

Directory Service enables the system to populate and synchronize the Cisco Unified MeetingPlace user database with the Cisco Unified Communications Manager user database, which is typically integrated with an LDAP directory.

'''Note: ''' For information about LDAP integration, see the ''Cisco Unified Communications Solution Reference Network Design (SRND)'' that applies to your version of Cisco Unified Communications Manager at http://www.cisco.com/go/designzone.

Specifically, Directory Service simplifies user profile administration by doing the following:

* Imports user profiles from Cisco Unified Communications Manager to Cisco Unified MeetingPlace.

* Periodically updates the Cisco Unified MeetingPlace database with new or modified user entries in the Cisco Unified Communications Manager database.

* Periodically checks the Cisco Unified Communications Manager database for inactive user entries, and deletes those user profiles from the Cisco Unified MeetingPlace database.

* Enables the system to use AXL authentication to authenticate Cisco Unified MeetingPlace Directory Service users against the external directory.

* Supports fully encrypted LDAP integration when Secure LDAP (SLDAP) is enabled on Cisco Unified Communications Manager and the LDAP server.
*: '''Note: ''' SSL for the Cisco Unified MeetingPlace Application Server is not required to support Secure LDAP integration. You must, however, make sure that the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#AXL URL|AXL URL]] begins with "https" instead of "http."

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

== Directory Service User Profile Configuration ==

During the initial Directory Service import of a user profile, the fields are configured as described in [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Table: User Profile Field Configuration Through Directory Service|Table: User Profile Field Configuration Through Directory Service]]. If the corresponding Cisco Unified Communications Manager user profile is modified, the next Directory Service user profile update or full synchronization reconfigures the Cisco Unified MeetingPlace user profile fields as specified in [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Table: User Profile Field Configuration Through Directory Service|Table: User Profile Field Configuration Through Directory Service]].

'''Note: ''' To change any of the [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#User Profile Fields|User Profile Fields]] in [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Table: User Profile Field Configuration Through Directory Service|Table: User Profile Field Configuration Through Directory Service]], you must configure the corresponding [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Source|Source]].

===== Table: User Profile Field Configuration Through Directory Service =====

{| border = 1
|-
!Source
!User Profile Fields
|-
|

Directory Service import process
|

[[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] -- This is always set to No in each Directory Service user profile.
|-
|

Cisco Unified Communications Manager user database
|

Unless otherwise specified, if the corresponding field in Cisco Unified Communications Manager is empty, the field is left blank in the Cisco Unified MeetingPlace user profile.
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#First name|First name]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Last name|Last name]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]]
** Release 7.0.2 and later releases -- See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Cisco Unified MeetingPlace for Directory Service#Assigning Profile Numbers to Directory Service Users|Assigning Profile Numbers to Directory Service Users]].
** Release 7.0.1 -- Unique number based on the Telephone Number in Cisco Unified Communications Manager. If the Telephone Number is not available in Cisco Unified Communications Manager, Cisco Unified MeetingPlace randomly generates a unique [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] during the initial import of the user profile. As long as the phone number remains unavailable in Cisco Unified Communications Manager, the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile number|Profile number]] is not overwritten by Directory Service user profile updates or full synchronizations.
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User status|User status]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#E-mail address|E-mail address]]
* [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Main phone number|Main phone number]]
|-
|

User group filters

or

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Group name|Group name]] in user profile
|

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Group name|Group name]] -- See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Cisco Unified MeetingPlace for Directory Service#Assigning User Groups for Directory Service Users|Assigning User Groups for Directory Service Users]].
|-
|

Time zone filters

or

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Time zone|Time zone]] in user group or user profile
|

[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Time zone|Time zone]] -- See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure Cisco Unified MeetingPlace for Directory Service#Assigning Time Zones to Directory Service Users|Assigning Time Zones to Directory Service Users]].
|-
|

Guest Profile (first import only)
|

All user profile fields ''not'' mentioned previously in this table are initially populated with the values configured in [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Guest Profile|Guest Profile]]. You can then modify the individual user profile fields through the Administration Center. The values will ''not'' be overwritten by Directory Service user profile updates or full synchronizations.

Restrictions:
* Remember that all user profile fields set to "Group default" inherit their value from the user group. If the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Group name|Group name]] is modified through Directory Service filters or department number changes, the user profile fields will be modified accordingly.
* The following fields are not populated at all through Directory Service. Because Directory Service users are ''not'' authenticated by Cisco Unified MeetingPlace, these password fields are not imported and cannot be modified through Cisco Unified MeetingPlace:
** [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password|User password]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User password confirm|User password confirm]]
** [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile password|Profile password]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile password confirm|Profile password confirm]]
|}

===== 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 Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

== Directory Service User Profile Deletion ==

The system periodically checks Cisco Unified Communications Manager for inactive user entries and deletes those user profiles from Cisco Unified MeetingPlace. Specifically:

* (For Cisco Unified Communications Manager with LDAP integration) When a user is deleted or disabled in the LDAP directory, the corresponding user entry in Cisco Unified Communications Manager becomes ''inactive''.
: Every 24 hours, Cisco Unified Communications Manager ''deletes'' user entries that have been inactive for more than 24 hours.

* Every 8 hours, Cisco Unified MeetingPlace checks the value of the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]] field on the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Directory Service Configuration Page|Directory Service Configuration Page]].
** If the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]] field value is less than 24 hours, then no action is taken.
** If the [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]] field value is 24 hours or more, then the system checks Cisco Unified Communications Manager for any inactive users, and ''deactivates'' those users in Cisco Unified MeetingPlace by setting the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User status|User status]] user profile field to Inactive.
: The system does ''not'' import or update user profiles using this 8-hour cycle. Instead, the importing and updating of user profiles occurs at the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]].
* According to the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]], the system ''deletes'' the following user profiles from Cisco Unified MeetingPlace:
** Users that are inactive in Cisco Unified Communications Manager.
** Directory Service users that are inactive in Cisco Unified MeetingPlace.
: The system also imports and updates user profiles at the configured [[Cisco Unified MeetingPlace, Release 7.0 -- Directory Service Configuration Page#Update users interval|Update users interval]].

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

== Directory Service [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] Setting In User Profiles ==

Each user profile in Cisco Unified MeetingPlace includes an [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] setting, which determines:

* Whether the user is authenticated externally through AXL authentication.

* How the user profile settings are configured.

{| border = 1
|-
![[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]]Setting
!Description
|-
|

Yes
|
* User is authenticated locally against the Cisco Unified MeetingPlace database.
* User profile settings can be modified through Cisco Unified MeetingPlace user interfaces.1
* Yes is the default value for user profiles that are manually imported or created through the Administration Center.
|-
|

No
|
* Identifies a Directory Service user.
* User is authenticated externally through AXL authentication. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#External AXL Authentication for Directory Service Users|External AXL Authentication for Directory Service Users]].
* User profile changes that are made through Cisco Unified MeetingPlace user interfaces1 may be overwritten by the next Directory Service user profile update. See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]].
* No is the default value for user profiles that are imported through Directory Service.
|}

'''Footnote 1:''' Cisco Unified MeetingPlace user interfaces include the end-user web interface on the Web Server, the Cisco WebEx integration end-user interface on the Application Server, and the Administration Center (both the User Profiles Page and the Import User Profiles Page).

'''Note: ''' The [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] setting ''cannot'' be configured through the Administration Center. If you manually set [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] to No by adding or editing user profiles by import, note that the user profiles may be affected during the next Directory Service user update:

* Any ''inactive'' user entries found in Cisco Unified Communications Manager will be deleted from the Cisco Unified MeetingPlace database.

* Some user profile fields will be overwritten by data from Cisco Unified Communications Manager and by Directory Service filters.

See [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service User Profile Configuration|Directory Service User Profile Configuration]].

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- How To Import Data#Adding or Editing User Profiles by Import|Adding or Editing User Profiles by Import]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure User Profiles#Methods for Adding User Profiles|Methods for Adding User Profiles]]

== External AXL Authentication for Directory Service Users ==

Directory Service users are those whose [[Cisco Unified MeetingPlace, Release 7.0 -- User Profiles-Raw Data Export and Import Specifications#isLocalUser|isLocalUser]] user profile field is set to No. Which external device authenticates a Directory Service user depends on:

* Whether the user logs in over the phone or web.

* Whether Cisco Unified Communications Manager uses LDAP directory integration.

===== Table: Directory Service User Authentication =====

{| border = 1
|-
!Directory Service User Login Method
!Device Used to Authenticate the Directory Service User (With LDAP Integration)
!Device Used to Authenticate the Directory Service User (Without LDAP Integration)
|-
|

Phone
|

Cisco Unified Communications Manager
|

Cisco Unified Communications Manager
|-
|

Web
|

LDAP directory
|

Cisco Unified Communications Manager
|}

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

* [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory Service isLocalUser Setting In User Profiles|Directory Service isLocalUser Setting In User Profiles]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- User Authentication for Cisco Unified MeetingPlace|User Authentication for Cisco Unified MeetingPlace]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]]

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

Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System

2010-02-09T02:03:43Z

Dunn: /* Configuring Requirements for Meeting Passwords */ - update to explain meeting passwords are numeric

{{Template:Required Metadata}}

== Enabling Password Complexity for the mpxadmin User ==

''Note: This section only applies to Release 2.1.x.''

You can increase the security of your Cisco Unified MeetingPlace Express system by enabling password complexity for the mpxadmin user. Complex passwords have the following characteristics:
* Must be 14 characters or longer
* Must contain at least two lowercase characters
* Must contain at least two uppercase characters
* Must contain at least two digits
* Must contain at least two special characters
* Must be changed at least every 60 days

'''Notes: '''
* When the mpxadmin user logs in after the mpxadmin password has expired, the system prompts the mpxadmin user to change it.
* If the mpxadmin password has expired, the application will not come up. You can restart the system, but until you change the mpxadmin password, the application services will not start properly.

===== Procedure =====

# Log in to the Cisco Unified MeetingPlace Express operating system as the '''mpxadmin''' user.
# At the password prompt, enter the mpxadmin password.
# Right-click on the desktop.
# From the menu, select '''New Terminal'''. This brings up a terminal session.
# Enable password complexity for the mpxadmin user by entering the following:
#: '''$MP_OS_HOME/enable_complex_passwd.sh'''
# Disable password complexity for the mpxadmin user by entering the following:
#: '''$MP_OS_HOME/disable_complex_passwd.sh'''

== Configuring User Password Requirements ==

You can increase the security of your Cisco Unified MeetingPlace Express system by doing the following:
* Requiring long user passwords
* Requiring users to change their passwords frequently

===== Tip =====
* Long passwords and frequent password changes may frustrate your users. Align your password requirements with those already in use at your company.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration''' > '''Usage Configuration'''.
# Configure the following fields:
#* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Minimum profile password length|Minimum profile password length]]-A higher value is more secure than a lower value.
#* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Change profile password (days)|Change profile password (days)]]-A lower value is more secure than a higher value.
#* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Minimum user password length|Minimum user password length]]-A higher value is more secure than a lower value.
#* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Change user password (days)|Change user password (days)]]-A lower value is more secure than a higher value.
# Click '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Field Reference: Usage Configuration|Field Reference: Usage Configuration]]

== Limiting the Number of Failed User Login Attempts ==

This topic describes how to configure the number of times in a session that an end user can fail to log in to Cisco Unified MeetingPlace Express before the user profile becomes "locked." Users with locked user profiles cannot log in.

Before reaching the maximum number of login attempts, the user may restart the counter for failed login attempts by taking one of the following actions:
* Close the browser and open a new one to continue the login attempts.
* End the call to Cisco Unified MeetingPlace Express and begin a new call to continue the login attempts.

===== Restriction =====
* The preconfigured system administrator profile cannot be locked.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration''' > '''Usage Configuration'''.
# Configure the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Maximum profile login attempts|Maximum profile login attempts]] field. A lower value is more secure than a higher value.
# Click '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Change the State of a User Profile#How to Change the State of a User Profile|How to Change the State of a User Profile]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Field Reference: Usage Configuration|Field Reference: Usage Configuration]]

== Configuring Requirements for Meeting Passwords ==

You can increase the security of your Cisco Unified MeetingPlace Express system by doing the following:
* Requiring passwords for meetings scheduled by some or all users
* Requiring long meeting passwords

Meeting passwords prevent uninvited people from attending meetings. The meeting passwords are recognised as a numeric form, that is, even if you have set an alphabetical password for a scheduled meeting, each character of the password will be recorded as a numeric digit based on the telephone keypad. For example, 'turnaround' will be recorded as '8876276863'.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration''' > '''Meeting Configuration'''.
# Configure the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Meeting Configuration#Minimum meeting password length|Minimum meeting password length]] field. A higher value is more secure than a lower value.
# Click '''Save'''.
# Click '''System Configuration''' > '''User Configuration'''.
# To configure a user group, click '''User Group Management'''. To configure an individual user profile, click '''User Profile Management'''.
# To configure an existing user group or user profile, click '''Edit'''. To configure a new user group or user profile, click '''Add New'''.
# Set the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Group#Password required|Password required]] to '''Yes'''.
# Click '''Save'''.
# Repeat [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Step 5|Step 5]] through [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Step 9|Step 9]] for all user groups and user profiles for which you want to require meeting passwords.

===== Tips =====

Remember that the password must be communicated to the meeting invitees in order for them to join the meeting:
* Configure user groups and user profiles to include passwords in e-mail notifications. See the [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Configure E-Mail Notifications#Configuring E-Mail Notification Settings for a User Group|Configuring E-Mail Notification Settings for a User Group]].
* If not all meeting invitees will receive e-mail notifications, the meeting scheduler or another organizer must manually communicate the meeting password.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Meeting Configuration#Field Reference: Meeting Configuration|Field Reference: Meeting Configuration]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Group#Field Reference: Add User Group|Field Reference: Add User Group]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Profile#Field Reference: Add User Profile|Field Reference: Add User Profile]]

== Restricting Access to Scheduled Meetings and Recordings ==

This topic describes how to restrict unprofiled users from taking the following actions:
* Attend meetings that are scheduled by some or all users.
* Listen to meetings recorded by some or all users.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration''' > '''User Configuration'''.
# To configure a user group, click '''User Group Management'''. To configure an individual user profile, click '''User Profile Management'''.
# To configure an existing user group or user profile, click '''Edit'''. To configure a new user group or user profile, click '''Add New'''.
# To restrict meeting attendance ''and'' access to meeting recordings to profiled users, set the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Group#Who can attend|Who can attend]] field to "Users with Cisco Unified MeetingPlace Express profiles only":
# Click '''Save'''.
# Repeat [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Step 2|Step 2]] through [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Step 6|Step 6]] for all user groups and user profiles for which you want to restrict meeting access to profiled users.

===== Tips =====
* Remember that 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.
* Similarly, if access to meeting recordings is restricted to profiled users, then unprofiled external users (such as your customers or business partners) and users with locked profiles cannot access these meeting recordings.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Group#Field Reference: Add User Group|Field Reference: Add User Group]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Profile#Field Reference: Add User Profile|Field Reference: Add User Profile]]

== Restricting the Use of Vanity Meeting IDs ==

By default, Cisco Unified MeetingPlace Express allows the meeting scheduler to request a specific meeting ID, such as one that is easy to remember (12345) or one that spells a word (24726 or CISCO). If, however, an uninvited person knows the phone number of your Cisco Unified MeetingPlace Express server, that person can easily guess a popular meeting ID and join a meeting that he is not authorized to attend.

You can also prevent unauthorized meeting attendance in the following ways:
* Requiring meeting passwords-See the [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Configuring Requirements for Meeting Passwords|Configuring Requirements for Meeting Passwords]].
* Restricting scheduled meeting attendance to profiled users-See the [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Restricting Access to Scheduled Meetings and Recordings|Restricting Access to Scheduled Meetings and Recordings]].

This topic describes how to prevent unauthorized meeting attendance by disabling the ability to request a vanity meeting ID when scheduling a meeting. Instead, a unique, randomly generated ID is assigned to every scheduled meeting. Users cannot change the assigned meeting IDs.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration > Meeting Configuration'''.
# Set the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Meeting Configuration#Allow vanity meeting IDs|Allow vanity meeting IDs]] field to '''No'''.
# Click '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Meeting Configuration#Field Reference: Meeting Configuration|Field Reference: Meeting Configuration]]

== Restricting Third Parties from Starting Reservationless Meetings ==

This topic describes how to configure the system so that only the meeting owner may start a reservationless meeting.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration''' > '''Meeting Configuration'''.
# Set the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Meeting Configuration#Reservationless: Allow 3rd party initiate|Reservationless: Allow 3rd party initiate]] field to '''No'''.
# Click '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Configure Scheduled and Reservationless Meetings#Enabling Users to Schedule Reservationless Meetings|Enabling Users to Schedule Reservationless Meetings]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Meeting Configuration#Field Reference: Meeting Configuration|Field Reference: Meeting Configuration]]

== Restricting Dial-Out Privileges for Guest Users ==

This topic describes how to restrict guests from dialing out. By completing this task, only profiled users who successfully log in to Cisco Unified MeetingPlace Express can dial out. This restriction can reduce the potential for toll fraud.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''System Configuration''' > '''Usage Configuration'''.
# Set the [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Allow guest outdials|Allow guest outdials]] field to '''No'''.
# Click '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Restricting Dial-Out Privileges for Profiled Users|Restricting Dial-Out Privileges for Profiled Users]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Usage Configuration#Field Reference: Usage Configuration|Field Reference: Usage Configuration]]

== Restricting Dial-Out Privileges for Profiled Users ==

This topic describes how to restrict dial-out privileges to specific user groups and user profiles. Restricting dial-out privileges reduces the potential for toll fraud.

===== Procedure =====

# Log in to Cisco Unified MeetingPlace Express and click '''Administration'''.
# Click '''User Configuration'''.
# To restrict dial-out privileges for specific user groups, click '''User Group Management'''. To restrict dial-out privileges for specific user profiles, click '''User Profile Management'''.
# Select a user group or user profile and click '''Edit''' in the same row.
# To restrict dial-out privileges, configure the following fields:
#* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Group#Can call out from meetings|Can call out from meetings]]-Set to '''No'''.
#* [[Cisco Unified MeetingPlace Express, Release 2.x -- Field Reference: Add User Group#Ask for profile password|Ask for profile password]]-Set to '''Yes'''.
# Click '''Save'''.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Secure Your System#Restricting Dial-Out Privileges for Guest Users|Restricting Dial-Out Privileges for Guest Users]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Configure User Groups#Navigating the User Group Management Page|Navigating the User Group Management Page]]
* [[Cisco Unified MeetingPlace Express, Release 2.x -- How to Configure User Profiles#Navigating the User Profile Management Page|Navigating the User Profile Management Page]]

[[Category:Configuring Security for Cisco Unified MeetingPlace Express, Release 2.x]]

Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Video Integration when installed with Cisco Unified MeetingPlace 6.0

2010-01-04T17:32:29Z

Dunn: /* Cisco Unified MeetingPlace Video Integration Requirements */ - remove Radvision products

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

'''Custom Search:'''
<html>
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="007771824002417948961:q0te3ntvco0" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<input type="submit" name="sa" value="Search" />
</div>
</form>

<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</html>

== Cisco Unified MeetingPlace Video Integration Requirements ==

===== Table: Requirements for Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0 when used with Cisco Unified MeetingPlace Release 6.0 =====

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

Cisco MCS hardware and system software
|

Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0 run on the server on which Cisco Unified MeetingPlace Web Conferencing Release 6.0 is installed. (For Web Conferencing hardware requirements, see [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0|Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0]].)

There are no additional hardware or operating system requirements for Video Integration.

For hardware and operating system requirements for Video Administration, see [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Video Integration when installed with Cisco Unified MeetingPlace 6.0#Video Administration for Cisco Unified MeetingPlace Requirements|Video Administration for Cisco Unified MeetingPlace Requirements]].
|-
|

Cisco Unified MeetingPlace Audio Server (Cisco 8112 or Cisco 8106)
|

Release 6.0
|-
|

Cisco Unified MeetingPlace Web Conferencing
|

Release 6.0
|-
|

Video Administration for Cisco Unified MeetingPlace
|

Release 5.4 or Release 5.6
|-
|

Cisco Unified MeetingPlace for Lotus Notes (Optional)
|

Release 6.0
|-
|

Cisco Unified MeetingPlace for Outlook (Optional)
|

Release 6.0
|-
|

Cisco Unified MeetingPlace H.323/SIP IP Gateway
|

Release 5.2.1 or later
|-
|

Cisco Unified MeetingPlace Directory Services (Optional)
|

Release 5.4 or Release 6.0
|-
|

Cisco Unified Videoconferencing Multipoint Control Unit (MCU)

|

===== Hardware =====

Release 4.x platform
* Cisco Unified Videoconferencing-3511-MCU or -3511-MCU-E
* 3544 chassis required for the following (four cards maximum per chassis):
** Cisco Unified Videoconferencing-3540-MCU-30 Port, -60 Port, or -100 Port
** Cisco Unified Videoconferencing-3540-EMP or -3540-EMP3 (optional, required for advanced video features)

Release 5.x platform
* Cisco Unified Videoconferencing-3515-MCU-12 Port or -24 Port
* 3545 chassis required for the following (four cards maximum per chassis; at least one MCU and one EMP card is required for video conferencing):
** Cisco Unified Videoconferencing-3545-MCU (96 port audio; each MCU supports up to four EMP cards)
** Cisco Unified Videoconferencing-3545-EMP (24 ports video; requires MCU card be present in chassis)
* Any hardware or components that are required to deploy the preceding releases, as specified in the documentation for each release.
* Rate Matching Module and Data Conferencing card are not supported. Disable them if they are present.
* A transcoder card may be required if you need to support the G.729 codec.

===== Software =====

Release 4.0 or later.

'''Note: ''' Cisco Unified MeetingPlace does not support a mixed environment of both MCU release 4.0 and MCU release 5.0. When using MCU release 4.0, the cascading video meeting feature is not available.

If your system uses SCCP video endpoints such as Cisco Unified Video Advantage, the following conditions apply:
* To view the continuous presence of multiple participants, the Cisco Unified Videoconferencing MCU requires an EMP processor running Release 2.0 or later.
* If the Cisco Unified Videoconferencing MCU has only an MP processor, and you choose to support SCCP endpoints, it is not possible to specify a continuous presence layout in the Cisco Unified Videoconferencing MCU. Therefore, all participants, regardless of their endpoint, can see only the active speaker.
* An EMP processor is included with release Cisco Unified Videoconferencing-3511-MCU-E.
|-
|

(Optional) Cisco Unified Videoconferencing PRI Gateway

(Optional) Cisco Unified Videoconferencing BRI Gateway
|

IPVC-3545-GW4S (4 Serial)

IPVC-3545-GW2P (2 PRI)

IPVC-3522-GW4B (4 BRI)

IPVC-3527-GW2P (2 PRI)

IPVC-3521-GW (4BRI)

IPVC-3526-GW (1PRI)

IPVC-3540-GW (2PRI)
|-
|

Cisco IOS gatekeeper

H.323 gatekeeper

|

Release not applicable.

If you use Cisco Unified CallManager, a Cisco IOS Gatekeeper is required.
|-
|

End user system operating system
|

Windows 98, Windows ME, Windows 2000, or Windows XP
|-
|

End user desktop video client
|
* The following video endpoints are supported:
** Any H.323 or SCCP video endpoint that the Cisco Unified Videoconferencing MCU and its associated components are configured to support.
** Any ISDN video endpoint and the associated required Cisco Unified Videoconferencing Gateway(s).
* A PC sound card is recommended in order to hear voice prompts.

|-
|

Room Based Video System
|

Any endpoints that are supported by the Cisco IPVC MCU.
|-
|

(Optional) Cisco Unified CallManager
|

Release 4.0(x), 4.1(x), 4.2(x), or 5.0(x). (For Cisco Unified MeetingPlace Release 6.0 MR5, we also support Cisco Unified Communications Manager Release 7.1.2.)
|}

== Video Administration for Cisco Unified MeetingPlace Requirements ==

Beginning with Release 5.4, the Cisco Unified MeetingPlace Video Integration includes and requires the Video Administration for Cisco Unified MeetingPlace subcomponent. You must install and configure the Video Administration for Cisco Unified MeetingPlace software on a separate Cisco MCS before installing Cisco Unified MeetingPlace Video Integration Release 5.4 or Release 6.0.

===== Table: Requirements for Video Administration for Cisco Unified MeetingPlace Release 5.4 and Release 5.6 when used with Cisco Unified MeetingPlace Release 6.0 =====

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

Hardware
|

Dedicated 7835 series or 7845 series Cisco MCS.
|-
|

Operating System
|

Cisco MCS OS 2003.1.1 or later.
|-
|

Software
|
* Video Administration for Cisco Unified MeetingPlace Release 5.4 or Release 5.6.
* Microsoft SQL Server 2000 must be installed on the Video Administration server. Microsoft SQL Server 2000 Desktop Engine (MSDE) is included with the Video Administration software and can be installed.
* (Optionally, Microsoft SQL Server 2000 Standard Edition or Microsoft SQL Server 2000 Enterprise Edition can be installed instead of MSDE. Customers must obtain their own software and licenses for Microsoft SQL Server 2000 Standard Edition or Microsoft SQL Server 2000 Enterprise Edition.)
* Microsoft Internet Explorer version 6.0 is required.
|}

Additional requirements may appear on the following page:

* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Components and Process#Supported Cisco Unified MeetingPlace System Configurations|Supported Cisco Unified MeetingPlace System Configurations]] for Cisco Unified MeetingPlace Video Integration.

Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Video Integration when installed with Cisco Unified MeetingPlace 6.0

2010-01-04T17:24:52Z

Dunn: /* Table: Requirements for Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0 when used with Cisco Unified MeetingPlace Release 6.0 */ - removed reference to Radvision ViaIP

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

'''Custom Search:'''
<html>
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="007771824002417948961:q0te3ntvco0" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<input type="submit" name="sa" value="Search" />
</div>
</form>

<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</html>

== Cisco Unified MeetingPlace Video Integration Requirements ==

===== Table: Requirements for Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0 when used with Cisco Unified MeetingPlace Release 6.0 =====

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

Cisco MCS hardware and system software
|

Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0 run on the server on which Cisco Unified MeetingPlace Web Conferencing Release 6.0 is installed. (For Web Conferencing hardware requirements, see [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0#Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0|Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.0]].)

There are no additional hardware or operating system requirements for Video Integration.

For hardware and operating system requirements for Video Administration, see [[Cisco Unified MeetingPlace, Release 6.x -- Requirements for Cisco Unified MeetingPlace Video Integration when installed with Cisco Unified MeetingPlace 6.0#Video Administration for Cisco Unified MeetingPlace Requirements|Video Administration for Cisco Unified MeetingPlace Requirements]].
|-
|

Cisco Unified MeetingPlace Audio Server (Cisco 8112 or Cisco 8106)
|

Release 6.0
|-
|

Cisco Unified MeetingPlace Web Conferencing
|

Release 6.0
|-
|

Video Administration for Cisco Unified MeetingPlace
|

Release 5.4 or Release 5.6
|-
|

Cisco Unified MeetingPlace for Lotus Notes (Optional)
|

Release 6.0
|-
|

Cisco Unified MeetingPlace for Outlook (Optional)
|

Release 6.0
|-
|

Cisco Unified MeetingPlace H.323/SIP IP Gateway
|

Release 5.2.1 or later
|-
|

Cisco Unified MeetingPlace Directory Services (Optional)
|

Release 5.4 or Release 6.0
|-
|

Cisco Unified Videoconferencing Multipoint Control Unit (MCU)

|

===== Hardware =====

Release 4.x platform
* Cisco Unified Videoconferencing-3511-MCU or -3511-MCU-E
* 3544 chassis required for the following (four cards maximum per chassis):
** Cisco Unified Videoconferencing-3540-MCU-30 Port, -60 Port, or -100 Port
** Cisco Unified Videoconferencing-3540-EMP or -3540-EMP3 (optional, required for advanced video features)

Release 5.x platform
* Cisco Unified Videoconferencing-3515-MCU-12 Port or -24 Port
* 3545 chassis required for the following (four cards maximum per chassis; at least one MCU and one EMP card is required for video conferencing):
** Cisco Unified Videoconferencing-3545-MCU (96 port audio; each MCU supports up to four EMP cards)
** Cisco Unified Videoconferencing-3545-EMP (24 ports video; requires MCU card be present in chassis)
* Any hardware or components that are required to deploy the preceding releases, as specified in the documentation for each release.
* Rate Matching Module and Data Conferencing card are not supported. Disable them if they are present.
* A transcoder card may be required if you need to support the G.729 codec.

===== Software =====

Release 4.0 or later.

'''Note: ''' Cisco Unified MeetingPlace does not support a mixed environment of both MCU release 4.0 and MCU release 5.0. When using MCU release 4.0, the cascading video meeting feature is not available.

If your system uses SCCP video endpoints such as Cisco Unified Video Advantage, the following conditions apply:
* To view the continuous presence of multiple participants, the Cisco Unified Videoconferencing MCU requires an EMP processor running Release 2.0 or later.
* If the Cisco Unified Videoconferencing MCU has only an MP processor, and you choose to support SCCP endpoints, it is not possible to specify a continuous presence layout in the Cisco Unified Videoconferencing MCU. Therefore, all participants, regardless of their endpoint, can see only the active speaker.
* An EMP processor is included with release Cisco Unified Videoconferencing-3511-MCU-E.
|-
|

(Optional) Cisco Unified Videoconferencing PRI Gateway

(Optional) Cisco Unified Videoconferencing BRI Gateway
|

IPVC-3545-GW4S (4 Serial)

IPVC-3545-GW2P (2 PRI)

IPVC-3522-GW4B (4 BRI)

IPVC-3527-GW2P (2 PRI)

IPVC-3521-GW (4BRI)

IPVC-3526-GW (1PRI)

IPVC-3540-GW (2PRI)
|-
|

(Optional) Radvision ViaIP GW-P20 Gateway
|

Release 2.0.1.12 or later
|-
|

Cisco IOS gatekeeper

H.323 gatekeeper

Radvision ViaIP ECS (gatekeeper)
|

Release not applicable.

If you use Cisco Unified CallManager, a Cisco IOS Gatekeeper is required.
|-
|

End user system operating system
|

Windows 98, Windows ME, Windows 2000, or Windows XP
|-
|

End user desktop video client
|
* The following video endpoints are supported:
** Any H.323 or SCCP video endpoint that the Cisco Unified Videoconferencing MCU and its associated components are configured to support.
** Any ISDN video endpoint and the associated required Cisco Unified Videoconferencing Gateway(s).
* A PC sound card is recommended in order to hear voice prompts.

|-
|

Room Based Video System
|

Any endpoints that are supported by the Cisco IPVC MCU.
|-
|

(Optional) Cisco Unified CallManager
|

Release 4.0(x), 4.1(x), 4.2(x), or 5.0(x). (For Cisco Unified MeetingPlace Release 6.0 MR5, we also support Cisco Unified Communications Manager Release 7.1.2.)
|}

== Video Administration for Cisco Unified MeetingPlace Requirements ==

Beginning with Release 5.4, the Cisco Unified MeetingPlace Video Integration includes and requires the Video Administration for Cisco Unified MeetingPlace subcomponent. You must install and configure the Video Administration for Cisco Unified MeetingPlace software on a separate Cisco MCS before installing Cisco Unified MeetingPlace Video Integration Release 5.4 or Release 6.0.

===== Table: Requirements for Video Administration for Cisco Unified MeetingPlace Release 5.4 and Release 5.6 when used with Cisco Unified MeetingPlace Release 6.0 =====

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

Hardware
|

Dedicated 7835 series or 7845 series Cisco MCS.
|-
|

Operating System
|

Cisco MCS OS 2003.1.1 or later.
|-
|

Software
|
* Video Administration for Cisco Unified MeetingPlace Release 5.4 or Release 5.6.
* Microsoft SQL Server 2000 must be installed on the Video Administration server. Microsoft SQL Server 2000 Desktop Engine (MSDE) is included with the Video Administration software and can be installed.
* (Optionally, Microsoft SQL Server 2000 Standard Edition or Microsoft SQL Server 2000 Enterprise Edition can be installed instead of MSDE. Customers must obtain their own software and licenses for Microsoft SQL Server 2000 Standard Edition or Microsoft SQL Server 2000 Enterprise Edition.)
* Microsoft Internet Explorer version 6.0 is required.
|}

Additional requirements may appear on the following page:

* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Components and Process#Supported Cisco Unified MeetingPlace System Configurations|Supported Cisco Unified MeetingPlace System Configurations]] for Cisco Unified MeetingPlace Video Integration.

Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0

2009-12-21T06:03:42Z

Dunn: /* Related Topics */ Updated URL link to docwiki pages

{{Template:Required Metadata}}
'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

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

== Enabling Automatic Authentication for IBM Lotus Notes Users ==

You can improve the speed of the meeting scheduling process by configuring your Lotus Domino Server to automatically authenticate users to Cisco Unified MeetingPlace. With automatic authentication, the Lotus Domino Server can pass user IDs to Cisco Unified MeetingPlace for verification whenever a user schedules a meeting. If the user IDs on both systems match, the system automatically signs users in to Cisco Unified MeetingPlace.

Without automatic authentication, users must enter their Cisco Unified MeetingPlace user IDs and passwords in the Calendar Entry form when they schedule a Cisco Unified MeetingPlace meeting.

=== Preparing the System for Lotus Domino Authentication ===

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

You must have a user ID with administrator privileges to log in to the Cisco Unified MeetingPlace Web Server.

===== Procedure =====

# Log in to the Cisco Unified MeetingPlace Web Server as an administrator.
# Select '''Start > Control Panel > Administrative Tools > Component Services'''.
# Select '''console root > Component Services > Computers > My Computer > DCOM Config > LNNotify''' from the left pane.
# Right click '''LNNotify'''.
# Click '''Properties'''.
# Click the Security tab.
# Select '''Customize''' from Launch and Activation Permissions.
# Click '''Edit'''.
# Highlight the user ID called Local Service.
# Grant the Local Service user ID Local Launch and Local Activation permissions.

=== Importing the User IDs ===

===== Restriction =====

You must configure Cisco Unified MeetingPlace to use only Cisco Unified MeetingPlace authentication before you can enable Lotus Domino authentication because IBM Lotus Notes does not support other authentication methods, such as Windows Integrated Authentication (WIA). For information on authentication, see the ''Configuration Guide for Cisco Unified MeetingPlace Release 7.0'' or the online help in the administrator interface.

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

You must have a user ID with administrator privileges to log in to the Lotus Domino Server.

===== Procedure =====

# Log in to the Lotus Domino Server as an administrator.
# Use one of the following methods to enter Cisco Unified MeetingPlace user IDs:
#* Import the Cisco Unified MeetingPlace user IDs.
#* Import the Lotus Domino address book ShortName field into the Cisco Unified MeetingPlace profile of each user as their user ID.
#: '''Note: ''' Although any Lotus Domino address book field can contain a Cisco Unified MeetingPlace user ID, we recommend using the ShortName field because it contains unique values, and has configurable security settings. If you decide to use another field that contains multiple values, make sure that the Cisco Unified MeetingPlace user ID is listed first. By default, Cisco Unified MeetingPlace uses the first value in the field for authentication.
# Set the security option in the ShortName field to '''Must Have at Least Editor Access to Use'''. This prevents users from changing their user IDs and signing in to Cisco Unified MeetingPlace as someone else.

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

For information about how to import Cisco Unified MeetingPlace user IDs, see the "Raw Data Export and Import Specifications" topic in the Configuration Guide for Cisco Unified MeetingPlace Release 7.0 at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace,_Release_7.0_--_Raw_Data_Export_and_Import_Specifications_for_Cisco_Unified_MeetingPlace

=== Verifying the Import ===

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

You must have a user ID with administrator privileges to log in to the Cisco Unified MeetingPlace Web Server.

===== Procedure =====

# Log in to the Cisco Unified MeetingPlace Web Server.
# Open the Gateways Configuration utility.
# Click the '''Notes Gateway''' tab.
# Verify that the authentication field contains the Cisco Unified MeetingPlace user IDs.
# Close the Gateway Configuration utility.

=== Setting the Authentication Method ===

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

You must have user IDs with administrator privileges to log in to the Lotus Domino Server, IBM Lotus Notes server, and Cisco Unified MeetingPlace Administration Center.

===== Procedure =====

# Log in to the Lotus Domino Server as an administrator.
# Open the MeetingPlace Server Agent Database.
# Click '''Use Domino Authentication'''.
# Click '''Save'''.
# Click '''Close'''.
# Open a web browser.
# Connect to the Cisco Unified MeetingPlace Web Server by entering '''http://''<hostname>''''', where ''<hostname>'' is the hostname of the internal Web Server.
# Click''' Sign In'''.
# Enter an administrator username and password.
# Click '''Admin'''.
# Click '''Web Server'''.
# From the Web Server Administration page, click the name of your server on the bottom half of the page. Server information populates the top half of the page.
# Choose '''Yes''' in '''Set Trust Web Server Authentication'''.
# Click '''Web Server Name''' in the View area.
# Scroll to the Web Authentication area.
# Choose '''Web Page Form''' in Step 2: Login Method.
# Click '''Submit'''.
# Exit Cisco Unified MeetingPlace.

'''Tip: ''' After you synchronize the user IDs on Cisco Unified MeetingPlace and Lotus Domino, you can develop a process to ensure that all new users have a Cisco Unified MeetingPlace profile. By developing scripts and using the Cisco Unified MeetingPlace import capabilities, you can automate this process so that Lotus Domino and Cisco Unified MeetingPlace are synchronized. For information about how you can use scripts to update the Cisco Unified MeetingPlace database, contact Cisco Technical Support.

== Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server ==

The template and Java files are in ''drive'':\Program Files\Cisco Systems\Cisco MeetingPlace for Notes\Files. You must copy these templates and files to the Lotus Domino Server data directory.

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

MPSA.ntf
|

The MeetingPlace Server Agent Database. Use this file if you do ''not'' want to set up SSL support.
|-
|

MPSA_SSL.ntf
|

The MeetingPlace Server Agent Database. Use this file if you ''do'' want to set up SSL support.
|-
|

mail''xx_xx''MP.ntf
|

The Cisco Unified MeetingPlace mail template for the version of IBM Lotus Notes that you are using. For example, mail70_1MP.ntf corresponds to the 7.0.1 mail template.
|-
|

jcert.jar

jnet.jar

jsse.jar
|

Additions to the Java setup for Lotus Domino. These files allow you to support SSL.
|}

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

* Log in to the Cisco Unified MeetingPlace Application Server as an administrator.

* Use ftp to connect to the Lotus Domino Server.

* Log in to the Lotus Domino Server with a user ID that has rwx privileges in the Lotus\Domino\Data directory.

===== Procedure =====

# Copy the following files to your Lotus Domino Server:
#* If you do ''not'' want to set up SSL support, copy the MPSA.ntf and mail''xx_xx''MP.ntf files to the Lotus\Domino\Data directory on your Lotus Domino Server.
#* If you ''do'' want to set up SSL support, copy the MPSA_SSL.ntf and mail''xx_xx''MP.ntf files to the Lotus\Domino\Data directory on your Lotus Domino Server. Copy the three Java extension files (jcert.jar, jnet.jar, jsse.jar) to the Lotus\Domino\jvm\lib\ext directory on your Lotus Domino Server.
#:'''Note: ''' If any of the template files already reside on the Lotus Domino Server and you overwrite these files with new ones, exit and restart the Lotus Domino Server after copying the new template files. This prevents the Lotus Domino Server from mistakenly signing templates stored in its cache.
# Enter '''Exit '''at the console command prompt.
# Choose '''Start > Programs > Lotus Applications > Domino Server''' to restart the Lotus Domino Server.

== Setting Up Database and Mail Templates for IBM Lotus Notes ==

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Granting Permission to Run Restricted and Unrestricted Agents on the Lotus Domino Server|Granting Permission to Run Restricted and Unrestricted Agents on the Lotus Domino Server]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Signing the MeetingPlace Server Agent Template|Signing the MeetingPlace Server Agent Template]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Signing the Cisco Unified MeetingPlace Mail Template|Signing the Cisco Unified MeetingPlace Mail Template]]

=== Granting Permission to Run Restricted and Unrestricted Agents on the Lotus Domino Server ===

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

* Log in to the Lotus Domino Server as an administrator.

* Open Domino Administrator.

* Click your Domain tab (for example, CISCO_Domain).

===== Procedure =====

# Click '''Configuration'''.
# Expand the '''Server''' view.
# Click '''Current Server Document'''.
# Click '''Security''' in the right pane.
# Double-click the page to bring it in to edit mode.
# Scroll to the right until you see the Programmability Restrictions area.
# In the Who Can column next to the following restrictions, add MeetingPlace to give yourself these permissions:
#* Run unrestricted methods and operations
#* Run restricted LotusScript/Java agents
# Click '''Save & Close'''.

=== Signing the MeetingPlace Server Agent Template ===

You must sign the MeetingPlace Server Agent template to verify that it is has permissions to run agents on the Lotus Domino Server.

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

* Copy the MeetingPlace Server Agent template to the Lotus Domino Server. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server|Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server]].

* Log in to the Lotus Domino Server as an administrator.

* Open Domino Administrator.

* Click your Domain tab (for example, CISCO_Domain).

===== Procedure =====

# Click '''Files'''.
# Choose '''Templates Only'''.
# Right-click the file name of the MeetingPlace Server Agent template (either MPSA.ntf or MPSA_SSL.ntf).
# Choose '''Sign'''.
# Click '''All Design Documents'''.
# Click '''OK'''.

=== Signing the Cisco Unified MeetingPlace Mail Template ===

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

* Copy the mail template to the Lotus Domino Server. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server|Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server]].

* Log in to the Lotus Domino Server as an administrator.

* Open Domino Administrator.

* Click your Domain tab (for example, CISCO_Domain).

===== Procedure =====

# Click '''Files'''.
# Choose '''Templates Only'''.
# Right-click the file name of the Cisco Unified MeetingPlace mail template (such as mail65_5MP.ntf or mail70_2MP.ntf).
# Choose '''Sign'''.
# Click '''OK'''.

'''Note: ''' To access the Cisco Unified MeetingPlace mail template from other Lotus Domino Servers, replicate the template file to those servers. See the Lotus Domino documentation for information about replicating files.

== Configuring SSL Support for IBM Lotus Notes ==

Secure Socket Layer (SSL) increases the security of your transmissions by enabling HTTPS encryption. For HTTPS encryption to function properly, you must configure both Lotus Domino and Cisco Unified MeetingPlace for SSL authentication. See the ''Configuration Guide for Cisco Unified MeetingPlace Release 7.0'' or the online help in the administrator interface for information on configuring SSL support for Cisco Unified MeetingPlace.

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Installing the Sun SDK File|Installing the Sun SDK File]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Adding Certificates to the Lotus Domino Keystore|Adding Certificates to the Lotus Domino Keystore]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Editing the java.policy File|Editing the java.policy File]]

=== Installing the Sun SDK File ===

The Sun SDK provides the keytool.exe tool which is used for importing certificates.

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

* Log in to the Lotus Domino Server as an administrator.

* Copy the three .jar files onto your Lotus Domino Server. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server|Copying IBM Lotus Notes Templates and Files to the Lotus Domino Server]].

===== Procedure =====

# Open a web browser.
# Navigate to http://java.sun.com/j2se/1.4.2/download.html.
# Click '''Download J2SE SDK'''.
# Select a platform.
# Check '''I agree to the Java 2 Software Development Kit (J2SDK) Standard Edition 1.4.2 License Agreement'''.
# Click '''Continue'''.
# Choose a download file from the Windows Platform area.
# Follow the prompts until the file is completely downloaded.

=== Adding Certificates to the Lotus Domino Keystore ===

After you obtain your certificates, use keytool.exe to add the certificates to the list of trusted certificates (your keystore) on your Lotus Domino Server. Your keystore is the cacerts file in the Lotus\Domino\jvm\lib\security directory of your Lotus Domino Server.

For more information about obtaining certificates, see the ''Configuration Guide for Cisco Unified MeetingPlace Release 7.0'' or the online help in the administrator interface.

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

Log in to the Cisco Unified MeetingPlace Web Server as an administrator.

===== Procedure =====

# Use FTP or a similar program to copy your certificate file from the Cisco Unified MeetingPlace Web Server to the Lotus Domino Server.
# Log in to the Lotus Domino Server as an administrator.
# Choose '''Start > Run'''.
# Enter '''cmd'''.
# Click '''OK'''.
# Enter the following command, replacing values as indicated below:
#: '''''<path>'' \jre\bin\keytool -import -alias [''anyalias''] -file [''yourcertificate.cer''] -keystore [''cacerts'']'''

{| border = 1
|-
!Replace
!With
|-
|

path
|

The path to your Java SDK files (for example, c:\j2sdk1.4.2_03)
|-
|

anyalias
|

The alias that you are applying to the certificate (for example, WebHomePageCertificate). This is how your certificate will be listed in the keystore.
|-
|

yourcertificate.cer
|

The path to your .cer file for the Home Page hostname (for example, c:\temp\webhomepage.cer)
|-
|

cacerts
|

The path to the cacerts file on your Lotus Domino server (for example, c:\Lotus\Domino\jvm\lib\ security\cacerts). cacerts is the name of your keystore.
|}
:: For example:
<tt> c:\j2sdk1.4.2_03\jre\bin\keytool -import -alias Ciscocertificate -file </tt>

<tt> c:\temp\newcertificate.cer -keystore c:\Lotus\Domino\jvm\lib\security\cacerts </tt>
:: '''Note: ''' Enter the default password, '''changeit''', if your Lotus Domino cacerts file requires a password.
7. Enter '''yes '''at''' '''the IBM Lotus Notes client prompt.

8. Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Step 6|Step 6]], replacing ''anyalias'' with a new alias and replacing ''yourcertificate.cer'' with the path to your .cer file for the server hostname.

9. Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Configure IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0#Step 7|Step 7]].

10. Close the command-line interface.

=== Editing the java.policy File ===

The java.policy file contains permission to set the system properties.

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

Log in to the Lotus Domino Server as an administrator.

===== Procedure =====

# Navigate to ''drive'':\Lotus\Domino\jvm\lib\security.
# Double-click java.policy to open it in Notepad.
# Add the following line to the end of the file just before the closing brace (};)
#: '''permission java.util.PropertyPermission "java.protocol.handler.pkgs", "write";'''
# Save and close the file.

== About Load Balancing for IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0 ==

There are no special considerations for load balancing when using IBM Lotus Notes with Cisco Unified MeetingPlace Release 7.0. For load balancing information, see [[Cisco Unified MeetingPlace, Release 7.0 -- About Load Balancing Options for the Web Server|About Load Balancing Options for the Web Server]].

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

Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions

2009-12-18T01:29:42Z

Dunn: /* Limitations of Video Administration */

[[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]]

== Limitations and Restrictions ==

This section contains the following information:
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Apple Safari Restrictions|Apple Safari Restrictions]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Configuration Considerations for Video Administration|Configuration Considerations for Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Database Unavailable During Initialization of Video Administration|Database Unavailable During Initialization of Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Expected Behavior for Video Administration|Expected Behavior for Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Limitations of Video Administration|Limitations of Video Administration]]

See also the ''Release Notes for Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0, and Video Administration Release 5.6'' here: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html

=== Apple Safari Restrictions ===

Cisco Unified MeetingPlace Web Conferencing does not support joining a video conference from the Apple Safari client. Users attending a web conference by using Safari cannot see the Use My Video Endpoint Number field and cannot join video conferences.

=== Configuration Considerations for Video Administration ===
* Cisco Unified MeetingPlace Video Administration can set only one Cisco MCM gatekeeper as its Cisco Internal Gatekeeper's neighbor.
* In certain countries, such as the United States, an area code is usually dialed with a phone number. In such cases, under Resource Management > Gateway in Video Administration, check the Always Dial Area Code check box.
* Ensure that terminal area codes are defined correctly and that domestic long-distance prefixes are omitted. DID numbers are currently assigned on a per-endpoint basis rather than on a per-meeting basis. This is an internal configuration and cannot be changed by using the Video Admin Configuration Tool or the Video Administration web interface.
* To ensure that web pages and pop-up windows are displayed normally, we recommend that you set the screen resolution to a standard resolution, such as 800 x 600 pixels or 1024 x 768 pixels. The minimum recommended resolution is 800 x 600 pixels, and the recommended font size is Normal or Large.
* The MCU service template name and description, terminal name, and gateway service prefix can contain only ASCII text. Unicode and other double-byte characters (such as Chinese, Japanese, Korean, and Hebrew characters) should not be used.
* Video Administration supports the Cisco Unified Videoconferencing 3500 MCU version 5.1 only in normal capacity configuration mode. High capacity mode is not supported. Additionally, high definition endpoints are not supported.

=== Database Unavailable During Initialization of Video Administration ===

If the database is not available during Video Administration initialization, restart the service when the database is available. If the connection between the database and Video Administration is lost after Video Administration initialization, Video Administration will function normally once the database is operating.

=== Expected Behavior for Video Administration ===
* If an MCU is taken offline, in-session meetings running on the MCU are canceled. The meeting records are moved to the History tab in the All Meetings and My Meetings sections.
* Taking an MCU offline and causing a large number of conferences to be rescheduled may result in an out-of-memory error.
* Cisco Unified Videoconferencing MCU version 4.x features, such as Encryption and Qualivision, function properly with Video Administration but are not displayed as meeting type information or in the In-Meeting Control user interface.
* If someone calls from an audio phone that has video capability to the video
conference, the system shows the endpoint with video and audio capability, even if the user only is using the audio capabilities.

=== Limitations of Video Administration ===
* Cascading cannot take place between a Cisco Unified Videoconferencing MCU version 4.x and an MCU version 5.0. Video Administration supports cascading only by using the same service on each MCU.
* Disconnecting Video Administration from an MCU while a conference is taking place may cause terminal participants in that conference to be disconnected.
* For cascaded MCU conferences, only one terminal participant on a slave MCU can be displayed on the conference layout.
* If the No Self-See setting is selected for an MCU service, when dragging terminals to the layout box on the In-Meeting Control screen, certain terminals are not displayed since they comply with the No Self-See restriction.
* The Subconf list on the In-Meeting Control screen displays inconsistent information for a cascaded conference.
* Video Administration does not support the Force Conference PIN Protection field in the MCU service definition.
* When scheduling a conference with 3G terminals, a terminal defined with a bandwidth of 64Kbps video is actually connected at 64Kbps audio. A workaround for this problem is to define the 3G terminal as an IP terminal whose E.164 number is a combination of the 3G Gateway service number and the phone number of the 3G terminal.
* When scheduling an MCU meeting with a meeting password, when the MCU authorizes a terminal by using the meeting password, Video Administration does not receive notification of the authorization event. Video Administration can determine this information only by polling MCU conference status, which may cause a delay in the notification of the authorization event to Cisco Unified MeetingPlace.
* In the Resource Management section of Video Administration, when you change the settings for a terminal, the changes are not reflected on the Terminals tab of the Meeting Templates and My Meetings sections.
* Reporting on a large number of conferences (on the Upcoming tab or the History tab) may cause an out-of-memory error.
* Adjusting the server clock disrupts the status of any recurring meetings that are scheduled.
* Each time you restart the Video Administration application, allow a few minutes for the service to initialize correctly. It is possible that some meetings may need to be extended during this time. In that case, meetings are not extended.
* The External conference authorization policy field on the Settings > Conference Management page must be set to None.
* If a meeting is set in waiting room mode, an H.323 terminal cannot unlock the meeting unless it is designated as the host terminal of this meeting.
* MeetingPlace Video Integration does not support endpoint-initiated ad-hoc or virtual room meetings by dialling a service prefix plus random number to form a meeting ID.
* Video Administration does not support the “auto” service in the H.320 gateway where the bandwidth is negotiated dynamically when a terminal connects.
* Video Blade fragmentation issues may occur when one meeting is scheduled on a Video Blade using a desktop service, and a second meeting is scheduled on the same Video Blade using a high rate service. Even though the combined port usage of the two meetings may be less than the capacity of a Video Blade, the meeting may still fail if the desktop meeting occupies the Video Blade DSP resource in such a way that only whole ports are left available for the high rate meeting, and only 1 or 2 ports are available. This is a rare event.
* When dialing into a Video Administration meeting, the MCU meeting ID is displayed on the endpoint monitor.
* Terminals in restricted mode (56K) cannot access a gateway in unrestricted mode (64 Kbps).
* Adjusting the server clock disrupts the status of any recurring meetings that are scheduled.
* Upload of a high definition continuous presence MCU service to another MCU that does not support high definition continuous presence is not supported.
* MCU features, such as encryption and Qualivision, function properly but are not displayed as meeting type information or in the in-meeting control user interface.
* When working with an MCU service that supports presentation view, the presentation view should be the second layout in the service definition on the MCU.
* When inviting multiple endpoints to a meeting, by default Video Administration sends the invitation request to the MCU for each endpoint in sequence without any delay between the requests. Sometimes this can cause a timing issue with the MCU so that not all the endpoints can connect successfully. To resolve this issue, go to Configuration Tool > General Settings and set the Command Delay value to 100 to 200 milliseconds.
* '''For Release 5.4(2.103) only:''' Cisco Unified MeetingPlace deployments do not support the use of the “Reserve Port on EMP for dynamic cascading” parameter on the Scheduling Settings tab of the Video Admin Configuration Tool.

Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions

2009-12-18T01:27:41Z

Dunn: /* Limitations of Video Administration */ removed # Endpoint-initiated ad hoc or virtual room meetings terminate 30 seconds after all participants have left. its in reference to CSCsy26804

[[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]]

== Limitations and Restrictions ==

This section contains the following information:
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Apple Safari Restrictions|Apple Safari Restrictions]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Configuration Considerations for Video Administration|Configuration Considerations for Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Database Unavailable During Initialization of Video Administration|Database Unavailable During Initialization of Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Expected Behavior for Video Administration|Expected Behavior for Video Administration]]
* [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions#Limitations of Video Administration|Limitations of Video Administration]]

See also the ''Release Notes for Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0, and Video Administration Release 5.6'' here: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html

=== Apple Safari Restrictions ===

Cisco Unified MeetingPlace Web Conferencing does not support joining a video conference from the Apple Safari client. Users attending a web conference by using Safari cannot see the Use My Video Endpoint Number field and cannot join video conferences.

=== Configuration Considerations for Video Administration ===
* Cisco Unified MeetingPlace Video Administration can set only one Cisco MCM gatekeeper as its Cisco Internal Gatekeeper's neighbor.
* In certain countries, such as the United States, an area code is usually dialed with a phone number. In such cases, under Resource Management > Gateway in Video Administration, check the Always Dial Area Code check box.
* Ensure that terminal area codes are defined correctly and that domestic long-distance prefixes are omitted. DID numbers are currently assigned on a per-endpoint basis rather than on a per-meeting basis. This is an internal configuration and cannot be changed by using the Video Admin Configuration Tool or the Video Administration web interface.
* To ensure that web pages and pop-up windows are displayed normally, we recommend that you set the screen resolution to a standard resolution, such as 800 x 600 pixels or 1024 x 768 pixels. The minimum recommended resolution is 800 x 600 pixels, and the recommended font size is Normal or Large.
* The MCU service template name and description, terminal name, and gateway service prefix can contain only ASCII text. Unicode and other double-byte characters (such as Chinese, Japanese, Korean, and Hebrew characters) should not be used.
* Video Administration supports the Cisco Unified Videoconferencing 3500 MCU version 5.1 only in normal capacity configuration mode. High capacity mode is not supported. Additionally, high definition endpoints are not supported.

=== Database Unavailable During Initialization of Video Administration ===

If the database is not available during Video Administration initialization, restart the service when the database is available. If the connection between the database and Video Administration is lost after Video Administration initialization, Video Administration will function normally once the database is operating.

=== Expected Behavior for Video Administration ===
* If an MCU is taken offline, in-session meetings running on the MCU are canceled. The meeting records are moved to the History tab in the All Meetings and My Meetings sections.
* Taking an MCU offline and causing a large number of conferences to be rescheduled may result in an out-of-memory error.
* Cisco Unified Videoconferencing MCU version 4.x features, such as Encryption and Qualivision, function properly with Video Administration but are not displayed as meeting type information or in the In-Meeting Control user interface.
* If someone calls from an audio phone that has video capability to the video
conference, the system shows the endpoint with video and audio capability, even if the user only is using the audio capabilities.

=== Limitations of Video Administration ===
* Cascading cannot take place between a Cisco Unified Videoconferencing MCU version 4.x and an MCU version 5.0. Video Administration supports cascading only by using the same service on each MCU.
* Disconnecting Video Administration from an MCU while a conference is taking place may cause terminal participants in that conference to be disconnected.
* For cascaded MCU conferences, only one terminal participant on a slave MCU can be displayed on the conference layout.
* If the No Self-See setting is selected for an MCU service, when dragging terminals to the layout box on the In-Meeting Control screen, certain terminals are not displayed since they comply with the No Self-See restriction.
* The Subconf list on the In-Meeting Control screen displays inconsistent information for a cascaded conference.
* Video Administration does not support the Force Conference PIN Protection field in the MCU service definition.
* When scheduling a conference with 3G terminals, a terminal defined with a bandwidth of 64Kbps video is actually connected at 64Kbps audio. A workaround for this problem is to define the 3G terminal as an IP terminal whose E.164 number is a combination of the 3G Gateway service number and the phone number of the 3G terminal.
* When scheduling an MCU meeting with a meeting password, when the MCU authorizes a terminal by using the meeting password, Video Administration does not receive notification of the authorization event. Video Administration can determine this information only by polling MCU conference status, which may cause a delay in the notification of the authorization event to Cisco Unified MeetingPlace.
* In the Resource Management section of Video Administration, when you change the settings for a terminal, the changes are not reflected on the Terminals tab of the Meeting Templates and My Meetings sections.
* Reporting on a large number of conferences (on the Upcoming tab or the History tab) may cause an out-of-memory error.
* Adjusting the server clock disrupts the status of any recurring meetings that are scheduled.
* Each time you restart the Video Administration application, allow a few minutes for the service to initialize correctly. It is possible that some meetings may need to be extended during this time. In that case, meetings are not extended.
* The External conference authorization policy field on the Settings > Conference Management page must be set to None.
* If a meeting is set in waiting room mode, an H.323 terminal cannot unlock the meeting unless it is designated as the host terminal of this meeting.
* MeetingPlace Video Integration does not support endpoint-initiated ad-hoc or virtual room meetings initiated by dialling a service prefix plus random number to form a meeting ID.
* Video Administration does not support the “auto” service in the H.320 gateway where the bandwidth is negotiated dynamically when a terminal connects.
* Video Blade fragmentation issues may occur when one meeting is scheduled on a Video Blade using a desktop service, and a second meeting is scheduled on the same Video Blade using a high rate service. Even though the combined port usage of the two meetings may be less than the capacity of a Video Blade, the meeting may still fail if the desktop meeting occupies the Video Blade DSP resource in such a way that only whole ports are left available for the high rate meeting, and only 1 or 2 ports are available. This is a rare event.
* When dialing into a Video Administration meeting, the MCU meeting ID is displayed on the endpoint monitor.
* Terminals in restricted mode (56K) cannot access a gateway in unrestricted mode (64 Kbps).
* Adjusting the server clock disrupts the status of any recurring meetings that are scheduled.
* Upload of a high definition continuous presence MCU service to another MCU that does not support high definition continuous presence is not supported.
* MCU features, such as encryption and Qualivision, function properly but are not displayed as meeting type information or in the in-meeting control user interface.
* When working with an MCU service that supports presentation view, the presentation view should be the second layout in the service definition on the MCU.
* When inviting multiple endpoints to a meeting, by default Video Administration sends the invitation request to the MCU for each endpoint in sequence without any delay between the requests. Sometimes this can cause a timing issue with the MCU so that not all the endpoints can connect successfully. To resolve this issue, go to Configuration Tool > General Settings and set the Command Delay value to 100 to 200 milliseconds.
* '''For Release 5.4(2.103) only:''' Cisco Unified MeetingPlace deployments do not support the use of the “Reserve Port on EMP for dynamic cascading” parameter on the Scheduling Settings tab of the Video Admin Configuration Tool.

Cisco Unified MeetingPlace, Release 6.x -- Compatibility Matrix

2009-12-13T21:55:25Z

Dunn: Adding notes to MPOL for 6.0MR5

[[Cisco Unified MeetingPlace, Release 6.x]]

'''Custom Search:'''
<html>
<form action="http://www.google.com/cse" id="cse-search-box">
<div>
<input type="hidden" name="cx" value="007771824002417948961:q0te3ntvco0" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<input type="submit" name="sa" value="Search" />
</div>
</form>

<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
</html>

This page lists the latest supported version combinations of Cisco Unified MeetingPlace Audio Server and the other Cisco Unified MeetingPlace components used in Release 6.0.

== Upgrade Information ==

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 on this page.

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 the Audio Server: Cisco Unified MeetingPlace MeetingTime, Cisco Unified MeetingPlace Web Conferencing, Network Backup Gateway, H.323/SIP IP 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]].

== Compatibility Matrix ==

===== Table: Supported Version Combinations for Audio Server Release 6.0 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(5.11)'''

Also known as

Maintenance Release 5 (MR5)

Released July 15, 2009
|
Directory Services 6.0(530.0)
|
July 15, 2009
|-
|
Gateway SIM 6.0(5.22)
|
July 15, 2009
|-
|
H.323/SIP IP Gateway 6.0(5.7)
|
July 15, 2009
|-
|
Jabber Integration 6.0(600.0)
|
July 15, 2009
|-
|
Language Pack 6.0(2.13)
|
January 31, 2008
|-
|
Lotus Notes Integration 6.0(532.0)
|
July 15, 2009
|-
|
MCU 5.7(0.0.21)
|
July 15, 2009
|-
|
EMP 5.7(0.0.4)
|
July 15, 2009
|-
|
MeetingTime 6.0(5.4)
|
July 15, 2009
|-
|
Network Backup Gateway 6.0(5.3)
|
July 15, 2009
|-
|
Microsoft Office Communicator (MOC/LCS 2005) Integration 6.0(504.0)
|
July 15, 2009
|-
|
Outlook Integration 6.0(547.0)

''Note: MPOL 6.0(547.0) is available as a full installer package or an upgrade installer to 6.0(537.0), and are available by contacting Cisco TAC.''
|
December 8, 2009
|-
|
Password Utility Patch 1.0

''Note: Optional. This feature is intended for Government use and is only available by contacting Cisco TAC.''
|
June 2, 2008
|-
|
SMTP E-Mail Gateway 6.0(532.0)
|
July 15, 2009
|-
|
Video Administration 5.6(2.104)
|
July 15, 2009
|-
|
Video Integration 6.0(5.5)
|
July 15, 2009
|-
|
Web Conferencing:
* 6.0(639.0)
* 5.4(156.2)

''Note: Release 5.4(156.2) is a hot fix and is only available by contacting Cisco TAC.''
|
* July 15, 2009
* September 7, 2007
|-
|
Cisco IP Telephony OS
* Windows 2003.1.4 through 2003.1.5 supported
* Windows 2003.1.4asr12 & Windows 2003.1.5sr2 are the latest service releases.
* OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
* Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
* Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm
|
October 20, 2009
|-
|<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.
|-
|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(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 IP 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)

''Note: Release 5.4(109.0) requires Web Conferencing Release 5.4.(156.2).''
|
* 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
|-
|

Microsoft Office Communicator Integration 6.0(201.0)
(MOC/LCS 2005)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(407.0)
* 5.4(165.0)

''Note: Release 5.4(165.0) requires Web Conferencing Release 5.4(156.2).''
|

* December 17, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0

''Note: Optional. This feature is intended for Government use and is only available by contacting Cisco TAC.''
|

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)

''Note: Release 5.4(156.2) is a hot fix and is only available by contacting Cisco TAC.''
|

* December 17, 2008
* September 7, 2007
|-
|
Cisco IP Telephony OS
* Windows 2003.1.4 through 2003.1.5 supported
* Windows 2003.1.4asr12 & Windows 2003.1.5sr2 are the latest service releases.
* OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
* Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
* Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm
|
October 20, 2009
|-
|<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.
|-
|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)

''Note: Release 5.4(109.0) requires Web Conferencing Release 5.4.(156.2).''
|
* 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
|-
|

Microsoft Office Communicator Integration 6.0(201.0)
(MOC/LCS 2005)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(307.0)
* 5.4(165.0)

''Note: Release 5.4(165.0) requires Web Conferencing Release 5.4(156.2).''

|

* June 2, 2008
* December 21, 2007
|-
|

Password Utility Patch 1.0

''Note: Optional. This feature is intended for Government use and is only available by contacting Cisco TAC.''
|

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)

''Note: Release 5.4(156.2) is a hot fix and is only available by contacting Cisco TAC.''
|

* June 2, 2008
* September 7, 2007
|-
|
Cisco IP Telephony OS
* Windows 2003.1.2a through 2003.1.5 supported
* OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
* Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
* Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm
|
October 20, 2009
|-
|<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.
|-
|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)

''Note: Release 5.4(109.0) requires Web Conferencing Release 5.4.(156.2).''
|

* 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
|-
|

Microsoft Office Communicator Integration 6.0(201.0)
(MOC/LCS 2005)
|

January 31, 2008
|-
|

Outlook Integration:
* 6.0(214.0)
* 5.4(165.0)

''Note: Release 5.4(165.0) requires Web Conferencing Release 5.4(156.2).''

|

* 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)

''Note: Release 5.4(156.2) is a hot fix and is only available by contacting Cisco TAC.''
|

* January 31, 2008
* September 7, 2007
|-
|
Cisco IP Telephony OS
* Windows 2003.1.2a through 2003.1.5 supported
* OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
* Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
* Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm
|
October 20, 2009
|-
|<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.

|-
|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
|-
|

Microsoft Office Communicator Integration 6.0(102.0)
(MOC/LCS 2005)
|

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)
''Note: Release 5.4(156.2) is a hot fix and is only available by contacting Cisco TAC.''

|

* September 7, 2007
* September 7, 2007
|-
|
Cisco IP Telephony OS
* Windows 2003.1.2a through 2003.1.5 supported
* OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
* Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
* Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm
|
October 20, 2009
|-
|<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
|-
|

Microsoft Office Communicator Integration 6.0(11.0)
(MOC/LCS 2005)
|

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)

''Note: Release 5.4(156.2) is a hot fix and is only available by contacting Cisco TAC.''
|

* May 31, 2007
* September 7, 2007
|-
|
Cisco IP Telephony OS
* Windows 2003.1.2a through 2003.1.5 supported
* OS base for MP Web Conferencing, Video Administration, Directory Service on MCS servers
* Upgrades available via Cisco.com Downloads found under: Voice and Unified Communications > Cisco Unified Communications Manager Version 4.3 > Voice Applications OS and BIOS Updates
* Cisco IP Telephony Operating System, SQL Server, Security Update Information located here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/os_srv_sec/osbios.htm
|
October 20, 2009
|-
|<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.
|-
|}