The following is a complete listing of fix updates for Blueworx Voice Response 7 for AIX, 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 latest fix updates for Blueworx Voice Response for AIX.
Fix Level 7.0.0.21
Fix release date: 17 Apr 2025
Status: Current
Download: BVR.7.0.0.21.tar.Z
| Ticket# | Update Details |
| 220072 | There is a header value (tag) limit of 256 characters. We build the "Replaces" header by concatenating "Call-ID", "To" tag and "From" tag. This can create a "Replaces" which is longer than 256 characters. This causes a buffer overwrite and various problems. The resolution is to increase the MAX_URI_LEN from 256 to 320 characters. |
Fix Level 7.0.0.20
Fix release date: 08 Mar 2023
Status: Current
Download: BVR.7.0.0.20.tar.Z
This Fix Update provides Db2 V11.5 support for BVR V7 for AIX. For details of this feature, please refer to the following Knowledge base article:
BVR V7 for AIX support for Db2 V11.5
Fix Level 7.0.0.19
Fix release date: 18 Oct 2022
Status: Current
Download: BVR.7.0.0.19.tar.Z
| Ticket# | Update Details |
| 293052 | Fixed a VOIPL3_SIP core dump occuring by adding a null check. |
Fix Level 7.0.0.18
Fix release date: 08 Apr 2022
Status: Current
Download: BVR.7.0.0.18.tar.Z
| Ticket# | Update Details |
| 276305 | Fixed 21006 error occurring from fetch. |
Fix Level 7.0.0.17
Fix release date: 17 Sep 2021
Status: Current
Download: BVR.7.0.0.17.tar.Z
| Ticket# | Update Details |
| 6802 | Fixed the code so VOIPL3_SIP doesn't core dump that previously occurred 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 7.0.0.16
Fix release date: 23 Mar 2021
Status: Superseded
Download: BVR.7.0.0.16.tar.Z
| Ticket# | Update Details |
| 6757 | Fixed 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. |
Fix Level 7.0.0.15
Fix release date: 05 Mar 2021
Status: Current
Download: BVR.7.0.0.15.tar.Z
| Ticket# | Update Details |
| 5097 | Fixed a problem where long DTMFs are reported twice by BVR. |
| 5833 | Fixed playing audio during a trombone call. |
| 6192 | Fixed a problem where the state table action RecordVoiceMessage didn't work and BVR error 700 was logged. |
| n/a | Fixed a problem where the vm_integrity tool could not find compressed voice message files in BVR. |
| n/a | Fixed a import problem with VoiceMessagingSample.imp so now imports without any errors being logged. |
Fix Level 7.0.0.14
Fix release date: 18 Aug 2020
Status: Superseded
Download: BVR.7.0.0.14.tar.Z
| Ticket# | Update Details |
| 3994 | Fixed an issue where processing CANCEL immediately after a BYE caused a VOIPL3_SIP race condition, eventually ending in a core dump. |
Fix Level 7.0.0.13
Fix release date: 28 Feb 2020
Status: Superseded
Download: BVR.7.0.0.13.tar.Z
| Ticket# | Update Details |
| 1810 | Prevent customer added tasklist.data entries from being ignored by adding support of deprecated entry types in tasklist.data after migration from V6.1 to V7. |
| 1814 | Fixed 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 7.0.0.12
Fix release date: 27 Sep 2019
Status: Superseded
Download: BVR.7.0.0.12.tar.Z
| Ticket# | Update Details |
| 1766 | Fixed an issue that prevented VXML fetchaudio from playing. |
| 1777 | Fixed an issue with the OAMEXEC executeable writing spurious error messages during BVR start up similar to the following: |
Fix Level 7.0.0.11
Fix release date: 14 Aug 2019
Status: SupersededCurrent
Download: BVR.7.0.0.11.tar.Z
| Ticket# | Update Details |
| 1552 | Updated AMD to better detect beeps and voice and ignore small spikes/clicks of audio. |
| 1708 | Fixed AMD custom server errors that caused AMD to core dump. |
| 1728 | Fixed issue with channels not being visible in System Configuration when upgrading to BVR 7. |
| 1739 | Fixed a BVR migration problem, that would falsely report a Db2 level wasn't installed, by checking the contents of $SYS_DIR/db2/db2level for db2_10_01. |
Fix Level 7.0.0.10
Fix release date: 28 Jun 2019
Status: Current (partly superseded)
Download: BVR.7.0.0.10.tar.Z
| Ticket# | Update Details |
| 1589, 1663, 1664 | Three VoIP parameters were added to the parameter group in BVR and can be found under Configuration->System Configuration->VoIP SIP Signalling:
|
| 1669 | Fixed an issue with the bvr_lsi executeable writing spurious warning messages during deviation of an AIX system ID similar to the following: |
| 1672 | Fixed a rare race condition that could cause VOIPL3_SIP to core in certain circumstances. |
Fix Level 7.0.0.9
Fix release date: 15 May 2019
Status: Superseded
Download: BVR.7.0.0.9.tar.Z
This Fix Update provides DB2 V11.1 support for BVR V7 for AIX. For details of this feature, please refer to the following Solutions article:
BVR V7 AIX support for Db2 V11.1
Also the following issue has been fixed:
| Ticket# | Update Details |
| 1472 | Fixed an issue where by the greetings and audio name associated with a subscriber were not deleted when the subscriber is removed from the system. |
Fix Level 7.0.0.8
Fix release date: 10 May 2019
Status: Partly Superseded (not SpeechClient)
Download: BVR.7.0.0.8.tar.Z
| Ticket# | Update Details |
| 1440 | Fixed the behaviour of a SIP transfer, when previously if a NOTIFY was received before 202 Accepted, it would cause the call to hang up, now during this scenario, it continue with the transfer as normal. |
| 1509 | Fixed an SIP issue when a CANCEL request failed previously 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). |
Fix Level 7.0.0.7
Fix release date: 22 Nov 2018
Status: Superseded
Download: BVR.7.0.0.7.tar.Z
| Ticket# | Issue | Resolution |
| N/A | No 3270 Server support. | Added support for 3270 Servers on BVR V7 for AIX via Communications Server for AIX V6.4. For more details, refer to the Blueworx 7 AIX InfoCenter. |
Fix Level 7.0.0.6
Fix release date: 14 Sep 2017
Status: Superseded
Download: BVR.7.0.0.6.tar.Z
| Ticket# | Issue | Resolution |
| N/A | No MRCPv2 support | Added support for MRCPv2 on BVR V7 for AIX. For more details, refer to the Solutions article: |
| T1131 | Errors 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 state table. | Fixed a potential error_id 1201, error_id 1 that can occur when using VXML if a SIP call is cancelled before BVR has finished it's answer sequence. |
Fix Level 7.0.0.5
Fix release date: 20 Dec 2017
Status: Superseded
Download: BVR.7.0.0.5.tar.Z
| Ticket# | Issue | Resolution |
| N/A | No BRM license support. | Add support for BRM licensing server. For more details, refer to the Solutions article: |
| N/A | No SIP disconnect cause code within the state table API when an outbound call from BVR fails to connect. | BVR has been enhanced to provide the SIP disconnect cause code within the state table API when an outbound call from BVR fails to connect. BVR indicates that the cause value is available by setting SV176 to 1 after the state table MakeCall action fails. If SV176 is set to 1 then the disconnect cause code is present in SV175. If SV176 is not set to 1 then SV175 will not contain a valid cause code. |
| 1061 | INVITEs 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. |
| 1460 | A 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. |
Fix Level 7.0.0.4
Fix release date: 20 Dec 2017
Status: Superseded
Download: dirTalk.VOIP_SIP.7.0.0.4.bff
| Ticket # | Problem | Resolution |
| 1402 | After 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 |
Fix Level 7.0.0.3
Fix release date: 30 Aug 2017
Status: Superseded
Download: BVR.7.0.0.3.tar.Z
New fixes/features contained in Fix Level 7.0.0.3:
| Ticket# | Problem | Resolution |
| N/A | Unable 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 Solutions article: |
| 1117 | No answer machine detection available in 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 |
| 1278 | No Call Detail Record support for calling IP address is available in BVR. | Add support for calling IP address on the Call Detail Records. |
| 1290 | Calls to T1 channels configuration cause problems on CTI setup. | Add in an inbound and outbound channel allocation method to honor the T1 channel limits (24) and also the license limits. This is specifically for use with CTI and any code that uses the trunk/channel to calculate a channel index. |
Fix Level 7.0.0.2
Fix release date: 25 Jul 2017
Status: Superseded
Download: BVR.7.0.0.2.tar.Z
Important: After installing this Fix Update (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 7.0.0.2
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 the following article:
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 7.0.0.2:
| Ticket# | Problem | Resolution |
| 1048 | An 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. |
| 1186 | User 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. |
| 1286 | Opening an Application using the BVR GUI displays "FolderCreateResourceTab", instead of State Table, Custom Server, etc. | Fixed to display the correct object headings. |
| 1286 | Running restoreDT on BVR 7 using file output of saveDT run on BVR 7 produces the following error:DATA UPGRADE FAILED: Error During: | Fixed the restoreDT script to restore objects correctly. |