Question

What fixes have been released for Blueworx Voice Response for AIX, Version 6.1?


Answer

The following is a complete listing of fix update files (PTFs) for Blueworx Voice Response for AIX, Version 6.1 and the fixes included within them, with the most recent updates at the top.


Fix updates can be found in the Blueworx Help Center Fix Center for the latest updates, or they can be downloaded from the Blueworx FTP site for older and larger updates. For more information go to How to obtain PTFs for Blueworx Voice Response for AIX.


Base changes:

Features:







Fix Level 6.1.0.535
Fix release date: 27 Apr 2022
Status: Current
A fix is available: Obtain the fix for 6.1.0.535


Contents


The following issue has been fixed:


Ticket#Update Details
293052Fixed a VOIPL3_SIP core dump occuring by adding a null check.





Fix Level 6.1.0.534
Fix release date: 08 Apr 2022
Status: Current
A fix is available: Obtain the fix for 6.1.0.534


Contents


The following issues have been fixed:


Ticket#Update Details
6802
Fixed a core dump in VOIPL3_SIP that can occur when using the SIP SUBSCRIBE messages.
7928
Fixed missing and duplicate DTMFs.
276011
Fixed error reporting crash in VOIPL4 and a race condition when handling BYE causing a crash in VOIPL3_SIP.
n/a
Fixed a rare memory leak in VOIPL3_SIP





Fix Level 6.1.0.533
Fix release date: 09 Apr 2021
Status: Current
A fix is available: Obtain the fix for 6.1.0.533


Contents


The following issues have been fixed:


Ticket#Update Details
5097Fixed a problem where long DTMFs are reported twice by BVR.
5833Fixed playing audio during a trombone call.
6757Fixed AIX crash due to invalid lock handling in the BVR DTNA. For further information, please refer to the News solution article - A BVR issue causes AIX to crash for certain AIX 7 levels .
n/aFixed a problem where the vm_integrity tool could not find compressed voice message files in BVR.







Fix Level 6.1.0.531
Fix release date: 20 Apr 2020
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.531


Contents


The following issues have been fixed:


Ticket#Update Description
1814Fixed a problem where BVR would not correctly recognise strings of DTMFs because of merging of several rapid RFC2833 DTMFs together, for example in an account number or pin. If the user entered 123456 BVR may recognise 13456 instead.







Fix Level 6.1.0.530

Fix release date:14 Oct 2019
Status: Current
A fix is available: Obtain the fix for 6.1.0.530



Contents


The following issues have been fixed:


Ticket#Update Description
1552Updated AMD to better detect beeps and voice and ignore small spikes/clicks of audio.
1672Fixed a rare race condition that could cause VOIPL3_SIP to core in certain circumstances.
1708Fixed AMD custom server errors that caused AMD to core dump.
1766Fixed an issue that prevented VXML fetchaudio from playing.
1777Fixed an issue with the SDIEXECexecuteable writing spurious error messages during BVR start up similar to the following:


entstat: 0909-003 Unable to connect to device ent0, errno = 19

 






Fix Level 6.1.0.529

Fix release date: 03 May 2019
Status: Current
A fix is available: Obtain the fix for 6.1.0.529



This Fix Update provides DB2 V11.1 support for BVR V6.1 for AIX. For details of this feature, please refer to the following Solutions article:
48000984791-blueworx-voice-response-v6-1-for-aix-support-for-db2-v11-1


Also the following issue has been fixed:


Ticket#Issue
Resolution
1669bvr_lsi prints error message if ent0 does not exist.Fixed the issue with the bvr_lsi executeable writing spurious warning messages during deviation of an AIX system ID.







Fix Level 6.1.0.528

Fix release date: 02 Apr 2019
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.528



Ticket#Issue
Resolution
1472The greetings and audio name associated with a subscriber are not deleted when the subscriber is removed from the system.Implemented code fix to correct this error.







Fix Level 6.1.0.525

Fix release date: 22 Mar 2018
Status: Current
A fix is available: Obtain the fix for 6.1.0.525



Ticket#Issue
Resolution
1402After adding Request in siphdrtags,cfg, enable ports caused the core dump.Fixed a core dump in VOIPL3_SIP that can occur when using the siphdrtags.cfg
1445The DTdatabase -r command fails on a BVR version 6.1 system that has been upgraded from DB2 version 9.5 to 10.1. The error message displayed is:
SQL5186N Configuring the DB2 environment failed because the specified DB2 environment variable, DB2 registry variable, or DB2 configuration parameter is discontinued. Variable or parameter name: "DB2_RR_TO_RS"
Removed the discontinued variable DB2_RR_TO_RS from the DTdatabase script. This variable is discontinued because Type-1 indexes are no longer supported.
1460A crash occurred that was caused by the DTNA.Fixed a rare crash that can occur as a trombone is being broken down by adding checks to make sure trombone hasn't been destroyed before attempting to destroy it.
N/AIncomplete SDP is being presented during on hold delayed offer.Fixed SIP handling of a delayed offer INVITE to renegotiate the streams whilst in an on hold (inactive). The full SDP is now correctly generated.







Fix Level 6.1.0.524

Fix release date: 10 Nov 2017
Status: Current
A fix is available: Obtain the fix for 6.1.0.524



Ticket#Issue
Resolution
N/ANo BRM license support.Add support for BRM licensing server.

For more details, refer to the Help Center article at the following URL:
48000984743-add-support-for-brm-licensing-server








Fix Level 6.1.0.523

Fix release date: 16 Jun 2017
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.523



Important: After installing this PTF, you will need a license key from your Blueworx sales representative or Blueworx support for BVR to continue taking calls. There is a grace period of 45 days in which to do this. Please see below for further details.


New feature contained in Fix Level 6.1.0.523:


In order for customers to ensure their compliance with license terms, Blueworx Voice Response has now been updated with a different License Use Management (LUM) system, a more modern approach to managing active channels.


The system will now require a software key to ensure that a Blueworx Voice Response system uses only licensed channels. The key is unique to each specific system and must be generated by a Blueworx support representative. This new level of management provides customers and Blueworx with coverage to ensure that all licenses have been purchased and that customer systems remain in compliance.


After installing BVR 7 for AIX 7.0.0.2, BVR for AIX 6.1.0.523 or BVR for Linux 7.2.2, you will need to follow the step-by-step instructions at:

48000984740-bvr-license-key-procedure


and contact our support team who will generate a unique software key for your system. A software key looks similar to this:


XE8RGT-LGFVK3-JDKY5B-7WCJN6-WRUXGP


Licenses can be used on any system; however, a License Key can only be used on the system they were generated for. If you wish to move your licenses to a different system you will need to contact Blueworx Support and provide the System Identifier of the new system and a new License KEY will be generated for that system.


New fixes contained in Fix Level 6.1.0.523:


Ticket#ProblemResolution
1186User receives an error that says: "Unable to read the list of data items Requested file not found." in the GUI. However, when the user calls into BVR, they are able to hear the voice segments.Increase limit on number of segments that can be viewed in the GUI.
N/AAMD ignores the initial voice_on_time worth of voice. This causes the AMD code to detect "human" with spoken audio longer than the human_time and shorter
than human_time + voice_on_time.
Use the current sample blocks length when moving from initial to detected voice states.
1244Double sending of RTP packets when performing a half tromboneAdd check to count number of outbound trombone legs present. If there is more than 0 then don't send on our own channel.







Fix Level 6.1.0.522

Fix release date: 20 Jan 2017
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.522



Ticket#ProblemResolution
N/AUnable to configure prompts to stop only when a complete match of an active grammar is detected in a VXML2 application.Implemented single DTMF key hotword barge-in functionality for VXML2 applications. With this, the prompt is only stopped when a complete match of the single DTMF key grammar is detected and any input that does not match is ignored.

For further details on this enhancement refer to the following article:
48000984717-single-dtmf-hotword-barge-in








Fix Level 6.1.0.521

Fix release date: 12 Dec 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.521



Ticket#ProblemResolution
1141Fax/modem too quiet for tone detection.Allow fax tones of a lower energy to be detected.
1148Further problems with the DTNA thread scheduling.Modify the DTNA threads so they have a more favourable priority and policy. This is to reduce the threads being scheduled late and poor/glitchy RTP heard.







Fix Level 6.1.0.519

Fix release date: 21 Nov 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.519



Ticket#ProblemResolution
1117No answer machine detection available for BVR.Add Answer Machine Detection custom server. Full instructions for use are supplied in the README file. The README file is in $CUR_DIR/ca/AMD_dir after the custom server has been imported.

The custom server can be imported from $VAE/sw/amd/AMD.imp







Fix Level 6.1.0.518

Fix release date: 21 Nov 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.518



Ticket#ProblemResolution
T1048An UPDATE request arrives during the INVITE sequence prevents call being answered.Fixed so the call does get answered. Also applies to any other incoming requests during the INVITE sequence.
T1061INVITEs with unsupported Content-Types are rejected when Content-Disposition handling is "optional".Incoming INVITEs with non-SDP "optional" content in the message body is now treated as a delayed offer.







Fix Level 6.1.0.517

Fix release date: 26 Sep 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.517



Ticket#ProblemResolution
N/ANo migration path to BVR 7Added a new script saveMigrationData to provide migation from BVR 6.1 to BVR 7.







Fix Level 6.1.0.516

Fix release date: 03 Jun 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.516



Ticket#ProblemResolution
1040Problems with the threads taking a long time to wakeup/become scheduled.Force DTNA processing threads to run at a higher priority.
1052CPU shows at 100% and is due to the machine being up for a long time and BVR being restarted. This will cause BVR to believe it's a 32 bit AIX (which it isn't). When the CPU counters are read, they are treated as 32 bit values and not 64 bit values.Change CPU detection code to correctly handle machines that have been up for a long time and BVR has been restarted recently.


Internal Defect fix

  • Update to GSKit 8.0.14.53 CC certified stream version







Fix Level 6.1.0.514

Fix release date: 19 Feb 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.514



APARDescription
IV76352Fixed a race condition between CHPs all attempting to access RD at the same time. This resulted in a flood of error text in DTstatus.out.
IV78103Fixed an issue that was introduced when the option was added to force sending of "Connect ACKnowledge" messages, where:
a) the force send connect acknowledge parameter didn't work and b) if Force send connect acknowledge was disabled, it would also disable sending of RESTART messages.
IV79999Fixed the DTNA adapter code to correctly honour the "Override DTNA RTP Transport IP Address" configuration value. This allows the DTNA to bind the RTP/RTCP sockets to a given interface.







Fix Level 6.1.0.512

Fix release date: 08 Dec 2015
Status: Superesed
A fix is available: Obtain the fix for 6.1.0.512



APARDescription
IV78783Precompiled Nuance grammars with the content-type "x-swi-grammar" are now forwarded to Nuance and no longer resolved by WVR. This ensures that Nuance can interpret the grammar as a binary grammar format, allowing it to be resolved correctly.







Fix Level 6.1.0.509 

Fix release date: 26 Jul 2015
Status: Current
A fix is available: Obtain the fix for 6.1.0.509



APARDescription
IV74831.A new configuration option "Version of cdr.log" has been added within the "General" configuration panel, and with the correct setting, will allow a new field "TFR" to be added to the end of each record written to the cdr.log. This field indicates if the call has terminated by way of a call transfer.

For further information on this feature, please refer to the following article:
48000984700-enhanced-support-for-new-voip-sip-call-transfer-version-of-cdr-log-record


Internal Defect fix

  • A new configuration option "Late Offer on Outbound Calls" has been added within the "Voip SIP Signalling" configuration panel. If set to yes then no SDP will be provided on the outgoing INVITE request associated with an outgoing call. If set to no (the default) then behaviour will be unchanged for outgoing calls and SDP will be attached to outgoing INVITE requests

    For further information on this feature, please refer to the following article:
    48000984795-support-for-late-offer-on-voip-sip-outbound-calls







Fix Level 6.1.0.507 

Fix release date: 26 Jun 2015
Status: Partly Superseded
A fix is available: Obtain the fix for 6.1.0.507



APARDescription
IV71716Fixed the state table dependency view to handle a large number of entries.
IV72814Fixed a problem with changing the technical difficulty message that caused trunks not to enable.
IV73686Fixed a problem with REGISTER that would cause registrations to fail if the registrar sends 100 responses.
IV74045Fixed the segment description entry text dialog to make sure that the description is no longer than 503 characters.








Fix Level 6.1.0.504 

Fix release date: 30 Apr 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.504



APARDescription
IV72487Removed all RC4 related ciphers from ciphers.ini due to "The RC4 Bar Mitzvah Attack" TLS/SSL client and server vulnerability. A backup copy of ciphers.ini was created before this removal, and is named ciphers.ini.CVE-2015-280.

For futher information, please refer to the following article:
48000984701-security-bulletin-vulnerability-in-rc4-stream-cipher-affects-blueworx-voice-response-for-aix-cve-2015-2808-







Fix Level 6.1.0.501 

Fix release date: 20 Mar 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.501



APARDescription
IV69846Update GSKit V8.0.14.48 CC certified stream version. This fixes various defects and security vulnerabilities.


