General and Technical Aspects of Our Software
We support configurations employing the 16 port Dialogic D/160SC-LS (analog) card on the low-end, incrementing through the family of non-retired analog, digital T-1/E-1 Dialogic/Intel voice telephony cards, supporting conferencing. The maximum amount of concurrent call traffic on a system is only limited by:
Our products are easy to install, maintain, navigate and can be run on any standard desktop PC, half-height tower, or rackmount passive-backplane system. Simply...
Our products (technical) - All of our programs are less than 200K in size, designed in state-machine design, in the "C/C++" programming language. Our executable code is optimized for speed and (operating system) resource management. We don't use 3rd party libraries or development kits. Instead, we program directly over the Dialogic device drivers, for pure performance, using the native Dialogic API's. We don't use the overhead of ActiveX controls or libraries in our designs, either. As a result, we're able to capture, process and display realtime channel events regardless of call traffic saturation on high (dense) channel capacity deployments. These are not novice designs. Our products are industrial grade. We try to maintain a consistant "look and feel" across our product line, in both the interface and the internal features (ads/mailbox, live 1-on-1, call-forwarding, and admin. functionality), where applicable. Our hope is to minimize the learning curve, when migrating from one product to another. All of our systems include a backdoor/admin. channel. The "backdoor" is accessed on channel 1 and is used to setup/maintain accounts and monitor/supervise system activity. Many of the features, accessed by the admin. channel are also available, in the form of pop-up windows, from our menu bar, for remote/local desktop management. Some of the intuitive features found in our products include:
|