A count based license can be dynamically floated and shared among the SBC in a network licensing mode. It also allows the enforcement of the number of sessions purchased in local and network licensing modes.
The SBC supports three license modes:
Legacy Mode: The Licenses are encoded to a unique SBC instance based on system information to a particular SBC and this is an xml-based SBC license model.
Legacy licensing mode is the default license mode on the SBC. Legacy licensing is currently the only option available for users deploying hardware SBCs. Local and Network license modes are currently limited to specific SBC deployments. For more information, contact the Sonus Technical Assistance Center (TAC).
Local Mode: The licenses are fixed to the SBC and cannot be shared by other devices in the network. Licenses are installed on SBC through EMA or a new CLI interface by applying an xml-based license bundle. The xml-based license adopts the new license format, which includes additional data such as purchase order information.
- Network Mode: The licenses are assigned dynamically by an SLS server based on demand as traffic increases. When the traffic decreases, the licenses are returned to the server. These licenses can float between SBCs based on the demand. Licenses are pooled centrally in the SLS server which is co-located with the EMS.
For more information on supported licenses, refer to SBC Node-Locked Licenses for HW and SWe SBCs.
The SBC supports two types of license, instance and counted.
- Instance licenses enable a feature system wide.
- Counted licenses limit a customer to the number of licenses purchased for a particular service.
- In a legacy or local license mode, x is the license units purchased by the user and is part of the xml bundle that is applied directly at the SBC. When the license limit is zero, it indicates that no license is purchased.
- In a network license mode, x is limited by the number of units available at the Site License Server (SLS), the maximum count configured with the license in the required license table or any basic platform restriction. For example, Call Admission Control (CAC) or media profile configuration.
callCountIntervalStatistics table provides usage statistics for services enforced by a counted license. For more information on statistics, refer to Configuring Licenses Using CLI.