Resolved Known Issues
ID | Description | Severity | Found In | Fixed In |
---|---|---|---|---|
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:
|
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:
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:
|
2 | S-Cz9.1.0 | S-Cz9.1.0p3 |
26497348 |
When operating in HA mode, the ESBC 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 OCSBC 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.
|
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 ESBC does not support HA replication of a Wildcard PAU. | 3 | S-Cz9.0.0 | S-Cz9.0.0p1 |
32939208 | You cannot set the ESBC
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 ESBC .
You cannot set the OCSBC 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:
|
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:
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 ESBCs, 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 ESBCs, 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 OCSBC 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 OCSBC 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 |
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.
|
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 ESBC 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 ESBC is under heavy load from SIP traffic, a mid-call intercept operation may not occur after the addition (causing the ESBC to stop responding). If the ESBC 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 |
30364057 |
Do not use DNS for multiple
services on the OCSBC simultaneously. DNS service operates on
the OCSBC 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 OCSBC 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 OCSBC 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 OCSBC stops generating registration refreshes after 12 hours for Surrogate Agents. After a reboot, the OCSBC 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 OCSBC cannot forward a call that uses a TEL-URI and includes the routing number (rn) parameter. Depending on your routing configuration, the OCSBC may reject these call with a 404 Not Found/No Route to Destination. The OCSBC 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 OCSBC 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 OCSBC. |
1 | S-Cz8.1.0m1p9, S-Cz8.3.0p7 | S-Cz8.3.0m1p4 |
29403076 |
When generating HDR reports and SNMP output on resource utilization that includes threads, the OCSBC 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 |
26432028 | On the Acme Packet 1100, Acme Packet 3900, and VME un-encrypted SRTP-SDES calls result in one-way audio. | 3 | E-Cz7.5.0 | S-Cz8.0.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 ESBC 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 ESBC 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:
The SBC can leak File Descriptors in cases where
there are certain process errors. For example:
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 |
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 OCSBC 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 OCSBC reboots. Instead, Azure
sometimes tries to process a non-existent packet as soon as the
OCSBC comes back up, resulting in a kernel panic.
Workaround - If you experience a kernel panic after OCSBC reboot, stop and restart the vSBC from the Azure UI. |
3 | S-Cz8.3.0 | S-Cz8.3.0m1p2 |
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:
|
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 OCSBC does not support ICMP over IPv6. | 3 | 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 |
26313330 |
In some early media call flows, the ESBC 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:
|
3 | S-Cz720 | 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 |
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:
|
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 ESBC a second time, after it initially starts. |
3 | SCz8.1.0m1 | S-Cz8.2.0 |
27240195 |
The cpu-load command does not display the correct value under show-platforms. |
3 | E-Cz8.0.0 | 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 | |
27795586 |
When running E-Cz8.1.0 over Hyper-V, and you set
the process-log level to DEBUG, the system can become unstable
or stop responding. The system requires a reboot.
Workaround: Do not enable process-log level DEBUG. |
3 | E-Cz8.1.0 | S-Cz8.2.0 |
28475320 |
When running E-Cz8.1.0M1 on the Acme Packet 3900, IPSec functionality is not available. | 2 | S-Cz8.1.0 | S-Cz8.2.0 |
32849192 | The Data Integrity entitlement does not work properly, sometimes introducing system instability. Do not enable the Data Integrity entitlement. | 2 | S-Cz9.0.0 | S-Cz9.0.0p1 |
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 ESBC. Furthermore, the
ESBC 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 OCSBC sends a 200OK with IPv4 media address for call flows with offerless INVITES and the OCSBC 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 OCSBC 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 OCSBC does not support outbound ICMP. |
30612465 |
On Virtual platforms, the OCSBC 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 ESBC 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 ESBC 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 |
|
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 ESBC retains some IMS-AKA subscriber TCP sockets. You can clear these sockets by rebooting the ESBC. |
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 ESBC 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 OCSBC 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 OCSBC 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 OCSBC does not support IPSec. |