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

26497348

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

Issue: When upgrading to S-Cz8.4.0p7 from a release prior to S-Cz8.4.0p5, the system does not display templates in Configuration Assistant.

Work-around: Run mkdir /code/configAssistant/ before the upgrade.

Or, if upgraded already, run mkdir /code/configAssistant/ and cp /var/configAssistant/template-package.tar.gz /code/configAssistant/

You need to do this only once. The folder persists unless you delete it manually.

32688016

32695177

Workaround—You can correct these 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 four issues above so that the SBC performs the following:

1. Within a register call flow wherein the SBC receives an AAA with a 3002 error code from the PCRF after the diameter transaction has timed out, the SBC does not send an STR to the PCRF.
2. Within emergency REGISTER call flows when S8HR is enabled and there are no EPC level identities cached, the SBC does not issue an STR simultaneously with a 403 error code if it receives a 3002 error code from the PCRF.

32524837

32524762

32488834

32502583

Workaround—You can correct these 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 four issues above so that the SBC performs the following:

1. If the SBC receives an S8HR Emergency Registration, with or without Authorization header, and either the Rx interface is not available or there is an error in AAA response sent by PCRF, the SBC replies with a 5xx response.
2. If the SBC receives an S8HR Emergency Registration without an Authorization header and the EPC identities validation fails, the SBC sends a 403 error with the SIP reason header. If the SBC receives a REGISTER request with the authorization header, it sends a MIME XML body with a reason tag.
3. For S8HR registrations and calls, the SBC adds the P-Visited-Network-ID header using the format "plmnIdPrefix.mncxxx.mccxxx.3gppnetwork.org".
4. During an S8HR registration scenario, if the SBC receives a REGISTER request with the Authorization header and the next-hop is not configured, the SBC sends a 403 response if the EPC identities validation fails.

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.

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.

28618563

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.

Workaround: Edit the data before copy/paste.

• Setting the state to disabled does not work and removing it is required.

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.

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.

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.

30364057

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.

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.

30158557

30444535

29846828

30330778

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.

29913123

29403076

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.

26669090

22322673

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

29931732

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.

ZNSt8_Rb_treeISsSt4pairIKSs4SptrI10SipContactEESt10*_Select*1stIS5_ESt4lessIS sE SaIS5_EE11equal_rangeERS1_ (+ 0x67) - sp =
0x7f334938d380, ip = 0x1f1b117

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

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.

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.

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.

TCP Chat does not have this error.

30114764

30127762

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.

30289027

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

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.

26258705

28617938

1. Set admin state to disabled.
2. Save and activate.
3. Set admin state to enabled.
4. Save and activate.

28679339

26313330

26281599

The applicable ap-smgmt.mib SNMP objects include:

• apSysMgmtPhyUtilThresholdTrap
• apSysMgmtPhyUtilThresholdClearTrap

25144010

S-Cz8.2.0

26183767

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.

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.

28659469

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

27811129

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

28610095

30612465

26559988

26598075

23756306

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.

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.

23253731

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 OCSBC may become unstable and stop responding when it exceeds 200k IMS-AKA subscriber registrations.

• NNC-OCSDM XSD file for SCZ840p4 with SDM 8.2.x

24809688

30534173

21805139