1. Essentials Guide
  2. Introduction to the Core Session Manager, and the Session Load Balancer and Route Manager S-CZ8.2.5
  3. New Features

New Features

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

The S-Cz8.2.5 version of the Oracle Communications Core Session Manager also inherits some of the features from the S-Cz8.2.0 version of the OCSBC. Not all of the OCSBC features are supported for S-Cz8.2.5, based on their relevance to the OCCSM. Contact your Oracle representative to verify whether specific OCSBC features are supported in S-Cz8.2.5 before attempting to deploy them.

ODI Preservation

As the Oracle Communications Core Session Manager (OCCSM) 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 OCCSM 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 OCCSM 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 OCCSM to maintain all ODIs for the duration of the dialog.

See the SIP Call section in this Essentials Guide.

HDR Groups

The OCCSM includes new Historical Data Records (HDR) groups that enhance monitoring and troubleshooting of traffic between itself and HSS servers. These HDR groups align with the output of the show home-subscriber-server ACLI command.

See the layout of these HDR groups in the References and Debugging chapter of this Essentials Guide.

Making Key Information sent to OCOM Anonymous

The OCCSM allows 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.

OpenStack Heat Template

The following new parameters are available for configuration in the environmental file.

  • diskPartitions—Specify the percentage of disk space that will be allocated for each partition.
  • applyBaseConfiguration—Enable or disable the base configuration, which is suitable for minimal Standalone or HA-pair functionality.
  • configuration—If applyBaseConfiguration is set to true, specify the input parameters for the base configuration. Sub-parameters include:
    • dosCores—Specify the number of CPU cores dedicated for denial-of-service protection.
    • forwardingCores—Specify the number of CPU cores dedicated for forwarding frames.
    • transcodingCores—Specify the number of CPU cores dedicated for transcoding media.

      Note:

      Do not configure any transcoding cores. The OCCSM does not support media.
    • ntpServer1—Specify the IP address of an NTP server to use for time synchronization.
    • ntpServer2—Specify the IP address of an NTP server to use for time synchronization.
    • snmpCommunityName—Specify the name of the SNMPv2 community to use for SNMP management.
    • snmpIpAddress—Specify the IP address to add to the SNMPv2 community for SNMP management.
  • wancom0VLAN—(Only available on Pike and newer) Specify the bootparameter VLAN value for the wancom0 interface.
  • vnicBinding—Specify the virtual NIC binding type for each media interface.

For a list of all supported parameters, see the The Platform Preparation and Installation Guide.