Validation Visa VoiceXML Media Server 3.6.1 GA 24/09/2012 M.B. Rakoto. Y.Evain

Release Details Version Information Product Version Date Integration Visa Validation Visa VoiceXML Media Server 3.6.1 GA 24/09/2012 M.B. Rakoto. Y.Evain Approbation Components Name Version Description 3.13.0 Build 1 Provides VoiceXML Interpretation functions. 3.13.0 Build 1 Provides SSML Processing functions. MIOSIP 1.13.0 Build 1 ADTCP 1.9.0 Build 0 Media Resource Function: Provides SIP interface, media processing, and MRCP control of ASR resources. Media Resource Function: Provides TCP interface between MIOSIP and. System Requirements Domain Description Operating Systems RedHat Enterprise Linux Enterprise Server Release 5 (Nahant Update 6) Minimum Hardware Requirements Dual 3.2 GHz Intel Xeon RAM: 2 GB Disk: 500 MB Updates From v3.6.0 To v3.6.1 Component CR ID Task ID Description MIOSIP MRCPv1 keep alive feature MIOSIP RTCP Updates From v3.5.3 To v3.6.0 Component CR ID Task ID Description VoiceXML Media Server v3.6.1 1/12 GEN OMP 4044E

MIOSIP ADTCP Build on RHEL 5 Linux operating system 2122 ENHANCEMENT: Added HMP license management to console Now check license validity once a day or when license refresh action is enabled from the Management Console. When license expiration is imminent, thevoicexml Media Server alerts this status on daily license checking via SNMP. Added parameters: 2150 FIX SWI semantics interpretation - LicenseValidationTime in vxmlinterpreter.conf to set the hour of checking license each day. - "LicenseExpirationAlert" in vxmlinterpreter.conf the number of days to consider a license expiration to be imminent. FIX TTS permission handling Considering Billing TTS contents change: from denying some TTS feature state to authorising all TTS features state (when TTS feature permission content is empty). Updates From v3.5.2 To v3.5.3 Component CR ID Task ID Description 1686 ENHANCEMENT: Authorization exchange implementation Now allow a thinnest control on ASR and TTS. The optional element <com.voxpilot:featurepermission> may be use to authorise or deny a particular ASR engine or a particular TTS voice. ASR features may be filtered by Vendor, Language or/and EngineType parameters. TTS features may be filtered by Vendor, Language, Gender or/and Voice parameters. 1882 1885 FIX: Not responding channels. 2054 FIX: file descriptor leak on SSML processor and VoiceXML interpreter. Added new configuration setting to clean up CURL session in CLOSE_WAIT state after a specified timeout: - CurlSessionCleanup, in VxmlInterpreter.conf, default value is 120s. - ResourceManagerCurlSessionCleanup, in Ssmlinterpreter.conf (default: 120s). ENHANCEMENT: Throw NO RESOURCE error when no language is found for playing audio and prompt tags from VXML files. 2309 FIX: channels creation lock on starting on VMS installation by setting fs.mqueue.msgsize_max to 8448 when possible. VoiceXML Media Server v3.6.1 2/12 GEN OMP 4044E

Updates From v3.5.1 To v3.5.2 Component CR ID Task ID Description 1682 ENHANCEMENT: Logging a warning when an audio file cannot be played 1935 ENHANCEMENT:added param "vxmlstatusnotifying" in vxmlinterpreter.conf to allow sending an error if vxml initial document not found. Data sent in SIP BYE body : exit= voxpilot_not_found & reason=exit Updates From v3.5.0 To v3.5.1 Component CR ID Task ID Description 8318 ENHANCEMENT: Now allow ASCII alpha-numeric characters when adding VoiceXML applications to the configuration. 8280 ENHANCEMENT: Changed log message from CallPlacer from "Could not get an instance for the outbound call to "No channels available to make the outbound call. dial-id=xx obnumber=xx". Also added number of calls processed by channel, and system total, to message "Channel X finished processing call" to aid debugging and parsing of logs. 60397 8195 FIX: Fixed crash with http request longer than 1024 characters 60940 8266 FIX: Now check system limit (of 256) for number of child SSML elements applied for prompt, choice, emphasis, and other SSML elements (ie. audio, break, lexicon, mark, paragraph, phoneme, prosody, sayas, sentence, and voice). This avoids constructing large SSML strings which were causing instability on RHEL. 8317 ENHANCEMENT: Now support draft 10 of MRCP v2 (which is deprecated, but still in use by some ASR and TTS vendors). - Ensure lowercase "application/sdp" is used as Content-Type in INVITE - Check to see if format field (" 1") is missing from application m-line in SDP in response. 60447 8226, 8225 ENHANCEMENT: Can now set a timeout for transfer of files that are streaming, separate from the usual fetchtimeout. Added new configuration setting to specify this value, ResourceManagerStreamTimeout, value in seconds, minimum 0, maximum 2147483647, default 120. Note value 0 disables the timeout. 8170 FIX: Fixed crash playing 3gp files with H264/G729 codec 8222 FIX: Fixed memory leak playing 3gp file with H264 codec 8221 FIX: Fix to avoid buffer too small error when playing back 3gp files. 60310 8177 FIX: Fixed log messages for long messages, which was causing a crash. 8197 FIX: Fixed log messages which were causing a crash when using MRCP v2. MIOSIP 61162, 2817 8311 FIX: Now correctly pass any builtin grammar which has failed local activation down to the ASR engine. Previously, this was causing a issue with proprietary third-party builtin grammars when inputmodes was set to voice only. VoiceXML Media Server v3.6.1 3/12 GEN OMP 4044E

