New Features

The S-Cz8.2.5 release of the Oracle Communications Unified Session Manager (OCUSM) supports the following new features and enhancements.

The OCUSM 825 Release adds OCSBC 820 functionality. Please refer to OCSBC 8.2.0 Release Documentation for the product details. It may be possible that OCUSM use cases differ from OCSBC use cases. Therefore, it is recommended to validate the applicable scenarios in the lab environment before a field deployment.

ODI Preservation

As the Oracle Communications Unified Session Manager (OCUSM) works through dialogs with Application Servers (AS), it saves and uses the Original Dialog Indicator (ODI) parameter to manage a call's service subscription sequence. By default, the OCUSM deletes the in-memory Service Profile, including the ODI, on receiving a final response to a transaction with an AS. If you enable the preserve-odi parameter in the sip-config however, the OCUSM maintains the in-memory service profiles, and each associated ODI, until it receives the BYE from the AS that ends the dialog between them. This is a global configuration, causing the OCUSM to maintain all ODIs for the duration of the dialog.

See the SIP Call section in this Essentials Guide.

Making Key Information sent to OCOM Anonymous

The OCUSM allows you to hide the information presented in the SUBJECT headers and MIME body in INVITE and/or MESSAGE methods before sending the packets for analysis to Oracle Communications Operation Manager (OCOM). You do this by configuring the anonymize-invite and/or the anonymize-message options in the comm-monitor element. This provides an extra layer of security for Chat and SIP sessions.

See the explanation and configuration procedure on this feature in the References and Debugging chapter of this Essentials Guide.