1. Essentials Guide
  2. Oracle USM Supporting the IMS Core
  3. User Authorization
  4. UAR/UAA Transaction

UAR/UAA Transaction

Before requesting authentication information, the Oracle Communications Unified Session Manager sends a User Authorization Request (UAR) to the HSS for the registering endpoint to determine if this user is allowed to receive service. The Oracle Communications Unified Session Manager populates the UAR’s AVPs as follows:

  • Public-User-Identity—the SIP AOR of the registering endpoint
  • Visited-Network-Identity—the value of the network-id parameter from the ingress sip-interface.
  • Private-User-Identity—the username from the SIP authorization header, if it is present. If not, this value is the public User ID.
  • User-Authorization-Type—always set to REGISTRATION_AND_CAPABILITIES (2)

The Oracle Communications Unified Session Manager expects the UAA to be either:

  • DIAMETER_FIRST_REGISTRATION
  • DIAMETER_SUBSEQUENT_REGISTRATION

Any of these responses result in the continued processing of the registering endpoint. Any other result code results in an error and a 403 returned to the registering UA (often referred to as a UE). The next step is the authentication and request for the H(A1) hash.