Introduction

Currently, voice applications are accessed using a telephone device as shown in Figure . A Voice Browser is used to access multiple applications ${A_1,A_2,...,A_n}$ that are hosted on the same Application Server (App Server in the figure). Since all the voice applications are on the same server, and are accessed by the same Voice Browser, it is possible for the Application Server to maintain a browsing history of the applications being browsed. The applications $A_1$ to $A_n$ can provide a link to each other [1] .

Figure: The current deployment and access model.

However, in this architecture, the Voice Browser at the first site will not be able to surf a link from an application in set $A$ to any application in $B$. How to enable surfing such cross-browser links is the problem we address in this paper. By allowing a voice application on one Voice Browser to link to another voice application deployed on another Voice Browser, the reachability of these applications can be significantly increased. This is analogous to the web applications in the World Wide Web, where any website can connect to any other website, regardless of where they are deployed. Continuing the Web analogy further, we have shown that creating and deploying voice applications (called VoiceSites) is as easy as creating a webpage [3]. This is especially important for people in developing countries where Internet/PC availability is low, since creating VoiceSites can be done by speaking through an ordinary telephone. We also described the process of enabling hyperspeech link to another voice application. and presented a Hyperspeech Transfer Protocol to support hyperspeech links [2]. Such an interconnection of VoiceSites open several possibilities for telephony voice applications and can create a web parallel to the WWW, known as WWTW [4]. As an example, a fisherman can create his VoiceSite that has information and pricing of the fishes available with him. He can link his VoiceSite to a payment gateway VoiceSite to enable transactions. Villagers can call his VoiceSite and order a fish and make payment while the fisherman is busy at his lake farm. In a practical scenario, it is likely that these two VoiceSites are hosted at different Voice Browsers. In this paper, we present the concept and architecture of a T-Web Browser. This browser will enable navigation of interlinked voice applications that are deployed across different Voice Browsers. The architecture illustrates that the Browser can be implemented as a special VoiceSite (Section ) and can support standard browsing features such as go-back and bookmark. The T-Web browser can also be implemented on the device itself, but that would require speech recognition support on the device.