Voice Elements is a .NET API for writing Voice, SMS and WebRTC applications, written by C# developers for C# developers. Voice Elements applications are built to run as windows services. Deploy on either Cloud or Premise with no code changes needed. The best place to get started is to follow one of our tutorials. For simple Programmable Voice and SMS applications, start with the Getting Started tutorial. We recommend using Visual Studio to write Voice Elements Applications.
Benefits of Using Voice Elements
Today and Tomorrow’s Telephony Interfaces:
- Deploy on your own Premise or in our Telephony Cloud. Start in our Cloud and when your premise service is ready, migrate over with no code changes needed.
- Voice Elements provides VOIP SIP through our own native SIP interface HMP Elements. Voice Elements can also integrate with legacy TDM and analog interfaces using Dialogic hardware if your system is dependent on it, although we no longer recommend Dialogic.
Speedy Time to Market:
- Application is developed first – no need to install drivers, boards, software, or telephone circuits.
- “Show the boss” – prove your application before investing in the telephony resources.
Flexible Cloud Telephony Architecture:
- Applications and telephony resources are separate.
- Development can be done anywhere.
- Ease of debugging (step through your voice application using the Visual Studio debugger).
- No need to restart services to implement new versions.
Field Proven:
- Scale – Tens of Thousands of ports deployed.
- Longevity – The Voice Elements core was developed in 1995.
- Experience – we built our first telephony application in 1987.
High Density & Large Scale Experience:
- 5.5 million calls in one day on the Voice Elements engine. Many more examples are out there, just ask our sales crew.
Ideal for Enterprises Already Using .NET:
- Seamless integration into existing business systems and rules.
- Use existing .NET talent from within your organization.
Flexibility & Choice for Cloud or Premise:
- Use our lines and resources with Telephony Bank architecture or install your own Voice Elements Server.
- Switching from Telephony Bank to your own Voice Elements server requires no code changes.
Brings the Ease of .NET Development Tools to Telephony:
- IntelliSense and Visual Studio features make coding quick and easy.
- Get all the benefits of developing in Visual Studio .NET.
Benefits of Using Voice Elements Platform
- Deploy using our cloud hosting service or install your own server and easily connect via SIP– your choice.
- Able to use both SIP and TDM from the same application.
- Fast Time to Market.
- Application is developed first – before the need to install drivers, boards, SIP software or telephone circuits.
- “Show the boss” – Prove application before investing in the telephony resources.
- Provides for “telephony in the cloud” (i.e. “cloud computing”).
- Applications and telephony resources are separate.
- Ease of development (do it anywhere).
- Ease of debugging (step through your voice application using the Visual Studio debugger).
- No restarting of services to implement new versions.
- Targets enterprises using Visual Studio and .NET.
- Ease of integration into existing business systems and rules.
- Easy transition from TDM to VoIP (SIP).
- Switching from a cloud telephony deployment to your own Voice Elements server requires no code changes.
- Design and implement multiple applications without interfering with currently deployed applications.
- Bring state of the art .NET development environment to telephony.
Articles
- Welcome to Voice Elements
- System Requirements for Voice Elements Demo Samples
- Start Coding Voice Elements
- Voice Elements Platform
- Voice Elements Platform Benchmarks
- Benefits of Using Voice Elements Platform
- Getting Started with Voice Elements
- Why Should I Develop My Own Voice Application?
- Free Telephony Software
- Voice Elements Skeleton Project – C
- Class Diagram
- Logging in Voice Elements
- What Are the Deployment Options for Voice Elements?
- What Are the Different Connection Mode Options?
- Licensing Questions
- License Agreement