vbvoice 10.2 service pack...

1

VBVoice 10.2 Service Pack 8 Release Notes (v10.2.8) August 15, 2019 This service pack is a maintenance release, which cumulates all the fixes and improvements since the previous release. It also adds support for Windows Server 2019, Visual Studio 2019 and the latest Dialogic drivers for both HMP and JCT cards.

Resolved Issues

On SIP, using Dialogic Call Control, the outbound calls fail when the calling number is empty

and SIP registration not enabled.

Visual Connect installer is not setting the ASP parent’s paths.

VBVoice online help links are not valid.

General Versioning Information

OS:

Windows 7 Pro, Ultimate, Enterprise 64-bit with Service Pack 1 Windows 8.1 Pro, Enterprise, 64-bit Windows 2008 Server R2 (64-bit) with Service Pack 1 Windows Server 2012 Standard Windows Server 2012 R2 Standard

Windows Server 2019 Standard

IDE:

Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio Professional 2013, Update 3 Visual Studio Community Edition 2013 Visual Studio Professional and Community Edition 2015 Visual Studio Professional, Enterprise and Community Edition 2017 Visual Studio Professional, Enterprise and Community Edition 2019

Dialogic HMP drivers:

Windows 7, Windows 8.1 Pro, Windows Server 2008 R2, Windows Server 2012, Windows Server 2016, Windows 10 Pro, Windows Server 2019 operating systems

2

- HMP 3.0 Service Update 395 for Windows 7, Server 2008, Server 2016, Windows 10

Dialogic JCT drivers:

Windows 7 Ultimate, Windows Server 2008 and 2008 R2, Windows Server 2012 Standard and 2012 R2 Standard , Windows Server 2016, Windows 10 Operating Systems

- SR 6.0 for Windows, Service Update 276

VBVoice 10.2 Service Pack 7 Release Notes (v10.2.7) March 18, 2019 This service pack is a maintenance release, which cumulates all the fixes and improvements since the previous release. It also supports the latest Dialogic HMP drivers, which fix some important issues.

Resolved Issues

On SIP, using Pronexus Call Control, on answered calls, the callflow exits Dial Control

through “Other” node with a timeout if there was no 180 (Ringing) provisional response

received before OK.

In certain cases, on a range node of GetDigits, the callflow wrongly exits through that node if

* or # was pressed. For example, if the range is 100-300, 21* would cause the callflow to exit

through that range node.

On SIP, using out-of-band DTMF (RFC2833 or SIP INFO), in some conditions GetDigits

control detects a digit twice and returns a double digit instead of the digit pressed.

On SIP, using Dialogic Call Control, the ini setting for SIP signaling address

(SipSignalingIPAddress) has no effect.

On SIP, using Pronexus Call Control, the outbound calls fail to authenticate if the registration

endpoint address contains a port number.



Windows 7, Windows 8.1 Pro, Windows Server 2008 R2, Windows Server 2012, Windows Server 2016, Windows 10 Pro Operating Systems

3


Excepting Dialogic HMP drivers, VBVoice 10.2.7 has been tested and released using the same drivers and hardware as VBVoice 10.2.6.

VBVoice 10.2 Service Pack 6 Release Notes (v10.2.6) February 8, 2019 This service pack is a maintenance release, which cumulates all the fixes and improvements since the previous release.

Resolved Issues

On HMP with Pronexus Call Control, unsupervised dial sends DTMF as SIP INFO when

DTMF mode is set to RFC2833.

On HMP with Pronexus Call Control, RawCallnfo for busy calls is empty.

When the application uses some custom connections set in Connections Property Page, at

runtime, the voice system fails to start.


VBVoice 10.2.6 has been tested and released using the same software and hardware as VBVoice 10.2.5.

VBVoice 10.2 Service Pack 5 Release Notes (v10.2.5) Nov 30, 2018

4

This service pack is a maintenance release, which cumulates all the fixes and improvements since the previous release.

What’s new?

Support for custom connection information in SDP

This applies only to Pronexus Call Control. Using an ini setting, the Connection Data (“c=”) field of the SDP could be customized to use an external IP address: [VoIP] ExternalRTPAddress The default is blank and the local address is used in this case.

Resolved Issues

Race condition on SIP re-invites when using Dialogic Call Control.

At runtime, WorkerThread control does not get properties set at design time in the property

page.


VBVoice 10.2.5 has been tested and released using the same software and hardware as VBVoice 10.2.4

VBVoice 10.2 Service Pack 4 Release Notes (v10.2.4) Aug 31, 2018 This service pack is a maintenance release, which cumulates all the fixes and improvements since the previous release. It also supports the latest Dialogic HMP drivers, which fix some important issues.

5

Resolved Issues

On SIP, re-invites fail when using Pronexus Call Control.

On SIP, re-invites without SDP fail when using Pronexus Call Control.

Number ordinal phrases played incorrectly.

VBVoice applications throw exceptions when starting voice system (StartSystem method of

VBVFrame).





Excepting Dialogic HMP drivers, VBVoice 10.2.4 has been tested and released using the same software and hardware as VBVoice 10.2.3.

VBVoice 10.2 Service Pack 3 Release Notes (v10.2.3) June 7, 2018 This service pack is a maintenance release, which cumulates all the fixes and improvements since the previous release.

Resolved Issues

On SIP, transfers fail when using Pronexus Call Control.

DNI cards do not work on HMP with Pronexus Call Control.

SIP INFO messages are not processed on HMP with Pronexus Call Control.

Receiving SUBSCRIBE messages causes Dialogic to leak internal resources and stop

working on HMP with Dialogic Call Control.

RTM redundancy fixes.

6


VBVoice 10.2.3 has been tested and released using the same software and hardware as VBVoice 10.2.2.

VBVoice 10.2 Service Pack 2 Release Notes (v10.2.2) April 16, 2018 This service pack adds some new SIP functionality and cumulates all the fixes and improvements since the previous release. It also upgraded support for the latest Dialogic drivers and Microsoft operating systems.

What’s new?

Support for processing DTMF by using SIP INFO messages

To avoid problems caused by in-band DTMF detection, an alternative is sending the DTMF in SIP INFO messages. Eventually, combined with using TCP for SIP signaling, this guarantees a safe digit processing, as opposed to problems arisen from in-band and even RFC2833, which could be affected by lost packets and jitter. This is supported only for Pronexus SIP Call Control. To use this DTMF mode, an .ini setting must be set: [Intel] SIPDTMFMode=SIPINFO In this case, all received and sent digits are using SIP INFO messages. Unsupervised Dial control is sending each digit in a SIP INFO message.

Resolved Issues

On SIP, GetDigits is detecting some digits twice when RFC2833 is used and the

gateway/PBX does an incomplete clamping of DTMF tones; fixed for both Dialogic and

Pronexus Call control.

Ini setting RcvFlags for receiving faxes is not working for HMP; the same setting as for

Dialogic JCT is now functional by using [Intel] section with the same values documented for

Dialogic.

SendFax on HMP shows 0 for TotalPages even on successful faxes.

7

SIP with Pronexus Call Control: REFER does not reply to authentication requests.

MRCPv2 does not work for ASR when the grammar is passed as URI.

General Versioning Information:

VBVoice 10.2.2 has been tested and released using the following:

OS:


Windows 10, Pro, Enterprise 64-bit Windows Server 2016 Standard

IDE:

The same as 10.2.0

Dialogic drivers:



Windows 7 Ultimate, Windows Server 2008 and 2008 R2, Windows Server 2012 Standard and 2012 R2 Standard , Windows Server 2016, Windows 10 Operating Systems

- SR 6.0 for Windows, Service Update 275

VBVoice 10.2 Service Pack 1 Release Notes (v10.2.1) January 9, 2018

8

This service pack is a maintenance release, cumulating all the fixes and improvements since the previous release.

What’s new?

Remote Diagnostic Logging for VBVMRCPClient

By setting DiagLogPort in section [MRCP] of the VBVoice.ini file to a valid port, VBVMRCPClient will publish the logs to that port and VBVDiagClient could be used to collect and save the logs. The default is 0, meaning that the logs are saved locally.

Resolved Issues

DialControl – SIP response codes not passed to CallResult.

