Call Termination Cause Codes of CUCM, CME, and CUBE
Tariscope is a call accounting and billing system that provides many different features to analyze calls information. Tariscope is a Web application; therefore, it is available on a desktop PC, laptop, and smartphone.
Tariscope contains many features for analysis of call termination cause codes from Cisco Unified Communications Manager (CUCM), Cisco Call Manager Express (CME), and Cisco Unified Border Element (CUBE):
- The display of call termination cause codes in the calls views.
- The report generation on the call termination cause codes.
- The display information on the specific call termination cause codes on the Tariscope dashboard.
- Immediate sending of messages to the administrator by certain codes immediately after receiving CDR.
Let us consider these options.
The display of the codes in the calls views
The Tariscope views for calls provide the output of many CDR fields. There is the Release cause field among them. You can see an example of the view in Figure 1.
Figure 1
The Tariscope calls view allows a user:
- To select records with required codes.
- To sort information.
- To group data by the release cause.
- To get information on the original CDR data.
The user can select the desired records in the calls view and get the view that contains all original records of CDR. The example of the view is shown in Figure 2.
Figure 2
The Tariscope user can create the view that display calls information only for the specific call termination cause codes, for example, for today. An example of such settings is shown in Figure 3.
Figure 3
If you want to know how many calls made with each termination code type, you should apply the grouping in the view. Figure 4 shows the example of the grouping by the Release cause field. The view contains only two field, because it is enough to apply grouping. If you need, you can sort the table with the grouping data.
Figure 4
Any view can be exported to the external file. Supported the following file types:
- Excel.
- HTML.
- CSV.
- PDF.
The report generation
In addition to receiving a report by exporting a view, you can create a report that can contain both the text and graphical data. How to create the report with information on the call termination cause codes you can find in the article.
You can initialize the report generation manually or use the automatic scheduled report generation. In the latter case the Tariscope Tasks service is used. The service can generate reports by schedule and send it to the specific email addresses. And you will always be up to date on call termination codes.
Monitor the termination codes on the dashboard
Tariscope contains the dashboard that includes a large set of widgets. You can easily install a widget that, for example, will display information, for example, by completion codes 41 and 47 in the last minute. An example of the widget is shown in Figure 5.
Figure 5
In the widget, you can set a list of the fields that you wish.
Immediate sending of messages
If you need to get information about a call with the specific termination cause code immediately after Tariscope receives such call record, Tariscope help you to solve this task. You should create the script that will be executed after each call processing. The example of the similar script is described in the article. Let us know if you need our help in the script creation. You should bind the script to the New call event as shown in Figure 6.
Figure 6
Let us know if you have any other suggestions for analyzing call termination codes.
You can try Tariscope. It is a free. Download the Tariscope trial.
The tables of codes from the Cisco document are shown below.
Table 1. Call Termination Cause Codes
|
Code
|
Description
|
|---|---|
| 0 | No error |
| 1 | Unallocated (unassigned) number |
| 2 | No route to specified transit network (national use) |
| 3 | No route to destination |
| 4 | Send special information tone |
| 5 | Misdialed trunk prefix (national use) |
| 6 | Channel unacceptable |
| 7 | Call awarded and being delivered in an established channel |
| 8 | Preemption |
| 9 | Preemption—circuit reserved for reuse |
| 16 | Normal call clearing |
| 17 | User busy |
| 18 | No user responding |
| 19 | No answer from user (user alerted) |
| 20 | Subscriber absent |
| 21 | Call rejected |
| 22 | Number changed |
| 26 | Non-selected user clearing |
| 27 | Destination out of order |
| 28 | Invalid number format (address incomplete) |
| 29 | Facility rejected |
| 30 | Response to STATUS ENQUIRY |
| 31 | Normal, unspecified |
| 34 | No circuit/channel available |
| 38 | Network out of order |
| 39 | Permanent frame mode connection out of service |
| 40 | Permanent frame mode connection operational |
| 41 | Temporary failure |
| 42 | Switching equipment congestion |
| 43 | Access information discarded |
| 44 | Requested circuit/channel not available |
| 46 | Precedence call blocked |
| 47 | Resource unavailable, unspecified |
| 49 | Quality of Service not available |
| 50 | Requested facility not subscribed |
| 53 | Service operation violated |
| 54 | Incoming calls barred |
| 55 | Incoming calls barred within Closed User Group (CUG) |
| 57 | Bearer capability not authorized |
| 58 | Bearer capability not presently available |
| 62 | Inconsistency in designated outgoing access information and subscriber class |
| 63 | Service or option not available, unspecified |
| 65 | Bearer capability not implemented |
| 66 | Channel type not implemented |
| 69 | Requested facility not implemented |
| 70 | Only restricted digital information bearer capability is available (national use) |
| 79 | Service or option not implemented, unspecified |
| 81 | Invalid call reference value |
| 82 | Identified channel does not exist |
| 83 | A suspended call exists, but this call identity does not |
| 84 | Call identity in use |
| 85 | No call suspended |
| 86 | Call having the requested call identity has been cleared |
| 87 | User not member of CUG (Closed User Group) |
| 88 | Incompatible destination |
| 90 | Destination number missing and DC not subscribed |
| 91 | Invalid transit network selection (national use) |
| 95 | Invalid message, unspecified |
| 96 | Mandatory information element is missing |
| 97 | Message type nonexistent or not implemented |
| 98 | Message is not compatible with the call state, or the message type is nonexistent or not implemented |
| 99 | An information element or parameter does not exist or is not implemented |
| 100 | Invalid information element contents |
| 101 | The message is not compatible with the call state |
| 102 | Call terminated when timer expired; a recovery routine executed to recover from the error |
| 103 | Parameter nonexistent or not implemented - passed on (national use) |
| 110 | Message with unrecognized parameter discarded |
| 111 | Protocol error, unspecified |
| 122 | Precedence Level Exceeded |
| 123 | Device not Preemptable |
| 125 | Out of bandwidth (Cisco specific) |
| 126 | Call split (Cisco specific) |
| 127 | Interworking, unspecified |
| 129 | Precedence out of bandwidth |
| 131 | Call Control Discovery PSTN Failover (Cisco specific) |
| 132 | IME QOS Fallback (Cisco specific) |
| 133 | PSTN Fallback locate Call Error (Cisco specific) |
| 134 | PSTN Fallback wait for DTMF Timeout (Cisco specific) |
| 135 | IME Failed Connection Timed out (Cisco specific) |
| 136 | IME Failed not enrolled (Cisco specific) |
| 137 | IME Failed socket error (Cisco specific) |
| 138 | IME Failed domain blacklisted (Cisco specific) |
| 139 | IME Failed prefix blacklisted (Cisco specific) |
| 140 | IME Failed expired ticket (Cisco specific) |
| 141 | IME Failed remote no matching route (Cisco specific) |
| 142 | IME Failed remote unregistered (Cisco specific) |
| 143 | IME Failed remote IME disabled (Cisco specific) |
| 144 | IME Failed remote invalid IME trunk URI (Cisco specific) |
| 145 | IME Failed remote URI not E164 (Cisco specific) |
| 146 | IME Failed remote called number not available (Cisco specific) |
| 147 | IME Failed Invalid Ticket (Cisco specific) |
| 148 | IME Failed unknown (Cisco specific) |
Table 2. Cisco-Specific Call Termination Cause Codes
|
Decimal Value Code
|
Hex
|
Description
|
|---|---|---|
| 262144 | 0x40000 | Conference Full (was 124) |
| 393216 | 0x60000 | 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. |
| 458752 | 0x70000 | Conference drop any party/Conference drop last party (was 128) |
| 16777257 | 0x1000029 | CCM_SIP_400_BAD_REQUEST |
| 33554453 | 0x2000015 | CCM_SIP_401_UNAUTHORIZED |
| 50331669 | 0x3000015 | CCM_SIP_402_PAYMENT_REQUIRED |
| 67108885 | 0x4000015 | CCM_SIP_403_FORBIDDEN |
| 83886081 | 0x5000001 | CCM_SIP_404_NOT_FOUND |
| 100663359 | 0x600003F | CCM_SIP_405_METHOD_NOT_ALLOWED |
| 117440591 | 0x700004F | CCM_SIP_406_NOT_ACCEPTABLE |
| 134217749 | 0x8000015 | CCM_SIP_407_PROXY_AUTHENTICATION_REQUIRED |
| 150995046 | 0x9000066 | CCM_SIP_408_REQUEST_TIMEOUT |
| 184549398 | 0xB000016 | CCM_SIP__410_GONE |
| 201326719 | 0xC00007F | CCM_SIP_411_LENGTH_REQUIRED |
| 234881151 | 0xE00007F | CCM_SIP_413_REQUEST_ENTITY_TOO_LONG |
| 251658367 | 0xF00007F | CCM_SIP_414_REQUEST_URI_TOO_LONG |
| 268435535 | 0x1000004F | CCM_SIP_415_UNSUPPORTED_MEDIA_TYPE |
| 285212799 | 0x1100007F | CCM_SIP_416_UNSUPPORTED_URI_SCHEME |
| 83886207 | 0x1500007F | CCM_SIP_420_BAD_EXTENSION |
| 369098879 | 0x1600007F | CCM_SIP_421_EXTENSION_REQUIRED |
| 402653311 | 0x1800007F | CCM_SIP_423_INTERVAL_TOO_BRIEF |
| 419430421 | 0x19000015 | CCM_SIP_424_BAD_LOCA TION_INFO |
| 1073741842 | 0x40000012 | CCM_SIP_480_TEMPORARILY_UNAVAILABLE |
| 1090519081 | 0x41000029 | CCM_SIP_481_CALL_LEG_DOES_NOT_EXIST |
| 1107296281 | 0x42000019 | CCM_SIP_482_LOOP_DETECTED = 0x42000000 + EXCHANGE_ROUTING_ERROR |
| 1124073497 | 0x43000019 | CCM_SIP_483_TOO_MANY_HOOPS |
| 1140850716 | 0x4400001C | CCM_SIP_484_ADDRESS_INCOMPLETE |
| 1157627905 | 0x45000001 | CCM_SIP_485_AMBIGUOUS |
| 1174405137 | 0x46000011 | CCM_SIP_486_BUSY_HERE |
| 1191182367 | 0x4700001F | CCM_SIP_487_REQUEST_TERMINATED |
| 1207959583 | 0x4800001F | CCM_SIP_488_NOT_ACCEPTABLE_HERE |
| 1258291217 | 0x4B000011 | CCM_SIP_491_REQUEST_PENDING |
| 1291845649 | 0x4D000011 | CCM_SIP_493_UNDECIPHERABLE |
| 1409286185 | 0x54000029 | CCM_SIP_500_SERVER_INTERNAL_ERROR |
| 1442840614 | 0x56000026 | CCM_SIP_502_BAD_GATEWAY |
| 1459617833 | 0x57000029 | CCM_SIP_503_SERVICE_UNAVAILABLE |
| 2801795135 | 0xA700003F | CCM_SIP_503_SERVICE_UNAVAILABLE_SER_OPTION_NOAV |
| 1476395110 | 0x58000066 | CCM_SIP__504_SERVER_TIME_OUT |
| 1493172351 | 0x5900007F | CCM_SIP_505_SIP_VERSION_NOT_SUPPORTED |
| 1509949567 | 0x5A00007F | CCM_SIP_513_MESSAGE_TOO_LARGE |
| 2701131793 | 0xA1000011 | CCM_SIP_600_BUSY_EVERYWHERE |
| 2717909013 | 0xA2000015 | CCM_SIP_603_DECLINE |
| 2734686209 | 0xA3000001 | CCM_SIP_604_DOES_NOT_EXIST_ANYWHERE |
| 2751463455 | 0xA400001F | CCM_SIP_606_NOT_ACCEPTABLE |
Links
Download and test Tariscope
Benefits of Tariscope to collect and analyze CDR and CMR from CUCM
Control of call quality for CUCM using Tariscope
Tariscope configuration to use the restriction feature with CUCM
