Howto:License Master: Difference between revisions
| Line 5: | Line 5: | ||
==More Information== | ==More Information== | ||
As PBX hosting provider or in large configurations it is of interest to implement a centralized license management. | |||
The advantage of this, new license can be added without to have reset the master PBX. | |||
From one pool of licenses various of master PBXs can be distributed. | |||
A central licensing server instance is needed thus. This can be run on the master Kerberos server or on a seperate hardware without previous PBX function. All licenses purchased by the PBX hosting provider are installed here. The license server runs as Master-PBX. The only task for this PBX is to host the licenses and distribute them to the Frontend and Media PBXs, which are registered as "License only" slaves and will further distribute the licenses to the customer PBXs. | |||
Following screenshot shows the structure and relationships | Following screenshot shows the structure and relationships | ||
Revision as of 10:58, 13 October 2015
Applies To
This information applies to
Build V9 and later.
More Information
As PBX hosting provider or in large configurations it is of interest to implement a centralized license management.
The advantage of this, new license can be added without to have reset the master PBX. From one pool of licenses various of master PBXs can be distributed.
A central licensing server instance is needed thus. This can be run on the master Kerberos server or on a seperate hardware without previous PBX function. All licenses purchased by the PBX hosting provider are installed here. The license server runs as Master-PBX. The only task for this PBX is to host the licenses and distribute them to the Frontend and Media PBXs, which are registered as "License only" slaves and will further distribute the licenses to the customer PBXs.
Following screenshot shows the structure and relationships
