Trusted UE

When a 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 inserts the first P-Preferred-Identity header field.
• If the request includes one or more P-Asserted-Identity header fields, then the Oracle Communications Unified Session Manager will use the first P-Asserted-Identity header field.
  • The contents of the From header field do not form any part of this decision process.
  • P-Preferred-Identity header fields will always be removed.

The Default Public Identity is the first appearing, non-barred identity in the set of implicitly registered Public User Identities.

To enable this behavior, add the pai-comply-to-3gpp option in the sip config configuration element.