Envox CT ADE 9.

2 Release Notes
02-November-06

System Requirements
Operating System Support CT ADE 9.2 supports Windows 2000, Windows XP, and Windows 2003. System Release Support CT ADE 9.2 supports Intel Dialogic* System Release 6.0. Host Media Processing (HMP) Software Support CT ADE 9.2 supports Intel NetStructure Host Media Processing Software 2.0 and 3.0. Supported ASR Engines Microsoft SAPI 5.0 or higher. Nuance Speech Recognition System 8.5 or higher. Nuance SpeechPearl* 8.0 or higher. Nuance OpenSpeech* Recognizer 3.0. Supported TTS Engines Microsoft SAPI 5.0 or higher. Nuance RealSpeak* Telecom 4.0 or higher. Note that ScanSoft has been renamed Nuance. The online documentation has been updated to reflect this change but may still refer to ScanSoft SpeechPearl and ScanSoft RealSpeak in some topics. For more information about the name change, see the Nuance web site: www.nuance.com.

What's New in Version 9.2?

CT ADE 9.2 software provides: Support for Intel NetStructure Digital Station Interface Boards through the R4SiTrunk technology: - DSI162HMP 2 wires per station port - DSI162LGNHMP 4 wires per station port - ADL and ADX samples for inbound and outbound calls to digital stations, as well as station capabilities control.

1 of 9

Support for Intel NetStructure SS7 boards with Integrated Services Digital Network User Part (ISUP): - SPCI2S - SPCI4 - SS7HDPD4TE - SS7HDCD16 - SS7HDCQ16t Envox CTI Link for Envox CT ADE lets you call Envox CT Connect 7.0 routines from your ADL applications: - Develop screen pop and intelligent call routing solutions. - Perform call control functions such as transfers and conferencing. Support for Intel NetStructure Host Media Processing 3.0: - Support continues for features previously supported with Intel NetStructure Host Media Processing Software 2.0. - HMP conferencing (CNF API) supported with Intel NetStructure Host Media Processing Software 3.0 and the new CT ADE technology, R4CnfConf. Improved ADX components integration with .NET: - Improved ADX components - Visual C# sample: Inbound - Visual C# sample: Outbound New ADX methods: PlayList PlayListClear PlayListModeOff PlayListModeOn

New MaxArgvLength entry in the ADL Settings file lets you control RLL argument length: - New C SDK functions let you access ADL Settings file values from your RLLs. - Updated MTNLIB file uses new entry. Help for ADL Legacy functions now included in the ADL Users Guide, ADL.chm.

CT ADE version 9.1 added: Support for Intel NetStructure Host Media Processing Software 2.0 features as follows: - Higher Channel Density Support - Interface Board Support - Echo Cancellation - SIP Re-INVITE Support for Thin Blades: - DNI300TEPHMP Single T-1/E-1 Digital Network Interface - DNI601TEPHMP Dual T-1/E-1 Digital Network Interface

DNI1200TEPHMP Quad T-1/E-1 Digital Network Interface

Support for additional Intel Dialogic boards: - DM/V600BTEP - DM/V1200BTEP - DM/V600BTEC - DM/V1200BTEC New R4DxFeatureList entry in the Profile for R4DxMedia resources. This entry provides information from the Intel API dx_getfeaturelist about the features of the corresponding media. For details, refer to the online CT ADE Documentation Library.

The Nuance Text-to-Speech (NuTTS) technology, which requires Nuance Vocalizer, is no longer supported with this release of CT ADE. Any references to NuTTS in the online documentation should be ignored.

Fixes in Version 9.2

SIP/H.323 registration fails. Issue: Attempts to run the HMP example could fail on the gc_ReqService call. Additionally, the help file example reported incorrect parameter order for REGID_R4GcReqService.

Solution: CT ADE version 9.2 fixes this bug and adds eight new RegIDs to let you control SIP Registrar and H.323 Gatekeeper registration information. See SIP/H.323 Registration in the the ADL Users Guide, ADL.chm, or the ADX Users Guide, ADX.chm, for details.

MediaPlayTone and PlayTone cut off continuous tones. Issue: Attempts to play a continuous tone with MediaPlayTone (ADL) or PlayTone (ADX) play the tone for .5 seconds before stopping, instead of playing until a stop tone is pressed.

Solution: CT ADE version 9.2 fixes this bug.

3 of 9

NetHub RLL Messages over 128 bytes generate errors. Issue: Calling the HubMsgSend function to send a message longer than 128 characters could generate intermittent errors: Instance Name too large (3528 characters), must be at most 1280 characters Solution: CT ADE version 9.2 includes a new entry in the ADL Settings file: [RLLParameters] MaxArgvLength This setting specifies the maximum length for RLL arguments. A new version of the MTNLIB file has been added that uses MaxArgvLength. Note: If you are upgrading RLLs from a previous version of CT ADE and want to use the new MTNLIB file, you will need to rebuild your RLLs. See MTNLIB in the ADL Users Guide, ADL.chm, for details.

ADX Voice Recognition functions may play .WAV files as .VOX files. Issue: Voice Recognition functions (such as PlayAndRecogDate) could attempt to play .WAV files in the .VOX format. Often when this happened, a click was audible at the start of playback as the .VOX header was interpreted as audio data.

Solution: CT ADE version 9.2 fixes this bug.

Notes, Known Bugs, and Workarounds

CT ADE Installation Issue: The CT ADE 9.2 installer installs the file, drive:\installationdirectory\MFC-setup.exe (where drive:\installation-directory is the location you specify for the software install). When the installer tries to run MFC-setup.exe, you may see a Windows Installer dialog displayed with the message Incorrect command line parameters. This indicates that you have an older version of Microsoft* Windows* Installer on your system.

Solution: This is an issue with the installer for CT ADE 9.1 and 9.2. If you see this message: 1) Click the OK button to proceed with the installation. CT ADE 9.2 will be installed, but the GUI tools (for example, the Profile Configuration Utility and ADL Studio) will not run correctly. 2) Install a newer version of Microsoft Windows Installer from: http://support.microsoft.com/?id=893803 3) When you have updated Microsoft Windows Installer, run the file MFC-setup.exe. Issue: When a user modifies a Minimal Installation the changes are not recorded

by the installer. If later the user tries to repair the installation the Minimal Installation will be restored and if the user removes the installation the components that were added to the minimal installation are not removed. Solution: If you select the Minimal installation, you should not manually modify the installation components. To select the installation you want, choose the Custom installation.

Board-Related Restrictions and Issues CPi/400 BRI Basic Rate ISDN Fax Board Not Supported CT ADE 9.2 does not support the Intel Dialogic CPi/400 BRI Basic Rate ISDN Fax Board. Intel has scheduled this board for retirement. For more information, refer to the Intel web site: http://www.intel.com/network/csp/products/4421web.htm. Fixed Routing Not Supported CT ADE 9.2 does not support fixed routing configurations (firmware prefix fn_) on System Release 6 for DMF240-type boards. However, it does support flexible routing configurations (firmware prefix fn3_). Other Board-Related Issues Issue: Attempting to enable or disable local audio routing on station with a DSI board produces unexpected results.

Solution: This issue has been assigned DUS-101726077 with Intel NetStructure Services Support. Digital station functionality varies greatly between systems. To fully understand your systems expected behavior, youll need to test calls to REGID_R4SiSetLocalAudioRoute and REGID_R4SiGetLocalAudioRoute on digital stations in your system. Issue: Multiple calls to a DSI station (with the R4SiTrunk RegIDs) return an error: Enum_SiErrorInvState, 17 Solution: The most likely cause of this error is that your station is still busy from a previous R4SiTrunk RegID call when a second RegID attempts to control the station. This issue has been assigned DUS-101668277 with Intel NetStructure Services Support. To work around this issue, insert sleeps between calls to the R4SiTrunk RegIDs. In the CT ADE lab, delays of 5ms prevented the error messages. Since the timing can vary greatly from system to system, you may need to use longer delays in your applications. Issue: Attempting to assign a custom tone for use as a stop tone with a DM3 board and System Release 5.1.1 causes an error and/or custom digits dont get detected.

5 of 9