Internal Defect fixes

  • Fixed the following error that can occur when running dtProblem:
    get_db2info[25]: DB2PRODDIR: 0403-040 Parameter null or not set.
  • Fixed a problem that was resetting the ownership and permissions on file /etc/rc.dirTalk everytime the user ran vae.setuser. This file should be owned by root so this fix allows you to do this without having to go back again to reset it again.
  • Fixed some problems associated with the use of MST (MRCP state tables) and MRCP custom server. Within an SSI setup, ownership of the MRCP custom server cannot be achieved by running certain commands such as dtjenable and vae.setuser on the SSI client. This fix provides detection of this and details on how to run these commands on the SSI server. This fix also removes a dependency for the Speech Client fileset to be installed before the ownership of the MRCP custom server could be updated by vae.setuser.







Fix Level 6.1.0.500 

Fix release date: 23 Dec 2014
Status: Preventative Maintenance (Fix Pack 10)
A fix is available: Obtain the fix for 6.1.0.500



APARDescription
IV67660The Fix Pack contains the following new enhancements:
  • DB2 10.1 Support
  • POWER8 hardware support
  • UM Enhancements

For more information on the Fix Pack 10 features, please refer to the following article:
48000984810-blueworx-voice-response-for-aix-v6-1-fix-pack-10


Internal Defect fix

  • The wvrtrunk command does not complete and hangs when attempting to enable trunks (using command "wvrtrunk -e -t all" for example) if there are any adapters containing trunks that are set as "defined".
    This will be corrected by ensuring any trunks that are set to "defined" are ignored when attempting to enable or disable trunks, as expected.







Fix Level 6.1.0.481 

Fix release date: 11 Dec 2014
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.481



APARDescription
IV67320Added support and the help for ISDN CONNECT ACKNOWLEDGE option.







Fix Level 6.1.0.478 

Fix release date: 27 Oct 2014
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.478



APARDescription
IV64764Fixed a crash with system configuration, which is most likely to occur on machines with a long host name and when system configuration is opened for browsing.
IV65729The vaeinit.pre script was incorrectly calling a non-existant executable called DT_generate_keyring. This was generating an error saying that DT_generate_keyring could not be found. The invocation of DT_generate_keyring has now been removed from vaeinit.pre
IV65221Allowed sending of DTMFs to temporarily stop a trombone. Without this fix any DTMFs sent during a trombone are ignored and never actually go out on the line.
IV66103Fixed a problem that would occur if a prompt directory contains more than 1020 entries. When playing the 1020th entry a tech_diff message would be played to the caller and the CHP process can core dump. Also when playing entries after the tech_diff message the system will report a prompt not found error.


Internal Defect fix

  • DTTA adapter dump files are incorrectly created with a length of 0 bytes. This has no customer implications; however the dump files are used as part of the support process.







Fix Level 6.1.0.476 

Fix release date:19 Aug 2014
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.476



APARDescription
IV62623Performance enhancements for iLBC.


Internal Defect fix

  • Improvement to dnd statistics monitoring - active chans now gives more accurate results.








Fix Level 6.1.0.475 

Fix release date:25 Jul 2014
Status: Preventative Maintenance (Fix Pack 9)
A fix is available: Obtain the fix for 6.1.0.475



APARDescription
IV61888The Fix Pack contains the following new enhancements:
  • Outbound arbitrary SIP headers
  • RTP for Avaya (SRTP key management)
  • VoIP/SIP audio compression codec support

For more information on the Fix Pack 9 features, please refer to the following article:
48000984721-blueworx-voice-response-for-aix-v6-1-fix-pack-9
IV60722Stopped spurious error 27405 from being raised without a matching 27404 error having been previously raised.
IV60432Fix a crash in the WVR dtdd device driver that can very rarely occur when reading the remaining audio data (via a remote record) after the call has dropped.
IV60175Shipped a fix that resolves a vulnerability problem, when using secure SIP, certain obscure SSL error conditions may result in a looping and high CPU usage.
Vulnerability Reference: CVE-2014-0963
IV56452Added new balanced channel allocation method. The option "Inbound Call Channel Allocation Method" can be found in the VoIP SIP Signalling section of the system configuration. The balanced SIP method will attempt to distribute all incoming calls evenly across the trunks. This will balance out resource usage across the system's CPU. By default WVR will fill up one trunk before allocating calls to channels to the next trunk as it has done previously.
IVI4128Fixed an AIX crash caused by incorrectly sending an external DTMF detection override to a DTTA trunk. External DTMF detection override is not supported on the DTTA adapter and is only supported on the DTNA.
IV53479Allow outbound RFC2833 DTMFs to correctly be sent during a trombone. As per audio the trombone will be temporarily stopped whilst the DTMFs are sent.


Internal Defect fixes

  • Previously running vae.setuser did not modify the owner for files in $DTJ_LOGS (/var/dirTalk/DTBE/dtj_logs). The owner of files in $DTJ_LOGS (/var/dirTalk/DTBE/dtj_logs) is now set to the owner specified on the vae.setuser command.
  • Fixed very bad DTNA compressed voice quality. This affects the recording of compressed voice rather than playing compressed voice segments.
  • GSKit 8.0.14.32 CC certified stream version security update
  • dtProblem now validates certificates in keyring.db and saves in security.txt inside dtProblem zip








Fix Level 6.1.0.450 

Fix release date: 26 Nov 2013
Status: Preventative Maintenance (Fix Pack 8)
A fix is available: Obtain the fix for 6.1.0.450



APARDescription
IV50080New feature contained in this PTF:
  • Secure versions of both the SIP and RTP protocol are now able to be configured on Blueworx Voice Response, adding encryption to protect the integrity and confidentiality of messages, and security for SIP communications on non-secure networks such as the internet.

For more information on the Fix Pack 8 features, please refer to the following article:
48000984720-blueworx-voice-response-for-aix-v6-1-fix-pack-8
IV42925Fixed a problem concerning outbound DTMFs. In some situations the current outbound DTMF can become stuck and never finish sending. This prevents the sending of further outbound DTMFs.
IV43396Fixed potential AIX crash when reading last RTP packet of a call once the call has actually been terminated. The vnaio driver would attempt to do a read on a blocking socket in an interrupt handler which is not allowed.
IV42401Corrected a potential NullPointerException when using MRCP recognition.


Internal Defect fix

  • Removed an incorrect VOIP SIP overload warning. This warning incorrectly reports that WVR has become overloaded. VOIP SIP incorrectly assumes a single threaded DTNA and also uses invalid DTNA statistics. The warning has been removed as the DTNA has specific warnings on a per thread basis which are much more accurate.

    The reported warnings are DTNA/SIP System Overload Warnings with an errno of 29805 with the message "Some incoming calls are not being answered to prevent the system from being overloaded."








Fix Level 6.1.0.425 

Fix release date: 7 May 2013
Status: Preventative Maintenance (Fix Pack 7)
A fix is available: Obtain the fix for 6.1.0.425



APARDescription
IV37769A new optional Genesys TelephonyService configuration parameter CalledNumberType for use with Genesys I-Server, controls the presentation of the called number. This allows the called number to be presented in the most appropriate way for TDM or SIP calls. It is now possible to specify that SIP Genesys CTI call transfers are re-routed through Blueworx Voice Response if for some reason a transfer operation using Genesys CTI cannot be completed satisfactorily.

For more information on the Fix Pack 7 features, please refer to the following article:
48000984722-blueworx-voice-response-for-aix-v6-1-fix-pack-7
IV36695Fixed VAGIO buffer leak caused by using the dtimport command.







Fix Level 6.1.0.405 

Fix release date: 11 Mar 2013
Status: Part superseded
A fix is available: Obtain the fix for 6.1.0.405



APARDescription
IV33060Fixed the dtProblem script to recognise and provide information about the DB2 V9.5 installation instead of reporting that DB2 is not installed on machine.
IV32761Moved some excess MRCP tracing to trace level 9. This reduces the extra unwanted trace at level 2 that was masking some other customer problems.
IV29267Set RFC2833 RTP DTMF marker bit in first packet of each DTMF to fix a problem where DTMFs are not detected on outbound SIP calls that use the DTNA.


Internal Defect fix

  • This PTF contains changes to the help text associated with the VOIP proxy mode parameter. These changes clarify the support and operation of the Automatic Service Lookup:DNSSRV method.









Fix Level 6.1.0.400 

Fix release date: 02 Nov 2012
Status: Preventative Maintenance (Fix Pack 6)
A fix is available: Obtain the fix for 6.1.0.400



APARDescription
IV28172New feature contained in this PTF:
  • Maximum channel capacity of a machine doubled.
    Using DTNA and VoIP/SIP, the number of Blueworx Voice Response LPARs supported per BladeCenter blade or pSeries has been increased from two to four. An appropriate allocation of CPU, memory, storage and Ethernet resources must be assigned to each Blueworx Voice Response LPAR. As a guideline, a system performance rPerf of 20 can support a 480-channel Blueworx Voice Response LPAR running speech-enabled VoiceXML applications.

For further information on the Fix Pack 6 features, please refer to the following article:
48000984723-blueworx-voice-response-for-aix-v6-1-fix-pack-6

PLEASE NOTE: This fix pack contains updates to the configurable $SYS_DIR/files in voip/: basicList.ini, master.ini and allowedHostList.ini. It will overwrite any changes made to those files upon installing this fileset.

PLEASE back up any changes you might have made to these files before install. They are used in the SIP REGISTER and allowed host list features, so this will only affect users who have activated either of those features.
IV27597Fixed an issue with a customer who needed to register to a proxy - added the Proxy= line to master.ini parsing, which allows a user to set a target to set a proxy address. This is an optional field that, if set, specifies an IP address to register to for the registrar. The Registrar will be used in all TO, FROM and CONTACT headers in the message but the message will be sent to the proxy address.
IV24344Fix playing audio and greeting files that have been recorded in a different format to the configured WVR format (ie. compressed/uncompressed). An attempt will be made to play the file in the configured WVR format. Should this fail the alternate format will be used.
IV20221Update the CNAME entry in RTCP packets to correctly follow the CNAME specification. The is formatted as aappcc@ip. Where aa is adapter number, pp is packet number, cc is channel number and ip is the ip address of the WVR machine.


Internal Defect fix

  • Fix a problem with CHP and playing segment, audio name and greeting files. If the audio files are stored in a compression format opposite to the system compression format the audio files will be ignored by WVR. With the fix any play and check storage will check both the system compression and then the opposite compression format.









Fix Level 6.1.0.375 

Fix release date: 27 Jun 2012
Status: Preventative Maintenance (Fix Pack 5)
A fix is available: Obtain the fix for 6.1.0.375



APARDescription
IV20358New features contained in this PTF:
  • Turn-based MRCP
  • Trusted Host List

For further information on the Fix Pack 5 features, please refer to the following article:
48000984724-blueworx-voice-response-for-aix-v6-1-fix-pack-5
IV20205Fixed a problem where WVR wouldn't restart after an AIX shutdown whilst it was running.
IV20226Fixed a problem with various voice database custom server subroutines that can occur when using a T1 uncompressed system:

CA_Get_Greeting() returns a different number of voice elements to the number requested.
CA_Create_Voice_msg() returns CA_INV_VOICE_ELEMENT errno.
IV20287Fixed a problem where vae.setuser incorrectly reverted any changes made by the dtjes script. This caused the system to revert back to using an earlier ECMAScript version.
IV12874Fixed a timing related defect that could result in a:
"com.ibm.telephony.directtalk.PlugInException: (102)
INVALID_STATE:MRCPCSLink request error"
being reported in the VRBE logs.
IV12929Fixed a potential leak of filedescriptors when using the VXML2 recordutterance property with a Nuance speech server.
IV12051Moved some CPU intensive tracing from trace level 8 to trace level 9 and recommend to use trace.option=8 for trace operation on production systems.


Internal Defect fixes

  • Fixed 3 problems in the SIP REGISTER mechanism:
    1. Fixed the CSEQ to increase by 1 for each new message rather than incorrectly remain at 1.
    2. Corrected the code to recognise an expiration length if received within the contact header rather than in an expires header.
    3. Added a RegisterAs option for those registrars that do not deal with hostnames, only IP addresses. By default, WVR will use its hostname contact address. RegisterAs is used to specify an IP address or hostname to override the default value on a per-host basis in the master.ini file. See the description in $SYS_DIR/voip/master.ini.orig for more details.
  • Fixed internal system monitor functionality.








Fix Level 6.1.0.350 

