Current issues with the Avaya VoiceXML feature
Application developers should consider the following issues when developing VoiceXML applications:
- Redefining a variable that was set previously changes the value of the variable.
- Formats of data in the say-as tag must conform to the Text-to-Speech engine being used. See the appropriate vendor documentation for SSML and say-as tag support.
- If a VoiceXML application using Natural Language Speech Recognition (NLSR) calls a TAS application that uses NLSR, the speech functionality will not be available to the TAS application. The reason for this is that the AvayaVXI retains the license to use NLSR, and does not pass this license to the TAS application.
- session.connection.local.uri contains the same value as session.telephone.dnis.
- session.connection.remote.uri contains the same value as session.telephone.ani.
- transfer bridge="true" is not supported for a VoIP configuration.
- Certain elements of the VoiceXML 2.0 specification is not supported by the Avaya IR VoiceXML feature. For more information, see Unsupported features of the VoiceXML 2.0 specification.
