TERAVoice is a high-performance multi-threaded windows system-service offering a unique and scalable telephony platform. The system can be easily expanded by purchasing additional licenses for lines and mailboxes.
TERAVoice supports a broad range of telephony hardware and three CAPI based VoIP (H.323 and SIP) stacks. The supported hardware can be asp:Panelided in three basic categories:
- TAPI based hardware
- CAPI based hardware
- Voice Modems
More information about the supported brands and devices can be found on our Hardware Compatibility List. Devices can be bundled into Device Groups to simplify management and administration.
All incoming calls are handled by Call Handlers which offer specific call processing capabilities. The call handler that is designated to handle a specified call is determined by its Routing Parameters. TERAVoice offers four types of routing parameters:
- Device Routing
This type of routing assigns the appropriate call handler depending an the telephony device or line on which the call occurs
- DTMF Routing
Most analog PBX systems can signal the station number from which a current call has been redirected to the telephony server by transmitting DTMF tones during the first few seconds of the call. This technique is also referred to as "In-band signaling"
- MSN Routing (Routing by Called ID)
This type of routing is typically used in digital networks. Telephony hardware can service different extensions (called MSN's - multi subscriber numbers in ISDN) on a single physical line. This MSN which is transmitted as the Called ID on TAPI devices can be used to assign a call to a distinct Call Handler
- Redirector Routing
This type of routing is very often available in digital networks as well. If a call which is targeted to a certain extension is redirected to the telephony server (either by an explicit redirection the user has set on his telephone or by implicit redirection through PBX ringing groups) the PBX often transmits the original call target as the 'Redirecting Party Number'. This is an excellent option for easy mailbox assignment in digital networks.
The following types of call handlers are available in TERAVoice Server 2004:
A detailed description of all Call Handlers can be foundhere.
TERAVoice supports all kinds of Call Transfer as long as the transfer method is supported by the hardware device:
- Attended Call Transfer
- Unattended Call Transfer
- 3-Party Conference
- In ISDN networks with CAPI boards: ECT-E and ECT-I
- Software Bridging
Software bridging can transfer a call between different networks or within one network in case the hardware, network or PBX does not support call transfer. Software bridging also works with VoIP targets.
Users can be notified about new calls or new messages with various options:
- E-mail notification of new messages
An e-mail message is sent to the configured e-mail address each time a new message is recorded. An audio file of the message is attached to the e-mail
- E-Mail notification of new calls
For those calls where the caller does not leave a message a notification e-mail can be sent to a different e-mail address. This allows the subscriber to permanently keep up with all received calls. This function can be also used for creating call-logs in the messaging system. As an example a MS Exchange Public Folder's e-mail address can be used in order to create a call log in this folder.
- SMS or pager notification
This method allows receiving notification messages on your mobile phone or pager either for all calls or only for those with a recorded message. The sender number for SMS messages can be set to the number of a remote control Call Handler for quick dialing into the remote control box
- MWI notification
Many PBX systems allow signaling new messages via the MWI-Indicator (Message Waiting Indicator) on their PBX telephones. This is done by dialing a certain special number for switching on and off.
- TERAVoice Client Application
TERAVoice comes with a small Windows client application which loads in to the system tray. New messages are indicated via the tray icon and can be listened locally via the computer system's speakers. This requires Windows network access to the TERAVoice server.
TERAVoice comes with a plugin architecture which allows to do a reverse lookup on incoming calls. Currently an Active Directory plugin is delivered with TERAVoice, more plugins for MS Exchange contacts, general database lookup, general LDAP lookup and some phone number CD will be provided.
Instead of playing voice prompts TERAVoice can also play text messages that are synthesized by a Text-To-Speech engine. TERAVoice supports all Microsoft SAPI 5.1 compatible TTS engines.
TERAVoice can be administered and monitored locally and from remote systems. Administration is implemented as a Snap In for the Microsoft Management Console (MMC) and can be used like any other Windows administration tool.
An integrated monitor shows current activity with detailed call status information for all lines. Central logs for handled calls, informational and error messages are provided as well. TERAVoice can log information to Windows EventLog, TERAVoice internal log as well as a text file and even sent error messages by e-mail to the administrator's e-mail address.
TERAVoice currently offers support for both English and German language for windows user interface, documentation and all audio files. User interface language is depending on the current language setting of the currently installed operating system.
The audio interface language of system audio messages can be configured on a per-mailbox basis, in such way that user A can get English language remote control menu while user B can listen to the same menu message in German.
Further languages are planned and will become available for download as soon as available. Other languages for system voice messages can also be created by the customer.
Language support for voice menus or IVR modules can be implemented as desired.
TERAVoice supports the following standards and technologies: