MT Voice Calls did not Connect and Failed to Complete in ECE
(Doc ID 2170258.1)
Last updated on MARCH 24, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Diameter Gateway
In an ECE setup, MT voice calls did not connect , so failed to complete while it was expected that all MT calls should be free and call must connect even if there was no credit balance or free bucket available.
AVP (Role of Node) was set as 1 (i.e. MT) in INITIATE request but ECE treated this as MO or normal call and worked accordingly. So it tried to give quota and checked credit balance available and as it was zero it threw Credit Breach error.
INITIATE (CCR and CCA given below):
How to resolve this?
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