CDR History
Storage of Call Detail Records (CDR) for all calls (or call attempts) what are passed via Yeti. Yeti save CDR for every call termination attempt, so one received call on legA can cause multiple CDRs in case of rerouting. All CDRs related to one call will have same values of Orig Call Id and Local tag, routing attempt value indicates sequence number of CDR withing same call.
See also
There is built-in tool to provide RTP statistics retention, see Data retention documentation.
CDR’s attributes:
- Id
Unique CDR’s id.
- Time Start
Date and time of call starting.
- Time Contect
Date and time of receiving 200OK response.
- Time Contect
Date and time of receiving Bye.
- Customer
Value of the *Name* attribute of the Customer Contractor for the call.
- Vendor
Value of the *Name* attribute of the Vendor Contractor for the call.
- Customer Auth
Value of the *Name* attribute of the Customer Auth.
- Src Prefix Routing
Prefix of the source number (A-number) that was used for routing for the call.
- Src Area
Source Area for the call (if any).
- Dst Prefix Routing
Prefix of the destination number (B-number) that was used for routing for the call
- Dst Area
Destination Area for the call (if any).
- Dst Country
Country that was associated (via Network Prefixes table) with the destination number (B-number) for the call.
- Status
Status of the call regarding its Disconnect Code. Could be SUCCESS (if “Success” flag is enabled for Disconnect Code that was applied to the call) or FAILURE (otherwise).
- Duration
Duration of the call in seconds.
- Is Last CDR
This field should be “yes” (“true”) for last routing attempt for the call (“no”(“false”) otherwise).
- Dump Level
Level of capturing of call to PCAP (Packet Capture) files that was chosen in the Dump Level attribute of Customers Auth that is related to this call:
Capture nothing - Information didn’t capture to pcap-file for this call.
Capture signaling traffic - Only signaling information had been captured to pcap-file for this call.
Capture rtp traffic - Only RTP traffic had been captured to pcap-file for this call.
Capture all traffic - Only signaling information & RTP traffic had been captured to pcap-file for this call.- Orig GW
Value of the *Name* attribute of Gateway that was used as Originator for the call.
- Term GW
Value of the *Name* attribute of Gateway that was used as Terminator for the call.
- Routing Plan
Routing plan that was used for the call.
- Routing Group
Routing Group that was used for the call.
- Routing Tag
Routing Tag that was used for the call.
- Rateplan
Rateplan that was used for the call.
- Internal Disconnect Code
Internal Disconnect Code for the call.
- Lega Disconnect Code
Disconnect Code for interconnection between Yeti and Gateway that was used as Originator for the call.
- Lega Disconnect Reason
Disconnect Reason for interconnection between Yeti and Gateway that was used as Originator for the call.
- Legb Disconnect Code
Disconnect Code for interconnection between Yeti and Gateway that was used as Terminator for the call.
- Legb Disconnect Reason
Disconnect Reason for interconnection between Yeti and Gateway that was used as Terminator for the call.
- Src Prefix In
Source number (A-number) that was received from Gateway that was used as Originator for the call.
- Dst Prefix In
Destination number (B-number) that was received from Gateway that was used as Originator for the call.
- Src Prefix Out
Source number (A-number) that was sent to Gateway that was used as Terminator for the call.
- Dst Prefix Out
Destination number (B-number) that was sent to Gateway that was used as Terminator for the call.
- LRN
Routing number that was received from LNP database (in case of requesting) for the call.
- Diversion In
Value of SIP Diversion header that was received from Gateway that was used as Originator for the call.
- Diversion Out
Value of SIP Diversion header that was sent to Gateway that is used as Terminator for the call.
- Src Name In
Name of caller that was received in the “From” field of SIP header from Gateway that was used as Originator for the call.
- Src Name Out
Name of caller that was sent in the “From” field of SIP header to Gateway that was used as Terminator for the call.
- Node
Node (independent installation of YETI-SEMS) that was used for the call.
- PoP
Point of Presence that was received the call.
- Local Tag
Internal session ID for call legA
- LebB Local Tag
Internal session ID for call legB
- Orig Call
Unique ID of the call that was received ( in the Call-ID header) from Gateway that was used as Originator for the call.
- Term Call
Unique ID of the call that was generated by Yeti and was used in communication (in the Call-ID header) between Yeti and from Gateway that was used as Terminator for the call.
- Routing Attempt
Number of attempt to route this call to destination.
- Customer Price
Price that was used for changing balance of Customer’s Account (in case of success call).
- Vendor Price
Price that was used for changing balance of Vendors’s Account (in case of success call).
- Vendor Invoice
Invoice with billing information about changing balance of Vendors’s Account (in case of success call).
- Customer Invoice
Invoice with billing information about changing balance of Customer’s Account (in case of success call).
- Routing Delay
Delay (in miliseconds) between receiving call by Yeti (from Originator) and starting of its termination (to Terminator).
- PDD
Post Dial Delay (PDD) for this call ( time between the start of the call and the moment the phone of the called party starts ringing) in seconds.
- RTT
Round-trip time (RTT) for this call.