Setting Up Product-Type, Features, and Functionality
You enable features and functionality primarily through the Setup Entitlements task, where you self-provision features and certain session capacities. The Oracle® Enterprise Session Border Controller is seeded with a default feature set when you first follow the Setup Product task, and is based on software version, the platform on which the software runs, and the product type that you choose.
Note:
Refer to the Self-Provisioned Entitlements and License Keys section in the Release Notes for a list of the methods used to enable features in this release.Initial Setup
Prior to system configuration, you must set up the product, self-provision entitlements, and optionally install license keys to activate features as required. If you log onto an unconfigured Oracle® Enterprise Session Border Controller, the system displays a warning message that a valid product type is required.
Entitlement Provisioning
License provisioning for components of the Oracle® Enterprise Session Border Controller is offered in a Basic bundle and an Advanced Bundle.
- Application Communication Protocol (ACP )
- AMR-25 (NB) royalty
- AMR-WB-25 royalty
- Enhanced Variable Rate Codec (EVRC) royalty
- Enhanced Variable Rate Codec - B(EVRC-B) royalty
- G.729 royalty
- H.323
- High Availability (HA)
- Intrusion Detection System (IDS) advanced
- Intrusion Detection System (IDS) reporting
- National Security Emergency Preparedess NSEP/RPH (GETS)
- SIP Session Recording (SIPREC)
- Session Initiation Protocol (SIP)
- Software Secure Real-time Transport Protocol (SRTP)
- Software Transport Layer Security (TLS)
- Accounting
- ENUM Lookup
- IWF
- Load Balancing
- QoS
- Routing
- AMR-25 royalty
- AMR-WB-25 royalty
- EVRC royalty
- EVRCB royalty
- G.729 royalty
- Software SRTP
- Software TLS
System Setup
Before you begin configuring the Oracle® Enterprise Session Border Controller, you will set the product type with the setup product command, and the features with the setup entitlements command.
Note:
Not all of the features are available on all platforms.Setup Product
ORACLE# setup product
--------------------------------------------------------------
WARNING:
Alteration of product alone or in conjunction with entitlement
changes will not be complete until system reboot
Last Modified 2014-09-24 14:38:59
--------------------------------------------------------------
1 : Product : Enterprise Session Border Controller
Enter 1 to modify, d' to display, 's' to save, 'q' to exit. [s]: 1
Product
1 - Enterprise Session Border Controller
Enter choice : 1
Enter 1 to modify, d' to display, 's' to save, 'q' to exit. [s]: s
save SUCCESS
ORACLE#
Note:
When configuring an HA pair, you must provision the same product type and features on each system.Setup Entitlements
- Type setup entitlements at the ACLI. Currently provisioned features are printed on the screen.
- Type the number of the feature you wish to setup followed by pressing the <Enter> Key. Some features are set as enabled/disabled (provisionable features), and some features are provisioned with a maximum capacity value (provisionable capacity features). The command will let you provision these values as appropriate.
- Type enabled or disabled to set a provisionable feature, or type an integer value for a provisionable capacity feature. Both input types are followed by pressing the <Enter> key.
- Repeat steps 2 and 3 to setup additional entitlements.
- Type d followed by the <Enter> key to review the full range of your choices. Note that disabled entitlements display their state as blank.
- Type s followed by the <Enter> key to commit your choice as an entitlement for your system. After saving the value succeeds you will be returned to the ACLI.
- Reboot your Oracle® Enterprise Session Border Controller.
Editing and Viewing Features
If you are not changing the product type, and you are changing only the features, you can edit the existing feature with the setup entitlements command. Executing this command will display existing features before giving you the option to modify their settings.
The show entitlements command displays the currently provisioned features and controlled features. You may also use the setup entitlements command and type d to display the current features. Upon first executing the setup entitlements command, all features (excluding controlled features) are displayed on the screen.
License Keys and Self-Provisioned Entitlements Compatibility
The Oracle® Enterprise Session Border Controller continues to support any license keys originally purchased and installed pre-self-provisioned-entitlements for enabling system features.
- You must use self-provisioning to enable features and session capacity on all platforms.
- Oracle only provides license keys to enable specific features and capacities not available for self-provisioning, such as codecs and regulatory features .
- Upon migrating to self-provisioned entitlements, the system seeds the current range of your installed license keys to the self-provisioned entitlements. The system's functionality remains identical.
- When you upgrade to self-provisioned entitlements and then downgrade the software to an older version that requires license keys, any pre-existing license keys will still function.
- When you upgrade to self-provisioned entitlements and then change the functionality (such as, adding more SIP sessions or removing a feature set), the new functionality will not be present upon downgrade to an older version that requires license keys.
System Setup with Existing License Keys
- After running setup product and setup entitlements, the system will be seeded with the existing license keys' functionalities.
- When the system is seeded with its previous functionality to the provisioned entitlements system, functionality may be changed with the setup entitlements command.
- You may notice that there are fewer entitlements than there were with license keys. This is normal.
- After setting up self-provisioned features, the show features command will still function to display the previously installed license keys.
Adding and Deleting License Keys
Certain features may only be enabled with license keys, like royalty-based codecs. The following guidelines apply to these license keys:
- Each license key is bound to a specific Oracle® Enterprise Session Border Controller by serial number.
- Oracle does not allow transferring a license key from one Oracle® Enterprise Session Border Controller to another.
- Multiple license keys can be active on the same Oracle® Enterprise Session Border Controller simultaneously.
- If a feature is covered by more than one license key, the latest expiration date applies.
- You can activate and deactivate license keys in real time.
You can request license keys via the License Codes website at http://www.oracle.com/us/support/licensecodes/acme-packet/index.html
Note:
For a list of features enabled with license keys in your software, see the Feature Entitlements section in your version of the Release Notes.License Key Expiration
When a license expires, you are no longer able to use the features associated with it. The Oracle® Enterprise Session Border Controller automatically disables all associated functionality.
To avoid a license unexpectedly expiring and therefore potentially disrupting service, you should track expiration dates and renew licenses well in advance of expiration.
Expired licenses appear in the show features command until you delete them, although you cannot use those features. Deleting an expired license requires that you take the same steps as you do for deleting a valid one.
Add a License Key
Once you have obtained a license key, you can add it to your Oracle® Enterprise Session Border Controller and activate it.
Delete a License Key
You can delete a license from your Oracle® Enterprise Session Border Controller, including licenses that have not expired. If you want to delete a license that has not expired, you need to confirm the deletion.
To delete a license from the Oracle® Enterprise Session Border Controller:
View Installed Features, Entitlements, and Licenses
Use the show entitlements command to display all self-provisioned entitlements and features enabled with license keys.
ORACLE# show entitlements
Provisioned Entitlements:
-------------------------
Session Border Controller Base : enabled
Session Capacity : 16000
Accounting : enabled
IPv4 - IPv6 Interworking :
IWF (SIP-H323) :
Load Balancing : enabled
Policy Server : enabled
Quality of Service : enabled
Routing : enabled
SIPREC Session Recording :
Admin Security :
IMS-AKA Endpoints : 0
IPSec Trunking Sessions : 0
MSRP B2BUA Sessions : 0
SRTP Sessions : 0
TSCF Tunnels : 0
Keyed (Licensed) Entitlements
-----------------------------
LI
Transcode Codec AMR (25 AMR transcoding sessions)
Transcode Codec EVRC (25 EVRC transcoding sessions)
Transcode Codec Opus (25 OPUS transcoding sessions)
Transcode Codec SILK (25 SILK transcoding sessions)
Use the show features to display currently active features on the system. This command shows the union of features enabled with license keys and with the self-provisioning method.
ORACLE# show features
Total session capacity: 16000
Enabled features:
16000 sessions, SIP, H323, QOS, ACP, Routing, Load Balancing,
Accounting, High Availability, LI, External BW Mgmt,
External CLF Mgmt, External Policy Services, ENUM, NSEP RPH,
Transcode Codec AMR (25 AMR transcoding sessions),
Transcode Codec EVRC (25 EVRC transcoding sessions), IDS,
IDS Advanced,
Transcode Codec Opus (25 OPUS transcoding sessions),
Transcode Codec SILK (25 SILK transcoding sessions)
ORACLE(license)# show
License #1: 16000 sessions, SIP, LI,
Transcode Codec AMR (25 AMR transcoding sessions),
Transcode Codec EVRC (25 EVRC transcoding sessions),
Transcode Codec Opus (25 OPUS transcoding sessions),
Transcode Codec SILK (25 SILK transcoding sessions)
expires at 06:28:15 Feb 07 2020
installed at 17:08:15 May 08 2030
Note:
Examples in this section are provided for illustration and may not reflect all available features on your system.Setup Features on an HA Pair
An HA pair requires that you set up identical features on both systems during the same service window. Peers with mismatched features may exhibit unexpected behavior. You should carefully confirm system synchronization at every step.
This procedure uses the designations system-1 as the original active and system-2 as the original standby.