MIOSIP 61062 8284 FIX: Fixed a situation where a race condition was occurring if making an outbound call failed and a retry was being attempted. Added some extra checks for certain error conditions when placing outbound calls (e.g. receiving a 5xx class message after a 1xx class message, or timeout after a 1xx message). Now correctly store call start time for outbound calls so the call duration is correctly calculated for statistics and log message at the end of the calls. Now correctly report a busy status if we receive a SIP 480 for an outbound call. MIOSIP 8238 FIX: Fixed the value of BargeInTime (= 0) if recognition comes from a stored buffer MIOSIP 60451 8237 FIX: Now if a previous DTMF recognition buffer exists check if this is completed or wait for new digits. MIOSIP 8046 FIX: Fixed crash when recording video files with H263 codec. MIOSIP 2844 8165 FIX: Fixed crash caused by matching a <grammar> which is inside a <record>. MIOSIP 8093 FIX: Now clear out privacy header map properly. MIOSIP 2837 8138 FIX: Added transport type and message type (if INVITE) to log messages MIOSIP 2840 8139 FIX: Added log message show the SIP stack has constructed successfully and report which port it is listening on. MIOSIP 60117, 2842 8141 FIX: Added RVSIP_CALL_LEG_REASON_CALL_TERMINATED as retry reason if an outbound call fails. This avoids the situation where the failure was not detected correctly. MIOSIP 59988 8142 FIX: Now correctly reset last known nonce after each outbound call. Updates in v3.5.0 Component CR ID Task ID Description ENHANCEMENT: Packaging modifications 55595 7708 FIX: Fixed rare situation where setting a property could lead to a channel exception. 7897 ENHANCEMENT: Added new custom session variables so that the VoiceXML developer has access to the types of media codecs that are being used in the current call. These new codecs are named as follows; session.connection.protocol.sip.audiocodec session.connection.protocol.sip.videocodec Currently, the new variables may take one of the string values shown in this table: Call Type Allowed String Value audiocodec videocodec Audio Call g711u, g711a, g729 none" Video Call g711u, g711a, g729, amrnb-rfc3267, amrnbif2 h263-rfc2190, h263- rfc2429, h264 VoiceXML Media Server v3.6.1 4/12 GEN OMP 4044E

