Support for Nuance SessionXML

GVP 8.1.7 and above support SessionXML for:

• Nuance NR10 over MRCP v2 (recognition)
• Vocalizer 5.7 over MRCPv2 (synthesis)

You can use a single SessionXML file for both recognition and synthesis. Your Nuance documentation explains in detail how to create a SessionXML file.

MRCPv2 Support

When receiving an MRCP request, the MRCPv2 client searches the session configuration parameter object for the Nuance Speech Synthesizer (NSS) session.xml file URL, which is specified by including gvp.config.vrm.nsssessionxml in the RURI of the call.

See Resource Manager Support.

• If the URL is not specified, the MRCPv2 client retains the current behavior.
• If the URL is specified, the MRCPv2 client sends the SessionXML data to the NSS. This action is controlled by the engine-specific provision parameter vrm.client.SendSessionXML. This parameter enables/disables this functionality:
  • true enables the SessionXML file contents to be sent to NSS server.
  • false (default) disables transmission.
  • MRCPv2 supports only the local SessionXML file that is specified in vrm.nsssessionxml. It supports only file:// protocol and absolute path.

Tip

The MRCPv2 client embeds the SessionXML file the contents as-is into the body of the SDP of the INVITE message, when it requests a Speech Resource.

The MRCPv2 client does not validate the contents of the specified SessionXML file. If that file is empty or cannot be read, MRCPv2 returns an error.

Resource Manager Support

On a per application and per tenant basis, the RM allows you to configure the NSS SessionXML URL by specifying it as the configuration parameter gvp.policy.speech-resources.nsssessionxml. RM looks first for this Type-III policy parameter in the IVR Profile and if the search is fruitless, then searches the tenant hierarchy from the bottom up. When found, the RM passes the URL to the MCP handling the request as the SIP Request URI parameter gvp.config.vrm.nsssessionxml.

Tip

Configure this parameter exactly as you would any other IVR Profile/tenant-level configuration parameter.