top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

When to set Error 'E' bit in Diameter message?

+1 vote


I want to know in which scenario or which diameter messages can set the Error bit ('E') bit in request/response messages.
Also, How 'E' bit is set with Transient failures, Permanent failures and Protocol Errors.

Thanks in advance.

posted Mar 28, 2016 by Chinmoy Padhi

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

When processing of a Diameter request message fails, response message is sent with setting 'E' bit.
For example: If an AVP is unknown for the node, it sends error code comes under the permanent failure.
Since Diameter Answer message is carrying failure response, Experimental-Result-Code will carry "DIAMETER_INVALID_AVP_VALUE (5004)". 'E' bit is set in answer message when node finds a protocol error while processing request message.

answer Mar 28, 2016 by Vimal Kumar Mishra
Thanks Vimal for your answer. But I was confused with the RFC-6733 Section 7.2 it says The 'E' (Error Bit) in the Diameter header is set when the request caused a protocol-related error. So how can we set 'E' bit for transient and permanent failures.
Chinmoy, you are correct. Error bit is set when failure is related to protocol error. I will correct it. Thanks.
Similar Questions
+2 votes

Based on the 3GPP 29.272, the IDR (Insert-Subscriber-data Request message) is generated by the HSS to the MME to update the subscriber profile in the MME and/or requesting subscriber info such as location-information, subscriber state...
However the SUBSCRIPTION-DATA AVP containing the of profile to be added or updated is defined as Mandatory.
What should contain this AVP if the IDR is sent only for requesting subscriber-info without updating the subscriber profile.
Should ot be present without any nested AVP under it?

+1 vote

I was going through rfc3588 and could not understand when a Diameter Server/Agent adds Error-Reporting -Host AVP within the answer message.

+5 votes

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

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 ?