Next

The Loway Keyring

Loway

Revision History
Revision $Revision: 1.5 $ - covers Keyring 0.1.15$Date: 2011/10/24 07:54:22 $L

Table of Contents

1. Introducing the Loway Keyring
1.1. Terminology used
2. Installation
2.1. Installing using RPM
2.2. Setting up a cron job
3. Setting Up QueueMetrics for use with the Keyring
3.1. Activating the keyupdater profile
3.2. Turning off the key expiration message
4. Using the Keyring
4.1. Initial setup
4.2. Loading PPKs
4.3. Adding a QueueMetrics system
4.4. How to’s

Revision history:

1. Introducing the Loway Keyring

The Loway Keyring is a simple dashboard application that allows you to administer multiple instances of QueueMetrics that are deployed on the cloud.

These can be provisioned, scaled up and down and even closed using a web GUI that keeps track of which licenses are installed on each system and that lets you change them as needed.

This model is best suited for deploying a large number of parallel QueueMetrics instances - for example, as a complement of an existing Asterisk cloud offer - without taking the financial risk of purchasing many long-term licenses.

In this way:

  • You can generate a key as soon as your clients ask for it (no delays due to bank payments, different time zones, etc.)
  • If your business model is hosting remote call centers with QueueMetrics, you can purchase QM licenses that last as long as your client has paid you for; if they pay you monthly, you do not have to commit to a four-year license in advance.
  • When each key expires, you can install a different one - you invoice your client for actual usage.

1.1. Terminology used

A pre-purchased key (PPK) is an activation key that you purchase from Loway and specifies an activation period for a given license of QueueMetrics - for example, a PPK that looks like this:

XQI-LOWAY-74KKMREX6TOH1:QM-50/1/90

will eventually convert into a 90-day QueueMetrics key for 50-agents and 1 Asterisk server, counting from the day you convert it.

A license key is the actual key that will be installed in QueueMetrics in order to activate it. It can be installed manually within the ’web.xml’ file or over QM itself, on the License page. It contains a fixed expiration date that cannot be changed once it’s generated.

   Next