1. Release Notes
  2. Known Issues and Resolved Known Issues
  3. Caveats and Limitations

Caveats and Limitations

The following sections list known or reported issues that are either expected behavior or will not be fixed in future releases:

Oracle Communications Session Delivery Manager

  • During the course of SDM upgrades, any certificates uploaded to the Java keystore in a previous SDM version (for example – certificates for LDAP SSL connectivity) need to be imported again to the Java keystore of the new SDM version. This is needed for LDAP over SSL to work

  • The REST and SOAP API response omits the reason phrase in SDM 8.2.3 and later versions, because Tomcat v9 and later versions have deprecated the reason phrase. The Tomcat server returns the status code as the reason phrase, hence the status code appears twice in the response. For example:
    HTTP/1.1 200 200
    instead of 
    HTTP/1.1 200 OK

  • Software and bootloader file integrity check

    • If the source device version is earlier than SCZ8.0.0 or ECZ8.0.0, file integrity check is not performed as the command to check file integrity is only available from SCZ8.0.0 and ECZ8.0.0 version.

    • If the target software and bootloader file versions are earlier than SCZ8.0.0 or ECZ8.0.0, file integrity check is not performed as for most of the SCZ7*.bz, ECZ7*.bz, SCZ7*.boot and ECZ7*.boot images signature is not present.
  • Modelling

    • Offline Configuration or Global Parameters created using Software version for ECB - PCZ330 or above cannot be used to push dialing context entries.

    • Workaround: Create Offline Configurations or Global Parameters from the managed device or make dialing-context modifications using the ECB user interface.

  • It is not possible to perform software and bootloader upgrades from SDM for devices running SZ830m1. Devices running SCZ830m1pX work fine. As a workaround, upgrade devices running SZ830m1 using the device ACLI.
  • The Offline Configurations functionality in the Configuration Manager is not supported for ECB HA pair devices.
  • SDM will not be able to perform software upgrades (software image and/or bootloader) if the current software version on the device is SCz840 till SCz840p3 and R226 is enabled on the device. The reason is that on these versions the /boot is not accessible using SFTP. You will need to perform any upgrade from these versions using SBC ACLI.
  • The current running software image must be present in the /code/images/ directory of the network device, so that OCSDM can archive the image. This archived image can be used later during a rollback to recover from upgrade failures. If the existing image is not available, then you cannot use OCSDM for software upgrades.
  • The LDAP configuration sub-element routing attribute 'address-of-record' which can be accessed using LDAP-config, routing, and address-of-record will not be visible in the SDM user interface for ECB version PCZ330. Hence it cannot be configured from the SDM User Interface.Workaround You can configure the same attribute from the ECB PCZ330 device ACLI or device GUI.
  • When you add or edit the snmp-user-entry element through the OCSDM GUI for a device, applying a none or empty password for the Auth protocol and Priv protocol parameters are not supported.

    Workaround: If a none or empty password is required for Auth protocol and Priv protocol parameters, you must apply these parameters through the device ACLI.

  • Do not add spaces to the "To Address" of the local routing policy.
  • SNMPv3 parameters are not supported when adding a Network Function (NF) through the OCSDM REST API.

    Workaround: You can enter SNMPv3 parameters for an NF that you want to add through the OCSDM GUI.

  • OCSDM does not support devices with IPv6 management addresses. Refer to defect number 24361366 for more information.
  • New R226 security features where introduced in the SCz8.1 and ECz 8.1 releases. If you need to manage devices with these releases (and later) with OCSDM, you must perform the following tasks:
    1. Upgrade to OCSDM 8.1 or later to manage releases which have the R226 security features.
    2. You must enable ACP over TLS on the devices.
    Refer to the Configure Transport Layer Security Certificates section in the Oracle Communications Session Delivery Manager Installation Guide for more information regarding OCSDM support.
  • For CSM/SLRM images 825p3 and later, you must mandatorily enable ACP over TLS.

  • We recommend that the target name of your SBC device does not have an underscore character (_). This character may cause information to not appear correctly for an SBC device in OCSDM product applications. Also, the historical data record (HDR) data detection feature does not work on an SBC device if its name has an underscore.

  • If the plug-in is replaced or upgraded, any previously uploaded XSD work spaces are removed.

    Workaround: If required, reapply the XSD work spaces once the plug-in is installed.

  • When a user installs a plug-in on a cluster node that supports new functionality, other users that are logged in may not see this new functionality.

    Workaround: The user can use click Refresh in Device manager or log out of their SDM GUI session and then log back in to see the change.

  • When you use the OCSDM setup process to create a self-signed certificate for OCSDM northbound WebServer HTTPS communication, a single DNS name can be used only because OCSDM supports one northbound HTTPS interface.
  • When you use the OCSDM setup process to create an entity certificate to facilitate mutual authentication for OCSDM southbound (ACP), a single DNS name can be used only because the OCSDM supports one southbound ACP over TLS interface.
  • In the Element Manager Plugins table Tools, Plugin Management, you cannot sort the Status, Server, and Date Modified columns in ascending or descending order.
  • If you implement an OCSDM cluster, one server only must be started successfully and operational before other servers in the cluster can be started.
  • When connecting an SDM to an SBC with the Admin Security ACP feature enabled, you must have the security, admin-security, enable-login-banner configuration parameter set to disabled.

  • The ability to use an offline configuration to provision network function (NF) device clusters is not available for the Acme Packet 9200 platform.

  • When the Fraud Detection and Prevention feature is enabled, you must run the OCSDM as a standalone server only.
  • When any changes are made to existing entitlements, OCSDM does not automatically refresh and the new entitlements changes are not enabled.

    Workaround: Remove and re-add the device to OCSDM.

  • In custom OCSDM installations, SAML Single sign on configuration for importing self-signed certificates into the Route Manager certificates file (cacerts), is not currently supported.

