Oracle Acme Packet SBC

See also

Sources

1. 1
   Oracle's acquisition of Acme Packet was completed on March 28, 2013, after which Acme Packet became an indirect wholly owned subsidiary of Oracle.

   Acme Packet Inc. Form 8-K (Completion of Acquisition) · Item 2.01 Completion of Acquisition or Disposition of Assets · Checked 2026-10-14
2. 2
   The ACLI activate-config command, a Superuser-mode command, makes the current configuration the running configuration.

   activate-config - ACLI Reference Guide S-Cz10.1.0 · activate-config, Description and Mode · Checked 2026-10-14
3. 3
   An Acme Packet 3900 or 4600 running SBC or Enterprise SBC software cannot move to any release after S-Cz10.1.0, so moving beyond the 10.1.0 train needs a hardware or virtual platform migration.inferred

   Supported Physical Platforms - SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, last-release note below SBC list · Checked 2026-10-14
4. 4
   For S-Cz10.1.0 the Acme Packet 6350 is supported only with the Quad 10GbE NIU.

   Supported Physical Platforms - SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, SBC list entry for Acme Packet 6350 · Checked 2026-10-14
5. 5
   An edit to an Oracle SBC through the ACLI does not take effect until it is saved with save-config and then made the running configuration with activate-config, with verify-config run first.inferred

   activate-config - ACLI Reference Guide S-Cz10.1.0 · activate-config Description; read together with save-config Description and verify-config Description · Checked 2026-10-14
6. 6
   Oracle states that S-Cz10.1.0 is the last Oracle Enterprise SBC release that will support the Acme Packet 3900 and Acme Packet 4600.

   Supported Physical Platforms - Enterprise SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, note below Enterprise SBC list · Checked 2026-10-14
7. 7
   Release S-Cz10.1.0 of the Oracle Enterprise SBC supports the Acme Packet 1100, 3900, 3950, 4600, 4900, 6350 (Quad 10GbE NIU only) and 6400 physical platforms.

   Supported Physical Platforms - Enterprise SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, Enterprise SBC list · Checked 2026-10-14
8. 8
   As of 2026-10-14 the newest Oracle Enterprise SBC release listed in Oracle's documentation library is S-CZ10.1.0, with S-CZ10.0.0 before it.

   Enterprise Session Border Controller Documentation · release list, first entry · Checked 2026-10-14
9. 9
   Oracle Enterprise SBC releases up to E-CZ8.1.0 carry the E-CZ prefix, and releases from S-CZ8.2.0 onward carry the S-CZ prefix used by the Oracle Communications SBC.

   Enterprise Session Border Controller Documentation · release list (Release E-CZ8.1.0 followed by Release S-CZ8.2.0) · Checked 2026-10-14
10. 10
    A local-policy policy-attribute next-hop can be an IP endpoint, a session agent, a session agent group prefixed SAG:, a local route table prefixed lrt:, or an ENUM lookup prefixed enum:.

    local-policy - ACLI Reference Guide S-Cz10.1.0 · local-policy, policy-attribute next-hop parameter examples · Checked 2026-10-14
11. 11
    local-policy is a multiple-instance element under the session-router path that decides where session signaling messages are routed or forwarded, matched on from-address, to-address and source-realm.

    local-policy - ACLI Reference Guide S-Cz10.1.0 · local-policy, Description, Path and parameters from-address / to-address / source-realm · Checked 2026-10-14
12. 12
    A realm's addr-prefix defaults to 0.0.0.0, and left at the default it matches all addresses on the realm's network interface.

    Realms - SBC Configuration Guide S-Cz10.1.0 · Realms, addr-prefix step · Checked 2026-10-14
13. 13
    realm-config is configured under the media-manager path in the ACLI (configure terminal, media-manager, realm-config), and its identifier must be unique.

    realm-config - ACLI Reference Guide S-Cz10.1.0 · realm-config, Path and identifier parameter · Checked 2026-10-14
14. 14
    A realm-config names the inbound and outbound SIP manipulation rules it applies through its in-manipulationid and out-manipulationid parameters.

    realm-config - ACLI Reference Guide S-Cz10.1.0 · realm-config, parameters in-manipulationid and out-manipulationid · Checked 2026-10-14
15. 15
    Only one network-interface can be assigned to a single realm-config, except in local multi-homing SCTP deployments.

    Realms - SBC Configuration Guide S-Cz10.1.0 · Realms, network-interface step · Checked 2026-10-14
