Topup Fails As Duplicate In Diameter Gateway

(Doc ID 2086061.1)

Last updated on JUNE 21, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


On : version, Diameter Gateway


Topup is failing as duplicate in diameter gateway, while the first request is success.
The second request is failing as duplicate request even though it is not duplicate.
A different session-id and recharge reference number is being passed . The topup history count is set as 3.


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