Fix release date: 13 Dec 2011
Status: Preventative Maintenance (Fix Pack 4
A fix is available: Obtain the fix for 6.1.0.350



APARDescription
IV09275New features contained in this PTF:
  • Remote DTMF detection and DTMF Grammar Compilation
  • Enable Endpointed Audio with Nuance NR9
  • "Core" Nuance Framework Dialog Modules Certification
  • DTNA Multiprocessor Support
  • Expanded <property> element support

For further information on the Fix Pack 4 features, please refer to the following article:
48000984725-blueworx-voice-response-for-aix-v6-1-fix-pack-4
IV08962Fixed VXML <menu> tag to ensure correct operation when used with a Nuance speech server. This will solve Nuance errors that state that there are multiple xml:lang attributes in the grammar sent when using the menu tag.
IV07915Fix a problem with loopback RTP packets from the vnaio to the vnaio. The receiving code can leak a data buffer. This eventually causes AIX to run out of buffers. The problem ONLY occurs when the vnaio sends to itself via a direct loopback. As SIP doesn't allow this is it requires and external endpoint to terminate two SIP calls. Once the two SIP calls have been created the RTP flow has to be negotiated away from the terminating endpoints so WVR streams to itself.
IV07916Update the DTNA/vnaio driver to handle badly constructed RFC2833 DTMF packets. The DTMFs are now placed at the same timestamp as the audio and maintain and set length and gap. This will stop DTMFs with the wrong timestamp and/or duration being placed "correctly" but then ignored by the DTNA.
IV03912Added support for Loquendo Speech Technology.

For more information refer to the Zendesk article at the following URL:
/hc/en-us/articles/216679187
IV02868Added support for tromboning between:
1) RFC2833 to SIP INFO DTMF
2) SIP INFO DTMF to RFC2833
3) SIP INFO DTMF tp SIP INFO DTMF
4) RFC2833 to RFC2833 (support already present)

Add support for two SIP INFO DTMF content types:
1) dtmf-relay
2) vnd.nortelnetworks.digits

Add socket state information in DTNA to make the socket handling more robust. This will stop situations where sockets can not be bound but are then used potentially resulting in a system crash.

Add support for full software TDM in the DTNA. The original support only allowed either normal or full trombone operation on the DTNA. The custom server CA_TDM_Connect subroutine now allows all TDM combinations to be altered on DTNA (as per DTXA and DTTA). This change allows recording of other channels, DSP (WVR) and Line (customer).
IV03003Fixed problems with missing DTMFs when using RFC2833 on the DTNA. This can occur when the far end leaves gaps in the RTP stream between DTMF end and audio start.
IV03035Prevents AIX crashes with DTNA when ports cannot be bound and allows port ranges to be configured above 32000.


Internal Defect fixes

  • Fixed to ensure that all attributes required by a Nuance server are included in a TTS <speak> request
  • Fixed the processing of a 404 MRCP return code returned in a MRCP COMPLETE status message in response to a Speak request sent to a speech server.
  • Fixed the calculation of a MRCP header field sent when issuing a speak command to the MRCP speech server.
  • Fixed processing of MRCP header fields to allow processing of session ID returned by Loquendo.
  • Fixed processing of session attributes returned from speech server so that MST can process unsupported attributes without returning an error. .
  • Added an output log to MST_Import to ensure problems can be debugged.
  • Added a new DTMF algorithm variant 2 that will only report DTMFs that are on for at least 60ms (Note, this is a Field access level system parameter). This should only be used if double detections are occuring for DTMFs and the audio stream contains a smaller clipped DTMF before the real DTMF. This can occur when TDM voice is converted to VoIP and then back to TDM before entering the DTXA/DTTA. The gateway doing the TDM to VoIP conversion can ended up leaving a little bit of the original tone before declaring an RFC2833 DTMF. When the stream is converted back into TDM the RFC2833 generates a new tone sometime after the original tone. Thus two DTMFs appear in the audio stream.








Fix Level 6.1.0.300 

Fix release date: 6th July 2011
Status: Preventative Maintenance (Fix Pack 3)
A fix is available: Obtain the fix for 6.1.0.300



APARDescription
IV00013New features contained in this PTF:
  • Extended Brooktrout TR1034 Fax Card Support - Blueworx Voice Response now supports the 4-channel and 16-channel versions of these cards as well as the 30-channel version.
  • State Table MRCP TTS Support - State Table applications can now use an MRCP Voice Server for Text To Speech.
  • SIP Stack Auto Restart - in the event of the SIP stack crashing, Blueworx Voice Response will now automatically restart it in order to bring the system back to a working state.
  • ECMAScript 1.7 Support - VoiceXML and CCXML applications can now be configured to use ECMAScript 1.7 for their scripts. By default, the existing ECMAScript 1.3 implementation will be used.
  • Bargein type=dtmf_only - Provided a method for VoiceXML prompts in a speech-enabled application to restrict the method of bargein to be DTMF only, rather than both Speech and DTMF.
  • Multiple Grammar Result Contexts Support - Blueworx Voice Response now supports the use of Speech Grammars that return multiple interpretations of the recognition with contextual information in the form of named slot arrays for speech recognition in VoiceXML applications.
  • CCXML Latest Version - CCXML has been updated to conform to the Proposed Recommendation of the CCXML specification, located at
    http://www.w3.org/TR/2011/PR-ccxml-20110510/

When starting Blueworx Voice Response after applying this PTF, you will be prompted to accept a new licence agreement.

For further information on the Fix Pack 3 features, please refer to the following articleL:
48000984745-blueworx-voice-response-v6-1-for-aix-fix-pack-3
IZ99174Add auto restarting of DBHEALTH should the code stop running. This will stop the database being stuck in the not running/down state.
IZ99175Fixed an issue which would result in a 0 length duration being reported for recordings that ran until the maximum duration edge was returned.
IZ99184This fix overcomes a possible yellow alarm 17035 error (Network does not respond) at first startup of WVR when configured as T1 CAS e.g. T1 FXS/LS. Previously with trunks set to auto-enable at startup (i.e. Enabled and InService), the error could occasionally occur when first starting up.


Internal Defect fix

  • Fixed a problem to ensure that the VXML2 termchar shadow variable is set after a <record> is terminated by a DTMF key.








Fix Level 6.1.0.250 

Fix release date: 30th November 2010
Status: Preventative Maintenance (Fix Pack 2)
A fix is available: Obtain the fix for 6.1.0.250



APARDescription
IZ86663New features contained in this PTF:
  • Enhanced VoiceXML and CCXML application support for call information - Provide protocol specific tagging information in VXML and CCXML.
  • VRBE Expire Resource Tool - allows a system administrator to manually expire a resource in the VXML, CCXML or Audio caches.
  • Support for SIP Registration - provides support for the SIP registration method described in RFC 3261.
  • New VoIP Signalling - Inbound Call Channel Allocation Method. A new Inbound Call Channel allocation option called "Allocate calls for D2IS" has been added to system configuration to control the channel used for DTNA based calls. This option is for use when using the Genesys-supplied D2IS custom server in a behind-the-switch Genesys Framework implementation.
  • Trombone Custom Server Enhancement - allow called party to pass back a termination value to calling party.
  • VRBE problem determination utility - enables a system administrator to collect a dtbeProblem output (or run any other command) automatically when an error or other message is reported in VRBE.

For further information on the Fix Pack 2 features, please refer to the following article:
48000984726-blueworx-voice-response-for-aix-v6-1-fix-pack-2
IZ85227Fixed a device driver problem involving freeing invalid memory when unconfiguring devices. On AIX6 this generates GEN_XMDBG errors in errpt.
IZ84381Fixed a problem with message deletion. If the receiving mailbox deletes the message without listening to it the sender is getting an acknowledgment without the actual voice message. When the sender listens to the acknowledgement an error is generated.
IZ84382Fixed a potential AIX crash when using juke_box custom server. The crash occurs when music is being streamed to an uninitialised music channel
IZ77937Fixed a system crash that can occur during the main WVR device driver processing of an adapter pack DMA whilst the adapter is crashing. This is a very small timing window as the adapter has to be crashing during DMA processing. Any adapter crash can cause this system crash.
IZ80210Fixed a DTNA problem whereby it is possible for two packets to arrive on each socket and deadlock the system as the packets are sent of the opposite/partner sockets. The fix is to unlock channel sockets before sending out RTP packet, to allow for the race condition with two tromboned channels attempting to send packets to, using each others socket.
IZ81672Fixed a "Requested file not found" error that can occur when creating a new language from the WVR GUI.
IZ74142Fixed a problem of the lack of backwards compatibility and codec changes between different versions of WVR and UM by creating new interface library.


Internal Defect fixes

  • Usability updates to the DTcheck_bin utility.
  • Report back correct error code when attempting to log into the same mailbox simultaneously.
  • Fix auto restart scripts for the DTNA adapter.
  • Fixed incorrect message length reported when pausing the message during recording. The length used to just contain the last segment of the message rather than all segments.
  • Fixed a potential problem with vae.setuser when changing the default WVR user from dtuser to another AIX user id. Before the fix, there was a chance that any new executables shipped as a result of fixes etc would not have their file ownership changed to the new user.
  • Fixed a problem with restarting WVR devices if WVR was still running when the machine was rebooted. If the dtline devices end up in the defined state then WVR doesn't recover the devices correctly. This results in script errors appearing in DTstatus.out and trunks failing to appear in WVR.
  • Fixed a machine crash due to a race condition where the DTNA sends trunk information to the WVR device driver during a shutdown. The WVR device driver attempts to access the trunk information from the DTNA via an internal structure which has since been freed.
  • Outbound RFC2833 packets fixed to use the correct payload type.
  • Added better filename reporting to vm_integrity and DTverifydb









Fix Level 6.1.0.220 

Fix release date: 1st April 2010
Status: Preventative Maintenance (Fix Pack 1)
A fix is available: Obtain the fix for 6.1.0.220



APARDescription
IZ71035Features included in this PTF are:
  1. Changes needed in the base to provide ISDN UUI protocol specific tagging information in VXML and CCXML applications.
  2. Changes needed in the base for significant usability improvements to WVR Java application logging.

For further information on the Fix Pack 1 features, please refer to the following article:
48000984727-blueworx-voice-response-for-aix-v6-1-fix-pack-1
IZ70203When a pack was in equipped or defined state the SNMP vPackType request returned the pack type (e.g. "T Pack T1") while the documentation stated that when the pack was in either of these states a vPackType request should return "Unassigned". This fix brings the vPackType request inline with the documentation.
IZ70202This fix enhances sample state table application IBMTromboneCall to enable the calling application (e.g. IBMTromboneXmp) to distinguish between original caller hangup both before and after a successful trombone transfer. Previously the same error was returned for both cases and this prevented accurate statistics collection of successful verses failed trombone transfers.
IZ61950Modified the DTNA code to prevent an error_id 29800 from occurring if the "Inbound DTMF Method Override" system parameter is set to "DTMF via SIP info".


Internal Defect fixes

  • Fixed the support of CDR recording of VXML applications.
  • Fix a codec problem with the library path sometimes not being initialised correctly. When this occurs audio files will not be played.
  • Fixed an internal WVR V6.1 build issue.
  • Correct release level checked by DB2_CHECK script and DT6_DB2_SPEC



3270 Fixes






Fix Level 6.1.0.205 

Fix release date: 9th October 2009
Status: Current
A fix is available: Obtain the fix for 6.1.0.205



APARDescription
IZ62514This PTF fixes a problem with 3270 peeker sessions using up all the buffers up due to a spining loop.

This can occur when the 3270 peeker sessions are being used on a remote X server, for example, Exceed. If the remote X server connection drops requests are made for window id 0 which causes the peeker code to loop.




ISDN Fixes






Fix Level 6.1.0.532
Fix release date: 11 Dec 2020
Status: Current (ISDN.com)
A fix is available: Obtain the fix for 6.1.0.532


Ticket #Description
1020Fixed an occasional glare when making outbound calls on ISDN T1 system. 




 


Fix Level 6.1.0.508 

Fix release date: 26 Jul 2015
Status: Superseded (ISDN.com)
A fix is available: Obtain the fix for 6.1.0.508



APARDescription
IV73868Fixed issue with the ISDN single step call transfer application (SSTransfer) when FACILITY messages were too large for the buffer, causing the data passed to the custom server to be truncated, resulting in mandatory data required for transfer being missing.


 




Fix Level 6.1.0.481 

Fix release date: 11 Dec 2014
Status: Current (All ISDN file sets)
A fix is available: Obtain the fix for 6.1.0.481



APARDescription
IV65902
IV67321
IV67322
IV67323
IV67324
Added the option to force ISDN to send a CONNECT ACKNOWLEDGE when the variant would not normally support it (e.g. DMS250).This can be configured in Configuration>System Configuration>Change>ISDN Signalling>Force CONNECT ACKNOWLEDGE.
The default setting is false so this will not affect existing users unless they change the option.
IV09079Fix prevents ISDN_MONITOR from core dumping if /tmp is cleared.
IZ80291This fix overcomes a possible 29213 error (ISDN channel state machine invalid primitive) when an outbound/inbound call clash occurs (glare) on a QSIG ISDN channel. Previously after such a clash the error could occur during the first inbound call received on the channel
IZ60576This fix helps overcome repetitive 1201 (Line problem/Glare occurred > 20 times) errors seen occasionally during QSIG ISDN transfer calls on certain Hicom switches.

Previously when this error occurred the 1201 error would repeat on each and every follow-on outbound call until the failing channel was reset at the switch end. The fix overcomes the problem by setting the channel disabled to prevent further call attempts.
IZ70398This fix overcomes possible ISDN errors 29109 (ISDN ES buffer pool low) and 29615 (ISDN Layer 1 discarding incoming messages) seen with 2BCT transfer calls on T1 ISDN DMS100 National. Previously the loss of environment services buffers associated with these ISDN errors could result in failure to handle any new calls (inbound or outbound) until WVR was restarted.




Brooktrout Fax Fixes


 




Fix Level 6.1.0.250 

Fix release date: 30th November 2010
Status: Current
A fix is available: Obtain the fix for Brooktrout Fax 6.1.0.250



APARDescription
IZ86667Improved initial fax channel allocation during Brooktrout fax startup.



SP Fixes



There no SP Fix Updates on WVR for AIX, V6.1.



GEOTEL Fixes


 




Fix Level 6.1.0.383 

Fix release date: 14 Sep 2012
Status: Current
A fix is available: Obtain the fix for 6.1.0.383



APARDescription
IV27691Fixed a GeoTel custom server problem concerning trace. This occurs if the custom server fails to trace after reading a message from the message queue. The custom server will incorrectly report that the message queue has failed.
IV07741Fixed a problem converting some hostnames and service names during GeoTel custom server startup. This results in the custom server refusing to start. The failure cases for hostname are dotted address, any, localhost and the failure for service name is blank.

Hostname failures:
  • Hostname set to dotted address, eg 192.168.0.1
  • Hostname set to "any"
  • Hostname set to "localhost"

Service name failures
  • Service name is blank

Backup any configuration in $CUR_DIR/ca/GeoTel_dir before importing the GeoTel custom server as this will reset the configuration.




ADSI Fixes


There no ADSI Fix Updates on WVR for AIX, V6.1.



TDD Fixes


There no TDD Fix Updates on WVR for AIX, V6.1.


SS7_D7 Fixes


 



Fix Level 6.1.0.379 

Fix release date: 02 Nov 2012
Status: Current
A fix is available: Obtain the fix for 6.1.0.379



APARDescription
IV26316This fix overcomes a possible SS7 30013 error (Invalid Data Item / Attempt to access Message Register when not loaded) with an outbound call attempt when 16 Channel Groups are configured for use (e.g. 1 Channel Group for each of 16 T1/E1 SS7 voice trunks).


 




Fix Level 6.1.0.250 

Fix release date: 30th November 2010
Status: Preventative Maintenance
A fix is available: Obtain the fix for SS7 6.1.0.250



APARDescription
IZ86668Improve error condition handling.


 




Fix Level 6.1.0.206 

Fix release date: 28th October 2009
Status: Preventative Maintenance
A fix is available: Obtain the fix for 6.1.0.206



APARDescription
IZ63565This fix provides support for AIX 64-bit kernel working of the device driver (artic8260) for the SS7 signalling card (SS8/NewNet quad T1/E1 HAX50PCGEN).

The fix includes the D7 1.3.1.19 update package for the D7 1.3.1.0 base install package. Also corrected in the update is a possible system crash associated with the D7 etmod device driver.



SpeechClient Fixes


 





Fix Level 6.1.0.522

Fix release date: 20 Jan 2017
Status: Current
A fix is available: Obtain the fix for 6.1.0.522



Ticket#ProblemResolution
N/AUnable to configure prompts to stop only when a complete match of an active grammar is detected in a VXML2 application.Implemented single DTMF key hotword barge-in functionality for VXML2 applications. With this, the prompt is only stopped when a complete match of the single DTMF key grammar is detected and any input that does not match is ignored.

For further details on this enhancement, please refer to the following article:
48000984717-single-dtmf-hotword-barge-in

 





Fix Level 6.1.0.511 

Fix release date: 01 Dec 2015
Status: Current
A fix is available: Obtain the fix for 6.1.0.511



APARDescription
IV76880Precompiled Nuance grammars with the content-type "x-swi-grammar" are now forwarded to Nuance and no longer resolved by WVR. This ensures that Nuance can interpret the grammar as a binary grammar format, allowing it to be resolved correctly.


 




Fix Level 6.1.0.502 

Fix release date: 20 Mar 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.502



APARDescription
IV69939This PTF fixes some problems associated with the use of MST (MRCP state tables) and MRCP custom server. Within an SSI setup, ownership of the MRCP custom server cannot be achieved by running certain commands such as dtjenable and vae.setuser on the SSI client. This fix provides detection of this and details on how to run these commands on the SSI server.


 




Fix Level 6.1.0.454 

Fix release date: 21 Jan 2014
Status: Preventative Maintenance
A fix is available: Obtain the fix for 6.1.0.454



APARDescription
IV53415Fixed a problem where during MRCP TTS and Reco there were repeated DNS lookups of local machine IP address.
IV49665Fixed a problem in the MRCP plugin where DTMF grammars fail to compile if using Nuance whilst wvr.dtmf.useexternaldetection is set to true.
This caused an MRCP 407 Complete error to appear in the trace.
IV41358Fixed a potential NullPointerException when using MRCP recognition.


 




Fix Level 6.1.0.425 

Fix release date: 17 May 2013
Status: Preventative Maintenance (Fix Pack 7)
A fix is available: Obtain the fix for SpeechClient 6.1.0.425



APARDescription
IV37773New feature contained in this PTF:

Support for back-up speech recognition and text-to-speech servers has been added so that MRCP speech recognition and text-to-speech can continue in the event of a server failure.

For more information on the Fix Pack 7 features, please refer to the following article:
48000984722-blueworx-voice-response-for-aix-v6-1-fix-pack-7
IV30891Fixed a problem where an interrupted TTS prompt would cause the next TTS message not to play, instead playing silence to the caller.


Internal Defect fix

  • Moved some excess MRCP tracing to trace level 9. This reduces the extra unwanted trace at level 2 that was masking some other customer problems.


 




Fix Level 6.1.0.400 

Fix release date: 02 Nov 2012
Status: Preventative Maintenance (Fix Pack 6)
A fix is available: Obtain the fix for SpeechClient 6.1.0.400



APARDescription
IV28170New features contained in this PTF:
  • DTMF Hotword Support
    Hotword DTMF barge-in is now supported with remote DTMF grammar detection.
  • Reporting of raw NLSML result within a VXML application
    Blueworx Voice Response now supports the use of multiple recognition contexts for speech recognition in VoiceXML applications, including the raw NLSML that was returned from the speech server.

For further information on the Fix Pack 6 features, please refer to the following article:
48000984723-blueworx-voice-response-for-aix-v6-1-fix-pack-6


 




Fix Level 6.1.0.375 

Fix release date: 27 Jun 2012
Status: Preventative Maintenance (Fix Pack 5)
A fix is available: Obtain the fix for SpeechClient 6.1.0.375



APARDescription
IV20362New features contained in this PTF:
  • Turn-based MRCP

For further information on the Fix Pack 5 features, please refer to the following article:
48000984724-blueworx-voice-response-for-aix-v6-1-fix-pack-5
IV12046Fixed a timing related defect that could result in a:
"com.ibm.telephony.directtalk.PlugInException: (102)
INVALID_STATE:MRCPCSLink request error"
being reported in the VRBE logs.
IV12390Fixed a potential leak of filedescriptors when using the VXML2 recordutterance property with a Nuance speech server.
IV12050Moved some CPU intensive tracing from trace level 8 to trace level 9 and recommend to use trace.option=8 for trace operation on production systems


Internal Defect fixes

  • Fixed internal error that was caused when MRCP servers do not respond within timeout window. This error would cause an OutOfMemory Exception in the VRBE error logs.
  • Fixed internal system monitor functionality.


 




Fix Level 6.1.0.350 

Fix release date: 13 Dec 2011
Status: Preventative Maintenance (Fix Pack 4)
A fix is available: Obtain the fix for SpeechClient 6.1.0.350



APARDescription
IV09337New features contained in this PTF:
  • Remote DTMF detection and DTMF Grammar Compilation
  • Enable Endpointed Audio with Nuance NR9
  • "Core" Nuance Framework Dialog Modules Certification
  • Expanded <property> element support

For further information on the Fix Pack 4 features, please refer to the following article:
48000984725-blueworx-voice-response-for-aix-v6-1-fix-pack-4
IV08942Fixed VXML <menu> tag to ensure correct operation when used with a Nuance speech server. This will solve Nuance errors that state that there are multiple xml:lang attributes in the grammar sent when using the menu tag.
IV09073Fixed to ensure that all attributes required by a Nuance server are included in a TTS <speak> request.
IV03717Removed reliance on mrcp_tech parameter when determining what MRCP speech vendor is being used for speech recognition. WVR will autodetect the speech vendor.


Internal Defect fix

  • Fixed interpretation of grammarID that could cause speech recognition results to be ignored for some speech vendors.


 




Fix Level 6.1.0.300 

Fix release date: 6th July 2011
Status: Preventative Maintenance (Fix Pack 3)
A fix is available: Obtain the fix for SpeechClient 6.1.0.300



APARDescription
IV00138State Table MRCP TTS Support - State Table applications can now use an MRCP Voice Server for Text To Speech.
IZ95453Fixed an issue where VXML2 hotword recognition would not work if a Nuance speech server was used. The RECOGNIZE request would fail with a 403 completion code indicating an unsupported parameter.
IZ95454Increased amount of voice data buffered by the device driver to allow for CPU glitches to be handled better by MRCP. With a smaller buffer a CPU glitch can cause the reco to stop.


Internal Defect fixes

  • Fixed an issue where the following error would appear under heavy call load:
    Unhandled exception occurred during MRCP message receive. Details: java.lang.NullPointerException at com.ibm.telephony.directtalk.mrcp.ReceiverThread.run (ReceiverThread.java:197)
  • Ensure logging of Speech Resource related connection problems at startup.
  • Fixed an issue with MRCP not honouring the negotiated RTSP port on SETUP messages, which would instead stream to the default port.


 




Fix Level 6.1.0.250 

Fix release date: 30th November 2010
Status: Preventative Maintenance (Fix Pack 2)
A fix is available: Obtain the fix for SpeechClient 6.1.0.250



APARDescription
IZ86716There is a minor race condition in the MRCP custom server that can occur during stopping TTS. If the MRCP custom server is stopping due to a DTMF then it carries on processing incoming voice from the TTS engine but doesn't stream it to the line. If during this stop a Speak complete comes back from the TTS engine the custom server is told to immediately stop. The custom server ignores this due to stopping because of the DTMF. Unfortunately this causes the TTS to never actually stop. A problem occurs when the next TTS is started as this fails to be setup correctly complaining that the custom server is already streaming.
IZ83657Fixed a problem with the MRCP custom server hanging at startup, potentially with 100% CPU.
IZ84763Fixed an issue that can cause a MRCP PluginException (completion-cause 006) if a caller hung up just after a recognition attempt was started.
IZ80453Corrected the handling of RTSP 454 "Session not found" responses when attempting recognition or TTS. Prior to the fix, the application would terminate if such a response was received. After installing the fix, the code will correctly try to re-establish a session to the speech server.
IZ80463Corrected a problem whereby a no-input event will be reported to the a VXML application as a no-match. This problem only occurs when using Nuance as the speech server.
IZ80629The code fixes the confidence-threshold, sensitivity threshold and speedVSaccuracy setting in WVR. With the fix, if you define a decimal fraction for these 3 properties in a VoiceXML app, WVR will convert it to integer value more accurately.
IZ70399Corrected a potential problem when setting up a connection to a MRCP server if the response message uses uppercase characters for the audio format section.
IZ65904Fix a potential timing window in the MRCP distributor thread. When the problem occurs the MRCP custom server will stop delivering packets to WVS. This causes the 006 error return from WVS (no audio streamed). The sleep time in the MRCP can be on the order of hours, so all reco will fail for every channel during this time. The timing window can only occur if the act of reading the time between two neighbouring lines of code is greater than 100ms. Normally this would happen if the CPU were heavy loaded and the custom server swapped out for some reason.
IZ65921Fix a timing window when stopping reco/tts whilst the system is very busy. If the state table times out whilst waiting for the stop and closes the MRCP custom server link then when the custom server finally responds it results in an exception and the custom server stopping
IZ64798Improved the MRCP plugin import code so that the custom server will start regardless of the ulimit value set on the machine.
IZ65931Correct a problem that can cause the system to report an "MRCP Plugin not initialised" message in the wvrtrace files.
IZ61951Fixed a potential BufferUnderflowException in the MRCP plugin that could occur when using the recordutterance VXML property.


Internal Defect fix

  • Removed a spurious check in the MRCP plugin that generated the following error if a speech server other than WVS was used.

    (1007560) WVR can only be used with Blueworx Voice Server.

    There is no limitation on the MRCP speech servers that can be used with WVR 6.1.



VRBE_XML Fixes


 





Fix Level 6.1.0.527

Fix release date:04 Dec 2018
Status: Current
A fix is available: Obtain the fix for 6.1.0.527



Ticket#Update Details
n/aAdded support for IBM Voice Gateway to BVR. For more details, refer to the Blueworx Help Center article:
Integration with IBM Watson through IBM Voice Gateway
1555Fixed memory leak and added some missing socket closes for TCP and TLS SIP connections.
n/aExtended support for incoming SIP headers using the siphdrtags.cfg file.

Previously header entries in siphdrtags.cfg controlled the SIP headers that were provided as tags in SV542 when an incoming INVITE message was received.


This fix update extends this support so that header entries in siphdrtags.cfg can now be used to provide SIP headers as tagss in SV543 when an incoming BYE message is received. As for headers on an incoming INVITE, the first ten other (non-standard) headers in the configuration file /usr/lpp/dirTalk/db/sys_dir/voip/siphdrtags.cfg can be used in SV543 on an inbound BYE.

 






Fix Level 6.1.0.526

Fix release date:06 Jun 2018
Status: Current
A fix is available: Obtain the fix for 6.1.0.526