At development time, StartTest fails with an error “Invalid exit node” (#565).

Voice file path not reset after the call is terminated (#607).


VBVoice 10.2.1, IDEs and drivers have been tested and released on the same operating systems as VBVoice 10.2.0.

VBVoice 10.2 Release Notes (version 10.2.0) November 15, 2017 This release brings a new look & feel to the VBVoice toolkit for a better experience at development time, as well as a better source control management for VBVoice projects. There are also new features leading to a greater stability and error diagnostic at runtime. It supports the latest operating systems and development tools from Microsoft® as well as the latest drivers from Dialogic, and cumulates all the fixes since the previous version.

9

What’s new?

A New Look & Feel of VBVoice Controls VBVoice changed the controls’ appearance to improve the visual recognition of the product. The controls’ colors are now linked by group or based on their functional similarity. All the components have been restyled to follow new trends (similar to Windows 10’s style). There are multiple schemes available to be selected by developers to suit their preferences.

MRCP Performance Enhancements

A new VBVMrcpClient (version 2) has been added to offer developers a version that is able to handle more load than VBVMrcpClient version 1; both versions now also offers redundancy and load balancing.

Mrcp Load Balancing Servers’ addresses are placed in a circular queue; the initial order is the same as the order specified in the VBVoice.ini. When an Mrcp session is being established, VBVoice picks the first address from the queue, matches the address with one of the specified Mrcp Profiles, sends the profile to MrcpV2Client, and places the address at the end of the queue. This mechanism balances the load between all available servers, avoiding the use of the same server for multiple sessions in a row.

Mrcp Redundancy

If VBVMrcpClient cannot establish a session with a server, it will try to establish a session with the next server in the Server Address Queue. The number of re-tries will equal the number of specified servers.

Dial Control Enhancements

This feature is applicable to SIP calls. When an outbound call does not get a provisional response (network disconnected or the INVITE did not reach the PBX) the call will exit through the “Other” node with a CallResult equal to vbvNetTimeout (57). New behaviour: If Answering Machine or Fax Detection are enabled, the dial has 2 stages. The first is only about signaling; after a connection is established, a tone analysis is performed. If the caller disconnects during tone analysis, a Disconnect event is fired and the call is terminated.

High Availability for VBVoice RTM on VMware The purpose of the HA feature is to provide continuously operational VBVoice service. When the virtual machine running the RTM is moved, the new machine will be able to provide the same functionality.

How to Configure HA Feature:

Edit vbvrtm.ini (from C:\Windows\vbvrtm.ini)

[Config]

; default 0 for the full MachineID

10

UseBasicMachineID=1

Diagnostic Logs Collector

In order to collect quickly all the diagnostic logs needed to be sent to Pronexus support (VBVLogs, VIL logs, RTF logs), a new item has been added to the support section of the VBVoice Control Panel. Just select the ‘Collect Logs’ menu item and choose an output path, and all the necessary logs will be saved in a compressed (zipped) file, ready to be sent to Pronexus Support.

Remote Diagnostic Logging

When chasing a problem, VIL logs are set to log many details and are written to files locally; this can use a lot of disk space. Our logging for Dialogic is based on log4cplus and allows multiple appenders to be used for custom logging. Using a configuration file in DiagnosticLogs directory with the name “Dialogic.log4cplus.properties” will allow the default RollingFile appender to be overridden. Using ZMQAppender, the logs can be sent to any subscribers through TCP. We provide a standalone application which could collect the logs and save them to files and locations customizable through a GUI.

New Format for Serializing Controls’ Properties

Previously, the properties of VBVoice components were saved in .resx files in a binary format, preventing a comparison of different versions in source control. The current version replaces the binary data with clear, readable text, so changes can be easily traced and modifications can be done without opening the project in VisualStudio. Opening a project in the latest version will perform the transition automatically when modified and saved.

SIP Pronexus Call Control RawCallInfo

Using Pronexus Call Control, the RawCalInfo property of Linegroup is able to retrieve all custom headers and most standard headers.

Automatic Generation of Crash Dumps

A new setting in the VBVoice Control Panel allows automatic creation of memory dumps to be sent to support for analyzing memory violations.

Resolved Issues

Pronexus Call Control: re-invites not processed in certain scenarios

Pronexus Call Control: codec negotiation issues

Memory violation when using database controls in ODBCOwnThread mode

SendFax throws an exception when using Fax objects

11

Known Issues

VBVoice installer may not be able to close automatically some of the applications it needs closed

to be able to finish installation without the need for a reboot. This is normal; however, on some

systems, when a message box shows up asking whether to retry or ignore, the Windows Explorer

process may have already been closed and pressing “Retry” may lead the installer to hang. With

Windows Explorer killed, there is no way to continue but to press Ctrl+Alt+Del and open the Task

Manager, then from its menu try to run the Explorer process.

Sometimes changes in a VBVoice form create changes in the sizes of VBVoice controls. These

changes can be ignored when committing to a source control repository. If they are committed,

eventually their values will stabilize.

In some cases, using Visual Studio 2017, the Toolbox icons are not visible when connected

remotely through RDP.

Sometimes VBVoice installer fails to install its toolbox in one version or more of an already

installed Visual Studio on the target machine. There might several reasons; for example, Visual

Studio has not been opened for a while, the user login was forgotten, or a new agreement or

license needs to be signed by the user to use Visual Studio. Two workarounds might be needed:

either running the toolbox install from the VBVoice control panel after finishing the installation and

correcting the login issue to Visual Studio, or manually adding the VBVoice tab and controls to

the toolbox after removing the old one if this is an upgrade.

Simulator is not starting on Windows 2016 and Windows 2012 R2

For known issues related to earlier versions please refer to the previous version release notes.


VBVoice 10.2 has been tested and released using the following:

OS:


Windows 10, Pro, Enterprise 64-bit Windows Server 2016 Standard

IDE:

Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio Professional 2013, Update 3

12

Visual Studio Community Edition 2013 Visual Studio Professional and Community Edition 2015 Visual Studio Professional, Enterprise and Community Edition 2017

Microsoft .net Framework 4.0 and up.

Dialogic drivers:


- HMP 3.0 Service Update 375 for Windows 7 and Server 2008

Windows 7, Windows Server 2008 and 2008 R2, Windows Server 2012, Windows Server 2012 R2 Operating Systems

- SR 6.0 PCI Service Update 271 for Windows 7 and Server 2008

Tested Configurations

Telephony Cards Win 7 Win 8.1

Win 2008 Serv

Win 2012 R2 Serv

Win 2016 Serv

Win 10

ISDN (NI2)

T1 RB CAS (US MF IO)

VS 2010

VS 2017

Max Lines Tested

D240JCT-T1 PCIe * * * * * * * 24

DNI 2410 184 (92) *

DNI 1210 92 (92) *

DNI 1200 * * * * * * * 96 (96) *

DNI 610 46 (46) *

DNI 601 48 (46) *

DNI 310 23 (23) *

DNI 300 * * 23 (23) *

D4 PCIe N/A N/A 4

D41JCT * * N/A N/A 4

D120JCT N/A N/A 12

HMP 3.0 SIP Dialogic Call Control

* * * * * N/A N/A * * 100

13

HMP 3.0 SIP Pronexus Call Control

* * * * * N/A N/A * * 100

* The bracketed number indicates the number of additional HMP 3.0 IP lines run simultaneously with ISDN-Ni2 trunks (23 lines per trunk). E.g. The DNI1210 was run with 92 ISDN + 150 IP channels for a total of 242 simultaneous channels.

NOTES:

The asterisks indicate combinations that have been tested.

The empty fields represent combinations that are possible and supported but have not been tested.

Fields with N/A (not applicable) represent the not supported combinations.

The Max Line column shows only the number of channels used in our testing. An application can use more channels, up to the hardware imposed limits.

Please check with Support for specific card versions

The test machines ranged from dual Xeon 2.14 GHz, 4GB RAM, up to quad Xeon 2.14 GHz, 4GB RAM, running both physical and virtual machines on VMware ESXi.

VBVoice 10.1 Service Pack 2 Release Notes (v10.1.2) May 2, 2017 This service pack is a maintenance release, cumulating all the fixes and improvements since the previous release.

What’s new?

ReleaseResource for TTS and ASR

ReleaseResource control is now able to release the currently allocated ASR or TTS engines; when the resource is not needed anymore, it could be freed and used by another call. Once an ASR or TTS engine is released, it cannot be grabbed again for the same call.

Pronexus Call Control improvements

1. The Ringing reply to INVITE is now containing SDP info

2. Linegroup RawCallInfo can retrieve multiple custom headers; this is driven by an INI setting. If

[Voip]

14

RetrieveSipHeader

is left blank, RawCallInfo is going to contain all custom headers, one per line.

If it is set to a certain header, RawCallInfo will retrieve only that header, the same behavior as

using Dialogic Call Control.

Changed default call clearing delay after SIP transfer

The ini setting [Voip] SipPostTransferDelayMs sets a delay to drop the call after a successful SIP transfer; some PBXs fail to complete transfer if the call is dropped right after the application receives a 202 reply (accepted) to REFER. The default had a value of 0; the new default is 50.

Resolved Issues

Pronexus Call Control: SIP signaling using TCP does not work

Fax not working for card types DialogicDM3 and DialogicHMP

Known Issues

All other known issues from VBVoice 10.1.1 still apply to VBVoice 10.1.2


VBVoice 10.1.2 has been tested and released on the same operating systems, IDEs and Dialogic JCT card drivers as VBVoice 10.1.1. For HMP, it was built and tested using HMP 3.0 SU 372.

VBVoice 10.1 Service Pack 1 Release Notes (v10.1.1) February 28, 2017 This service pack is a maintenance release, cumulating all the fixes and improvements since the previous release.

15

What’s new?

Improved install for first time users

When the install is done, there is an option to open VBVoice Control Panel, allowing users to control VBVoice or to run a demo application using Simulator Mode.

Resolved Issues

Memory leaks when using VisualConnect

Memory violation when using NLog on certain machines

VBVLog and VBVRLog are showing duplicate channels toolbars

Known Issues



VBVoice 10.1.1 has been tested and released on the same operating systems, IDEs and drivers as VBVoice 10.1.0

VBVoice 10.1 with VisualConnect™ Release Notes (v10.1.0) January 25, 2017 This release extends the functionality of VisualConnect™, offering capability to develop more complex applications targeting data on mobile phones and diverse devices. It supports the latest operating systems and development tools from Microsoft® as well as the latest drivers from Dialogic. It cumulates all the fixes since the previous version.

16

What’s new?

VisualConnect™ New Functionality

VisualConnect™, released in our previous version, added to the toolkit the new capability of developing applications that enable a user interaction from a browser with the same callflow as a voice application. This release adds more functionality to components already supported by VisualConnect and adds support for more components. 1) New behaviour when the caller presses the back button or refresh:

a. The VisualConnect application is now a single page in the browser history, which means pressing back is leaving the callflow.

b. A warning message is displayed when pressing back leads the caller to leave the current callflow session. It will not show if the session has already been ended by reaching the end of the callflow.

c. Revisiting the URL of the same application starts a new session and restarts at the beginning of the callflow.

2) More controls support:

