MRCP
Google SS Plugin
Administrator Guide
Distribution: Debian / Ubuntu
Created: May 24, 2018
Last updated: March 15, 2021
Author: Arsen Chaloyan
Table of Contents
2 Installing Deb Packages Using Apt-Get
3 Installing Deb Packages Manually
3.2 Package Installation Order
5 Obtaining Service Credentials
6 Configuring Server and Plugin
6.1 Plugin Factory Configuration
This guide describes how to obtain and install binary packages for the Google Speech Synthesis (GSS) plugin to the UniMRCP server on Debian-based Linux distributions. The document is intended for system administrators and developers.
Instructions provided in this guide are applicable to the following versions.
UniMRCP 1.5.0 and above UniMRCP GSS Plugin 1.0.0 and above |
UniMRCP deb packages are currently available for x86_64 (64-bit) architecture only.
Operating System |
Released |
End of Support |
Ubuntu 16.04 LTS (xenial) |
June 2018 |
March 2021 |
Ubuntu 18.04 LTS (bionic) |
May 2019 |
TBA |
Ubuntu 20.04 LTS (focal) |
March 2021 |
TBA |
Note: packages for other distributions can be made available upon request. For more information, contact services@unimrcp.org.
UniMRCP binary packages are available to authenticated users only. In order to register a free account with UniMRCP, please visit the following page.
Note: a new account needs to be verified and activated prior further proceeding.
Using the APT package handling utility (apt-get) is recommended for installation of UniMRCP binary packages.
Supply login information by creating a file /etc/apt/auth.conf.d/unimrcp.conf containing the following entry.
machine unimrcp.org login username password password |
Note: the username and password fields must be replaced with the corresponding account credentials.
Configure a repository by creating a file /etc/apt/sources.list.d/unimrcp.list containing the following entry.
deb [arch=amd64] https://unimrcp.org/repo/apt/ distr main |
Note: the distr field must be replaced with the corresponding distribution code name such as xenial, bionic, focal, etc. To determine the distribution code, use `lsb_release -cs`.
For verification of binary packages, UniMRCP provides a public GnuPG key, which can be retrieved and installed as follows.
wget -O - https://unimrcp.org/keys/unimrcp-gpg-key.public | sudo apt-key add - |
In order to check for updates and apply the changes in the APT configuration, use the following command.
sudo apt-get update |
In order to install the GSS plugin, including all the dependencies, use the following command.
sudo apt-get install unimrcp-gss |
As a result, apt-get will check and prompt to download all the required packages by installing them in the directory /opt/unimrcp.
In order to install the additional data files for the sample client application umc, the following command can be used.
sudo apt-get install umc-addons |
Note: this package is optional and provides additional data which can be used for validation of basic setup.
UniMRCP deb packages can be installed manually using the dpkg utility. Note, however, that the system administrator should take care of package dependencies and install all the packages in appropriate order.
The deb packages have the following naming convention:
$packagename_$universion-$distr_$arch.deb |
where
· packagename is the name of a package
· universion is the UniMRCP version
· distr is the distribution code name (trusty, xenial, …)
· arch is the architecture (amd64, i386, all, …)
The following is a list of UniMRCP deb packages required for the installation of the GSS plugin.
Package Name |
Description |
unimrcp-gss |
GSS plugin to the server. |
unigrpc |
UniMRCP edition of the gRPC library. |
umc-addons |
Sample en-US data files used with umc. [Optional] |
unilicnodegen |
Node information retrieval tool, required for license deployment. |
unimrcp-server |
Shared library and application of the server. |
unimrcp-client |
Shared libraries and sample applications of the client. [Optional] |
unimrcp-demo-plugins |
Set of demo plugins to the server. [Optional] |
unimrcp-common |
Data common for the client and the server. |
uniapr |
UniMRCP edition of the Apache Portable Runtime (APR) library. |
uniapr-util |
UniMRCP edition of the Apache Portable Runtime Utility (APR-Util) library. |
unisofia-sip |
UniMRCP edition of the Sofia SIP library. |
Packages for APR, APR-Util and Sofia-SIP libraries must be installed first.
sudo dpkg --install uniapr_$aprversion-$distr_$arch.deb sudo dpkg --install uniapr-util_$apuversion-$distr_$arch.deb sudo dpkg --install unisofia-sip_$sofiaversion-$distr_$arch.deb |
Then, a package containing common data for the client and the server, and a package for the server should follow.
sudo dpkg --install unimrcp-common_$universion-$distr_$arch.deb sudo dpkg --install unimrcp-server_$universion-$distr_$arch.deb |
Next, a package containing the utility tool unilicnodegen, required for license deployment.
sudo dpkg --install unilicnodegen_$toolversion-$distr_$arch.deb |
Next, a package containing the gRPC library.
sudo dpkg --install unigrpc_$grpcversion-$distr_$arch.deb |
Finally, a package containing the GSS plugin should follow.
sudo dpkg --install unimrcp-gss_$universion-$distr_all.deb |
The GSS plugin to the UniMRCP server is a commercial product, which requires a license file to be installed.
The following license types are available:
· Trial
· Production
· Test and Development
The license files are bound to a node the product is installed on. In order to obtain a license, the corresponding node information needs to be retrieved and submitted for generation of a license file.
Use the installed tool unilicnodegen to retrieve the node information.
sudo /opt/unimrcp/bin/unilicnodegen |
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 by mentioning the product name in the subject.
The license file needs to be placed into the directory /opt/unimrcp/data.
sudo cp umsgss_*.lic /opt/unimrcp/data |
Create a project in the Google Cloud Platform Console, if not already created. Projects allow to manage all Google Cloud Platform resources, including deployment, access control, billing, and services.
1. Open the Cloud Platform Console. https://console.cloud.google.com 2. In the drop-down menu at the top, select a project My First Project created by default or create a new project. |
Enable billing for your project, if not already enabled. Enabling billing allows the application to consume billable resources such as Text-to-Speech API calls. See Cloud Platform Console Help for more information about billing settings.
In the Google Cloud Platform Console, navigate to API & Services and enable the Text-to-Speech API.
Download a service account credentials file.
1. In the Google Cloud Platform Console, navigate to API & Services > Credentials > Create credentials > Service account key 2. Under Service account, select New service account. 3. Under Service account name, enter a service account name of your choice. For example, accessor. 4. Under Role, select Project > Owner. To better understand the Cloud IAM roles that you can grant to your service account to access Cloud Platform resources, check out the following page. https://cloud.google.com/iam/docs/understanding-roles 5. Under Key type, leave JSON selected. 6. Click Create to create a new service account and download the json credentials file. |
The downloaded json credentials file needs to be placed into the directory /opt/unimrcp/data.
sudo cp *.json /opt/unimrcp/data |
In order to load the GSS plugin into the UniMRCP server, open the file unimrcpserver.xml, located in the directory /opt/unimrcp/conf, and add the following entry under the XML element <plugin-factory>. Disable other synthesizer plugins, if available. The remaining demo plugins might also be disabled, if not installed.
<!-- Factory of plugins (MRCP engines) --> <plugin-factory> <engine id="Demo-Synth-1" name="demosynth" enable="false"/> <engine id="Demo-Recog-1" name="demorecog" enable="true"/> <engine id="Demo-Verifier-1" name="demoverifier" enable="true"/> <engine id="Recorder-1" name="mrcprecorder" enable="true"/> <engine id="GSS-1" name="umsgss" enable="true"/> </plugin-factory> |
In order to enable log output from the plugin and set filtering rules, open the configuration file logger.xml, located in the directory /opt/unimrcp/conf, and add the following entry under the element <sources>.
<source name="GSS-PLUGIN" priority="INFO" masking="NONE"/> |
The configuration file of the plugin is located in /opt/unimrcp/conf/umsgss.xml. Default settings should be sufficient for general use.
Refer to the Usage Guide for more information.
Validate your setup by using the sample UniMRCP client and server applications on the same host. The default configuration and data files should be sufficient for a basic test.
Launch the UniMRCP server application.
cd /opt/unimrcp/bin sudo ./unimrcpserver |
In the server log output, check whether the plugin is normally loaded.
[INFO] Load Plugin [GSS-1] [/opt/unimrcp/plugin/umsgss.so] |
Next, check for the license information.
[NOTICE] UniMRCP GSS License
-product name: umsgss -product version: 1.0.0 -license owner: Name -license type: trial -issue date: 2018-05-11 -exp date: 2018-06-10 -channel count: 2 -feature set: 0 |
Next, check for the service account credentials.
[NOTICE] Set Google App Credentials /opt/unimrcp/data/My First Project-a78…c15.json |
Note: the optional package umc-addons must be installed for this test to work.
Launch the sample UniMRCP client application umc.
cd /opt/unimrcp/bin ./umc |
Run a typical speech synthesis scenario by issuing the command run bss1 from the console of the umc client application.
run bss1 |
This command sends a SPEAK request to the server and then records synthesized stream into a PCM file stored in the directory /opt/unimrcp/var.
Visually inspect the log output for any possible warnings or errors.