CCXML Voxeo 1.0 Development Guide

| TOC

This documentation is for CCXML 1.0-Voxeo, which has been superceded by CCXML 1.0-W3C. The CCXML-Voxeo platform is not being updated any longer. The CCXML 1.0-W3C version, however, has many new features and is actively being enhanced. If you're writing a new CCXML application, you should use CCXML 1.0-W3C. Click here for the CCXML 1.0-W3C documentation.

Platform issues and limitations

This section will serve to keep you informed of any open bugs with the Voxeo's Call Control XML implementation. Please make yourself aware of these bugs and limitations before coding your application, else you might end up having to rework a sizable portion of code.

HTTPS support

HTTPS is supported when the developer has a Tier 1 certification from a known vendor, such as Verisign . Not sure if you have a certificate that will work with VWS? Bring up the url in a web browser; if you see a dialog box, then you will be out of luck, and will need to look into purchasing a valid certificate.

Reporting

In the Account Manager, you will see the option to get an Excel spreadsheet that reflects the network traffic that your application has logged for a specified timeframe. Do be aware that it does take bewtween 1 to 3 hours for the data to trickle down to the report, so a call made to your application at 12 noon might not show on the report for another three hours.

Transfer Encoding

It is strongly advised that you make certain that your HTTP transfer encoding headers so that they do NOT contain the 'chunked' value, as this can cause severe performance issues, especially with ASP and .NET documents. Note that the default setting for IIS has this set to 'chunked' so it is in your best interests to send across a 'blank' value for this to alleviate any potential performance issues.

Maximum Filesizes

the maximum filesize for a CCXML document on the Voxeo platform is 100k; exceeding this limit will bring about a very noticable error in the logger that indicates this limit. However, it is suggested that you keep your documents to no more than 20k, else you may see application performace degrade. Can we up the limit? Most assuredly not, as this is a realistic limit for allowable size, and even if the limit were raised to 500k, the performace of the application in question would be virtually unusable in any kind of 'real world' production environment.

Open CCXML Platform bugs

Issue: The use of the <script> tag is currently unsupported on the Voxeo platform. however, you may still perform basic ECMAScript operations within variable values.

Status: Pending resolution from Voxeo, (7/18/03).

Issue: The <exit> element is currently not throwing the 'ccxml.exit' event when it executes.

Status: Pending resolution from Voxeo, (7/20/03).

Issue: <redirect> element non-functional. At this time, it is slated for fixing, but a timeframe has not been solidified by the Engineering team.

Status: Pending resolution from Voxeo, (7/20/03).

Issue: <disconnect reason> element/attribute combination is non-functional. Note that the element itself does work as defined in the specification, but the 'reason' attribute is disabled at this time.

Status: Pending resolution from Voxeo, (7/20/03).

Issue: <authenticate> element completely disabled. At this time, no authentication is required between the hosting servers and the Voxeo network, although this might change in the future.

Status: No resolution scheduled by Engineering.

Found a Bug?

We strive to keep an accurate listing of known CCXML bugs and platform issues detailed in this section, but nobody is all-knowing. If you think that you have come across a legitimate bug, please let us know, and we will see about scheduling a fix. Barring immediate resolution of the problem, we will at the very least document your findings here for the edification of all.

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page

Getting Support Help

| TOC

| C: Events & Errors