| Graphical VOS
Graphical VOS is an object-oriented software development IDE and language
for call processing. Graphical VOS gives you a unique combination
of a proven, high-performance run-time engine, together with the widest
range of supported telephony technologies, user-friendly tools and an easily
learned language.
The Graphical VOS development environment includes the following tools:
Graphical VOS FlowCharter: A tool that lets you build VOS applications
by drawing flow charts and generating VOS source code automatically.
Graphical VOS Debugger: A source-code level, interactive debugger.
VOS Language: An applications-oriented language that supports call processing,
voice over IP, fax, voice recognition, text-to-speech, T-1, E-1, R2, ISDN,
ANI, DNIS, Caller ID, switching, conferencing, call centers, SC and SCX
buses, database access, and much more.
Features - Benefit Overview
-
The VOS language is source and binary compatible across the following
operating systems: Windows 95, Windows NT, SCO-UNIX, and DOS. This unique
feature allows VOS applications to be deployed on any platform protecting
your development investment.
-
With Graphical VOS version 7 and the underlying Topaz architecture, VOS
applications are plug-and-play compliant across ALL Dialogic APIs including
CT Media, TAPI, SR4, DM3 etc..protecting your development investment.
-
VOS includes a full-featured, applications-oriented language that is simpler
and more robust than "C", but it is much more powerful than the simple
"scripting languages" available with some other products. For example,
VOS supports arithmetic and logical expressions with parentheses, "and",
"or" and "not" operators, functions and subroutines with named parameters
and private variables, function libraries for re-usable code and many other
language features. As a language, VOS is very comparable with the xBase
languages or Visual Basic.
-
VOS supports a wider range of hardware and software options than any other
tool. For example, VOS is guaranteed to support any combination of Dialogic
boards and supports over 100 different international signaling protocols,
supports all the latest high density and SC Bus products, etc.
-
VOS can directly read, write and share databases with other applications
in dBase III, dBase IV,Clipper and FoxPro formats. There is also free support
in VOS for the Microsoft ADO and JetDatabase engines which provide access
to a wide range of database file types, including SQL servers,ODBC data
sources and many traditional PC file formats such as dBase, FoxPro, Paradox,
Btrieve, Excel, Lotus and others.
-
VOS supports higher-density solutions than any other tool available today.
For example, VOS has been used to build a 384-port switch in a single
PC. A solution that was built from scratch in three weeks to replace
and existing million-dollar switch.
-
VOS can be used to build almost any call processing application much more
quickly and easily than C/C++ programming but with much more flexibility
and power than most "application generator" products
VERY IMPORTANT: Both Graphical VOS and VOS come with VOSMail, a
full featured voice mail application including the source code, saving
you time and money, as this one of many FREE toolkits available.
CALLSUITE
CallSuite is a set of individually sold ActiveX controls which provides
high-level functions (control methods) for using telephony cards.
CallSuite controls add telephony to your Visual Basic, Visual C++, Delphi,
FoxPro, or PowerBuilder programs. CallSuite controls can be mixed and matched
in any combination to create robust and full-featured telephony applications.
The CallSuite product line includes the following individually sold
ActiveX controls:
| VoiceBocx/TAPI |
for TAPI compliant voice fax modems and hardware |
| VoiceBocx/Analog |
for multiple line analogue voice cards from Dialogic |
| VoiceBocx/Digital |
for multiple line digital ISDN/PRI voice cards from Dialogic |
| VoiceBocx/CT Media |
for support of Dialogic's CT Media API |
| VoiceBocx/IPLink |
for multi-channel IP interface cards from Dialogic (DM3 IPLink) |
| FaxBocx/Dialogic |
for VFX/40ESC+ and VFX/PCI cards from Dialogic |
| FaxBocx/GammaLink |
for single and multiple line GammaLink fax cards |
| ChatterBocx/SAPI |
adds support for SAPI text-to-speech (requires TTS engine) |
| MatchBocx/SAPI |
adds support for SAPI voice recognition (requires ASR engine) |
| SwitchBocx |
adds conferencing support for Dialogic MSI/SC and DCB |
What are the differences between VOS and CallSuite?
Programming
You can create VOS applications with the Graphical VOS FlowCharter,
or you can write them inthe VOS language. Although it's easy to learn,
VOS is a robust, professional-level telephony development language, designed
specifically to handle the stringent demands of telephony servers.
CallSuite product are designed for users who are experienced in one
of the popular Windows- based "visual" languages such as Visual Basic,
Delphi,Visual C++, Visual FoxPro, PowerBuilder and others. With CallSuite
tools,you'll be programming in your favorite visual language--this can
be particularly helpful if you're already an expert VB, VC++, or Delphi
programmer.
Supported Technologies
Using CallSuite's various controls in a visual language you already
know can simplify programming, but the trade-off is that you don't get
support for every obscure feature of every board. With VOS, on the other
hand, we guarantee support for all features of all Dialogic boards. If
we forgot something, we'll enhance VOS and deliver it to you quickly --
very often
within a day or two.
Line Density
Since VOS was specifically designed for telephony, there are enormous
performance differences between VOS and appications written in languages
like Visual Basic, Visual C++ or Delphi. VOS poses no limit on the number
of telephone lines and Dialogic hardware in a single PC.
Platforms
VOS is available with an identical language and highly compatible run-time
engine on Windows NT and 9x, as well as SCO UNIX and DOS. CallSuite controls
are compatible with Windows NT or 9x.
Which is best for my project?
The answer depends on who you are and the details of your project and
other telephony projects you and your company may be doing in the future.
For example, if you are experienced in Visual Basic and have a 4-line
IVR project requiring integration with non-telephony Windows APIs which
can easily be integrated in VB, CallSuite would be probably be the preferred
choice. If you need to build mission-critical switching systems for a debit
card service with 10 T-1s (240 ports) per box which will be processing
millions of call-minutes per month, VOS would be the only choice.
The choice isn't always easy: both VOS and CallSuite are very capable
product lines. The safest choice is VOS: you know that whatever your application
and whatever the platform (Windows, DOS, UNIX) where you need to deliver,
VOS can handle it. On the other hand, if you are experienced with a Windows
visual language and CallSuite supports the features for your application,
then CallSuite controls are probably the best choice for you.
|
