Cisco Bug: CSCsz56287 - CTI should handle unsupported characters or digits in the dial string
Feb 22, 2014
- Cisco Unified Communications Manager (CallManager)
- Cisco Unity Connection Version 7.1
- Cisco Unified Communications Manager Version 7.1
Known Affected Releases
5.1(3) 5.1(3.2101.1) 6.1(4) 7.0(2) 7.1(2)
Symptom: The CDR Analysis and Reporting (CAR) tool may cease importing CDR records and the following error may be printed in the CAR traces. ========== 2009-04-21 11:01:29,464 ERROR [DailyCdrLoad] controller.CtrLoadCDRRecords - processRecords(): NumberFormatException Error while setting UDT object ========== Conditions: This problem may occur when a call is presented to Cisco Unified Communication Manager (CUCM) with invalid character(s) in the dial string like commas, spaces, etc. Most devices (phones, gateways, etc) prevent such invalid characters from being dialed, but it has been found that if JTAPI or TAPI applications have not be coded to catch and prevent such illegal characters from being presented to CUCM's CTIManager service, that CTIManager will pass these invalid strings to the CUCM service which may cause unexpected for CAR or other applications, services, or processes.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases