How to Use the CDR Lookup Report

This report allows users to review full details about call detail records (CDR) in the system.

 

Report -> Usage -> CDR Look up

 

You can view full details about all calls here, including the reason they failed.

A lot of filters are available that can be used for searching any specific call you need to check – e.g. customer, PIN, carrier, date range, called number, calling number, source IP, destination IP, call margin, call revenue, call cost, call duration, etc.

The “Maximum rows in result” determines how many CDRs will be displayed – if you expect results to be over 5000 rows (e.g. if you are trying to view CDRs for longer periods of time) the results will not be displayed, but a file will be generated and will be available for download in CDR Lookup Jobs menu.

If the “Maximum rows in result” is less than 5000, a grid with the CDRs that match the search will appear:

 

Please note that the search by Time is based on the Disconnect time of the calls.

 

The system displays the main details for each call based on the selected criteria:

 

There are three different durations for each CDR:

  • Billable duration – the duration of the call based on the carrier increment
  • Charge duration – the duration of the call based on the customer increment
  • Session duration – the total duration of the call including the PDD based on 1 second increments

 

Example:

Carrier increment – 1/1

Customer (your) increment – 30/30

Call PDD – 5 seconds

Actual call duration – 27 seconds

 

The different durations for this call will be as follows:

  • Billable duration – 27 seconds
  • Charge duration – 30 seconds
  • Session duration – 32 seconds

 

If the account uses a currency different than the system currency, in the column “FX Charge” you will see the charge in the account currency and in the details of the CDR will see the exchange rate, based on which the FX Charge is calculated.

You can download the list of CDRs displayed in the report by clicking on the “Download CDR” button.

You can also view the details of each CDR by clicking on the “View CDR” button.

 

The system displays full details about the CDR, for example:

  • CDR ID
  • global session ID
  • IVR ID
  • call type
  • member
  • account
  • endpoint
  • the routes through which the failover passed
  • why the routes forwarded the call to the next one
  • the ring time
  • the session duration
  • the billable duration
  • the relevant bill plan with details for the charge and cost of the call
  • the disconnect causes
  • etc.

 

Disconnect Causes
 
Please find below a list of the mappings between YATE and PSTN disconnect causes:
  • “Normal Call Clearing” => 16
  • “EndedByLocalUser” => 16
  • “EndedByNoAccept” => 21
  • “EndedByAnswerDenied” => 21
  • “EndedByRemoteUser” => 16
  • “EndedByRefusal” => 21
  • “EndedByNoAnswer” => 19
  • “EndedByCallerAbort” => 24
  • “EndedByTransportFail” => 127
  • “EndedByConnectFail” => 127
  • “EndedByGatekeeper” => 127
  • “EndedByNoUser” => 21
  • “EndedByNoBandwidth” => 49
  • “EndedByCapabilityExchange” => 58
  • “EndedByCallForwarded” => 29
  • “EndedBySecurityDenial” => 21
  • “EndedByLocalBusy” => 17
  • “EndedByLocalCongestion” => 34
  • “EndedByRemoteBusy” => 34
  • “EndedByRemoteCongestion” => 34
  • “EndedByUnreachable” => 3
  • “EndedByNoEndPoint” => 27
  • “EndedByHostOffline” => 27
  • “noroute” => 3
  • “noconn” => 63
  • “noauth” => 57
  • “nomedia” => 58
  • “noanswer” => 19
  • “busy” => 17
  • “congestion” => 34
  • “offline” => 27
  • “rejected” => 21
  • “forbidden” => 57
  • “incomplete” => 28
  • “looping” => 127
  • “failure” => 41
  • “timeout” => 102
  • “nocall” => 127
  • “pending” => 127
  • “Bad Request” => 127
  • “Unauthorized” => 57
  • “Payment Required” => 21
  • “Forbidden” => 57
  • “Not Found” => 1
  • “Method Not Allowed” => 127
  • “Not Acceptable” => 127
  • “Proxy Authentication Required” => 21
  • “Request Timeout” => 102
  • “Conflict” => 41