Recommendation Around Diameter Requests without AVPs which are Mandatory in Mediation Spec
(Doc ID 2271361.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Diameter Gateway
How to handle Diameter scenarios without AVPs which are mandatory in Mediation Spec ?
- Client will send to DGW, the Diameter traffic that only in Initial request an incoming message will contain all mandatory AVPs which are needed to Event Type detection via Mediation Spec.
- In Updates and Terminate (for SCUR sessions) the messages will not contains:
- Subscription-Id AVP Group
and location information (MCCMNC in custom AVP).
How to manage those traffic scenarios and properly match into ECE event Type?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document