Session Expired During Long Call Duration
Last updated on SEPTEMBER 22, 2016
Applies to:Oracle Communications Service Broker - Version 3.1.1 to 3.1.1 [Release 3.1.0]
Information in this document applies to any platform.
***Checked for relevance on 07-Jul-2013***
During long call (more than 30 min.) duration the session expired with error in the log.
The expiration of session is causing abnormal call release (for example not propagating oDisconnect message to SIP AS side as SIP BYE message) and as result increasing number of TCAP Aborts.
The error appearing in the log:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms