New Developers are often overwhelmed in trying to understand all of the new words they see in Voice Elements. This is not meant as a complete guide on what each of these topics is, and what it is capable of, but is meant to provide a brief definition or overview of what each item is.
Voice Elements is the programmatic interface between your .NET application and the Telephony Layer (usually HMP Elements). Voice Elements works in conjunction with HMP Elements, our SIP Stack. (In legacy platforms, it was used with Dialogic HMP, and Dialogic Boards.)
Voice Elements Platform
HMP Elements and Voice Elements make up the Voice Elements Platform. HMP Elements is responsible for the lower level transmission of packets, and Voice Elements provides the programmatic interface between your client application and HMP Elements. Read more in our article Introduction to Using Voice Elements.
Voice Elements Developer
Voice Elements Developer consists of the Voice Elements DLLs that allow you to write your Voice Applications. The Voice Elements Client DLLs are responsible for communicating between your application and the Voice Elements Server.
HMP Elements is the SIP stack component of the Voice Elements Platform. It is responsible for transmitting and receiving both SIP (Call Control) and RTP (Audio) packets. By contrast, Voice Elements provides a programmatic interface between your .NET application and HMP Elements. For more articles about HMP Elements and its powerful features, see HMP Elements.
It is reliable, and is capable of handling more than a thousand concurrent calls. It is also flexible, and can be used inside of a virtual machine.
Border Elements is our programmable Session Border Controller. This software implementation runs as a Windows Service and accesses a SQL Server database for making call routing decisions. You can quickly and easily set up Border Elements and unlock all of it’s features. For more information about Border Elements, features and applications, see the article Border Elements – Our Powerful Session Border Controller (SBC).
Mobile Elements is a VoIP mobile application which runs on Android, iOS and Universal Windows platforms. This application has been built using Xamarin forms cross platform development environment which is a built-in feature in Visual Studio. The Mobile Elements application supports outbound and inbound calling facility using the Voice Elements server platform. For more information, see our article Mobile Elements Client.
WebRTC allows you to use your browser simultaneously as a web browser and as soft phone. By combining the flexibility your own webpages with WebRTC you can provide a complete solution to your customers. Read more in our article WebRTC – Getting Started.
Conferencing is the ability to have 3 or more individuals on a single phone call. Conferencing can be used for both phone conferences, with multiple active participants, but also for coaching and pupil mode (allowing for a coach to tell an operator what to say without the third party being able to hear the coach).
One client won the Guiness Book of World Records for the largest teleconference at nearly 17,000 people on a single call – all built on HMP Elements.
The Fax Resource allows you to both make and receive faxes.
The Voice Resource is a stand-alone resource that when routed to a Channel Resource allows you to perform various functions such as Plays, Getting Digits, Speech Recognition, Recordings, etc.
The Telephony Server represents your connection to a Voice Elements Server — whether it be your own instance, or a hosted Voice Elements Telephony Bank. There are several useful functions on the Telephony Server class. See Server Configuration for more information.
If you have any questions, please feel free to contact email@example.com
TTS (Text To Speech)
TTS Stands for Text To Speech, and allows you to play different strings to a user. This can be useful for customizing greetings. Voice Elements supports SAPI 5.3 compatible TTS voices, along with Microsoft Speech Platform Text To Speech Voices.
HMP Elements is licensed per port. One port can be considered as an equivalent to a single telephone line. If you are licensed for 500 ports, you may make 500 concurrent calls.
The phone number that the call was received on.
The phone number of the caller.
The Channel Resource is roughly equivalent to a phone line. The Channel Resource class provides methods for placing calls, answering calls, and disconnecting calls. In addition, it contains information about calls such as DNIS, and ANI. It is a base class, which means that if you use it instead of a more specific class (such as a SipChannel), your code is portable between TDM based Dialogic equipment, and SIP based resources (such as HMP Elements, or Dialogic HMP). You’ll want to read our developer documentation for more information.