a. On a data channel, greetings of type wave now show the text from an accompanying text file, the name of which is created by adding “.txt” to the wave file name; e.g., if the wave file name is x.wav, the accompanying text file is called x.wav.txt. This allows developers to attach meaningful text messages to wave files.

b. Delay and WorkerThread controls have been updated to behave in a session similarly to a voice call.

c. Record control is now supported. It records an accompanying text file on a data channel, the same file that would show when playing back a greeting of the same .wav file.

d. Dial control now supports Transfer mode. It offers the end user a link to call the target number.

e. GetDigits control has support for both Dynamic Menus and Mixed Menu mode. It shows a convenient keypad for entering digits when digits are expected. It supports cruise mode (when enabled) using the control’s timeouts defined in its properties.

f. VoiceRec control supports both Dynamic Menus and Mixed Mode. g. A Text Prompt automatic format enhancement function has been added, which fixes the

punctuations and allows a better concatenation of several text phrases. This is particularly useful for Greeting objects of multiple phrases of type VAP.

3) Voice-over-Data channel:

VBVoice Controls can define a new greeting, called HintGreeting, to be used to play specified voice prompt only on data channels. The HintGreeting could be the EntryGreeting of the control or a customized copy that may provide extra information or a summary of information useful to the end user. By default, this feature works on desktops and tablets but requires enablement on some phones to allow an automatic voice playback to HTML5 pages. Voice-over-data feature is controlled by a system-wide INI setting.

4) Cruise Mode:

This feature makes data sessions behave in a way similar to telephone voice calls. VBVoice controls now automatically proceed to the next ones when possible (no data input expected), following a voice-over-data prompt playback.

17

Consolidated .NET Assemblies

The VBVoice .NET interface is now consolidated in one assembly, Pronexus.VBVoice, This simplifies development because only one reference is needed in VBVoice projects, instead of multiple Pronexus assemblies that had to be referenced before.

MRCP Resource Allocation Enhancements

1) VBVoice is now able to allocate a TTS engine at the beginning of the call, making sure a resource is allocated before it’s needed. If the allocation failed at the beginning of the call, VBVoice is trying to get the engine on the first play of TTS phrases. Use the following setting to enable this feature: [TTS] AllocEnginePerCall=1 With the default set to 0 (old behavior, allocate when needed).

2) GrabResource control is now able to allocate a TTS or ASR engine; set the resource pool name to “TTS” or “ASR”; on exit through OK node, an engine is allocated to the channel. On re-entry, if the engine is already allocated, the callflow will exit through the OK node; otherwise, VBVoice will try again to allocate an engine.

Resolved Issues

When having two subsequent sayText phrases in a greeting, if there is no space at the end of the

first phrase’s text or at the beginning of the second, text is concatenated incorrectly before sending

the SPEAK request to the MRCP server

TTS fails to play when the text “sip” is contained by the text to be played

Dial Control log is misleading when CallResult is a negative number

HMP with Pronexus Call Control - outbound calls From and Contact fixes

HMP with Pronexus Call Control – fixes for transfers

All known issues from VBVoice 10.0 not listed here as resolved still apply to VBVoice 10.1.

Functional Limitations

Running VisualConnect applications has the following limitations for data channels: o Maximum number of concurrent sessions tested is limited to 40

All functional limitations from VBVoice 10.0 not listed as resolved still apply to VBVoice 10.1.

18



OS:


Windows 10, Pro, Enterprise 64-bit

IDE:

Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio Professional 2013, Update 3 Visual Studio Community Edition 2013 Visual Studio Professional 2015 Visual Studio Community Edition 2015


Dialogic drivers:

Windows 7, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 and Windows 8.1 Pro Operating Systems




Note: There is no Dialogic support for Windows 10.

GlobalCall Protocols Version 4.00

Note: Any other versions are not supported

19

VBVoice 10 Service Pack 1 Release Notes (v10.0.1) June 27, 2016 This service pack is a maintenance release, cumulating all the fixes and improvements since the previous release.

What’s new?

ContactAddress Some PBXs require a different contact address to be set in the reply to a SIP INVITE message. An ini setting has been added:

[VoIP] ContactAddress When left blank (default), the machine’s local address is used in the contact header.

Configurable SIP response code when no lines available The response code to an incoming INVITE, when all the lines are in use and the IVR cannot process new calls, could now be customized. An ini setting has been added: [VoIP] NoLinesAvailableResponseToInvite The default is 486 (Busy here).

Running in development mode warning

Now the developers have the capability to choose to not show the “running in development mode" warning.

Resolved Issues

Multiple SIP registrations using Dialogic Call Control – only the first registration succeeds

The toolbox is not installed on VisualStudio 2015

Custom license feature not working

VBVoice OLE DB providers throw exception

Edit phrases dialog in design mode: not able to open files after a play

Memory leaks when using Pronexus Call Control

20

Failing outbound calls when using Pronexus Call Control

A compatibility issue between IVRGuard and VBVoice 10

Failing to remove a data channel

TakeCall from an EnterEvent does not work for some controls on a data channel

Fixing the behavior of LicenseDrop vbvFrame event and adding another one called

RTMConnectionEvent to inform the application when a connection to RTM is lost or restored.

Known Issues


Functional Limitations Removed

All known limitations from VBVoice 10.0.0 still apply to VBVoice 10.0.1

.



21

VBVoice 10 with VisualConnect™ Release Notes (v10.0.0) October 6th, 2015 This release is introducing VisualConnect™, offering capability to develop and run applications targeting data on mobile phones and diverse devices. It adds support for Chinese language, Mandarin and Cantonese. It supports the latest operating systems and development tools from Microsoft® as well as the latest drivers from Dialogic. It cumulates all the fixes since the previous version

What’s new?

VisualConnect™

VisualConnect™ is a new product added to the toolkit to allow developing applications that enable a user interaction from a browser with the same callflow as a voice application. The developers can use an existing voice application and add data functionality by configuring some channels for data processing or write data only applications using the same components as voice applications. Some specific data or voice functionality could be customized as there is runtime information about the type of call being processed on each channel (voice or data).

1) VisualConnect client applications run in a browser on diverse devices: smartphones, tablets, laptops, desktops; browsers must support HTML5. Firefox and Chrome on desktop and Windows Phone on smartphones have been tested

2) It is using IIS on the same machine with the VBVoice application 3) The same controls and callflow can now be used to run voice channels or data channels 4) Data channels do not support outbound calls; if StartCall method is used on a data channel it will

throw an exception (Unsupported) 5) Phrases from Greetings are converted to text automatically for phrases containing text ((as VAP

phrases, SayText, etc); for wave file, the text contains the file name and it should be overridden. . A new property called Text has been added to Phrase objects; if set to a not null string, it overrides the automatic text generation. This property also support VBVoice’s property substitution technique to provide dynamic contents at runtime.

6) Multiple skins could be used for the background and they could be set at runtime per session or even per page.

7) LineGroup has a new initial property, MobileAppName that sets the name of the application served by that linegroup. It could be set at design time in Linegroup’s property pages or in code before starting the voice system. An empty string in this property (the default value) is considered an application with the name “default”.

