The following is a complete listing of updates for Blueworx Voice Response 7 for Linux, and the fixes included within them, with the most recent updates at the top.
7.39
- Description and Max Call Duration for Application Mappings
- RTP Mode field for SIP Proxies
- Fetch Timeout and Fetch Warning Timeout for Applications
For more information see the following:
BAM Command Line Utility Application Mappings Panel
BAM Command Line Utility Applications Panel
Release: 7.39.4
Release date: 10 September 2025
New fixes contained in 7.39.4
| Issue # | Problem |
|---|---|
| 629 | Update CCXML session id with time |
| 630 | Fix priority/weighted lists |
Release: 7.39.3
Release date: 1 July 2025
New fixes contained in 7.39.3
| Issue # | Problem |
|---|---|
| 621 | Add thread dump on shutdown |
| 622 | Fix BAM outbound application creation |
| 623 | Update IAM timeouts |
| 625 | Call dispatcher in bvr -m |
| 626 | Add epoch time into session.fullid to make it unique between restarts |
Release: 7.39.2
Release date: 6 June 2025
New fixes contained in 7.39.2
| Issue # | Problem |
|---|---|
| 620 | Fix NPE when making outbound ccxml on 7.39.1 |
Blueworx Voice Response 7.39.1 adds support for SIP WWW authentication credentials. For more information see the following:
SIP WWW-Auth Credentials Panel
Release: 7.39.1
Release date: 17 April 2025
New fixes contained in 7.39.1
| Issue # | Problem |
|---|---|
| 610 | Secure URI display base path |
| 611 | Add WWW-Authenticate credentials |
| 613 | bvrProblem error with two versions of postgresql |
| 615 | Missing last bits of call recording |
| 616 | ZKNode 0.0.0 versions deleted |
| 617 | BAM outbound application field error |
| 618 | BRM ZooKeeper node race condition |
| 619 | VXML NPE setting fetch timeout |
Release: 7.39.0
Release date: 10 March 2025
New fixes contained in 7.39.0
| Issue # | Problem |
|---|---|
| 591 | Add bvr --terminate command |
| 593 | CCXML assign VXML no call exception |
| 598 | bvrProblem command does not collect the postgresql files |
| 599 | Full SIP URI ignores SIP Proxy Group |
| 600 | Add support to change outbound secure call |
| 601 | Add AMD changes |
| 602 | Allow audio_submit to write to filesystem |
| 604 | Control secure logging at account level |
| 605 | App mapping description field |
| 606 | Improved fetch timeouts |
| 607 | Max call duration configuration |
| 608 | Support call recording to disk rather than memory |
| 609 | Remove dtna 3.10 |
7.38
Blueworx Voice Response 7.38 adds support for Call Recording. For more information see the following:
Release: 7.38.3
Release date: 27 November 2024
New fixes contained in 7.38.3
| Issue # | Problem |
|---|---|
| 572 | Gradle fails to install on clean build |
| 580 | HTTP API attributes |
| 584 | Application log left open |
| 586 | HTTPProxyGroupId NPE for VXML prepared from CCXML |
| 587 | Class cast exception with tel URI |
| 589 | getIAMData hangs |
| 590 | Increase CSeq after 407 INVITE |
| 594 | Amazon Polly variants update |
| 595 | TTS parameters not setting on Google TTS |
| 596 | Double CALL_FINISHED |
Release: 7.38.2
Release date: 7 October 2024
Blueworx Voice Response 7.38.2 improves the HTTP API status by providing more information. For details, refer to the following:
New fixes contained in 7.38.2
| Issue # | Problem |
|---|---|
| 528 | Call dispatcher race condition |
| 545 | BVRCommand race condition |
| 561 | VXML2 stuck reco and TTS |
| 566 | Stop SysV on systemd machines |
| 575 | NPE quiesce when BRM down |
| 583 | Improve HTTP status API |
| 585 | CCXTeleMgr timing window |
Release: 7.38.1
Release date: 10 September 2024
Blueworx Voice Response 7.38.1 adds support for BVR Capture. For more information see the following:
Capturing Audio and/or SIP Flow of Calls
Release: 7.38.0
Release date: 20 August 2024
New fixes contained in 7.38.0
| Issue # | Problem |
|---|---|
| 571 | PCI - Implement support for encryption of VXML variables in memory |
| 576 | STT does supply record audio |
| 578 | Support call recording |
| 579 | VXML DTMFs only does nothing |
7.37
Blueworx Voice Response 7.37 adds support for encrypted configuration (bvr_secconfig). For more information see the following:
Release: 7.37.0
Release date: 24 April 2024
New fixes contained in 7.37.0
| Issue # | Problem |
|---|---|
| 507 | Generic cloud license (no system id check) |
| 570 | Support encrypted configuration (bvr_secconfig) |
| 574 | Fix CDR duration race condition |
7.36
Blueworx Voice Response 7.36 adds support for DTMF on Google DialogFlow CX, and for CCXML Merge on Call Transfer. For more information on these additions, see the following:
Integration with Google Dialogflow
Using <merge> to Hand Off Calls
Release: 7.36.1
Release date: 12 March 2024
New fixes contained in 7.36.1
| Issue # | Problem |
|---|---|
| 567 | Incorrectly restarting Watson assistant |
| 568 | No reuse connection for Watson IAM |
| 569 | DialogTransfer/bvr.transfer CCXML event has no source |
| 573 | No reset timeout fetching URIs |
Release: 7.36.0
Release date: 20 February 2024
New fixes contained in 7.36.0
| Issue # | Problem |
|---|---|
| 547 | bw_no_input_timeout numeric error |
| 559 | Provide postgresql prereq on AL2023 |
| 563 | Fix deadlock in HTTP server |
| 564 | Turn off faulty cache auto deleter |
7.35
Blueworx Voice Response 7.35 adds support for ElevenLabs Text To Speech along with concurrency updates to Java and any included libraries. For more information on ElevenLabs TTS support see the following:
Parameters for TTS_ELEVEN_LABS Call Feature
Release: 7.35.1
Release date: 21 November 2023
New fixes contained in 7.35.1
| Issue # | Problem |
|---|---|
| 560 | Improve websocket handling |
Release: 7.35.0
Release date: 16 November 2023
New fixes contained in 7.35.0
| Issue # | Problem |
|---|---|
| 553 | ElevenLabs TTS support |
| 555 | Make sure DTNA uninstalls when Blueworx is updated |
| 557 | Call_Feature_Group trigger incorrect - this stopped both adding and removing a call feature from a call feature group |
| 558 | Google TTS parameters not used in caching |
7.34
Blueworx Voice Response 7.34 adds support for a new Virtual Assistant call feature type to connect to Nu Workforce. For more information see the following:
Parameters for VIRTUAL_ASSISTANT_NU_WORKFORCE Call Feature
Release: 7.34.1
Release date: 26 September 2023
New fixes contained in 7.34.1
| Issue # | Problem |
|---|---|
| 550 | Uninstall/update doesn't remove DTNA first |
| 551 | Add call status to trace |
| 552 | TraceMessage toJSON assume session |
Release: 7.34.0
Release date: 14 September 2023
New fixes contained in 7.34.0
| Issue # | Problem |
|---|---|
| 538 | Dynamic Watson agent ID |
| 541 | Normalise local SIP UR |
| 543 | Detect call feature groups changing |
| 544 | Fix and support silence in VXML record tag |
7.33
Blueworx Voice Response 7.33 adds Rocky Linux to our list of supported OS's. For more information see the following:
Release: 7.33.0
Release date: 12 June 2023
New fixes contained in 7.33.0
| Issue # | Problem |
|---|---|
| 540 | DTNA crash large secure packets |
7.32
Blueworx Voice Response 7.32 expands our OS support capabilities by adding a new user space DTNA (streaming module) as well as the original kernel module. This seamlessly allows the Blueworx Platform to run on any new kernel versions that are released for our supported OS's.
The update also adds in the capability to include SIP messaging in the application call logs. For more information see the application_call_logging parameter here:
Release: 7.32.0
Release date: 09 May 2023
New fixes contained in 7.32.0
| Issue # | Problem |
|---|---|
| 539 | Fix postuninstall set_blueworx_env |
| 537 | VXI traces null characters |
| 535 | Unable to set SIP proxy caller id to none/null |
| 534 | Classpath set to invalid directory exception |
| 533 | Uninstall doesn't clean up bash profile |
| 532 | Add support for sip in call logs |
| 531 | Remove user/kernel not found warning |
| 529 | DTNA formats trace incorrectly |
| 527 | T302602 - Attempting to check zookeeper null path |
| 526 | T302602 - Outbound API timeout event set to CCXML |
| 525 | T000845 - WARNING Remote party rejected on hold request |
| 524 | Outbound call assumes app mapping works |
| 523 | Use correct DNIS |
| 522 | Private cache files race condition with end of call |
7.31
Blueworx Voice Response 7.31 adds support for HTTP proxies to the platform. HTTP proxies can be attached to various call features to allow the platform to make outbound http requests via the prxy rather than directly to the associated resource. For more information see the following:
Release: 7.31.0
Release date: 30 January 2023
New fixes contained in 7.31.0
| Issue # | Problem |
|---|---|
| 512 | T296355 - Dialog prepare retrieves null conference id |
| 514 | Add proxy_tls into next release |
| 515 | NumberFormatException from CCXML basichttp send if application exits. |
| 516 | T299009 - Watson STT timesout from BYE |
| 517 | T298831 - bvrProblem causing java core |
| 518 | SIP Proxy OPTIONS never comes back |
| 519 | Improve fetcher threads |
| 520 | BWFetcher doesn't timeout on connect |
| 521 | NoResourceError throw in field with transfer |
7.30
- Updates to VoiceXML to allow standalone use of an STT call feature within a VoiceXML application
- Additional parameters on calls to an IBM Cloud STT call feature
- Dynamic configuration for Watson Virtual Assistant
Add support for STT usage in VoiceXML
Blueworx Voice Response 7.30 adds the ability to use an STT call feature directly within a VoiceXML application. This allows a VoiceXML application to connect to Speech To Text engines (STT) as an alternative to traditional MRCP ASR speech providers. For more information see the following:
Using Speech To Text (STT) engines
Updates to the IBM Cloud STT call feature.
The IBM Cloud STT call feature now supports dynamic configuration for several STT parameters. For more information see the following:
IBM Cloud Speech To Text (STT) supported parameters
Dynamic configuration for Watson Virtual Assistant.
It is now possible to dynamically set the IBM Watson Assistant service URL, assistant ID and API key within a VoiceXML application to override the values configured for the call feature. For more information see the following:
Watson Virtual Assistant Specifics
Release: 7.30.0
Release date: 29 September 2022
New fixes contained in 7.30.0
| Issue # | Problem |
|---|---|
| 448 | Virtual Assistants will tight loop without actually sending anything to assistant if "transcript" is set and prompt has bargein set to "true" |
| 492 | CDRs need to include account name as well as account ID. |
| 493 | Add uniqueness constraint for Names associated with configurable items in BAM |
| 496 | Support splitting STT and VA steps |
| 497 | Watson STT updates. |
| 498 | Watson STT warning about access_token |
| 501 | DTMF 0 detected on first call into BVR even when not pressed. |
| 502 | Non master BRM returning 123 for status |
| 503 | XPO: Unsupported audio format causes fetch failure. |
| 504 | Fix 404 ERROR reporting on Watson ending race condition |
| 508 | ArrayIndexOutOfBoundsException from translateHeadersToProtocol() method |
| 510 | Watson STT add support for additional parameters |
7.29
- Support for Google Dialogflow CX in addition to the existing support for Dialogflow ES
- Updates to the Google STT call feature
Add support for Google Dialogflow CX
Blueworx Voice Response 7.29 adds support for integration with Google Dialogflow CX Virtual Agents. For more information see the following:
Dialogflow Virtual Assistant Specifics
Updates to the Google STT call feature.
The Google STT call feature now supports dynamic configuration for several Google STT parameters. For more information see the STT parameters section of the following page:
Dialogflow Virtual Assistant Specifics
Release: 7.29.0
Release date: 27 July 2022
New fixes contained in 7.29.0
| Issue # | Problem |
|---|---|
| 400 | BVR StreamingEngine waitingCalls leak |
| 456 | Documentation generation does not output config sections in a sensible order (e.g. alphabetical) |
| 466 | BUILD: Gradle license report plugin version causes build issues, force to 1.17 in settings.gradle |
| 489 | PlayStreamer TimerTask already cancelled |
| 490 | Add content types to VXIContext for VoxGen SpeechWizard |
| 491 | bam should display names in place of numbers when viewing/changing/etc. |
| 494 | Fix incorrect 477 merge (STT websockets Timer Already Cancelled issue) |
| 495 | Watson STT stt_parms ignored |
| 467 | BUILD: Jenkins create output dirs not creating the base output dir first, build fails |
7.28
- Add Support for sending events to CCXML applications through the HTTP API
- Extend the HTTP API to include a status request
Add Support for sending events to CCXML applications through the HTTP API
Blueworx Voice Response 7.28 adds the capability to allow arbitrary CCXML events to be sent via the HTTP API. This allows the application developer to control call flow from outside of the CCXML application environment, for example to allow an agent to trigger a payment IVR for a conferenced caller by sending an API request through a desktop button. For more information see the following:
Add Support for sending events to CCXML applications through the HTTP API
The HTTP API now includes a status API that can be used to query status of the Blueworx Platform. Currently supports returning information relating to calls and BVR status. For more information see the following:
Release: 7.28.0
Release date: 5th April 2022
New fixes contained in 7.28.0
| Issue # | Problem |
|---|---|
| 477 | Websocket get stuck in CLOSE_WAIT |
| 478 | NPE on playDTMF |
| 479 | Custom header overridden by presentation address |
| 480 | Fix CCXML HTTP encode |
| 481 | Caller ID being SIP user |
| 482 | Send DTMF to dialog in conference |
| 483 | doBlindTransfer did not complete properly |
| 484 | Vendor properties not going to ASR |
| 485 | Single BRM looses connection |
7.27
- Add support for conferences in CCXML
- Extend VXML functionality to allow DTMFs to be played
- Updates to the outbound API
Add support for conferences in CCXML
Blueworx Voice Response 7.27 adds support for the CCXML conference tag. This enables the platform to support conferences of up to 10 entities, connections or dialogs. For more details see the following:
Extend VXML functionality to allow DTMFs to be played
The Blueworx Voice Response VXML interpreter now includes the ability to play a string of RFC2833 DTMFs using the VXML value element. See here for more details:
Updates to the Outbound API
The outbound API HTTP GET method now allows headers and hints to be sent with the request.
For further information see the following:
Release: 7.27.0
Release date: 25th November 2021
New fixes contained in 7.27.0
| Issue # | Problem |
| 474 | VXML submit with no fields/namelist npe |
| 473 | Unnecessary warning about no notify |
| 472 | CCXML cache invalid on update |
| 470 | DTNA crash if RTP packet incomplete |
| 468 | Proxy config causes NPE |
| 465 | basichttp incorrectly sends from all BRMs |
| 464 | Option ping fails |
| 463 | transfer_sample.ccxml exits sometimes |
7.26
- Add support for Amazon Linux 2
- Updates support for Centos to include version 8.4
- Add support for HTTP GET to the Outbound API
Add support for Amazon Linux
Blueworx Voice Response 7.26 adds support for Amazon Linux 2 https://aws.amazon.com/amazon-linux-2/. In order to install on Amazon Linux 2 an alternative yum repository file is required, for further details see the following:
Installing the Blueworx Yum repository on Amazon Linux 2
Updates support for Centos to include version 8.4
Blueworx Voice Response 7.26 now supports installation on Centos 8.4
Add support for HTTP GET to the Outbound API
The outbound API now supports HTTP GET as well as HTTP POST.
For further information see the following:
Release: 7.26.0
Release date: 3rd August 2021
New fixes contained in 7.26.0
| Issue # | Problem |
| 398 | Watson Assistant + Dialogflow do not send the correct event back to CCXML in the case that they fail (error.dialog and error.dialog.notstarted) |
| 423 | VXML prefetches raise WARNING, then when doc is actually fetched another WARNING is raised. prefetch should not raise a WARNING |
| 424 | Make the Watson Assistant HTTP request timeout configurable |
| 425 | Playing recorded audio (application.lastresult$.recording) doesn't work if audio URIs are redacted |
| 426 | NullPointerException on setCallCodec if createsession CCXML tries to start a dialog before call is established (e.g. if in call.progressing) |
| 427 | Enhancement - Create new trace component for VXML_DOC just to log VXML document (on INTENSIVE) |
| 428 | Enhancement - Don't redact failed fetches (configurable in bvr.config) |
| 429 | Can't fetch Waveform-URI if call hangs up - should fetch immediately in MRCP code to remove race condition |
| 430 | Update to Java 16 |
| 431 | Call feature status change trace should report call feature ID |
| 434 | Add support for user_id in Watson Assistant |
| 435 | Cache not tracing full URL |
| 436 | VXML Submit + Subdialog defaulting to POST |
| 437 | Fetcher traces HTTP RC twice and says "null" if response message is not set |
| 438 | Cache file deleted during fetch can cause BVR to send If-Not-Modified-Since header, resulting in 304 but no cached entry to use |
| 439 | TraceID T003761 not honouring URI redaction |
| 440 | URI with space at the end fails to parse - this is not a legit URI but can happen so we should trim the URI string before parsing |
| 441 | Trace - Call rejected trace line (T003326) doesn't include ANI + DNIS. Also the colon is in the wrong place. |
| 442 | MRCP OPTIONS ping can NPE if endpoint doesn't give MRCP SDP |
| 444 | Currency - Update libraries to latest levels |
| 445 | CCXML Log lines being repeated (since call logs now also go to trace as of 7.25) |
| 446 | Virtual Assistant objectToJson doesn't correctly unassign variables (set to null), can cause issues if unsetting transcript so STT can be used again |
| 447 | "Starting parse" and "Finished parse, took ..." coming out in bvr.out |
| 449 | Virtual Assistant does not set application.lastresult$.utterance in the case of a nomatch |
| 450 | REFERing to tel: URL without + fails as "not a valid SIP URL" |
| 451 | session.connection.protocol.sip not populated in VXML |
| 454 | Support for AWS Linux |
| 455 | Add parameter to block CCXML + VXML logging |
| 457 | presentation_address in [network] config not applying as default for sip_presentation_address, causes NPE |
| 458 | TTS cache not honouring max age etc. config in bvr.config |
| 459 | Prepared dialogs without calls can leak VXML2 threads |
| 460 | Add support for GET outbound API and full CCXML session id |
| 461 | CURRENCY - Add support for CentOS 8.4 |
| 462 | References to cache entry metadata still in memory after removal, causes memory leak |
7.25
- Backup URI for applications
- Updates to the BVR quiesce command
- Support for stale-if-error when fetching resources
- Updates to time related configuration options and inclusion of a CCXML initial fetch timeout configuration option
- Support for STT confidence threshold and confidencelevel support for VXML Virtual Assistants
Backup URL for applications
Blueworx Voice Response 7.25 adds an optional backup application URI to voice applications. This backup URI is used if the primary URI can not be resolved.
For further information see the following:
BAM Command Line Utility Applications Panel
Updates to the BVR quiesce command
The bvr -q quiesce command has been updated to provide more detailed platform information while it is being executed. This change also includes a new configuration option, quiesce_default_timeout to control how long the quiesce waits before forcibly terminating BVR.
For further information see the following:
Support for stale-if-error when fetching resources
Blueworx Voice Response 7.25 now supports stale-if-error checking as defined in RFC5861. This allows the Blueworx Platform to use an expired, cached resource even if the webserver is not accessible.
There are two new configuration options for each resource category that control this behavior, default_max_stale and default_stale_if_error. For further information see the following:
VXML Cache Configuration Options
CCXML Cache Configuration Options
AUDIO Cache Configuration Options
TTS Cache Configuration Options
Updates to time related configuration options and inclusion of a CCXML initial fetch timeout configuration option.
Time related configuration options throughout the platform have been updated to allow the use of human readable times, e.g. 1 hour or 5 minutes. We have also added a new configuration option, fetch_timeout, to control the default fetch timeout for CCXML applications.
For further information see the following:
Virtual Assistant integrations in BVR now support setting an STT confidence threshold. VXML Virtual Assistants now also support the confidencelevel property.
CCXML Integration with IBM Watson Asssitant
CCXML Integration with Google Dialogflow
VXML Virtual Assistant Integrations
Release: 7.25.1
Release date: 18th May 2021
New fixes contained in 7.25.1
| Issue # | Problem |
| 390 | BVR SIP code always looking up DNS records remotely, not checking hosts file first |
| 399 | CCXML Watson + Dialogflow to support Call Feature definitions |
| 402 | VXML Virtual Assistant integration has no way to access STT recording |
| 404 | Feature - Ability to flush SIP DNS cache live |
| 406 | MRCPv2 has explicitly predefined "Cause" parsing meaning we error if the MRCPv2 server sends us an unexpected cause |
| 407 | VXML menu with no prompts causes BVR to infinite loop |
| 408 | HEAD check doesn't honour VXML fetch_timeout |
| 409 | Feature - Ability to specify fetch timeout on dialogstart |
| 410 | Human readable time values can be multiplied unnecessarily in some circumstances |
| 411 | VXML2 initial document fetch not honouring fetch_timeout config option |
| 412 | BVR is too strict when parsing MRCPv2 headers that are supposed to be quoted (e.g. Completion-Reason) |
| 413 | sessionLog doesn't go to trace as well |
| 415 | Too much trace output for CACHE when set to TRACE |
| 416 | MRCPv2 not setting default presentation address if [mrcp] section doesn't exist |
| 417 | MRCPv2 and SIP are using Streaming presentation addresses from [[network]] config |
| 418 | Call IDs missing from various trace points in CACHE and MRCP |
| 419 | Caller and Called ID information is transposed in BVR call record. |
| 420 | NullPointerException when external voice grammar specified in srcexpr |
| 421 | BVR doesn't output content of Warning header if present when an outbound call is rejected |
| 422 | No site document for ja_JP |
Release: 7.25.0
Release date: 11th May 2021
New fixes contained in 7.25.0
| Issue # | Problem |
| 366 | Some Watson STT URL parameters are not supported, and should be usable with the stt_parms structures |
| 374 | T6593 - VXML raises "WARNING doBlindTransfer did not complete correctly" if the call is hung up while prompts in same block as transfer are playing |
| 375 | NPE if using SIPREC |
| 376 | siprec calls fail if endpoint fails to provide labels in its SDP response |
| 377 | All cache going to account ID -1 |
| 378 | idle_timeout in CCXML uses timer but doesn't purge cancelled tasks, could cause high memory usage on high volume systems with a long idle timeout |
| 379 | Expired cache entry gets permanently set to expired, refetches every time |
| 380 | CCXVRBEWorker.exec() Manager does not exist for the specified ID null |
| 382 | Watson sometimes sees this: HTTP request failed org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 2,300; received: 2,299) |
| 383 | VXML doesn't perform HTTP HEAD check if not subdialog of CCXML, causing BVR not answer call and hang up instead of sending a 404 response |
| 385 | BVR, BAM, BRM, BSM, BDB should not be installable if any blueworx component is running |
| 386 | BVR cache utiliser marking an entry in use blindly adds to list, can result in list full of the same entry |
| 387 | CCXML queue monitor generating threads unnecessarily |
| 388 | WatsonAssistantSession may not send DELETE message in some cases, session may not end |
| 389 | WatsonAssistantSession HTTP requests/responses not being traced against call ID |
| 391 | Call can hang if call ends just before Reco/TTS started by VXML (null signalling means call never set on sig session, never get disconnected event) |
| 392 | Watson TTS doesn't failover if it gets error responses beyond a specific subset (e.g. won't failover on 503) |
| 393 | Watson Assistant virtual assistants can cause deadlock when ending session, blocking a HTTP task queue thread |
| 397 | VXI can get set back to connected after being set to disconnected if initial document's fetch takes a long time |
| 401 | SIP DNS only tries first search suffix from resolv.conf |
| 403 | BVR errors not publishing account ID and application ID to kafka - only on sessionLog |
7.24
- Enhancements to detail provided in CDRs
- Ability to rename Kafka topics
- New MRCP monitor utility
- Support for the latest PostgreSQL releases
CDR updates
Blueworx Voice Response 7.24 adds to the data included in CDRs generated at the end of each call. The updates include a more detailed breakdown of the call feature usage for the call, including detailed information about each call feature type used during the call.
For further information see the following:
Renaming Kafka topics
It is now possible to rename the Kafka topics used by the Blueworx Platform. This allows a greater flexibility when monitoring output from a cluster of servers within a single Kafka environment.
For further information see the Kafka Configuration Options section for each of the Blueworx Platform components in this section:
MRCP Monitor
Blueworx Voice Response 7.24 adds a new monitoring utility to allow Platform administrators to monitor the MRCP message flow as it occurs from the BVR component.
For further information see here:
Release: 7.24.0
Release date: 4th March 2021
New fixes contained in 7.24.0
| Issue # | Problem |
| 344 | Application hangs if MRCPv2 server does not respond to SPEAK request |
| 346 | Store last 5 bvr.out files so startup doesn't wipe it out |
| 347 | VXML2Session not resetting all values (e.g. pendingRecoStopped) causing issues for following session that reuses the instance |
| 348 | TTSCall and RecoCall can send multiple CALL_FINISHED events |
| 349 | Optimisation - MRCPv2 to use pooled threads |
| 351 | T6244 - Failure to lock file in cache does not cause a retry attempt (only tries once) |
| 352 | T6244 - LockableRandomAccessFile.lock exception caused by simultaneous write and get |
| 353 | sips URI does not default to TLS transport |
| 354 | BVR startup doesn't remove duplicate cache entries |
| 355 | SIP NullPointerException from Reco call in rare case where no ApplicationData has been set before disconnect |
| 356 | BVR command exception can cause future commands to become unresponsive as thread is taken out |
| 357 | CCXML fetching doesn't use cookies set in responses on future requests + needs to pass them to subdialogs |
| 358 | CCXML Watson Assistant and DialogFlow sessions do not end running threads at end of application - memory leak |
| 359 | Optimisation - Various AppSessions to use dynamically allocated pooled threads when needed, rather than thread per session |
| 362 | If request for an IAM token fails, it permanently stays in a failed state |
| 363 | T6365 - Watson Assistant ending when a call is over can cause WARNINGs to appear incorrectly |
| 364 | Call Feature Failover should try unavailable call features if all matching features are currently unavailable |
| 365 | Log current active calls per account/app/mapping in BRM when a new call is created |
| 367 | CCXML - Potential race condition can cause thread to misreport time taken, causing unnecessary spawning of new threads |
| 372 | Occasional "Exception in thread "BVR status" java.lang.NullPointerException" in bvr.out on startup |
7.23
- Outbound API
- Allow/Deny list to control outbound dialing
Outbound API
Blueworx Voice Response 7.23 adds a new HTTP API to the platform that can be used to initiate outbound calls from the BVR component and start arbitrary VoiceXML And CCXML applications.
For further information see the following:
HTTP API Configuration Options
BAM Command Line Utility HTTP API Keys Panel
Allow/Deny list to control outbound dialing
It is now possible to control the phone numbers that can be used when making outbound calls. This is achieved using the new Allow/Deny list functionality introduced in Blueworx Voice Response 7.23. The Allow/Deny list is checked whenever the platform is used to make an outbound call.
For further information see the following:
BAM Command Line Utility Outbound Allow/Deny List Panel
Release: 7.23.1
Release date: 19th Jan 2021
New fixes contained in 7.23.1
| Issue # | Problem |
| 341 | T5629 - Trace system can potentially lock up |
| 342 | T5945 - CCXML fetches fail with ClassCastException if recordutterance or DialogFlow were ever used beforehand |
| 343 | MRCPv2 endpoint status check (OPTIONS ping) not told to stop during BVR shutdown causing unexpected error messages |
| 345 | Watson Assistant CCXML Applications broken in 7.23.0 |
Release: 7.23.0
Release date: 15th Dec 2020
New fixes contained in 7.23.0
| Issue # | Problem |
| 336 | Null pointer exception handling non MRCPv2 sessions |
| 337 | Default user_sources is incorrectly set to Request_URI, now changed to To header |
| 338 | BRM doesn't create an initial zookeeper/data_dir directory |
| 340 | CCXML creates excess exceptions from missing files |
7.22
- Call Feature Failover Support.
- Arbitrary Vendor specific Parameters on MRCP RECOGNIZE requests.
- Configurable no_audio_warning in streaming configuration section.
- Configurable dns_retry_interval in sip configuration section.
Call Feature Failover Support
Blueworx Voice Response 7.22 adds functionality to failover between call features to prevent downtime of the Blueworx Platform if an external call feature fails.
This functionality adds the ability to create groups of call features, with associated weights and priorities, and assign those groups to an application. The Blueworx platform keeps track of the status of the call features in a group and will failover between matching call features when there is a failure.
For further information see the following:
BAM Command Line Utility Call Features Panel
Weight and Priority usage in the Blueworx Platform
Arbitrary Vendor specific Parameters on MRCP recognize requests
It is now possible to define arbitrary Vendor Specific Parameters within a VoiceXML application to be sent on an MRCP RECOGNIZE request. This allows the application author to control the MRCP ASR call feature directly, configuring things like extra logging or call recording for ASR tuning.
For further information see the following:
VoiceXML arbitrary MRCP Vendor Specific Parameters
New configration parameters
no_audio_warning in the streaming section of BVR configuration to set the amount of time to wait without receiving packets at the start of a voice call before raising a warning.
dns_retry_interval in the sip section of BVR configuration to set the amount of time to wait before retrying a DNS query if the last attempt returned no results.
idle_timeout in the CCXML section of BVR configuration to set the length of time to wait after a CCXML session has ended all it's calls before exiting the CCXML session. Used to automatically clean up idle CCXML sessions that are not actively handling calls.
For further information see the following:
Streaming Configuration Options
7.22.1
Blueworx Voice Response 7.22.1 adds support for Red Hat Enterprise Linux 7.9 and CentOS 7.9.
Release: 7.22.1
Release date: 02th Dec 2020
New fixes contained in 7.22.1
| Issue # | Problem |
| 334 | BVR can now check multiple "user" sources (eg To: header, Request-URI) |
| 335 | CCXML idle_timeout functionality not working for far end hangup calls |
Release: 7.22.0
Release date: 24th Nov 2020
New fixes contained in 7.22.0
| Issue # | Problem Fixed/Change Made |
| 284 | If the DB connection goes down on BRM it never attempts to reconnect, meaning BAM changes aren't reflected in BRM |
| 304 | BAM doesn't format detail table field values correctly if they are longer than screen width, inserts newlines in the wrong place |
| 305 | CCXML dialogStart request method inverting POST/GET flag, causing BVR to POST when we should GET |
| 306 | CCXML sessions not being <Exit>ed hang around forever - Added a [ccxml] config parameter idle_timeout to automatically terminate CCXML sessions X minutes after all associated calls have hung up |
| 308 | ifixes loaded in via classpath are picked up by startup report but aren't added to classpath if classpath configured with a bad wildcard |
| 309 | T4872 - IBM STT socket connection failures cause applications to end. STT WebSocket connections now have a shorter timeout and retry 3 times |
| 310 | T4871 - VXML VirtualAssistant makeRecoResult NPE |
| 311 | T4871 - Race condition can cause 2 No Input Timers to be started if TTS ends at the same time as the STT gets its result |
| 313 | stdout no longer going to bvr.out etc (so can't get thread dumps) |
| 314 | T4956 BAM - Attaching SIP custom headers to proxies gets stuck in infinite loop |
| 315 | Update bvrProblem to take thread dumps |
| 316 | Potential NPE when deleting cache directories |
| 318 | BVR can't transfer to a non-SIP URI (legitimate scenario if proxy assigned) |
| 319 | T5075 - Cache entries not always being deleted if replaced by newer version |
| 320 | Ensure JVM always provides stack trace on exception |
| 322 | Cache deadlock when cache is full and cleanup process runs |
| 323 | Handle exceptions in ZK exists task |
| 324 | VXML Applications can hang around if hung up before established |
| 325 | Cache - Unique identifiers on duplicate/replaced cache entries not generated efficiently, can conflict |
| 326 | Improve no audio warning - Highlight whether at start of call or middle of call |
| 328 | Cache exception when performing clean-up (when at capacity) |
| 329 | 7.22.0 - General performance improvements |
| 332 | T5215 - ConcurrentModificationException when setting inbound headers in CCXML |
7.21
- Integration with a Dialogflow Virtual Assistant through VXML and CCXML applications.
- Improvements to the Virtual Assistant data structures used by the platform.
- Updates to the SIP proxy support.
- More granularity in configuring call limits.
Virtual Assistant Integration with Dialogflow
Blueworx Voice Response 7.21 adds functionality to allow a VoiceXML application to interact directly with a Dialogflow Virtual Assistant, allowing for a direct alternative to an MRCP speech server for ASR and TTS capability when using VoiceXML. Also included is fuctionality to pass control to a Dialogflow Virtual Assistant from a CCXML application using the CCXML dialogstart transition.
This feature is a continuation of our drive to provide access to multiple AI vendors through all IVR application models in Blueworx Voice Response.
- Can fully replace Nuance/Lumenvox as an ASR provider within VoiceXML.
- Provides full "tier 4" speech capability.
- VoiceXML support allows “what comes next” business logic and managing complex application state to be performed within the VoiceXML application rather than in the Virtual Assistant. Uses a custom grammar format to drive the Virtual Assistant and custom response data from the Virtual Assistant, while still supporting standards compliant VoiceXML.
- CCXML support gives full control of the dialog to the Dialogflow Virtual Assistant whilst allowing call control within the Blueworx Platform.
For further information see the following:
Integration with Virtual Assistants
Dialogflow Virtual Assistant Specifics
Integration with Google Dialogflow
Improve Virtual Assistant data structure format
- There is now a custom_vars structure which is a platform agnostic way to send custom variables to the Virtual Assistant
- context is now considered platform specific as different Virtual Assistant implementations use this differently. It will still behave in exactly the same way as it did for Watson Assistant.
- New variable message_text added, which is a simple way to get the Virtual Assistant's response message without having to work through message structures or check array sizes.
For further information see the following:
Integration with Virtual Assistants
SIP Proxy Mode Option
New mode option for SIP proxies to allow easy use of tel: URIs when making outbound calls from the Blueworx Platform.
For further information see the following:
Call Limits
Added the ability to limit the number of calls an Application can handle to go alongside the pre existing options to assign a call limit to an Application Mapping.
For further information see the following:
BAM Command Line Utility Inbound Applications Panel
Release: 7.21.1
Release date: 9th Oct 2020
New fixes contained in 7.21.1
| Issue # | Problem |
| 285 | T4293 - BVR offers 2 media description blocks in its SDP when rtp encryption mode set to OPTIONAL, should offer RTP/AVP with crypto lines (rfc8643) |
| 289 | Feature: Add ability to control sending of HEAD request before fetching VXML documents |
| 290 | CCXML createcall callerid field always assumes value is a full SIP address |
| 291 | T4417 - BRM expired connections can lead to incorrect active call counts, causing call rejection if application/app mapping cumulative call limits set |
| 293 | T4531 - BSM not using correct address (presentation address) for BVR in Contact address when REGSITERing |
| 295 | Feature: Add CentOS 8.2 support |
| 296 | bam, bvr, brm and bsm commands don't tell you what the help command is if you input an invalid command |
| 297 | Feature: Add ability to match SDP offer (RTP/AVP or RTP/SAVP) with the transport of the outbound call (e.g. offer AVP on sip and SAVP on secure SIP) by adding a new RTP encryption mode MATCH_SIGNALLING |
| 298 | Feature - Include User-Agent header on outbound SIP messages |
| 299 | Watson Assistant should send HTTP request body in UTF-8 |
| 300 | Virtual Assistants don't always correctly pick the correct assistant if locale is switched |
| 301 | T4572 - Virtual assistant won't start next recognize if prompt is empty |
| 302 | T4676 - Not always picking the correct ASR Call Feature if locale is switched mid application |
Release: 7.21.0
Release date: 17th Sep 2020
New fixes contained in 7.21.0
| Issue # | Problem |
| 279 | BVR takes a long time to report disconnected if a SIP call is asked to disconnect but it is retransmitting its INVITE |
| 280 | BVR takes a long time to start if there are a lot of cache entries |
| 286 | saveaudio isn't able to fetch audio saved to filesystem with file:// path |
| 287 | bvr -sm should show timestamps, other useful info on SIPMSG line |
| 288 | bvrProblem issues - truncates reports, unnecessarily compresses config and reports dirs fixed |
7.20
Blueworx Voice Response 7.20 adds support for SIP Register and includes changes to allow installation on the latest 8.1 releases of Red Hat and CentOS Linux. This release also adds the capability to use the Linux systemctl command for starting, stopping and monitoring the Blueworx platform.
SIP Register
Blueworx Voice Response 7.20 adds a new optional component, Blueworx Signalling Manager (BSM) that can be used to provide SIP Register support.
- Blueworx Signalling Manager (BSM) is an optional component, used to manage and send SIP Registration requests for configured Application Mappings.
- Configuration of SIP Registrars and Application Mappings using Registration is through BAM.
- Multiple Registrars can be configured and assigned to different Application Mappings.
For more information see the following:
BAM Command Line Utility SIP Registrars Panel
BAM Command Line Utility Application Mappings Panel
Red Hat Enterprise Linux and CentOS version 8.1
- Blueworx Voice Response 7.20 adds support for the latest releases of Red Hat and CentOS linux.
For detailed release information see the following:
Support for Linux services and the systemctl command.
- Blueworx Voice Response 7.20 adds support for the linux systemctl command for starting, stopping and monitoring status of the Blueworx platform.
For more information see the following:
Release: 7.20.2
Release date: 4th August 2020
New fixes contained in 7.20.2
| Issue # | Problem |
| 238 | T2701 - SIP OPTIONS responds with 200 OK during BVR Quiesce - now responds with 503 Service Unavailable |
| 263 | T3928 - Lumenvox reports language conflict if builtin grammars used with grammars that aren't en-US |
| 273 | Race condition causes app to get stuck if call cancelled during setup sequence |
| 274 | T3930 - Improve DTNA handling of incoming packets |
| 275 | Can't configure SIP listening points in BSM using [[sip.listening_point]] |
| 276 | Add support for Posrgres 12 |
Release: 7.20.1
Release date: 6th July 2020
New fixes contained in 7.20.1
| Issue # | Problem |
| 254 | T3860 - BAM occasionally hangs when getting cache entries, times out |
| 255 | T3866 - Watson STT can hang if max speech set but STT service provides empty results |
| 256 | T3846 - Watson Assistant dialogs do not exit back to the CCXML application if IAM tokens cannot be generated |
| 257 | record utterance doesn't correctly set the recording VXML variable, result cannot be submitted |
| 258 | REST API no longer responding due to missing classes in Java 13 JRE |
| 259 | T3885 - Use of Reco/TTS call during HUP causes NPE |
| 260 | Audio format not being detected correctly from Content-Type |
| 262 | T3897 - Japanese VXML2 site docs fail to load. |
| 270 | dtmf_recognition parameter no longer working on ASR Call Features |
| 271 | BVR not correctly handling empty dtmf termchar |
| 272 | NLSML processor treats values without a decimal as a % and are divided by 100 so a confidence of 1 returns 0.01f |
Release: 7.20.0
Release date: 24th June 2020
New fixes contained in 7.20.0
| Issue # | Problem |
| 249 | Incorrect tracing of some call id's |
| 250 | Outbound SIP headers aren't being set when sending a transfer in CCXML |
| 251 | BVR not parsing message/sipfrag or application/rs-metadata content |
| 252 | ClassCastException when deleting VXML recordings |
| 253 | SIP reINVITE stream RTP to new address |
7.19
VoiceXML Virtual Assistant Integration
Blueworx Voice Response 7.19 adds functionality to allow a VoiceXML application to interact directly with an IBM Watson Virtual Assistant, allowing for a direct alternative to an MRCP speech server for ASR and TTS capability when using VoiceXML. This change is a continuation of our drive to provide access to AI through all IVR application models in Blueworx Voice Response.
- Can fully replace Nuance/Lumenvox as an ASR provider within VoiceXML.
- Provides full "tier 4" speech capability.
- When compared to BVR's CCXML AI support, this feature allows “what comes next” business logic and managing complex application state to be performed within the VoiceXML application rather than in the Virtual Assistant.
- Uses a custom grammar format to drive the Virtual Assistant and custom response data from the Virtual Assistant, while still supporting standards compliant VoiceXML.
For further information see the following:
Integration with Virtual Assistants
IBM STT
- IBM STT now uses WebSockets for asynchronous results and improved reliability and speed
- Added "Input detection mode" option to change how BVR detects the start of speech, which can be either NOISE, FIRST_INTERIM_RESULT or FIRST_FINAL_RESULT.
Watson Assistant CCXML integration
- New Parameter: Max speech duration. Determines the maximum amount of speech to detect once initial input has been detected before completing the result.
- New Parameter: stt_parms. An Object containing key/value pairs of parameters to send to the STT engine.
- Some parameters can now be changed on a per prompt basis by setting context variables in the Watson Assistant. These are: bw_bargein, bw_no_input_timeout, bw_max_speech_duration
For further information see the following:
Integration with IBM Watson Assistant
Release: 7.19.1
Release date: 29th May 2020
New fixes contained in 7.19.1
| Issue # | Problem |
| 94 | recordutterance VXML property does not do anything. |
| 243 | VXML URLs get decoded before being fetched, causing fetch failures |
| 244 | SIP does not set From tag on out of dialog requests |
| 245 | Watson TTS caching results even if TTS fails. Results in empty cached TTS audio. |
| 246 | T2965 - BVR does not gracefully handle conversion of 16 bit audio if it is malformed and contains an odd number bytes |
| 247 | T2965 - BVR assumes all content from a 2xx response is valid audio when fetching audio without checking Content-Type |
| 248 | VXML does not correctly play headless audio formats (alaw and mulaw) |
Release: 7.19.0
Release date: 22nd May 2020
New fixes contained in 7.19.0
| Issue # | Problem |
| 232 | T2565 - Long pause between speech input and Watson response |
| 240 | TaskQueue can, in rare cases, lose tasks causing them to never be executed |
| 241 | Modify SIP Allow behaviour to assume everything is allowed if there is no Allow header provided |
Release 7.18
Shared Database Across Multiple Clusters
Blueworx Voice Response 7.18 enables a single database to be shared with multiple clusters even when each cluster has their own Zookeeper Shared Memory quorum. This has significant benefits in situations where multiple clusters are required, such as for geographic redundancy, but a single configuration database is preferred to ensure the multiple clusters function as a single system. Previously, either a separate database for each cluster or a shared Zookeeper quorum across sites was required.
BVR for Linux uses Zookeeper technology to provide resilient Shared Memory across a cluster of BVR components, enabling redundancy, scaling and reliability. It is also used for signalling between components. However running Zookeeper across geographies can introduce challenges.
Previously, when Blueworx Admin Manager (BAM) modified the database, it notified any BRMs in the cluster via Shared Memory to refresh their cache of the database (Diagram 1). 7.18 now uses the database itself to trigger a notification to any BRMs that they need to refresh their cache. As a result, any modifications made by BAM on Cluster A is propagated to Cluster B even though they are not in the same Shared Memory quorum (Diagram 2).
Release: 7.18.0
Release date: 9th April 2020
New fixes contained in 7.18.0
| Issue # | Problem |
| 177 | DNS queries for SIP can get each others results if executed simultaneously |
| 233 | bvrProblem hangs when "Collecting BRM component information" |
| 236 | T2676 - async play fails if audio if playing from private cache |
| 237 | T2676 - Audio URI not always redacted if audio URI redaction configured |
| 239 | 7.17.2 unintentionally removed support for eliptic curve cipher suites preventing IBM Cloud connectivity |
Release 7.17
Enhanced SIP Proxy Support
Blueworx Voice Response 7.17 includes enhancements to the SIP Proxy support.
- Configuration of SIP Proxies is now achieved using BAM.
- SIP Proxies and Proxy groups can be assigned to individual applications rather than just on a system wide basis, allowing each application to use a different set of SIP proxies.
- Individual SIP proxies can be configured with active monitoring (using SIP OPTIONS messages) to support immediate failover when the SIP proxy is down.
For further information see the following:
Release: 7.17.2
Release date: 19th March 2020
New fixes contained in 7.17.2
| Issue # | Problem |
| 224 | The default trace levels for various components have changed to what they should be when trace level is not explicitly set in config |
| 225 | T2470 - Watson HTTP requests no longer working after a number of calls have gone through the system |
| 226 | T2486 - Exception when converting streamed audio from 16 bit to 8 bit (in rare circumstance audio chunk contains odd number of bytes) |
| 227 | When using sips/tls, transport is incorrectly set to TCP on response contact headers |
| 229 | T2551 - CCXML Application Logs sometimes causing NullPointerException in logger, resulting in dialog not starting |
| 230 | bvr -sm doesn't work if trace level is off |
| 234 | Update java version to 13.0.2 |
Release: 7.17.1
Release date: 13th Feb 2020
New fixes contained in 7.17.1
| Issue # | Problem |
| 212 | Digest credentials using static cnonce value, should be randomly generated |
| 213 | T1867 BVR error trying to create FileCache |
| 214 | T1865 - BVR fails to send outbound messages if a proxy definition has headers defined with the same name as headers defined in application hints |
| 215 | T1867 - Application gets stuck in infinite loop |
| 217 | T1867 - MRCPv2 RECOGNIZE only sending 1 grammar in URI list |
| 218 | T1865 - Application on non-account 0 account can select proxies from account 0 if group name supplied in hint. |
| 219 | T1865 - Realm credentials from bvr.config never used in non account 0 applications |
| 220 | T1866 - Added options to redact audio URIs from logging |
| 221 | Startup of Blueworx components should list ifix info, and warn if ifix is configured and not present or ifixes conflict |
| 222 | Variety of improvements to Watson Assistant integration |
| 223 | Kafka: Non-error trace is being published to the blueworx.error topic |
Release: 7.17.0
Release date: 23rd Jan 2020
New fixes contained in 7.17.0
| Issue # | Problem |
| 204 | SIP Proxy authorization sends Authorization and Proxy-Authorization headers rather than just Proxy-Authorization |
Release 7.16
Dynamic Redundancy Quorum
The Blueworx Resource Manager updates in Blueworx Voice Response version 7.16 allow for improved management of high availability, adding in the ability to dynamically add or remove machines from a cluster's quorum.
Blueworx Voice Response version 7.16 also includes improvements to failover handling when a BRM in a highly available cluster is shutdown along with updates to various internal libraries for PCI compliance.
Release: 7.16.3
Release date: 8th Jan 2020
New fixes contained in 7.16.3
| Issue # | Problem |
| 209 | Update to ZooKeeper 3.5.6 |
| 210 | ZK reload requests aren't cleared after being processed causing BRM to process an increasing number of reloads |
Release: 7.16.2
Release date: 19th Dec 2019
New fixes contained in 7.16.2
| Issue # | Problem |
| 208 | ZooKeeper code does not handle certain IP addresses |
Release: 7.16.1
Release date: 18th Dec 2019
New fixes contained in 7.16.1
| Issue # | Problem |
| 207 | java.lang.NoClassDefFoundError on BRM startup in some cases. |
Release: 7.16.0
Release date: 17th Dec 2019
New fixes contained in 7.16.0
| Issue # | Problem |
| 174 | 'brm -l' command shows duplicate records of BVRs |
| 186 | VXML fetch timeout only applies to first call |
| 187 | Hanging up while Polly is trying to render text can cause app to hang around |
| 189 | Rare NPE in VXML2Session during SVT |
| 190 | Add support for kafka headers in topics |
| 191 | Rare ConcurrentModificationException in cache when fetching |
| 193 | Kafka producer has 0ms timeout |
| 194 | BAM commands stop working after some time running cache command, NPE |
| 195 | NPE when testing very long recordings. |
| 196 | Cache capacity errors when attempting a very long recording. |
| 197 | CCXML HTTP requests do not honour hints as headers |
| 198 | T1827 - Trace point T003319 has From and To the wrong way around |
| 203 | T1837 - Handle NPE on invalid DTMF Key |
Release 7.15
Cache Control
The Blueworx Admin Manager provided with Blueworx Voice Response version 7.15 now provides utilities to selectively view and purge the VoiceXML, CCXML and Audio caches across a cluster.
The cache entries can be displayed in a variety of formats, including a simple or detailed list, in a table or in JSON format.
Control of the cache is particularly useful when updating applications or audio; purging the cache ensures that the latest version is being used. Deleting an entire cache can affect performance and place additional load on the servers. With the addition of parameters, it is possible to purge only one type of cache, or only entries with a particular key, providing the granularity and flexibility often required in real-time, multi-application environments.
For further information see the following:
Release: 7.15.1
Release date: 12 Nov 2019
New fixes contained in 7.15.1
| Issue # | Problem |
| 121 | Ticket 1711+1793 - BRM assumes Host header has address:port |
| 166 | Ticket 1788 JSON not written out - Outbound Calls always try to use account 0 in CCXML |
| 168 | BRM hangs with DB connection blocked |
| 170 | Call active TTS + ASR is wrong |
| 171 | CDR JSON applicationId is wrong |
| 172 | Conference CDR not written out to file |
| 173 | CDR no call feature id in resources |
| 178 | CDR doesn't allow both file + kafka |
| 181 | NPE + apps hang around if call hung up early on application with multiple TTS services |
| 182 | CCXML sessions hanging around if fetch fails |
| 183 | BAM default config security section refers to BRM directories. |
| 184 | NPE playing audio during SVT on 7.15.0-157 |
| 185 | VXML apps fail to play anything after a fetchaudio is played in 7.15.0-157 |
| 188 | NPE when doing a CCXML dialogprepare on a createsession started app |
Release: 7.15.0
Release date: 31 Oct 2019
New fixes contained in 7.15.0
| Issue # | Problem |
| 175 | Very rare circumstance causes apps not to finish (caused by MRCPv2 sessions not finishing) |
| 176 | VXML applications occasionally not ending if managed by CCXML session |
Release 7.14
Support for direct integration with IBM Watson Assistant
- Blueworx Voice Response version 7.14 adds support for directly connecting to Watson Assistant using CCXML.
For further information see Integration with IBM Watson Assistant
Support IBM Speech Services
- Blueworx Voice Response version 7.14 adds support for IBM Text to Speech and IBM Speech to Text.
- IBM Text to Speech is available for use with both VXML and IBM Watson Assistant applications, IBM Speech to Text is only available for use with IBM Watson Assistant Applications.
For further information see the following:
Parameters for TTS_WATSON Call Feature
Parameters for STT_WATSON Call Feature
Release: 7.14.1
Release date: 08 Oct 2019
New fixes contained in 7.14.1
| Issue # | Problem |
| 158 | T1755 Uncaught CCXML Exception in CCXTeleMgr when handling DTMF events around the time of a call hangup |
| 159 | BVR doesn't send ACK if it is waiting to send a disconnect (e.g. after sending CANCEL) and incoming response is response to INVITE |
| 161 | T1549 Certain date formats unparseable when fetching |
| 162 | T1781 Recording only lasting 4.08 seconds |
| 163 | T1781 Beep not playing |
| 164 | NPE when sending CANCEL if transaction terminates at the same time as it's being sent |
| 165 | CDR files using wrong JSON format |
Release: 7.14.0
Release date: 07 Aug 2019
New fixes contained in 7.14.0
| Issue # | Problem |
| 150 | bvrProblem - VXML cache files are not collected |
| 151 | bvrProblem - The status.dat file is not collected for all components |
| 152 | Trying to set a BRM or BAM trace flag throws an exception |
| 153 | BVR and BRM throw NPE if command run with no args |
| 155 | bam doesn't work if no args are supplied, should behave same as bam -w |
Release 7.13
Extended Kafka support
Blueworx Voice Response version 7.13 adds new Kafka topics to better support monitoring of the system. Additionally, new fields have beed added into the existing Kafka topics.
New Kafka topics
- Event: A new event based topic detailing key events happening across all the BVR components.
- Status: A new status based topic detailing both call and component status. The call status breaks down both active and cumulative calls across the cluster. The component status shows the health/usage of specific components within the cluster.
For further information see the following:
Updated Kafka topics
- Application logging: Extra information concerning the source of the application logging has been added. This is to better support multiple BVR components running within a cluster.
- Trace/error: Extra information concerning the source of the trace and error logging has been added. This is to better support multiple BVR components running within a cluster.
For further information see the following:
Release: 7.13.3
Release date: 11 July 2019
New fixes contained in 7.13.3
| Issue # | Problem |
| 148 | BAM shutdown refers to BRM |
| 149 | Allow code to run against a new DB |
Release: 7.13.2
BVR Problem Enhancements
Blueworx Voice Response version 7.13.2 adds much greater problem capturing capabilities.
Release date: 9 July 2019
New fixes contained in 7.13.2
| Issue # | Problem |
| 92 | bvrProblem doesn't reference correct path for blueworx.jar |
| 122 | Invalid/blank trace line from DTNA |
| 138 | Add extra information in call status Kafka events |
| 144 | BRM and BAM don't correctly use log4j |
| 145 | Stop BRM from closing twice |
| 146 | BAM -q will not quit till automatically killed |
Release: 7.13.1
SIP Proxy Enhancements
Blueworx Voice Response version 7.13.1 adds the ability to specify a proxy group to use on specific outbound calls. It also adds options to SIP proxy config to allow custom SIP headers to be set on specific SIP request types when using that proxy.
For further information see the following:
SIP Proxy Header Configuration Options
Release date: 25 June 2019
New fixes contained in 7.13.1
| Issue # | Problem |
| 103 | Creating a CCXML call and starting a VXML dialog simultaneously may cause VXML session to not be created |
| 132 | RTCP packets are not being sent |
| 133 | No error message when bvr starts up if the mode string in the [cdr] section of bvr.config contains a non valid string |
| 136 | MRCPv2: "[T000530] ERROR Channel 09487ba2-3845-4221-8@speechrecog unexpectedly closed (channel not open on sock.recv)" unnecessary error message |
| 137 | BRM logs show "Blueworx A Manager" at the top, should be "Blueworx Resource Manager" |
| 139 | CCXML reports errors to log unnecessarily when a call hangs up immediately |
| 140 | CallHandler fails to find call due to HUP in some cases, causing INFO message |
| 141 | CCXML IBM Voice Gateway can't handle SIP URI without the user part |
Release: 7.13.0
Release date: 07 June 2019
New fixes contained in 7.13.0
| Issue # | Problem |
| 99 | Increase zookeeper buffer limit issue which prevented BVR from taking calls if too many applications or app mappings were defined |
| 100 | Fix "ERROR DomTransition Caught exception java.lang.String cannot be cast to org.mozilla.javascript.Scriptable" |
| 101 | Fix BVRSIPMessage trace lines so that they now all show BVR call ID (where available) |
| 102 | Fix issue introduced in 7.12.0 which prevented SIP messages showing in trace files if SIP_MONITOR trace level set using the command line |
| 105 | Fix issue where DTNA was adding unwanted padding to DTMFs |
| 106 | Fix issue which cause a NullPointerException if Proxy-Authentication requested but no proxy configuration was supplied |
| 114 | Fix issue introduced in 7.12.0 which broke the ability to add Call Features |
| 115 | Added the ability to configure Polly TTS in the Web UI |
| 116 | Fix issue introduced in 7.12.0 which broke the ability to modify Call Features |
| 118 | Fix issue in Web UI where adding an app mapping with no application attached returns 404 Not Found |
| 120 | Fix issue where BVR could attempt to use uncreated ZooKeeper nodes on a new install, preventing BVR from working correctly |
| 123 | Fix race condition where CCXML could throw a NullPointerException if an event becomes null while it's being used for logging |
| 124 | Fix issue introduced in 7.12.0 where MRCPv2 ASR calls could restart and reinitialise during call hangup, resulting in a call that never closes |
| 125 | Fix NullPointerException that occurs if we attempt to update the ZooKeeper nodes when a node has no path defined yet. |
| 126 | Added WARNING if incoming SIP 482 received, and ERROR if SIP 500 message sent or received |
Release 7.12
Integration with Amazon Speech services
Blueworx Voice Response version 7.12 adds direct integration with two of the Amazon AWS speech services. Amazon Polly for TTS and Amazon Lex for voice activated chat bots.
Amazon TTS using Polly
- BVR VXML applications can now use the Amazon Polly TTS service: https://docs.aws.amazon.com/polly/latest/dg/what-is.html
- Acts as a direct replacement for an MRCP TTS service with no application changes needed.
- Configured as a call feature using the Blueworx Admin Manager.
- Enables the same TTS voice to be used when integrating VXML applications with Amazon Lex chat bots.
For further information see Parameters for TTS_POLLY Call Feature
Amazon Lex Bot integration
BVR applications can now seamlessly integrate with Amazon Lex, enabling a blend of traditional VXML IVR applications with chat bots running on Amazon Lex.https://docs.aws.amazon.com/lex/latest/dg/what-is.html
- Integration is through the CCXML dialogstart functionality.
- Includes support for voice bargein, allowing a caller to interrupt a Lex prompt and provide input.
- CCXML application can seamlessly transition between VXML and Lex Bot applications.
For further information see Integration with Amazon Lex
Release: 7.12.2
Release date: 10 May 2019
New fixes contained in 7.12.2
| Issue # | Problem |
| 93 | Fix for ConcurrentModificationException when processing SIP OPTIONS and trace is on INTENSIVE |
| 96 | Sending DTMFs via a CCXML join when using dtmfclamp=false is unreliable. |
| 97 | DTMFs sent over a conference (CCXML createcall/join) have incorrect RTP timestamps |
| 98 | Linux kernal crash if DTNA's DTMF buffer fills up |
Release: 7.12.1
Release date: 26 Apr 2019
New fixes contained in 7.12.1
| Issue # | Problem |
| 90 | Environment variables are set but not exported causing issues for some scripts (such as bdb backup) |
| 91 | Lex sample applications don't check if evt.values has been set on dialog.exit |
Release: 7.12.0
Release date: 25 Apr 2019
New fixes contained in 7.12.0
| Issue # | Problem |
| 87 | MRCPv2 - Recognition failure not reported and actioned if RECOGNITION-COMPLETE event received without a response to the initial RECOGNIZE request |
Release 7.11
Blueworx Voice Response version 7.11 achieves full redundancy with the introduction of redundancy for the Blueworx Resource Manager (BRM) component. It also introduces a new component, the Blueworx Admin Manager (BAM) for cluster management tasks.
BRM Redundancy
- BRM was introduced in BVR for Linux 7.3 to enable a cluster of BVR machines to share configuration information and to provide centralized management and monitoring. This enabled BVR to become redundant; if one instance becomes unavailable, another instance can continue to take call using the configurations in BRM.
- BRM itself can now be made redundant with a self-managing, self-healing architecture. Additional instances of BRM can be added to a cluster, and the BRMs will communicate and sync to provide a consistent and continuous service to all the BVR instances in the cluster. This means that should any BVR or BRM instance become unavailable, the cluster will continue to take calls without any intervention.
For further information see Redundancy
BAM Component
- Cluster management tasks that are not critical to call handling have been divested from BRM into a new component called Blueworx Admin Manager (BAM). This increases the security and resilience of time-critical tasks for call handling, minimising the effect of external factors, such as runaway processes or DoS attacks.
- Management and monitoring APIs used by the Web Admin Interface are now served by the BAM component.
For further information see BAM Operation
Release: 7.11.2
Release date: 25 March 2019
New fixes contained in 7.11.2
| Issue # | Problem |
| 85 | Fix issue causing BAM CLI to hang when attaching Call Feature to outbound application |
| 86 | Fixed issue preventing reuse of TTS and Reco resources between dialogs on the same call |
Release: 7.11.1
Release date: 19 March 2019
New fixes contained in 7.11.1
| Issue # | Problem |
| 81 | Improved reporting of failed MRCP messages by logging Completion Reason |
| 82 | Fix DB package unnecessarily pulling in postgresql server |
| 83 | Enhanced redundancy handling during a failover |
Release: 7.11.0
Release date: 1 March 2019
New fixes contained in 7.11.0
| Issue # | Problem |
| 78 | Fixed issue where host names with '-' character in them can cause incomplete hostname directory names in log and config |
| 79 | Fixed bug where VXML resource fetches did not follow http redirects |
| 80 | Fixed issue where 2 consecutive TTS plays causes the 2nd TTS play to immediately finish, so the TTS is never heard |
Release 7.10
Blueworx Voice Response version 7.10 includes support for full call recording via SIPREC along with improvements to the networking configuration.
SIPREC support
Blueworx Voice Response can now act as a SIPREC client.
- Allows full call recording of both inbound and outbound audio when using a 3rd party SIPREC server
- Enables IBM Watson to listen in on a call with an agent or IVR through use of the SIPREC server provided in IBM Voice Gateway
For more information, see here: Recording calls using SIPREC
Network support
- Enhanced support for multiple network interfaces in the BVR component: Multiple Network Interfaces
- BVR now supports DNS SRV records for URIs when making outbound SIP requests (such as outbound calls or MRCPv2 session initiation).
Note: Configuration of the SRV record is performed on the DNS server rather than on BVR: https://tools.ietf.org/html/rfc2782
Note: Failover is not supported using DNS SRV, it is simply used as a mechanism to distribute load. Therefore only records using the lowest priority value will be used.
Release: 7.10.1
Release date: 13 February 2019
New fixes contained in 7.10.1
| Issue # | Problem |
| 74 | java.lang.NumberFormatException from badly formed createsession URL |
| 75 | dialogprepare not returning a dialog.prepared for VXML apps |
| 76 | SIP DNS lookups not using suffixes if using hostnames instead of FQDN |
| 77 | MRCPv2 messages can be processed out of order causing unexpected behaviour |
Release: 7.10.0
Release date: 24 January 2019
Release 7.9
Blueworx Voice Response version 7.9 includes enhancements to significantly improve security and extend CCXML support.
Increased Platform Security
- Secure SIP support for inbound and outbound calls
- Secure SIP support for MRCP and IBM Voice Gateway connectivity
- Secure RTP support for all streaming audio
- Support HTTPS encrypted communication to web servers for application resource fetching
- Support HTTPS encrypted communication to the Centralised Outbound Calling API
- Logging enhancements to allow the platform to be configured to obscure sensitive information such as recognition results and DTMF keys from the BVR logs and traces
For further information see Security
CCXML Enhancements
- CCXML support to allow DTMF key presses to be detected in the CCXML application as well as in the VXML application. For further details see CCXML DTMF Support
- Full support for the dtmfclamp attribute of the CCXML join tag, to allow DTMF clamping to be enabled or disabled during bridged calls.
Other Enhancements
- Blueworx Voice Response 7.9 now supports PostgreSQL 10. See here for more details: Installing PostgreSQL 10 Database for Blueworx CPD
Release: 7.9.2
Release date: 20 December 2018
Status: Superseded
New fixes contained in 7.9.2
| Issue # | Problem |
| 70 | Fix for default_presentation_address not being used by SIP or Streaming if [sip] or [streaming] sections do not exist |
| 71 | Fix an issue where call IDs could be incorrect in application logging |
| 72 | Updated default app_log_mode from OFF to FILE |
| 73 | Updates to log and trace statements for Kafka support |
Release: 7.9.1
Release date: 20 November 2018
Status: Superseded
New fixes contained in 7.9.1
| Issue # | Problem |
| 61 | Proxies were only usable on outbound calls. proxy_groups setting added. For full details on how to use this please refer to the "BVR SIP Proxy Configuration Options" section in the product documentation. |
| 62 | NLSML Grammars reveal DTMFs in logs even when secure logging enabled |
| 63 | app_log_mode does not default to "FILE" if keep_logs is true |
| 64 | DTMFs logged during FSG processing if secure_logging is enabled |
| 65 | Rare scenario allows creating app mapping for OUTBOUND application |
| 66 | SIP Proxies unable to resolve IP address of server if it is a CNAME record |
| 67 | Callers hanging up during a record can result in an error.internal event being thrown rather than a connection.disconnect.hangup. |
| 68 | BDB backup - fix to ensure if no directory path specified for backup file then file is created in current directory |
Release: 7.9.0
Release date: 6 November 2018
Status: Superseded
Release 7.8
- Application logging (high level application events and user generated logging)
- Errors, Warnings and emergency Informational messages
- Low level tracing
For further information see Configuring Apache Kafka topics for BVR
Release: 7.8.1
Release date: 10 October 2018
Status: Superseded
New fixes contained in 7.8.1
| Issue # | Problem |
| 59 | Stop DTMFs being lost when transitioning between audio prompts |
| 60 | Fixed a problem with fetchaudio attribute in VXML that could cause future audio plays to fail. |
Release: 7.8.0
Release date: 20 September 2018
Status: Superseded
New fixes contained in 7.8.0
| Issue # | Problem |
| 58 | Update database scripts to allow better integration with PostgreSQL's .pgpass file |
Release 7.7
This release includes:
- Centralised Outbound Calling API using BRM
- Bridged transfer support in CCXML (and VXML when controlled by CCXML)
- Fax Call Progress Analysis (CPA) for Outbound Calling
- Sample applications for Fax CPA and all types of call transfer.
Consult the BVR for Linux version 7 docs for an overview and installation instructions.
Release 7.7.2 introduced the blueworx-utils package, containing an Apache Kafka consumer for reading Call and Conference Detail Records and outputting these records to a PostgreSQL database. For installation instructions see the installation documentation, and for instructions on how to use the CDR consumer, see these operating instructions.
Release: 7.7.2
Release date: 07 August 2018
Status: Superseded
New fixes contained in 7.7.2
| Issue # | Problem |
| 57 | Added support for remote database installation |
| 56 | Fix BRM startup issues when startup process fails |
Release: 7.7.1
Release date: 10 July 2018
Status: Superseded
New fixes contained in 7.7.1
| Issue # | Problem |
| 55 | Fix java.lang.StringIndexOutOfBoundsException when using CCXML |
| 54 | Fix for MRCP SDP media description |
| 51 | Fixes a problem with passing URLs with spaces in them to the createsession interface of the CCXML HTTP server |
| 50 | Adds capability to use the joinid attribute of <createcall> to immediately join the completed outbound call to another call. This will automatically complete a bridge transfer if one is in progress on the call referenced in joinid |
| 49 | Update the HTTP handling code to improve handling of server disconnection and detection |
| 48 | Update of bvr.config.sample to have better port range examples, specifically ports that don't clash |
| 47 | MRCPv2 now sends a re-INVITE to deallocate an MRCPv2 channel before it closes the socket as per RFC 6787 section .42 |
| 46 | Added an extended call ID that is unique across all BVR machines and all time. This extended call ID can be used to pair up calls with conferences. |
Release: 7.7
Release date: 14 June 2018
Status: Superseded
Release 7.6
For details on what the new release of BVR 7 for Linux provides, please follow this link Building a Foundation for Dynamic Contact Center Infrastructure Performance Monitoring and Reporting on the Blueworx site. This release includes the introduction of support for outputting Call Detail Records (CDR) to Apache Kafka topics or to files. Read the Building a Foundation for Dynamic Contact Center Infrastructure Performance Monitoring and Reporting article for details and consult the BVR for Linux version 7 docs for installation instructions.
Release: 7.6
Release date: 17 May 2018
Status: Superseded
New fixes contained in 7.6.0
| Issue # | Problem |
| #44 | Clean up delayed messages when a CCXML session terminates |
Release 7.5
For details on what the new release of BVR 7 for Linux provides, please follow this link Rethink, Re-invent, Revive Your Contact Center with Cognitive Solutions from Blueworx and IBM Voice Gateway on the Blueworx site. This release included the introduction of integration between Blueworx Voice Response and IBM Voice Gateway. Read the Rethink, Re-invent, Revive Your Contact Center with Cognitive Solutions from Blueworx and IBM Voice Gateway article for details and consult the BVR for Linux version 7 docs for installation instructions.
Release: 7.5.1
Release date: 26 Mar 2018
Status: Superseded
New fixes contained in 7.5.1
| Issue # | Problem |
| #43 | Fix for no RTP packets sent during pauses in audio playback |
| #42 | Fixes to SIP tracing |
| #41 | Update log configuration section |
| #40 | Added outbound header support for IBM Voice Gateway applications |
| #39 | Fixed NPE when specifying vendor MRCP properties |
| #38 | Ignore invalid properties as per VXML spec |
Release: 7.5
Release date: 20 Mar 2018
Status: Superseded
Release 7.4
For details on what the new release of BVR 7 for Linux provides, please follow this link BVR 7.4 for Linux on the Blueworx site. This release included the introduction of the Web User Interface for Blueworx Resource Manager. Read the BVR 7.4 for Linux article for details and consult BVR for Linux version 7 docs for installation instructions.
Release: 7.4.3
Release date: 06 Mar 2018
Status: Superseded
New fixes contained in 7.4.3
| Issue # | Problem |
| 19 | VXML2: Site context path is incorrect causing an error.semantic to be reported if the default VXML catch handlers are executed. |
Release: 7.4.2
Release date: 01 Feb 2018
Status: Superseded
New fixes contained in 7.4.2
| Issue # | Problem |
| 16 | Database update script fix & update to v7.4.2 database |
| 8 | Adding in application logging and call flow logging: BVR Documentation: Application logging |
| 7 | Outbound session variables for application logging: session.connection.local.uri & session.connection.remote.uri |
| 6 | Add ANI and DNIS to VXML2 session variable list: session.blueworx.connection.ani & session.blueworx.connection.dnis |
Release: 7.4
Release date: 19 Dec 2017
Status: Superseded
New fixes contained in 7.4
| Issue # | Problem |
| 4 | Licensing: Add better reporting for errors involving invalid keys |
Note: our defect / bug / issue tracking system changed during release. As such defect / issue number has reset.
| Defect # | Problem |
| 3766 | CLI - Doesn't present if user is primary - Fix when creating users |
| 3504 | BRM tracing/logging improvements |
| 3736 | Plus '+' sign not allowed in simple app mapping, parses as invalid regex |
| 3735 | Remove log from bvr.config.sample |
| 3734 | BRM Web - AppMappings weren't showing appID |
| 3732 | BRM - DB won't let us create AppMapping with no AppID |
| 3720 | Fixing keepSession closure with CCXML/VXML (2 dialogs) |
| 3730 | SIP - CSeq gets incorrectly incremented when sending a CANCEL |
| 3729 | BRM Help - incorrect explanation for attributes |
| 3728 | BRM - Email templates not correctly populates, BRM won't start without them |
| 3724 | SIP - Outbound Call - NPE when sending CANCEL after ring timer expires |
| 3723 | bvr -r doesn't format tables correctly for TTS and ASR Call IDs |
Release 7.3
For details on what the 7.3 release of BVR for Linux provides, please follow this link BVR 7.3 for Linux on the Blueworx site. This release includes the introduction of the Blueworx Resource Manager (BRM) and associated Database (DB) component. Read the BVR 7.3 for Linux article for details and consult BVR for Linux version 7 docs for installation instructions.
Release: 7.3
Release date: 19 Oct 2017
Status: Superseded
New fixes contained in 7.3
| Defect # | Problem |
| 3748 | Improving CCXML stability/performance |
| 3712 | bvr -r : Call IDs in reports not formatted correctly (new CallID format - table column too small and not written out as hex) |
| 3715 | ERROR Could not find the socket for message BVR_CALL_FINISHED |
| 3701 | Long timeouts - voice applications hanging |
| 3706 | CCXML Error - muting spurious errors for dialog.exit when session has already terminated in CCXML |
| 3696 | Error while quiescing bvr with 480+ incoming calls |
| 3697 | NPE in trace for CCXML Call Dispatcher |
| 3699 | Partial hotword bargein stopping recording |
| 3693 | CCXML basic http - java.text.ParseException : invalid address [sip:user@hostname] - Should now work with full sip address |
| 3630 | Over logging of error/warning on failed MRCPv2 connection |
| 3646 | Incoming call to CCXML does not work |
| 3675 | bvr -m gives a max call limit of 500 when I have a 480 license and parm is not set in bvr.config |
| 3561 | Implement Call Features on BVR |
| 3508 | TraceID updates - Updating TraceIDs for config errors |
| 3544 | Update to newer JRE |
| 3500 | Locale not being converted correctly - Locales work properly between "_" "-" |
| 3549 | SIP - Set transfer as termination reason on successful transfer |
| 3537 | VXML2 Arbitrary SIP header support |
| 2397 | Fix up wvr.config sample |
| 3622 | CCXML fails to recognise app mapping |
| 3587 | Call feature locale not found |
| 3550 | Null check required for no headers |
| 3523 | Bargein issues with DTMF only - startReco regardless of voiceAllowed |
Release 7.2
For details on what the 7.2 release of BVR for Linux provides, please follow this link BVR 7.2 for Linux on the Blueworx site.
Fix Pack: 7.2.6
Release date: 19 Oct 2017
Status: Superseded
New fixes contained in 7.2.6
| Defect # | Problem |
| 3730 | SIP - CSeq gets incorrectly incremented when sending a CANCEL |
| 3725 | SIP - CallerID doesn't work properly with tel: uris |
| 3721 | Fix version on rm |
| 3724 | SIP - Outbound Call - NPE when sending CANCEL after ring timer expires |
| 3627 | CCXML connection fails |
| 3718 | Develop MRCP |
| 3720 | Fixing keepSession closure with CCXML/VXML (2 dialogs) |
| 3716 | AMD round to nearest 20ms |
| 3709 | Eliminating dialog 2 second shutdown wait for CCXML in the case where there are no active dialogs for efficiency |
| 3713 | VXML interferes with another session because they are started on the same call |
| 3685 | Adding redirect handling to post method on CCXML HTTP server |
| 3688 | Update CCXML to support https |
| 3691 | Adding http-get to CCXML http server |
| 3532 | marktime and markname not working correctly for all different turn types |
| 3564 | MRCPv2/VXML2 - maxage and maxstale do nothing on define grammars |
| 3562 | Incorrectly printing out a VXML2 error when not appropriate. |
Fix Pack: 7.2.5
Release date: 11 Aug 2017
Status: Superseded
New fixes contained in 7.2.5
| Defect # | Problem |
| 3532 | marktime and markname not working correctly for all different turn types |
| 3560 | CallerID tag in CCXML should set from header in SIP |
| 3554 | VXI incorrectly evaluated inputmodes variable in VXML |
| 3559 | NPE if CCXML app has regex expression for user in app_mapping. |
Fix Pack: 7.2.4
Release date: 28 Jul 2017
Status: Superseded
New fixes contained in 7.2.4
| Defect # | Problem |
| 3558 | Multicall mdoe - Multicall mode correction |
| 3557 | bvr script hostname not using .hostname, now uses .hostname file rather than sed. |
| 3555 | License expires license limit should be 2, is 1 |
| 3554 | VXI incorrectly evaluated inputmodes variable in VXML |
| 3551 | Resolving name incorrectly on BVR Linux |
| 3552 | Determine MRCP Vendor results in NPE |
| 3536 | SIP - Get user agent of far end |
| 3543 | Fixing getRecording to streamline recording |
| 3548 | NPE on record with dtmfterm=false and no DTMF grammar present. |
Fix Pack: 7.2.3
Release date: 12 Jul 2017
Status: Superseded
New fixes contained in 7.2.3
| Defect # | Problem |
| 3547 | License key code fails on CentOS 7 |
| 3543 | Fixing getRecording to streamline recording |
| 3503 | Hotword record dtmf |
| 3542 | Fixing bug with GCTI startup |
| 3538 | Centos build |
| 2697 | hotword not working |
| 3540 | Add RIFF header to recordings from DTNA |
| 291 | DTMF Hotword Support |
| 3539 | LumenVox not defining menu grammars correctly |
| 3530 | GCTI support |
| 3536 | SIP - Get user agent of far end |
| 3534 | Add bvr_key |
| 3533 | Temporary Cache not working correctly |
| 3532 | marktime and markname not working correctly for all different turn types |
| 3531 | SIP - Add option to ignore the sent by check when a response comes in |
| 3529 | MRCPv2 - Implement speech markers |
| 3528 | Update AMD to match AIX |
| 3526 | Fixing issue with BUSY HERE |
| 3525 | Update TerminationReason to handle BUSY |
| 3524 | Re-encode the URI for createsession to handle spaces etc |
Fix Pack: 7.2.2
Release date: 06 Apr 2017
Status: Superseded
New fixes contained in 7.2.2
| Defect # | Problem |
| 3522 | Race Condition with Multiple VXML2 Apps on Turn End |
| 3516 | Updates for License Type 2 |
| 3513 | Update core license library to support machine id and longer keys |
| 3511 | Developing BVR client |
| 3517 | BVRProblem using environment variable |
| 3515 | Createsession does not work for http uri's |
| 3514 | dtmfGrammarList empty when using external grammars with mrcp resource active |
Fix Pack: 7.2.1
Release date: 01 Mar 2017
Status: Superseded
New fixes contained in 7.2.1
| Defect # | Problem |
| 3506 | Adding Message Type classes |
| 3502 | Fixing linux build to happen locally |
| 3462 | Updating logic in printObject to fix formatting bug |
| 3460 | SIP - Bulk outbound calls fail with proxy |