top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

How does a diameter node treat result code "limited success" in answer message ?

+4 votes
4,387 views

I am not able to understand the significance of "limited success" in a answer message and also want to know what a diameter node does when it receives this limited success within a answer message ?

posted Dec 31, 2014 by Harshita

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
From RFC3588:
DIAMETER_LIMITED_SUCCESS           2002
      When returned, the request was successfully completed, but
      additional processing is required by the application in order to
      provide service to the user.

1 Answer

+1 vote

Limited success is returned when one operation is expected from server after processing a request. For an example in case of Gy RAR flow, if RAR is triggered from OCS towards CTF(PCEF) , it is expected that the CTF will again trigger one update CCR towards OCS for re-authorization after sending back RAA.

answer Apr 20, 2017 by anonymous
Similar Questions
0 votes

I know Diameter client can re-transmit the request message until it receives the answer message.
But what about when a Diameter node has sent answer message to the last received request from its peer and that's is not received but its peer. In this case, from Diameter client node transaction is not completed since it did not receive answer message but from other node point of view it has responded with answer and transaction is completed.

+3 votes

I'm doing some integration toward Gy client (PCEF), and encountered an unclear area. I'm not sure if it is unclear in RFC 4006 or the 3GPP TS32.299 or both.

Scenario: A user logs on. The user has no credit left for a rating-group 42.

CCR-initial and CCA-initial:
Nothing interesting. In Gy it is typically just "empty" requests for the purpose of registering the user session.

The user then attempts to use rating-group 32:

CCR-update:

 Multiple-Services-Credit-Control {
 Rating-Group = 42
 Requested-Service-Unit {
 }
 }

to which the OCS (Gy server) would normally respond:

CCA-update:

 Result-Code = 2001 (success)
 Multiple-Services-Credit-Control {
 Rating-Group = 42
 Result-Code = 4012 (credit-limit-reached)
 Final-Unit-Indication {
 ...
 }
 }

However, the Gy specification says that a zero-grant is needed, which to me sounds a bit odd, but nevertheless:

Result-Code = 2001 (success)
 Multiple-Services-Credit-Control {
 Rating-Group = 42
 Result-Code = 4012 (credit-limit-reached)
 Granted-Service-Unit {
 CC-Total-Octets = 0
 }
 Final-Unit-Indication {
 ...
 }
 }

Now, the Gy client vendor says that the result-code inside the MSCC must be 2001 (success). It sort of makes sense because there is a grant.

But that made me wonder: In which case would result-code=4012 make sense? Is it just 3GPP who has "mangled" diameter-credit-control in the Gy application?

+6 votes

Can someone please explain difference between these two. Could both Result-Code and Experimental-Result AVPs be used in same diameter or only one of them is allowed ?

+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.

...