For a Web2SIP scenario,the Call is Killed on the Web User Side while the Call is Running on the SIP Side
Last updated on JULY 19, 2017
Applies to:Oracle Communications WebRTC Session Controller - Version 7.1.0 and later
Information in this document applies to any platform.
A Lightweight Proxy Registrar with static Registration Mode and conditional Forking Mode is configured.
The problem is that with Firefox version 44, when doing a web2sip call, the Signaling Engine(SE) takes too much time to send the INVITE to the Session Border Controler(SBC).
Due to this, the call is killed on the web user side while the call is still running on the SIP side.
It is expected that SE should send the INVITE message much faster in order to avoid the call interruption.
In the engine log the following error message is seen:
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