Communications Portal 10
The Enghouse Interactive Communications Portal (CP) runs voice applications but draws its recognition and synthesis from an external speech engine over MRCP. Capacity Private Cloud is that engine, connecting to CP over MRCPv2 (SIP). This guide has been tested with CP 10.0 (formerly Syntellect Communications Portal / Envox Communications Development Platform); for product details, visit enghouseinteractive.com.
Before configuring your CP platform to point at the platform's speech engine, you should have already installed, licensed, and tested your ASR (SRE) Server, TTS Server, Media Server, and License Server (if applicable). This guide assumes some familiarity with the Enghouse Interactive CP administration interface and that Communications Portal 10.0 is already installed and licensed.
CP 10.0 connects to the platform using the MRCPv2 (SIP) protocol. Because both applications use SIP, their default configurations assume port 5060. If you intend to run CP 10.0 and the platform on the same server, you must change the platform's SIP port — see Installing CP 10.0 and the Platform on the Same Server below.
Start CP 10.0
Start the CP Console 10.0 application.
In the Console application, right-click your server and select Start CP Engine(s). Several new tree nodes then appear in the ECS View.
Configure the ASR
Expand Engine Settings > Speech > Interface Configurations > ASR Direct APIs and select MRCP_ASR to open the ASR configuration.
In the MRCP_ASR Configuration window, set the following parameters:
- Number of ASR resources in the resource pool (0 to disable; -1 for auto) — default is
0(resource pooling off). Enter-1for automatic resource pooling. - MRCPv2 server address — always prefix with
sip:, followed by the IP address of the host running the Media Server. If the MRCPv2 server uses a non-default port, use the formatsip:<server_address>:<port_number>. For example, with the default port:sip:172.18.2.139:5060; with a changed port:sip:172.18.2.139:5066. (If the platform runs on the same server as CP 10.0, you will have changed the platform'ssip_port— see the same-server section below — and the port here must match.) - MRCPv2 server vendor — set this to LumenVox. (Other MRCP vendors implement the standard differently, and the client MRCP code may be optimized for a specific MRCPv2 server.)
- SIP Fast Start — must be set to Disabled.
Leave the remaining parameters at their default values.
Configure the TTS
Expand Engine Settings > Speech > Interface Configurations > TTS Direct APIs and select MRCP_TTS to open the TTS configuration.
In the MRCP_TTS Configuration window, set the same parameters as for the ASR:
- Number of TTS resources in the resource pool (0 to disable; -1 for auto) — default is
0; enter-1for automatic resource pooling. - MRCPv2 server address —
sip:followed by the Media Server's IP address (and port if non-default), e.g.sip:172.18.2.139:5060. - MRCPv2 server vendor — set this to LumenVox.
- SIP Fast Start — must be set to Disabled.
Leave the remaining parameters at their default values.
VoiceXML Testing Notes
When a VoiceXML script is loaded on the channel, two fields need to be populated: the VoiceXML application URI (the location of the VXML script) and Configurations.
The Configurations field specifies the speech configuration the VXML script will use. If the script uses both TTS and ASR, this field must specify a speech configuration that contains both TTS and ASR.
CTI Connect Media Gateway Configuration Notes
If you are working with the CTI Connect Media Gateway, you may need to install this service and set its Port Number to 7777.
First, open the CTI Connect Server Configuration utility and select Modify next to the link you created when the gateway was installed.
Then set the port number to 7777, if it is not already:
You may also need to configure the CTI Connect Media Gateway's Access Control List (ACL) to allow it to accept calls.
Installing CP 10.0 and the Platform on the Same Server
If you intend to run CP 10.0 and the platform on the same server, ensure there are sufficient machine resources (CPU, memory, etc.) for both, and make the following configuration change.
Because both applications use SIP, their default settings have them on port 5060, which cannot be shared by multiple applications on the same machine — so one must change. The easier change is the sip_port setting in media_server.conf, which lets the Media Server use an alternate SIP port (for example 5066). Restart the Media Server service after making the change. The exact port is not important as long as it does not conflict with another application's port — ports 5066 or 5068 are typically available. If unsure, ask your network administrator.
Once changed, configure CP 10.0 to use the SIP port the platform is now configured for (e.g. 5066). See the ASR and TTS configuration sections above for how to specify the port in the MRCPv2 server address.
Testing the Integration
Once the system is configured, place a call into the CP 10.0 system and test the ASR MRCP Words project. It should prompt you to say "North, South, East, or West." After you say one of the four words, the platform should confirm your spoken selection back to you. If this works correctly, the TTS and ASR integration is working.