Speech Server using MRCPv2: First call fails but second call succeeds when Nuance is configured to use hostname

Last Updated : Dec 02, 2013 |

If the configuration for an Experience Portal speech server is set to use MRCPv2 (TLS or TCP) and the Engine Type is Nuance, then the MPP might not be able to resolve the hostname sent in the contact tag from the SIP 200 OK that speech server sends back.

Proposed Solution 1: Set “useHostIPAddress” to 1

Procedure

  1. On each Nuance server machine, log in to the operating system and navigate to the directory in which Nuance NSSserver.cfg is stored.
  2. Open the NSSserver.cfg file in an ASCII editor.
  3. Modify the value for the parameter useHostIPAddress to set the value to 1.
  4. Save and close the file.
  5. Restart the Nuance server.
  6. Repeat this procedure for any other Nuance ASR servers in the Experience Portal system.

Proposed Solution 2: Add speech server hostname to local hosts file on all MPPs

Procedure

  1. Log on to Linux on the Experience Portal server with root privileges.
  2. Take a back up of the original file prior to editing the file by entering the cp /etc/hosts /etc/hosts.bak command.
  3. Open the /etc/hosts file in an ASCII text editor of your choice.
  4. Create a new line for each speech server in the Experience Portal system using the format IP_address hostname1 hostname2... where:

    • IP_address is the IP address of a server in the Experience Portal system.

    • hostname1 hostname2... is one or more hostnames, separated by tabs or spaces, to associate with the IP address.

  5. Save and close the file.
  6. Repeat this procedure for each MPP in your Experience Portal system.