Registration Response with the Authentication-info Header

The Oracle Communications Unified Session Manager can include the authentication-info header, as described in RFC 2617, in its 200 OK response to REGISTERs when using SIP digest. The user enables this functionality using a sip-registrar option.

By default, the Oracle Communications Unified Session Manager supports registration with SIP digest authentication without using the authentication-info header. This is not compliant with TS 24.229. Enabling the add-auth-info option causes the Oracle Communications Unified Session Manager to calculate and insert the required authentication-info header fields in the 200 OK.

The Oracle Communications Unified Session Manager also presents this authentication header during third party registrations. The system includes the entire 200OK message in the third party registration request.

This authentication state is not shared across high availability nodes. The user can expect the Oracle Communications Unified Session Manager to request re-authentication by registering UEs after failover to a backup Oracle Communications Unified Session Manager.

Authentication-Info header field parameters sent by the Oracle Communications Unified Session Manager include:

• qop—Matches the qop sent by the UE
• rspauth—A response-digest calculated as described in RFC 2617
• cnonce—Matches the cnonce sent by the UE
• nonce-count—Matches the nonce-count sent by the UE

The nextnonce authentication-info header field parameter, which can request a new nonce for subsequent authentication responses from the UE, is not implemented on the Oracle Communications Unified Session Manager.

The ACLI syntax for enabling the add-auth-info option follows.

ORACLE(sip-registrar)#+options=add-auth-info enabled

The Oracle Communications Unified Session Manager provides NOTICE level log entries in log.sipd to indicate this option's status.