Here is the scenario in our Customer environment :
For VoLTE Gx environment, our Customer use Cisco PGW, Oracle DRA and Openet PCRF.
Their DRA has sessions/subscribers database.
In order to avoid ghost sessions on DRA, they have implemented a feature to send RAR message to PGW from DRA to have a confirmation that the user is still using the services and the session is still alive.
As per PCEF (ims-auth service) current design is :
- in a DRA setup, RAR from any origin-host is accepted
- in non-DRA setup RAR is accepted only from configured peer
The PCEF (ims-auth service) consider the setup as DRA or non-DRA based on the origin-host received in CCA-I or RAR.
DRA setup = If the Origin-Host received in CCA-I/RAR is not the same as the directly connected/configured peer (in diameter-endpoint). The DRA mode is selected by PCEF and we accept RAR from any origin-host.
Non DRA setup = If the Origin-Host received in CCA-I/RAR is the same as the directly connected/configured peer. The non DRA mode is selected by PCEF and we accept RAR only from primary or the secondary server of the selected row in the diameter host-select table.
The Problem is :
• When the origin-host is changed using RAR, and it is now the
same as the directly connected/configured peer ,the directly connected peer is not considered as a DRA from PCEF perspective.Then when the RAR received from a different peer than the one configured, is rejected.
• It also the same case for CCR-T which is sent to the new origin-host received in the RAR .
Please could you advise some best practice so that PGW (PCEF) accept RAR sent from any origin host ?
Kindly,
