How to configure?¶
Some parameters can be defined only in the configuration files <use-config-file>`, other parameters can be defined via API.
Warning
Configurations defined in the files are read only at system startup, therefore you must restart the ASR Server after the configurations have been modified.
The engine.conf file¶
The recognition engine is configured using the file /opt/cpqd/asr/config/engine/engine.conf
. The configuration parameters follow the format: --nome=valor
. Comments must be preceded by #
.
For example, to configure the parameter decoder.maxSentences
with a value of 5, edit the file engine.conf
and define the line: --decoder.maxSentences=5
, as shown below:
# ==================================
# Configure License
# ==================================
--licenseManager.licenseId=AB9AB9AB9AB9AB9
--licenseManager.channels=10
# ==================================
# Configure recognition
# ==================================
#--lm.preloadModels=builtin:slm/general
--decoder.maxSentences=5
#--decoder.confidenceThreshold=30
The config.yml file¶
The recognition server is configured using the file /opt/cpqd/asr/config/server/config.yml
in the YAML format. Parameters can be indicated using slashes “/”. Comments are preceded by #
.
For example, the parameter logging/loggers/br.com.cpqd
can be configured with DEBUG
, editing the file config.yml
, as shown below:
logging:
level: WARN
loggers:
br.com.cpqd: DEBUG
Configuration by the API¶
The way to define the configuration parameters presented by means of an API must be verified in the section corresponding to the desired API: WebSocket and REST.
The MRCP interface has its own standardization of parameter names and configuration method. For more information, please see the MRCP API section.