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-Cz10.0.0 Build Notes.
| ID | Description | Severity | Found In |
|---|---|---|---|
| 37677691 | When upgrading vSBCs running over
KVM, Vmware or cloud deployments to release S-Cz930p5 or later
(including S-Cz10.0), spaces in the
interface-mapping labels can corrupt the
interface-mapping list and cause some
media interfaces to fail after the upgrade.
Workaround: If you have configured labels to your interface-mapping list entries, remove any blank spaces from them before you upgrade. If you have already upgraded, you can edit your interface-mapping labels so that there are no blank spaces in the label and reboot. |
2 | S-Cz9.3.0p5 |
| 37431006 | After running the restore-backup-config command, you must reboot your system to make sure all the non-RTC configurations are applied properly. After this reboot, traffic can be started. | 3 | S-Cz10.0.0, S-Cz9.3.0, S-Cz9.2.0 |
| 37243688 | When operating with the AMR-WB codec over the Acme Packet
4600, 6350, 1100 and 3900 platforms, you may find that the system is
not able to transcode some DTMF tone signals to RFC 2833 packets.
This issue is also limited to very specific integration deployments. Contact Oracle Technical Support to verify you are experiencing this issue. |
2 | S-Cz10.0.0 |
| 37431251 | When operating over the ACME Packet 4600, 6300 and 6350
platforms in HA mode and using BFD, the primary BFD interface on the
active will not come up. Note that the virtual interface on the
active and the secondary interface on the standby do come up. But
this is not useful for BFD until the primary session on the active
Enterprise SBC comes up.
Due to this, BFD can't be used to perform switchover between active and standby, as switchover happens only when primary session of BFD goes down. It is recommended not use BFD when operating HA deployments over the Acme Packet 4600, 6300 and 6350. |
3 | S-Cz9.3.0 |
| 37211703 | TLS client and server negotiates EC (elliptic curve) named
curves in supported_groups extension. With this fix, SBC uses the
below named curves:
Note: Earlier SBC versions used only secp256r1. |
2 | S-Cz9.3.0p3 |
| 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 |
| 36195612 | When generating RADIUS CDRs, the Acme-TerminatingTrunk-Group and Acme-TerminatingTrunk-Context fields are missing in the Start, Interim-Update, and Stop CDRs. | 3 | S-Cz9.2.0p5 and S-Cz9.1.0p10 |
| 35641698 | When supporting IPSEC tunnels using
IKEv1 in initiator mode, and when the endpoint initiates an Security
Association renewal sequence (rekey/refresh) over the connection,
the SBC can lose connectivity to that endpoint after an HA
switchover. This behavior can be considered rare because the SBC is
configured as the initiator.
Workaround: An example scenario that causes this behavior is when connection rekey requests come from the endpoint. This can occur because the rekey timing configuration on the endpoint is shorter than that of the SBC. A workaround for this scenario is to manually configure rekey timing such that the SBC always issues the rekey request. |
3 | S-Cz9.3.0 |
| 36001121 | The suppress-hold-resume-reinvite feature does not work if the applicable Hold and Resume Re-INVITEs do not include SDP. | 3 | S-Cz9.3.0 |
| 35815496 | With Virtual SBCs, registration and calls work fine initially when running IMS-AKA, however, they may stop accepting registrations over TCP after multiple refresh registrations. | 2 | S-Cz9.2.0p2 |
| 34991934 | Do not upgrade any device licensed to use FIPS to S-Cz9.2.0, S-Cz9.3.0, or S-Cz10.0.0. These releases disable FIPS mode. Upgrading a FIPS-enabled system to these releases can lead to call failures and unstable system behavior. | 3 | S-Cz9.2.0 |
| 35038085 | If an exiting audio stream is interrupted by a stray SSRC within the flow's packets, this interruption may trigger one-way audio wherein the audio towards the called party fails. You can confirm this condition by locating RTP packets in the flow with stray SSRC. | 2 | S-Cz9.1.0 |
|
The system does not save the changes when you leave the fields header-name, content-type, and parameter-name blank while adding cfgrules (header-rule and element-rule) sub-objects for the SIP Manipulation object. Workaround: Enter data in the header-name, content-type, and parameter-name while adding the cfgrules (header-rule and element-rule) sub-objects. |
N/A | S-Cz9.2.0 | |
|
The system displays the “must have a header-name” warning while adding cfgrules (element-rule) sub- object when you leave the header name field blank in cfgrules (header-rule) sub-object in the SIP Manipulation object Workaround: Enter the header-name field in cgfrules (header-rule) sub-object before proceeding to addor modify cfgrules (element-rule) sub-object. |
N/A | S-Cz9.2.0 | |
|
Configuration does not copy sub-objects without a header name when you create a copy of a SIP Manipulation object. Workaround: Enter the required field, such as header-name, content type, or parameter-name, when adding the cfgrules sub-object. |
N/A | S-Cz9.2.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 Enterprise 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 |
| 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 |
|
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 |
The system does not support SIP-H323 hairpin calls with DTMF tone indication interworking. | N/A | S-CZ720 |
|
None |
The Enterprise 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 |
|
26316821 |
When you configure the 10 second QoS update mechanism for OCOM, the Enterprise 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 Enterprise 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 Enterprise SBC 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 |
| 28617865 | This version of the Enterprise SBC is not supported as a VNF over VMware using Mellanox interface cards. | 3 | S-Cz8.2.0 |
| 29170419 | In long call scenarios, the Enterprise SBC does not send the expected refresh before the Session-Expires: header value time is up for SUBSCRIBE messages. | 2 | S-Cz8.2.0 |
| 34267143 | No left-side Index and search in the browser for local Help files. | 4 | S-CZ9.1.0 |