|
|
As described in Chapter 1, the DAS Server Shelf records information about each Frame Relay Dial-Up or Dial-Backup call in a Call Detail Record (CDR). This appendix contains information about the format of CDRs. It includes the following sections:
The call detail record (CDR) feature creates text records of call related data. The data recorded includes calling and called numbers, call origination/connect time, the time the call was disconnected, the disconnect reason, the DLCI field to identify the originating PRI, and the bearer (B) channel used. There are CDRs for normal calls, i.e., calls that were successfully completed and for failed calls.
The CDRs are collected in files so that they can be uploaded by an StrataView Plus Workstation and to prevent file over-writes and disk capacity problems. The DAS Server Shelf stores up to 10 files of CDRs at any time. Each CDR file contains CDRs that are collected during the time period configured by the CDR Interval. (To configure the CDR Interval and the number of CDR files, see the Modify CDR Configuration section in the chapter, Understanding the DAS Command Line Interface.) If the CDR Interval is configured for 30 minutes (the default), each CDR file will hold CDRs for calls that are accepted during a 30-minute interval. The size of the CDR files will be proportional to the CDR configuration parameters and the call activity rate.
The StrataView Plus Workstation uploads the CDR files from the DAS Server Shelf every 30 minutes, archives and stores them. These archived files are kept for 30 days on the StrataView Plus Workstation before they are deleted.
The CDR is logged in character (ASCII) and fixed-space format, i.e., each data entity (field) occupies a fixed number of spaces in the record. Table D-1 illustrates the fixed-spaced format of the CDRs. The bold text (e.g., Time [26]) identifies the data entity (field) and the number of spaces in the record that it occupies. There is one CDR event, such as a call origination (orig) or a call disconnect (disc), per line in the record. Each line is terminated by an end-of-line character. The time logged in a CDR is the time kept by the DAS Server Shelf.
| Time [26] | Qualifier [11] | Calling Number [21] | Called Number [21] | PRI ID Number [5] | B-Channel Number [3] | Time [26] | Text [35] |
|---|---|---|---|---|---|---|---|
| orig time | Call Rqst | calling | called | PRI id | B-channel | ||
| disc time | Call Disc | calling | called | PRI id | B-channel | connect time | cause |
| orig time | Setup Fail | calling | called | PRI id | B-channel | ||
| disc time | Disc Fail | calling | called | PRI id | B-channel | connect time | cause |
The fields of each record are defined as follows:
All incoming call requests are recorded, time-stamped, and identified by the Call Rqst qualifier to help trace network events triggered by the call request. For each call request, the DAS Server Shelf will record the following:
Call failures may occur during call setup or teardown. These failures will be recorded in CDR files, which include all available information identifying the call, as well as failure codes.
All call-related operation failures will also be recorded in a CDR. The information in a CDR for a failed call will include:
The majority of the failure/error Cause Codes maintained by the DAS Server Shelf are identical to those described in Q.931 specifications. The set of Q.931 Cause Codes has been enhanced, however, for the DAS (INS) Dial-Up Frame Relay application in the following two ways:
Table D-2 lists the Standard Q.931 Cause Codes which have slightly enhanced meanings when applied to the DAS Server Shelf or the DAS (INS) Dial-Up Frame Relay application. These altered meanings are very closely aligned with the Cause Codes defined in Q.931.
| Cause Code [Decimal] | Cause Mnemonic | Exception/error condition |
|---|---|---|
| 16 | Normal call clearing | 1. Normal disconnect/release
2. Cause not present/unavailable |
| 18 | No user response | Call timed out awaiting connection in FR network |
| 21 | Call rejected | Caller/calling length error |
| 31 | Normal unspecified | Call declined by Server |
| 41 | Temporary failure | Call processing suspended |
| 58 | Bearer cap not available | 1. Rate adaptation not V110
2. Non restricted/unrestricted data 3. Data transfer rate not 64kbp 4. User rate not 56 or 64kbps |
| 66 | Channel type not implemented | 1. H type or mapped channel type
2. Call on D-channel |
| 96 | Info element missing | Calling number (ANI) missing |
In addition, there are a few failure conditions for the DAS Server Shelf and DAS (INS) Dial-Up Frame Relay application that do not have close equivalents in the set of Q.931 Cause Codes. Cisco has designed some Error/Failure Cause Codes that are specific only to the DAS Server Shelf and DAS Dial-Up Frame Relay application. These "new" Cause Codes are listed in Table D-3 . These codes are never sent in the "cause information element" of any Q.931 messages. They are used only in the alarm traps and CDR files.
| Cause Code [Decimal] | Cause Mnemonic | Exception/error condition |
|---|---|---|
| 512 | Database error | Problem accessing call database |
| 513 | ANI not subscribed | Specified ANI not in call database |
| 514 | Local FR port busy | Port at local-end of connection is busy |
| 515 | Far-end FR port busy | Port at far-end of connection is busy |
| 516 | Connection exists | Requested connection already exists in the network |
| 517 | Routing failure | Connection could not be routed in network |
| 518 | Conn. removal failure | Could not delete original connection in backup connections during setup, or backup/dialup connection during disconnect |
| 519 | Node operation failure | Setup declined/timed-out by FR network node |
| 520 | Indeterminate PRI endpoint | PRI location in network could not be determined |
| 521 | INSD suspended | INSD not processing new calls temporarily |
| 522 | INS off-line | INS (DAS Server Shelf) not processing calls |
| 523 | Miscellaneous failure | Unknown failure |
| 524 | INSD response timeout | INS/DAS timed out waiting for response from INSD |
|
|