7727 ENHANCEMENT: Shortened label for MIO log callbacks from Status: LOG_MESSAGE_FROM_MIO to MIO_LOG: to allow for smaller system log file size. ENHANCEMENT: Packaging modifications FIX: Fixed Administration Guide known issue of incorrect description for NumChannelsMedia. ENHANCEMENT: Added support for H.264 video over IP 7725, 7803 ENHANCEMENT: Added support for MRCP v2 TTS (ie. MRCP v2 speechsynth resource only). This functionality does not affect MRCP v1 functionality. To use an MRCP v2 resource, the SIP URI of the resource server is used in the configuration XML file, as described in the Administration Guide. Four new main configuration file settings are introduced to control MRCP v2 behaviour; MRCPv2Enable (default is true), MRCPv2SIPPort (default is 5040), MRCPv2SIPTransport (default is tcp), and MRCPv2SIPLogDir (which enables logs from the SIP stack used by the MRCP v2 functionality, default is empty so no logs are produced).. 7974 FIX: Now correctly handle MRCP requests that get an unexpected complete status when we were expecting in-progress. MIOSIP 55861 7543 FIX: Fixed rare situation where use of SIP registration could have led to a crash. MIOSIP 7534 FIX: Fixed rare situation where loading configuration settings could have led to a crash. MIOSIP 2750 7516 FIX: Now correctly honour spaces and whitespace in RTSP messages. MIOSIP ENHANCEMENT: Added support for H.264 video over IP MIOSIP 8025 ENHANCEMENT: Added basic support for RFC 3325 by forwarding any SIP privacy headers received in a subsequent transfer call. This behaviour can be disabled by setting the new config setting miosip.dialog.forwardprivacyheaders to false (default is true). MIOSIP 7728, 7970 ENHANCEMENT: Added support for MRCP v2 ASR (ie. MRCP v2 speechrecog resource only). This functionality does not affect MRCP v1 functionality. To use an MRCP v2 resource, the SIP URI of the resource server is used in the configuration XML file, as described in the Administration Guide. Four new main configuration file settings are introduced to control MRCP v2 behaviour; miosip.media.stack.mrcpv2enable (default is true), miosip.media.stack.mrcpv2sipport (default is 5050), miosip.media.stack.mrcpv2siptransport (default is tcp), and miosip.media.stack.mrcpv2siplogdir (which enables logs from the SIP stack used by the MRCP v2 functionality, default is empty so no logs are produced). MIOSIP 7972 FIX: Now correctly handle MRCP requests that get an unexpected complete status when we were expecting in-progress. Known Issues Component Description VoiceXML Media Server v3.6.1 5/12 GEN OMP 4044E

VoiceXML Intepreter MIOSIP The MIOSIP module now handles fetching and caching of top-level grammars; previously the VoiceXML Interpreter did this. However, in the current version there is no means of configuring the fetch properties in MIOSIP; nor is there any way of getting information from MIOSIP on the number of items currently in the grammar cache, or the size of the cache. For this reason, the Status page of the VoiceXML Interpreter s web management console will always display 0 for both the current memory cache and disk cache sizes. If the platform is required to maintain a consistent high load of calls, it is advised to provision for an extra 10% of channels above the required number of concurrent calls. This is because each channel exhibits some clean-up latency after each call, to free its associated resources, during which it cannot accept a new call. VoiceXML Media Server v3.6.1 6/12 GEN OMP 4044E

Objectives VoiceXML Media Server v3.6.0 is a release built on RedHat version 5 whose primary function is to add license management mechanism and integrates Authorization Exchange feature from 3.5.3 version, make package adjustments, to fix a small number of bugs. New Features RedHat version 5 License management Authorization Exchange Third Party Components Updated o o Loquendo ASR v7.9.1/v7.9.10 and TTS v7.20.1 Nuance ASR v9.0.18 and TTS v5.0.5 o Acapela TTS v7.000 o Telisma TeliSpeech 3.1.GA VoiceXML Media Server v3.6.1 7/12 GEN OMP 4044E

Notes on Third Party Components VoiceXML Media Server integrates a number of third party components; in particular, TTS and ASR resources. This section describes some of the steps that must be taken to enable these components to operate correctly within the VoiceXML Media Server framework. In many cases, the information is specific to the current version of the third party component in question; for example, it may refer to a bug in the current version and describe a work-around for the bug. The information is liable to change as third party components are upgraded in future releases of the VoiceXML Media Server. The following engines are supported through MRCP. Vendor Component Version Notes 7.9.1 Speech Suite 7.0.10 (linux) ASR Loquendo 7.9.10 Speech Suite 7.0.18 (Windows) TTS Engine 7.20.1 Speech Suite 7.0.10 (Linux) and 7.0.18 (Windows) Nuance Recognizer 9.0.18 Nuance Speech Server 5.1.0 Vocalizer 5.0.5 Nuance Speech Server 5.1.0 Acapela TTS 7.0 Telisma TeliSpeech 3.1.GA In the following table, are listed the non-mrcp engines which are for most of them not more handled by vendors. Vendor Component Version Notes ScanSoft Speech Works Media Server for MRCP 3.1.9 If a large number of concurrent channels are active and using RealSpeak TTS via MRCP on the VoiceXML Media Server, there are some suggested changes to the configuration for the SWMS OSSServer. The configuration file for OSSServer, OSSserver.cfg, is found in the config subdirectory of the server directory in the SWMS installation directory. For example, the default on Windows is C:\Program Files\SpeechWorks\MediaServer\server\config. The following settings to change are commented out by default, their recommended values are as follows: Setting Name Recommended Value (if running 120 channels on VMS) server.realspeak4.audiothreadnumber 150 server.realspeak4.cache.enable 1 server.realspeak4.cache.initialnumber 120 server.realspeak4.cache.maxnumber 130 (should be set to the number of RealSpeak licenses.) server.realspeak4.cache.timeoutsec 600 VoiceXML Media Server v3.6.1 8/12 GEN OMP 4044E

