1. Essentials Guide
  2. Caveats and Known Issues
  3. Caveats and Limitations

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.

OCUSM Caveats

  • Do not load configurations from sibling products, the Oracle SBC for example, on the Oracle Communications Unified Session Manager (OCUSM). Those configurations are incompatible with the OCUSM, causing incorrect operation. Users should configure the OCUSM from scratch or use another valid OCUSM configuration.
  • Multi-stage routing does not work for S-CSCF routing functions.
The OCUSM accepts only the first message received from an application server in response to messages from the OCUSM that included an ODI. If it receives subsequent messages from that application server, the OCUSM 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 OCUSM that include an ODI originally provided by the OCUSM.
  • Geo-redundancy is currently not supported by the OCUSM.

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 Acme Packet platform, lower-level system issues, and applicable application issues apply across the S-CZ8.2.x product versions, including the OCUSM.