Destination-Host AVP in ACR Message

This chapter describes the following topics:

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

ECS

Applicable Platform(s)

  • ASR 5500

  • VPC-DI

  • VPC-SI

Feature Default

Enabled - Always-on

Related Changes in This Release

Not Applicable

Related Documentation

ECS Administration Guide

Revision History


Important

Revision history details are not provided for features introduced before releases 21.2 and N5.1.

Revision Details

Release

In this release, the ACR message (acct-record-number=x) that is sent to the OFCS server will not have the Destination-Host AVP where its previous interim message (acct-record-number=x-1) is written into HDD. Instead, it follows the day-1 behavior like archiving request message.

21.4

First introduced.

Pre 21.2

Feature Changes

After powering off Charging Collection Function (CCF) servers, the P-GW is not sending the destination host in the interim accounting messages. The returned failure message DIAMETER_UNABLE_TO_DELIVER (3002) keeps incrementing until an SRP switchover is performed. This issue is seen when the P-GW does not send the destination host in the interim accounting message when a previous interim message is written to the hard disk drive (HDD).

Previous Behavior

The accounting-request (ACR) message (acct-record-number=x) that is sent to the Offline Charging System (OFCS) server has the Destination-Host AVP where its previous interim message (acct-record-number=x-1) is written to the HDD.

New Behavior

The ACR message (acct-record-number=x) that is sent to the OFCS server will not have the Destination-Host AVP where its previous interim message (acct-record-number=x-1) is written into HDD. Instead, follows the day-1 behavior like archiving request message.

This behavior is applied for a single server and multiple server configuration, Session Recovery scenario, and ICSR scenarios.

Impact on Customer

The new behavior is seen where the HDD is used as the RF interface.