CDR Archiving

In an overload of CDRs scenario, the CGF server becomes slow in providing a response. This scenario leads to unacknowledged CDRs due to sendReqList buffer being full and then the CDRs drop. To avoid the CDR drop in such a case, the GTPP endpoint enqueues new CDRs into the archive list.

GTPP performs the CDR archiving in the following way:

  • The archive list flush happens in a paced manner depending on the network load condition.

  • After all the CGFs become inactive or due to back-to-back switchovers, an archive record is written into HDD in the paced manner to avoid losing the archived CDRs.

  • Archive list is replicated on standby GTPP endpoint pod.

Note
  • The archive list is maintained per GTPP profile level. The maximum size of the archive list is 5M.

  • After reaching the maximum configured size, the oldest record is purged and a new record is added.

  • Archive list gets replicated on the standby pod. When the active pod is inactive, the standby pod becomes the active pod and starts processing the CDRs to retain all the archive records.