3 Known Issues

The following topics list the known issues for the Cloud Native SBC. Oracle updates this document to distribute issue status changes. Check the latest revision of this document to stay informed about these issues.

Bug Severity

The Cloud Native SBC adopts the following four general definitions for bug severity

  • Severity 1 - Critical/Complete loss of service.
  • Severity 2 - Significant/Major/Severe loss of service.
  • Severity 3 - Standard/Minor/Minimal loss of service.
  • Severity 4 - Minimal/Informational/Minor error/No loss of service/Cosmetic.

Known Issues

Review the known issues before using the Cloud Native SBC. ORACLE is aware of these known issues and may resolve these in future releases. Refer the workarounds if available to handle the known issue and review this section periodically for updates.

Table 3-1 Known Issues

ID Description Severity Found In
Internal bug

Deployment of Signaling, Media or Transcode Engine as a part of the Cloud Native SBC application package fails. The pod fails to reach the Ready state and displays an error in the vNIC injection job pod. 
ERROR: Interface name not found for mac address xx:xx:xx:xx:xx:xx

Workaround: Run this command to delete the Cloud Native SBC Application pod that failed to reach Ready state. 

kubectl delete pod <CNSBC application failed pod name> - n <namespace>

<namespace> is the Cloud Native SBC application namespace.

2
  • 25.1.0
Internal bug

In the Cloud Native SBC GUI, under sip-manipulation > cfg-order, the Move Up or Move Down option to re-order the manipulation rule does not appear on the first mouse click. This option is available under the action column, represented by a horizontal ellipsis icon.

Workaround: Click the actions icon(represented by the horizontal ellipsis icon) twice to view the Move Up or Move Down option.

3
  • 25.1.0
Internal bug

Reviewing configurations changes for access-control element is not supported in Cloud Native SBC GUI. 3
  • 25.1.0
Internal bug

After a failover occurs in a high-availability (HA) setup, existing Denial of Service (DoS) entries for the previously active Signaling Engine do not reflect in the newly active Signaling Engine. 3
  • 25.1.0
Internal bug

Traces are not generated when the following conditions are met in sip-adv-log-trace element.
  • match-type is request-type
  • match procedure is exact-match or regex-match
  • match-value is any one of these - REGISTER, ACK, BYE, CANCEL, PRACK, OPTION, INFO, SUBSCRIBE, NOTIFY, REFER, UPDATE, MESSAGE, PUBLISH.

The traces are generated only when the match-value is INVITE.

 3
  • 25.1.0
Internal bug

Advanced logs are not generated when the following conditions are met in sip-adv-log-trace element.
  • match-type is request-type
  • match procedure is exact-match or regex-match
  • match-value is any one of these - ACK, BYE, CANCEL, PRACK, INFO, REFER
 3
  • 25.1.0
Internal bug

The Cloud Native SBC does not support sending STIR requests to an STI server located on a routed external network. 2
  • 25.1.0
Internal bug

While the Transcode Engine processes moderate volume of media traffic in para-virtualized mode, intermittent DPWD crashes may occur. This could result in a minimal call impact. 2
  • 25.1.0

Caveats

Review the caveats before using the Cloud Native SBC. These caveats talk about the Cloud Native SBC's unexpected behavior as per design. ORACLE is aware of these caveats that do not have a workaround. Review this section periodically for updates.

Transcoding Caveats

Software-based transcoding on the Cloud Native SBC is only supported on servers with INTEL CPUs.

CPU Resource Configuration Unavailable in Cloud Native SBC Console Database

The Cloud Native SBC Console database does not support CPU resource configuration.

Console Core URL

If you update the coreStaticIpAddress parameter in the Console values YAML file and upgrade the Console, then manually update the IP address of the Console Core in the home URL for your client sbc from the IAM's UI(Clients page).

Large Configuration Limitation

It is advisable to operate within a limit of 50,000 configuration objects and attributes to ensure optimal performance and minimize the risk of service degradation. This number can vary depending on the mix of various configuration element types. For large configurations, it is recommended to save and activate configuration during times of low traffic. Future updates are road mapped to further enhance performance and will allow for higher configuration limits.

It is also recommended to configure a minimum of 3 minutes for both clientTimeout and serverTimeout when setting up timeouts in load balancer during platform preparation.

For more information on the factors that influence the activation of configurations, refer to the Oracle Cloud Native Session Border Controller GUI Guide.