diameter2 Configuration Objects
RequestReject
RequestReject service configuration can be used to send an error code to reject a session during initial attach or update when certain condition (such as, APN-RAT combination) is met.
|  Note | The RequestReject service configuration functionality remains the same whether the policy configuration is CRD based or not. For explanation purposes, CRD based functionality is described in this section. | 
This configuration has two attributes, ErrorCode and IsExperimentalErrorCode and values to these two attributes gets populated using result column of STG (output columns of CRD).
|  Note | Error-Code is a Number type column and IsExpermentalErrorCode is a Boolean type column. | 
CRD table gets evaluated with retrievers/request bindings (such as, APN, RAT-TYPE, Cmd-Code, application-id, Request-Type) done at CRD level and gives ErrorCode and IsExperimentalErrorCode as derived output. Based on this ErrorCode, CPS sends the response message. If no Error-Code is derived, then CPS behaves normally.
CPS logs a counter for each request rejection. For this a new statistics, <InterfaceName>_<RequestType>_policy_driven_rejection_<ResultCode> has been added.
| Parameter | Description | ||
|---|---|---|---|
| Priority | |||
| Diameter Client | |||
| Error Code | Value of this field is pulled from the CRD output column which is of type Number (need to configure pull value from column to map to a result column of the CRD table), which represents the error code that needs to be sent in response. Default value of Error Code is 0. 
 | ||
| Is Experimental Error Code | Value of this field is pulled from the CRD output column which is of type Boolean (need to configure pull value from column to map to a result column of the CRD table), which represents how CPS has to send the Error Code in response either through Result-Code AVP or 'Experimental-Result-Code' grouped AVP. Default value is false that means CPS sends an error code in response through Result-Code AVP. | 
ResetDiameterSession
ResetDiameterSession service configuration is used to release the primary Gx session of the subscriber when primary Gx session has released all the other secondary sessions gracefully.
| Parameter | Description | ||
|---|---|---|---|
| Priority | |||
| Diameter Client | |||
| Protocol | Currently, GX_TGPP is the only protocol supported. 
 | ||
| Release Cause | Reason for aborting Gx session. Default value is UNSPECIFIED_REASON(0). The following release causes are supported: 
 | 
 Feedback
Feedback