Messages over 60 seconds do not accept DTMF commands
While we wait for the TAC - client has odd issue. If a message left in Unity is over 60 seconds in length, Unity will not respond to DTMF commands for standard coversation. All paramters are default (message length etc). Unity version is 4.0.5. Anyone ever run into this? We have tested repeatedly and often and this applies to leaving or retreiving messages. If you are retreiving and # to the end in a message that is over 60 seconds DTMF works fine.
Re: Messages over 60 seconds do not accept DTMF commands
Well, that's a first - pretty confident this is not a problem on the Unity side as there's no logic anywhere that will suddenly have us ignoring digit events coming up to us from the TSP - especially not based on the length of a message...
The best I can suggest is go go through the usual digit and one way audio issues that folks have run into in the past while you're waiting - no clue why any of these would be specific to messages longer than 60 seconds but I'm rather confident you're not going to find some bizzare Unity bug or configuration issue that would result in that behavior either.
here's a couple of tech tips that might be related to Unity "ignoring" digits:
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...