Caveats and Limitations

The following information lists and describes the caveats and limitations for this release. Oracle updates this Release Notes document to distribute issue status changes. Check the latest revisions of this document to stay informed about these issues.

OCCSM Caveats

This section list caveats related to Version S-CZ8.2.5 of the Oracle Communications Core Session Manager.

Do not load configurations from sibling products, the Oracle SBC for example, on the Oracle Communications Core Session Manager. Those configurations are incompatible with the Oracle Communications Core Session Manager, causing incorrect operation. Users should configure the Oracle Communications Core Session Manager from scratch or use another valid Oracle Communications Core Session Manager configuration.

Configuration elements specific to the SLRM, including lb-interface are not compatible with Oracle Communications Core Session Manager configuration elements. The set-component-type command provides a warning indicating that the user must delete any prior configuration and create the new component type configuration from scratch to avoid potential configuration conflicts. Note the sample output below.
- ```
SCZ715_64# set-component-type core-load-balancer
WARNING: Changing component type is service impacting.
********************************************************  
Ensure that you follow these steps if you choose to  
change the component type:  
1. Issue the delete-config command.  
2. Reboot.
********************************************************
Continue with the change [y/n]?:
```

Multi-stage routing does not work for S-CSCF routing functions.

The Oracle Communications Core Session Manager does not support 'netboot' when operating on the Oracle VM platform. The user must, instead, upload new images to the Oracle Communications Core Session Manager and boot from them locally.

By default, storage is not persistent across a reboot of a Oracle Communications Core Session Manager virtual machine. You must create persistent storage space for log and dump file data.
- Issue - Generic virtual machine installation documentation may not include the requirement to run the command format hard-disk during virtual machine installation.
- Resolution - Run the command format hard-disk to create a persistent partition for your /opt directory, within which you can store data needed after a reboot. Perform this procedure the FIRST time you start your Oracle Communications Core Session Manager.
The OCCSM accepts only the first message received from an application server in response to messages from the OCCSM that included an ODI. If it receives subsequent messages from that application server, the OCCSM drops the reused ODI and processes the message as if they were received without an ODI.
- Resolution - Do not configure an AS to fork responses to the OCCSM that include an ODI originally provided by the OCCSM.
Geo-redundancy is currently not supported by the OCCSM.

Caveats Inherited from the S-CZ8.2.0 SBC

Refer to the Caveats in the S-CZ8.2.0 OCSBC Release Notes to complete your review of issues in this release. Issues withinin the OCSBC, especially including applicable VNF platform and applicable application issues apply across the S-CZ8.2.x product versions, including the OCCSM.