|
Back in July 1999, TMC Labs reviewed Envox’s CT Studio 3.0 and found out first hand that this application generator was a quality product for building custom communications solutions for the enterprise or the public network. We were able to create simple IVR and unified messaging applications in a short period of time. With a little more time, we could have created much more complex solutions. For this reason, we were looking forward to reviewing the latest version, now just called Envox 4.0, to see how well the product has kept up with newer technologies from such industries as e-business, Web automation, wireless, and Internet telephony. We discovered many new developmental tools integrated into Envox 4.0, which is neatly tucked into the graphical development interface now called Envox 4.0 Studio. Likewise, the Envox 4.0 Communications Server, an interface used for the execution and maintenance of the applications, was still intact with very few changes from its earlier version.
INSTALLATION
To test Envox 4.0 in our labs, we placed an Intel D/240PCI-T1 board into a Windows 2000 Server, which we had installed on a CTI-400D industrial computer from Siliconrax-Sliger (both of these products are reviewed separately in this issue of
Communications Solutions). From there, we installed the driver for the Intel board, which we obtained from one of the two Envox 4.0 CDs. In addition to the drivers, the entire 5.01 Intel (formerly Dialogic) system software package was included. We could have chosen to install the CT Media 2.1 drivers instead, if that had been what we needed. When installing the 5.01 drivers, we chose the Custom option so that we could add the GlobalCall API package and ISDN package with what is normally included with the typical option. For Envox 4.0 to work properly, the GlobalCall API must be installed. Since we had a T1 board, we had to include the ISDN package to successfully synchronize with the Gordon Kapes’ T1 simulator we were using. After the installation was finished (or so we thought), we rebooted the computer only to find that the software had not actually completely installed. We went through the entire process again, uninstalling and then reinstalling the Intel drivers. This time, it installed correctly. When starting the service for the voice board, we had to make sure that the Envox 4.0 Communications Server was not open. If it was, the service would issue an error message and refuse to connect. As for installing the Envox 4.0 software, this was done easily and quickly.
DOCUMENTATION
Although there are no printed manuals, there is plenty of documentation that can be accessed through Acrobat Reader from either of the two Envox 4.0 CDs or from their Web site. The manuals consist of a main manual, discussing the whole Envox 4.0 platform, the Communications Server manual, and the Studio manual. While some of the information from the main manual overlaps with the others, there is still quality information to be obtained from all of them. We also found it useful that Envox provides general tutorial films about certain aspects of 4.0 through Lotus ScreenCam.
However, it is the help files that really separate Envox’s documentation from other (inferior) examples of product literature. The help files are completely context-sensitive for both the Communications Server and for Studio. For example, a user only needs to press “F1” on his keyboard to discover the functionality of that particular building block for every block that’s placed on the Envox 4.0 Studio interface. This is immensely useful when first learning to build an application.
Samples of short scripts used to develop specific applications are also included with Envox 4.0 Studio. These samples help users figure out the logical design for the applications. While each specific block is explained rather well, we feel there is still a need to talk about each sample script more generally so that the user could understand the script as a whole instead of by each individual block. The notes included in these samples help to this end but sometimes still do not quite teach the user the entire general concept of the more complex sample scripts.
FEATURES
There is an abundance of features for Envox 4.0 so that just about any communications application can be created. The following is a list of the major features added for the latest version of the product:
-
XML support — twelve new building blocks for creating XML documents and XML nodes, setting XML attributes, and transforming XML documents; VoiceXML for creating voice portal solutions.
-
Use of WML for designing WAP applications.
-
Added SS7 protocol and ATM support to go along with other telephony
protocols and interfaces, including IP, ISDN BRI/PRI, T1/E1, and analog.
-
Compliant with CT Media for building open communications applications with multiple software and hardware vendors to coexist on one server.
-
Can integrate with IMAP4 e-mail servers through ten new building blocks and four new building blocks for support of X.25.
-
Support for the Nuance speech recognition technology upgraded to version 7.0.
-
ISAPI plug-in enables any request for any URL (HTTP, WAP, etc.) to be redirected to Envox via TCP/IP for on-the-fly response.
OPERATIONAL TESTING
Our first tests of Envox 4.0 resembled those that we completed when we reviewed CT Studio 3.0. After a look at the latest version, we can safely say that almost all of the information stated in the Operational Testing section of the earlier review is still accurate. We again created simple telephony scripts in the same “connect the block” fashion as last time and called into the system through the T1 simulated line to make sure our script was working. We then checked the progress of the call through both our phone and the Envox 4.0 Communications Server interface. To test the ACD functionality, we kept one telephony call active on the first port, then set up the same script on the second port, and dialed. The second phone connected and rang. Because of the set up of the T1 line, the ACD could only be used sequentially instead of skipping, say, from port one to port three if port two had no application available to use.
The real fun began when we started to examine scripts to create newer applications, such as for XML, WAP, or integrating IMAP4 e-mail servers. We looked at the blocks associated with these new applications and tried to formulate strategies for creating a successful application with the help from samples available in the program. We also checked our newly created applications for any errors before building the script. While it took some time to understand the new blocks in general, to handle the variables and expressions associated with them, to develop a “script within a script,” and so on, these new blocks do not pose too much of a hurdle for developers familiar with Envox’s application generator. The new blocks needn’t overwhelm novices, either. The help files should aid all developers as they build applications. Overall, these new applications integrate seamlessly into Envox 4.0 Studio, whose interface has changed little from what it looked like two years ago. In Studio’s case, this is fine since the interface is still top-quality.
On the other hand, while the interface for the Communications Server has not changed much, it has not stood the test of time quite as well. While still not bad, it could benefit if the interface were more compact or at least had a hierarchal form to it. Right now, we think that expanding the window to anything more than eight ports on the screen makes the interface clumsy, although doing this is not necessary thanks to the page down/up buttons. Overall, the interface for the Envox 4.0 Communication Server still does what it sets out to do —show the status of the port and the application running on it; configure certain characteristics of the drivers, boards, and ports; and perform other functions as well, such as the single step debugging tool for step-to-step script execution.
ROOM FOR IMPROVEMENT
We feel that Envox 4.0 has certainly improved on its former versions, especially in its updated feature set, but some of our suggestions from the last review still apply. For one, Envox should offer reviewers or other product testers the option of using a software-based telephony simulator for testing without the use of an Intel voice board.
For the Envox 4.0 Studio interface, an undo function should be added to the edit menu to rectify rudimentary mistakes. As for the Communications Server, the interface should at least include “tool tips” that would tell what each icon represents, but slightly more radical changes could lead to a cleaner and more efficient interface. Maybe a more hierarchal approach could be taken, such as using a variation of the uniform Microsoft Management Console (MMC) snap-in model, so that all the ports for a T1 or E1 could be maintained efficiently on one readily viewed screen.
CONCLUSION
With their latest release, Envox has graduated from being primarily a CTI-related application generator to being able to build virtually any communications application from the ground up. It is still well-designed and user-friendly, and its new features combined with a solid foundation make it one of — if not the best — application generator on the market today.
[ Return
To The November 2001 Table Of Contents ] |