destCause_value: CUCM destination cause codes 0, 16 and 393216
destCause_value is the exact Cisco CUCM CDR export field. It records a call-clearance reason using Q.850 and Cisco-specific cause values.
Field definition and source
Reflects the reason for the calss that the destination party cleared. See topics that are related to call termination cause codes for a listing of the valid values per Q.850. For calls that the originating party clears, this field stays zero. In addition to the standard values that are described in Q.850, when a call gets split by a feature (transfer or conference), the CDR terminates, and this field gets set to 393216. This represents a proprietary value for this field. Default - 0. If the destination cannot be reached, this field stays 0.
- Readable name
- Destination Cause value
- Type
- enum
What does destCause_value 0 mean?
Zero in this field is not a complete call-success verdict. Cisco specifies that destCause_value stays zero when the originating party clears the call, and also when the destination cannot be reached. Read origCause_value and the timing fields before deciding what happened.
What does destCause_value 393216 mean?
393216 is Cisco's proprietary call-split value. A transfer or conference can split a call into multiple CDRs: the current CDR ends, while another leg may continue the conversation. Treating every 393216 as a failed conversation would misclassify those records.
Inspect the related call legs, transfer/conference fields, connection time and duration. CDR Clarity preserves the original code and displays its shared decoded meaning.
Is destCause_value 16 an error?
Code 16 means normal call clearing. It describes the release cause; it does not prove that the audio was acceptable or explain the user's reason for hanging up. Use matching CMR observations when investigating media quality.
How should I compare destCause_value with origCause_value?
Keep both fields from the same CDR together. destCause_value reports the destination side's clearance reason; origCause_value supplies the other side. A zero on one side must not hide a nonzero reason on the other. If a feature creates another call leg, inspect its own record rather than overwriting the first record's causes.
Raw values and decoded meanings
| Code | Cisco meaning | Reference |
|---|---|---|
0 | No error | Cisco code table |
16 | Normal call clearing | Cisco code table |
17 | User busy | Cisco code table |
47 | Resource unavailable, unspecified | Cisco code table |
393216 | Call split (was 126) This code applies when a call terminates during a transfer operation because it was split off and terminated (was not part of the final transferred call). This code can help you to determine which calls terminated as part of a feature operation. | Cisco code table |
The labels come from the same code table used by the analyzer. Source links identify the documented release; check your CUCM release when a value is absent or its behavior differs.
Related fields and troubleshooting
- origCause_value
- destCallTerminationOnBehalfOf
- origCallTerminationOnBehalfOf
- Q.850 cause=47 and Cisco call disposition terminology
- Connection time and duration
Have an entire CDR file?
Load your CUCM CDR and matching CMR files to decode values, inspect related call legs and compare causes in context. Files are processed locally in your browser.