1. Service Provider and Session Router 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
None This version's enhancement to SMP-Aware Task Load Limiting, which adds a second parameter to the sip-config load-limit option, is currently not supported. N/A SCZ740

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 OCSBC may display extraneous "Contact ID" output from the show sipd endpoint-ip command. You can safely ignore this output. 3 SCZ800

26258705

The show sipd srvcc command does not display the correct number of unsuccessful aSRVCC calls. 3 SCZ800

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. 3 SCZ800

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. 3 SCZ800

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 SCZ730

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 OCSBC 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
None The system does not support HA Redundancy for H.323 calls. N/A N/A

23756306

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

3 S-Cz7.2.0

23253731

After an HA switchover, the new standby OCSBC retains some IMS-AKA subscriber TCP sockets. You can clear these sockets by rebooting the OCSBC. 2 SCZ730M2

27699451

Oracle qualified the QSFP interface for the OCSR operating over the Oracle X7-2 platform 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 SCZ810

27911939

When running the OCSBC over the KVM hypervisor and using SR-IOV interface mode, the system fails over when all of following conditions are in effect:

  • 4 forwarding cores
  • 8 signaling cores
  • IMS-AKA in use
  • High call traffic load
3 SCZ810

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

26316821

When configured with the 10 second QoS update mechanism for OCOM, the OCSBC 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

26669090

The OCSBC dead peer detection does not work with IPv4. 3 SCZ8.0.0

27031344

When configured to perform SRTP-RTP interworking, the OCSBC 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
28819431 For TSM use case, the ETC CPU load increased 40% over the previous release. 2 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
29005944 On engineered hardware in an HA configuration, with a large number of IMS-AKA endpoints, the standby is unable to syncronize, and when rebooted goes OOS. 3 SCZ820
28999116 IWF (SIP-H323) appears at the setup entitlements prompt on virtual platforms when H.323 is not supported. 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
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 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

28679339

When supporting SRVCC roaming calls, the OCSBC 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 OCSBC to respond to calls to those URIs with 404 not found messages until the end-station re-registers. 2 SCZ800 SCZ820p4
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 OCSBC 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

25144010

When an OCSBC operating on an Acme Packet 6300 fails over, the secondary can successfully add new ACL entries, but it also retains old ACL entries that it should have deleted. 3 SCZ740p1

SCZ820

26183767

When operating in HA mode and handling large traffic loads, the active OCSBC 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 SCZ800

SCZ820

21975038 The Acme Packet 4600, 6100, 6300, and 6350 platforms do not support MSRP File Transfer. 3 SCZ810 SCZ820
27579686 This release does not support TSM. 2 SCZ810 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
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 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 OCSBC a second time, after it initially starts.

3 CZ810m1 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
28998693 For TSM use cases, AP6100 and AP6300 systems do not support data-flow modes. 2 SCZ820 SCZ820p1

27811129

When upgrading an OCSBC 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 SCZ810 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 OCSBC 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