Fix release date: 07 Jun 2018
Status: Current



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 development platform :
  • 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 development platform:
  • BVR now ignores unknown vendor properties.
  • BVR now accepts short property names.


Download information


The Fix Update for this issue is available on the Blueworx FTP site:


https://blueworx.hostedftp.com/files/path/Fix+Center/BVR610/BVR.6.1.0.526.tar.Z


This update may require requisite Fix Update files to be installed at the same time, and are available on our Blueworx FTP site as a cumulative collection of all Blueworx Voice Response Fix Updates from 6.1.0.500 - 6.1.0.519, and also as individual Fix Update files for the latest updates.


https://blueworx.hostedftp.com/files/path/Fix+Center/BVR610/BVR610.ML5.fix500-519.tar.Z