Cisco
Unity 7.0(2) Engineering Special 31 Readme
New and Changed Requirements and Support
Support for Active Directory 2008
Before Installing the ES and Patches
Checking the Consistency of the Cisco Unity
Database, and Backing Up Cisco Unity Data
Installing the ES and Required Patches Without
Failover
Installing the ES and Required Patches With
Failover Configured
Fixing Problems on Specific Configurations
Exchange 2007:
CU7.0(2)_Exchange2003-KB957593-x86-ENU.exe
Exchange 2007: UseProfileServerNameForMDB
Registry Key
Changing the DTMF Key Used to Disable
Message Notifications
After Installing the ES and Patches
Uninstalling an Engineering Special
This document contains information on installing software, new and changed support, new and changed functionality, and resolved defects for Cisco Unity 7.0(2) Engineering Special (ES) 31.
ES 31 is a cumulative Engineering Special. In addition to the defects resolved in ES 31, the defects fixed in the following Engineering Specials and Patches have been rolled-up into ES 31:
· Engineering Specials: 2, 3, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 28, 29, and 30.
· Patches: CU7.0(2)_TestWritableDomainController.exe, CU7.0(2)_Configurable_DTMF_Key.exe, and CU7.0(2)_Exchange2003-KB957593-x86-ENU.exe.
A complete list of defects resolved in ES 31 can be found in the Resolved Defects section.
ES 31 requires Cisco Unity 7.0(2). On systems using failover, ES 31 must be installed on both the primary and secondary Cisco Unity servers. You do not need to remove previous Engineering Specials before installing ES 31.
This section contains information about new and changed requirements and support introduced in an Engineering Special subsequent to the Cisco Unity 7.0(2) release.
Cisco Unity 7.0 ES 7 and later supports the following:
· The Cisco Unity server can be a member server in an Active Directory 2008 domain.
· The Active Directory objects for Cisco Unity subscribers, contacts, distribution lists, or locations can be created in an Active Directory 2008 domain.
Although optional, we recommend that you do the procedures in this section before installing the ES.
Before you install the ES, we recommend that you run the DbWalker utility to check the consistency of the Cisco Unity database. Running DbWalker fixes most minor errors automatically and flags any major errors.
On a system with a few hundred subscribers, running DbWalker takes only a few minutes. However, on a large system, running DbWalker may take several hours. The duration depends on the speed of the processor, the amount of RAM in the server, the number of calls that Cisco Unity is taking, and other variables.
We also recommend that you back up Cisco Unity data by using the Disaster Recovery Backup tool. Running the tool takes only a few minutes, and having a DiRT backup allows you to restore Cisco Unity data, if necessary.
To Check the Consistency of the Cisco Unity Database
If Cisco Unity failover is configured, do this procedure on the primary server.
1. On the Cisco Unity server, install the latest version of DbWalker, if it is not already installed.
2. Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
To Back Up Cisco Unity Data
If you choose to back up messages as well as Cisco Unity data in the next procedure, backing up takes longer, the size of the backup is significantly larger, and the account with which you log on to Windows requires additional permissions. Refer to DiRT Help for detailed information.
If Cisco Unity failover is configured, do this procedure on the secondary server.
1. On the Cisco Unity server, install the latest versions of DiRT Backup and Restore, if the tools are not already installed.
2. Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
CAUTION! Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
3. If the Cisco Unity server has an ES installed on it, we recommend that you save the self-extracting file containing the currently installed ES with the DiRT backup file. If you ever need to do a DiRT Restore on another server, we recommend that you install the exact same ES that was installed when you did the backup. ESes may include a database schema change, and if you back up a system that includes a schema change and try to restore to a system without the schema change, the restore will fail or may result in an unstable system. Storing the ES self-extracting file with the DiRT backup file serves as a reminder to first install the ES before doing the DiRT Restore. Additionally, it saves you time from having to download the ES again. If you are unsure if an ES is installed on the server do the following procedure:
a. On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.
b. In the left pane, under Reporting Tools, double-click Gather Unity System Info.
This section contains instructions for installing the ES and required patches on a Cisco Unity server that does not have failover configured. We recommend that you install the ES when phone traffic is light, for example, after business hours.
1. Download the file CU7.02ES31RollUp.exe from cisco.com.
2. Disable and stop antivirus services and the Cisco Security Agent service.
3. Create a folder called CU7.02ES31RollUp ES31 on the Cisco Unity server, and copy the file CU7.02ES31RollUp.exe to the folder.
4. Double-click CU7.02ES31RollUp.exe and extract the following files to the ES31 folder:
· CU7.02ES31_Readme.htm—Help file containing these instructions
· CU7.0(2)_ES31.exe—Cumulative Engineering Special
· CU7.0(2)_TestWritableDomainController.exe—Patch
· CU7.0(2)_Configurable_DTMF_Key.exe—Patch
· CU7.0(2)_Exchange2003-KB957593-x86-ENU.exe—Patch
5. Double-click CU7.0(2)_ES31.exe and follow the on-screen instructions to install the Engineering Special.
6. Reboot the Cisco Unity server. Make sure that Cisco Unity is running before continuing with the next step.
7. Stop the Tomcat service from the Service Control Manager.
8. Delete everything in the \CommServer\cscoserv\Tomcat\work\Standalone\localhost\ciscopca directory.
9. Restart the Tomcat service from the Service Control Manager.
10. Install the TestWritableDomainController.exe patch.
The TestWritableDomainController.exe patch allows Cisco Unity to support Active Directory 2008. The TestWritableDomainController.exe patch, which has been required since Cisco Unity 7.0(2) Engineering Special (ES) 4, must be installed regardless of the Active Directory version and message store—IBM Lotus Domino or Microsoft Exchange—that Cisco Unity uses. If ES 4 or later has been installed, the TestWritableDomainController.exe patch should already be installed. If you are unsure whether the patch is installed, or if ES 31 is the first ES to be installed on the Cisco Unity server, follow the instructions below to install the TestWritableDomainController.exe patch. Reinstalling the patch will not affect Cisco Unity. (Applies to defect CSCsr90209.)
To Install
the Patch
a. Double-click the file CU7.0(2)_TestWritableDomainController.exe.
b. Specify the root of the Commserver folder in the Unzip to Folder field and click Unzip. The files will be automatically extracted to the appropriate folders within the Commserver folder.
11. Install the CU7.0(2)_Configurable_DTMF_Key.exe patch.
The CU7.0(2)_Configurable_DTMF_Key.exe patch introduces a feature enhancement that allows subscribers to configure the DTMF key used to disable message notifications to a phone. The CU7.0(2)_Configurable_DTMF_Key.exe patch, which has been required since Cisco Unity 7.0(2) ES 1, must be installed even if you will not be enabling the feature enhancement provided in the patch. If ES 1 or later has been installed, the CU7.0(2)_Configurable_DTMF_Key.exe patch should already be installed. If you are unsure whether the patch is installed, or if ES 31 is the first ES to be installed on the Cisco Unity server, follow the instructions below to install the CU7.0(2)_Configurable_DTMF_Key.exe patch. Reinstalling the patch will not affect Cisco Unity. (Applies to defect CSCso65982.)
To Install
the Patch
a. Double-click the file CU7.0(2)_Configurable_DTMF_Key.exe.
b. Specify the root of the Commserver folder in the Unzip to Folder field and click Unzip. The files will be automatically extracted to the appropriate folders within the Commserver folder.
12. Re-enable antivirus services and the Cisco Security Agent service.
13. Run some basic tests to make sure that Cisco Unity is functioning properly, for example:
· Leave a few messages and then listen to them. Make sure that the message waiting indicator (MWI) goes on/off as expected.
· Log on to the Cisco Unity Administrator.
· Log on to the Cisco Unity Assistant.
· Check the Event Viewer for warnings or errors.
This section has instructions for installing the ES when the Cisco Unity servers are configured for failover. Although these steps minimize the time that Cisco Unity is unable to take calls, we recommend that you install the ES when phone traffic is light, for example, after business hours.
The following steps assume that the primary is the active server, and the secondary is the inactive server. The general approach to the procedure is:
· Install the ES and patches on the secondary (inactive) server
· Failover to the secondary (now the primary is inactive)
· Install the ES and patches on the primary server
· Failback
1. Download the file CU7.02ES31RollUp.exe from cisco.com.
Continue with the ES installation on the secondary (inactive) Cisco Unity server.
2. Disable and stop antivirus services and the Cisco Security Agent service.
3. Create a folder called ES31 on the Cisco Unity server, and copy the file CU7.02ES31RollUp.exe to the folder.
4. Double-click CU7.02ES31RollUp.exe and extract the following files to the ES31 folder:
· CU7.02ES31_Readme.htm—Help file containing instructions for installing ES 31 and the patches
· CU7.0(2)_ES31.exe—Cumulative Engineering Special
· CU7.0(2)_TestWritableDomainController.exe—Patch
· CU7.0(2)_Configurable_DTMF_Key.exe—Patch
· CU7.0(2)_Exchange2003-KB957593-x86-ENU.exe—Patch
5. Double-click CU7.0(2)_ES31.exe and follow the on-screen instructions to install the Engineering Special.
6. Reboot the Cisco Unity server. Make sure that Cisco Unity is running before continuing with the next step.
7. Stop the Tomcat service from the Service Control Manager.
8. Delete everything in the \CommServer\cscoserv\Tomcat\work\Standalone\localhost\ciscopca directory.
9. Restart the Tomcat service from the Service Control Manager.
10. Install the TestWritableDomainController.exe patch.
The TestWritableDomainController.exe patch allows Cisco Unity to support Active Directory 2008. The TestWritableDomainController.exe patch, which has been required since Cisco Unity 7.0(2) Engineering Special (ES) 4, must be installed regardless of the Active Directory version and message store—IBM Lotus Domino or Microsoft Exchange—that Cisco Unity uses. If ES 4 or later has been installed, the TestWritableDomainController.exe patch should already be installed. If you are unsure whether the patch is installed, or if ES 31 is the first ES to be installed on the Cisco Unity server, follow the instructions below to install the TestWritableDomainController.exe patch. Reinstalling the patch will not affect Cisco Unity. (Applies to defect CSCsr90209.)
To Install
the Patch
a. Double-click the file CU7.0(2)_TestWritableDomainController.exe.
b. Specify the root of the Commserver folder in the Unzip to Folder field and click Unzip. The files will be automatically extracted to the appropriate folders within the Commserver folder.
c. Close the WinZip Self-Extractor tool.
11. Install the CU7.0(2)_Configurable_DTMF_Key.exe patch.
The CU7.0(2)_Configurable_DTMF_Key.exe patch introduces a feature enhancement that allows subscribers to configure the DTMF key used to disable message notifications to a phone. The CU7.0(2)_Configurable_DTMF_Key.exe patch, which has been required since Cisco Unity 7.0(2) ES 1, must be installed even if you will not be enabling the feature enhancement provided in the patch. If ES 1 or later has been installed, the CU7.0(2)_Configurable_DTMF_Key.exe patch should already be installed. If you are unsure whether the patch is installed, or if ES 31 is the first ES to be installed on the Cisco Unity server, follow the instructions below to install the CU7.0(2)_Configurable_DTMF_Key.exe patch. Reinstalling the patch will not affect Cisco Unity. (Applies to defect CSCso65982.)
To Install
the Patch
a. Double-click the file CU7.0(2)_Configurable_DTMF_Key.exe.
b. Specify the root of the Commserver folder in the Unzip to Folder field and click Unzip. The files will be automatically extracted to the appropriate folders within the Commserver folder.
c. Close the WinZip Self-Extractor tool.
12. The ES installation is complete. Re-enable antivirus services and the Cisco Security Agent service.
13. If you have just installed the ES on the secondary server, do the following sub-steps. If you have just installed the ES on the primary server, skip to step 14.
a. On the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
b. Click Failover.
c. Click Yes. At this point, the secondary server is active, and the primary server is inactive.
d. Run some basic tests on the secondary server to make sure that Cisco Unity is functioning properly, for example:
· Leave a few messages and then listen to them. Make sure that the message waiting indicator (MWI) goes on/off as expected.
· Log on to the Cisco Unity Administrator.
· Log on to the Cisco Unity Assistant.
· Check the Event Viewer for warnings or errors.
e. If Cisco Unity is functioning normally on the secondary server, repeat steps 1 through 12 to install the ES on the primary server.
14. If you have just installed the ES on the primary server, do the following sub-steps:
a. On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
b. Click Failback.
c. Click Yes. At this point, the primary server is active, and the secondary server is inactive.
d. Run some basic tests on the primary server to make sure that Cisco Unity is functioning properly.
This section
contains steps to fix problems that happen only on certain configurations. Do
only the steps that are applicable for your configuration.
This Microsoft patch should be installed only on systems that have the Exchange 2003 System Management Tools installed, and that have Cisco Unity subscriber mailboxes homed on Microsoft Exchange 2007. The patch fixes a problem where Cisco Unity intermittently reports incorrect message counts to subscribers when they log on to Cisco Unity by phone. This patch has been included in cumulative Engineering Specials since Cisco Unity 7.0(2) ES 19. To determine if the patch has been previously installed, run Add/Remove Programs with the Show Updates check box checked and look for “KB957593.” Installation of this patch on the Cisco Unity server should be done during off-peak hours when the Microsoft Exchange servers are not busy. (Applies to defect CSCsi10964.)
To Install the
Patch
1. Double-click the CU7.0(2)_Exchange2003-KB957593-x86-ENU.exe file and follow the instructions to install the patch on the Cisco Unity server.
2.
Right-click the Cisco Unity taskbar icon to stop and
restart Cisco Unity.
NOTE: After the patch is installed,
all Microsoft Exchange servers where Cisco Unity subscriber mailboxes are homed
will experience a performance load when Cisco Unity is restarted. This is
attributed to rebuilding the search folders on those Microsoft Exchange
servers. A full rebuild of the search folders will only happen once. Customers
are advised to install this patch after hours.
3. If Cisco Unity failover is configured, the patch must be applied to both the primary and secondary servers.
Customers with Cisco Unity subscribers homed on Microsoft Exchange 2007 servers configured in a cluster where MWIs are not working properly should add a new registry key on the Cisco Unity server as follows. (Applies to defect CSCsu80743.)
Registry Key Location: [HKEY_LOCAL_MACHINE\Software\Active
Voice\ExchangeMonitor]
Registry Key Name: UseProfileServerNameForMDB
Registry Key Type: DWORD
Registry Key Values:
1 Enables the defect fix in CSCsu80743.
0 Default 7.0(2) behavior.
Additional Information: Cisco Unity must be restarted for the key to take effect. If Cisco Unity failover is configured, make the registry change on both the primary and the secondary servers because registry settings are not replicated.
This section contains descriptions of new features included in this ES and the steps to enable them.
When a Cisco Unity subscriber
receives a message notification to a phone, by default, the conversation
provides the opportunity to disable future notifications to the number called
by pressing the "1" key on the phone keypad. The conversation then
prompts the subscriber to sign in to listen to the new message. The CU7.0(2)_Configurable_DTMF_Key.exe
patch must be installed on the Cisco Unity server to use this feature. (Applies to defect CSCso65982.)
The procedures in this section describe:
· How to change the DTMF key that subscribers press to disable notifications to a phone, and the key that subscribers press during a notification to sign in to listen to the new message.
· How to change the DTMF keys back to the default values.
These changes are made system-wide and apply to all subscribers.
To Change
the DTMF Keys Used During Message Notifications to a
Phone
1. On the Cisco Unity server, browse to CommServer folder, and open the file ConfigureTUINotificationKeys.sql in Notepad.
2. Look
for the following:
-- Define the single DTMF key to assign to each
action here
Set @DisableNotificationKey = N'9'
Set @SignInKey = N'1'
3. To change the key used to disable message notifications to that phone, change the number assigned to DisableNotificationKey. Be sure that the number is in single quotes. For example, to change the key to 5:
Set @DisableNotificationKey = N'5'
4. To change the key used to sign in during a message notification, change the number assigned to SignInKey. Be sure that the number is in single quotes.
5. Save the changes and close Notepad.
6. Open a CMD window and change directories to the root of the Commserver folder. For example:
cd commserver
7. Run the TUINotificationKeys.bat batch file with the command line option "create". For example:
TUINotificationKeys.bat create
8. Right-click the Cisco Unity taskbar icon to stop and restart Cisco Unity.
To Reset the DTMF Keys Back to Default Values
1. Open a CMD window and change directories to the root of the Commserver folder.
2. Run the TUINotificationKeys.bat batch file with the command line option "remove". For example:
TUINotificationKeys.bat remove
3. Right-click the Cisco Unity taskbar icon to stop and restart Cisco Unity.
To retain the urgent setting on replies and forwarded messages on a per-subscriber basis, create a new registry key name based on the subscriber's alias in the registry.
Registry Key Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Conversations\1.0\RetainUrgent]
Registry Key Name: JSmith (This is
just an example. You will use the actual alias of a Cisco Unity subscriber.)
Registry Key Type: DWORD
Registry Key Values:
1 Retain urgent on reply only.
2 Retain urgent
on forward only.
3 Retain urgent
on both reply and forward.
0 Disabled
(Default behavior)
Additional Information: The change takes effect immediately; Cisco Unity does not need to be restarted. Only subscribers listed in this registry key will have access to this feature. Registry changes for this feature can be made while Cisco Unity is running. To disable the feature for a user, remove them from the registry. If Cisco Unity failover is configured, make the registry change on both the primary and the secondary servers because registry settings are not replicated. (Applies to defect CSCsv12679.)
After the ES and Patches have been installed, you may want to delete the installation files from the server to free up disk space.
If you plan to do a DiRT backup of the server, we recommend that you save the self-extracting file, CU7.02ES31RollUp.exe, with the DiRT backup file. If you ever need to do a DiRT Restore on another server, we recommend that you install the exact same ES that was installed when you did the backup. ESes may include a database schema change, and if you back up a system that includes a schema change and try to restore to a system without the schema change, the restore will fail or may result in an unstable system. Storing the ES self-extracting file with the DiRT backup file serves as a reminder to first install the ES before doing the DiRT Restore. Additionally, it saves you time from having to download the ES again.
If desired, you can delete the following files from the Cisco Unity server after installing the Engineering Special and Patches.
· CU7.0(2)_ES31.exe
· CU7.0(2)_TestWritableDomainController.exe
· CU7.0(2)_Exchange2003-KB957593-x86-ENU.exe
· CU7.0(2)_Configurable_DTMF_Key.exe
· CU7.02ES31_Readme.htm
Although the Gather Unity System tool reports the Engineering Special version installed on the Cisco Unity server, it does not detect what Patches have been installed. You may want to keep a record of the Patches that have been installed. For example, you could create a text file within the ES31 folder and write down the date and the names of the patches that you have installed, and any changes to the registry that you have made.
In the event that installing the ES causes a problem with Cisco Unity, use the following procedure to uninstall the ES.
1. Browse to the CommServer\EngineeringSpecialBackup\CU7.0(2)_ES31 folder.
2. Double-click Restore.bat. Click OK to dismiss the pop-ups warning you that the server must be rebooted.
3. Delete the CU7.0(2)_ES31 folder. (If you do not delete the folder, Gather Unity System Info will report that the ES is still installed when it is not.)
4. Reboot the Cisco Unity server.
The following defects of been fixed in this cumulative ES.
|
Identifier |
Component |
Sev |
Headline |
|
pca |
1 |
Issue with ActiveX controls shipped with Unity PCA |
|
|
vmws |
1 |
Login doesn't check alternate extensions |
|
|
conversations |
2 |
Dom: Sub-to-sub messages disappear when partner
server down |
|
|
conversations |
2 |
Digitally network subscribers send message cause
conversation exceptions |
|
|
core |
2 |
Virtual Bytes / Fragmentation in AvCsMgr |
|
|
core |
2 |
"Some upgrade paths do not add DTMF, LDAP authentication
providers to db" |
|
|
core |
2 |
"Secure Messaging: With Message Aging, new
messages treated as expired" |
|
|
database |
2 |
Missing stored procedures after running scripts in UnitydbEx |
|
|
database |
2 |
Failover: FCW can fail if
run after certain ESs applied |
|
|
dommessaging |
2 |
Unity 5.0(1) Domino:6.5.4 AvCs exception caused by UCUnseen
delete |
|
|
import |
2 |
Unity 7.0(2) - Bulk Import Exchange Overwrites AD
Display Name w/ Alias |
|
|
messagemonitor |
2 |
MM VML: Severe delays in
conversation with medium load using PhoneView |
|
|
sa |
2 |
Authentication bypass w/ anonymous auth |
|
|
trap |
2 |
Unity 7.0(2)ES19:new
AvTrapSvr.dll broke VMO TRaP Play function |
|
|
umr |
2 |
Unity System Mailbox Cleanup can cause UMR due to
mailbox full |
|
|
vmws |
2 |
Free form search recipient |
|
|
vmws |
2 |
Play returns a SOAP Fault when the trap call is
disconnected |
|
|
vmws |
2 |
ForwardMessage with
no recording does not forward message |
|
|
vmws |
2 |
RunConversation
method hangs up Trap Call and does not redirect to TUI |
|
|
vmws |
2 |
No SOAP fault on sending message when mailbox is full |
|
|
vmws |
2 |
GetMessages request
returning incorrect data. |
|
|
vmws |
2 |
Login when Password Expired causes E_AVAUTHEN_INVALID_TICKET |
|
|
vmws |
2 |
No AccountStatus set for BroadcastMessages |
|
|
vmws |
2 |
GetMessageProps
response corrupted intermittently |
|
|
vmws |
2 |
VMWS: VMWS diags show user passwords |
|
|
conversations |
3 |
TUI-Delivery Receipts in Ex2007
do not announce intended recipient |
|
|
conversations |
3 |
Unity 5.0(1) ES 41 or above breaks Message
Notification Timeout |
|
|
conversations |
3 |
"If Interview Handler Question Skipped, Unity
States Message Has No Audio" |
|
|
conversations |
3 |
DCR orphan not
preserving name property for return receipt |
|
|
core |
3 |
Unity sends port 0 in SDP
information |
|
|
core |
3 |
AvCsMgr leaks Found during 7.0 load testing |
|
|
core |
3 |
Intermittent MALEx and Conv errors under heavy load |
|
|
database |
3 |
COBRAS Import fails due to max character allowed for
password in SQL SP |
|
|
database |
3 |
"Alternate Extension
""Learning"" can break cross box login/transfer" |
|
|
database |
3 |
users not added to globalsubscriber
and DtmfAccessId tables correctly |
|
|
documentation |
3 |
"After loading ES to support AD2008,
you can no longer run MSCW" |
|
|
domdirconnector |
3 |
PDL Del via Domino Admin - PDL remains visible within
UNITY SA. |
|
|
dommessaging |
3 |
DOM: Exclude Return Receipt does not work |
|
|
dommessaging |
3 |
Unity does not detect clustermate
when Domino partner is down |
|
|
exdirconnector |
3 |
AvDSAD: Syncing of ScopeDls
causes performance problems. |
|
|
exmessaging |
3 |
Ex2007-Some message
types wont play over the TUI for certain subscriber |
|
|
exmessaging |
3 |
MWI may not function when Unity is partnered with
Exchange 2007 cluster |
|
|
exmessaging |
3 |
MALEx - Request to
support CONNECT_IGNORE_NO_PF |
|
|
exmessaging |
3 |
AvWmEx - Feature
request to create mem capture on thread stall |
|
|
exmessaging |
3 |
AvWm custom store
check reports store offline during online backup |
|
|
exmessaging |
3 |
Unity logic for unknown sender (to offer reply) must
handle SMTP address |
|
|
exmessaging |
3 |
Failure to create search folder results in MWI
failure |
|
|
exmessaging |
3 |
Unity Message Store Monitor does not need to
re-create MAPI sessions |
|
|
failover |
3 |
Unity Domino failover causes MWI out of synch |
|
|
licensing |
3 |
Intermittent License Corruption on double-byte Unity
systems |
|
|
mediamaster |
3 |
Enabling Anonymous Authentication still causes NTLM login at Media Maste |
|
|
mediamaster |
3 |
HTTP TRAP - CPCA TRaP record does not work |
|
|
messagemonitor |
3 |
Delays in the creation of message monitor images seen
under heavy load |
|
|
pca |
3 |
CPCA - Unable to
update greetings after applying 7.0(2) ES |
|
|
pca |
3 |
Unity Inbox timestamp incorrect for some time zones |
|
|
pca |
3 |
DST change for Western Australia |
|
|
pimg |
3 |
Unity rely on the
position of the port tags to route calls. |
|
|
sa |
3 |
SA>Primary Location page is vulnerable to Cross
Site Scripting |
|
|
sa |
3 |
Anonymous Auth Logon page counts against the session
count |
|
|
sa |
3 |
Adding subscribers for secondary exchange server
produces no alias |
|
|
sa |
3 |
Can't create Unity subscribers after upgrading to
Unity 7.0.2 |
|
|
sa |
3 |
modify exclusion
pattern so . (period) is allowed |
|
|
setup |
3 |
MSCW: Needs to allow Notes 8.x on Unity server |
|
|
setup |
3 |
Improve RODC check to
include all monitored domains |
|
|
setup |
3 |
Missing resource DLL from ES package - SvcWizRes.dll |
|
|
syscheck |
3 |
SCW: Needs to allow
Notes 8.x on Unity server |
|
|
syscheck |
3 |
AD2008: Writeable DC
test fails on Domino systems |
|
|
telephony |
3 |
Secure messages forwarded twice have static via SIP
integrations |
|
|
telephony |
3 |
Exception in MiuLine:Play
locks wave resource & port |
|
|
telephony |
3 |
Unity has IP Port conflicts with DNS after MS08-037 installed. |
|
|
telephony |
3 |
Unity sends REFER message to the wrong destination on
transfer. |
|
|
telephony |
3 |
Unity incorrectly parses SIP-URI when no userinfo part exists |
|
|
telephony |
3 |
Unity sends SIP INVITE with SDP
but doesn't support early media |
|
|
trap |
3 |
DUC124: TRaP fails in Domino PCA and
Notes 8 on Vista in workgroup |
|
|
utilities |
3 |
AST: CONV - Full Mailbox
Check Features not active after being set |
|
|
utilities |
3 |
AST: CONV - Full Mailbox
Check Prompt not active after being set |
|
|
utilities |
3 |
Bulk import not following the correct permissions to
import users |
|
|
vmws |
3 |
ForwardMessage uses
a previously recorded message |
|
|
vmws |
3 |
"SearchRecipient
""FreeForm"" Search does not
match DTMF ID" |
|
|
vmws |
3 |
Incorrect Soap Fault if an Invalid Message ID is
passed to DeleteMessage |
|
|
vmws |
3 |
SetMessageProps
shouldn't be able to set Sensitivity |
|
|
vmws |
3 |
"""Unknown"" string returned
for NonVoiceMailAttachments message property" |
|
|
vmws |
3 |
Set PasswordCacheEnabled
value to 1 by default |
|
|
vmws |
3 |
accountStatus of firstTimeEnrollment set after enrollment is done |
|
|
vmws |
3 |
E_VMWS_MSG_MAILSERVER_OFFLINE
not returned when mail server is offline |
|
|
vmws |
3 |
TUIPasswordExpired
still set for 1st Login after user changes password |
|
|
vmws |
3 |
No indication from searchReceipients
that there are more search results |
|
|
vmws |
3 |
searchRecipient()
does not pick up strings that begin with a digit |
|
|
vmws |
3 |
NonVoiceAttachmentList
returns empty from getMessageProps |
|
|
vmws |
3 |
Handle Blind Addressing in SearchRecipients |
|
|
vmws |
3 |
VMWS: Inactive
server does not return E_VMWS_GEN_SERVER_NOT_ACTIVE |
|
|
vmws |
3 |
VMWS: Running FCW makes VMWS stops working |
|
|
vmws |
3 |
Return E_VMWS_MSG_INVALID_MESSAGE_ID
if play a deleted message |
|
|
vmws |
3 |
Add AddressInfoID as Login
property |
|
|
vmws |
3 |
VMWS - reduce search
queries for recipient searches |
|
|
vmws |
3 |
VMWS: voicemail sent
from Midlet is not encrypted |
|
|
vmws |
3 |
Package midlet jar/jad/localization files in VMWS
installer |
|
|
conversations |
4 |
Unity 7.x Mark-Urgent not reset between messages sent
in same session |
|
|
conversations |
4 |
DCR Not Invoked in
Several Call States |
|
|
conversations |
4 |
"Unity during message record, press zero to get
to operator" |
|
|
database |
4 |
Unity failing to connect to SQL causing Unity to stop
working as expecte |
|
|
dommessaging |
4 |
Domino Message Count Incorrect When Multiple Notfications are Recieved |
|
|
exdirconnector |
4 |
Read-only AD 2008 pop-up erroneously displayed |
|
|
mediamaster |
4 |
Preferred Audio Device Is Not Retrieved Correctly by
Media Master |
|
|
messagemonitor |
4 |
MM VML: Device refresh-
Exceeded allowed rate for Realtime information. |
|
|
messagemonitor |
4 |
MM/VML - Diagnostic
improvements |
|
|
utilities |
4 |
Conversation traces not enabled using Macro
Conversation State Traces |
|
|
vmws |
4 |
SOAP Authentication.Login
Version properties not returned |
|
|
vmws |
4 |
SearchRecipients -
Distribution list display name contains repetition |
|
|
vui |
4 |
Home Phone notification device update via TUI puts
number in wrong field |
|
|
messagemonitor |
5 |
PhoneView: Need a
new diagnostic to track number of sessions |
|
|
cmts-spectrum |
6 |
CNIR measurement for
DOCSIS 3.0 |
|
|
conversations |
6 |
CUOM voicemail test
fails to deliver msg to inbox |
|
|
conversations |
6 |
Need to configure dtmf key
to disable notification device over TUI |
|
|
conversations |
6 |
Retain urgent setting on forwards and replies. |
|
|
conversations |
6 |
create new PlayPhrase state
with longer FirstDigitTimeout |
|
|
conversations |
6 |
Provide a way to disable sticky playback speed keys |
|
|
core |
6 |
Add AD 2008 support |
|
|
core |
6 |
Unity AD sync - offer setting to disable sync'ing Scope DL's |
|
|
database |
6 |
increase DCR timer to 24
hours |
|
|
exmessaging |
6 |
Application Log is flooded with CiscoUnity_MALEx
30020 and 80040115 |
|
|
exmessaging |
6 |
Fea-Req - Create
only needed Exchange search folders based on COS |
|
|
exmessaging |
6 |
Request to change the limit of Exchange information
store. |
|
|
pca |
6 |
Remove feedback link from CPCA
and SA |
|
|
sa |
6 |
modify exclusion pattern so _ (underscore) is allowed
with Exchange |
|
|
telephony |
6 |
TSP remains registered to CUCM
after failover event |
|
|
umr |
6 |
Improve the process to enter UMR |
|
|
vmws |
6 |
"Add new property ""localArrivalTime"" for getMessages()" |