Troubleshooting Cisco Unity Connection Deployments

Troubleshooting Installation Issues

If you receive an error during installation of Cisco Unity Connection, do the following:

Troubleshooting Upgrade Issues

Following are the issues that you might face while upgrading from one version of Unity Connection to another:

Troubleshooting Locale Issues After Upgrade

If you face any problem related to locale after upgrade, do the following

Procedure


Step 1

Check if the locale is installed or not using the show cuc locales CLI command.

Step 2

In Cisco Unity Connection Administration, navigate to Users > Users and select a user for whom locale is not displaying correctly.

Step 3

Verify that the correct language is selected from the language drop-down list.

Step 4

Click Save to apply the settings.


Troubleshooting SELinux Issues

Procedure


Step 1

To check the status of SELinux on Unity Connection server, run the Command Line Interface (CLI) command utils os secure status.

Step 2

If SELinux is in Enforcing mode, run the CLI command utils os secure permissive to put the Unity Connection server in Permissive mode.

Step 3

Try to reproduce the symptom with SELinux in permissive mode. If the symptom is reproducible, it is not caused by SELinux.

Step 4

If the symptom is not reproducible, do the following steps to gather logs before you contact Cisco TAC:

  1. Create your test directory on sftp server to save the audit log diagnostic file at that location.

  2. Put Unity Connection server in Enforcing mode by running the CLI command utils os secure enforce.

  3. Try to create the symptom again.

  4. Create the audit logs diagnostic file by running the CLI command utils create report security. This command creates a diagnostic file “security-diagnostics.tar.gz”. Copy the diagnostic file to sftp directory created in step 4(a) by running the CLI command file get activelog syslog/security-diagnostics.tar.gz.

Step 5

Contact Cisco TAC.