16. 16
    S-Cz10.1.0 adds certificate automation, in which the SBC acts as a CMP client (RFC 4210/4211) to handle X.509 certificate tasks including renewal; it requires the CMP entitlement.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0 > Certificate Automation · Checked 2026-10-14
17. 17
    The S-Cz10.1.0 release notes for the Oracle Communications SBC and Session Router were first published in April 2026.

    Revision History - Oracle Communications Session Border Controller and Session Router Release Notes, Release S-Cz10.1.0 · Revision History, April 2026 entry (Initial release) · Checked 2026-10-14
18. 18
    The September 2026 revision of the S-Cz10.1.0 release notes added the S-Cz10.1.0p2 new features, changed VMware support to version 7.0 or later, and added Oracle Communications Server E6-2L and OCI VM.Standard.E6.Flex shapes.

    Revision History - Oracle Communications Session Border Controller and Session Router Release Notes, Release S-Cz10.1.0 · Revision History, September 2026 entry · Checked 2026-10-14
19. 19
    In S-Cz10.1.0, SIPREC changes on session-recording-server take effect through real-time configuration without a reboot.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0 > Real Time Configuration Support for SIPREC · Checked 2026-10-14
20. 20
    S-Cz10.1.0 adds TLS for syslog, enabled by setting transport-protocol to TLS and specifying a tls-profile.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0 > TLS for Syslog · Checked 2026-10-14
21. 21
    S-Cz10.1.0p2 removes public key authentication for HDR push receivers, which had been introduced in S-Cz10.1.0p1; only password authentication remains.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0p2 > Removal of Public Key Authentication for HDR Push Receivers · Checked 2026-10-14
22. 22
    Members of a session agent group are logically equivalent and interchangeable, and an allocation strategy on the group spreads traffic across them.

    Session Agents, Session Groups, and Local Policy - SBC Configuration Guide S-Cz10.1.0 · Session Agents, Session Groups, and Local Policy, definition of session agent group · Checked 2026-10-14
23. 23
    The ACLI save-config command saves the current configuration to the last-saved configuration in flash memory and increments the current configuration number by one.

    save-config - ACLI Reference Guide S-Cz10.1.0 · save-config, Description and Notes · Checked 2026-10-14
24. 24
    S-Cz10.1.0 uses DPDK version 24.11.1.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · DPDK version statement at end of Supported Private Virtual Infrastructures and Public Clouds · Checked 2026-10-14
25. 25
    Oracle states that S-Cz10.1.0 is the last Oracle Communications SBC release that will support the Acme Packet 3900 and Acme Packet 4600.

    Supported Physical Platforms - SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, note below SBC list · Checked 2026-10-14
26. 26
    Release S-Cz10.1.0 of the Oracle Communications SBC supports the Acme Packet 3900, 3950, 4600, 4900, 6350 (Quad 10GbE NIU only) and 6400 physical platforms.

    Supported Physical Platforms - SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, SBC list · Checked 2026-10-14
27. 27
    Starting with S-Cz9.3.0 the Oracle Communications SBC no longer supports the Acme Packet 6100, Acme Packet 6300, or Acme Packet 6350 with the dual-port NIU.

    Supported Platforms - SBC Release Notes S-Cz9.3.0 · Platforms No Longer Supported, SBC list · Checked 2026-10-14
28. 28
    In the Oracle SBC a session agent defines a signaling endpoint: a next-hop signaling entity to which traffic shaping attributes can be applied.

    Session Agents, Session Groups, and Local Policy - SBC Configuration Guide S-Cz10.1.0 · Session Agents, Session Groups, and Local Policy, definition of session agent · Checked 2026-10-14
29. 29
    For SIP and H.323 session routing, session agents and session agent groups are optional; routing can be defined with local policies alone.

    Session Agents, Session Groups, and Local Policy - SBC Configuration Guide S-Cz10.1.0 · Session Agents, Session Groups, and Local Policy, introductory paragraph · Checked 2026-10-14
30. 30
    A change of product type, alone or together with entitlement changes, is not complete until the system reboots.

    setup product - ACLI Reference Guide S-Cz10.1.0 · setup product, Notes · Checked 2026-10-14
31. 31
    The ACLI setup product command lets one software image be provisioned as Session Border Controller, Session Router (session stateful), Session Router (transaction stateful), Subscriber-Aware Load Balancer, Enterprise Session Border Controller or Peering Session Border Controller, depending on platform.

    setup product - ACLI Reference Guide S-Cz10.1.0 · setup product, Description and example product list · Checked 2026-10-14
32. 32
    The sip-manipulation element (under session-router) lets the SBC add, modify and delete SIP headers and header elements through header-rules, with separate mime-rules, mime-isup-rules and mime-sdp-rules subelements for message bodies.

    sip-manipulation - ACLI Reference Guide S-Cz10.1.0 · sip-manipulation, Description, Path and parameter list · Checked 2026-10-14
33. 33
    Oracle states that S-Cz10.1.0 is the last Session Router release that will support the Acme Packet 4600 and Oracle Server X8-2.

    Supported Physical Platforms - SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, note below Session Router list · Checked 2026-10-14
34. 34
    Release S-Cz10.1.0 of the Oracle Session Router supports the Acme Packet 4600, Acme Packet 4900, Oracle Server X8-2, Oracle Server X9-2 and Oracle Communications Server E6-2L.

    Supported Physical Platforms - SBC Release Notes S-Cz10.1.0 · Supported Physical Platforms, Session Router list · Checked 2026-10-14
35. 35
    Session Router can be deployed on the Acme Packet 6400 starting with image S-Cz10.1.0p1.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0p1 > Session Router on Acme Packet 6400 Platform · Checked 2026-10-14
36. 36
    Session Router support on Oracle Communications Server E6-2L arrived in S-Cz10.1.0p2, in session-stateful or transaction-stateful mode, with the Mellanox NIC supported only for HA and wancom ports.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0p2 > Support for Session Router on Oracle Communications Server E6-2L · Checked 2026-10-14
37. 37
    The steering-pool port-allocation-strategy defaults to mixed (all session types); single is recommended for MSRP and pair for audio and video.

    Steering Pools - SBC Configuration Guide S-Cz10.1.0 · Steering Pools, port-allocation-strategy values · Checked 2026-10-14
38. 38
    Overlapping steering-pool port ranges on the same interface trigger a verify-config error, but the SBC does not prevent that configuration from being saved and activated.

    Steering Pools - SBC Configuration Guide S-Cz10.1.0 · Steering Pools, port range caution · Checked 2026-10-14
39. 39
    If a signaling interface and a steering pool share an IP address over TCP, the steering-pool port range must exclude the signaling port, or the SBC cannot properly process signaling on that interface.

    Steering Pools - SBC Configuration Guide S-Cz10.1.0 · Steering Pools, TCP signaling port caution · Checked 2026-10-14
40. 40
    Microsoft's list of SBCs certified for Teams Direct Routing includes the Oracle AP 1100, AP 3900, AP 3950, AP 4600, AP 4900, AP 6350 and VME on 9.x and 10.x, AP 6300 on 9.x only, AP 6400 on 10.x only, and Oracle Cloud Native SBC on 1.26.0.1.0 or higher without media bypass.

    Session Border Controllers certified for Direct Routing - Microsoft Teams · Certified SBC vendors table, Oracle rows · Checked 2026-10-14
41. 41
    In-service upgrades to S-Cz10.1.0 for the SBC, Enterprise SBC and Session Router are supported from S-Cz9.2.0p13 or higher, from S-Cz9.3.0p9 or S-Cz9.3.0p11 or higher, and from S-Cz10.0.0p5 or higher.

    Upgrade Information - SBC Release Notes S-Cz10.1.0 · Upgrade Information, supported in-service (hitless) upgrade paths · Checked 2026-10-14
42. 42
    Out-of-service upgrades to S-Cz10.1.0 are supported from S-Cz9.0.0p12 and from S-Cz9.1.0p14.

    Upgrade Information - SBC Release Notes S-Cz10.1.0 · Upgrade Information, supported out-of-service upgrade paths · Checked 2026-10-14
43. 43
    Upgrading from S-Cz9.3.0p10 to S-Cz10.1.0 is not a supported upgrade path.

    Upgrade Information - SBC Release Notes S-Cz10.1.0 · Upgrade Information, note on S-Cz9.3.0p10 · Checked 2026-10-14
44. 44
    Upgrading with a different image type (for example a non-LI deployment moving to an LI image) is not hitless and needs an extra reboot of all upgraded devices to establish the new deployment type.

    Upgrade Information - SBC Release Notes S-Cz10.1.0 · Upgrade Information, image type guidance · Checked 2026-10-14
45. 45
    Oracle instructs that an upgrade should always start from the latest patch of the currently installed release.

    Upgrade Information - SBC Release Notes S-Cz10.1.0 · Upgrade Information, procedural guidance · Checked 2026-10-14
