P-Asserted-Identity Invisible To Sipservlet
Last updated on JUNE 19, 2018
Applies to:Oracle Communications Converged Application Server - Version 3.1.0 and later
Information in this document applies to any platform.
BEA Telco WebLogic SIP Server - Version: 3.1
On WebLogic SIP Server (WLSS) 3.1, with the P-Asserted-Identity header in the SipServlet checked, container does not dispatch the header to SipServlet in the Request messages.
By adding Trusted Authentication Hosts field, the P-Asserted-Identity headers take into effect but it is picked on all SIP deployments in the WLSS domain.
How to configure individual sipservlet dynamically during service initialization phase? Or how to configure the SipServlet to get the P-Asserted-Identity headers?
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