Actions

Call detail record: Difference between revisions

No edit summary
(Add explanation on Id in the case scenario)
Line 19: Line 19:
== Call Detail Records Generation  ==
== Call Detail Records Generation  ==
TelcoBridges CDRs are generated on a per-leg bases when the call is answered and when the call is terminated.
TelcoBridges CDRs are generated on a per-leg bases when the call is answered and when the call is terminated.
In the cases illustrated below:
'''Id''' is a 128 bits unique identifier for all the records of a same call.
* Id = h323-conf-id  for RADIUS; @{SessionId} for Text CDR
'''Original Id''' is a 128 bits unique identifier used for Call Transfer record. Each Call Transfer outgoing legs has its own unique '''Id''', the '''Original  Id''' is used to associated the transfer led with the original call legs (incoming+outgoing).
* Original Id = h323-conf-id  for RADIUS; @{SessionId} for Text CDR


=== Case 1: Call Answered  ===
=== Case 1: Call Answered  ===
Line 32: Line 40:


== Text-based Call Detail Records ==
== Text-based Call Detail Records ==
[[Text Call Detail Records (CDR)|Text-based call detail records]]
[[Text Call Detail Records (CDR)|Text-based call detail records]]


== RADIUS Call Detail Records  ==
== RADIUS Call Detail Records  ==

Revision as of 14:21, 25 April 2016

Call detail records, or CDR for short, are the foundation of subscriber billing activities by telecom service providers. They are data records containing call-related information such as:

  • Incoming Network
  • Outgoing Network
  • Calling number
  • Called number
  • Start time
  • End Time

See this link from more details Wikipedia - Call Retail Record

TelcoBridges and call detail records

TelcoBridges TMG800, TMG3200 and TMG7800 products support the generation of call detail records in text format. They also support the ability to export call detail records to a RADIUS server for accounting purposes. Both methods can be used simultaneously.

Text CDRs are stored locally on the TMG units and must be extracted from the system either manually, or automatically.

If the network supports RADIUS, this method is preferred as each record will be sent in a timely manner to an external database for storage.

Call Detail Records Generation

TelcoBridges CDRs are generated on a per-leg bases when the call is answered and when the call is terminated.

In the cases illustrated below:

Id is a 128 bits unique identifier for all the records of a same call.

  • Id = h323-conf-id for RADIUS; @{SessionId} for Text CDR

Original Id is a 128 bits unique identifier used for Call Transfer record. Each Call Transfer outgoing legs has its own unique Id, the Original Id is used to associated the transfer led with the original call legs (incoming+outgoing).

  • Original Id = h323-conf-id for RADIUS; @{SessionId} for Text CDR

Case 1: Call Answered

Case 2: Call Unanswered

Case 3: Call Transferred

Text-based Call Detail Records

Text-based call detail records

RADIUS Call Detail Records

RADIUS