Call detail record
William Wong (Talk | contribs) |
William Wong (Talk | contribs) |
||
| Line 48: | Line 48: | ||
* This HA refers to system with Primary host controller and Secondary host controller or Tmedia 1+1 system | * This HA refers to system with Primary host controller and Secondary host controller or Tmedia 1+1 system | ||
* In '''Text CDR only''' CDR Mode, CDR records will be present in both primary and secondary hosts, with gateway application active host storing actual content of the CDR record (i.e. nonzero Byte of CDR log file) | * In '''Text CDR only''' CDR Mode, CDR records will be present in both primary and secondary hosts, with gateway application active host storing actual content of the CDR record (i.e. nonzero Byte of CDR log file) | ||
| − | * In '''Radius CDR only''' CDR Mode, CDR records will be sent out to Radius server from gateway application active host only, with no CDR record in both | + | * In '''Radius CDR only''' CDR Mode, CDR records will be sent out to Radius server from gateway application active host only, with no CDR record in both hosts |
* In '''Text and Radius CDR''' CDR Mode, CDR records will be present in both primary and secondary hosts, with gateway application active host storing actual content of the CDR record and at the same time sending CDR record to Radius server | * In '''Text and Radius CDR''' CDR Mode, CDR records will be present in both primary and secondary hosts, with gateway application active host storing actual content of the CDR record and at the same time sending CDR record to Radius server | ||
* In '''Radius CDR with Text CDR fallback''' CDR Mode, CDR records will be sent out to Radius server from gateway application active host only. If Radius server is out of service, CDR records will be restored in both primary and secondary host machines, with gateway application active host storing actual content of the CDR record | * In '''Radius CDR with Text CDR fallback''' CDR Mode, CDR records will be sent out to Radius server from gateway application active host only. If Radius server is out of service, CDR records will be restored in both primary and secondary host machines, with gateway application active host storing actual content of the CDR record | ||
Revision as of 03:04, 28 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
Contents |
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.
- h323-conf-id for RADIUS and @{SessionId} for Text CDR
'Original Id is a 128 bits unique identifier used for Call Transfer records. Each call transfer outgoing legs has its own unique Id with its Original Id associated call legs (incoming+outgoing).
- h323-incoming-conf-id for RADIUS and @{OriginalSessionId} 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
Call Detail Records in High Availability (HA) Environment
- This HA refers to system with Primary host controller and Secondary host controller or Tmedia 1+1 system
- In Text CDR only CDR Mode, CDR records will be present in both primary and secondary hosts, with gateway application active host storing actual content of the CDR record (i.e. nonzero Byte of CDR log file)
- In Radius CDR only CDR Mode, CDR records will be sent out to Radius server from gateway application active host only, with no CDR record in both hosts
- In Text and Radius CDR CDR Mode, CDR records will be present in both primary and secondary hosts, with gateway application active host storing actual content of the CDR record and at the same time sending CDR record to Radius server
- In Radius CDR with Text CDR fallback CDR Mode, CDR records will be sent out to Radius server from gateway application active host only. If Radius server is out of service, CDR records will be restored in both primary and secondary host machines, with gateway application active host storing actual content of the CDR record
- In this HA environment, external CDR processing application must obtain CDR records from both primary and secondary hosts for processing
