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

Known Issues

The following table lists Known Issues and provides the Service Request ID number, a description of the issue, any workaround, when the issue occurred, and when Oracle fixed the issue. This table includes issues from previous releases that either remain open or are resolved in this release. Issues from previous releases that do not appear here do not apply to this release. You can also find information about resolved issues in the Build Notes for this release.

ID Number Description Found In Fixed In
32723531 Upon clicking Verify when adding an LST entry, the OECB incorrectly displays a logout prompt. PCZ3.2.0 N/A
32671930 During sipd crashes, OECB is also becoming unavailable. PCZ3.2.0 N/A

29582306

The Dial pattern's "Delete All" function does not work properly, causing system disruption including system reboot.

Work-around: Delete the entire plan using the "Delete Dial Plan" function and recreate your Dial plan with the appropriate Dial patterns.

PCZ3.2.0 N/A

30509697

An OECB configured with 1 million user database entries stops accepting new calls for ~90 seconds after performing a save and activate.

Work-around: Configure systems with user databases that approach 1 million entries during a maintenance window.

In addition, Oracle recommends using the OECB's ACLI paste-config command or the automatic CSV import feature to perform uploads of these large user databases and avoid system interruption. 		PCZ3.2.0 N/A
No ID number

If you want to establish a High Availability pair that uses IP addresses other than the defaults, perform the following procedure. Use this procedure regardless of whether the ECBs run on virtual or physical systems.

The IP addresses you use must be available and valid in your network. If not, you must directly connect the two ECBs before performing this procedure to establish the HA pair initially.

Note
  • Primary default—169.254.1.1
  • Secondary default—169.254.1.2

Procedure

  1. Perform the standard HA setup with the run setup command, and allow both systems to come up in an HA pair.
  2. From the GUI, go to General, General, High Availability and assign the IP addresses that you want to use to the Primary and Secondary ECBs.
  3. Move the wancom1 connection to the network that you want to use. (Either the physical connection, or for VMs, change the vswitch used by the wancom1 interface.)
  4. Double reboot both systems, and they will come back up in an HA pair.
PCZ3.0.0 N/A