8) VBVFrame has a new method named IsDataChannel (int channel) that returns true for VisualConnect data channels and false for voice channels.

9) GetDigis and VoiceRec have been extended to support a menu mode. 10) Components not supported by VisualConnect™ (permanent, they are not applicable to data

sessions): - CallQueue - Conference - DynGrammar

22

- FreeResource - GetResource - GrabResource - Language - PlayMsgs - ReceiveFax - Record - ReleaseResource - ResourceGroup - ResourcePool - Ring - SenFax - TapRecord - VerifySpeaker - VoiceCmd

11) Methods applicable only to voice calls (like Linegroup’s BridgeChannelToChannel, ListenToChannel, etc) are not supported for data sessions.

Windows 10 Support

The latest operating system from Microsoft is now supported for development; executing VBVoice applications is limited to VisualConnect channels and running slave applications. Development is now available in Visual Studio® 2010, 2012, 2013 and 2015, including 2013 and 2015 Community editions.

New languages support: Chinese (Mandarin and Cantonese)

Full support for Chinese language has been added, allowing developing IVR applications for both Mandarin and Cantonese.

Setting a different RTP address for outbound calls

For HMP SIP calls, using Dialogic call control, a different address/port could be set for outbound calls by using a new ini setting: [Intel] OutboundRTPAddress

Centralized Diagnostic Logs

In order to provide detailed information to Pronexus about problems related to Dialogic HMP and DMV cards or related to VisualConnect, diagnostic logs are created in a single location for all the applications. VBVConfig could be used to set the location and names of the log files. [DiagnosticLogs] Location= default C:\ProgramData\Pronexus\VBVoice\DiagnosticLogs

23

The log file name for Dialogic HMP and DMV cards is set by Dialogic= default VBVDialogicHMPVIL.log DialogicLogLevel= default 1 The log file name for VisualConnect is set by DataServer= default VBVDataServer.log DataServerLogLevel= default 1 Log level goes from 1 (fatal) to 5 (debug)

Microsoft Visual Studio 2015 Support

The latest version of Microsoft’s main development tool Visual Studio 2013 adds numerous features and facilitates faster development. You can now develop VBVoice applications in VB.NET and C# using Visual Studio 2015, targeting .NET framework 4.0 and up.

Discontinued Support for Windows 2003 Server and Visual Basic 6

As Microsoft has stopped supporting Windows 2003 Server, Pronexus is discontinuing support for Windows 2003 Sever as well starting with the release of VBVoice 10. As there is no currently supported Microsoft operating system to develop Visual Basic 6 applications, we discontinue support for Visual Basic 6 development.

Resolved Issues

Dialogic HMP with Dialogic Call Control – loss of internal resources leads to application not being able to answer calls

All known issues from VBVoice 8.20 not listed here as resolved still apply to VBVoice 10.


Running VisualConnect applications has the following limitations for data channels: - Modularity is not supported for data sessions - Maximum number of concurrent sessions tested is limited to 20 on Windows 2012 Server and

Windows 10, to 50 on Windows 7 - TakeCall method could be called only from VBVoice events on the same channel, it does not

work when called from another event or for a different channel

24

NOTE: These are not permanent limitations and will be resolved in future VBVoice Service Packs.

Windows 10 does not have drivers support from Dialogic yet, therefore only VisualConnect or slave applications for voice could be run; we are going to support running voice channels in Windows 10 soon after Dialogic makes drivers available.

Dialogic HMP with Pronexus SIP Call Control – not able to answer calls that do not have SDP info in the initial INVITE message All functional limitations from VBVoice 8.20 not listed as resolved still apply to VBVoice 10.


The following limitations have been removed for VBVoice IVRs using Dialogic HMP with Pronexus SIP Call Control:

- Does not support extended codecs, only G.711 A-Law and u-Law are supported - Does not support multiple registrations.

All other known limitations from VBVoice 8.20 still apply to VBVoice 10

Known Issues

Running VisualConnect applications on Windows 2012 Server or Windows 10 is limited to maximum 10 concurrent sessions and in certain conditions it stops processing any calls


VBVoice 10 has been tested and released using the following:

OS:

Windows 7 Pro, Ultimate, Enterprise 64-bit with Service Pack 1 Windows 8.1 Pro, Enterprise, 64-bit

Windows 2008 Server R2 (64-bit) with Service Pack 1 Windows Server 2012 Standard Windows Server 2012 R2 Standard

Windows 10, Pro, Enterprise 64-bit

25

Note: Windows 2003 Server has been discontinued.

IDE:

Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio 2012 Service Pack 1 (Professional, Premium) Visual Studio Professional 2013, Update 3 Visual Studio Community Edition 2013 Visual Studio Professional 2015 Visual Studio Community Edition 2015


Dialogic drivers:

Windows 7, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 and Windows 8.1 Pro Operating Systems




Note: There is no Dialogic support for Windows 10.



26

VBVoice 8.20 Service Pack 1 Release Notes (v8.20.1) November 3, 2014 This service pack is a maintenance release, cumulating all the fixes and improvements since the previous release.

What’s new? In order to develop and deploy IVR applications successfully using VBVoice, some essential rules must be strictly followed; in order to help developers to be aware of the rules and best practices, we added a list of the essential rules to the install and also a link to our best practices web page. Being aware of our best practices from the beginning will help developers to avoid later pitfalls and failures. During VBVoice installation, a dialog will display the top five important rules to follow when developing IVR applications using VBVoice, as well as a link to the “Best Practices” webpage on VBVoice.com; users must acknowledge each item from the list of top five important rules in order to be able to resume the installation.

Resolved Issues

Disconnect event is not fired in certain conditions: when the callflow goes to OnHook to terminate the call and PreDisconnect is fired, if the other party hangs up before Disconnect event is fired, Disconnect event will not fire

Dialogic HMP – SIP calls are not detected on some PBXs due to the change of Dialogic’s default value of sip_mime_mem.size parameter for the virtual SIP board

ASR - LumenVox automatically starts input timers when barge-in is detected; contact support for more info

MRCP ASR A-Law codec negotiation is not handled during session initialization

Known Issues



The following limitations have been removed for VBVoice IVRs running Pronexus SIP Call Control: - No call transfers - Not able to use custom headers

27

- No support for retrieving RawCallInfo

All other known limitations from VBVoice 8.20.0 still apply to VBVoice 8.20.1

.



VBVoice 8.20 Release Notes (v8.20.0) September 3, 2014 This release supports the latest operating systems and development tools from Microsoft® as well as the latest drivers from Dialogic. Added features include a new SIP Call Control for HMP, support for encrypted media (audio and DTMF) for VoIP calls as well as a provider of data to be monitored by IVRGuard, the new monitoring tool just released by Pronexus. It is also ready to be used to create IVR applications which work in a Microsoft Lync environment. It cumulates all the fixes since the previous version

What’s new?

Windows 8.1 and Server 2012 R2 Support

The latest operating system from Microsoft are now supported for both development and executing VBVoice applications. Development is now available in Visual Studio® 2010, 2012 and 2013. Other versions of Visual Studio® are not supported on Windows 8.1 and Server 2012 R2.

Microsoft Visual Studio 2013 Support

The latest version of Microsoft’s main development tool Visual Studio 2013 adds numerous features and facilitates faster development. You can now develop VBVoice applications in VB.NET and C# using Visual Studio 2013, targeting .NET frameworks from 2.0 to 4.5.

New SIP Call Control for HMP

The current use of Dialogic Call Control has some limitations due to the API used for HMP integration. VBVoice 8.20 replaces the Dialogic SIP Call Control component and allows the addition of more features previously not supported, such as secure/encrypted media (audio and DTMF) for Voice Over IP through “Secure Real-Time Protocol” (SRTP).

28

Pronexus Call Control is only supported only for SIP calls on Windows 8 and later and Windows Server 2008 and later. In order to switch to Pronexus SIP Call control an ini setting has been added: [Intel] SIPCallControl with the possible values “Dialogic” and “Pronexus”; the default value is Dialogic. Use SIPCallControl=Pronexus to get the application to use Pronexus SIP Call Control, leave it as default for Dialogic Call Control Currently this has some limitations, please check below. Using Pronexus SIP Call Control would not require Dialogic HMP Call Control licenses but it needs Pronexus Call Control licenses instead.

Secure/Encrypted Media Support for SIP (Secure RTP)

For SIP calls which go through public networks, the audio could be easily intercepted and therefore conversations and data transmitted during the call (digits) are not secure. SRTP (Secure RTP) will encrypt all audio streams (both directions), making all of the information passed inaccessible to possible attempts to tap and listen to the call. SRTP is adding little overhead and it offers encryption, message authentication and integrity, and replay protection to the RTP data carrying the voice, digits and fax. While we acknowledge SRTP offers better protection when used with TLS for signaling, TLS is not supported in this release, thus only RTP packets will be encrypted and not the SIP signaling. To enable SRTP, an ini setting is used: [VoIP] SRTP with the default 0; set it to 1 in order to enable SRTP. For example setting the following will enable SRTP: [VoIP] SRTP=1 When SRTP is enabled, all SIP calls are going to use SRTP;. Mixing unencrypted calls with encrypted calls is not supported. There are 2 modes of SRTP operation:

