08-10-2001 12:26 AM - edited 03-12-2019 12:12 PM
We are having a problem with addressing new messages. The feature that allows users to toggle between searching by name or searching by extension by pressing the # key twice works with land lines, however cell phone users cannot use this feature. When they hit the # key Unity skips straight to recording the message. Is there a setting for the tones that Unity listens for that will correct this?<br><br>
08-10-2001 12:26 AM
This is probably a case where the cell phone users are not able to press the keys fast enough... by default the #s need to come within a quarter of a second of one another. There is a registry setting where you can define how far apart key presses need to be before they are considered individual keys or a "double key" event.
HKLM\Software\Active Voice\CDE\1.0\Advanced Navigation\
DWORD: DoubleKeyInterDigitTimeOut
The value is in milliseconds, the default (without the key) is 250 ms.
This isn't used often other than the ## thing to change addressing modes, however theres a hidden "44" feature for blindly replying to everyone in the TO and CC list instead of just the sender that some folks still know about (and now you do, too).
And again, this value is included in my RegistrySetting tool on my web page if you don't want to go trundling around in the registry adding keys.
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
08-10-2001 12:26 AM
Is there a way to diable the "44" reply to all? I have had users report that they replied to everyone in a distribution list that they were a member of which I attributed to user error.
08-10-2001 12:26 AM
no, the feature is on all the time... why would they hit "44" to reply?
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
04-19-2002 12:19 AM
Does this apply with Unity 3.X ? We are having this issue.
04-19-2002 12:38 AM
digit timing is a bit longer by default in 3.x I believe but you may still need to adjust this. The Advanced Settings tool allows you to do this easily.
Jeff Lindborg
Unity Technical Lead/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
12-10-2002 09:04 AM
I have a customer where their owner cannot do ## while in his mailbox. Using the Advanced Setting Tool I have increased the delay to 500 ms. He is still unable to use ##. Here are the tests that we have done.
- From land line - passed
- From land line IP phone - passed
- From cell phone (AT&T) - passed
- From cell phone (Sprint) - failed
- From cell phone (Verizon-customer's carrier) - failed.
Additionally, I opened a case with the TAC, D426780. Adam Fuller stated that all that can be done has.
Do you have any additional input?
12-10-2002 11:09 AM
Update to this post.
Changed the delay to 1000ms and this worked all across the board.
Dropped it back down to 750ms and it still seems to work.
Will Duensing
12-10-2002 11:09 AM
well, you can try to bump it up further but if a cell phone provider can't pass DTMF any faster than a half second apart, I'd be deeply suspicious - that's awfully slow - I've never seen a value of 500 ms here actually fail regularly under any circumstances.
There's nothing else we can really do on our end here - if the tones aren't reaching us fast enough we're kind of stuck. I would definitely not suggst cranking it up to more than, say, 750 ms however.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: