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

Known Issues

This table lists the OCSBC known issues in version CZ8.2.0. You can reference known issues by Service Request 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 this release's Build Notes.

ID Description Severity Found In

24574252

The show interfaces brief command incorrectly shows pri-util-addr information in its output. 3 SCZ740

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 SCZ800
26338219 The packet-trace remote command does not work with IPv6. 2 SCZ740

26497348

When operating in HA mode, the E-SBC may display extraneous "Contact ID" output from the show sipd endpoint-ip command. You can safely ignore this output. 3 SCZ800
The show sipd srvcc command does not display the correct number of unsuccessful aSRVCC calls. 3 SCZ800

21805139

RADIUS stop records for IWF calls may display inaccurate values. 2 SCZ730b6

24809688

Media interfaces configured for IPv6, and using different VLANs that operate over different infrastructures, including VoLTE and 3GPP, are not supported. 3 SCZ730

None

The system does not support SIP-H323 hairpin calls with DTMF tone indication interworking. N/A S-CZ720

None

The E-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-CZ740

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 CZ810m1

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 CZ810m1

25954122

Telephony fraud protection does not black list calls after a failover.

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

3 E-CZ7.5.0

26136553

The E-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 E-SBC can reach the LDAP server before performing switchover.

2 Unknown

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.

3 E-CZ7.5.0

26316821

When configured with the 10 second QoS update mechanism for OCOM, the E-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 SCZ8.0.0p1

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 SCZ8.0.0p1
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

26669090

The E-SBC dead peer detection does not work with IPv4. 3 SCZ8.0.0

27031344

When configured to perform SRTP-RTP interworking, the E-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.

3 SCZ8.0.0p1
28539155 When operating as a VNF and using Mellanox interface cards, the OCSBC does not support ICMP over IPv6. 3 SCZ820
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 SCZ820
28617865 This version of the OCSBC only is not supported as a VNF over VMware using Mellanox interface cards. 3 SCZ820
28639227 When operating as a VNF and using Mellanox interface cards, the OCSBC does not support SCTP transport. 3 SCZ820
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 SCZ820
28748784 When operating as a VNF and using Mellanox interface cards, the OCSBC does not support outbound ICMP. 3 SCZ820
28906914 For transcoding use cases, the G711/G729 codec pair might experience unstable performance when each DSP has greater than 500 transcoding sessions. 3 SCZ820
28770472 ACLI Users will receive an error on the output of the show registration sipd by-user command. 4 SCZ820
29170419 In long call scenarios, the SBC is not sending the expected refresh before the Session-Expires: header value time is up for SUBSCRIBE messages. 2 SCZ820

29931732

The embedded communications monitor probe does not send IPv6 traffic to the Oracle Communications Operations Monitor's mediation engine. 3 SCZ800
28820258 On PNF 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 SCZ800

Resolved Known Issues

The following table provides a list of previous Known Issues that are now resolved.
ID Description Severity Found In Fixed In
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 SCZ820 SCZ830p6
28526228 Maximum SRTP capacity on VNF platforms is 25% lower than in the SCZ8.1.0 release. Expected capacity will be restored in a follow up patch. 3 SCZ820 SCZ830

26313330

In some early media call flows, the E-SBC may not present the correct address for RTP causing the call to terminate. 3 SCZ800 SCZ820

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 SCZ720 SCZ820

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 SCZ810 SCZ810
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 SCZ740 SCZ820
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 CZ810 CZ820
28305575 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 CZ810 CZ820

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 E-SBC a second time, after it initially starts.

3 CZ810m1 SCZ820
27240195

The cpu-load command does not display the correct value under show-platforms.

3 ECZ8.0.0 SCZ820
If you configured the ims_aka option, you must also configure sip-interfaces with an ims-aka-profile entry. 3 ECZ7.4.0 ECZ7.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 ECZ8.1.0 SCZ820

28475320

When running ECZ810M1 on the Acme Packet 3900, IPSec functionality is not available. 2 CZ810 SCZ820
The following Known Issues and Caveats have been found not to be present in this release. They are collected here for tracking purposes.
ID Description Found In Fixed In

22322673

When running in an HA configuration, the secondary E-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.

N/A N/A
N/A The T.140-Baudot Relay is not excluded from supported features with pooled transcoding. N/A N/A

28367500

When operating the OCSBC on the Acme Packet 6300, the traceroute command does not show hops for an IPv6 traceroute that does not reach the target address. The system successfully displays hops when the traceroute reaches the target and for IPv4 traceroutes. N/A N/A