Preview Tool

Cisco Bug: CSCtb39405 - Ampersand Entered in Fast Dial Through Web Interface Causes XML Parse Er

Last Modified

Feb 07, 2017

Products (1)

Known Affected Releases


Description (partial)


Ampersand Entered in Fast Dials Through Web Interface Causes XML Parse Error

This bug is opened to try to configure the web interface to have a bit of JavaScript code to check for ampersands in the text boxes, and give warning, before the page is submitted. Since general users are allowed to edit their own speed dials, they're going to have no idea what went wrong when they go to access their directory and their speed dial directory shows "XML Parse Error"!


Setup personal fast dials for IP phone through the CME web interface and put an ampersand in one of the labels.  When looked at the personal speed dials through the ip phone, the phone displayed "XML parse error" instead of displaying his speed dials.  After looking at the fast dial setup, there was the ampersand configured,  after removing the ampersand, the personal fat dials now displayed properly.

You will see "XML parse error" when you have an invalid character in the label command.  See the following:

> ephone-dn  17  dual-line
>  number 122
>  label B&W x122

An ampersand (&) is an invalid character in the XML specification.  

Since that is how the phone configs are stored and speed dials are propagated, you need to conform to XML standards for labels and speed-dial descriptions.  Here is a snip of the W3 XML standard:

"Only the characters '<' and '&' are strictly illegal in XML.  Apostrophes, quotation marks and greater than signs are legal, but it is a good habit to replace them."

This is also documented on CCO in the link below:

"The & character cannot be parsed by the phone. If the directory entry contains the & character, the phone displays XML Parse Error."


The & character must not be used in any of the directory entry. In order to avoid this issue, check the directory entries. If any of the entries have the & character, remove the same from that entry.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.