Local Filesystem Applicable for Unity Connection In the Directory field, enter the path of the folder that contains the upgrade file.
In the Server field, enter the server name or IP address. In the User Name field, enter the alias that is used to sign in to the remote server. In the User Password field, enter the password that is used to sign in to the remote server. In the Transfer Protocol field, select the applicable transfer protocol. Select the upgrade version that you want to install and select Next.
The upgrade file is copied to the hard disk of the Unity Connection server. When the file is copied, a screen displaying the checksum value appears. Warning: Another session is installing software, click Assume Control to take over the installation. To continue monitoring the upgrade, select Assume Control.
During the initial phase of upgrade, the Installation Log text box in Cisco Unified Operating System Administration is updated with the information on the progress of the upgrade. To confirm the completion of upgrade, open the console of the Unity Connection server and make sure that a message indicating the completion of upgrade appears on the screen along with the login prompt.
The upgraded Unity Connection version is in the inactive partition and old version is in the active partition. This command should display the message for successful upgrade along with the upgraded version.
After completing the upgrade process, you need to manually switch over to the upgraded version of Unity Connection. For a single Unity Connection server, you can select either manual switch version or automatic switch version. You can perform the switch version running the CLI command utils system switch-version. The system automatically reboots after the switch version. If you select not to automatically switch to the upgraded partition at the end of the upgrade, do the following procedure when you are ready to switch partitions.
From the Settings menu, select Version. On the Version Settings page, select Switch Versions , to start the following activities:. Data from the active partition is copied to the inactive partition. Note that the messages are stored in a common partition, therefore they are not copied. The Unity Connection server restarts and switches to the newer version. Copy the Cisco Option Package. If you are upgrading the subscriber server in a Unity Connection cluster, type the following address to access Cisco Unified Operating System Administration:.
In the Directory field, enter the path to the folder that contains the. If the. For example, if the. In the Transfer Protocol field, select the applicable transfer protocol and select Next. When the file is copied, a screen displays the checksum value. During the upgrade, the value of the Status field is Running. When the upgrade process is complete, the value of the Status field changes to Complete. After upgrading the Unity Connection version, you can rollback to the software version that was running before the upgrade by switching to the software version on inactive partition.
You can revert a single Unity Connection server or a cluster to the version on inactive partition. To rollback a Unity Connection cluster, you should rollback both the servers, first the publisher and then the subscriber. After the successful rollback of both the publisher and subscriber servers, reset the replication between the two servers running the following CLI commands:.
Stop the replication on subscriber server with the CLI command utils dbreplication stop. Stop the replication on publisher server with the CLI command utils dbreplication stop.
Reset the replication running the CLI command utils dbreplication reset all on the publisher server. After the reset of replication between the two servers, check the cluster status running the CLI command show cuc cluster status utils system restart on both publisher and subscriber.
From the Settings menu, select Version and the Version Settings window displays. Select the Switch Versions option. After you confirm that you want to restart the system, the system restarts that might take up to 15 minutes.
Follow the given steps to confirm that the switch version is successful:. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 2. Updated: September 9, Chapter: Upgrading Cisco Unity Connection. The following are the two ways to switch to the new version: Automatic Switching: Allows you to automatically switch to the new version of Unity Connection as part of the upgrade process.
Note You can install or upgrade Unity Connection Table 1. Refresh Upgrade RU 8. You need the following COP files before performing this upgrade: ciscocm. Level 2 L2 You need the following COP file before performing this upgrade: ciscocm. Install with Data Import Examples of supported paths: Note After the upgrade, you may need to reinstall the locale depending on the source and the target version.
Status of Unity Connection Cluster During an Upgrade When a Unity Connection cluster is upgraded, the publisher server is completely disabled for the entire duration of upgrade but the subscriber server continues to provide services to users and callers. However, the performance of the cluster is affected in the following ways: If the phone system is routing calls to the subscriber server, outside callers and Unity Connection users can leave voice messages but the messages are not immediately delivered to user mailboxes.
Duration of Upgrade Under ideal network conditions, an upgrade process takes approximately two hours to complete on each server.
Tip You can reduce the duration of upgrade process by asking users to permanently delete items in the deleted items folder before starting the upgrade. The choice you make determines which Exchange mailboxes Unity Connection can access: If you select a specific Exchange client access server, Unity Connection can access all Exchange mailboxes in the Exchange organization, but cannot access Exchange mailboxes or Exchange mailboxes.
See the below section to grant permissions to the applicable Exchange server: Granting Permissions for Exchange , Exchange or Exchange Note If you want to select a specific Exchange server when you add a unified messaging service, you may need to add more than one unified messaging service to allow Unity Connection to access all mailboxes in the Exchange organization.
Table 1 explains when you need to add more than one unified messaging service. Table 1. One for Office server that you want Unity Connection to be able to access. This service can also access Exchange mailboxes. When Unity Connection cannot detect the new mailbox, you must manually update unified messaging services or unified messaging accounts: If you moved all the Exchange mailboxes accessed by a unified messaging service: Update the unified messaging service to access a different Exchange server.
Table 2. Ensure that you have sufficient licenses for the voicemail users: Navigate to Cisco Unity Connection Administration, expand System Settings and select Licenses. Step 2 Create an Active Directory account for unified messaging users to communicate with Exchange , Exchange or Exchange Step 3 Decide whether you want Unity Connection to be able to search for and communicate with different Exchange , Exchange or Exchange server, or you want Unity Connection to communicate with a specific Exchange , Exchange or Exchange server in case the hostname or the IP Address of the specific server is known.
Step 5 Selected configurations only : In either or both of the following conditions, you need to upload SSL certificates on the Unity Connection server to encrypt communication between Unity Connection and Exchange and between Unity Connection and Active Directory: If you have configured Exchange to use HTTPS in Step 3 b , configure unified messaging services to validate certificates for Exchange servers.
Caution When you allow Unity Connection to search for and communicate with different Exchange servers, Unity Connection communicates with Active Directory servers using Basic authentication. By default, the username and password of the unified messaging services account and all other communication between the Unity Connection and Active Directory servers is sent in clear text.
Step 6 Configure one or more unified messaging services on Unity Connection. Step 7 Update the settings for unified messaging users.
Step 8 Configure one or more unified messaging accounts to link the Unity Connection users with the mail server with which they are communicating. Step 9 Test unified messaging configuration. Task List for Configuring Unified Messaging with Office Procedure Step 1 Make sure that you have met the prerequisites before configuring unified messaging.
Step 2 Create an Active Directory account to be used by Unity Connection unified messaging users to communicate with Office Step 3 Decide and select the type of authentication that you want Unity Connection to use to sign in to Office client access servers.
Step 4 Applicable only for OAuth2 web authentication mode Do the following steps for registering the application on Azure portal. Note It is recommended that for latest updates and link of Azure Portal, refer Microsoft updates. Click Delegated permissions and add below permissions in your application: Features Permissions Calendars Calendars. ReadWrite Contacts Contacts.
All Mail Mail. ReadWrite, Mail. Send On API permissions window, select Grant admin consent for Cisco Systems to provide grant admin consent for the requested permissions. Caution Repeat Steps 4 and 5 for the following: In case of multiple clusters , the above fields should be unique for each cluster configuration. Step 7 Synchronization threads configuration should be done based on latency between Unity Connection and Office server. Uploading certificates allows you to: Validate the certificates for Exchange Servers.
Note If Unity Connection server is being shared by tenants for voicemail service, then multiple Unified Messaging Service accounts are required.
Step 11 Update the settings for unified messaging users. Step 12 Test the unified messaging service. Uploading messages into Exchange mailboxes Tracking changes to messages in Exchange Updating messages with changes made in Unity Connection Deleting messages in Exchange when the messages are deleted in Unity Connection, and so on.
Note the following points while configuring Unified Messaging in active directory: Give the account a name that identifies it as the unified messaging services account for Unity Connection. Caution Some newer Exchange versions need mailbox for domain user account.
The key that is used to encrypt the password is accessible only with root access, and root access is available only with assistance from Cisco TAC. Granting Permissions Granting Permissions for Exchange , Exchange or Exchange Granting Permissions for Exchange , Exchange or Exchange Procedure Step 1 Sign in to a server on which Exchange Management Shell is installed using either an account that is a member of the Enterprise Admins group or an account that can grant permissions on Exchange objects in the configuration container.
Note When configuring unified messaging service account for Exchange , Exchange or Exchange you need to assign the Application Impersonation management role to the unified messaging service account. Step 3 Sign in to a server that has access to the same Exchange client servers that is accessed by the Unity Connection.
Caution The unified messaging services account must use the same type of authentication for EWS that you specified for autodiscover. Step 8 Repeat Step 5 through Step 7 for the other Exchange , Exchange or Exchange client access servers that Unity Connection can access. Configuring Paged View Functionality in Unity Connection for Exchange , Exchange or Exchange If any unified user Exchange mailboxes have more than messages including voicemails and receipts, then enable the EWS paged view search functionality in Unity Connection server.
MbxSynchUsePaging' parameter is set to 1. Set-ExecutionPolicy Unrestricted Step 2 On a Windows PowerShell endpoint, run the following command and enter the Office administrator account credentials for authentication in the popup window. Caution If you have activated the Active Directory Synchronization feature and migrating from local Exchange server to Office , then the further user management is done through the on-premises Active Directory Services and it gets synchronized with Office automatically.
You must make sure the Application Impersonation Management role is given to your Office server. Creating a Unified Messaging Service to Access Mail Server Do the following procedure to create one or more unified messaging services in Unity Connection to access the supported mail server.
Note If you configured the supported mail server to use HTTPS, you need to configure the unified messaging services to validate certificates for the mail servers.
You need to upload certificates from the certification authority that issued the SSL certificates for mail server to both Tomcat-trust and Unity Connection-trust locations. Creating Unified Messaging Services in Unity Connection Creating Unified Messaging Services in Unity Connection If you are configuring Unity Connection to communicate with individual mail servers, you need to configure unified messaging services for each mail server.
Uploading CA Public Certificates for Exchange and Active Directory At the time of creating unified messaging services, if you selected to validate certificates for Exchange servers or for Active Directory domain controllers DCs , you must upload the public certificates from the certification authority CA that signed the certificates on the Exchange servers and DCs.
If you selected the option to validate certificates for Exchange servers, and if SSL certificates are not already installed on all of the following servers: Get and install certificates: Exchange , Exchange or Exchange client access servers.
Step 5 In the Certificate dialog box, select the Details tab. Step 6 On the Details tab, select Copy to File. Step 9 On the File to Export page, specify the full path of the public certificate, including a location that is accessible to the Unity Connection server, and a file name.
Step 10 Select Next. Step 12 Select OK three times to close a message box and two dialog boxes. Step 14 If you issued SSL certificates for all of the servers listed in Step 1 using the same installation of Microsoft Certificate Services, you are finished with this procedure.
Step 3 In the Certificate Name list, select tomcat-trust. Step 4 Optional Enter a description in the Description field and select Browse. Step 5 Browse to the location where you saved the public certificates in. Step 6 Select Upload File. Step 8 If you have public certificates from more than one certification authority, repeat Step 2 through Step 7 for the remaining certificates.
Uploading Certificates for Office and Cisco Unity Connection At the time of creating unified messaging services, if you select "Validate Certificates for Exchange Servers" for Office , you must perform the following steps to upload Office root certificate to the tomcat-trust of Cisco Unity Connection.
Step 4 In the Certificate Name list, select tomcat-trust. Step 5 Optional Enter a description in the Description field and select Browse Step 6 Browse to the location where you saved the Office root certificate, and select the certificate.
Step 7 Select Upload File. Step 3 You must configure message aging or message quotas. Step 5 Select Save. Unified messaging accounts are separate objects from user accounts: When you create a user account, Unity Connection does not automatically create a unified messaging account for that user.
Step 3 To check the configuration for the user, select Test. Step 2 To sort by the values in a column in ascending order, select the heading for the column.
Step 3 View the following settings: To display the Unified Messaging Accounts page for an account, select the icon or the value of the Alias column in the applicable row.
Testing System Configuration and Unified Messaging with Exchange and Unity Connection You can run a Unity Connection system test that includes tests of the unified messaging configuration and that provides summary data on configuration problems, if any, for example, the number of accounts assigned to a specified unified messaging service that has configuration problems.
Do the following to check the system configuration and unified messaging configuration: Procedure Step 1 In Cisco Unity Connection Administration, expand Tools and select Task Management. Step 3 Select Refresh to display links to the latest results. Step 4 Review the results, resolve problems, if any, and re-run the Check System Configuration task until no more problems are found.
Testing Access to Calendars for Unity Connection If you configured Unity Connection to calendars, do the following procedure to test the access to calendars. Procedure Step 1 Sign in to Outlook. Step 2 On the Go menu, select Calendar. Step 4 Enter values in the required fields to schedule a new meeting for the current time and invite a user who has an account on Unity Connection.
Step 5 Sign in to the Unity Connection mailbox of the user that you invited to the Outlook meeting in Step 4. Step 6 If the user account is configured for speech access, say Play Meetings.
Note Microsoft Exchange server can be used as a smart host. Packet Sniffer Custom sensor. PerfCounter Custom sensor. Ping sensor. Ping Jitter sensor. POP3 sensor. Port sensor. Port Range sensor. PostgreSQL sensor. Probe Health sensor. Python Script Advanced sensor. RDP Remote Desktop sensor. REST Custom sensor. Sensor Factory sensor. Share Disk Free sensor.
SIP Options Ping sensor. SMTP sensor. SNMP Custom sensor. SNMP Library sensor. SNMP Memory sensor. SNMP Printer sensor. SNMP Traffic sensor. SNTP sensor. Soffico Orchestra Channel Health sensor. SSH Disk Free sensor. SSH Load Average sensor. SSH Meminfo sensor. SSH Remote Ping sensor. SSH Script sensor. SSH Script Advanced sensor. SSL Certificate sensor. SSL Security Check sensor.
Syslog Receiver sensor. System Health sensor. TFTP sensor. Traceroute Hop Count sensor. Veeam Backup Job Status sensor. Veeam Backup Job Status Advanced sensor. Windows CPU Load sensor. Windows IIS 6. Windows IIS Application sensor. Windows Network Card sensor. Windows Pagefile sensor.
Windows Print Queue sensor. Windows Process sensor. Windows System Uptime sensor. Windows Updates Status PowerShell sensor.
WMI Battery sensor. WMI Custom sensor. WMI Custom String sensor. WMI Disk Health sensor. WMI Event Log sensor. WMI Exchange Server sensor. WMI File sensor. WMI Memory sensor. WMI Remote Ping sensor. WMI Security Center sensor. WMI Service sensor. WMI Share sensor.
WMI Storage Pool sensor. WMI Volume sensor. WSUS Statistics sensor. Zoom Service Status sensor. What It Monitors. Response time and response code of the target server. Response times of the target server. Response time of the target server using TCP ping. Loading time of a web page or element. Ping time and packet loss. Time until a request to a port is accepted.
Traffic on a device via SNMP. Bandwidth usage and traffic of a network interface via WMI or Windows performance counters. A Windows DC for replication errors. Changes to file content and file time stamp.
A folder using SMB. An email server using IMAP. Status of all backup job runs on the Veeam Backup Enterprise Manager in the last 24 hours. Status of a specific backup job that runs on the Veeam Backup Enterprise Manager. Traffic data from a jFlow v5 compatible device. Traffic data from a NetFlow v5 compatible device. Compatibility Matrix for Cisco Unity Connection. We have restructured this guide to make it more user friendly and removed duplicate content. Contains the supported version combinations for Unity Connection and the software installed on user workstations.
Describes the guides that make up the Unity Connection documentation set. Provides licensing information for open-source software included in Unity Connection. Contains information on new and changed requirements and support, new and changed functionality, limitations and restrictions, caveats, and documentation updates.
Contains information on new and changed requirements and support, new and changed functionality, limitations and restrictions, installation and upgrade instructions, caveats, and documentation updates for version 8. Contains information on new and changed requirements and support, new and changed functionality, limitations and restrictions, installation and upgrade instructions, caveats, and documentation updates for versions 8. Contains information on new and changed requirements and support, new and changed functionality, limitations and restrictions, installation and upgrade instructions, caveats, and documentation updates.
Provides information and procedures for configuring Visual Voicemail within a Cisco Unified Communications system. Contains information on installation process and scenarios, taking the backup of the database, locales and license installation, and the complete upgrade process. Lists the requirements for installing the Unity Connection system; also lists supported versions of required and optional software.
0コメント