A SIP Servlet can be configured to use one of the following identity assertion mechanisms:

• P-Asserted-Identity: With this mechanism, identity must be asserted using the P-Asserted-Identity header in a SIP message that originates from a trusted domain. This identity assertion mechanism is described in RFC 3325.

• Identity: With this mechanism, identity must be asserted using the Identity and Identity-Info headers in SIP messages, which can originate from other domains. This identity assertion mechanism is described in RFC 4474.

Converged Application Server does not support the WebSocket identity assertion mechanism.

You specify the identity assertion mechanism in the @SipLogin annotation inside an @SipApplication annotation. The @SipLogin annotation element determines which identity assertion mechanism is required for the Servlet. See the JSR 359, section 22.3.3 for information @SipApplication annotation, and information on configuring the identity assertion for a Servlet. See JSR 359, section 22.3.3.1 for information on @SipLogin annotation.

Converged Application Server supports identity assertion mechanisms using security providers. The sections that follow describe how Converged Application Server handles messages with each identity assertion mechanism, and how to configure the required security providers.