Cisco Bug: CSCte67714 - numeric value for Notification.SignIn key may cause signin failure.
Feb 14, 2011
- Cisco Unity Servers
Known Affected Releases
Symptom: Setting the value of the notification sign-in key to a numeric value may result in a failed logon. Conditions: This issue is related to the following setting: "DTMF key assigned to route to Subscriber Sign-In Conversation" found under Notification Devices on the bottom of SA-->Configuration-->Settings page. If the sign-in key is set to 3 then I need to dial 33069 at the "To check new messages enter your ID now". If I attempt to just dial my ID the conversation will strip of the leading 3 and will attempt to sign me in as 069. This will of course fail even though I did exactly what the prompt asked. When such a conflict occurs, there is no way for Unity to know that the intent of the leading 3 when dialing 3069. As a more extreme example, consider the case where both 3301 and 301 were valid subscriber extensions in Unity. When the Notification conversation sees 3301 as dialed digits should it assume this is x301 who has first dialed the sign-in key? or should it assume this is x3301 bypassing the sign-in key?
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases