GENBAND is a global leader in real time communications software solutions for service providers, enterprises, independent software vendors, systems integrators and developers in over 80 countries. It recently released the Kandy cloud communications solution.
How does Kandy enhance software applications with cloud-based features?
Carlos Aragon, director Kandy/UC Solutions Marketing at GENBAND, said: “The key term is not ‘cloud-based features’, but ‘cloud-based real-time communications’. Kandy is a communications platform-as-a-service (cPaaS) that provides APIs and SDKs to allow communication service providers (CSPs), enterprises and independent software vendors (ISVs) to embed communications within their applications and business processes. Kandy allows these players to make communications an integral part of their applications.
“For example, if you are working on your CRM platform and you need to contact a customer, typically, you would have to find the phone number and call the customer from your phone or softphone. Wouldn’t it be better to just click on the customer name in the screen and have that call happen automatically from within the CRM application? That’s exactly what Kandy enables, your applications can now trigger voice or video calls, messaging, co-browsing, collaboration and many other communication related activities, and you don’t need to be a communications engineer to make that happen or have an expensive communications network to terminate the calls.
Hasn’t it been long claimed that real-time communications will revolutionize the telecoms and technology worlds? Is this any closer to that?
He agreed that the the term revolution is very frequently abused. “We prefer to use evolution. For us, it is the natural step in ICT, first the integration of information technology and communications happened on the network level, by migrating voice and video to IP and using the same transport network to deliver them. We moved from dedicated telephone wiring in our offices to sharing the same Ethernet cables to connect our phones and computers and the analogue and PRI trunks have given way to SIP trunks over an IP link.
“The next step on this evolution was to have the integration at the application level. Real-time communications have already been consumed as applications for years (Skype, WhatsApp, Yahoo Messenger, MSN. Google Talk, and the plethora of Unified Communications Soft Clients in the market), but true integration of those components into business flows and applications never happened.
“Kandy bring us closer to that world, where communication is a natural part of our everyday applications. where a phone line is not tied to a physical telephone, where one can start a conversation with anyone, no matter which device (old and new) they are using from the device or application we choose. That’s what Kandy enables.”
SaaS and PaaS are also related. How is Kandy really different?
He noted that SaaS, PaaS and Kandy are related indeed. “Kandy is PaaS, more specifically, cPaaS (communications platform-as-a-service). With SaaS you obtain a fully functional application that you consume from the cloud (Salesforce.com, Workday, SAP C4C, even Facebook can be qualified as SaaS). With PaaS you use a cloud service as building material to build your final application.
“You can’t just start using PaaS because it doesn’t provide you with an application to consumer directly, instead, it provides you with an API and/or SDK to allow you to use its services within your application. But you have to develop on top of it. In the end, the difference between SaaS, PaaS, IaaS and on premise solutions is who is responsible for each part of the solution.”