Master/ Slave Licensing

Chaining

From V10.6.925 - It is possible to set both the master and slave flags on a single installation, allowing an instance of CallGem to accept agent registrations from slaves while also passing them on to a second master instance. Once such a ‘chain’ of masters has been established, an agent registration is reviewed by all of them. If the registration fails the limit checks on any master, the response is passed back down the chain to the slave.

This could be utilised in various ways, e.g.

• a customer could have two master installations, with a secondary acting as a backup and forwarding its requests to the primary
• Sytel may in future offer its own master server to act as a central regulator for customers

Fig. 1 - Master/ Slave Chaining

Fig. 1 shows an example master/ slave chain, where

1. Master Server 1 is the primary master (see Registry Settings), taking registrations from Slave Servers 1, 2 & 3. If the slave servers are unable to connect (see Losing Connection), Master Server 2 will take over as the primary master
2. Both masters in turn request registration from SMaster (or Supermaster) Server, which could be hosted for example in the cloud (e.g. Amazon Web Services (AWS)).