Ticket#Issue
Resolution
1440During a SIP transfer, if a NOTIFY was received before 202 Accepted, it would cause the call to hang up.Changed the behaviour to allow this scenario and continue with the transfer as normal.
1509SIP CANCEL fails if an in-dialog request is received during an outbound INVITE sequence. For example, if making an outbound call and we receive an in-dialog NOTIFY, but the call is never answered (causing the ring timer to fire), BVR would try to send a CANCEL which would fail.This has now been fixed and BVR will now CANCEL the current pending INVITE.
n/aUpdates to allow full integration with Blueworx CX:
  • BVR logs errors if unknown vendor properties are defined in a VXML document. According to the VXML spec, they should simply be ignored.
  • BVR could hit an exception if a short property name is used in a VXML document.

Updates to allow full integration with Blueworx CX:
  • BVR now ignores unknown vendor properties.
  • BVR now accepts short property names.


 





Fix Level 6.1.0.522

Fix release date: 20 Jan 2017
Status: Current
A fix is available: Obtain the fix for 6.1.0.522



Ticket#ProblemResolution
N/AUnable to configure prompts to stop only when a complete match of an active grammar is detected in a VXML2 application.Implemented single DTMF key hotword barge-in functionality for VXML2 applications. With this, the prompt is only stopped when a complete match of the single DTMF key grammar is detected and any input that does not match is ignored.

For further details on this enhancement, please refer to the following article:
48000984717-single-dtmf-hotword-barge-in


 





Fix Level 6.1.0.520

Fix release date: 12 Dec 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.520



Ticket#ProblemResolution
T1131BVR errors 1201 and 1 are reported when a SIP call is cancelled before being 200 OK'ed if VRBE is handling the call and the AnswerCall action has been removed from the IncomingCall statetable.Fixed the issue by making sure we do something with the return code from attempting to answer the call.


 





Fix Level 6.1.0.513

Fix release date: 19 Feb 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.513



APARDescription
IV79733Corrected a problem with WVRs handling of resources specifying more than one cache-control directive, for example:
Cache-Control: max-age=0, public
which could cause a java.lang.NumberFormatException to occur.


 




Fix Level 6.1.0.510 

Fix release date: 05 Oct 2015
Status: Current
A fix is available: Obtain the fix for 6.1.0.510



APARDescription
IV76087Fixed a problem with port scanners connecting to VRBE listening port and sending rubbish. This causes an out of memory error and all call related information to become stagnant.
IV74716Removed the line 'export LDR_CNTRL=MAXDATA=0x40000000' in dtjshost script that reduced the amount of memory available to the native heap, as it is not needed anymore in Java 1.4.2 and higher. In almost all instances, the automatic settings of LDR_CNTRL=MAXDATA will be adequate.
IV76895Fixed a problem where the system would report an Inconsistent CacheManager Version error like the following:

2015-09-01 23:23:37.111 call 0:0.0.0.0 PID[0:34] (2025015) FAILURE: Inconsistent CacheManager version.
FileCache::get(http://localhost:9080/Greeting.jsp) file length=0 version=0
IV77027During the import of the DTJConsult state tables, lines of the state table were not imported yet no error was flagged. These lines represented the test for a VOIP verses non VOIP call. The resultant imported state table treated each call as VOIP, performing a TransferCall action with an empty PhoneNumber parameter and with the TO_HDR tag set to the numberToCall parameter that is passed to the state table. In the non VOIP case, depending on the protocol in use, a transfer may well have been attempted but no transfer data was provided.

This fix updates the DTJConsult state table to correctly process the transfer of both VOIP and non VOIP calls. If you have modified this state table for your own purposes, you will need to modify it again after importing the new version.

As the BVR user:
  1. Ensure WVR is running.
  2. As WVR user (normally dtuser) run:
    DTst -export -f $DTJ_DIR/DTJConsult.st.backup -o DTJConsult
  3. cd $DTJ_DIR
  4. dtjstimp DTJConsult.st

Note: a non zero result means failure

If you have customised the DTJConsult state table, you will need to restore those changes. The modified state table was backed up in step 2 to the file $DTJ_DIR/DTJConsult.st.backup.

To see the detailed changes, diff the $DTJ_DIR/DTJConsult.st.backup and $DTJ_DIR/DTJConsult.st files.


 




Fix Level 6.1.0.505 

Fix release date: 02 Jun 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.505



APARDescription
IV73057Fixed a problem in the VXML browser that can cause an error when attempting a non-SIP transfer from within a VXML application, resulting in the following output: VarScope::eval:The undefined value has no properties.:error executing: session.connection.protocol.sip.outbound


Internal Defect fix

  • Fixed an problem where WVR would not properly process 4XX and 5XX HTTP return codes responding to fetches, taking the empty response as the document. The error code should now be correctly logged rather than just resulting in a parse error such as "VXML browser terminated with exception com.ibm.vxi.intp.BrowserProcException: VXIContext::interpret"

 





Fix Level 6.1.0.503 

Fix release date: 16 Apr 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.503



APARDescription
IV70888Fixed a problem where the following error is shown on a transfer:
VarScope::eval:The undefined value has no properties.:error executing: session.connection.protocol.sip.outbound
This should only be an issue with non-SIP systems doing VXML transfers.
IV71467Fixed a problem where dtjcache assumes an hour of maxstale expiry time that does not exist, and so reports the expiry of audio files an hour later than they will actually expire and be refetched by WVR.


 




Fix Level 6.1.0.477 

Fix release date: 20 Oct 2014
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.477



APARDescription
IV62786Fixed a potential deadlock in the CCXML browser that could cause new calls to hang before audio is played to the caller.


 




Fix Level 6.1.0.475 

Fix release date: 25 Jul 2014
Status: Preventative Maintenance (Fix Pack 9)
A fix is available: Obtain the fix for 6.1.0.475



APARDescription
IV61891The Fix Pack contains the following new enhancements:
  • Outbound arbitrary SIP headers
  • RTP for Avaya (SRTP key management)
  • VoIP/SIP audio compression codec support

For more information on the Fix Pack 9 features, please refer to the following article:
48000984721-blueworx-voice-response-for-aix-v6-1-fix-pack-9
IV55438Fixed an issue where VXML using <p> and <s> as part of TTS would be converted to <paragraph> and <sentence> before being sent to the TTS service. Tags will now remain as originally given in the VXML document, <p> remaining <p> and <paragraph> remaining <paragraph>. The same is true for <s> and <sentence>. Should a user need to force the old behaviour, they can add the following line to dtj.ini file:
wvr.vxml2.useoldssml=true
IV52433Fixed an issue where DTMF grammars generated by VoiceXML <option>s in <field>s would fail to evaluate the result properly, generating the following error:

VarScope::eval:missing ; before statement:error executing:var $$$;
function func1() {
var $ = new Object ();
var _text = "1";
__WVR__PLACEHOLDER__FOR__DOLLAR__"1";
$$$ = new Object(); $$$.text = _text; return $;
}
func1();

This error occurs when generating DTMF results locally rather than via a Voice Server.


Internal Defect fixes

  • Fixed Single Call Mode CCXML to prevent a bug where applications would take 30 seconds to answer calls, playing silence instead of progressing with the call.
  • Fixed an issue where an incorrect error message would be shown if rejecting an inbound call due to the default application being unavailable, instead the message would read "Unknown called

 





Fix Level 6.1.0.450 

Fix release date: 25 Nov 2013
Status: Preventative Maintenance (Fix Pack 8)
A fix is available: Obtain the fix for 6.1.0.450



APARDescription
IV50090New feature contained in this PTF:
  • Blueworx Voice Response can now be configured to pass data from SIP headers of your choice into the application layer, state table, VoiceXML and CCXML.
    By default SIP will pass tags such as the TO and REQUEST headers.

    This feature allows you to specify headers to pass up to the code - for example, custom SIP headers used to pass user-to-user information.

For more information on the Fix Pack 8 features, please refer to the following article:
48000984720-blueworx-voice-response-for-aix-v6-1-fix-pack-8
IV50647Fixed a problem where temporary audio files with extensions such as .a00, .a01 etc. would persist and start to fill up the filesystem due to an internal timing error.
IV47942Fixed an issue where dtjlogmon would fail to realise that the condition that it was searching for had occurred due to either hanging on the dtjflog read or failing to read a large enough part of the log file to actually make a full trace line.
IV44912Fixed an issue that prevented POST data from reaching the CCXML HTTP server. The server will now accept parameters delivered both in POST data and on the URL as GET-parameters.
IV41087Fixed a problem where a ClassCastException arises from a multi-level NLSML <instance> heirarchy failing to parse from an NLSML result.
The Exception is between com.ibm.voice.server.nlsml.NLSMLVector and String and an example is:

Error in startElement(,alignment,alignment,org.apache.xerces.
parsers.AbstractSAXParser$AttributesProxy@a300a30){value:[],
confidence:63.0}
java.lang.ClassCastException: java.lang.String incompatible with
com.ibm.voice.server.nlsml.
NLSMLProcessor$NLSMLDatahandler$NLSMLVector
IV41158Fixed a problem that could result in a NullPointerException when using the VXML property:
<property name="com.ibm.dtmf.useexternaldetection" value="true"/>
to change where WVR performs DTMF detection.


 




Fix Level 6.1.0.425 

Fix release date: 17 May 2013
Status: Preventative Maintenance (Fix Pack 7)
A fix is available: Obtain the fix for 6.1.0.425



APARDescription
IV37772New feature contained in this PTF:

The dtjcache command has been modified to allow three new parameters:-age, -olderThan and -delete.Both age and olderThan specification flags filter the resources to be expired to be those older than an amount of time (-age) or a specific point (-olderThan). When used on the VoiceXML cache, the -delete flag not only expires the resource but also removes the cached resource from the filesystem. The default behavior when a resource is expired from the VoiceXML cache is to leave the resource on the filesystem.

For more information on the Fix Pack 7 features, please refer to the following article:
48000984722-blueworx-voice-response-for-aix-v6-1-fix-pack-7
IV33057A new dtj.ini parameter has been added to allow the system administrator to disable logging from the PlexManager, this includes logging from commands such as dtjqapps, dtjqccx and dtjqhost.
To disable logging, add the following line into dtj.ini:
dtj.plexmanager.logging=false
IV32400Fixed a problem where information files were not deleted from the VoiceXML cache when the content was, resulting in increasing use of disk space on systems that cache a lot of differently named files.


 




Fix Level 6.1.0.400 

Fix release date: 02 Nov 2012
Status: Preventative Maintenance (Fix Pack 6)
A fix is available: Obtain the fix for 6.1.0.400



APARDescription
IV28113New features contained in this PTF:
  • DTMF Hotword Support
    Hotword DTMF barge-in is now supported with remote DTMF grammar detection.
  • VRBE Sample Updates
    The sample applications shipped with WVR have been updated to work with the Nuance Speech Server in addition to Blueworx Voice Server.
  • Reporting of raw NLSML result within a VXML application
    Blueworx Voice Response now supports the use of multiple recognition contexts for speech recognition in VoiceXML applications, including the raw NLSML that was returned from the speech server.

For further information on the Fix Pack 6 features, please refer to the following article:
48000984723-blueworx-voice-response-for-aix-v6-1-fix-pack-6

NOTE: If the following error is logged in the DTstatus.out window after installation,then run dtjconf to reload the VRBE configuration:DTJ3138 Configuration database /var/dirTalk/DTBE/native/aix/config.cfd may be from previous release, run dtjconf to refresh
IV26371Modified code to ensure that the com.ibm.dtmf.useexternaldetection property can be set when using Nuance NDMs.
In order to set the property for an individual NDM subdialog, add a variable declaration for property_useexternaldetection and set it to the value you want for the com.ibm.dtmf.useexternaldetection property.
Then add the variable into the namelist attribute for the NDM subdialog call, for example:

<var name="property_useexternaldtmfdetection" expr="'true'"/>

<subdialog name="ndm_core_call"
src="http://ndm.ibm.com/ndm-core/controller/ndm"
method="get"namelist="property_useexternaldtmfdetection"/>

IV23252Fixed a potential deadlock in Audio fetching present in VRBE levels 6.1.361 - 6.1.375. With those levels, Audio fetches would stop being processed but VoiceXML would otherwise operate should this deadlock occur.
IV21356Implemented a fix to resetting VRBE tracing using the trcserv command. Previously, when resetting VRBE tracing after removing some trace options from trcserv.ini, the value for the removed option would not revert to the default. This only affected a couple of the trace options, including trace.output.dir. This has now been fixed so that if the option is no longer present in trcserv.ini, the default option value is used.


Internal Defect fix

  • Fixed a problem that caused a VXML consult transfer to fail with a timeout when using Genesys CTI

 





Fix Level 6.1.0.375 

Fix release date: 27 Jun 2012
Status: Preventative Maintenance (Fix Pack 5)
A fix is available: Obtain the fix for 6.1.0.375



APARDescription
IV20322New fixes contained in this PTF:
  • Turn-based MRCP
  • Trusted Host List

For further information on the Fix Pack 5 features, please refer to the following article:
48000984724-blueworx-voice-response-for-aix-v6-1-fix-pack-5

NOTE: If the following error is logged in the DTstatus.out window then run dtjconf to reload the VRBE configuration.

E DTJ3138 Configuration database /var/dirTalk/DTBE/native/aix/config.cfd may be from previous release, run dtjconf to refresh

New fixes contained in this PTF:

Fixed dtjqapps to display the correct Node that an application is executing in, rather than the VRNode.
IV21232Fix to VoiceXML <goto> element to correctly handle blank next attribute.
IV21656Update to allow customers to change the key value pair separator character used in a GCTI route requests.
IV19724Fixed a memory leak in the audio cache which would occur only for dynamically generated audio file URIs. A Hashmap grows with each new request that doesn't have the same URI as a previously fetched resource.
IV11846Fixed parameter type issue when using <object> element to perform GCTI RouteRequest.
IV12318Fixed to ensure connection.transfer.disconnect is not thrown too quickly after a CTI transfer.
IV12638Added an optional parameter into the object tag call used to perform a GCTI RouteRequest from a VXML application that allows the application to override the default GCTIUData separator character. The parameter is called setGCTIUDataSeparatorCharacter and takes a single character as the value.

For example to change the separator character to a semicolon you would code the object tag like this:

<object name="gcti"
classid="method://com.ibm.wvr.vxml2.NativeAppSupport/invokeGCTI"
type="javacode-ext" codetype="javacode-ext">
<param name="setGCTIActionToInvoke" value="RouteRequest"/>
<param name="setGCTIUDataSeparatorCharacter" value=";"/>
<param name="setGCTIUData" expr="'1=1;2=2;time=12:13:14'"/>
<param name="setGCTIRouteDN" value="vdn"/>
<param name="setGCTIRouteCED" value="1234"/>
</object>

The default behaviour if the new parameter is not used will be to use a colon as the separator character.
IV10235The error message: "com.ibm.ccx.browser.CCXParser parse() Got SAXException (Error in <ccxml> element: Document has more than one <ccxml>" appears
despite the document being fetched not having multiple ccxml elements.
CCXML then refuses to load any more documents with the same error.


Internal Defect fixes

  • Previously the Genesys Framework configuration panel provided by dtjit had "Client Name" and "Call ID Range" as optional parameters. This was incorrect and these parameters have now been modified to be mandatory. At the same time typical default values have been provided for the Start and End settings for "Call ID Range".
  • Provide new AAIKVPSeparator parameter within default.cff TelephonyService to override default AAI separator character.
  • Improve error reporting when attempting to parse an invalid VXML document. The trace and log will contain URI (including attributes), line number, column number and XML parsing error. The logging showing the semi parsed VXML document as been removed as this was confusing and unhelpful.
  • Fixed a rare NullPointerException. The NullPointerException was reported as:
    (DTJ1008046) FAILURE: VXML2TurnCoordImpl.doField Caught a
    RuntimeException: java.lang.NullPointerException
    at com.ibm.wvr.vxml2.VXML2TurnCoordImpl.doField
    (VXML2TurnCoordImpl.java:1359)
    at com.ibm.wvr.vxml2.VXML2TurnCoordImpl.doTurn
    (VXML2TurnCoordImpl.java:269)
    at sun.reflect.GeneratedMethodAccessor32.invoke
    (Unknown Source)
  • Fixed internal system monitor functionality.
  • Fixed specification non-compliance where we would ignore the Path set on any cookie headers that we received in VoiceXML applications. A resolution mechanism has been added to handle overlapping cookies with different paths set on a web server - for example, a web server could specify different sessionid cookie headers for two different areas of the site. Existing fetching without paths should be unaffected, but if a user wishes to force use of the old method then they should set the following in $DTJ_HOME/dtj.ini
    wvr.vxml2.FetchSession.ignoreCookiePath=yes
  • Increased the default trace buffer size and reduce time waiting if there are no more trace buffers. This does not change the amount of trace written to disk or the size of the trace files on the disk. The change is to handle situations when a lot of trace is being generated and the internal trace system can not keep up. When this happens the tracing routines will slow down causing VRBE to also slow down.
  • Fixed an issue where WVR would fail to fetch certain Nuance builtin URIs reporting a FileNotFoundException.
  • Fixed a NullPointerException gleaned from using a voice-enabled menu in a document that does not specify 'xml:lang'.
  • Fixed dtjit which incorrectly offered en_UK as an option in the Locale field for Add/Change TTS Service and Reco Service panels. This has now been corrected to be en_GB.
  • Fixed an issue with very long URI lengths that would cause resource not to be cached for VXML and potentially cause performance issues by altering the way that files are named in the cache. This fix will mean WVR will not use any files cached before this fix is applied.
  • Fixed the universals help grammar to work with various speech site documents.
  • Updated the dtjes script to delete both old and new style of VoiceXML cache.
  • Move some CPU intensive tracing from trace level 8 to trace level 9.

 





Fix Level 6.1.0.350 

Fix release date: 13 Dec 2011
Status: Preventative Maintenance (Fix Pack 4)
A fix is available: Obtain the fix for 6.1.0.350



APARDescription
IV09336New features contained in this PTF:
  • Remote DTMF detection and DTMF Grammar Compilation
  • Enable Endpointed Audio with Nuance NR9
  • "Core" Nuance Framework Dialog Modules Certification
  • Expanded <property> element support

For further information on the Fix Pack 4 features, please refer to the following article:
48000984725-blueworx-voice-response-for-aix-v6-1-fix-pack-4
IV09441Fixed an issue where WVR could fail to parse a reco result in some cases, reporting a property error:

"function evalSI () { var si = {, length:0}; return si;); evalSI();"
IV08758Ensured that the correct connection.disconnect.hangup event is returned if a caller HUPs before a transfer is started.
IV03718Corrected a potential exception within the dtjstop command that can cause VRBE nodes to remain running after dtjstop is executed.
IV03720Code changes made to ensure that the correct "termtimeout" is used for a nomatch when using a DTMF grammar.


Internal Defect fixes

  • Fixed the <menu> VXML element so that Voice navigation of a menu now works correctly with Nuance and Loquendo.
  • Improved application error logging and inclusion of document name where missing.
  • Fixed an issue with NLSML slot results being presented as conglomerate results if different slot names were used in individual results.
  • Fixed an issue where a single result, single slot NLSML-enabled grammar could have the wrong interpretation format.
  • Fix to enable the passing of the VoiceXML <mark> element to a speech server in a VoiceXML version 2.0 application.
  • Made a change to the <menu> element processing to ensure that the language is sent to the MRCP server if the menu can be navigated using voice.

 





Fix Level 6.1.0.300 

Fix release date: 6th July 2011
Status: Preventative Maintenance (Fix Pack 3)
A fix is available: Obtain the fix for 6.1.0.300



APARDescription
IV00121New features contained in this PTF:
  • ECMAScript 1.7 Support - VoiceXML and CCXML applications can now be configured to use ECMAScript 1.7 for their scripts. By default the existing ECMAScript 1.3 implementation will be used.
  • Bargein type=dtmf_only - Provided a method for VoiceXML prompts in a speech enabled application to restrict the method of bargein to be DTMF only, rather than both Speech and DTMF.
  • Multiple Grammar Result Contexts Support - Blueworx Voice Response now supports the use of Speech Grammars that return multiple interpretations of the recognition with contextual information in the form of named slot arrays for speech recognition in VoiceXML applications.
  • CCXML Latest Version - CCXML has been updated to conform to the Proposed Recommendation of the CCXML specification, located at
    http://www.w3.org/TR/2011/PR-ccxml-20110510/
  • VRBE call transfer mechanism implemented in DTJConsult has been updated to:
    - better support VXML blind transfer using SIP
    - add support for VXML consultation transfer using SIP
    - show the possible use of the XFER_TIMER tag with VXML blind transfer using SIP

    See the DTJConsult update section below for more details.

    NOTE - for VXML consultation transfer using SIP to work the VOIP_Call_Transfer custom server must be installed and running.
    For details on how to install and execute this custom server, refer to Blueworx Publications at the following URL :
    http://docs.blueworx.com/BVR/InfoCenter/V6.1/help/index.jsp?topic=%2Fcom.ibm.wvraix.voip.doc%2Fattendedtransferusingthevoip_c5.html

For further information on the Fix Pack 3 features, please refer to the following article:
48000984745-blueworx-voice-response-v6-1-for-aix-fix-pack-3
IZ92785Fixed a potential "No Reco or TTS plugin found error" when using CCXML applications.


Internal Defect fixes

  • Fixed a NotSerializableException possible with caching Audio files of the form:
    com.ibm.vxi.cachemgr.CacheException: Lost Connection to the VRNode,reason [error marshalling arguments; nested exception is:
    java.io.NotSerializableException: com.ibm.wvr.vxml2.DTAudioProxy]
    at com.ibm.wvr.vxml2.DTAudioProxy.put(DTAudioProxy.java:846)
    at com.ibm.vxi.resmgr.Fetcher.fetchFromServer(Fetcher.java:828)
    at com.ibm.vxi.resmgr.Fetcher.performCachePolicy(Fetcher.java:488)
    at com.ibm.vxi.resmgr.Fetcher.run(Fetcher.java:226)
  • Fixed an issue where VoiceXML2 applications invoked from the Java API could fail with a NullPointerException at:
    com.ibm.wvr.vxml2.DTTelServiceSupport.getSessionVar
    (DTTelServiceSupport:210)
  • Fixed an issue where CCXML would not use the default port on an outbound <send> HTTP post.
  • Fixed an issue with caching long URIs that did not contain a '?', and would instead throw an IOException with the message "Filename was too long to create a file for, name: <URI>".
  • Prevented a potential memory leak in the VRNode caused by a gradual increase in thread usage.
  • Fixed an issue where VRBE would repeatedly fail to load resources from the cache due to cache corruption. VRBE now forces a refetch of the cached resource.
  • Provide parameters to allow a system administrator to limit the number of threads WVR will use when fetching resources on system startup.

    The following parameters have been added which should be added to $DTJ_HOME/dtj.ini :
    wvr.vxml2.fetchthreads.limit
    wvr.vxml2.fetchthreads.limit.timer

    Where wvr.vxml2.fetchthreads.limit is the maximum number of threads to use (default is 500) and wvr.vxml2.fetchthreads.limit.timer is the time in minutes to apply the limit (default 10 minutes).
    After this time, WVR will revert to the default maximum thread limit. Setting wvr.vxml2.fetchthreads.limit.timer to 0 applies the limit permanently.
  • Fixed an issue where CCXML wildcard NumToApp mappings would take precedence over specific VoiceXML or Java API applications. For example, using the following NumToApp mappings:
    NumToApp=111,VXMLApp
    NumToApp=1*,CCXMLService
  • Fixed an MRCP resource problem that can result when multiple VXML documents are called from one CCXML document during a single call.
  • Fixed a potential StringIndexOutOfBoundsException that could occur is there was an error when using dtjcache to list items.
  • Fixed the VoiceXML caching to allow long URIs to be stored (Previously, AIX would prevent any URI longer than 254 characters being stored)
  • Fixed an issue which would cause a second instance of connection.connected events to be generated when being moved from one session to another using <move>.
  • Fixed an issue where return values from a VoiceXML <exit> would be preserved for a second VoiceXML document used on the same call.
  • Fixed CCXML-controlled VoiceXML transfers to be more descriptive in errors. Also fixed dialog.transfer events to contain .uri as per spec, the .URI parameter has been kept for backwards compatibility.
  • Fixed an issue where dynamic browsers were not released for five minutes when VoiceXML made a transfer using CCXML.
  • Fixed an issue with CCXML <move> that could lead the session.connections entry of a connection to have an inconsistent input and dialogid entry.
  • Fixed an issue where <createcall> requests from CCXML could fail when the rest of VRBE was still starting up. Calls would fail with System Failure.

 





Fix Level 6.1.0.250 

Fix release date: 30th November 2010
Status: Preventative Maintenance(Fix Pack 2)
A fix is available: Obtain the fix for 6.1.0.250



APARDescription
IZ86672New features contained in this PTF:
  • Enhanced VoiceXML and CCXML application support for call information - Provide protocol specific tagging information in VXML and CCXML.
  • VRBE Expire Resource Tool - allows a system administrator to manually expire a resource in the VXML, CCXML or Audio caches.
  • VRBE problem determination utility - enables a system administrator to collect a dtbeProblem output (or run any other command) automatically when an error or other message is reported in VRBE.
  • Nuance Certification - SpeechClient supported by Nuance.

For further information on the Fix Pack 2 features, please refer to the following article:
48000984726-blueworx-voice-response-for-aix-v6-1-fix-pack-2
IZ84830Fixed an issue that can cause a MRCP PluginException (completion-cause 006) if a caller hung up just after a recognition attempt was started.
IZ80778Fixed a VarScope error which can occur when a grammar result returned from a Nuance server included empty strings. The VarScope error will look like the following:

(VXI00000) FAILURE: 654322449181048843-0:VarScope::eval:syntax
error:error executing:function evalSI ()
IZ80780Fixed an issue that can cause a delay in a speech enabled VXML application if the caller does not provide any input to the prompt.
IZ80782Fixed a potential deadlock when fetching VXML resources that can cause a memory leak and eventually an OutOfMemory error.


Internal Defects fixes

  • Introduced a new dtj.ini paramter 'wvr.vxml2.grammar.fetch.external' to provide an override in WVR for unnecessary grammar fetching/caching when using SpeechServer.

    If wvr.vxml2.grammar.fetch.external=false, then http/https/builtin grammars will no longer be fetched by WVR (either at prefetch or during document execution), but they still will be fetched by the speech server. Only file: grammars will continue to be fetched by WVR.

    By default this is set to true (current behavior) ie all grammars are fetched by WVR.
  • Fixed an issue where cached VoiceXML files would remain in the cache (but be unused ) when the cache control headers were changed to nocache or to have an expires value of 0.
  • Fixed a potential NullPointerException when executing a dialogprepare element in CCXML. Note that this would not occur with a straight dialogstart.
  • Remove erroneous file from vxi.jar.
  • Allow non W3C defined builtin grammars to be referenced within VXML2 documents as supported by Nuance. e.g. CreditCard.
  • Fixed an incompatibility issue with Nuance recognition and WVR which could cause an "ERROR: NLSMLException" to be reported in the VRBE log files.
  • Fixed an issue where if two VXML dialogs were started sequentially from one CCXML document, when the second dialog was initialised an exception could occur stopping the CCXML application.
  • Fixed an issue where self-terminating <send> elements in CCXML documents with space after the / character would throw a StringOutOfBoundsException
  • A race condition exists between the starting of the Java Hostmanager and the DTAAlarm process. If the Hostmanager wins the race then errors such as:
    com.ibm.hursley.trace.DTAAlarmQueue.process() NotBoundException java.rmi.NotBoundException: DTAAlarm

    are written to the VRBE log file. This fix resolves the race condition and ensures these errors are not logged.
  • Under certain circumstances DTAAlarm can terminate with a RemoteException when dtjshost -exit is run. This change prevents this invalid termination from occurring.
  • Fixed issue with VoiceXML not getting passed parameters from CCXML intermittently when many VXML browsers are being started. The error seen would depend on what the parameter was being used for, typically with the <value> tag. An example error would be VarScope::eval:The undefined value has no properties.:
    error executing:session.ibm.values.passedInParam
  • To avoid JVM errors between multiple AppNodes, the dtjit tool will automatically specify one separate VXML2Cache per AppNode. The error that could otherwise appear is: "Unable to obtain exclusive file lock".
  • Fixed a CCXML issue that would occasionally cause a CCXThread.run() error message to report a NullPointerException, stopping CCXML from starting up. This is due to a timing error in sending messages before the internal queues are set up completely.
  • Previously the session.uri field would strip forwardslashes from the uri after the protocol, e.g. http://example.com becomes http:example.com. This fix ensures the URI is set to the exact value used to fetch the source of the CCXML document.
  • Enables the use of code like the following in CCXML:
    <var name="myHints" expr="new Object()"/>
    <assign name="myHints.CLGN" expr="new Object()"/>
    <assign name="myHints.CLGN._value" expr="'932000'"/>
    <assign name="myHints.CLGN.NUMBER_TYPE" expr="'0'"/>
    <assign name="myHints.CLGN.NUMBER_PLAN" expr="'0'"/>
    <createcall dest="'tel:121281;phone-context=056534'" hints="myHints" timeout="'10s'"/>
    to make a call to an ISDN switch whilst setting multiple parameters, rather than just a single level. (In the example above, setting myHints.CLGN to a simple string rather than a map of several attributes.) The _value part will be turned into the value of the tag by WVR, e.g.
    <`CLGN`=`932000` `NUMBER_TYPE`=`0` `NUMBER_PLAN`=`0`>
  • Fixed a problem where <object> element calls to java classes may fail due to tighter rules on class name definitions. This fix ensures that java classes are invoked correctly internally and requires no change to the customers VXML application.

 





Fix Level 6.1.0.221 

Fix release date: 1st April 2010
Status: Preventative Maintenance (Feature Pack 1)
A fix is available: Obtain the fix for 6.1.0.221



APARDescription
IZ71038Features included in this PTF are:
  1. Changes needed in VRBE to provide ISDN UUI protocol specific tagging information in VXML and CCXML applications.
  2. Changes needed in VRBE for significant usability improvements to WVR Java application logging.
  3. Better integration with the advanced CTI services offered by the Genesys CTI platform. Allows VXML applications to use internal routing within the Genesys CTI platform.

For further information on the Feature Pack 1 features, please refer to the following article:
48000984727-blueworx-voice-response-for-aix-v6-1-fix-pack-1
IZ66158Removed potentially confusing error message about DJIT_HOME not being set
IZ68709This fix corrects an out of memory cache problem which can occur when fetching large numbers of CCXML documents.
IZ61670Maxspeechtimeout events did not generate an application.lastresult$ variable. However, with the introduction of recordutterance it is useful for them to do so in order to access the recording subproperty.


Internal Defects fixes

  • Fixed the support of CDR recording of VXML applications.
  • The dtaalarm code produced a new log file in $DTJ_LOGS each time the alarm server is started, rather than using existing log file. It should now operate correctly.
  • The toString method in DTAAlarmMessage did not check for null params in the param list. If it got one then a null pointer exception occured. This is now fixed.
  • DTAAlarmQueue.java required logging of certain failures, which were only traced. The queue should now operate properly.
  • Upgraded message displayed by dtjit shown when VRBE tracing is on and VRBE is not running.
  • Fixed a StringIndexOutOfBoundsException raised by the VXML browser which could cause the browser instance to terminate.
  • Update prerequisite level for Java6.sdk to Service Release 7 (Fix level 6.0.0.175) as it is required to fix memory release problem.. The following URL is a link to the Java 6 APAR:
    http://www.ibm.com/support/docview.wss?rs=1207&uid=isg1IZ67337
  • Corrects a mis-spelling in the vrbetrace shell script that meantwhen logging was required from the dtjit utility by setting DTJIT_DEBUG environment variable, if vrbe tracing or logging was modified then the correct java executeable required toexecute the modification was not invoked and the modification.
  • Fixed issue when internal components of WVR tried to talk to each other when one had already exited - now they should stop.
  • Fixed an issue where dialogs taking a long time to return tried to communicate with connections that no longer exist.
  • Fixed a problem with the <break> tag that could be seen when migrating a VXML2 application from a WVR 4.2 system.



VOIP_SIP Fixes


 





Fix Level 6.1.0.527

Fix release date: 04 Dec 2018
Status: Current
A fix is available: Obtain the fix for 6.1.0.527



Ticket#Update Details
n/aAdded support for IBM Voice Gateway to BVR. For more details, refer to the Blueworx Help Center article:
Integration with IBM Watson through IBM Voice Gateway
1555Fixed memory leak and added some missing socket closes for TCP and TLS SIP connections.
n/aExtended support for incoming SIP headers using the siphdrtags.cfg file.

Previously header entries in siphdrtags.cfg controlled the SIP headers that were provided as tags in SV542 when an incoming INVITE message was received.


This fix update extends this support so that header entries in siphdrtags.cfg can now be used to provide SIP headers as tagss in SV543 when an incoming BYE message is received. As for headers on an incoming INVITE, the first ten other (non-standard) headers in the configuration file /usr/lpp/dirTalk/db/sys_dir/voip/siphdrtags.cfg can be used in SV543 on an inbound BYE.


 





Fix Level 6.1.0.526

Fix release date: 06 Jun 2018
Status: Current
A fix is available: Obtain the fix for 6.1.0.526



Ticket#Issue
Resolution
1440During a SIP transfer, if a NOTIFY was received before 202 Accepted, it would cause the call to hang up.Changed the behaviour to allow this scenario and continue with the transfer as normal.
1509SIP CANCEL fails if an in-dialog request is received during an outbound INVITE sequence. For example, if making an outbound call and we receive an in-dialog NOTIFY, but the call is never answered (causing the ring timer to fire), BVR would try to send a CANCEL which would fail.This has now been fixed and BVR will now CANCEL the current pending INVITE.
n/aUpdates to allow full integration with Blueworx CX:
  • BVR logs errors if unknown vendor properties are defined in a VXML document. According to the VXML spec, they should simply be ignored.
  • BVR could hit an exception if a short property name is used in a VXML document.
Updates to allow full integration with Blueworx CX:
  • BVR now ignores unknown vendor properties.
  • BVR now accepts short property names.


 














Fix Level 6.1.0.525

Fix release date:22 Mar 2018
Status: Current
A fix is available: Obtain the fix for 6.1.0.525



Ticket#Issue
Resolution
1402After adding Request in siphdrtags,cfg, enable ports caused the core dump.Fixed a core dump in VOIPL3_SIP that can occur when using the siphdrtags.cfg
1445The DTdatabase -r command fails on a BVR version 6.1 system that has been upgraded from DB2 version 9.5 to 10.1. The error message displayed is:
SQL5186N Configuring the DB2 environment failed because the specified DB2 environment variable, DB2 registry variable, or DB2 configuration parameter is discontinued. Variable or parameter name: "DB2_RR_TO_RS"
Removed the discontinued variable DB2_RR_TO_RS from the DTdatabase script. This variable is discontinued because Type-1 indexes are no longer supported.
1460A crash occurred that was caused by the DTNA.Fixed a rare crash that can occur as a trombone is being broken down by adding checks to make sure trombone hasn't been destroyed before attempting to destroy it.
N/AIncomplete SDP is being presented during on hold delayed offer.Fixed SIP handling of a delayed offer INVITE to renegotiate the streams whilst in an on hold (inactive). The full SDP is now correctly generated.


 




Fix Level 6.1.0.518 

Fix release date: 21 Nov 2016
Status: Current
A fix is available: Obtain the fix for 6.1.0.518



Ticket#IssueResolution
T1048An UPDATE request arrives during the INVITE sequence prevents call being answered.Fixed so the call does get answered. Also applies to any other incoming requests during the INVITE sequence.
T1061INVITEs with unsupported Content-Types are rejected when Content-Disposition handling is "optional".Incoming INVITEs with non-SDP "optional" content in the message body is now treated as a delayed offer.


 




Fix Level 6.1.0.515 

Fix release date: 29 Feb 2016
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.515



APARDescription
IV79550Prevent occasional errors if SIP call is CANCELled immediately.


 




Fix Level 6.1.0.509 

Fix release date: 26 Jul 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.509



APARDescription
IV74885A new configuration option "Late Offer on Outbound Calls" has been added within the "Voip SIP Signalling" configuration panel. If set to yes then no SDP will be provided on the outgoing INVITE request associated with an outgoing call. If set to no (the default) then behaviour will be unchanged for outgoing calls and SDP will be attached to outgoing INVITE requests.

For further information on this feature, please refer to the following article:
48000984795-support-for-late-offer-on-voip-sip-outbound-calls


 





Fix Level 6.1.0.506 

Fix release date: 04 Jun 2015
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.506



APARDescription
IV72815Fixed a problem to allow data to be passed along with the transfer address on a SIP blind transfer. The data is passed by adding a '?' character after the transfer address followed by the data.
For example, data of "User-to-User=123456" is passed as follows:

sip:247093@machine.location.company.com?User-to-User=123456

The data is passed within the Refer-To header contained in the REFER message that is sent as part of a blind transfer. For example

Refer-To:sip:247093@machine.location.company.com?User-to-User=123456

Note - Previously WVR stripped the '?' chararacter and any subsequent data from the transfer address.

Snippet of state table code:
AssignData(numberToCall, "ASSIGN" ,"sip:247093@machine.location.company.com?User-to-User=123456");
AssignData(SV541, "PUT_TAG", "TO_HDR", numberToCall);
TransferCall("", "", 0, 0, 0);

Snippet of VXML Code:
<form id="transfer1">
<transfer name="mycall" dest="sip:247093@machine.location.company.com?User-to-User=123456" type="blind">
<filled>
<log>
Transfer filled. mycall (form variable) = <value expr="mycall"/>
</log>
</filled>
</transfer>
</form>

Snippet of CCXML Code:
<transition event="connection.connected">
<if cond="event$.connection.local == '1001'">
<log expr="'[connection.connected] Immediate CCXML blind transfer call...'"/>
<var name="target" expr="'sip:247093@machine.location.company.com?User-to-User=123456'"/>
<send
target="event$.connectionid"
name="'ibmwvr.transfer'"
namelist="target"
targettype="'connection'"/>


 






Fix Level 6.1.0.480 

Fix release date: 27 Oct 2014
Status: Superseded
A fix is available: Obtain the fix for 6.1.0.480



APARDescription
IV65421Correctly hangs up call if a BYE is received during a consultation transfer when we're expecting a NOTIFY.
IV65816Fixed SIP code to:
  • send 200 OK on INFO message with no content. No longer raises 29805 error as a result.
  • prevent 29806 error on blind transfer.


 





Fix Level 6.1.0.475 

Fix release date: 25 Jul 2014
Status: Preventative Maintenance (Fix Pack 9)
A fix is available: Obtain the fix for 6.1.0.475



APARDescription
IV61889The Fix Pack contains the following new enhancements:
  • Outbound arbitrary SIP headers
  • RTP for Avaya (SRTP key management)
  • VoIP/SIP audio compression codec support

For more information on the Fix Pack 9 features, please refer to the following article:
48000984721-blueworx-voice-response-for-aix-v6-1-fix-pack-9
IV56199Fixed a problem with the SDP origin version not changing on a reINVITE of an existing call which can confuse some SIP endpoints.
IV54188Fixed an issue that would lead to incomprehensible errors if a user sets the proxy mode to Local Proxy and leaves Proxy Address blank.Transfers/outbound calls will now generate a meaningful error and abort the routing in this bad configuration.
IV52385Fixed the "Override DTNA RTP Transport IP Address" system parameter to no longer be ignored if set.


 





Fix Level 6.1.0.450 

Fix release date: 25 Nov 2013
Status: Preventative Maintenance (Fix Pack 8)
A fix is available: Obtain the fix for 6.1.0.450



APARDescription
IV50082New feature in this PTF:
  • SIP Register now supports the authentication digest challenge mechanism that allows a registrar to identify the registering party and so stop third parties from being able to register as a user.

    This feature works automatically if your registrar supports it and has it enabled, and can be used independently from Secure SIP.

For more information on the Fix Pack 8 features, please refer to the following article:
48000984720-blueworx-voice-response-for-aix-v6-1-fix-pack-8
IV43183Fix a problem where the SIP stack was accepting calls with media properties that are unsupported. This causes WVR to attempt to stream to an invalid IP address/port and error id 29800 may occur.
IV36641Fixed a problem where the DTEA driver would crash with a VoIP Media (UPA) Internal Failure error if DTMFs were transmitted using the SIP-Info method. A warning will now be raised to show that WVR is ignoring the input on the DTEA device driver.
IV25439Fixed a problem where an unnecessary error was raised when setting the record route header.
IV24776Fixed a problem where VOIP falsely believes that the record route information has been updated.
This can cause the route headers to appear in the wrong order.


Internal Defect fix

  • Corrected a code defect that prevented MWI blind notification from working when using VoIP/SIP.

 





Fix Level 6.1.0.375 

Fix release date: 27 Jun 2012
Status: Preventative Maintenance (Fix Pack 5)
A fix is available: Obtain the fix for 6.1.0.375



APARDescription
IV20361New features contained in this PTF:
  • Trusted Host List

For further information on the Fix Pack 5 features, please refer to the following article:
48000984724-blueworx-voice-response-for-aix-v6-1-fix-pack-5


Internal Defect fix

  • Fix MEDIA_CTRL_DTNA restart problem if VOIPL3_SIP crashes. The MEDIA_CTRL_DTNA will now correctly attempt to reconnect to the MRCPrecv and send queues.

 





Fix Level 6.1.0.360 

Fix release date: 22 Mar 2012
Status: Preventative Maintenance (including Fix Pack 4)
A fix is available: Obtain the fix for 6.1.0.360



APARDescription
IV09322New features contained in this PTF:
  • Remote DTMF detection and DTMF Grammar Compilation
  • DTNA Multiprocessor Support

For further information on the Fix Pack 4 features, please refer to the following article:
48000984725-blueworx-voice-response-for-aix-v6-1-fix-pack-4
IV16893The fileset dirTalk.VOIP_SIP 6.1.0.350 pre-req'd itself and therefore it couldn't be installed. This PTF supersedes it and pre-reqs Fix Pack 3 dirTalk.VOIP_SIP fileset.

NOTE: If you have downloaded dirTalk.VOIP_SIP 6.1.0.350, you will need to delete or remove it from the install directory, and remove the .toc file before attempting to install this PTF otherwise the install will fail.
IV14314Allows for larger SDP sizes (now up to 2048 chars).
IV12642Fixed an installation problem with the srv.init file so now it gets installed in the /home/dirTalk/sys_dir directory correctly. Before it installed in the /usr/lpp/dirTalk.VOIP_SIP/inst_root/home/dirTalk/sys_dir directory.
IV11136Fixed a VOIP issue where we weren't correctly setting the local address in contact headers when TCP is used, meaning that some callers are unable to respond to the correct address.
IV11616Fix MGCP error reporting in MEDIA_CTRL_DTNA to use base WVR rather than SIP.
IV11916If during an attempted VOIP Consult call transfer, the original caller disconnects during a certain time period while the outbound call is being established then the following errors are logged and the channel used for the outbound call can become useable for subsequent incoming or outbound calls.

errorid 29806 sequence 40911 YELLOW errno 0
parms='voip_callfn.c'
'CLSgTransferCallInConsult' '11197' '1' '1' '6' 'Outbound Transfer Call not found.' '0'

followed by :

errorid 29815 sequence 40912 YELLOW errno 0
parms='voip_callfn.c'
'CLInvalidPrim' '6283' '1' '1' '6' '14' 'Invalid layer 3 primitive for this state/event combination' '11'

Over a period of time this may manifest itself as transfer failing to work as these unuseable channels increase in number and are selected for transfer outbound call establishment.
IV08709Removed extraneous warning about No Content-Length Header, error ID 29805 when SIP is used UDP to transport RTSP messages.
IV09076Fixed a problem with MakeCall to an IP address that exists but isn't running SIP. If the MakeCall is then stopped the SIP CANCEL request also can't be sent. This causes a loop of INVITE and CANCEL requests to be sent. If a CANCEL fails to send then this will be assumed to also cancel the original request. This problem is most likely to occur if the MakeCall is via a trombone.
IV02992Added support for tromboning between:
1) RFC2833 to SIP INFO DTMF
2) SIP INFO DTMF to RFC2833
3) SIP INFO DTMF tp SIP INFO DTMF
4) RFC2833 to RFC2833 (support already present)

Add support for two SIP INFO DTMF content types:
1) dtmf-relay
2) vnd.nortelnetworks.digits


Internal Defect fixes

  • Some tracing of NOTIFY used some information from the SIP transaction. If the NOTIFY occurs without a proper transaction this can cause a crash. The trace now only occurs if the transaction is valid.
  • Stop MEDIA_CTRL_DTNA dropping into the wrong code path when VOIP is shutdown. This was causing error 29800 to be raised.
  • Remove a race condition in ES services used by VoIP. This race condition caused error 29106 from es_queue.c
  • Remove 100rel from Supported header in outbound INVITE. This can cause the UAS to require 100rel and reliable responses. WVR currently doesn't support this. The result is the 101-199 response is resent until WVR CANCEL's the call.
  • Fixed a problem where WVR reports 29805 SIP signalling process error on setRecordRoute for messages that do not have a record route defined. This fix removes the erroneous warnings.
  • Fix prevents VOIP_MONITOR from core dumping if /tmp is cleared.
  • Register removed from ALLOW as we ignore it, INFO added to ALLOW as we support it, and 100rel added to Supported as we support it.
  • Added Accept and Accept-encoding headers as required in RFC 3261.
  • Now reject INVITES with no acceptable media types as 488 - not acceptable here, as per RFC 3261.
  • Correctly report a busy condition in response to an Options request when no channels are available.
  • Fixed provisional responses for calls with a Require: 100rel.

 