OSR ASR 3.0.13 and 3.0.3 1. Running OSR 3.0.13 on RHEL There may be an issue with the hostname of the server (DHCP may contribute to this). When you attempt to run OSRServer you may get an error similar to the following: ** ERROR => SVC LOSS ** -2 SWI_ERROR recoverable error OSRServer::Initialize() Caught a CORBA exception while initializing ORB. Usually this indicates another instance of OSRServer is already running on this system. OSR Server initialization failed. This may be resolved by logging in as root and changing the hostname from localhost to the desired hostname using a command similar to the following: [root@localhost server]# hostname net01asr01 A useful point to note, but not required to resolve this issue, is the /etc/hosts file may be changed to reflect the desired hostname (and corresponding IP address). So your /etc/hosts file might read as follows: # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost localhost.localdomain 10.0.0.10 net01asr01 2. Running OSR 3.0.3 Warnings similar to the one below appear in the ScanSoft OSR 3.03 logs : ** WARNING ** -2 SWI_ERROR recoverable error SWIepDetectorCreateInternal increment SWIepCurrChanId = 1 RealSpeak TTS 4.0.x This warning is written to the log, for engineering purposes only. It indicates that the channel id of the end-pointer was incremented. There is no problem with the end-pointer when the message is written, and may be ignored. The following notes apply to non-mrcp implementations. 1. Running RealSpeak If you wish to use the ScanSoft RealSpeak 4 TTS engine with the, you must first install the RealSpeak 4 SDK on the machine where the will run. On Linux, you must also explicitly set the environment variable $SSFTTTSSDK to the RealSpeak install directory, e.g. /usr/local/scansoft/realspeak_4.0/. The RealSpeak installer does not do this automatically. This must be set in the Voxpilot user s environment. See the ScanSoft RealSpeak documentation for more details. 2. Dutch Voice For the RealSpeak Dutch voice (Claire), the documentation states that the language identifier should be Netherlands Dutch. However, in version 4.0.5, specifying this value will not work. Instead, the language should be set to Dutch in the XML configuration file. VoiceXML Media Server v3.6.1 9/12 GEN OMP 4044E

Acapela Acapela Telecom HQ (& Win32 HD) TTS + MRCP Server Addon v6.1 (Win32) v6.0 (RHEL) + v1.1 In order to use the xml:lang attribute in the SSML <speak> element to select different languages, you must pre-load the languages in the MRCP Server s mrcp.conf file. (For example, the default on Windows is: C:\Program Files\Acapela Group\Acapela MRCP Server Add-on for Acapela Telecom\mrcp.conf) For example, setting the following line in the mrcp.conf: Voice-name=Claire;Heather;Maria will allow you to switch between languages so the following SSML will work as expected: <?xml version="1.0" encoding="utf-8"?> <speak version="1.0" xml:lang="en-gb">the current time is 17,55.</speak> <speak version="1.0" xml:lang="fr-fr">il est 17:55.</speak> <speak version="1.0" xml:lang="es-es">el tiempo actual es 17:55.</speak> ELAN Sayso TTS 5.1 The following voice identifiers are currently supported for the ELAN Sayso engine: Voice Language Gender Voice Language Gender cathy08 French F sofia08 Italian F claire08s French F chiara08s Italian F robert08 French M massimo08 Italian M julie8k French F veronica08 Spanish F vicky08 UK English F maria08s Spanish F lucy08s UK English F rafael08 Spanish M gordon08 UK English M ana8k Spanish F graham08s UK English M emma8k Swedish F mary08 US English F femke8k Dutch F laura08s US English F sofie8k Belgian Dutch F william08 US English M radek08 Polish M aaron08s US English M magda08s Polish F heather8k US English F joana08 Brazilian Portuguese ryan8k US English M pedro08 Brazilian Portuguese F M dagmar08 German M nicolai08 Russian M lea08s German F merwan08 Arabic M thomas08 German M salma8k Arabic F sarah8k German F Cepstral Cepstral TTS + OpenMRCP v5 Under load conditions, the OpenMRCP server in combination with the TTS engine show a memory leak issue, which may necessitate restarting the server and the engine. VoiceXML Media Server v3.6.1 10/12 GEN OMP 4044E

