My favorites ▼ | Sign in
Project Home Downloads Wiki Issues Source
Search
for
InteroperabilityGuide  
MRCP vendors/products UniMRCP client and server are known to work with.
Phase-Deploy, Id-30
Updated Jun 16, 2010 by achalo...@gmail.com

Overview

This guide provides information regarding UniMRCP interoperability. UniMRCP has been developed in accordance with the MRCP specifications. Therefore, UniMRCP client and server should inter-operate with all MRCPv1 and MRCPv2 compliant implementations.
Below is the list of MRCP vendors/products UniMRCP client and server are known to work with. The interoperability has been tested internally either on UniMRCP or vendor side.


UniMRCP Server

Vendor MRCPv1 MRCPv2
Voxpilot Completed N/A
Aculab Completed N/A
Holly-Connects Completed N/A


UniMRCP Client (TTS)

Vendor MRCPv1 MRCPv2
Nuance Completed Completed
IBM WVS Completed N/A
Speech Technology Сenter Completed N/A


UniMRCP Client (ASR)

Vendor MRCPv1 MRCPv2
Lumenvox Completed Completed
Nuance Completed Completed
IBM WVS Completed N/A
Speech Technology Сenter Completed N/A



If you used UniMRCP client or server with MRCP vendors/products not mentioned above, please leave a comment below by providing the following information

  • Vendor:
  • Protocol: MRCPv1 and/or MRCPv2
  • Resource: ASR and/or TTS
If you experienced interoperability issues, please submit them to the issue tracker.

Comment by project member chaitany...@gmail.com, Apr 5, 2009
  • Vendor:Telisma
  • Protocol: MRCPv1
  • Resource: ASR
Comment by project member bayrambo...@gmail.com, Apr 9, 2009
  • Vendor: Avaya IR
  • Protocol: MRCPv1
  • Resource: TTS
Comment by project member chaitany...@gmail.com, Apr 30, 2009
  • Vendor:Nuance
  • Protocol:MRCPv1 and/or MRCPv2
  • Resource:ASR
Comment by project member chaitany...@gmail.com, Apr 30, 2009

For nuance we had one or two issues. We had to set the contentid in the MRCP header to testrecog@speechworks.com or something like xxxx@speechworks.com, also we had to modify the mrcpv1 and v2 params in the nuance configuration file.

Comment by sadeek.k...@gmail.com, Aug 7, 2009
  • Vendor: Cisco CVP 4.0
  • Resource: TTS & ASR
  • Protocol: MRCPv1
  • Status: In Progress
Comment by project member tomas.valenta@speechtech.cz, Aug 17, 2009
  • Vendor: Genesys Voice Platform (client)
  • Resource: TTS & ASR
  • Protocol: MRCPv1
  • Status: There is a bug (probably in GVP)

GVP rejects RTSP response to DESCRIBE RTSP request on speechrecognizer resource. The problem is in the Transport header of the response, GVP says client_port does not match. (How could we know client port without Transport header or SDP in request?) Excluding Transport header from the response solves the issue. So generally, is it necessary to include transport header in the response for RTSP DESCRIBE? I think it is a bug of GVP, that is why I have not put it on issue tracker. It can be easily patched by commenting out lines 540--543 in mrcp_unirtsp_sdp.c (r1086).

Comment by project member jeanmich...@gmail.com, Nov 19, 2010
  • Vendor: Acapela
  • Protocol: MRCPv1 and/or MRCPv2
  • Resource: TTS

Remarks:

Acapela TTS for Linux and Windows Server have 2 Server add-on implementing MRCP.

  • Acapela TTS MRCP add-on 1.300 is a proprietary implementation of MRCPv1 and is compatible with UniMRCP 1.000 client stack (with MRCPv1 protocol)
  • Acapela TTS MRCP add-on 2.002 is based on UniMRCP 1.000 server stack for MRCPv2 TTS server implementation and is of course compatible with UniMRCP client stack (with MRCPv2 protocol)

More info

Comment by beh...@avaya.com, Jun 2, 2011
  • Vendor: Loquendo
  • Protocol: MRCPv1
  • Resource: ASR and TTS

► Sign in to add a comment
Powered by Google Project Hosting