1) Fixed Master Key and No Master Key Management In this case, the master key must be set on both sides and there is no crypto information sent in the INVITE message. Use [VoIP] SRTPFixedMasterKeys=1 to enable this mode. Default is 0, use master key per call The master key must be set in

29

[VoIP] SRTPMasterKey and is a 40 characters string with each character in hex format ex: SRTPMasterKey=6b722b5a53627767743975466f495537396e56735434496575347575362b4e43734d686b70424a45

2) Master Key per call (default mode) - For outbound calls, a master key is generated for each call and sent in the SDP part of the

INVITE message - For inbound calls, the master key is retrieved from the SDP of the INVITE message

Interoperability with Microsoft Lync

Lync has made inroads into the enterprise, offering a Unified Messaging integrated natively with other Microsoft products. It allows routing /connection of calls from different endpoints. Our testing is proving that VBVoice applications using SIP are playing nicely in the Lync ecosystem. Calls could be made in both directions and both audio quality and DTMF have been tested successfully. In order to get more information about setting the Lync server to work with VBVoice, please contact our technical support.

Support for Pronexus IVRGuard

Pronexus has developed a new product for IVR monitoring called IVRGuard. When IVRGuard is enabled, VBVoice applications feed the required monitoring data to IVRGuard, which is responsible for analyzing the sanity of the application and sending alarms when certain conditions are met.

Discontinued Support for Windows XP

As both Microsoft and Dialogic have stopped supporting Windows XP, Pronexus is discontinuing support for Windows XP as well starting with the release of VBVoice 8.20.

Resolved Issues

Dialogic HMP – DNI cards have audio connection only in one direction

Set Dialogic recommended Call Progress Qualification Templates for Dialogic Springware cards

All known issues from VBVoice 8.0 and 8.01 not listed here as resolved still apply to VBVoice 8.20

30


Running applications with Pronexus SIP Call Control has the following limitations: - Does not support extended codecs, only G.711 A-Law and u-Law are supported - Does not support call transfers - Does not support use of custom headers and getting RawCallInfo - Does not support re-invites - Does not support T.38 fax - Does not support multiple registrations - Maximum number concurrent calls tested is limited to 50 - It runs only VoIP applications, no mixed TDM /VoIP use NOTE: These are not permanent limitations and will be resolved in future VBVoice Service Packs.

Visual Studio 2010 to 2013: Building applications targeting .NET Framework Client Profile is not supported (permanent). The project’s target framework should be set from the beginning to the full .NET Framework. All functional limitations from VBVoice 8.0 and 8.01 not listed as resolved still apply to VBVoice 8.20

Known Issues

Applications running with Pronexus SIP Call Control have a slight memory leak of around 200 bytes per call. At this time it is advised to perform a scheduled server reboot once a maximum of 100,000 calls are completed (or sooner).



OS:

Windows 2003 Server Standard Edition 32-bit with Service Pack 2 Windows 2003 Server Standard Edition 32-bit R2 with Service Pack 2 Windows 7 Pro, Ultimate, Enterprise, 32-bit and 64-bit with Service Pack 1 Windows 2008 Server 32-bit and 64-bit with Service Pack 2 Windows 2008 Server R2 (64-bit) with Service Pack 1 Windows 8, Pro, Enterprise, 32 and 64-bit Windows 8.1 Pro, Enterprise, 64-bit Windows Server 2012 Standard Windows Server 2012 R2 Standard

Note: Windows XP has been discontinued.

31

IDE:

Visual Studio 6.0 Service Pack 6 (Visual Basic 6) – not supported on Windows 7and later Visual Studio 2005 Service Pack 1 (Standard, Professional) Visual Studio 2008 Service Pack 1 (Standard, Professional) Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio 2012 Service Pack 1 (Professional, Premium) Visual Studio Professional 2013, Update 3

Dialogic drivers:

Windows Server 2003: - SR 6.0 PCI, Service Update 271 for Server 2003 - HMP 3.0 Service Update 354 for Server 2003

Windows 7, Windows Server 2008 and 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows 8 Pro and Windows 8.1 Pro Operating Systems




Note: SR6.0 does not support Windows 8 and Windows 8.1



32

VBVoice 8 Service Pack 1 Release Notes (v8.0.1) December 12, 2013 This service pack is mainly a maintenance release, updating support for the latest Windows operating systems and the latest drivers from Dialogic. It cumulates all the fixes and improvements done from the previous release.

What’s new?

Full Windows Server 2012 Support

The latest Microsoft server operating system, Windows Server® 2012, has been supported for development since VBVoice 8, on the same development IDEs as Windows 8. In the most recent service updates, Dialogic added support for Windows Server 2012 Standard for both HMP 3.0 and Service Release 6.0; as a result, VBVoice applications could be now run on this operating system.

MRCP ASR

In previous releases, the maximum time of recognition (Recognition-Timeout) had been hardcoded to 15 seconds; this value is acceptable for most applications but is a limiting factor while recognizing longer utterances. Now it could be customized by using the IMaxTime property (also found in the property page as “Max time of speech”) of VoiceRec control. If IMaxTime is left as default (0), then the old default value of 15 seconds would be used. If set to a positive number, that number would be used as maximum time of recognition (in MRCP it would set “Recognition-Timeout” parameter). The standard states the value for Recognition-Timeout ranges from 0 to an implementation specific value; however, VBVoice accepts only values starting from 1 as 0 is used for the previous hardcoded default of 15 s. This property is global per control and can be changed only at design time or at runtime before starting the voice system.

33

ABCD Digits

A, B, C and D DTMF digits, even though not found on regular phones, are used by some telephony systems. VBVoice had a limited functionality to detect and use these digits. Now all controls processing digits can detect and use these digits; for example, they can be used as option digits in Record control or could be part of the dial string of Dial control.

Resolved Issues

Dialogic HMP – loss of resources in some conditions leads to application not processing new calls

Memory access violation when voice system fails to start because of driver error

Using MRCP ASR on analog cards causes application to stop processing calls

When using MRCP ASR on analog cards there are random play greeting stops

MRCP ASR - recording recognized utterances does not retrieve the location of saved files when using Lumenvox MRCP Server

MRCP ASR detecting a digit upon starting recognition sometimes leads to recognition failure MRCP ASR - fast server replies (often due to running in the same box) lead to errors

MRCP TTS – setting the application to use TTS (VBVFrame’s property UsesTTS set to true) at runtime is causing a memory access violation when voice system is started

MRCP TTS – application fails to start from the IDE if Language property page of VBVFrame has been opened

Known Issues


.


VBVoice 8.0.1 has been tested and released using the following:

OS:

Windows XP 32-bit SP2 Windows 2003 Server Standard Edition 32-bit with Service Pack 2 Windows 2003 Server Standard Edition 32-bit R2 with Service Pack 2 Windows 7 Pro, Ultimate, Enterprise, 32-bit and 64-bit with Service Pack 1 Windows 2008 Server 32-bit and 64-bit with Service Pack 2 Windows 2008 Server R2 (64-bit) with Service Pack 1 Windows 8, Pro, Enterprise, 32 and 64-bit Windows 2012 Server Standard

34

IDEs:

Visual Studio 6.0 Service Pack 6 (Visual Basic 6) – not supported on Windows 8, Windows 7, Windows 2008 Server and Windows 2012 Server Visual Studio 2005 Service Pack 1 (Standard, Professional) Visual Studio 2008 Service Pack 1 (Standard, Professional) Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio 2012 Service Pack 1 (Professional, Premium)

Dialogic drivers:

Windows XP and Server 2003: - SR 6.0 PCI, Service Update 271 for Windows XP and Server 2003 - HMP 3.0 Service Update 347 for Windows XP and Server 2003

Windows 7, Server 2008 and 2008 R2, Server 2012: - SR 6.0 PCI Service Update 271 for Windows 7, Server 2008, Server 2008 R2, Server 2012

- HMP 3.0 Service Update 347 for Windows 7, Server 2008 and Server 2012



35

VBVoice 8 Release Notes (v8.0.0) May 15, 2013 This release has support for the latest operating systems and development tools from Microsoft®. It allows for the development of fully virtualized solutions, has improved the user experience and runtime stability. It cumulates all the fixes since the previous version.

What’s new?

Windows 8 Development Support