Loquendo Speech Suite ASR and TTS v7 used on RHEL 4 and above When starting SNMP on Linux (from RHEL 4 on), which is necessary for Loquendo, you may need to change the configuration for the Security-Enhanced (SE) Linux.: To see the actual SE status, log in as root and use: sestatus grep -i mode The SE mode must be set to permissive so it allows SNMP to be started for Loquendo. To set it temporarily for a session use: setenforce permissive To set it permanently edit the file: /etc/sysconfig/selinux and set the value of SELINUX to permissive. See the Loquendo documentation for more details. Speech Suite ASR and TTS v7.0.6 (ASR v6.7.5) and v7.0.4 (TTS v6.5.3 (Window s)) The following notes apply to non-mrcp implementations. Since Loquendo does not use a client-server based architecture, these steps must be followed: 1. The Loquendo software, including all voice data, must be installed on the machine where the is running. 2. You must ensure that the value of DataPath in the HKEY_LOCAL_MACHINE\SOFTWARE\loquendo\LTTS\default.session key in the Windows registry is set to the base directory of the Loquendo installation, e.g. C:\Program Files\Loquendo\LTTS\. 3. For each language that you wish to use, you must copy the appropriate DLL (e.g. LoqEnglish6.5.dll) into the %VOXPILOT%\ssmlprocessor\bin ($VOXPILOT/ssmlprocessor/bin) directory. See the Loquendo documentation for more details. Nuance MRCP Server 8.5 The default installation does not work with the VoiceXML Media Server. There are several configuration changes that need to be made. 1. Complete default installation of Nuance MRCP Server. 2. Install any required Language Packs (See Nuance docs). 3. Add Nuance to mrcp.xml. For example: <mrcp-config> <resource lang="en-us" resourcetype="speechrecog" vendor="nuance" persist="true"> <server uri="rtsp://<nuance-server-ip>:554/recognizer"/> </resource> </mrcp-config> Note that 127.0.0.1 or localhost cannot be used for <nuance-server-ip>. If you have to install Nuance on the same machine as VoiceXML Media Server, please use the IP-address of the machine (and not the loopback IP address). 4. Add com.voxpilot.miosip.media.defaultasrengine=nuance to your vxmlinterpreter.conf. 5. Add audio.rtp.localipaddress=<nuance-server-ip> to the command line when you start the Nuance MRCP server (required for Nuance MRCP server SP8, fixed in Nuance SP9). You may want to place this in your watcher startup. If you leave out the setting, Nuance will never receive an RTP stream with the audio, and the software will throw no-inputs when you try and do speech recognition. VoiceXML Media Server v3.6.1 11/12 GEN OMP 4044E

6. We recommend that you add audio.rtp.playsilence=false to the Nuance MRCP server command line. This will eliminate a constant stream of silence RTP packets from the Nuance MRCP server, thereby saving bandwidth (recommend for Nuance SP8, fixed in Nuance SP9). After you have completed these steps, the MRCP server line in the Nuance watcher startup might read as follows: mrcp-server -cfg %MRCP%/mrcp-config -package %MRCP%/mrcp-nl-nl -package %MRCP%/mrcp-en-gb -config %MRCP%/nuance-resources.txt config.clapiconfigfile=%mrcp%/clapi_cfg.xml audio.rtp.playsilence=false audio.rtp.localipaddress=10.0.0.5 Your mrcp.xml might read: <mrcp-config> <resource lang="en-gb nl-nl" resourcetype="speechrecog" vendor="nuance" persist="true"> <server uri="rtsp://10.0.0.5:554/recognizer"/> </resource> </mrcp-config> Ecotonics Ventures Kapanga Softphone 1.00.217 6 To allow H264 video recording with the VoiceXML Media Server is necessary to do the following configuration change: - Set Video Rate Control (bps): 19800 VoiceXML Media Server v3.6.1 12/12 GEN OMP 4044E