by the way, there is a standard Text To Speech API and reference
implementing for Java. I know Leap Wireless uses that with an EJB
container for some internal applications. I can't go into details, but
I do know of cases where it scales just fine.
peter
On Fri, 9 Jul 2004 11:19:23 -0700, Darshan
I think I get a better picture. I was guessing it might be a Text To
Speech application. I use to work on a wireless platform and one of
the features we explored was converting emails to .wav files and send
them to the user.
in my experience, the wav file would have been sent to a WAP phone
with a
Hi Peter,
I suppose there is some confusion.
I believe you got it right, that the Media Server is the one which
will interpret the VXML pages and not the Application server.
But these VXML pages wont have any SPEECH in it. Instead they have
specific TAGS related to speech
for e.g a snipplet from a
On Thu, 8 Jul 2004 18:59:23 -0700, Darshan Rawal <[EMAIL PROTECTED]> wrote:
> Hello Peter,
>
>
> I completely agree on this, but this interpretation of VXML pages is
> going to happen on the Media Server side. Hence as of now I am just
> concerned with generation of VXML pages and transporting th
Hello Peter,
Nice to know that somebody replied. Was really desperate to get some inputs!!
My replies are included below.
On Thu, 8 Jul 2004 21:39:23 -0400, Peter Lin <[EMAIL PROTECTED]> wrote:
> from where I am sitting, sounds like the project doesn't have enough
> information to make a good dec
from where I am sitting, sounds like the project doesn't have enough
information to make a good decision. Why move from MML/TCP to
VXML/HTTP?
if you read my performance article on the resources page, XML is very
CPU and memory intensive. Even with XStream java-xml binding library,
handling moderat
We implement a Messaging PLatform for Voice Applications.
Our current platform has 2 Major Components as shown below:-
Media Server <--- MML/TCP-IP ---> Application Server.
We want to move to a new architecture for our Application Server where
the interaction between App Server and Media Server i
