1. Essentials Guide
  2. Oracle USM Supporting the IMS Core
  3. 3GPP Compliance
  4. P-Asserted-Id in Requests and Dialogs
  5. Non-trusted UE

Non-trusted UE

When a non-trusted UE sends an initial request for a dialog or a request for a standalone transaction to the Oracle Communications Unified Session Manager, the P-Asserted-Identity to be inserted in the outgoing request is formed as follows:

  • If the request does not have a P-Preferred-Identity header field or none of the P-Preferred-Identity header fields included in the request match any of the registered public user identities, then the Oracle Communications Unified Session Manager inserts the default Public-Identity in the outgoing P-Asserted-Identity header.
  • If the request includes one or more P-Preferred-Identity header fields which match the registered public user identities, then the Oracle Communications Unified Session Manager includes only the first P-Preferred-Identity header field.
  • If the request includes one or more P-Asserted-Identity header fields which do not match the registered public user identities, then the Oracle Communications Unified Session Manager inserts the default Public-Identity in the outgoing P-Asserted-Identity header.