jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jakarta-taglibs Wiki] Update of "ReusableDialogComponents/Tutorials/TryingOut" by Stu Robertson
Date Tue, 14 Jun 2005 13:10:37 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-taglibs Wiki" for change notification.

The following page has been changed by Stu Robertson:

The comment on the change is:
Initial cut.  Focused on voice interpreter setup only.

New page:
'' 'cause you probably don't have a voice interpreter at home...''


You have a simple project containing your own RDCs, or one of the example WARs from the RDC
distro.  You have an application server like Tomcat setup and ready-to-go.  You've heard building
voiceXML applications is basically like web development, and you have your web browser.  Oh
wait!  This is a voice UI, so your html browser won't help...  To see RDCs in action, and
to test a voice application in its native mode of operation, you need a Voice Interpreter.
 Which you probably don't have.

Fear not.  If you have the ability to expose your application via the internet, poking a hole
through whatever firewall hides your development environment from the world, there's a readily
available option.  Many major voiceXML hosting companies provide free test environments. 
With very little work, you can point their voice browser to your application, and then call
into it to test your application.

I've used both [http://cafe.bevocal.com Bevocal Cafe] and [http://community.voxeo.com Voxeo],
and there are others.  I've found Bevocal's tools to be very straightforward, and more importantly
to me, their server logs are easy to read and find.

Here's a brief overview of the steps required to get setup.  ''TODO: add more detail''

* Make sure your application is visible via the internet.  If your ISP gives you a dynamic
IP, consider a service like [http://dyndns.org DynDNS.org] to get a domain name.  If you're
behind NAT you'll need to configure your router to use port forwarding to the box running
your application.  When you're done, the  address might look something like http://your-hostname.dyndns.org:8080/yourAppName/entryPoint.jsp.

* Sign up for a developer account at the voiceXML hosting site of your choice.  The two I
listed above work well.

* Follow their instructions to configure their voice browser.  This is simple.  You really
just tell it the endpoint that you setup above and you're done.

* Call into your application.  They'll give you a PIN and userID.  You can use a real phone,
you can use Skype, you can even use a free SIP phone if you take the time to set it up (Voxeo
has nice support for this).

After you've called in and stepped through the application, you can visit the hosting site
and view the log output generated from your session.  It should show you all of the interactions
between the voice interpreter and your application, including recognition events, fetching
resources, etc.

It's easy to use the RDC test jsps included with the distribution.  Just set the application
entry point to the jsp you want to test.

'''Big Caveat For Now''' - as of June 14th, most of the RDCs do not work with the Nuance grammar
compilers these hosting providers use.  Exceptions are select1 and possibly a few others.
 We're working on that.  If you want to help, jump into the discussion at the taglibs-dev
mailing list.

To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org

View raw message