Solution: With System Release 6.0, this feature is supported but with limitations. For details of these limitations, see the section on dx_addtone in the Voice API: Programmers Guide. For more information about this DM3 limitation with System Release 5.1.1, see the section on dx_addtone in the document, Compatibility Guide for the R4 API on DM3 4.3. Voice API Function and Parameter Restrictions at the following URL address: http://resource.intel.com/telecom/support/releases/winnt/SR511FP1/onldo c/htmlfiles/compgd/1237-11-12.html#P875_52073 It is possible to work around this limitation by using an RLL to monitor Dialogic events and dx_Stopch to stop the media operation. Issue: You cannot use CT ADE to set ec_setparm() parameters.

Solution: CTADE uses ec_setparm() to configure continuous signal processing (CSP) for voice-recognition applications, and those settings are not customermodifiable at this time. During the use of voice-recognition or automatic-speech-recognition (VR/ASR) applications in CTADE, ec_stream() is used to take advantage of echo cancellation and Continuous Signal Processing (CSP) features of the underlying hardware. CTADE enables and disables CSP at various points and during this process, CT ADE saves, updates and restores many parameters (including DXCH_SPEECHPLAYTHRESH) by using ec_setparm(). Because of this save-update-restore process in the execution of VR/ASR, coupled with the lack of any additional useful parameters available with ec_setparm(), access to ec_setparm() through CT ADE is not supported at this time.

Profile Configuration Utility Issue: Under some conditions, the Profile Configuration utility may not delete its temporary files.

Solution: In most cases, the Profile Configuration utility deletes its temporary files when it closes. There is no danger in leaving the files intact, but you can manually delete the following temporary files after saving your work and closing the Profile Configuration utility: ProfileScan.txt ProfileTemp.txt ProfileBackup.txt ProfileProgress.txt ProfileDeltaBackup.txt Issue: When opening the Profile, the Profile Configuration utility shows a blank window (the Profile window appears empty).

Solution: First, make sure you have stared the Profile Configuration utility from the Windows* Start menu. If you still have this problem, select "Recreate Profile..." from the File menu.

ADL/ADX Applications Issue: For applications that use OpenSpeech Recognizer: if a DTMF key is pressed during recognition and no DTMF stop digits are enabled in the recognition request, playback will be stopped prematurely. However, recognition will continue as normal. Sometimes the application is detecting a caller hang-up when the caller has not disconnected.

Issue:

Solution: Incorrectly detecting disconnect might be caused by a quick current drop in the line. Set the DXBD_MINLCOFF (545260558) parameter. DXBD_MINLCOFF (Minimum Loop Current Off) is the minimum time before loop current drop message is sent. Try setting it this to 1 second (100 x 10 ms = 1000 ms = 1 sec). For example: In ADL: TrunkSetInt(2300, 545260558, 100) In ADX: Call ADXVoice1.SetTrunkIntEx(2300, 100, 1, 545260558) You can find the value of DXBD_MINLCOFF in the DxxxLIB.h file: /* Min time of lc off before message*/ #define DXBD_MINLCOFF 0x040EL) ((PM_SHORT|PM_FW|PM_DXXX|PM_BD) |

The default value for this is 0, which will detect disconnect on any drop in the loop current. Increasing the value will prevent false disconnects caused by spurious loop current drops. Issue: When an application tries to assign a TTS personality to the current TTS resource on a system with multiple TTS technology types installed, an error occurs similar to: Topaz error:SapiTTS0 No personality 'SAPI5_Person0' found for this technology"

Solution: Each TTS technology type installed has a TTS resource associated with it. For example, if you are using a 4-port board on a system with SAPI4 and SAPI5 installed, there will be 4 SAPI TTS resources and 4 Sapi5TTS resources as follows: TTS 0 3 SapiTTS TTS 4 8 Sapi5TTS For this scenario, as defined in the TopazProfile, the first SAPI 5 personality is "SAPI5_Person0". If you issue the function 'TtsSetPersonality("SAPI5_Person0")', it will log the error "Topaz error:SapiTTS0 No personality 'SAPI5_Person0' found for this technology". To use your SAPI 5 personalities, you will need to do TTSUse(4) TTSUse(8).

7 of 9

Issue:

When making an outbound call the following error occurs: @X dx_initcallp(16[dxxxB1C2])=-1 ATDV_LASTERR(16)=65 Bad Tone Template ID

