Known Issues
The following table lists the known issues in this release. You can reference known issues by Service Request ID 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 the S-Cz9.3.0 Build Notes.
| ID | Description | Severity | Found In |
|---|---|---|---|
| 37522199 | ACLI is allowing the configuration of max-signaling-packets under media-manager to exceed the actual max-signaling-rate a system capacity allows. | 3 | S-Cz9.3.0p5 |
| 35782870 | If routes with both TCP and UDP are available, then the Initial transport method used is UDP. If a failure or timeout occurs, the subsequent transport method of TCP is used in response to a UDP INVITE. If this transport method is selected, then INVITEs are always sent via UDP as long as a response is received. If a route is available with only one transport method selected (either UDP or TCP) only that transport method is used. | 3 | S-Cz9.3.0 |
| 33600407 | When you add IPv4 and IPv6 addresses consecutively on the
hip-ip-list and icmp-address of the same network-interface, followed
by save and activate, the system eventually activates the
configuration change but the SBC goes into an unsteady state with the following
events on the console:
unregister_netdevice: waiting for <interface:id> to become free.Usage count = 1. Workaround: Add IPv4 and IPv6 address on the hip-ip-list and icmp-address separately and activate them individually. For example, activate the first config change or addition and then add and activate the second configuration change. |
2 | S-Cz8.4.0 |
| 33190562 | On the AP3950 and AP4900, in <
0.1% of reboots, the platform gets stuck and does not reach the ACLI
prompt.
Workaround: Perform a power cycle to successfully reboot the system. |
2 | S-Cz9.0.0p1 |
| When operating over the Azure platform, the SBC displays an inordinate number of kernel messages during the bootup process. You can safely ignore these messages. | 3 | S-Cz9.0.0 | |
| 32077115 | For Hairpin and Spiral call scenarios, the
hide-egress-media-update parameter under media-sec-policy is not
supported.
In addition, you must reboot the SBC when you change the hide-egress-media-update parameter under the media-sec-policy, inbound subelement. This parameter is not RTC supported. Oracle recommends you use the hide-egress-media-update parameter under the realm-config only. |
3 | S-Cz9.0.0 |
| 32565921 | The acquire-config process is unsuccessful when your
configuration includes an acp-tls-profile. The system does
successfully synch the profile after establishing HA.
Workaround: Disable your acp-tls-profile on the active system before performing an aquire-config procedure. Re-enable the profile after aquire-config completes successfully. |
3 | S-Cz9.0.0 |
| None | This version does not support the enhancement to SMP-Aware Task Load Limiting, which adds a second parameter to the sip-config load-limit option. | N/A | S-Cz7.4.0 |
|
26790731 |
Running commands with very long
output, such as the "show support-info" command, over an OVM virtual
console might cause the system to reboot.
Workaround: You must run the "show support-info" command only over SSH. |
2 | S-Cz8.0.0 |
|
None |
Re-balancing is unavailable on the OCSLB when running an Acme Packet 6300 as a cluster member. Set the SLB cluster-config, auto-rebalance parameter to disabled to use an Acme Packet 6300 as a cluster member from that SLB. | N/A | S-Cz730 |
|
None |
The system does not support SIP-H323 hairpin calls with DTMF tone indication interworking. | N/A | S-CZ720 |
|
None |
The SBC stops responding when
you configure an H323 stack supporting SIP-H323-SIP calls with the
max-calls parameter set to a value that is less
than the q931-max-calls parameter.
Workaround: For applicable environments, configure the H323 stack max-calls parameter to a value that is greater than its q931-max-calls parameter. |
N/A | S-CZ7.4.0 |
| None | The system does not support HA Redundancy for H.323 calls. | N/A | N/A |
|
27699451 |
Oracle qualified the QSFP interface for the OCSR operating over the Oracle X9-2 platforms for a single QSFP port operating in 4-port mode. Specifically, 4 media interfaces successfully map to the second port of the QSFP interface using a Hydra cable as physical connections to 10G switch ports. | 3 | S-Cz8.1.0 |
|
26316821 |
When you configure the 10 second QoS update mechanism for OCOM, the SBC presents the same codec on both sides of a transcoding call in the monitoring packets. You can determine the correct codecs from the SDP in the SIP Invite and 200 OK. |
3 | S-Cz8.0.0p1 |
| The SBC dead peer detection does not work with IKEv1. | 3 | S-Cz8.4.0 | |
| 28539190 | When operating as a VNF and using Mellanox interface cards, the OCSBC does not use the Host In Path (HIP) configuration to restrict management traffic, Instead the system allows any traffic over the interface. | 3 | S-Cz8.2.0 |
| 29170419 | In long call scenarios, the SBC does not send the expected refresh before the Session-Expires: header value time is up for SUBSCRIBE messages. | 2 | S-Cz8.2.0 |
|
30643522 |
Starting with S-Cz8.3.0m1p2, Lawful
Intercept users cannot modify LI configuration with the Session
Delivery Manager.
Workaround: LI Configuration must be performed through the ACLI. |
4 | S-Cz8.3.0m1p2 |
| 34267143 | No left-side Index and search in the browser for local Help files. | 4 | S-CZ9.1.0 |