Overview

The customer raises a request that RAR(Reauthorization Request) is not working. Some of the errors reported are:

17 Jun 2022 14:52:37,009 [DEBUG] PCRF-101 [SRVC-HDLR]: Subscriber-Profile Handler execution started for Core Session ID: bgl-ras-bng-bge-02;0000000000;0001714514;:Gx
17 Jun 2022 14:52:37,009 [ERROR] PCRF-101 [SUB-PROF-HDLR]: Rejecting invalid request. Reason: UserIdentity not found for identityAttribute CS.UserIdentity
17 Jun 2022 14:52:37,009 [DEBUG] PCRF-101 [SRVC-HDLR]: Subscriber-Profile Handler execution completed for Core Session ID: bgl-ras-bng-bge-02;0000000000;0001714514;:Gx
17 Jun 2022 14:52:37,009 [DEBUG] PCRF-101 [DIA-GROOVY-SCRIPT]: preSend of "BSNLUpdateDomainNamePCC_Plugin" for gateway = bgldra3.bsnl.in called
17 Jun 2022 14:52:37,009 [DEBUG] DIA-STACK-POOL-THR-23 [TGPP-UM-BUILDER]: Unable to set UsageMonitoringInfo.Reason: Usage-Monitoring-Info AVP not found from packet
17 Jun 2022 14:52:37,009 [DEBUG] PCRF-101 [PCRF-RES-LSNR]: No addOn found from PCRFResponse for Core-Session-ID:bgl-ras-bng-bge-02;0000000000;0001714514;:Gx, remove previously provided addOns from diameter session

Analysis

As per the analysis of the call traces, the Username of the RAR is received in "Sub.SubscriberIdentity" Attribute but PCC is expecting this to be in CS.UserIdentity AVP.

This is because of configured PCC Service Policy uses "CS.UserIdentity" AVP for mapping the username

This leads to the following error:

17 Jun 2022 14:52:37,009 [ERROR] PCRF-101 [SUB-PROF-HDLR]: Rejecting invalid request. Reason: UserIdentity not found for identityAttribute CS.UserIdentity

Solution

The recommended solution is to create another PCC Service Policy for RAR requests such as the one below:

After adding the new policy restart PCRF and verify if the calls are getting through.