Skip to main content

Scheduling an Audio conference with a single HTTP Request

When Anenth of TripThirsty blogged about creating a conferencing app overnight, that started me thinking. Since KooKoo also provides a simple <conference> tag, what is the least amount of code we need to create a conference scheduling app.

Since we all live in the cloud :), I did not want to host my code anywhere and it should be very minimal.

KooKoo takes care of telephony, so I searched for a scheduling service. Sometime back, I used to use Momentapp, but looks like it is down now. So finally I zeroed in on EasyCron. They had a good enough API and I signed up for a free account. Now I had all the ingredients in place and all I had to do was a cook up a single HTTP request recipe.

So without further ado, the HTTP request to schedule an audio conference:

------------------------------------------------------------------------------------------------------------------------

http://www.easycron.com/rest/add?
token=[your easy cron token]
&cron_expression=[cron expression to schedule the call]
&url=http%3A%2F%2Fwww.kookoo.in%2Foutbound%2Foutbound.php%3Fphone_no%3D[phone number to invite]%26api_key%3D[kookoo api key]%26outbound_version%3D2%26extra_data%3D%253Cresponse%253E%253Cconference%253Eroom_435%253C%2Fconference%253E%253C%2Fresponse%253E&email_me=0
&log_output_length=0
&testfirst=0  

--------------------------------------------------------------------------------------------------------------------------
Note: The KooKoo URL is URL encoded. You can find details about the outbound request here. The cron expression parameter takes a simple cron expression. Details of cron expression are here. Replace the values in [] in the above request with your account details.

What we are doing is simple, we are pipelining KooKoo outbound request which places a caller into a conference with the API request for Easycron to schedule the request. So at the specified time, EasyCron, makes a HTTP request to KooKoo which places the call and pulls the participant into a conference.

So there you have it, a single HTTP request to schedule an audio conferencing call. Well, its not exactly a single request as you have to make one request for every participant you want to add to the conference, but hey, you get the idea.

So go ahead and sign up for KooKoo and start your conferencing solution. Call costs are at 40ps/min local and 70ps/min STD.

Popular posts from this blog

Integrating Arborjs with Angular to create a live calls dashboard

Arborjs  is a cool graph visualization library. Angular  is one of the best JavaScript frameworks and we have been using Angular in a lot of our front end development. When you handle millions of calls, proper visualization becomes very important. Without proper visualization, you can get lost in the mountains of data. So we spend a lot of time to come up with good visualizations to represent the data. Since we loved the cool way in which Arbor represented graph data, we could not wait to hook it up with Angular. Because of Angular's two way data binding, when you hook up Angularjs with Arbor.js you can get a dynamically updated visualization of graph data with cool animations. To give back to the community, we have put up the code online at Github . Basically we have created an Angularjs directive for Arborjs. Please feel free to fork the code and add extensions and use it for your own visualizations. The code is self explanatory with comments inline. Best way to get s

First Post

In this blog, I will be talking about my experiences in trying to build a cloud telephony platform , KooKoo . Along the way I will also be talking about different design choices I made, good programming practices and the IVR domain in general. For technoratti: NNFJW8EW86C3

KooKoo Contact Center integration with WhatsApp

WhatsApp announced the launch of their business API yesterday. This is a big deal. A lot of businesses have been asking for WhatsApp integration and now its a possibility. Twilio has already launched an integration . Won't be long before we see a lot more integrations pop up. The most obvious use case is for support chat bots, alerts and reminders. But we at Ozonetel believe one other use case will become the dominant use case, WhatsApp as a support channel with human agents. We believe WhatsApp will become a dominant channel in contact centers world wide. There are multiple reasons for this: WhatsApp is ubiquitous. Everyone has the app. WhatsApp interface is well known to all customers. It is feature rich. You can share audio, video, location etc in the app itself. You can integrate bots for repetitive tasks. Being the leaders in cloud contact center solutions, we at Ozonetel knew that we had to integrate with the WhatsApp channel as early as possible.