Enterprise -> Licensing
License Types
TAP - TAPI (TCP 21050, 21051 (TLS))
SDK - SIMPLE (TCP 21055) (Telnet connection)
SDK - OAI (TCP 21054)
SDK - Javascript (TCP 21056) (Events)
SDK - .NET UCAPI (TCP 21050, 21051 (TLS)) (Events)
SDK - .NET UCClient (TCP 21050, 21051 (TLS)) (Events)
Registration details
Please ensure that the details entered into these boxes is accurate as they may need to be referred to at some point in the future.
Serial number
Please ensure that you enter your unique serial number here carefully to avoid problems with licensing.
Refresh licenses button
If your existing license has been upgraded in some way, you can click the 'Refresh licenses' button to re-load the updated license information from the Internet. You will need to have an active internet connection.
Manual registration button
If you do not have internet connectivity you may add new licenses manually. To add another license, press the 'Manual Registration' button and enter the code that you have been provided with. If you have not been provided with the unlock code please get access via an internet enabled device to the website link provided where you can obtain the unlock code(s).
Release license button
If you have previously registered Mirage and you want to move the software to another computer then you must release the software from the original machine. To do this, press the 'Release license' button and write down the code that you are given.
Before installing Mirage on the new server you must make your Mirage Maintainer aware that you are moving the license. They will need the serial number and the release code you have been provided.
The steps below should be used when migrating an existing Mirage Server configuration to a new machine. It is assumed Mirage has been installed on the new machine prior to these steps being undertaken.
- Logon to the original Mirage server, release the license and note the release code. Contact the Mirage support team and provide them with the serial number and the release code from the original Mirage Server.
- Stop the service: SQL Server (UCSERVER)
- Navigate to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ and check to see if the UCServer.mdf file exists at this location. * If it does not then search computer for this file and navigate to the directory located by the search.
- Copy the UCServer.mdf and UCServer_LOG.ldf files to a secure location as they will be used later.
- On the new machine, stop the service: SQL Server (UCSERVER)
- Navigate to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ and check to see if the UCServer.mdf file exists at this location. If it does not then search computer for this file and navigate to the directory located by the search. **
- Paste the saved UCServer.mdf and UCServer_LOG.ldf from the original Mirage server to this location which should overwrite the newer, existing files.
- Restart the following Services on the new machine in this order:
- SQL Server (UCSERVER)
- Mirage Server Service.
* This is the default location of the database files for version 2.3.10 and older of Mirage. It assumes that no other instances of SQL had been installed on the machine prior to the installation of our software. The exact location of these files is controlled by SQL and can change.
** This is the default location of the database files for version 2.3.17 and newer of Mirage. It assumes that no other instances of SQL had been installed on the machine prior to the installation of our software. The exact location of these files is controlled by SQL and can change.
Licensing assistance button
Click this button to view additional help with licensing.
Active licenses
Once registration is complete, you will see a list of active licenses appear. If this list is not correct please contact your software supplier.
Report this page