DIAMETER: When this error code (DIAMETER_UNABLE_TO_COMPLY 5012) will prompt up?

Question

I think any developer or tester can help me for this.

DIAMETER_UNABLE_TO_COMPLY 5012
This error is returned when a request is rejected for unspecified reasons. For sayings an unspecified reasons is very easy but as a tester if i want to verify this error code. How can i make it possible. How can i create this scenario?

For developer also it is difficult. Mostly all the scenario has been covered by RFC's. So for development as well as for testers this could be a challenge to generate/ test this error code. Can anybody share some words on this ?

Answer 1

We have seen servers returning this error when unable to process the request due to server side issues. One standard example is, 3GPP 29.228 (Cx/Dx) says HSS should return this error when it is unable to process a request e.g., due to internal database errors.

Answer 2

You could achieve it on the CER/CEA level. I would say If the receiver of the CER is unable to comply with what is in the request (different capabilities), it should send a CEA with the Result-Code AVP set to DIAMETER_UNABLE_TO_COMPLY.

From the RFC 6733, maybe you could block session removal which should lead to sending the ASA with cause code you look for.

8.5.2. Abort-Session-Answer (ASA)
[...]
If the session identified by Session-Id in the ASR was successfully terminated, the Result-Code is set to DIAMETER_SUCCESS. If the session is not currently active, the Result-Code is set to DIAMETER_UNKNOWN_SESSION_ID. If the access device does not stop the session for any other reason, the Result-Code is set to DIAMETER_UNABLE_TO_COMPLY.

Comments

Thanks for your answer.

I thought for both scenarios that you have suggested to me, but i am in same condition without conclusion. Like in CER/CEA level what can be the different capabilities. For every reason there is an error code. If i am adding unknown application-id it is giving 5010, If inband security mismatch then no common security error. Likewise every scenario has one different error. Further in second response where device does not stop the session. How it is possible in real scenario. If i am a tester and want to create this. I don't think any traffic generator tool would be able to create this. All valuable inputs would be welcome.

Answer 3

One more I recently faced..

Lest say you have working OCS or/an PCRF template - you are sending what the other side is expecting and replying to.
If so, then remove one AVP from Initial/Interim/terminate (depends on scenario, if basic then I suggest Initial) and start a session. This will give you Diameter Unable To Comply 5012

Comments

Thank you..!!

---

Answered By: Dhaval Vala.
---------------
If we configure Action for particular request as 'Drop Request' for particular Ruleset and When PCRF get Diameter Initial/Update/Terminate request, then in CCA we can have Result-Code = 'DIAMETER_UNABLE_TO_COMPLY (5012)'.

---

Hi Bart, if we remove AVP from our CCR-initial message as you suggested ,it throws DIAMETER_MISSING_AVP(5005), In this case from CCR-I message I have removed the "Auth-Application-id".