From innovaphone-wiki

Jump to: navigation, search
There are other versions of this article: Reference | Reference7 | Reference8 | Reference9 (this version) | Reference10 | Reference11r1 | Reference12r1 | Reference13r1

Licenses are used on the innovaphone gateways to enable specific features so that the customers have to pay for features only, which they actually use. There are 3 different types of licenses: For the Gateway (Relay), the PBX and DECT.


Gateway Licenses

Enables the use of the number of DSP channels as specified in the license. A DSP channel is needed for each call to a ISDN interface, an analog Interface or a conference interface. If no license is availabe the call is rejected.
Enables the use of a ISDN Basic Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.
Enables the use of a ISDN Primary Rate Interface. Only licensed interfaces are displayed in the user interface and can be used for calls. Which interface is enabled is chosen by a default sequence. If other interfaces are desired, interfaces can be disabled, which means they do not consume a license.
Enables the gatekeeper functionality on version 7,8 and version 9. Which means the gateway VOIP interface type 'Gatekeeper/Registrar' is available.

Built in Licenses

Since the release of version 7 some hardware platforms already come fully equipped with all necessary interface licenses. The units are:

  • IP22
  • IP24
  • IP28
  • IP302

This includes also the required Channel licenses. Built-in licenses are not shown in the Licenses table in Gateway / General.

PBX Licenses

All PBX licenses contain a version number, which is indicated by <v> in the follwing text (Example: Port<v> for Version 9 is Port9).

If on a PBX licenses of the same type but with different versions are installed, the lowest version is used for all licenses of this type (Example: If Port8=50, Port9=100 and Port10=50 is installed, the effektive license is Port8=200).

For licenses used on the PBX itself (Port, IPVA, Mobility, Voicemail, Standby) the version must be at least the version of the PBX (Example on a PBX Version 9, Port8 cannot be used, but Port9, Port10, ...).

For licenses used by external applications (SoftwarePhones, Operator, QueueMonitor, Reporting), the version of the external applications defines which license is needed. (Example: On a PBX Version 9, an Operator8 license maybe installed).

Port License. To register endpoints at PBX objects. Multiple endpoints can register at one object and only one port license is used. A port license gets used when an object has at least one registration. Objects without registration do not use licenses.
Port License. To register endpoints at PBX objects. This SMB version can not be installed at a slave PBX and can only be used for one device/project. Maximum 20 Ports of this SMB version are possible, for more ports normal port licenses must be added.
IPVA License. To allow registrations at the PBX running on IPVA, this license is needed in combination with the PORT9 (PORT9*20) license. As much as PORT9 licenses are in use as much IPVA9 licenses are needed. There may be less IPVA9 licenses installed then Port9 licenses, because with slave obtaining their license from a Master PBX some Ports may be used on IPVA and some on Gateways.
License to enable Mobility function for a user object.
License to use the innovaphone voicemail script. Must be at least the same as the port license.
License to enable Standby operation. Must be at least the same as the port license. With this license a PBX accepts registrations from endpoints not configured for this PBX, which should happen only if the PBX where the endpoint is configured for, is not available. A standby license installed without a port license does not do anything.
License to use a innovaphone software phone (not for the Bria softphone)
License to use the innovaphone operator software.
License to use the PBX queue monitor , one license needed per queue monitor.
License to use the reporting application. For each object that reports are generated for, a license is needed. The reporting license must not be the same size as the port license.

Port licenses are used for trunk, executive, gateway ,user and PBX objects (for registering slave and dyn PBXs).

** Note : If you do any License changing, adding or deleting, the PBX needs a reboot so that the license changes become effective.

Example IPVA

Running a PBX on IPVA with 100 port licenses, 90 port licenses are in use (there are registrations on 90 objects), then also 90 IPVA licenses are needed. When a new endpoint tries to register at a new object, the registration will be denied. There are enough port licenses that a endpoint could register, but not enough ipva licenses. If there are more registrations on one user object only one port license is in use and thus only one ipva license needed.

VMware HA and FT

Using the VMware HA (high availability solution) or the FA (Fault Tolerance) with the innovaphone IPVA, no extra innovaphone licenses are needed (even no standby license).

  • Note : This VWware features are not yet tested by innovaphone

Example PBX-QueueMonitor

This is a concurrent licence, means if one queue monitor connects at the PBX one license is consumed, if the queue monitor is off the licence gets released. Example 1: One waiting queue should be monitored by 5 PBX-queue monitor, so 5 licenses are needed. Example 2: 3 waiting queues, on the first waiting queue 3 PBX queue monitor ,on the second one PBX monitor and on the third no PBX monitor. So 4 licenses are needed.

Example Reporting

A PBX with 100 port licenses, but only for the waiting queue and 10 user objects reports should be done. Therefore only 11 reporting licenses need to be purchased. On the waiting queue and the 10 user objects the reporting chek-mark must be set, then the innovaphone reporting can generate reports for that objects.

Example Mobility

A user object requires a Port license if there is at least one registration on it. A user using a mobility object (that is, a forking destination and a mobility object is defined) requires a Mobility license per destination. A forking destination with no mobility object defined require no Mobility license. The mobility client (which is to be installed on the mobile phone) will require a GSM license.

So if you create a user object with a VoIP terminal registration and a forking destination with mobility, then you will need 1 Port license and 1 Mobility license. If on the user object there are no registrations but a forking destination with mobility enabled, then it will need 1 Mobility license but no Port license. If there are no registrations and a forking destination without mobility, then no license at all is required.

The standard configuration (a user object with registrations and a mobility enabled forking destination and a mobile phone with mobile client installed) requires 1 Port plus 1 Mobility plus 1 GSM license.

A mobility license is also required for disabled forking destinations.

In summary you also can have more Mobility lics than you have port lics.

PBX Floating mechanism

If no Port license is installed locally on a slave/standby PBX it obtains automatically all PBX licenses from the master. If this option is used, Port licenses need to be installed for the total number of endpoints in the system on the master.

Slaves with locally installed licenses can be mixed with Slaves obtaining their licenses from the master.

A slave/standby stores the received license in flash memory so it can still operate even if the master is not available.

License updates between master and slaves are sent in intervals of approximately 10min to limit the bandwidth usage. Because of this it may happen that temporarily more licenses can be used than actually available.

It is not necessary/possible to buy floating licenses. You can use them without a balance in There is no license needed at all to use the floating mechanism.

It is possible to use a V8 Slave and a V9 Master Firmware.

Licensing for Standby operation

If a PBX shall operate as standby (either as dedicated standby or as a master being standby for a slave, or as a slave being standby for a master), a standby license with at least the value of the Port license must be available. This Standby license can be obtained from the Master by the use of the Floating mechanism.


Dedicated Standby (Standby/Standby-Slave)

No PBX licenses should be installed on the Standby, to obtain the licenses from the master and a Standby license of the correct size has to be installed on the master.

Master acting as Standby

If a master should accept registrations which are configured for slaves, in case the slaves are not available a Standby license of at least the size of the Port licenses needs to be installed on this master.

Slave acting as Standby for Master

If a slave should accept registrations which are not configured for this slave, in case the master is not available, a standby license of at least the size of the Port license must be available on the slave. If the licenses are obtained from the master by the use of the Floating mechanism the Standby license must be installed on the master, if local licenses are used, the standby license must be installed on the slave.

Note: Standby registrations do not require licenses, so the counter will not increase, this is by design.

DECT Licenses

Multicell The Multicell license enables the Multicell master and defines the System Identification (ARI) on the wireless side, installed on the IP1200.
Personal tools