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.

The licensing and entitlements processes work with each other, as follows.

• 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

When changing the Oracle® Enterprise Session Border Controller licensing technique from the legacy license key method to the self-provisioned method, be aware of the following:

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