Hi Karl,

You can do this today with the Application Modifier element. It is an Action element with no required settings. It provides the ability to remove session data (among other things), and you can set new session data via its "Data" tab. You can use this element when you would like to set some session data while not necessarily performing some other action, which it seems you are describing.

In regards to concatenation, you can do this via substitution. For example, when creating new session data in this element, you can concatenate a piece of Element Data with a piece of Session Data by using substitution and inserting both of those values side-by-side. At runtime they will be concatenated and stored in the new session data variable you specified.

For calculations, the Math element is generally the way to go (as you mentioned). However, if that is not appropriate for your needs, please provide some additional insight into what you would like to do so that we can give a better recommendation.

In regards to Javascript values, please note that Javascript is executed on the voice browser side. While Call Services will include Javascript you specify in the root document for the voice browser to process, it will never see the result of that processing unless you specify in your VoiceXML that the result should be submitted back. You could create a custom element to submit this data back, or you could also do it with a VoiceXML Insert element (if it's a one-off situation).

Hope that helps,
Vance

Hi Karl,

Thanks for suggesting the JavaScript function reference by element and session data. Could you please provide a few use cases so that we could better understand your suggestion?

Thanks,

John

Hi Karl,

One of the strengths of Audium Call Services is the fact that it leverages a web app architecture and stores session data and performs most processing on the app server; this design takes much of the burden of processing a call and storing data off of the voice browser, and distributes it to the app server.

As a best practice, it is generally not recommended to use your voice browser to perform CPU-intensive processing or to store large amounts of caller-centric data since it could adversely affect other calls (which need CPU and memory resources for many other purposes).

With that said, we have entered the request to provide the ability to make a call to a JavaScript function and store the result in a session or element data variable into our internal issue-tracking system with an ID of CSCsh73482. Should you wish to track the status of this request in the future, please refer to that ID.

Regards,
Roberto