Recently Microsoft has released Windows® 8 as their flagship operating system, adding a new graphic interface to be used on multiple devices. Tablets can now use the same interface which enhances the mobile experience. Development in Windows 8 can now be done in Visual Studio® 2010 and 2012. Other versions of Visual Studio are not supported on Windows 8. Currently Dialogic® does not provide drivers for Windows 8, therefore only development can be done on Windows 8 and any applications must be deployed on operating systems supported by Dialogic (see General Versioning Information below). A VBVoice control panel has been added in order to be able to have easy access to all VBVoice features from a centralized location. It allows launching different VBVoice applications, like a logging utility or VBVConfig.

Windows Server 2012 Development Support

The latest Microsoft server operating system, Windows Server® 2012, is now supported on the same development IDEs as Windows 8. Currently Dialogic does not provide drivers for this OS but they are planning to add support soon. Once Dialogic does release the drivers, Pronexus will add support for running VBVoice applications.

Microsoft Visual Studio 2012

The latest version of Microsoft’s main development tool, Visual Studio 2012 adds numerous features and facilitates faster development. You can now develop VBVoice applications in VB.NET and C# using Visual Studio 2012, targeting .NET frameworks from 2.0 to 4.5.

36

Support for Fully Virtualized Solutions

The previous versions allowed running VBVoice applications in virtual machines but required running a Runtime Manager on a physical machine; now, the Runtime Manager can run on virtual machines. This is going to open new opportunities to deploy solutions based on VBVoice in data centers with all the benefits they offer.

Improved Help Available Online

A new updated help system is going to be available online at http://vbvoice.com/vbvoicehelp, allowing easy access to all the content.

Improved Log Files

Previously the log file names contained only the day and month; now, a full date, including year, is being used:

-VBVLog files are going to be named vbvYYYY-MM-DD.vlg -NLog files are going to be named vbvYYYY-MM-DD_*.vln

As a result, log files could be accumulated in the same directory for several years and could easily be sorted in chronological order.

Installation of VBVoice Automatically Removes Existing VBVoice Versions/Components

When installing VBVoice 8, the installer is going to automatically remove any existing VBVoice version or component, allowing one step installation.

MRCP Enhancements

Optimizations and tuning the ASR and TTS under MRCP allow an increased density to 30 simultaneous sessions of ASR and TTS. New properties have been added to the VoiceRec control in order to customize some MRCP properties, both at initialization and at runtime.

Initial properties: ISpeechComplete will set the “Speech-Complete-Timeout” MRCP property, default 1000 ms ISpeechIncomplete will set the “Speech-Incomplete-Timeout” MRCP property, default 1500 ms

Runtime properties: SpeechComplete(channel) will set “Speech-Complete-Timeout” MRCP property, default ISpeechComplete SpeechIncomplete(channel) will set “Speech-Incomplete-Timeout” MRCP property, default ISpeechIncomplete Also, a new Pronexus MRCP Client is still in beta and is installed by default. Ask Pronexus Technical Support if you are interested in testing this beta version, which will allow higher TTS densities.

http://vbvoice.com/vbvoicehelp

37

SIP Support Enhancements

- wait to start transfer after REFER

There is now the ability to add a delay after SIP REFER before clearing the channel.

After the REFER was sent and accepted, VBVoice was clearing the call right away, by sending a BYE. Some PBX-es do not complete the transfer in this case and need a delay between accepting the transfer request and the application clearing the call. A new setting has been added:

[VoIP] SipPostTransferDelayMs with a default of 0; the value is in milliseconds.

- Referred-By header for blind transfers

Added support for the Referred-By header to blind transfers with the same use as announced (attended) transfers.

Modularity Maximum Number of Channels

Modularity: maximum number of channels in a slave application was limited to 96; a new setting has been added to allow the changing of the number of channels a slave can process:

[Modularity] MaxChannels= with a default of 96.

DataFind Control

A new behavior has been added that will allow single threaded ODBC operations to be executed in a different thread than the main thread. Single threaded ODBC is recommended for ODBC drivers that are not thread safe. An INI setting was added to vbvoice.ini to enable this functionality:

[DataFind] doODBCInOwnThread=1 (default=0)

The old doODBCInMainThread (default=1) setting takes precedence over this one, so if both are set to 1, ODBC is executed in the main thread. Both settings should be set to 0 in order to allow multithreaded ODBC operations.

This change has a beneficial effect on performance and load, because for non thread-safe ODBC drivers, VBVoice used to load the main thread with time consuming ODBC operations. This was contrary to the stringent requirement to not do synchronous/long operations in the main thread.

38

Record Control

- Record control is now limited to the maximum recording time of 6000 seconds, the maximum allowed by Dialogic drivers. For longer recording times, another Record control in append mode could be used.

- A new runtime property has been added:

- vbvRecordTermReasons TermReason(short Channel)

It could be used in the Exit event to find the recording’s termination reason, for example vbvRecordTermMaxSil means a maximum silence caused the recording to terminate.

WorkerThread Control

A new event called CallTerminated has been added in order to allow adding code to cleanup on disconnects.

Resolved issues

Modularity: playing greetings containing multiple wave phrases leads to play errors.

VoiceRec:

When using modularity, maximum silence setting is ignored.

The recognition result (Words property of VoiceRec Control) is truncated to 499 characters if used after the Exit event of VoiceRec.

The recognition result (Words property) is not well formatted XML if recording utterances is disabled.

The default value for the setting of RecChopSilence in the [Record] section has been changed. It is now set to 0 for Dialogic HMP and DM3 cards to prevent chopping of the recorded file.

Analog cards: Caller ID is causing an error when calling from a public phone, where DNIS appears as unknown or blocked.

Conference Control: when the Dissolve method is called to dissolve a conference, the calls do not

exit the control.

MRCP on Dialogic Springware cards: speech recognition fails to start because of errors in Dialogic CSP.

HMP SIP registration: after a couple of failures to re-register after expiry time (eventually caused by network errors or registrar not answering), the drivers do not try to register anymore and the registration is lost.

ISDN on DM3 cards (Card type = Intel or IntelHMP): using TBCT, on load, after a while some lines do not answer calls anymore.

Conference Control: TakeCall method is not working when called in OptionDigit event.

Memory leaks on inbound calls on SIP/HMP.

39

Transfer fails if a re-invite is received right before the application initiates a transfer

DNI cards with DPNSS protocol: getting DNIS fails when sent overlapped

SIP fails to retrieve headers longer than 255 characters

SIP - T38 fax codec change errors

Known Issues

- MRCP TTS is not currently supported on Dialogic Springware cards

All other known issues from VBVoice 7.1.1 still apply to VBVoice 8.


VBVoice 8 has been tested and released using the following:

OS:

Windows XP 32-bit SP2 Windows 2003 Server Standard Edition 32-bit with Service Pack 2 Windows 2003 Server Standard Edition 32-bit R2 with Service Pack 2 Windows 7 Pro, Ultimate, Enterprise, 32-bit and 64-bit with Service Pack 1 Windows 2008 Server 32-bit and 64-bit with Service Pack 2 Windows 2008 Server R2 (64-bit) with Service Pack 1 Windows 8, Pro, Enterprise, 32 and 64-bit Windows 2012 Server Standard

IDEs:

Visual Studio 6.0 Service Pack 6 (Visual Basic 6) – not supported on Windows 8, Windows 7, Windows 2008 Server and Windows 2012 Server Visual Studio 2005 Service Pack 1 (Standard, Professional) Visual Studio 2008 Service Pack 1 (Standard, Professional) Visual Studio 2010 Service Pack 1 (Professional, Premium) Visual Studio 2012 Service Pack 1 (Professional, Premium)

Dialogic drivers:

Windows XP and Server 2003: - SR 6.0 PCI, Service Update 263 for Windows XP and Server 2003 - HMP 3.0 Service Update 338 for Windows XP and Server 2003

Windows 7 and Server 2008: - SR 6.0 PCI Service Update 263 for Windows 7 and Server 2008 - HMP 3.0 Service Update 338 for Windows 7 and Server 2008



40

VBVoice 7.1 Service Pack 1 Release Notes (v7.1.1) January 16, 2012 This service pack is a maintenance release. It cumulates all the fixes done from the previous release.

What’s new?

A new setting has been added to allow disabling automatic drivers’ retry on error for SIP: [Voip] SipRetryOnError with the default of 1; when set to 0 the drivers do not retry sending again the message.

Resolved issues

Runtime Manager using dongle failing to provide licenses after running for about a week

TapRecord is recording only 1second on HMP

TapRecord sometimes fails to record if is started right after a call to bridge/unbridge channels

Dialogic Springware cards – speech recognition improvement when using JCT cards and the memory audio provider

WorkerThread times out if job to execute is completed very fast

Record control – remove silence fixes for both compressed silence recording and regular recording

CallQ – calling Transfer method does not work while the entry greeting is being played

Known issues

All other known issues from VBVoice 7 do still apply to VBVoice 7.1 Note: VBVoice 7.1.1 was tested and released using the same drivers and operating systems as VBVoice 7.1.

41

