My Oracle Support Banner

OCSC Does Not Terminate The Call When <max-active-session-duration> Is Reached (Doc ID 2298400.1)

Last updated on NOVEMBER 21, 2019

Applies to:

Oracle Communications Service Broker - Version and later
Information in this document applies to any platform.


Setting <max-active-session-duration>50</max-active-session-duration> and keep <max-call-duration-timeout-interval-minutes>900</max-call-duration-timeout-interval-minutes>.

Run the following test:

      The call started at '2017-07-27 11:35:46'. 
      And "Session duration timer expired, forcefully stopping actor" can be seen in log at '2017-07-27 11:36:36'.

      2017-07-27 11:36:36,188 DEBUG ActorDistributedCacheWorker:6 SessionActor - [SID:<SID>][APP:framework][DEBUG][com.convergin.specific.axia.framework.mediation.impl.SessionActor$SessionDurationTimer.onEvent():372][Session duration timer expired, forcefully stopping actor]

      But Actually the call is not disconnected by OCSC. OCSC doesn't send the Camel (abort or end) since OCSC has unregisterred the sccp event.  MSC and NCC don't know the call is ended, so the call is not ended immediately. Finally, the call is ended by MSC because of no answer timeout after 10 seconds.  And the customer is still being charged in the 10 seconds.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.