08-17-2017, 12:01 AM
[attachment=4559]
This article is presented by:
C. Mohit, Xiaotao Wu, Venkatesh Krishnaswamy
Avaya Labs Research, 233 Mt. Airy Road, Basking Ridge, NJ 07920, USA
ABSTRACT
Google Wave [1] is a new tool developed by Google for communication and collaboration on the web. It combines different communication means, such as email, instant messaging, wikis, web chat, social networking, and project management in one in-browser communication platform. It was first announced in May 2009 and is expected to be released until later in 2009. It is open sourced and has many good features such as embeddability, extensibility, and drag and drop file sharing. But among all its features, it misses one important function that is critical for enterprise users: it cannot interact with enterprise voice communication networks. To overcome this drawback, we proposed a viable way of integrating enterprise voice communication functions into Google wave. The integration consists of three parts: monitoring voice communication events and presenting the events in Google Wave, bringing Google Wave functions to enhance call handling, and allowing users to control calls inside Google Wave. Each step has its own challenges. We discuss these challenges and our solutions in detail in Section II, IV, and V. This paper is organized as below. In Section II, we discuss some related work. Section II discusses how to monitor voice communication events in Google Wave. Section IV discusses new call handling features we can bring in Google Wave. Section V addresses how to control calls from Google Wave. Finally, Section VI concludes this paper and discusses our future work. In this paper, we base our discussion on Session Initiation Protocol (SIP) [2] for enterprise communication.
Related Work
We first introduce some terminologies in Google Wave. In Google Wave, a threaded conversation can be referred as a wave . A wave consists of one or several wavelets , which is like a single instant messaging (IM) conversation. Each message in the conversation is called a blip , and the content of the blip is called a document . There are two ways to extend Google Wave: gadgets and robots. A gadget is an application which users can participate with, for example, a chess game can be a Google Wave gadget. A robot is an automated participant within a wave. It can talk to wave users, check the content of a wave, and perform actions to alter a wave, such as inviting another user to join the wave. The idea of using robots allows developers to add arbitrary features to a particular wave. In our implementation, we use Wave robot to monitor communication events and control calls, and use Wave gadgets to provide additional call handling functions. There is an existing Google Wave extension called Twiliobot [3] that provides click-to-call function in Google Wave. The communication capability of Twiliobot is very limited. It simply translates the click-to-call number into a URL pointing to Twilio server, which handles call control logic. Once the user clicks the URL, the communication logic is completely out of Google Wave domain. There is no communication events sent back to Google Wave from Twilio server. In our approach, our Wave robot can monitor communication events, update call states based on the events, and apply appropriate call control actions.
Related Work
We first introduce some terminologies in Google Wave. In Google Wave, a threaded conversation can be referred as a wave . A wave consists of one or several wavelets , which is like a single instant messaging (IM) conversation. Each message in the conversation is called a blip , and the content of the blip is called a document . There are two ways to extend Google Wave: gadgets and robots. A gadget is an application which users can participate with, for example, a chess game can be a Google Wave gadget. A robot is an automated participant within a wave. It can talk to wave users, check the content of a wave, and perform actions to alter a wave, such as inviting another user to join the wave. The idea of using robots allows developers to add arbitrary features to a particular wave. In our implementation, we use Wave robot to monitor communication events and control calls, and use Wave gadgets to provide additional call handling functions. There is an existing Google Wave extension called Twiliobot [3] that provides click-to-call function in Google Wave. The communication capability of Twiliobot is very limited. It simply translates the click-to-call number into a URL pointing to Twilio server, which handles call control logic. Once the user clicks the URL, the communication logic is completely out of Google Wave domain. There is no communication events sent back to Google Wave from Twilio server. In our approach, our Wave robot can monitor communication events, update call states based on the events, and apply appropriate call control actions.