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

Known Issues

This table lists the Oracle Communications Core Session Manager (OCCSM) known issues in version S-Cz8.2.5. You can reference known issues by Service Request number and you can identify the issue, any workaround, when the issue was found, and when it was fixed using this table. Issues not carried forward in this table from previous Release Notes are not relevant to this release. You can review delivery information, including defect fixes in this release's Build Notes.

ID Description Severity Found In
31528120 Do not enable OCOM if you are running the OCCSM over KVM. This can introduce system instability, including system crash, especially if the system is managing a large number of registrations. 2 S-Cz8.2.5

30026648

The OCCSM High Availability function does not replicate sessions.

This issue is based on a change, per customer enhancement request, to eliminate B2BUA proxy mode as a valid configuration for the OCCSM.

The user can recognize this issue by observing that, although the sessions are not backed up, the standby still routes pertinent BYEs, CANCELs and other messages after switchover using backed up request URIs.

2 S-Cz7.3.5
Instead of routing a message via local policy, the OCCSM incorrectly issues an LIR when the following two conditions exist simultaneously:
  • The OCCSM is not configured with the e164-primary-config and e164-secondary-config options, and
  • The OCCSM receives a request with a tel-URI or a sip-URI with the user=phone parameter.

Note that the OCCSM sends the request via local-policy if the LIA for a tel-URI or sip-URI with user=phone returns 5001 DIAMETER_ERROR_USER_UNKNOWN. For all other errors in the LIA, the OCCSM returns an error.

You must change the sip-config's registration-cache-limit from the default of zero for an OCCSM to function with an SLRM. Oracle recommends you set this value to 500000.
When the user disables the lb-cfg on an OCCSM, breaks the SC link to the SLRM. However, instead of properly seeing the affected OCCSM as out-of-service, the SLRM sees the OCCSM as out-of-sync and may continue to forward new REGISTERs.

Known Issues Inherited from the S-CZ8.2.0 SBC

Refer to the Known Issues 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.