¶ 1 Overview
This guide describes how to obtain and install UniMRCP binary packages 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.
UniMRCP 1.4.0 and above
¶ 1.2 Supported Distributions
UniMRCP RPMs are currently available for x86_64 (64-bit) architecture only.
| Operating System | Released | End of Support |
|---|---|---|
| Red Hat / Cent OS 6 | February 2017 | August 2018 |
| Red Hat / Cent OS 7 | March 2017 | TBA |
| Red Hat / Cent OS 8 | January 2021 | TBA |
Packages for other distributions can be developed and made available in the scope of an annual maintenance agreement.
Contact Form Submit an inquiry¶ 1.3 Authentication
UniMRCP binary packages are available to authenticated users only. In order to register a free account, please visit the following page.
Profile Registration Open an account at unispeech.ioA newly registered account needs to be verified by the user and then activated by the administrator prior further proceeding.
Account verification and activation.
The account credentials can be used to log in to the following websites.
¶ 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 UniMRCP binary packages.
¶ 2.1 Repository Configuration
Configure a repository by creating a file /etc/yum.repos.d/unimrcp.repo with the following content.
[unimrcp]
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
[unimrcp-noarch]
name=UniMRCP Packages for Red Hat / Cent OS-$releasever noarch
baseurl=https://username:password@unimrcp.org/repo/yum/main/rhel$releasever/noarch/
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.
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 unimrcp
yum repolist unimrcp-noarch
where unimrcp and unimrcp-noarch are names of the sections set in the yum configuration file above.
In order to retrieve a list of packages the UniMRCP repository provides, the following command can be used.
yum --disablerepo="*" --enablerepo="unimrcp" list available
yum --disablerepo="*" --enablerepo="unimrcp-noarch" list available
¶ 2.3 UniMRCP Client Installation
In order to install the UniMRCP client binaries, including the dependencies, the following command can be used.
yum install unimrcp-client
As a result, yum will check and prompt to download all the required packages by installing them in the directory /opt/unimrcp.
Similarly, for installation of development kit(s), the UniMRCP client libraries and header files, the following command may follow.
yum install unimrcp-client-devel
¶ 2.4 UniMRCP Server Installation
In order to install the UniMRCP server binaries, including the dependencies, the following command can be used.
yum install unimrcp-server
As a result, yum will check and prompt to download all the required packages by installing them in the directory /opt/unimrcp.
Similarly, for installation of development kit(s), the UniMRCP server libraries and header files, the following command may follow.
yum install unimrcp-server-devel
In order to install a package containing a set of demo plugins to the UniMRCP server, the following command can be used.
yum install unimrcp-demo-plugins
¶ 3 Installing RPMs Manually
UniMRCP RPM 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 UniMRCP version
- 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 list of RPM packages required for installation of UniMRCP client and server.
| Package Name | Description |
|---|---|
| unimrcp-client | Shared libraries and sample applications of the client. |
| unimrcp-client-devel | Development kit of the client. |
| unimrcp-server | Shared library and application of the server. |
| unimrcp-server-devel | Development kit of the server. |
| unimrcp-demo-plugins | Set of demo plugins to the server. [Optional] |
| unimrcp-common | Data common for the client and the server. |
| unimrcp-common-devel | Development kit of the common client and server data. |
| uniapr | UniMRCP edition of the Apache Portable Runtime (APR) library. |
| uniapr-devel | Development kit of the corresponding APR library. |
| uniapr-util | UniMRCP edition of the Apache Portable Runtime Utility (APR-Util) library. |
| uniapr-util-devel | Development kit of the corresponding APR-Util library. |
| unisofia-sip | UniMRCP edition of the Sofia SIP library. |
| unisofia-sip-devel | Development kit of the corresponding Sofia SIP library. |
¶ 3.2 Package Dependency Graph
The following is a graph of package dependencies.
¶ 3.3 Package Installation Order
Note that all the RPM packages provided by UniMRCP 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
Packages for the APR, APR-Util and Sofia-SIP libraries must be installed first.
Packages for the APR, APR-Util and Sofia-SIP libraries must be installed first.
rpm -ivh uniapr-$aprversion-$packageversion.el$rhelversion.$arch.rpm
rpm -ivh uniapr-util-$apuversion-$packageversion.el$rhelversion.$arch.rpm
rpm -ivh unisofia-sip-$sofiaversion-$packageversion.el$rhelversion.$arch.rpm
Then, a package containing common data for the client and the server should follow.
rpm -ivh unimrcp-common-$universion-$packageversion.el$rhelversion.$arch.rpm
Based on your requirements, either a client package, or a server package, or both of them can be installed next.
rpm -ivh unimrcp-client-$universion-$packageversion.el$rhelversion.$arch.rpm
rpm -ivh unimrcp-server-$universion-$packageversion.el$rhelversion.$arch.rpm
Optionally, a package containing a set of demo plugins to the server may follow.
rpm -ivh unimrcp-demo-plugins-$universion-$packageversion.el$rhelversion.$arch.rpm
The same order should be considered for the installation of the corresponding development packages.
¶ 4 System Daemon
Check out the following guide for managing the UniMRCP service.