Fix Level 6.1.0.300 

Fix release date: 6 Jul 2011
Status: Preventative Maintenance (Fix Pack 3)
A fix is available: Obtain the fix for 6.1.0.300



APARDescription
IV00120New feature contained in this PTF:
  • SIP Stack Auto Restart - in the event of the SIP stack crashing, Blueworx Voice Response will now automatically restart it in order to bring the system back into a working state.

When starting Blueworx Voice Response after applying this PTF, you will be prompted to accept a new licence agreement.

For further information on the Fix Pack 3 features, please refer to the following article:
48000984745-blueworx-voice-response-v6-1-for-aix-fix-pack-3
IZ92367Fix a problem when using the VOIP SIP stack against a specific ethernet adapter and that adapter is not the first adapter in the machine. The contact header is always filled out with the ip address of the first adapter in the machine. With the fix the contact is filled out with the ip address for configured adapter.
IZ92918This fix overcomes a problem found with outbound VOIP_SIP calls when the target endpoint is reached via a single outbouund proxy. In some cases (e.g. if endpoint is using secure SIP i.e. transport=tls) an outbound call would fail to be established (because SIP ACK response to 200 OK was directed to the wrong ip address).
IZ92906This fix overcomes a 29806 error (VOIP signalling process call state machine error/Invalid phone number for called party IE) for a VOIP outbound call StateTable application if any of the the digits '*#ABCD' is set in the Phone Number parameter for a MakeCall action. Previously the outbound call would fail to proceed despite the Phone Number being unused in the call setup (for VOIP outbound calls the TO_HDR tag set by the application is used).
IZ94526Fixed a issue where VOIPL3_SIP core dumped when under high load.


Internal Defect fixes

  • Allows "#" in the FROM header in VoIP SIP calls.
  • In the case of a SIP blind transfer, if the transfer target did not answer, WVR erroneously logged a yellow alarm id 29805. This error logging has been removed in the no answer case.
  • In the case of a SIP consultation transfer using the VOIP_Call_Transfer custom server, if the transfer target did not answer, WVR erroneously logged a yellow alarm errorid 29806 stating 'The outbound transfer call failed to answer'. This error logging has been removed in the no answer case.
  • Prevents WVR from including REFER in the ALLOW header when system is configured not to accept incoming transfer requests such as REFER.
  • Prevents WVR from attempting an INVITE when making calls to an invalid address
  • Fixes error causing SIP_RESPONSE_ADDRESS_INCOMPLETE to be sent unnecessarily when processing a REFER message.
  • A REFER message with a Replaces parameter in the Refer-To header now returns a SIP not implemented message rather than address incomplete message.
  • Fixes incorrect SDP messages when SIP OPTIONS received, and prevents errors being raised when an OPTIONS message is received before a call is established.
  • This fix corrects the o= (owner) and c= (connection info) SDP (Session Description Protocol) header addresses returned in a SIP message to be that of the 2nd network interface when the system is configured to use the 2nd network interface for VOIP SIP messaging. Previously for VOIP SIP calls the default (1st network interface address) was being used in these SDP parameters.

 





Fix Level 6.1.0.250 

Fix release date: 30 Nov 2010
Status: Preventative Maintenance
A fix is available: Obtain the fix for 6.1.0.250



APARDescription
IZ86666New features contained in this PTF ( Fix Level 6.1.0.250)
  • Support for SIP Registration - provides support for the SIP registration method described in RFC 3261.
  • New VoIP Signalling - Inbound Call Channel Allocation Method. A new Inbound Call Channel allocation option called "Allocate calls for D2IS" has been added to system configuration to control the channel used for DTNA based calls. This option is for use when using the Genesys-supplied D2IS custom server in a behind-the-switch Genesys Framework implementation.

For further information on the Fix Pack 2 features, please refer to the following article:
48000984726-blueworx-voice-response-for-aix-v6-1-fix-pack-2
IZ86714This fix overcomes a possible VOIP yellow alarm 29805 error (VOIP SIP signalling process Internal Warning / Failed to create new callProvider object) which then leads to a failure to handle all subsequent inbound and outbound VOIP calls until WVR is restarted. Also fixed is a possible 29806 error (VOIP signalling process call state machine error / Could not add FINAL_RESPONSE tag to SL_CALL_DISCONNECT_IND: Too big) which can occur during a VOIP blind transfer.
IZ80221Fixes an issue where VoIP error 29805 is seen during call transfer with function handle_timer_expired and message 'connid not found'. This was observed when using blind transfers.
IZ80223Fixes an issue where the outgoing SIP ACK message in response to a 200 OK (call connected) message was being sent to the wrong IP Address in a multiple proxy system. This prevented the outgoing call from being established, causing an outbound call failure.


Internal Defect fix

  • Remove unused semaphores from VoIP/SIP that were leaking.

 





Fix Level 6.1.0.222 

Fix release date: 1 Apr 2010
Status: Preventative Maintenance
A fix is available: Obtain the fix for 6.1.0.222



APARDescription
IZ73011This fix overcomes error 29805 (VoIP SIP signalling process Internal Warning / Could not convert host address) for outbound VOIP calls when an alias address rather than an explicit ip address is set in the TO_HDR tag. Previously only outbound calls with an explicit target host address set by the application could be established.
IZ70300This fix modifies the behaviour of a VOIP/SIP blind transfer if the called third party fails to answer (a timeout occurs waiting for a NOTIFY/200 SIP message). The Transfer Call action now returns SL_REPLY_NO_ANSWER instead of SL_REPLY_OUTBOUND_LINE_PROBLEM. After terminating the transfer (with TerminateCall action) an application transfer retry should behave as expected without generating a 29808 error (VOIP signalling process trunk state machine error / Could not get trunk initial state from the trunk SIT).
IZ70302Fixed a problem in the construction of the 200 message in response to an incoming INVITE. The 200 media attributes can be incorrect if the last attribute present in the INVITE happens to be rejected. For example if the INVITE asks for audio and video. This was causing the video to be rejected (correctly) followed by the video being rejected a second time (incorrectly) and the audio being
ignored (also incorrectly).

In the failing case, the invite message would have included content like this when viewed in a network trace:

Content-Length: 210

v=0
o=user1 53655765 2353687637 IN IP4 9.146.171.66
s=-
c=IN IP4 9.146.171.66
t=0 0
m=audio 6000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
m=video 30000 RTP/AVP 34 99
a=rtpmap:34 H263/90000
a=rtpmap:99 H264/90000
IZ60570This PTF fixes a core dump in the DTNA code along with improvements to the DTMF detection.