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

Known Issues

This table lists the known issues in version S-Cz8.3.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
31373813 If upgrading TO any of the following releases FROM any prior release and you have IPSEC or IMS-AKA enabled and are configured in an HA configuration, an In-Service upgrade is not supported.
  • S-Cz8.1.0m1p23
  • S-Cz8.1.0m1p24
  • S-Cz830m1p5
  • S-Cz830m1p6
  • S-Cz830m1p7
  • S-Cz830m1p8

    You must upgrade both systems in the HA pair and perform a simultaneous reboot for HA synchronization to work in the above upgrade scenario. This also applies to a downgrade FROM the above releases TO prior releases. For example, if you are running S-CZ8.1.0M1P23 and decide to downgrade to S-Cz8.1.0M1P21, you will need to install the prior version (Cz8.1.0M1P21) on both systems in the HA pair and execute a simultaneous reboot.

    If you are already running one of the above releases and are upgrading between them, this step is unnecessary and in-service upgrades are supported.

 3 SCZ830m1p5

30611784

When executing a GET ALL procedure using the REST interface, the OCSBC fails over. The GET method does not produce results until the Standby server becomes Active.

Customer Impact: Customer will not be able to get any response(including 200 empty response) from OCSBC when he tries to retrieve configuration of any element using GET method.

3 SCZ830m1p2

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 SCZ810M1P9

29913123

NMC causes the Acme Packet 6350 to failover when NMC gets its first traffic match. 2 SCZ810M1P9

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, however, cause the OCSBC to reboot.

Oracle is acquiring a firmware fix from the DSP vendor.

3 SCZ810m1p9

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 SCZ740m2p4;810m1p18

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 ECZ810m1p8

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

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 SCZ810m1p16

29862440

When transcoding from T.38 to G711FB, the OCSBC includes mutiple (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 SCZ740m1p8

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 SCZ830p7

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

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 1800 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.

30520181

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

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

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

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

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
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 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. 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
29546194 The SBC is unable to maintain 400 or more TSM/DTLS tunnels. 2 SCZ830
The Acme Packet 6350 with Quad 10Gbe NIU is unable to maintain 375,000 or more idle TSM/DTLS tunnels. 3 SCZ830p2

29999832 and 30194470

When deployed as a vSBC, configured for IMS-AKA, and operating with registrations exceeding 60k, the OCSBC 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.

3 SCZ830

30643522

Starting with S-Cz8.3.0m1p2, Lawful Intercept users cannot modify LI configuration with the Session Delivery Manager.

Workaround: LI Configuration must be performed through the ACLI.

4 SCZ830m1p2

Resolved Known Issues

The following table provides a list of previous Known Issues that are now resolved.
ID Description Severity Found In Fixed In

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 via ACLI and SNMP are reporting more accurate values.

Note:

Similar components may not correspond between different platforms due to physical differences in each system.
3 SCZ810 SCZ830

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 SCZ800 SCZ830m1p8

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 SCZ830p7 SCZ830m1p5

30611784

When executing a GET ALL procedure using the REST interface, the OCSBC fails over. The GET method does not produce results until the Standby server becomes Active.

Customer Impact: Customer will not be able to get any response(including 200 empty response) from OCSBC when he tries to retrieve configuration of any element using GET method.

3 SCZ830m1p2 SCZ830m1p5

29931732, 31089996

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

31188777

 The SBC does not provide support for P-Acme-Playback header when 'direction=both'. 3 SCZ830 SCZ830m1p9
30375697 Infrequently during race conditions, the number of SIP registration entries on the active and standby SBCs differs, with the standby SBC containing less entries. When this happens and a failover 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 SCZ830 S-Cz830p6
28820258 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 SCZ800 S-CZ830m1p2
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 SCZ830 S-CZ830m1p2
29522609 Some calls that are configured to generate ring back tones result in one-way audio. 2 SCZ830 S-CZ830m1p2
29558827 IMS-AKA calls running over IPv6 networks which utilize VLANs on systems with Mellanox network interfaces may experience one-way audio. 3 SCZ830p3 S-CZ830m1p2
29580506 SBCs running on virtual platforms or the Acme Packet 3900 could failover when running IMS-AKA calls involving refresh registrations. 2 SCZ830p3 S-CZ830m1p2
29607573 The SBC is unable to successfully initiate a TCP connection to configured Diameter Accounting (Rf) servers. 2 SCZ830 S-CZ830m1p2

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-CZ830m1 S-CZ830m1p2

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-CZ830m1 S-CZ830m1p2

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-CZ830p6 S-CZ830m1p2

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 SCZ830 S-CZ830m1p2

30453532

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

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

2 SCZ830m1 SCZ830m1p2

26258705

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

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 SCZ830
29556215 The SBC does not send SIPREC data to a remote call server. 2 SCZ830 SCZ830p5
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 SCZ830 SCZ830p3
28539155 When operating as a VNF and using Mellanox interface cards, the OCSBC does not support ICMP over IPv6. 3 SCZ820 SCZ830
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 SCZ830
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

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 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 SCZ830

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 SCZ830
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 failover. This is a race condition that is relatively rare, but has been seen in internal testing.

System Impact of HA Failover:

  • The Registration cache and existing media sessions are replicated to the standby OCSBC.
  • 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 SCZ830p7 SCZ830m1

28610095

In some circumstances, and with add-sdp-invite and add-sdp-profile configured, the OCSBC does not include the original SDP in a Re-INVITE that has no SDP. This does not comply with RFC 3264. Instead, the OCSBC 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 SCZ740 SCZ830m1
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 SCZ830 SCZ830m1
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

21805139

RADIUS stop records for IWF calls may display inaccurate values. N/A N/A