|
|
 |
February 2004
Potentially Breaking Changes
The most important changes are listed towards the top of the
table, with minor ones later. Some of the more complicated changes have
links to the appropriate section of the VoiceXML 2.0 draft (e.g. §5.2)
for more detailed information.
| Relevance |
Description |
Compliance
|
According to the VoiceXML
specification, the <choice> tag can have <grammar> and PCDATA as children. The browser now follows the specification for the <choice> tag. Previously SSML tags were allowed to be children of the <choice> tag.
|
Compliance
|
According to the VoiceXML
specification, form level grammars should not fill in control items like <block>, <initial>. Now the browser follows the VXML specification correctly. Previously it filled the control items when the form level grammars returned multiple slots matching the control item names.
|
Speech Errors
|
The default value of the bevocal.maxdialogerrors property is now 50. The default value for the bevocal.maxerrors property is now 100. Previously, the default values for both properties was 0, meaning that there is no limit on the number of errors.
|
Speaker Verification
|
BeVocal extension tags <register> and <verify> are changed to <bevocal:register> and <bevocal:verify>. The browser throws a warning message when the old tag names are used. They will be deprecated in a future release. The functionality of the tags has not changed.
|
Record
|
bevocal:dest and bevocal:destexpr attributes of the <record> tag are deprecated.
|
Enhancements
| Relevance |
Description |
Secure Logging
|
The browser now supports secure logging. Check the documentation for bevocal.securelogging.enabled for more details. This allows certain secure portions of the log to be encrypted using a public key specified by the application and later decrypted using a private key.
|
Built-in Grammars
|
A new built-in grammar type, streetaddress, is introduced. It allows you to speak a more natural utterance like "685 Clyde Avenue". Check the documentation for <grammar> for more details.
|
Grammars
|
The year part of the grammar is made optional for built-in grammar "date". Users can now say the day and month of the year.
|
Call Control
|
The <bevocal:listen> tag now has a shadow variable. You can query the duration of the outbound call via the shadow variable similar to the <transfer> tag.
|
Transfer
|
During outbound calls, network errors are properly reported as network_error or network_busy errors. Previously some cases were reported as internal platform errors.
|
Log Browser
|
The Log Browser now allows you to view multiple logs in different browser windows. Previously all the logs opened in the same window which made it difficult to compare different logs.
|
Record
|
If the value of the finalsilence attribute of the
<record> tag is 0s,
the interpreter does a fixed length record for the number of seconds specified in the maxtime attribute. The
recording does not wait for speech input and does not throw a NOINPUT
event. The recording can still be terminated using any dtmf key if the dtmfterm attribute is
set to true.
|
Known Bugs and Limitations
| Bug |
Description |
5144
|
DTMF recognitions produce
incorrect utterance properties in shadow variables and application.lastresult$.
Currently, the utterance property is a string of the form "DTMF-1
DTMF-2 DTMF-pound". The VoiceXML specification requires that the
property be a simple string of digits and symbols such as "12#".
The specificaiton also requires that the termchar be removed from the
end of the utterance string, which we currently do not do.
|
6305
|
The numeric scale of the
confidence field of shadow variables and application.lastresult$
now
corresponds with the VoiceXML confidencelevel
property. The confidencelevel property uses an exponential
scale to map the VoiceXML property values 0.0-1.0 to the Nuance values
1-100. However, the confidence properties of shadow
variables and lastresult$ use a linear mapping.
|
Bug Fixes
| Bug |
Description |
5036
|
DTMF tones are now supported in hotword grammars.
|
5699
|
While executing JavaScript in <if> tag, the errors are shown with correct line numbers in the JavaScript code.
|
6729
|
A proper event error.unsupported.uri is thrown when you specify a wrong scheme in the transfer phone number URI. Previously the browser threw a generic error.connection.baddestination event.
|
6736
|
An error.badfetch event is thrown when both the next and expr attributes are specified for <submit> tag.
|
6744
|
A value of 0 is now accepted for the speedvsaccuracy
property. Previously the browser threw a exception for a 0 value.
|
7146
|
An error.badfetch event is thrown if you specify a 0 value for the finalsilence attribute in <record> tag.
|
7163
|
A <enumerate> tag inside a SSML tag is a no-op implementation now. A warning message is thrown that <enumerate> is not supported inside SSML. Previously this condition threw a runtime exception and exited the application.
|
7170
|
Switching tts voice via the <property> tag failed for calls placed using the Outbound Notification Service. It is fixed in this release.
|
7224
|
Some issues with the usage of Nuance NGO grammars in ABNF grammars are fixed in this release.
|
7250
|
When the browser checks for the MIME type of the grammar, the type attribute takes precedence over any other MIME type calculations, such as Content-Type header or file extension. Previously the Content-Type header took precendence over all other settings
|
7275
|
Fixed some issues where the prompt queueing was corrupted when there was a mix of bargein/non bargein prompts and the tts voice has been changed.
|
7289
|
Fixed the URL encoding problem for the reply parameters in
the Outbound Notification Service. Previously, the ReplyURI parameters were not properly encoded and
all of the input parameters except for INITIAL_URL
were erroneously duplicated in the ReplyURI. The fix properly encodes all parameters sent in the reply.
|
|
