Diameter Gateway - Support Of Multiple Subscriber-Id AVPs In ECE
Last updated on AUGUST 24, 2016
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The CCR (Credit Control Request) provided by the network cannot be sorted with the MSISDN set on Subscription-Id on the first position.
If the request starts with an Subscription-Id with the IMSI which is followed by MSISDN, the ECE is not able to identify the customer. But if the request starts with the Subscription-Id with MSISDN and followed by IMSI, it works fine.
The order cannot be sorted by the network and the order of the information provided to the diameter gateway cannot be sort with the MSISDN first.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms