Resolved Known Issues

The following table provides a list of previous Known Issues that are now resolved.
ID Description Severity Found In Fixed In
37135255 On large scale VMs with 12 forwarding cores, the last 2 cores do not take any traffic. Traffic is thus balanced between the first 10 forwarding cores. 2 S-Cz9.3.0 S-Cz9.3.0p3
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 S-Cz10.0.0
36344739 When deployed as a vSBC in HA mode and processing transcoding calls, the SBC, after a reboot or an HA switchover, may enter a state wherein a single core begins to process all calls rather than load balance them.

Workaround: Perform a manual HA switchover making the affected system the new stand-by. Next, reboot the new standby to get back it into the correct state. Finally, perform a second manual HA switchover to make the new standby active again. This last step is required because the original standby may have synchronized itself with incorrect data.

 3 S-Cz9.3.0 S-Cz10.0.0
35784723 The system may encounter a dpwd crash or datapath overload errors due to synchronization issues between cavium control core and data core when there is a high traffic in datapath. This issue is applicable to 4600/6300/6350 hardware platforms.

This issue was only seen under extremely heavy load and unusual traffic patterns during Oracle stress testing. These conditions are considered highly unlikely in live deployments.

 2 S-Cz9.2.0

SCZ930

CZ910p10

CZ920p5
34511656 Primary SD runs into a USBC crash after running show scode session-byid command. 3 S-Cz9.1.0 S-Cz9.2.0
35614646 Certain RFC2833/telephone-event sequences generated by customer endpoints may not be properly detected/reported/re-transmitted by the SBC, resulting in missing DTMF digit(s). 2 S-Cz9.2.0p3 S-Cz9.2.0p4
34789990 When deployed on the Acme Packet 4600, enabling the Elin-Ignore-PSAP-Source spl-option may impact the number of supported calls per second by approximately 50 CPS, reducing it to 500 CPS. 3 S-Cz9.1.0p6 S-Cz9.2.0p4
35011380 When running Remote Packet Trace on VNF platforms filtered to specific ingress IP addresses, in the PCAP capture you will sometime observe out of filter or wrong IP addresses. Specifically, the ingress flow packet addressing in the PCAP may display as the egress flow addressing and vice-versa. This depends on scheduling of original and captured packets by the NIC in SBC and this behavior is random.

If you find packets that have the wrong addressing, you need to analyze them using the content of the payload and ignore any incorrect addressing.

 2 S-Cz9.2.0 S-Cz9.2.0p3
34870648 The "show fans" command (a hidden command) is not working on the following SD6 platforms:
  • Acme Packet 1100
  • Acme Packet 3900
  • Acme Packet 3950
  • Acme Packet 4900
 4 S-Cz9.2.0p1 S-Cz9.2.0p2
34593124 Media interfaces configured with Mellanox NICs do not support STIR/SHAKEN. 3 S-Cz9.2.0 S-Cz9.2.0p1

34458541

 During Upgrade of an HA Pair from SCZ840 (any patch up to and including SCZ840p12) to SCZ910 (all releases), the Standby SBC running the SCZ840 release crashes as soon as one of the systems is upgraded to 910p2 and made Active. This crash occurs for the “radd” module which is responsible for CDR generation.
Scenario/Condition in which issue is observed:
  • SBC running with Stir/Shaken call flows
  • Protocol is set to RADIUS in account-config configuration attribute
  • cdr-output-redundancy is set to enabled (this is enabled by default)
With the above configuration, once the first SBC is upgraded and made Active on the SCZ910 release, there is a chance that the standby SBC (on SCZ840) release may experience a radd crash. This is due to an issue in the SCZ840 release in which standby SBC decodes radius CDR incorrectly resulting in corruption of the buffer received from Active SBC which results in crash.

Note:

This only occurs when all three of the above conditions are met and does not apply if only #2 and #3 are enabled and there are no Stir/Shaken call flows.

Workaround: The below steps can be taken as a workaround to perform an HA upgrade from SCZ840 to SCZ910 successfully without experiencing the radd crash described above. Please note this will stop radius CDR replication to standby briefly during the upgrade.

Once the secondary box is upgraded to the SCZ910 release, perform the following steps before triggering switchover to make the upgraded box as Active:
  1. Set “cdr-output-redundancy” config attribute under account-config to disabled and perform save/activate config on the active SBC (which is still on 840 release).
  2. Run “notify berpd force” to make the SCZ910 upgraded SBC active.
  3. Perform steps to start upgrading the second SBC.
  4. While the standby system comes up after reboot, enable “cdr-output-redundancy” config attribute under account-config again on 910 SBC which is currently active.

    If a roll-back to SCZ840 is required, the same process must be performed.

 2 S-Cz9.1.0 S-Cz9.1.0p3

26497348

When operating in HA mode, the SBC may display extraneous "Contact ID" output from the show sipd endpoint-ip command. You can safely ignore this output. 3 S-Cz8.0.0 S-Cz9.1.0p3
28658810 When operating as a VNF and using Mellanox interface cards, the SBC does not support any other type of card for media interfaces. (If any media interface uses a Mellanox card, all media interfaces must use a Mellanox card.) 3 S-Cz8.2.0 S-Cz9.1.0

26323802

The 10s QoS interim feature includes the wrong source IP address as the incoming side of a call flow.

The issue does not prevent successful call and QoS monitoring. For monitoring and debugging purposes, you can find the source IP in the SIP messages (INVITE/200OK).

3 S-Cz8.0.0p1 S-Cz9.0.0p5
32181987 Do not copy and paste characters into a configuration menu and attempt to edit the copied text. This applies to both console and SSH sessions.

Workaround: Edit the data before copy and paste.

3 S-Cz8.4.0 S-Cz9.0.0
33434641 If local-port-match value is set under security-policy, and local-port-match-max is not set, then SBC processes traffic considering full port range. SBC considers the default value of local-port-match-max (i.e. 65535) and applies the specific action mentioned under security-policy to full port range. Configure the local-port-match-max or remote-port-match-max value to set a new port range or set same value for local-port-match and remote-port-match-max to configure a single port. 2 S-Cz8.4.0p4 S-Cz8.4.0p9
32535426 The show temperature output will display different values compared to releases older than S-Cz8.3.0. Starting with S-Cz8.3.0, the temperature queries through the ACLI and SNMP are reporting more accurate values.
  • Similar components may not correspond between different platforms due to physical differences in each system.
 3 S-Cz8.1.0 S-Cz8.3.0
33059603 On the AP3900, AP3950, and AP4900, when performing quickly successive switchovers, an active system system may not synchronize and go OOS after a failover.

Workaround: Set the gateway heartbeat interval timeout value to 10 seconds with 3 gateway heartbeat retries.

 3 S-Cz9.0.0p1 S-Cz9.0.0p2
31344292 The SBC does not support HA replication of a Wildcard PAU. 3 S-Cz9.0.0 S-Cz9.0.0p1
32939208 You cannot set the SBC ikev2-ipsec-wancom0-params parameters using SDM due to issues with the configuration of the rekeyfuzz and localip parameters. Note these parameters have defaults or "0" and "empty" respectively. You can, however, configure these values from the SBC .

You cannot set the SBC ikev2-ipsec-wancom0-params via SDM due to issues in configuration of parameters rekeyfuzz and localip, which have defaults or "0" and "empty" respectively, using OCSDM.

Furthermore, if you change the values for rekeyfuzz and localip, you cannot change them back to their defaults.

Workaround for changing these parameters' values back to their defaults:

  1. remove the ikev2-ipsec-wancom0-params element from your configuration.
  2. Add the element again and set your values.
 3 S-Cz9.0.0 S-Cz9.0.0p1

24574252

The show interfaces brief command incorrectly shows pri-util-addr information in its output. 3 S-Cz7.4.0 S-Cz9.0.0
ACMECSBC-38270 Do not configure STIR over TLS. This configuration causes the system to crash. 3 S-Cz9.0.0 S-Cz9.0.0p1
32939113 Do not configure the auth-user-lookup parameter within the local-policy, policy-attribute without already having:
  • A configured sip-interface or,
  • If that sip-interface does not point to a configured realm
If either of these conditions are true, the SBC crashes when you perform a save-config or a verify-config.

Workaround: Configure the applicable sip-interface and associated realms before you configure the local-policy, policy-attribute, auth-user-lookup parameter.

3 S-Cz9.0.0 S-Cz9.0.0p1
29439964 ACLI Users will receive an error on the output of the show registration sipd by-user command. 4 S-Cz8.2.0 S-Cz8.4.0
32534935 Media is not resumed after RBT playback for transcoded calls on vSBC. Avoid upgrading to releases where this bug is open if your deployment uses a vSBC with Transcoding and is configured to use Ringback-Trigger values. 3 S-Cz8.4.0M0P4 S-Cz9.0.0
31163030 In VOLTE deployments with registration refreshes, you may see unusually large numbers in the alloc and usage count fields while executing the show buffers command. This is a known statistics accounting issue. 4 S-Cz8.3.0 S-Cz9.0.0
31315823

When running IMS-AKA over UDP on virtual SBCs, IMS-AKA registrations may not succeed. Registration failure can also cause associated calls to fail. Oracle has observed this only happens after a system reboot. Oracle has also observed that performing a Save and Activate command sequence after a reboot ensures these registrations are successful.

If you are running IMS-AKA over UDP on virtual SBCs, perform a Save and Activate command sequence after system reboot to ensure successful IMS-AKA registrations.

3 S-Cz8.4.0 S-Cz9.0.0
31828563 While using STIR/SHAKEN, Acme Packet 4600 performance is capped at 330 CPS, and Acme Packet 6350 performance is capped at 1200 CPS for both dual and quad NIU cards. 3 S-Cz8.4.0M0P2 S-Cz9.0.0
Do not upgrade to S-Cz9.0.0 directly from S-Cz8.4.0p4, S-Cz8.4.0p5 or any S-Cz8.4.0p5 OOC patches up to S-Cz8.4.0p5B. If running these versions, upgrade to S-Cz8.4.0p5C before upgrading to S-Cz9.0.0. Upgrading directly from these versions may cause the system to crash.

When upgrading from these versions, upgrade to S-Cz8.4.0p5C first.

 3 S-Cz8.4.0M0P4 S-Cz8.4.0M0P5

29881449

The DSP used by the SBC has a vendor firmware defect that causes failures with the T.38 codec. If you are using the T.38 codec, you may experience minimal media losses on those calls. This problem may also cause the SBC to reboot. 3 S-Cz8.1.0m1p9 S-Cz8.4.0p4
32517222 Media is not resumed after RBT playback for transcoded calls on vSBC. Avoid upgrading to releases where this bug is open if your deployment uses a vSBC with Transcoding and is configured to use Ringback-Trigger values. 3 S-Cz8.4.0M0P4 S-Cz8.4.0P4A
30794993

Please see the section on Upgrades For Configurations that Include Signaled IPSec Tunnels and LI Configurations in Upgrade Downgrade Caveats in this document for an explanation of this issue.

 3 S-Cz8.4.0 S-Cz9.0.0
32243204 STIR/SHAKEN entitlement is not available when the system is set up as a Peering Session Border Controller product. 2 S-Cz8.4.0p2 S-Cz8.4.0p4
32056356

While performing VoLTE Accounting on a 3G-to-4G MT call, the SBC incorrectly populates VSA ID 69 with the P-Asserted-Identity (PAI) retrieved from the response. This identifies the called side. Within the context of a mobile terminating call, the SBC should be identifying the caller, populating this VSA with the PAI retrieved from the INVITE.

Workaround—You can correct this by setting the unidirectional-p-asserted-id option in the applicable account-config to yes.

2 S-Cz8.4.0 S-Cz8.4.0p4

31812964

31926021

31918592

The SBC incorrectly exhibits the following 3 incorrect behaviors with the PCRF during Register and Message call flows:

  1. The SBC sends an STR to the PCRF in response to a de-register even though PCRF does not consider the session established, having sent an AAA with a 3xxx. 4xxx or 5xxx error in response to the corresponding Register.
  2. The SBC keeps the hold timer active and holds an SMS message even though the PCRF has sent an ASR telling the SBC to abort the diameter session.
  3. The SBC does not send an STR to the PCRF during Register flows that fail because of an error from the core, even though the Diameter session between the SBC and PCRF was established.

Workaround—You can correct this by setting the diam-rx-strict-compliance option to the applicable ext-policy-server to enabled. When you set this option, you can correct the three issues above so that the SBC performs the following:

  1. For Register flows that do not establish a diameter session with the PCRF due to a 3xxx. 4xxx or 5xxx error from the PCRF, the SBC does not send an STR to tear down the session when it receives a De-Register.
  2. For Message flows, when the SBC receives an ASR from PCRF, it stops the hold timer, forwards the MESSAGE to the core, and sends an ASA with success.
  3. For unsuccessful Register flows that include an established diameter session with the PCRF, the SBC sends an STR to tear down the session after the Register has failed due to, for example, responses from the core.
3 S-Cz8.4.0 S-Cz8.4.0p4

28618563

The system is not populating the Username AVP in Accounting Requests (ACRs) correctly. When triggered by an INVITE, these AVPs contain only the "@" sign. They do not include the username and domain name portion of the URL. 3 CZ8.1.0m1 S-Cz8.4.0
31726575 Do not configure sip-advanced-logging if you expect any auth-invite call flows (401/407). If you are upgrading to S-Cz8.4.0p2 or later, and your configuration includes conditional logging (session-router, sip-advanced-logging, state=enabled), you must first remove sip-advanced-logging from the config, otherwise calls will fail.
  • Setting the state to disabled does not work and removing it is required.
 2 S-Cz8.4.0p2 S-Cz8.4.0p4
32049267 Do not configure AEAD_AES_256_GCM cipher in the sdes-profile, crypto-list parameter, or the system will crash. 3 S-Cz8.4.0p3 S-Cz8.4.0p4
30794993

The SBC might display an excessive number of debug messages after an HA switchover, if you configured both X123 LI and IKEv2/IPSec with IPv6 security policies.

You can safely ignore these messages.

 4 S-Cz8.4.0 S-Cz8.4.0p2
31384643

During the testing of this release Oracle identified a pre-existing issue in the code where adding an LI warrant during a period of heavy SIP load may cause the system to stop responding, which results in a switchover. This issue exists in prior releases and will be addressed in an upcoming 8.4 patch. If you have not encountered this issue in the past, it is unlikely that you will encounter it now.

System Impact: If you add an LI warrant while the SBC is under heavy load from SIP traffic, a mid-call intercept operation may not occur after the addition (causing the SBC to stop responding). If the SBC stops responding a switchover will occur, but the warrant will have been added correctly. The issue can be mitigated by performing addition of LI warrants during off-peak times, such as maintenance windows.

3 S-Cz8.4.0 S-Cz8.4.0p2

30520108

Upon registering 100k or more IMS-AKA user registrations, and handling large numbers of VoLTE calls and registration refreshes, in excess of 8k for example, a vSBC may hang. At this point, you would find the vSBC unresponsive and inaccessible.

An example of conditions when this may occur includes:

  • 100k IMS-AKA registrations with 100 registrations per second and an expiry timer of 18.0.0 seconds.
  • Forwarding cores at 60% or above utilization.
  • New calls at 50 registrations per second and 10 second hold timers.

Reboot the system from the hypervisor to recover from this issue.

N/A N/A S-Cz8.3.0m1p5

30364057

Do not use DNS for multiple services on the SBC simultaneously. DNS service operates on the SBC normally when you configure it for a single purpose. When you configure it for multiple purposes, however, lookups do not complete correctly.

Workaround: An example of this would be configuring DNS for both PCRF and ENUM services. You can mitigate this issue by configuring the local routing table with ENUM lookups.

3 S-Cz8.3.0p7 S-Cz8.3.0m1p5

29862440

When transcoding from T.38 to G711FB, the SBC includes multiple (for example 2) m-lines in the SDP when there are multiple (for example 2) c-lines in the source SDP. This happens even if you have set the fax-single-m-line parameter in the applicable codec-policy to present a single m-line.

Workaround: Configure an ingress HMR to remove all but 1 c-line from the incoming SDP.

3 S-Cz7.4.0m1p8 S-Cz8.3.0m1p3

30158557

Under high media loads that include AMR/AMR-WB to PCMA transcoding, the 10G port on the Acme Packet 6300 is experiencing packet loss and, therefore media MOS degradation. 2 S-Cz8.1.0m1p16 S-Cz8.4.0

30444535

When configured for the minimum TCP disconnect time, the default for network-parameters, the SBC takes an unexpectedly long time before attempting to create a socket and connect. When using the defaults to create and connect using the minimum amount of time, this process takes 18 seconds instead of 9. 3 N/A S-Cz8.3.0m1p3

29846828

The SBC stops generating registration refreshes after 12 hours for Surrogate Agents. After a reboot, the SBC attends to registration and refreshes correctly using the new Call ID for 12 more hours. 2 E-Cz8.1.0m1p8 S-Cz8.1.0m1p22

30330778

The SBC cannot forward a call that uses a TEL-URI and includes the routing number (rn) parameter. Depending on your routing configuration, the SBC may reject these call with a 404 Not Found/No Route to Destination. The SBC forwards these portability scenarios properly when they present an R-URI. 1 S-Cz7.4.0m2p4;8.1.0m1p18 S-Cz8.1.0m1p23

29779932

The SBC uses a Diffie Hellman algorithm that conflicts with that of the 10.4 Solaris SFTP server. As a result, both CDR and HDR transfers to these servers fail.

Do not use the Solaris 10.4 SFTP server with the SBC.

1 S-Cz8.1.0m1p9, S-Cz8.3.0p7 S-Cz8.3.0m1p4

29913123

NMC causes the Acme Packet 6350 to switchover when NMC gets its first traffic match. 2 S-Cz8.1.0M1P9 S-Cz8.3.0m1p3

29403076

When generating HDR reports and SNMP output on resource utilization that includes threads, the SBC omits the thread name, leaving the applicable field and OID empty. 3 S-Cz8.1.0M1P9 S-Cz825p3
310398.2.0 When mid-call Lawful Intercept is enabled, and the SBC has not started intercepting particular sessions, those sessions will not be replicated on the standby. If a switchover occurs, affected calls could be dropped. 3 S-Cz8.3.0m1p2 S-Cz8.4.0

28157960

When setting up a SIPREC session, the SBC sets up 1-way audio if the far end offers an odd port number in the m line.

2 S-Cz8.0.0 S-Cz8.3.0m1p8

26669090

The SBC dead peer detection does not work with IPv4. 3 S-Cz8.0.0 Could not reproduce - S-Cz8.4.0

22322673

When running in an HA configuration, the secondary SBC might go out of service (OoS) during upgrades, switchovers, and other HA processes while transitioning from the "Becoming Standby" state. Oracle observes such behavior in approximately 25% of these circumstances. You can verify the issue with log.berpd, which can indicate that the media did not synchronize.

Workaround: Reboot the secondary until it successfully reaches the "Standby" state.

3 S-Cz7.3.0P1 S-Cz8.0.0

29931732

The embedded communications monitor probe does not send IPv6 traffic to the Oracle Communications Operations Monitor's mediation engine. 3 S-Cz8.0.0 S-Cz8.3.0m1p4
30375697 Infrequently during race conditions, the number of SIP registration entries on the active and standby SBCs differs, with the standby SBC containing fewer entries. When this happens and a switchover occurs, some endpoints are unable to receive calls until the endpoint re-registers. Increase Journal index size and optimize the Journal management code to avoid this. 2 S-Cz8.1.0m1p18 S-Cz8.1.0m1p18b
30544663 When a session add action is executed and the session is not found in the sipProxy, a new Sip Session and two Sip Dialogs are created and cross referenced and the buffer from the active is loaded. If the load fails, the update function exits and the SipSession and SipDialogs are left dangling and create a memory leak.

Workaround: To avoid this memory leak, successfully load the buffer BEFORE creating the session and dialogs. Monitor the standby SBC's memory usage and reboot as needed.

3 S-Cz8.1.0m1 S-Cz8.1.0m1p18b
30498837 A sipd process crash occurs with a signature containing the following: 
ZNSt8_Rb_treeISsSt4pairIKSs4SptrI10SipContactEESt10*_Select*1stIS5_ESt4lessIS sE SaIS5_EE11equal_rangeERS1_ (+ 0x67) - sp =
0x7f334938d380, ip = 0x1f1b117
The SBC can leak File Descriptors in cases where there are certain process errors. For example: 
[MINOR] (0) Selector::do_select() - epoll_ctl(DEL,
409) failed with errno=9:Bad file descriptor)

This does not trigger proper closure of sockets. This is avoided by closing the socket that was opened and then setting an error identifying exact error code.

2 S-Cz8.1.0m1p18 S-Cz8.1.0m1p18b
29403076

The "thread-event" and "thread-usage" HDR categories are displaying incorrectly due to MBCD and SIPD thread names not properly writing into the files and OID output. MBCD and SIPD now properly assign and pass the proper names.

3 S-Cz8.1.0m1p9 S-Cz8.1.0m1p18b
29633588

During certain configuration activities, the SBC restarts due to an issue caused by improper configuration steps being processed in the sip-manipulation, header-rules.

The SBC now returns an error message stating "Invalid Selection" instead of failing.

3 S-Cz8.1.0m1p11 S-Cz8.1.0m1p18b
29937232

GW unreachable and NetBufCtrl MBUFF errors - This can result in system instability including crash, gw-unreachable and redundancy issues. System will switchover if in HA. Show Buffers output will normally show an increase of errors reported in the NetBufCtrl field due to mbuf’s not being freed.

2 S-Cz8.3.0 S-Cz8.3.0p6
288.2.0258 On VNF platforms, when running TLS Chat on VMware-PV 4core (SSFD) + 16GB, TLS Chat sessions are gradually decreasing. When looking in Wireshark at EXFO, EXFO forwards a wrong TLS MSRP Chat payload to EXFO UAS.

TCP Chat does not have this error.

3 S-Cz8.0.0 S-Cz8.3.0m1p2
For Advanced Media Termination deployments using the 4600, 6300, 6350 platforms, the SBC is generating RTP and RTCP on the ports 20000 and 20001, instead of generating both on the same port 20000. 3 S-Cz8.3.0 S-Cz8.3.0m1p2
29522609 Some calls that are configured to generate ring back tones result in one-way audio. 2 S-Cz8.3.0 S-Cz8.3.0m1p2
29558827 IMS-AKA calls running over IPv6 networks which utilize VLANs on systems with Mellanox network interfaces may experience one-way audio. 3 S-Cz8.3.0p3 S-Cz8.3.0m1p2
29580506 SBCs running on virtual platforms or the Acme Packet 3900 could switch over when running IMS-AKA calls involving refresh registrations. 2 S-Cz8.3.0p3 S-Cz8.3.0m1p2
29607573 The SBC is unable to successfully initiate a TCP connection to configured Diameter Accounting (Rf) servers. 2 S-Cz8.3.0 S-Cz8.3.0m1p2

30114764

When presenting the content type for SPIROU during SIP to SIPI interworking, the SBC is displaying the text base=spirou. Based on relevant standards, it should display base=itu-92+ as the content type. 4 S-CZ8.3.0m1 S-Cz8.3.0m1p2

30127762

When performing SIP to SIPI interworking, the SBC is not including an ISUP REL in the interworked body of its 400 Missing CSeq message when it rejects applicable calls from the SIPI side. 4 S-CZ8.3.0m1 S-Cz8.3.0m1p2

30240798

The SBC closes connections when using some SFTP clients, including WinSCP and MOBA, to upload files over 200KB.

Workaround - Use the Linux or Filezilla SFTP client when uploading files greater than 200k.

3 S-CZ8.3.0p6 S-Cz8.3.0m1p2

30289027

Azure does not always properly reset media interfaces after the SBC reboots. Instead, Azure sometimes tries to process a non-existent packet as soon as the SBC comes back up, resulting in a kernel panic.

Workaround - If you experience a kernel panic after SBC reboot, stop and restart the vSBC from the Azure UI.

3 S-Cz8.3.0 S-Cz8.3.0m1p2

30453532

The Web GUI available in the S-Cz8.3.0M1 release cannot adequately be used to configure the Enterprise SBC.

Workaround: For Web GUI support, use releases either prior to S-Cz8.3.0M1, or releases S-Cz8.3.M1p2 and later.

2 S-Cz8.3.0m1 S-Cz8.3.0m1p2

26258705

The show sipd srvcc command does not display the correct number of unsuccessful aSRVCC calls. 3 S-Cz8.0.0 S-Cz8.3.0

28617938

The anonymize-invite option for CommMonitor is not RTC. To see a change, you must either reboot or toggle the admin state. The following is a general admin state toggle procedure:
  1. Set admin state to disabled.
  2. Save and activate.
  3. Set admin state to enabled.
  4. Save and activate.
4 CZ8.1.0m1 S-Cz8.3.0
29556215 The SBC does not send SIPREC data to a remote call server. 2 S-Cz8.3.0 S-Cz8.3.0p5
29608499 In all documents except for the Release Notes and Installation guide, the printed version of this release (S-Cz8.3.0) is incorrectly displayed as S-Cz8.2.0. 4 S-Cz8.3.0 S-Cz8.3.0p3
28539155 When operating as a VNF and using Mellanox interface cards, the SBC does not support ICMP over IPv6. 3 S-Cz8.2.0 S-Cz8.3.0
29322490 The SBC intermittently does not process the registration (Event: reg) of a SUBSCRIBE with Expires header=0 that should be created after receiving a NOTIFY with a termination request from a UE. 2 S-Cz8.2.0 S-Cz8.3.0
28526228 Maximum SRTP capacity on VNF platforms is 25% lower than in the S-Cz8.1.0 release. Expected capacity will be restored in a follow up patch. 3 S-Cz8.2.0 S-Cz8.3.0

28679339

When supporting SRVCC roaming calls, the SBC is handling SRVCC end-station de-registration events by properly including associated URIs in the 200 OK. It is not, however, saving those associated URIs in its registration cache. This causes the SBC to respond to calls to those URIs with 404 not found messages until the end-station re-registers. 2 S-Cz8.0.0 S-Cz8.3.0

26313330

In some early media call flows, the SBC may not present the correct address for RTP causing the call to terminate. 3 S-Cz8.0.0 S-Cz8.2.0

26281599

The system feature provided by the phy-interfaces overload-protection parameter and overload-alarm-threshold sub-element is not functional. Specifically, enabling the protection and setting the thresholds does not result in trap and trap-clear events based on the interface's traffic load.

The applicable ap-smgmt.mib SNMP objects include:

  • apSysMgmtPhyUtilThresholdTrap
  • apSysMgmtPhyUtilThresholdClearTrap
3 S-Cz720 S-Cz8.2.0

25144010

When an SBC operating on an Acme Packet 6300 switches over, the secondary can successfully add new ACL entries, but it also retains old ACL entries that it should have deleted. 3 S-Cz7.4.0p1

S-Cz8.2.0

26183767

When operating in HA mode and handling large traffic loads, the active SBC stops responding when you restore large configurations that are different from the configuration the active is currently running. The system subsequently goes out of service. 3 S-Cz8.0.0

S-Cz8.2.0

21975038 The Acme Packet 4600, 6100, 6300, and 6350 platforms do not support MSRP File Transfer. 3 S-Cz8.1.0 S-Cz8.2.0

27539750

When trying to establish a connection between the SBC and your network, while using TLS version 1.2, the SBC may reject the connection.

Workaround: You may need to adjust your cipher list.

3 S-Cz8.1.0 S-Cz8.1.0
28062411 Calls that require SIP/PRACK interworking as invoked by the 100rel-interworking option on a SIP interface do not work in pooled transcoding architectures. 2 S-Cz7.4.0 S-Cz8.2.0
28071326 Calls that require LMSD interworking, as invoked by the lmsd-interworking option on a SIP interface, do not work in pooled transcoding architectures. During call establishment, when sending the 200 OK back to the original caller, the cached SDP is not included. 2 S-Cz7.4.0 S-Cz8.2.0
None The CZ8.1.0 release does not support IPSec on the Acme Packet 3900 and VNF. You must upgrade to CZ8.1.0p1 to get this support. After you upgrade to CZ8.1.0p1, do the following:
  1. Run setup entitlements, again.
  2. Select advanced to enable advanced entitlements, which then provides support for IPSEC on Acme Packet 3900 and VNF systems.
N/A S-Cz8.1.0 S-Cz8.2.0
28.3.05575 On VNFs, the system erroneously displays the IPSEC entitlement under "Keyed (Licensed) Entitlements." The error does not affect any functionality and you do not need to do anything. 4 S-Cz8.1.0 S-Cz8.2.0

28659469

When booting CZ8.1.0M1 on any virtual platform, not all system processes start. This known issue only occurs on initial boot, and not in an upgrade scenario.

Workaround: Reboot the SBC a second time, after it initially starts.

3 SCz8.1.0m1 S-Cz8.2.0
If you configured the ims_aka option, you must also configure sip-interfaces with an ims-aka-profile entry. 3 E-Cz7.4.0 E-Cz7.4.0m1

27811129

When upgrading an SBC from a version that uses License Keys to enable CODECs, you must reboot the system after setting any CODEC entitlements to override the License Keys. 3 S-Cz8.1.0 S-Cz8.3.0
30152019

Oracle has identified a Potential tSipd crash when configured for a VOLTE w/SRVCC scenario. When the issue is encountered, there is a sipd crash and, if configured, an HA switchover. This is a race condition that is relatively rare, but has been seen in internal testing.

System Impact of HA Switchover:

  • The Registration cache and existing media sessions are replicated to the standby SBC.
  • During the switchover, transient calls/registrations are lost.
  • After the switchover, TCP connections to and from the UE’s must become re-established in order to make a new call out /refresh register /reregister.
  • The UEs is able to receive calls from the IMS-core because the setup message reestablishes the TCP connection towards the UE.
3 S-Cz8.3.0p7 S-Cz8.3.0m1

28610095

In some circumstances, and with add-sdp-invite and add-sdp-profile configured, the SBC does not include the original SDP in a Re-INVITE that has no SDP. This does not comply with RFC 3264. Instead, the SBC inserts the negotiated media information from the last successful negotiation as the ReINVITE's SDP offer and sends this ReINVITE with inserted SDP to the next hop signaling entity. This issue is evident by the contents of the SDP o line. 3 S-Cz7.4.0 S-Cz8.3.0m1
29541242 Installation and Platform Preparation guide incorrectly includes information about setting up HA on Oracle Cloud platforms. These platforms do not support HA deployments at this time. 3 S-Cz8.3.0 S-Cz8.3.0m1
The following Known Issues and Caveats do not occur in this release. They are listed here for tracking purposes.
ID Description

35575147

 The System Access Based on Server Availability topic in the Authentication and Authorization section of the Admin Security Guide has been created to document this incorrectly labeled known issue as expected behavior.

23756306

When you configure the session-router with an operation-mode of session, it does not correctly clear sessions.

25954122

Telephony Fraud Protection does not blocklist calls after a switchover.

Workaround: Activate the fraud protection table on the newly active server.

31162394 Running SIPREC on the Acme Packet 4600 over 1G interfaces may result in system instability.

Workaround : Do not egress traffic out of a physical interface that exceeds the bandwidth of the physical media capacity. You should determine the amount of egress media traffic and the amount of intercepted traffic on that interface. The intercepted traffic could be any recorded traffic on the interface like (SIPREC, LI, and remote packet trace).

26260953

Enabling and adding Comm Monitor config for the first time can create a situation where the monitoring traffic (IPFIX packets) does not reach the Enterprise Operations Monitor.

Workaround: Reboot the system.

33751575 Deployments must not signal any SILK codec with 12000 or 24000 clock rate in SDP to the SBC. Furthermore, the SBC must not use any SILK media profile with 12000 or 24000 Hz clock rate.

Under these conditions, there is a risk of system memory corruption that can potentially lead to a transcoding core crashing.

26598075

 When running on the Acme Packet 4600, the SBC sends a 200OK with IPv4 media address for call flows with offerless INVITES and the SBC configured with add-sdp-invite=invite and ALTC configured for IPv6 on the egress.

26559988

 In call flows that include dual ALTC INVITEs from the callee, and subsequent Re-INVITEs that offer an ALTC with IPv6 video, the SBC may not include the m lines in the SDP presented to the end stations during the Re-INVITE sequence. This results in the call continuing to support audio, but not video.
28748784 When operating as a VNF and using Mellanox interface cards, the SBC does not support outbound ICMP.

30612465

 On Virtual platforms, the SBC is not forwarding traffic transcoded to EVS or Opus codecs if you have configured the applicable policy with a forced ptime of 60ms.

21805139

RADIUS stop records for IWF calls may display inaccurate values.

26136553

The SBC can incur a system-level service impact while performing a switchover using "notify berpd force" with an LDAP configuration pointing to an unreachable LDAP server.

Workaround: Ensure that the SBC can reach the LDAP server before performing switchover.

28770472 ACLI Users will receive an error on the output of the show registration sipd by-user command.

29999832 and 30194470

When deployed as a vSBC, configured for IMS-AKA, and operating with registrations exceeding 60k, the SBC may exhibit performance degradation, exhibited by high CPU load or system crash.

Workaround - Oracle has found that disabling the security-policy sa-lookup-exception parameter allows IMS-AKA to function correctly while supporting a high number of registrations. This parameter is enabled by default. Disable this parameter within all applicable security policies before running IMS-AKA.

This parameter, when enabled on Acme Packet hardware, works as designed.

32062551 Virtual SBC platforms may incorrectly assess link status thereby causing major health degradation and triggering a failover.
30595413 The IKEv2/IPSEC negotiation fails while using TRANSPORT MODE and different IP’s for IKE and SIP interfaces.

23253731

After an HA switchover, the new standby SBC retains some IMS-AKA subscriber TCP sockets. You can clear these sockets by rebooting the SBC.
29005944 On Acme Packet hardware in an HA configuration, with a large number of IMS-AKA endpoints, the standby is unable to synchronize, and when rebooted goes OOS.

27031344

When configured to perform SRTP-RTP interworking, the SBC might forward SRTP information in the SDP body of packets on the core side, causing the calls to terminate.

Workaround: Add an appropriately configured media-sec-policy on the RTP side of the call flow. This policy is in addition to the policy on the SRTP side of the call flow.

30520181

When performing large numbers of simultaneous registrations, such as during a registration flood, the SBC may become unstable and stop responding when it exceeds 200k IMS-AKA subscriber registrations.

ACMECSBC-23446

24809688

Media interfaces configured for IPv6, and using different VLANs that operate over different infrastructures, including VoLTE and 3GPP, are not supported.
28639227 When operating as a VNF and using Mellanox interface cards, the SBC does not support SCTP transport.
28906914 For transcoding use cases, the G711/G729 codec pair might experience unstable performance when each DSP has greater than 500 transcoding sessions.
N/A The T.140-Baudot Relay is not excluded from supported features with pooled transcoding.
N/A When operating as a VNF deployed in an HA configuration, the SBC does not support IPSec.