DGW Response with RC=5031 Instead of RC=5030 for Customer in PORT_OUT State (210)
(Doc ID 2475561.1)
Last updated on MAY 10, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
After changing life cycle state for a customer to "Port Out", all data sessions are failing with reason code 5031 (DIAMETER_RATING_FAILED).
It has been noted that after the above change, old MSISDN number still has been visible in PublicUseridentity (PUI) cache.
Is this a problem or it is functioning as designed?
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