Diameter Errors

There are two type of errors in diameter
1. Protocol Errors :- These are the errors that occours at protocol level (mostly at Transport layer) such as link break, Node Rebooted etc. while handling these errors, Bit-E of the diameter answer message must be set.


Example of Protocol Error

2.Application Error:- These errors occour while the diameter application processing the message it has received, such as unknown avp, invalid Avp value etc. These errors fall in the categories where diameter node has properly received the message while the protocol errors fall in categories where diameter node unable to receive the message.

Example to Application Error
Result code AVP are use to report both type of error along with some other avp to give the description of the error. The decimal values of the result code avp are divided in to following
- 1xxx (Informational)
- 2xxx (Success)
- 3xxx (Protocol Errors)
- 4xxx (Transient Failures)
- 5xxx (Permanent Failure)



Your Comments /Suggestions and Questions are always welcome.I would try to clarify doubts with best of my knowledge. So feel free to put Questions.

19 comments:

  1. Can you please suggest me an implementation of pure java diameter protocol used for offline charging?

    ReplyDelete
  2. can you please provide a list of error codes for diameter protocol

    ReplyDelete
    Replies

    1. Following Link might help you.

      http://diameter-protocol.blogspot.in/2012/10/list-of-experimental-result-codes.html


      Happy to help you again.
      Team-Diameter

      Delete
  3. Hi Anonymous you can find all the error codes in RFC 6733 from page 90
    http://tools.ietf.org/search/rfc6733

    ReplyDelete
  4. Hi all,
    I have received a Result-Code of 5030 (DIAMETER_USER_UNKNOWN). That's why the session is terminated and I cannot send an UPDATE CCR.
    What can i resolve this problem ??
    thanks in advanced.

    ReplyDelete
    Replies
    1. Hi Amal,

      It is totally application dependent issue. You are trying to create session for Invalid User Identity. If you want exact solution from us, kindly share complete scenario.

      Thanks for your query.

      Happy to help you again.
      Team-Diameter

      Delete
  5. i am getting 4998 while sending CCR ,what doest it means Please advice

    ReplyDelete
    Replies
    1. Basically you get 4998 as error code if something of the AVP required is Missing or not properly formed

      Delete
  6. In Gy (online charging) interface, If Diameter Proxy responses CCR with 3002 Result-code in CCA, what other AVP should it place into that CCA, except Sesion-ID, Origin-host, -realm and that Result-code?
    Has it to put CC-Request-Type and CC-Request-Number in CCA, as it is required by 3GPP TS 32.299? And where is it specified?
    Thanks.

    ReplyDelete
  7. I have RFC Cause: DIAMETER_INVALID_AVP_VALUE, but after this failure UE do not return to LTE, just stay in UMTS but in UMTS UE cannot create PDP because cause "regular deactivation", any commnets about that.

    ReplyDelete
    Replies
    1. Hi Andres


      Kindly share diameter where you have observed DIAMETER_INVALID_AVP_VALUE. so that we could suggest possible causes.

      Thanks for your query.
      Happy to help you again.
      Team-Diameter


      Delete
  8. Hi,
    we received multiple times Diameter_unable_to deliver errors.what is the cause of it?

    ReplyDelete
  9. Diameter_unable_to deliver ---> It could be because of some AVP is missing...like Diameter Host AVP or some other AVP...

    ReplyDelete
  10. Hey,

    We are trying to configure SigScale OCS on our LTE equipment in University Lab. In Credit-Control Answer, we are getting DIAMETER_USER_UNKNOWN result code.
    Is User identity ISMI of the UE?

    Kindly guide how to resolve this.

    Thankyou.

    ReplyDelete
    Replies
    1. Hi RajatChopra,

      Hope following points shall help you.

      1) DIAMETER_USER_UNKNOWN comes back in response when user Identity in not present in server. [In general User Identity is exchanged in User-Name Avp,in LTE it contains IMSI.]

      2) Please check following AVP of CCR message that you have sent to OCS;; to identify user-identity being used for further processing. The Identity that is being sent OCS, OCS must have subscription data for that identity.

      Subscription-Id ::= < AVP Header: 443 >
      { Subscription-Id-Type }
      { Subscription-Id-Data }
      --> Subscription-Id-Type :: tells about type of identity.
      END_USER_E164 (MSISDN), END_USER_IMSI (IMSI),END_USER_SIP_URI (sip uri), END_USER_NAI (Network Access Identifier), END_USER_PRIVATE

      --> Subscription-Id-Data :: actual value of identity based on type selected.

      Please refer following section for more details.
      https://datatracker.ietf.org/doc/html/rfc8506#section-8.46


      3) Please refer section -7, RFC 8506, Page 50, Para-3rd from top
      https://datatracker.ietf.org/doc/html/rfc8506#section-7

      4) Please check at OCS what all identity types are supported.


      Thanks for your query
      Happy to help you agian.
      Team-Diameter

      Delete
  11. We are facing Gy successful rate is about 50%. The failure cause code contributor is 5030 (DIAMETER_USER_UNKNOWN) in the network.

    ReplyDelete
  12. can i get the solution , how to clear this issue

    ReplyDelete