Guest

Preview Tool

Cisco Bug: CSCtb63262 - identify and document causes for current CDR cause codes

Last Modified

Feb 26, 2015

Products (13)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Intercompany Media Engine
  • Cisco Business Edition 6000 Version 9.0
  • Cisco Unified Communications Manager Version 9.0
  • Cisco Business Edition 5000 Version 9.0
  • Cisco Business Edition 6000 Version 8.5
  • Cisco Business Edition 5000 Version 8.5
  • Cisco Unity Connection Version 7.1
  • Cisco Business Edition 6000 Version 8.6
  • Cisco Unity Connection Version 9.0
View all products in Bug Search Tool Login Required

Known Affected Releases

6.1(3) 7.1(2) 8.5(1) 9.0(1)

Description (partial)

Symptom:
Cause Codes in CDR are generic. Abnormal cause codes identify call failures but the text of those codes are very ISDN centric and do not directly translate to VOIP environments.  Given a cause code it is almost impossible to guess the underlying condition that triggers the cause code.

Conditions:
ccm currently disconnects cause with fairly generic cause codes.  We need to clarify the conditions that trigger each cause code.  This effort is for existing cause codes and independent of any effort for real cause codes.

As an example:
Cause Code 47:
May be caused by endpoint unregistering during active call
May be caused by interruption in H.225 or H.245 session for an active H.323 call
May be caused by failure to establish H.225 or H.245 session during H.323 call setup
May be caused by codec mismatch between 2 endpoints

We need identify and document the conditions under which CM will use each of the available cause codes. At a minimum document conditions that cause the most common abnormal cause codes.
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)
  • 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.