I found a bug in AXL where the server is returning an incorrect encoding type for the data being returned in the response message. I was wondering if anyone has a workaround for this bug.
Here are more details.
-- added "español" as a description for a phone.
-- sent "executeSQLQuery" SOAP Request using apache axis.
The response I receive from the ccm has "UTF-8" as the char encoding. Apache AXIS blows up trying to parse the message.
Has anyone run across this bug before and if so how did you fix it. Also it seems Cisco is not to interested in fixing the issue since they closed the TAC case on it. My only thing I can think of doing at this point is writing my own SOAP client and ignoring the encoding being returned.
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...