About this task

Use this procedure to configure vendor specific parameters in VoiceXML applications.

Users can use the following VoiceXML properties to set vendor specific parameters:

  • com.avaya.asr.valid.prefix - Specifies valid prefixes for ASR vendor specific parameters which are set and sent to ASR speech server.

  • com.avaya.tts.valid.prefix - Specifies valid prefixes for TTS vendor specific parameters which are set and sent to TTS speech server.

These properties are configured in the <property> element with string value in the VoiceXML application scope where the vendor specific parameters are set.

Procedure

  1. On the MPP server, do the following to configure valid prefixes for ASR and TTS vendor specific parameters to be used in the VoiceXML application:
    1. Add valid vendor prefixes to <parameter name="mpp.vendor.valid.prefix.list"> in the $MPP/config/mppconfig.xml file.
    2. Restart the MPP server.
  2. In the VoiceXML application, do the following:
    1. Specify valid vendor prefixes for ASR and TTS vendor specific parameters.

      • For ASR vendor specific parameters, set the com.avaya.asr.valid.prefix property.

      • For TTS vendor Specific parameters, set the com.avaya.tts.valid.prefix property.

    2. Set the vendor specific parameters which will be applied and sent to vendor.
      Note:

      If the com.avaya.asr.valid.prefix or com.avaya.tts.valid.prefix properties are not configured, all the vendor specific parameters that are specified in the VoiceXML application will be ignored, except the vendor specific parameters which are already supported by the voice browser by default.

      $MPP/config/mppconfig.xml:

…
<parameter name="mpp.vendor.valid.prefix.list">swi;com.ibm.voice.server;com.lumenvox</parameter>
…

VoiceXML application:
<?xml version="1.0" encoding="UTF-8"?>
<vxml xmlns="http://www.w3.org/2001/vxml" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:schemaLocation="http://www.w3.org/2001/vxml 
   http://www.w3.org/TR/voicexml20/vxml.xsd"
   version="2.0">
  <property name="com.avaya.asr.valid.prefix" value="com.lumenvox."/>
  <property name="com.lumenvox.secure_context" value="1"/>
  <form>
  <field name="drink">
     <prompt>Would you like coffee, tea, milk, or nothing?</prompt>
     <grammar src="drink.grxml" type="application/srgs+xml"/>
  </field>
  <block>
     <submit next="http://www.drink.example.com/drink2.asp"/>
  </block>
 </form>
</vxml>
  3. In the $MPP/logs/process/SessMgr directory, open SessionManager.log and verify that the required vendor specific parameter is sent in MRCP SET-PARAMS request to the vendor. 
    $MPP/logs/process/SessMgr/SessionManager.log:

…

FINEST|MRCP|22977|FileName=mrcpv2/Mrcpv2Connection.cpp,LineNumber=300|~Msg: Sending: MRCP/2.0 220 SET-PARAMS 3
Channel-Identifier: 47@speechrecog
confidence-threshold: 0.500000
dtmf-term-timeout: 0
input-modes: dtmf voice
logging-tag: ep-pepm-51-2018310121209-1
n-best-list-length: 1
no-input-timeout: 7000
save-waveform: false
sensitivity-level: 0.800000
speech-complete-timeout: 0
speech-language: en-US
speed-vs-accuracy: 0.500000
vendor-specific-parameters: com.lumenvox.secure_context=”1”; swirec_application_name=”Test”;swirec_company_name="Avaya";swi.rec.logValue=”ANII=419001|DNIS=60504”
…