Oracle Enterprise Session Border Controller licensing is structured around several distinct decisions: which platform license applies, how much concurrent-session capacity is required, and which optional capabilities the deployment needs. Understanding these layers helps engineering and procurement teams align the license configuration with the SBC’s hardware, signaling requirements and operational role. The details discussed here reflect Oracle’s E-Cz8.0.0 licensing document dated December 2017; confirm applicable terms and product availability for the version and agreement being considered.
How Oracle Enterprise Session Border Controller licensing is organized
The documented model includes base licenses, session-capacity licenses, advanced-feature licenses, security options and codec licenses. These categories are not interchangeable. A base license establishes access to the platform and specified baseline functions, while separate capacity or feature licenses may be needed to enable the intended scale or functionality.
The document identifies two base-license paths: an Oracle Enterprise Session Border Controller base fee for specified Acme Packet platforms, and an SMB Edition base fee for the Acme Packet 1100. Both provide access to Acme Packet OS and basic node-management functions, including CLI, FTP and SNMP. The standard base-fee entry lists Acme Packet 3900, 4500, 4600 and 6300 hardware as prerequisites; the SMB entry specifies Acme Packet 1100 hardware.
Baseline functions and session capacity
Base entitlements described in the document include SIP and H.323 functionality, high-availability heartbeat and checkpointing, and endpoint demotion functions associated with Intrusion Detection System (IDS) features. Other listed capabilities include ACP request handling, National Security and Emergency Preparedness (NSEP/RPH) support, SIPREC session replication, software SRTP using SDES, and software TLS for SIP signaling encryption. Some options have platform prerequisites, so feature availability should not be inferred from the base-license name alone.
Session capacity is a separate licensing dimension. The document describes capacity licenses in concurrent-session units and defines the licensed maximum across supported protocols, including SIP and H.323. In the Integrated Software Option (ISO) model, a per-server base license is paired with session-capacity licensing. Advanced-feature licenses are tied to that capacity: the documented requirement is an equal number of ISO session licenses, ordered in quantities matching the associated capacity licenses.
The document also describes perpetual Network Wide License (NWL) options in 50-concurrent-session units. These bundle platform access and baseline features with a defined session capacity. Corresponding advanced NWL licenses require an equal number of NWL session-capacity licenses. When comparing models, account for how the capacity metric and prerequisites apply, rather than comparing only the number of license line items.
What advanced-feature licenses can add
Advanced-feature entitlements cover capabilities used to shape traffic handling, support interworking and collect operational information. The listed functions include:
- Accounting: Creation of call accounting records using RADIUS or flat files stored locally or transferred to an external server by FTP.
- Routing and load balancing: Local-policy routing parameters, including options such as ENUM database and local route table support, plus Session Agent Groups for distributing traffic across core network elements.
- Quality of Service: Collection and reporting of media QoS information such as packet loss, jitter and latency. The ISO entry specifies a QoS-capable module prerequisite.
- Interworking: SIP-H.323 signaling interworking and, where licensed, IPv4-IPv6 interworking for signaling and media. The document notes platform exceptions for IPv4-IPv6 interworking.
- Additional controls and protocols: Fraud-protection functions, MGCP, H.248 and IPsec, with prerequisites specified for some platform and module combinations.
These functions affect more than a feature checklist. For example, a design that requires traffic distribution, protocol interworking or QoS reporting should verify both the relevant license entitlement and any platform-specific prerequisite before the system is configured.
Security and transcoding require separate checks
Security-related license options in the document include administrative security, data integrity and an Advanced Security Suite. Administrative security adds capabilities for password strength and usage policies, user roles and management of administrative users. Data integrity enables FIPS-related capabilities described for the cryptographic module, with hardware and session-capacity prerequisites varying by license model. The Advanced Security Suite combines Data Integrity and Administrative Security features; the document associates the JITC entry with FIPS 140-2 and a specified U.S. government DISA specification.
Codec support is another distinct licensing area. The listed transcoding licenses cover codecs including G.729, AMR-NB, AMR-WB, EVRC, EVRC-B, Opus and SILK. Requirements differ by codec and platform. For example, entries identify Virtual Machine Edition (VME), Acme Packet 4500 hardware with transcoding hardware, or specified platforms with a transcoding module as prerequisites. Confirm the exact codec, session metric and hardware combination in the applicable documentation.
A practical review before deployment
Before finalizing a bill of materials or implementation plan, verify the following against the governing license documentation:
- Identify the applicable base-license model and supported hardware platform.
- Estimate required concurrent sessions across the protocols in scope and select the corresponding capacity metric.
- Map required functions—such as QoS, fraud protection, security, interworking and transcoding—to their separate entitlements.
- Check that advanced-feature quantities match the associated session-capacity licenses where the document requires equal quantities.
- Validate hardware, module and VME prerequisites, along with any stated platform exceptions.
The practical implication is that SBC licensing should be treated as part of solution architecture, not as a final purchasing detail. Separating platform access, session capacity and optional capabilities makes dependencies easier to review and reduces the risk of planning around an entitlement that the selected platform or license combination does not provide. Because the cited document is version-specific and dated, use current Oracle licensing information and the applicable agreement to confirm present-day rights and requirements.