46. 46
    The ACLI verify-config command checks the consistency of the current configuration and should be run before activating it; it also runs as part of save-config and checks for duplicate addresses per network-interface.

    verify-config - ACLI Reference Guide S-Cz10.1.0 · verify-config, Description and Notes · Checked 2026-10-14
47. 47
    For S-Cz10.1.0 Oracle lists Microsoft Hyper-V on Microsoft Server 2012 R2 or later as a supported hypervisor.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Hypervisors for Private Virtual Infrastructures, Microsoft Hyper-V · Checked 2026-10-14
48. 48
    For S-Cz10.1.0 on KVM, Oracle lists minimum versions of Linux kernel 5.14.0-162, QEMU 6.1.1-3 and libvirt 7.10.0-2.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Hypervisors for Private Virtual Infrastructures, KVM · Checked 2026-10-14
49. 49
    For S-Cz10.1.0 the supported VMware hypervisor is vSphere ESXi 7.0 or later.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Hypervisors for Private Virtual Infrastructures, VMware · Checked 2026-10-14
50. 50
    On AWS EC2, ENA networking for the SBC is supported only on the C5 and C5n instance families.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Public Cloud Platforms, Amazon Web Services notes · Checked 2026-10-14
51. 51
    Support for the Microsoft Azure Standard_F32s_v2 instance size (32 vCPUs, up to 8 vNICs) begins with S-Cz10.1.0p1.

    New Features - SBC Release Notes S-Cz10.1.0 · S-Cz10.1.0p1 > Support for Microsoft Azure Standard_F32s_v2 · Checked 2026-10-14
52. 52
    The SBC does not support Data Disks on any Azure instance size.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Public Cloud Platforms, Microsoft Azure notes · Checked 2026-10-14
53. 53
    The default virtual SBC is 4 vCPU cores, 8 GB RAM, a 28 GB pre-formatted disk and 8 interfaces (1 management wancom0, 2 HA wancom1 and wancom2, 1 spare, 4 media).

    Requirements for Machines on Private Virtual Infrastructures - SBC Release Notes S-Cz10.1.0 · Requirements for Machines on Private Virtual Infrastructures, default resources list · Checked 2026-10-14
54. 54
    Oracle sizes the virtual SBC disk as twice the RAM plus 12 GB, and the SBC does not support automatic dynamic disk resizing.

    Requirements for Machines on Private Virtual Infrastructures - SBC Release Notes S-Cz10.1.0 · Requirements for Machines on Private Virtual Infrastructures, disk sizing sentence · Checked 2026-10-14
55. 55
    On Google Cloud the SBC must use the virtio network interface and does not work with gVNIC.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Public Cloud Platforms, Google Cloud Platform notes · Checked 2026-10-14
56. 56
    Accelerated media and signaling using SR-IOV (VF) or PCI passthrough (DDA) modes are not supported for the virtual SBC on Hyper-V.

    Requirements for Machines on Private Virtual Infrastructures - SBC Release Notes S-Cz10.1.0 · Requirements for Machines on Private Virtual Infrastructures, Hyper-V note · Checked 2026-10-14
57. 57
    A virtual SBC supports its media interfaces only when all of them are the same NIC model on the same Ethernet controller, with the same PCI vendor and device ID and the same I/O mode (SR-IOV, PV or PCI-PT).

    Requirements for Machines on Private Virtual Infrastructures - SBC Release Notes S-Cz10.1.0 · Requirements for Machines on Private Virtual Infrastructures, media interface constraint · Checked 2026-10-14
58. 58
    On OCI Flex shapes the virtual SBC requires a minimum of 4 OCPUs and 16 GB of memory per instance.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Public Cloud Platforms, Oracle Cloud Infrastructure note below shape table · Checked 2026-10-14
59. 59
    On OCI the virtual SBC supports only image-mode (SR-IOV native, hardware-assisted) networking; paravirtualized and emulated modes are not supported.

    Supported Private Virtual Infrastructures and Public Clouds - SBC Release Notes S-Cz10.1.0 · Supported Public Cloud Platforms, Oracle Cloud Infrastructure networking note · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). Oracle Acme Packet SBC. WarmTransfer. https://warmtransfer.net/knowledge/oracle-acme-packet-sbc

@misc{warmtransfer-oracle-acme-packet-sbc,
  title  = {Oracle Acme Packet SBC},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/oracle-acme-packet-sbc},
  note   = {Verified 2026-10-14}
}