VBVoice 7.1 Release Notes (v7.1.0) October 12, 2011

What’s new?

This new release is adding support for 64-bit versions of Microsoft Windows 7 and Windows Server 2008. Support for these operating systems includes developing applications using the latest Visual Studio versions (2010, 2008) and running applications on the latest Dialogic HMP 3.0 and SR 6.0 PCI drivers. It is also adding a new feature for VoIP to enable early media on inbound calls. It also cumulates all the fixes done from the previous release.

Windows 7 64-bit Support

The move to 64-bit operating systems has been prevalent in recent years. When Microsoft released Windows 7 as their current desktop operating system we added support for it and now we extend the support to the 64-bit versions. Development in Windows 7 64-bit is done using Visual Studio 2008 and 2010. Other versions are not supported on Windows 7. However, VBVoice applications developed with Visual Basic 6 could be run on Windows 7. The applications must be built for the 32-bit platform and run in 32-bit compatibility mode.

Windows Server 2008 64-bit Support Starting with Windows Server 2008 R2, Microsoft has moved to support only 64-bit on their server operating system; Windows Server 2008 is now supported on the same development IDEs and cards (drivers) as Windows 7. The applications must be built for the 32-bit platform and run in 32-bit compatibility mode.

SIP Early Media Support For SIP calls there is possible to establish the audio path before the call being connected and billed; this allows, for example, playing a message and asking the caller to confirm whether to proceed or no. Useful for prepaid phone cards, higher charge services where there are legal requirements to announce the caller about charges and many other scenarios. In order to use it, in the Ring event of the Linegroup Control, set Noofhhok to 1; the call is going to exit the Linegroup control through the Ring node without the call being answered (connected). However the audio path is established and PlayGreeting and GetDigits controls could be used for caller’s interaction with the IVR. No other controls are supported. When the call should be answered, an unsupervised Dial control with a comma ”,” as dial string would connect the call by sending the OK to the initial INVITE.

42

Dialogic HMP 3.0 support for Windows 7 64-bit and Server 2008 R2 64-bit From Service Update 298. Dialogic introduced support for the 64-bit versions of Windows® 7, WindowsServer® 2008 (with Service Pack 2), and Windows Server® 2008 R2 operating systems in 32-bit compatibility mode. As a result we updated and do support the latest version of HMP.

Dialogic SR6 PCI support for Windows 7 64-bit and Server 2008 64-bit Recently Dialogic introduced support for the 64-bit versions of Windows® 7, WindowsServer® 2008 (with Service Pack 2), and Windows Server® 2008 R2 operating systems in 32-bit compatibility mode. As a result we updated and do support the latest version of SR 6.0 PCI. New Improved Installer This release is introducing a new installer with less interaction and capabilities for automatic install. The Setup program accepts optional command line parameters. These can be useful to system administrators, and to other programs calling the Setup program. /SP- Disables the This will install... Do you wish to continue? prompt at the beginning of Setup.

/SILENT, /VERYSILENT

Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the startup prompt is (if you haven't disabled it with the '/SP-' command line option explained above).

If a restart is necessary and the '/NORESTART' command isn't used (see below) and Setup is silent, it will display a Reboot now? message box. If it's very silent it will reboot without asking.

/NOCANCEL

Prevents the user from cancelling during the installation process, by disabling the Cancel button and ignoring clicks on the close button. Useful along with '/SILENT' or '/VERYSILENT'.

/NORESTART

Prevents Setup from restarting the system following a successful installation, or after a Preparing to Install failure that requests a restart. Typically used along with /SILENT or /VERYSILENT.

/RESTARTEXITCODE=exit code

Specifies a custom exit code that Setup is to return when the system needs to be restarted following a successful installation. (By default, 0 is returned in this case.) Typically used along with /NORESTART. See also: Setup Exit Codes

43

/LOADINF="filename"

Instructs Setup to load the settings from the specified file after having checked the command line. This file can be prepared using the '/SAVEINF=' command as explained below.

Quotes must be used if the filename contains spaces.

/SAVEINF="filename"

Instructs Setup to save installation settings to the specified file.

Quotes must be used if the filename contains spaces.

/LANG=language

Specifies the language to use. language specifies the internal name of the language as specified in a [Languages] section entry.

When a valid /LANG parameter is used, the Select Language dialog will be suppressed.

/DIR="x:\dirname"

Overrides the default directory name displayed on the Select Destination Location wizard page. A fully qualified pathname must be specified. May include an "expand:" prefix which instructs Setup to expand any constants in the name. For example: '/DIR=expand:{pf}\My Program'.

/GROUP="folder name"

Overrides the default folder name displayed on the Select Start Menu Folder wizard page. May include an "expand:" prefix, see '/DIR='.

/NOICONS

Instructs Setup to initially check the Don't create a Start Menu folder check box on the Select Start Menu Folder wizard page.

Resolved issues

CallQueue - deadlock when calling QueueCount in CallQueued event

Setting the calling number for outbound calls does not work for DASS2 and DPNSS protocols on DM3 cards

Dialogic Springware digital cards – some lines stop accepting calls after channel was stopped with call in accepted state

44

MRCP ASR- timers for maximum silence and maximum time inaccurate for barge-in recognition

Multiple runtime manager stability fixes

Removed limitation:

Running on 64-bit operating systems

All other functional limitations from VBVoice 7 do still apply to VBVoice 7.1

Known issues

Windows 7 64-bit and Windows 2008 Server: when closing Visual Studio 2010 or 2008 and the project properties tab is open, the next time the project is opened the IDE is crashing with an exception. You should make sure the project properties tab is closed before closing the IDE. If it happened and got the exception, delete the solution’s .suo file and then you will be able to open the project. This is going to be addressed soon in a service pack.

VBVoice un-installation does not completely remove all files and directories

The HASP dongle driver does not install on Windows 7

The new VBVoice installer does not install the help files for any Visual Studio.net IDE

On 64 bit machines, new projects are not pointing to the right project voice directory of "Program Files (86)" but rather to "Program Files".

Dropping a Dynamic Grammar control on the frame for the first time after install is causing Visual Studio to stop working and throw an exception.

Dropping a DialogicD42OCX control on the frame fails with an exception in Visual Studio

All other known issues from VBVoice 7 do still apply to VBVoice 7.1

General Versioning Information: VBV 7.1 was tested and released using the following: OS: Windows XP 32-bit SP2 Windows 2003 Server Standard Edition 32-bit SP2 Windows 2003 Server Standard Edition 32-bit R2 SP2 Windows 7 32-bit Windows 7 64-bit Windows 2008 Server 32-bit Windows 2008 Server SP2 and R2 64-bit IDEs: Visual Studio 6.0 SP6 (VB6) – not supported on Windows 7 and Windows 2008 Server Visual Studio.NET 2003 - not supported on Windows 7 and Windows 2008 Server Visual Studio.NET 2005 SP1 (Standard, Professional) - not supported on Windows 7 and Windows 2008 Server

45

Visual Studio.NET 2008 SP1 (Standard, Professional) Visual Studio.NET 2010 (Professional, Premium) with or without SP1 Dialogic drivers: Windows XP and Server 2003:

- SR 6.0 PCI, Service Update 263 for Windows XP and Server 2003 - HMP 3.0 Service Update 307 for Windows XP and Server 2003

Windows 7 and Server 2008 (both 32 and 64-bit):

- SR 6.0 PCI Service Update 263 for Windows 7 and Server 2008 - HMP 3.0 Service Update 307 for Windows 7 and Server 2008

GlobalCall Protocols Version 4.00 Note: Any other versions are not supported

46

VBVoice 7 Service Pack 1 Release Notes (v7.0.1) February 10, 2011

What’s new?

This service pack is fully opening the VBVoice 7 development by removing the need for a license and allowing full access to all the functionality. It adds support for virtualization at design time and supports running applications using HMP on IP in a virtual machine. It also cumulates all the fixes done from the release and adds support for the latest drivers for HMP.

Free development

VBVoice 7 became free for development but had some limitations as requiring a (free) license and limited access to some components like TapRecord. This service pack is removing the last hurdles and allows developing applications without any license and having full access to all the components of the toolkit.

Virtualization Support Currently VBVoice 7 is supporting virtual machines both at design time and at runtime, the later being limited to IP channels on Dialogic HMP or to running slave applications. Development and running slave applications has been tested on VMware and VirtualBox. Starting from Service Update 275 for HMP 3.0 for Windows, Dialogic is supporting virtualization using VMware ESXi 4.0 Update 1 Installable, only for IP, on the following versions of Windows Server® 2003: • Windows Server® 2003 (Standard or Enterprise Edition) with Service Pack 1 or 2 • Windows Server® 2003 R2 (Standard or Enterprise Edition) • Windows Server® 2003 R2 (Standard or Enterprise Edition) with Service Pack 2 The setup needed to use HMP in VMware is described in detail in the release update of HMP (release_update.pdf, 1.12 Virtualization Support).

SIP - Provisional response to INVITE

A new setting, [VoIP] ProvisionalResponseToInvite allows setting the desired response to a SIP INVITE. The default is 180; it could be set to any value between 100 and 199.

47

Resolved issues

MRCP ASR – recognition failing when using Nuance Speech Server 9.0

MRCP ASR – recognition failing if A-Law is used

Caller ID not retrieved for Dialogic Springware analog cards Runtime Manager – High CPU usage with multiple applications connected

Functional limitations

Removed limitation:

Running any Pronexus product in virtual machines is not supported – this is going to be addressed in a service pack in the near future.

Running VBVoice applications in virtual machines is still having some limitations; it is supported only for slaves or IP on HMP in a VMware ESXi virtual machine. All other functional limitations from VBVoice 7 do still apply to VBVoice 7.0.1

Known issues

All other known issues from VBVoice 7 do still apply to VBVoice 7.0.1

General Versioning Information: VBV 7.0.1 was tested and released using the following: OS: Windows XP 32-bit SP2 Windows 2003 Server Standard Edition 32-bit SP2 Windows 2003 Server Standard Edition 32-bit R2 SP2 Windows 7 32-bit Windows 2008 Server 32-bit Note: VBVoice is not supported on any 64-bit operating system IDEs: Visual Studio 6.0 SP6 (VB6) – not supported on Windows 7 and Windows 2008 Server Visual Studio.NET 2003 - not supported on Windows 7 and Windows 2008 Server Visual Studio.NET 2005 SP1 (Standard, Professional) Visual Studio.NET 2008 SP1 (Standard, Professional) Visual Studio.NET 2010 (Professional) Dialogic drivers:

48

Windows XP and Server 2003:


Windows 7 and Server 2008:



49

VBVoice 7 Release Notes September 7, 2010

What’s new?

VBVoice 7 synchronizes all Pronexus’ offerings with the latest operating systems from Microsoft, namely Windows 7 and Windows Server 2008. Support for these operating systems includes developing applications using the latest Visual Studio versions (2010, 2008, 2005) and running applications on Dialogic HMP and SR6.0PCI.

Windows 7 support

Since Microsoft has released Windows 7 as their most current supported operating system, we have added support for it and are discontinuing support for Windows Vista. As the move to Windows 7 is generally accepted, Windows Vista support is no longer maintained by Dialogic. Starting with this release, Pronexus will not do any new development for Vista and will not support running VBVoice applications on Vista. Instead we are committed to fully supporting Windows 7. Development in Windows 7 is done using Visual Studio 2005, 2008 and 2010. Other versions are not supported on Windows 7. However, VBVoice applications developed with Visual Basic 6 can also be run on Windows 7.

Windows Server 2008 support

The latest Microsoft server operating system, Windows Server 2008 is now supported on the same development IDEs and cards (drivers) as Windows 7.

Microsoft Visual Studio 2010

The recently released version of Visual Studio 2010 adds numerous features and facilitates faster development. Now you can develop VBVoice applications in VB.NET and C# using Visual Studio 2010, targeting .NET frameworks from 2.0 to 4.0.

Dialogic HMP 3.0 support for Windows 7 and Server 2008

Dialogic added recently support for HMP 3.0 for Windows 7 and Windows Server 2008. Vista has never been supported for HMP and is not going to be. There are different drivers for Windows 7 and Windows XP even though they have the same Service Update number.

Dialogic SR6 support for Windows 7 and Server 2008

Dialogic added recently support for cards for Windows 7 and Windows Server 2008. There are different drivers for Windows 7 and Windows XP even though they have the same Service Update number.

50

Dropped support for Dialogic HMP 2.0

HMP 2.0 had been discontinued by Dialogic and Pronexus will no longer provide support for it as of this release. Customers using HMP 2.0 have the option to upgrade to HMP 3.0 or continue using older versions of VBVoice.

Dropped support for Windows Vista

Dialogic Drivers for Windows Vista are not being actively developed or maintained since the Windows 7 release. Developing VBVoice applications on Vista is still possible in this release but is not supported. Running VBVoice applications on Windows Vista is not supported, beginning with this release.

New INI settings for G.711 codec order for HMP

In order to select the order of codecs used by Dialogic HMP in the SDP, new values have been added for

Codec# setting:

g711u – only G.711 u-Law is present the SDP

g711A - only G.711 A-Law is present the SDP

g711u,g711A

g711A,g711u both u-Law and the A-Law are in the SDP in the chosen order.

New default behaviour for runtime checking of changing initial properties

Changing initial properties, global per control (not per channel) after the voice system has been started is a potential cause for errors (memory violations, wrong functionality) and therefore not recommended or supported. It has never been recommended but until this release, it has not been enforced. In a previous version of VBVoice, the following setting was introduced: [System] EnhanceRTCheck having a default value of 0 (disabled). When enabled, this would treat changing initial properties at runtime as errors. In VBVoice 7, we have changed the default to 1 to assure the integrity of VBVoice applications. Old applications should be reviewed and corrected to not modify initial properties after system start. In this release, this setting can still be disabled. However, Pronexus Technical Support will not accept error reports or troubleshoot issues if the Enhanced Runtime check has been disabled. Future VBVoice releases will remove the option of disabling this check. .

51

Resolved issues

Runtime Manager – Invalid license strings or large number of license strings cause memory violations

The Runtime Manager rolls over if the Runtime Manager Service fails. If the machine running the Runtime Manager goes down or loses the network connection, it does not roll over to the redundant server.

Power outage during uninstall cause uninstall to fail continuously.

Fax on SR6.0, DMV cards – random receive fax failures

Runtime Manager – Change of the IP of the machine running the runtime manager requires a reboot.

MRCP client memory violation on load

Memory violation on load in slave applications using Nuance ASR


Running any Pronexus product in virtual machines is not supported – this is going to be addressed in a service pack in the near future.

Running Aumtech MRCP with both TTS and ASR with barge-in enabled is not supported.

Visual Studio 2010: Building applications targeting .NET Framework Client Profile is not supported (permanent). The project’s target framework should be set from the beginning to the full .NET Framework.

All functional limitations from VBVoice 5.6 do still apply to VBVoice 7

Known issues

VBVoice installs will miss detecting Visual Studio 2010 until the development environment is set. Run Visual Studio 2010 once and pick C# or whatever environment you are going to use. Then VBVoice install will detect Visual Studio 2010 as an installed IDE and will add support for it.

HASP Driver on Windows 7 does not report activated on first run 1) Generate license for dongle and make sure ID matches 2) During the Runtime Manager install options, install Dongle driver, browse to license files 3) After install, activate license with reg file 4) Open RTMconfig, licenses are not activated 5) Try and auto-activate, RTMconfig is stuck trying to activate (not responding, Windows 7's 'busy' blue circle animation is spinning) If you close and re-open, licenses appear activated.

MaxSilence not working on MRCPASR on Dialogic Sprigware JCT cards All other known issues from VBVoice 5.6 do still apply to VBVoice 7

52

General Versioning Information: VBV 7.0 was tested and released using the following: OS: Windows XP 32-bit SP2 Windows 2003 Server Standard Edition 32-bit SP2 Windows 2003 Server Standard Edition 32-bit R2 SP2 Windows 7 32-bit Windows 2008 Server 32-bit Note: VBVoice does not support any 64-bit operating system IDEs: Visual Studio 6.0 SP6 (VB6) – not supported on Windows 7 and Windows 2008 Server Visual Studio.NET 2003 - not supported on Windows 7 and Windows 2008 Server Visual Studio.NET 2005 SP1 (Standard, Professional) Visual Studio.NET 2008 SP1 (Standard, Professional) Visual Studio.NET 2010 (Professional) Dialogic drivers: Windows XP and Server 2003:


Windows 7 and Server 2008:



53

Tested Configurations

Telephony Cards Win 2003 R2 SP2 Stnd.

Win XP Pro SP2

Windows 7

Win 2008 Server

ISDN (NI2)

T1 RB CAS (US MF IO)

Visual Studio 2010

Visual Studio 2008

Max Lines Tested

DMV 1200BTEP * * * * * * * 96

DMV 600BTEP * * * * * * 46

DMV 960A * * * * * * 96

DMV 960 4T1 * * * * 92

DMV 480A * * * 46

D240JCT-T1 PCIe * * * * * * 24

D240JCT-T1 * * * * * * * * 24

DNI 2410 * * * * 184 (92) *

DNI 1210 * * * * * * * 92 (92) *

DNI 1200 * * * * * * * * 96 (96) *

DNI 610 * * * * 46 (46) *

DNI 601 * * * * * * * * 48 (46) *

DNI 310 * * * * 23 (23) *

DNI 300 * * * * 23 (23) *

D4 PCIe

vbvoice 10.2 service pack...

Documents