Re: [SIPfoundry] SipX VXML and TTS
> -----Original Message-----
> From: discuss-bounces@xxxxxxxxxxxxxxxxxxx [mailto:discuss-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Gary
> Sent: Thursday, December 28, 2006 7:13 AM
> To: discuss@xxxxxxxxxxxxxxxxxxx
> Subject: [SIPfoundry] SipX VXML and TTS
>
> Forgive me if I missed something obvious, but the following is my
> impression when looking to see what sort of VXML related functionality
> SipX supports(I hunted around with google and the website)
>
> SipX uses SipXvxml to provide VXML support.
>
> SipXvxml is based on openVXI 2.0 and was never upgraded to 3.0?
>
> openVXI is a dead project in the open source community, the creators
> having taken the functionality they needed and incorporated it into
> their own commercial offerings. So I'm guessing there is no planned
> upgrade of what works into what might work to go to for sipXvxml?
>
> I can't seem to find a list of which vxml specs SipXvxml supports, am
I
> missing the obvious here? Can someone tell me where that is?
>
> SipXvxml provides rudimentary support for TTS with it's own built in
> functionality that only provides english support. While there is
> interest in upgrading that to use another engine, it requires
upgrading
> to openVXI 3.0, testing, and than testing integration - and those who
> are interested in TTS are too impatient to actually do all that
testing
> and fiddling and to help out?
>
> SipXvxml seems to be a somewhat dead project, as it is not listed on
the
> wiki as it's own project anymore, instead the functionality it
provides
> has been pretty much absorbed into SipX.
sipXvxml is stable and quite robust as a server side media server
solution, but you are right, there are some architectural issues.
Separating it from sipXpbx would be necessary so that it can run easily
on separate HW (this could be done fairly easily). Also, its Web UI
cannot be easily localized unless you recode the CGIs individually per
language. Use of Apache is too heavy and the Apache integration is non
standard. Also, media server cannot be networked as there is no
separation of media processing from storing media files. Adding
additional codecs is another item.
--martin
>
> Is this a fair summary of the state of things as of now?
> _______________________________________________
> discuss mailing list
> discuss@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/discuss
> List Archive: http://list.sipfoundry.org/archive/discuss
