Corporation Server User Manual

3GPP/Rf Diameter Java API
A-6 Oracle Communication and Mobility Server Developer’s Guide
int Accounting-Record-Number,
String roleOfNode,
String userSessionId,
String callingPartyAddress,
String calledPartyAddress)
■ Accounting-Answer (ACA)--The first following method creates a basic ACA (with
only mandatory AVPs) and the second one creates a more sophisticated ACA with
the most used AVPs as defined in 3GPP:
■ Diameter Message
createAccountingAnswer (String Result-Code,
int Accounting-Record-Type,
int Accounting-Record-Number)
■ Diameter Message
createAccountingAnswer (String Result-Code,
int Accounting-Record-Type,
int Accounting-Record-Number,
String roleOfNode,
String userSessionId,
String callingPartyAddress,
String calledPartyAddress)
3GPP/Rf Dictionary The 3GPP Rf Interface dictionary is returned by getRfDictionary()
and must be extended by the Diameter stack.
Rf Events
Like any Diameter application, an Rf application can receive/send accounting events
from/to the Diameter stack.
Process Event To receive an accounting event from the Diameter stack, user has to
implement the processEvent(DiameterEvent) callback in the DiameterRfListener
implementation.
The list of the possible received accounting events are the following ones:
■ DiameterTimeoutEvent(Object, DiameterSession, int): This event is generated by
the Diameter implementation when one of the session timers elapses. The different
reasons to trigger an event for the Rf Interface are:
■ SESSION_TIMEOUT_EXPIRED: The event is triggered by the stack on session
supervision timer expiration
■ TX_TIMEOUT_EXPIRED: The event is triggered by the stack on session
supervision timer expiration.
■ INTERIM_TIMEOUT_EXPIRED: The event is triggered when the time
specified by the interim interval duration has expired.
■ DiameterServiceEvent(Object, DiameterSession, int): This event is generated by
the Diameter implementation when one service is finished. The different reasons
to trigger an event for the Rf Interface are:
■ TERMINATE_SERVICE: The event is triggered by the stack when service is
terminated by the stack or by server.
■ DiameterInvalidMessageReceivedEvent(Object, DiameterSession, Message): This
event is triggered by the stack when an invalid message has been received. This
event object contains the invalid received message.