Credit Authorization with Direct Debiting
12.6.1 Handling Re-Auth-Request Messages
The OCS may initiate credit re-authorization by issuing a Re-Auth-Request RAR to the CTF. The application can register a session listener for handling this type of request. Upon receiving a RAR, the Diameter subsystem invoke the session listener on the applications corresponding RoSession object. The application must then respond to the OCS with an appropriate RAA message and initiate credit re-authorization to the CTF by sending a CCR with the CC-Request-Type AVP set to the value UPDATE_ REQUEST, as described in section 5.5 of RFC 4006 http:www.ietf.orgrfcrfc4006.txt . A session listener must implement the SessionListener interface and be serializable, or it must be an instance of SipServlet. A Servlet can register a listener as follows: RoSession session = roApp.createSession; session.addListenernew SessionListener { public void rcvMessageMessage msg { System.out.printlnGot message: id = msg.getSession.getId; } }; Example 12–4 shows sample rcvMessage code for processing a Re-Auth-Request. Example 12–4 Managing a Re-Auth-Request RoSession session = roApp.createSession; session.addListenernew SessionListener { public void rcvMessageMessage msg { Request req = Requestmsg; if req.getCommand = Command.RE_AUTH_REQUEST return; RoSession session = RoSession req.getSession; Answer ans = req.createAnswer; ans.setResultCodeResultCode.LIMITED_SUCCESS; Per RFC 4006 5.5 ans.send; CCR ccr = session.createCCRRo.UPDATE_REQUEST; ... Set CCR AVPs according to requested credit re-authorization ccr.send; CCA cca = CCA ccr.waitForAnswer; } In Example 12–4 , upon receiving the Re-Auth-Request the application sends an RAA with the result code DIAMETER_LIMITED_SUCCESS to indicate to the OCS that an additional CCR request is required in order to complete the procedure. The CCR is then sent to initiate credit re-authorization.12.7 Sending Credit-Control-Request Messages
The CCR class represents a Diameter Credit-Control-Request message, and can be used to send credit control requests to the OCF. For both ECUR Event-Based Charging Note: Because the Diameter subsystem locks the call state before delivering the request to the corresponding RoSession, the call state remains locked while the handler processes the request.Parts
» Oracle Fusion Middleware Online Documentation Library
» Multiple Responses SIP Servlets Versus HTTP Servlets
» Receiving Responses SIP Servlets Versus HTTP Servlets
» Proxy Functions SIP Servlets Versus HTTP Servlets
» Servlet Request Message Body
» Servlet Response Message Body
» Application Management Role of a Servlet Container
» Sends a 200 response to the CANCEL request.
» Sends a 487 response to the INVITE request to be cancelled.
» Invokes a doCancel method on the SIP servlet. This allows the application to
» Utility Functions Role of a Servlet Container
» Overview of Converged Applications
» Assembling and Packaging a Converged Application
» Using the Converged Application Example
» Overview of Header Format APIs and Configuration Summary of Compact Headers
» Assigning Header Formats with WlssSipServletMessage
» Summary of API and Configuration Behavior
» Overview Generating SNMP Traps from Application Code
» Requirement for Accessing SipServletSnmpTrapRuntimeMBean
» Obtaining a Reference to SipServletSnmpTrapRuntimeMBean
» Overview of Developing Distributed Applications
» Applications Must Not Create Threads
» Servlets Must Be Non-Blocking
» Store all Application Data in the Session
» All Session Data Must Be Serializable
» Use setAttribute to Modify Session Data in “No-Call” Scope
» Mark SIP Servlets as Distributable
» Session Expiration Best Practices
» Observe Best Practices for Java EE Applications
» Application Composition Model Oracle Fusion Middleware Online Documentation Library
» Using the Default Application Router
» Configuring a Custom Application Router
» Session Key-Based Request Targeting
» Overview of SIP Servlet Security
» Role Mapping Features Oracle Fusion Middleware Online Documentation Library
» Using Implicit Role Assignment
» Important Requirements Assigning Roles Using security-role-assignment
» Assigning run-as Roles Role Assignment Precedence for SIP Servlet Roles
» Debugging Security Features weblogic.xml Deployment Descriptor Reference
» Specifying a Predefined Logging Level
» Customizing Log Records Enabling Message Logging
» Overview Specifying Content Types for Unencrypted Logging
» Example Message Log Configuration and Output
» Configuring Log File Rotation
» Diameter Protocol Packages Oracle Fusion Middleware Online Documentation Library
» File Required for Compiling Application Using the Diameter API
» Implementing a Diameter Application
» Sending Request Messages Sending Answer Messages
» Creating New Attributes Working with AVPs
» Working with Diameter Sessions Creating Converged Diameter and SIP Applications
» Overview of Profile Service API and Sh Interface Support
» Enabling the Sh Interface Provider
» Using a Constructed Document Key to Manage Profile Data
» Prerequisites for Listener Implementations
» Implementing ProfileListener Monitoring Profile Data with ProfileListener
» Overview of the Profile Service API
» Implementing Profile Service API Methods
» Mapping Profile Requests to Profile Providers
» Configuring Profile Providers Using the Administration Console
» Overview of Rf Interface Support
» Understanding Offline Charging Events
» Configuring the Rf Application
» Specifying the Session Expiration Sending Asynchronous Events
» Accessing the Rf Application Implementing Event-Based Charging
» Using the Accounting Session State
» Overview of Ro Interface Support
» Credit Authorization with Unit Determination
» Credit Authorization with Direct Debiting
» Determining Units and Rating
» Configuring the Ro Application
Show more