AudioCodes Mediant 4000 SBC, User Manual

Page: 715 / 1037

CHAPTER 38 License Key
Mediant 4000 SBC | User's Manual
The device periodically checks with the OVOC license pool for SBC capacity licenses. OVOC
identifies the device by serial number. If it has an SBC license for the device, it sends it to the
device. If the device's installed License Key already includes SBC capacity figures, the SBC
license allocated from the pool is simply added to it (but up to the device's maximum supported
capacity capabilities). For standalone devices, you
must reset the device with a save to flash for
the allocated SBC license to take effect. If communication with OVOC is lost for a long duration,
the device discards the allocated SBC license (i.e., expires) and resets with its initial, local SBC
license according to the local License Key. This mechanism prevents misuse of SBC licenses
allocated by the OVOC license pool.
When the device operates in High-Availability (HA) mode, the active and redundant devices are
installed with the new SBC license from the OVOC license pool without affecting traffic. This is
achieved by a hitless license upgrade mechanism, whereby OVOC first downloads the license to
the redundant device, resets it, and then triggers the devices to perform an HA switchover. It then
downloads the same license to the previously active device (now the redundant), resets it, and then
triggers another HA switchover. Therefore, currently active calls are maintained throughout the
process.
The device sends the following SNMP alarms relating to the allocation/de- allocation of SBC
licenses by the OVOC license pool:
■ acLicensePoolInfraAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.106)
■ acLicensePoolApplicationAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.107)
■ acLicensePoolOverAllocationAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.125)
For more information on the alarms, refer to the SNMP Reference Guide .
● No configuration is required on the device; OVOC controls the allocation/de-
allocation of its resource pool to the managed devices. For more information on the
OVOC License Pool, refer to the
OVOC User's Manual .
● The allocation/de-allocation of SBC licenses to standalone devices by the OVOC
license pool is service affecting and requires a device reset.
● For HA systems, the OVOC license pool automatically allocates an equal number
of SBC licenses (sessions) to both the active and redundant devices. For example,
if the license pool allocates 200 sessions to the active device, it also allocates 200
to the redundant. Thus, it is important to take this into consideration when ordering
a license pool.
● If the device is restored to factory defaults, the SBC licenses allocated by the
OVOC license pool are removed and the SBC licenses from the locally installed
License Key are applied.
● If the device is allocated an SBC license by the OVOC license pool that exceeds
the maximum number of sessions that the device can support, the device sets the
number of sessions to its maximum supported.
● The Fixed License Pool cannot operate if the Floating License is used. Therefore,
make sure that the Floating License feature is disabled.
SBC Capacity Licenses from Floating License
The Floating License is a network-wide SBC capacity-related license that is dynamically shared
among multiple devices. The Floating License is initially ordered as a single license, which provides
a pool of the following SBC capacity resource types for all your deployed devices:
■ SBC sessions (media and signaling)
■ Signaling sessions
■ User registrations
■ Transcoding sessions
- 682 -