This chapter explains how to protect Oracle Communications Service Control by detecting 'dead/inactive' sessions earlier and purged the 'dead/inactive' sessions instead of waiting the max_session_duration. theoretically the feature is available for all signalling protocols e.g. diameter, ss7, sip. especially fit for long duration diameter sessions as customer requires to purge the 'dead/inactive' sessions.
An optional keepAliveSessionDuration configuration is added to implement the feature. The keep alive session timer is independent of maximum call duration timer. customer can optionally use both keep alive session timer and maximum call duration timer or only use one of them.
Note:
the keep alive session timer or maximum call duration timer can be disabled by setting a zero or negative value (e.g. -1).The keep alive session timer is independent of maximum call duration timer. Customer can optionally use both keep alive session timer and maximum call duration timer or only use one of them. while we usually suggest customer to disable the max call duration timer then only utilize the keep alive session timer to do the housekeeping for long duration data services:
set maxActiveSessionDuration = -1 to disable the max call duration timer in PN Framework and IM modules.
take PN Framework for an example:
http://${PN_Admin_IP}:${PN_Admin_Port}/axiaConsole
Goto Configuration MBeans -> com.convergin.wcs.osgi.framework.pn.impl -> 6.2.0 -> maxActiveSessionDuration
Set maxActiveSessionDurationz: -1 //disable the maxActiveSessionDuration timer. (ie. only use the keep alive session timer to do housekeeping)
add the keepAliveSessionDuration configuration
http://${PN_Admin_IP}:${PN_Admin_Port}/axiaConsole
Goto Configuration MBeans -> com.convergin.wcs.osgi.framework.pn.impl -> 6.2.0 -> addKeepAliveSessionDuration
Click to execute Then you will see newly added mbean attribute "keepAliveSessionDuration"
Set value of keepAliveSessionDuration in seconds(e.g. 21600s, 6h)
The implementation has set an initial delay(20s) for the periodic keep alive session timer. So the predicted maximum 'delayed' inactive session detection is 20s + 2keepAliveSessionDuration. e.g. if customer set the keepAliveSessionDuration = 21600s. the inactive session maybe clean up in 20s+2*21600s = 43220s later.