Solution: You can avoid this error by setting R4GcIgnoreAttachDelTones to True in the Profile. This is noted in the ADL and ADX Users Guide topics: GlobalCall: Profile Settings in the CT ADE Documentation Library. The R4GcIgnoreAttachDelTones ProfileID applies only to Technologies with R4GcAttachSupported set to True. Some technologies that invoke the API function gc_Attach, for instance ICAPI, destroy Call Progress Analysis tones that were preloaded to the voice channel. R4GcIgnoreAttachDelTones lets you determine whether or not CT ADE should restore these deleted tones. By default, this ProfileID is set to False, which means that CT ADE will try to restore the tones that have been deleted by gc_Attach. You should set it to True if you see an error from the API function dx_initcallp after gc_Attach in the log file. Issue: When calling TrunkMakeCall() in ADL, or MakeCall() in ADX, the method will return immediately without an event if R4MsTrunkWaitForConnect is not set to true for R4MsTrunk MSI station technologies.

Solution: To have the application wait for loop on or ring start before returning from the TrunkMakeCall() or MakeCall() methods, set the RegId R4MsTrunkWaitForConnect to true using the TrunkSetBool() method in ADL, or the SetBool() method in ADX. The default behavior for R4MsTrunk is to return immediately for an outbound call placed with TrunkMakeCall() or MakeCall(). R4MsTrunkWaitForConnect must be set to true to have the technology wait for loop on or ring start before returning. Issue: When running the simple inbound sample in ADL or ADX with HMP, calls are not answered properly. 1) In the Profile, the protocol entry needs to be set to H323 or SIP, depending on the protocol that is being used. If your application is either inbound only or outbound H323, you can leave it as IP. This is because the driver will automatically detect the protocol from the inbound call but it will assume H323 for outbound calls. For details on changing the profile entries please refer to the CT ADE help topic: Changing the Value of Multiple Profile IDs 2) After an incoming call is detected, but prior to answering the call, the application must set local and remote audio capabilities. If this step is missing, HMP will not start the RTP stream at all (or will do so incorrectly), and audio will not be heard by the caller. ADL Issue: Upgrading from 8.2 without adding memory may result in slower performance.

Solution: To use CT ADE with HMP, follow these steps:

Solution: With support for Unicode and strings longer than 127 characters, ADL version 9.0 and 9.1 requires more memory than previous versions. When

you upgrade from 8.2, you should re-evaluate your system and be sure it has enough memory to support your ADL applications. Remember to avoid relying on virtual memory instead of RAM, since swapping memory to a disk can also cause performance problems. Issue: Asynchronous mode fails for Conference Resources. Attempts at using the ConfWait function will return an error: ConfWait(): No asynchronous call has been made. WaitAsync() has failed.

Solution: At the time of writing, all current conferencing technologies add and remove parties instantly, so asynchronous mode is not necessary. Issue: Windows Explorer* cannot find ADL Studio. Double-clicking a .vs or .gvp file (or another file that should open in ADL Studio) in Explorer brings up the Open With dialog or the Program not Found dialog.

Solution: If the Open With dialog opens: Select ADL Studio Application from the Programs list. Check the box that says, "Always use the selected program to open this kind of file", then click OK. Explorer* associates the file type with ADL Studio. If the Program not Found dialog opens: Click Locate... In the Browse for Folder dialog, browse to the directory that contains the ADL Studio application, the ADL/Bin subdirectory of the CT ADE installation directory. If you followed the default installation, you should browse to this directory: C:\Program Files\Envox\CT ADE\ADL\Bin Click OK to close the Browse for Folder dialog, then click OK to close the Program not Found dialog. Issue: Memory leak and/or connection issues may appear when using database providers with the ADO RLL.

Solution: To overcome issues that appear with the OLE DB provider for Oracle* (the version that comes with Oracle 9i v9.2*), install version v9.2.0.2, which is downloadable from the Oracle Web site. Testing has shown connection issues with Unicode strings and the Microsoft* OLE DB provider for Oracle that comes with MDAC2.7. If possible, avoid using this DB provider. Issue: The hex addresses returned by dmpvx do not match the log file.

Solution: Add 3 to the dmpvx value to get the number that corresponds to the log file.

*Other names and brands may be claimed as the property of others.

9 of 9