Developing a VisualConnect application is no different from developing a normal VBVoice application. However, when deploying, running, or even testing the application over a data channel there are some settings that need to be set:
Enabling an IVR application to run VisualConnect features requires a runtime data channel license called RTDataLines. The size of this license is the maximum number of data sessions to be served at the same time. Refer to the Runtime Manager documentation to learn about adding licenses to RTM.
While the licenses deoployed on a Runtime Manager are shared by the machines that are served licenses by that RTM, developers may choose to specify the maximum number of data channels a particular machine is serving.
This can be set in VBVoice control panel >> Configuration >> Voice & Data Interfaces. It is also controled by an INI setting in the VBVoice.ini file as follows:
[Data]VisualConnect simplified the development of web applications by providing several built-in HTML and CSS (Cascading Style Sheet) templates that work in harmony with the toolkit. Applications may pick the template close to their desire using the INI setting:
[Data]Further customization to this template may be done by editing the HTML page itself, the CSS file referenced inside it, or/and any of the pictures or logos referenced inside the HTML or the CSS files. This requires knowledge of HTML and Style Sheets, developers are incouraged to contact Pronexus support for guidlines.
Data Sessions are frequently interrupted by an idle time during which the end user is reading the current HTML page and preparing a response or a data entry. This period has a maximum length called the data session idle timeout beyond which VBVoice considers the session ended.
[Data]