Powered by Universal Speech Solutions LLC

 MRCP

RPM Installation Manual

Administrator Guide

 

Revision: 1

Created: September 1, 2017

Last updated: September 1, 2017

Author: Arsen Chaloyan


 

Table of Contents

                     

1  Overview.. 3

1.1         Applicable Versions. 3

1.2         Supported Distributions. 3

1.3         Authentication. 3

2  Installing RPMs Using YUM.. 4

2.1         Repository Configuration. 4

2.2         Repository Verification. 4

2.3         License Server Installation. 5

2.4         License Toolkit Installation. 5

3  Installing RPMs Manually. 6

3.1         Package List 6

3.2         Package Installation Order 6

4  Installing License Files. 8

4.1         Host Information. 8

4.2         License Installation. 8

5  System Daemon. 9

5.1         Starting Daemon. 9

5.2         Stopping Daemon. 9

5.3         Retrieving Daemon Status. 9

5.4         Setting Auto-start on Next Boot 9

 


 

1       Overview

This guide describes how to obtain and install Unispeech License Server on Red Hat-based Linux distributions. The document is intended for system administrators and developers.

1.1      Applicable Versions

Instructions provided in this guide are applicable to the following versions.

 

Unispeech License Server 1.0.0 and above

1.2      Supported Distributions

Packages are currently available only for x86_64 (64-bit) architecture.

 

Operating System

32-bit

64-bit

Red Hat / Cent OS 7

 

box_info.png

 

Note: packages for other distributions can be made available upon request.

1.3      Authentication

An elevated UniMRCP user account is required to obtain the packages. Send a request to

 

services@unimrcp.org

 

2       Installing RPMs Using YUM

Using the Yellowdog Updater, Modifier (yum), a command-line package management utility for Red Hat-based distributions, is recommended for installation of packages.

2.1      Repository Configuration

The content of a typical yum configuration file, to be placed in /etc/yum.repos.d/unimrcp.repo, is provided below.

 

[unimrcp]

name=UniMRCP Packages for Red Hat / Cent OS-$releasever $basearch

baseurl=https://username:password@unimrcp.org/repo/yum/main/rhel$releasever/$basearch/

enabled=1

sslverify=1

gpgcheck=1

gpgkey=https://unimrcp.org/keys/unimrcp-gpg-key.public

 

[unilickit]

name=Unispeech License Server Packages for Red Hat / Cent OS-$releasever $basearch

baseurl=https://username:password@unimrcp.org/repo/yum/unilickit/rhel$releasever/$basearch/

enabled=1

sslverify=1

gpgcheck=1

gpgkey=https://unimrcp.org/keys/unimrcp-gpg-key.public

 

The username and password fields included in the HTTPS URI must be replaced with the corresponding account credentials.

2.2      Repository Verification

In order to verify that yum can properly connect and access the UniMRCP repository, the following command can be used.

 

yum repolist unilickit

 

where unilickit is a name of the section set in the yum configuration file above.

 

In order to retrieve a list of packages the repository provides, the following command can be used.

 

yum --disablerepo="*" --enablerepo="unilickit" list available

 

 

 

 

2.3      License Server Installation

In order to install the license server, including the dependencies, the following command can be used.

 

yum install unilic-server

 

As a result, yum will check and prompt to download all the required packages by installing them in the directory /opt/unimrcp.

2.4      License Toolkit Installation

In order to install the license toolkit only, which provides status retrieval and sample client applications to connect to the license server, the following command can be used.

 

yum install unilic-toolkit

 

As a result, yum will check and prompt to download all the required packages by installing them in the directory /opt/unimrcp.


 

3       Installing RPMs Manually

Packages can be installed manually using the rpm utility. Note, however, that the system administrator should take care of package dependencies and install all the packages in appropriate order.

 

The RPM packages have the following naming convention:

 

$packagename-$universion-$packageversion.el$rhelversion.$arch.rpm

 

where

·         packagename is the name of a package

·         universion is the version number of license toolkit

·         packageversion is the RPM release version

·         rhelversion is the Red Hat version

·         arch is the architecture (x86_64, i686, …)

3.1      Package List

The following is a complete list of RPM packages.

 

Package Name

Description

unilic-toolkit

Unispeech license toolkit.

unilic-server

Unispeech license server.

uniapr

UniMRCP edition of the Apache Portable Runtime (APR) library.

 

3.2      Package Installation Order

Note that all the RPM packages provided are signed by a GNU Privacy Guard (GPG) key. Before starting the installation, you may need to import the public key in order to allow the rpm utility to verify the packages.

 

rpm --import https://unimrcp.org/keys/unimrcp-gpg-key.public

 

 

A package for the APR librariy must be installed first.

 

rpm -ivh uniapr-$aprversion-$packageversion.el$rhelversion.$arch.rpm

 

Then, a package containing the license toolkit should follow.

 

rpm -ivh unilic-toolkit-$universion-$packageversion.el$rhelversion.$arch.rpm

 

Finally, a package containing the license server should follow.

 

rpm -ivh unilic-server-$universion-$packageversion.el$rhelversion.$arch.rpm rpm -ivh

4       Installing License Files

4.1      Host Information

Host information the license server is installed on needs to be retrieved and submitted for generation of license files.

 

Use the installed tool unilicadmin to retrieve the host information.

 

/opt/unimrcp/bin/unilicadmin –i

 

As a result, a text file uninode.info will be saved in the current directory. Submit the file uninode.info for license generation to

 

services@unimrcp.org

 

4.2      License Installation

The obtained license files must be placed into the directory /opt/unimrcp/data/license.

 

cp *.lic /opt/unimrcp/data/license

 

5       System Daemon

This section outlines how to start/stop the license server as a daemon.

 

Upon installation of the server package, a systemd unit file unilic.service is installed in the directory /usr/lib/systemd/system and can be used as follows.

5.1      Starting Daemon

 

systemctl start unilic.service

 

5.2      Stopping Daemon

 

systemctl stop unilic.service

 

5.3      Retrieving Daemon Status

 

systemctl status unilic.service

 

5.4      Setting Auto-start on Next Boot

 

systemctl enable unilic.service