Information About AVPs Not Supported In Diameter Gateway
Last updated on DECEMBER 14, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
In diameter gateway documentation, the AVPs are listed as 'supported' and 'not supported'. The 'not supported' AVPs are not present in the dictionary_main.xml file. What exactly does 'not supported' mean?
Is it not possible to use these AVPs in the incoming request? Is there any way to make some of the AVPs supported?
Problem is that as per NCC interface document, there are some AVPs which are expected to come as part of voice call session but these AVPs are not supported as per Diameter Gy Protocol documentation.
eg: AVPs like VCS-Information, Bearer-Capability, MSC-Address, ISUP-Location-Number, VLR-Number.
So even though some of the AVPs are not used for the rating purpose, those are still expected to reach diameter gateway. What should be done in this case?
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