Oracle Communications Session Element Manager

  • Many components of the Oracle Communications session delivery product device software are licensed by Oracle and some product devices require a license key. Product devices that have applied a license key appear in Device Manager, however device license entitlements do not currently appear in Device Manager.

    Workaround: Use the show entitlements command in the device ACLI to gather license entitlement information.

  • In the event of an unexpected server shutdown, the incremental save operation may be incorrectly reported as being successful if it is associated with a offline configuration update.

  • When entering a single quote in an attribute value, use the backslash symbol "\" to escape.

  • A CXF (SOAP) client may have its connection closed by the server for long duration transactions.

Oracle Communications Report Manager

  • If you are upgrading Oracle Communications Session Report Manager from a previous version, BI Publisher and Oracle database (Listener and Listener 2) need to be running and properly connected when you use the Oracle Communications Session Delivery Manager setup installation process, during which these databases are migrated. See the Prepare for a Report Manager Upgrade section in the Pre-Installation Tasks chapter of the Oracle Communications Session Report Manager Installation Guide for more information.
  • By default, the password for the nncentral user, OCSREMDW database user, and BI Publisher (for example, DEV_MDS and DEV_BIPLATFORM) database users for the Oracle reporting database expires in 6 months. Once the password expires, the nightly backup and restore capability for reporting fails. You must go to the Oracle database to change each user password. Ask your Oracle support for more specific information about performing this task.

    Note:

    This limitation applies to Report Manager users who have installed an Oracle database on the same server as OCSDM only.
  • Report Manager does not support data gathering or the TscfStats group for SBC devices with ScZ7.40 and ScZ7.4.0p1 releases. This problem will be fixed in the ScZ7.4.0p2 release.

  • With the introduction of OCSDM, Release 8.0, there is a single secure sockets layer (SSL) keystore that includes BI Publisher certificates. Any BI Publisher certificates that were previously imported into the keystore before Release 8.0 are lost.

    • Ensure that the BI Publisher certificate is in the desired directory on the OCSDM server. If the BI Publisher certificate is not on the server you must transfer it to server. See the Save and Transfer the BI Publisher Certificate to Session Delivery Manager section in the Register Oracle BI Publisher chapter of the Oracle Communications Report Manager Installation Guide for more information.
    • Ensure that the BI Publisher Certificate is added to the keystore either through the OCSDM server setup program (setup.sh) or upload it through the OCSDM GUI.

      Note:

      If you are using the OCSDM server setup program to upload a BI Publisher certificate, you must run the setup program on each OCSDM server cluster node to upload the BI Publisher certificate on each node. If you perform this task through the OCSDM GUI, the BI Publisher certificate is replicated to all OCSDM server cluster nodes.
      • See the Configure Southbound Interface Transport Layer Security section in the Custom Installation chapter of the Oracle Communications Session Delivery Manager Installation Guide for more information about loading the BI Publisher certificate through the OCSDM server setup program.
      • See the Manage Certificates for Southbound Authentication chapter in the Oracle Communications Session Delivery Manager Administration Guide for more information about loading the BI Publisher certificate through the OCSDM GUI.
  • In OCSDM, Release 8.0 or earlier, Report Manager is supported on Oracle Linux 6.5, 6.6, 6.7, 6.8 only. Also, Oracle Database 11g Standard Edition One, and Oracle Business Intelligence (BI) Publisher 11g are supported only.
  • In OCSDM, Release 8.x, Report Manager does not support device clustering.
  • In OCSDM 8.2.1, Report Manager works with Oracle Database 12c and Oracle BI Publisher 12.2.1.2.0 and not Oracle Database 11g. Therefore, during migration from a previous OCSDM 8.x release (running 11g) to OCSDM 8.2.1, only the Element Manager is migrated and the Report Manager is not.
  • In OCSDM, Release 8.2.2, Report Manager works with:
    • Oracle Database 12c and Oracle BI Publisher 12.2.1.2.0

      and

    • Oracle Database 19c and Oracle BI Publisher 12.2.1.2.0
    The Report Manager does not work with Oracle Database 11g. Therefore, during migration from a previous OCSDM 8.x release (running 11g) to OCSDM 8.2.2, only Element Manager is migrated and Report Manager is not. Also, there is no migration path from Oracle Database 12c to Oracle Database 19c.