I am pushing a URL to the phones using Execute object. It was much faster with 3.3.2, but we have noticed a significant slow down in the response time for 3.3.3. It takes about 1-2 minutes before the phone screen displays the executed object. I have tried to play with Priority variable within the ExecutItem tag, but it didn't help.
Is this a known issue? Has any one else experienced this problem too? Is there a work around?
I am not aware of any such issue with 3.3(3) at this time. Reset CallManager, and power cycle the phone. Insure that you have the most up-to-date phone load available from CCO. If you still run into problems, please open a case through Cisco Developer Support www.cisco.com/go/developersupport
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 ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...