Known Issues
This table lists the Oracle Communications Unified Session Manager (OCUSM) known issues in version CZ8.2.0. 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 |
---|---|---|---|
29815940 |
An
OCUSM HA pair crashes
when you peform configuration changes that include updating and/or removing
certificates within a
certificate-record
element.
The process that crashes is atcpd. |
2 | S-CZ7.3.5 |
26895359 |
While processing multiple REGISTERs for a
single AOR with different contacts that arrive within a few seconds of each
other, the
OCUSM may lose one or
more of those contacts.
The issue occurs because of a race condition in the correlation of the NAPTR answers received from the DNS server for the user contact record updates. |
3 | S-CZ7.3.5 |
28873421 |
It can take the
OCUSM more than 7
minutes to clear a single session when it is supporting 5000-6000 active
concurrent sessions.
This issue is caused by unusually large configurations. |
3 | S-CZ7.3.5 |
Instead of routing a message via local
policy, the
OCUSM incorrectly issues
an LIR when the following two conditions exist simultaneously:
Note that the OCUSM 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 OCUSM returns an error. |
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 Acme Packet platform, lower-level system issues, and applicable application issues apply across the S-CZ8.2.x product versions, including the OCUSM.