So, I am breaking the use cases out into individual entries. Who knows, over time this may become another series. For now, let's focus on one of the CentOS recovery use cases: Fixing Errors with Custom Announcement Uploads.
In this blog entry, we are (yet again) working around a software defect. I have seen the issue in UCM version 8.6 and 9.1(2). The problem arises when you are attempting to upload a custom announcement for use with the Hunt List queuing feature. When uploading the prompt, you receive the error "The .wav file could not be translated by the Audio Translator Application".
The software defect is CSCua90744.
The Fix
As with the article covering TFTP customer ring tones, the root cause of this problem is permissions. I used the procedures outlined here to fix a UCM 9.1(2) system in my lab. I compared file permissions on a UCM 10.0 cluster (which had no issue uploading the prompt) with the UCM 9.1(2) system (that exhibited the issue). After applying the fix, I was able to upload the custom announcements.
From what I could determine, the issue is the permissions setting on the "CustomAnn" directory:
Broken Example:
ls -ld /common/log/taos-log-a/cm/tftpdata/
drwxr-xr-x 2 root root 4096 Mar 11 2014 CustomAnn/
Working Example:
ls -ld /common/log/taos-log-a/cm/tftpdata/
drwxr-xr-- 2 tomcat ccmbase 4096 Mar 11 2014 CustomAnn/
As you can see, there are three issues:
You will need to repeat this process on the Publisher node and on all Music On Hold nodes in your cluster.
The software defect is CSCua90744.
The Fix
As with the article covering TFTP customer ring tones, the root cause of this problem is permissions. I used the procedures outlined here to fix a UCM 9.1(2) system in my lab. I compared file permissions on a UCM 10.0 cluster (which had no issue uploading the prompt) with the UCM 9.1(2) system (that exhibited the issue). After applying the fix, I was able to upload the custom announcements.
From what I could determine, the issue is the permissions setting on the "CustomAnn" directory:
Broken Example:
ls -ld /common/log/taos-log-a/cm/tftpdata/
drwxr-xr-x 2 root root 4096 Mar 11 2014 CustomAnn/
Working Example:
ls -ld /common/log/taos-log-a/cm/tftpdata/
drwxr-xr-- 2 tomcat ccmbase 4096 Mar 11 2014 CustomAnn/
As you can see, there are three issues:
- The owner (user) is wrong
- The group owner is wrong
- The user/group permissions are wrong
The Procedure
The CentOS boot process is discussed in a separate blog entry (read that first). To fix the custom announcement upload issue, do the following after booting into CentOS:
1. Go to the affected directory using the command: cd /common/log/taos-log-a/cm/tftpdata
2. Change the ownership attribute using the command:
chown tomcat:ccmbase CustomAnn
3. Change the permissions using the command:
chmod 754 CustomAnn
4. Check your work:
ls -ld */
4. Type exit at the prompt to reboot the VM.
5. Disconnect the CentOS ISO from your VM guest.
1. Go to the affected directory using the command: cd /common/log/taos-log-a/cm/tftpdata
2. Change the ownership attribute using the command:
chown tomcat:ccmbase CustomAnn
3. Change the permissions using the command:
chmod 754 CustomAnn
4. Check your work:
ls -ld */
4. Type exit at the prompt to reboot the VM.
5. Disconnect the CentOS ISO from your VM guest.
You will need to repeat this process on the Publisher node and on all Music On Hold nodes in your cluster.
Thanks for reading. If you have time, post a comment!
Thanks for that post.
ReplyDeleteWe have the same issue in 10.5