Table Of Contents
Cisco Unity 4.0(5) Engineering Special 20
Published July 28, 2005
The message locator conversation is not using the custom key mapping conversations if a user is configured for one.
Problem Description and Resolution
In the SetupPlaySearchMsgStack JavaState, it was only checking for SubMsgPlay (standard conversation) or SubMsgPlay_OptConv1 (Optional conversation 1) - it did not check for the N/S/X or Custom conversation settings.
As such after going through the message locator conversation and finding a message to play, the keys active during message playback and beyond were set to the standard conversation even though the subscriber could be configured for the N/S/X/Custom key mappings.
The message locator conversation now checks for custom key mapping.
Special Installation Instructions
New and Changed Behavior
© 2005 Cisco Systems, Inc. All rights reserved.