Incorrect User Identity Retrieved From SLR Subscription-Id And Used For Lookup
(Doc ID 2640361.1)
Last updated on FEBRUARY 24, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
- In a customer implementation of Elastic Charging Engine and Diameter Gateway, the Diameter Sy flows are working fine with current Core Network i.e., Ericsson EPG-Evolved Packet Gateway, but failing on Nokia CMG-Cloud Mobile Gateway.
- The reason for this issue was identified to be; Sy SLR (Spending-Limit-Request) message from CMG has Subscription-Id fields in different order compared to EPG, i.e., customer lookup is done on IMSI (International Mobile Subscriber Identity) rather than on MSISDN (Mobile Station International Subscriber Directory Number) (END_USER_E164).
- Seems like handling of Sy is missing same procedure as Gy is having, i.e., to specify which Subscription-Id shall be used for customer lookup.
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