My Oracle Support Banner

DiameterGateway Returned DIAMETER_UNABLE_TO_COMPLY Instead of DIAMETER_USER_UNKNOWN (Doc ID 2321382.1)

Last updated on NOVEMBER 09, 2018

Applies to:

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

Symptoms

On :  11.3.0.1.0 version, Diameter Gateway

The user was trying to make a concept test sending an BALANCE-QUERY operation to DGW/ECE informing an nonexistence account.

Expected result:
--------------------
DGW/ECE should return DIAMETER_USER_UNKNOWN error code.

Actual result:
-----------------------
It returned DIAMETER_UNABLE_TO_COMPLY inside CCA response.

ERROR
-----------------------
Diameter Message: CCR
Version: 1
Msg Length: 264
Cmd Flags: REQ,PXY
Cmd Code: 272
App-Id: 4
Hop-By-Hop-Id: 400
End-To-End-Id: 2141931256
  Session-Id (263,M,l=37) = 596f75ff
  Origin-Host (264,M,l=22) = ece.example.com
  Origin-Realm (296,M,l=18) = example.com
  Destination-Realm (283,M,l=19) = example.com
  Auth-Application-Id (258,M,l=12) = 4
  Service-Context-Id (461,M,l=22) = 32260@3gpp.org
  CC-Request-Type (416,M,l=12) = EVENT_REQUEST (4)
  CC-Request-Number (415,M,l=12) = 0
  Event-Timestamp (55,M,l=12) = 3709465727 (Wed Jul 19 08:08:47 PDT 2017)
  Subscription-Id (443,M,l=40) =
    Subscription-Id-Type (450,M,l=12) = END_USER_E164 (0)
    Subscription-Id-Data (444,M,l=19) = 50699999999
  Requested-Action (436,M,l=12) = BALANCE_QUERY (5)
  ORA-Balance-Query-Mode (248,V,v=3512,l=16) = SUMMARY_MODE (1)

Diameter Message: CCA
Version: 1
Msg Length: 188
Cmd Flags: PXY
Cmd Code: 272
App-Id: 4
Hop-By-Hop-Id: 400
End-To-End-Id: 2141931256
  Session-Id (263,M,l=37) = 596f75ff
  Result-Code (268,M,l=12) = DIAMETER_UNABLE_TO_COMPLY (5012)
  Origin-Host (264,M,l=23) = ece.example.com
  Origin-Realm (296,M,l=19) = example.com
  Auth-Application-Id (258,M,l=12) = 4
  CC-Request-Type (416,M,l=12) = EVENT_REQUEST (4)
  CC-Request-Number (415,M,l=12) = 0
  CC-Session-Failover (418,M,l=12) = FAILOVER_SUPPORTED (1)
  Credit-Control-Failure-Handling (427,M,l=12) = RETRY_AND_TERMINATE (2)
  Direct-Debiting-Failure-Handling (428,M,l=12) = TERMINATE_OR_BUFFER (0)

STEPS
-----------------------
Run a test using an existent account  and nonexistence account to verify that the problem is not in the CCR sent.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.