Article ID:	27
Last updated:	February 22, 2007

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

Audium Known Issues

• Dynamic element configurations implemented as XML-over-HTTP cannot set the default audio path or maintainer as dynamic element configurations implemented via Java.
• VoiceXML Insert elements cannot get information about the application's settings or make changes to the default audio path or maintainer as other elements can.
• On Windows, if the application server is installed as a service, the default installation of Audium 3 will not function. The developer must perform additional tasks documented in the GettingStarted.pdf document and in Knowledgebase Article #1008 in order for the Audium Server to function.
• The update administration script will not act gracefully in certain situations involving classes placed in the util folder of the application. This issue is described in more detail in Knowledgebase Article #1009.
• Using SayItSmart in certain Audium voice element's "done" audio groups to play back the value captured by the voice element itself will cause an error to be thrown. Only the following Audium Voice Elements are affected: Currency, Digit, Form, all menus, Number, and Yes_No_Menu.
• ClassCastExceptions may be encountered when accessing developer-specified objects stored in Session Data. To resolve this issue, the class or JAR files of these developer classes must be placed in the common folder of Audium Home (in classes or lib), they cannot be stored in the java directory of a specific application.
• In the Audium Builder, using substitution for an element's setting using element data or session data whose name contains a period (.) will not work correctly.

Session Replication using Resin

• A failover event occurring while a string of non-voice elements are being executed will cause that string of elements to be executed a second time on the backup machine. This issue is described in more detail in Knowledgebase Article #1010.
• In certain session replication designs, a machine can run two instances of Resin acting as a primary and a backup to another machine. Each application server instance (and hence Audium Server instance) must be run on its own IP address. When using virtual IPs to do this, SNMP monitoring must be configured to use a different port for each instance. See the UserGuide.pdf document on how to do this.

  Voice Browser Known Issues

  VoiceGenie Browsers

• When using the Record element on all VoiceGenie browsers (including SpeechGenie), no speech bargein is possible for the initial prompt.
• On all VoiceGenie browsers, a DTMF hotlink will not be activated within any Audium Element with an input mode set to "voice". With the input mode set to "both" or "dtmf" a DTMF hotlink can only be activated from within the following Audium Elements: Month, Month_Day, Phone, State, Year, Year_Month_Day, Zip, all menus, Audio, Form, and Number.
• On all VoiceGenie voice browsers, a DTMF keypress will cause throw a nomatch when any Audium or custom element's input mode is set to "voice". This primarily affects DTMF hotlinks. Audium recommends setting the input mode to "both" if DTMF hotlinks are to be used. VoiceGenie is aware of this and lists it as a known issue.
• When using the Form element on VoiceGenie with Nuance 8, a configuration that involves the combination of an inline speech grammar and an external speech grammar will crash the element when an utterance occurs that is defined in the external speech grammar. This may be fixed in a future version.
• When using the Form element on VoiceGenie with Nuance 8, if the element is configured for n-best with a grammar that does not use slots, only one guess will be returned, even if you configure the "maxnbest" setting to be greater than 1.
• When using the Form element on VoiceGenie with Nuance 8, the "Slot Name" setting is used, and an inline speech grammar is used (the "Voice Keyword setting), the "value" element data begins with a "+" sign when an utterance is matched by the inline grammar. If DTMF is used or the slot name not given, the element data does not begin with a "+".
• When using the Form element configured to use n-best with the VoiceGenie voice browser with BBN ASR or Nuance 8 ASR, all "utterance" element data with an index of 2 or greater will be returned with a value of "undefined". For example, the element data "utterance1" will contain the appropriate utterance but "utterance2", "utterance3", etc. will contain "undefined".
• The Form element will crash with the VoiceGenie voice browser with BBN ASR configured to use multiple slots. there are no problems with a single slot.
• The following Audium Voice Elements will not function when using the VoiceGenie interpreter with BBN ASR:
• Credit_Card
• Digits and Digits_With_Confirm
• Month_Day and Month_Day_With_Confirm
• Month_Year and Month_Year_With_Confirm
• Phone and Phone_With_Confirm
• SSN and SSN_With_Confirm
• Year and Year_With_Confirm
• Year_Month_Day and Year_Month_Day_With_Confirm
• Zip and Zip_With_Confirm

Nuance Browsers

• When using the Record element on all Nuance browsers, when bargein is turned on for the initial prompt, a beep will not be heard even if the setting is turned on.
• On Voice Web Server 1.3, a DTMF hotlink will not be activated within the following elements if their input mode is set to "voice": Currency, Month, Month_Day, Month_Year, Time, Year, Year_Month_Day, Form, State, all menus, Digits, Number, Phone, SSN, and Zip. Additionally, DTMF hotlinks cannot be activated for any input mode from within the Month_Year, SSN, and Time Audium Elements.
• On Voice Web Server 1.3, any field (in Audium or custom elements) with its inputmode set to DTMF will throw a nomatch when any speech utterance is detected.
• On Voice Web Server 2.0 and NVP, a DTMF keypress will cause dead silence to be heard when any Audium or custom element's input mode is set to "voice". The silence will end if the caller utters something. This primarily affects DTMF hotlinks. Audium recommends setting the input mode to ҢothӠif DTMF hotlinks are to be used. Nuance is aware of this and lists it as a known issue.
• When using the Transfer Audium voice element, no Nuance browser will play the "done" audio group.

SpeechWorks Browsers

• The root document used for VoiceXML Insert Elements will not be cached by OSB 1.2 and will instead be requested for each VoiceXML page within the insert element, though the root document for the application itself will be cached. Refer to Knowledgebase Article #1012 for information on workarounds.
• Speech bargein is not supported for the Audio and Transfer Audium elements as well as for any "done" or "yes" audio group of other elements (such as the Digits Audium element). DTMF bargein (as well as turning off bargein) is still available for all audio groups.
• The OSB 1.2 browser does not support the universal "help" utterance. As a result, help audio groups for any element will never be heard and the "help" utterances will throw a nomatch unless handled explicitly in a user-defined grammar.
• A voice hotlink will not be active within any element when its input mode is set to DTMF.

Tellme

• Bargein cannot be turned off for any audio group. A partial workaround is to set a VoiceXML property for the element named "bargein" with the value "false". This, however, will turn off bargein for all audio groups in the element.
• A voice hotlink will not be active within any element when its input mode is set to DTMF.
• A DTMF hotlink will not be active within the following elements if their input mode is set to "voice" Currency, Month, Month_Day, Month_Year, Time, Year, Year_Month_Day, Form, State, all menus, Digits, Number, Phone, SSN, and Zip.
• When using Tellme Studio, deprecation warnings will be sent to the maintainer reporting that the exit tag is not supported. This exists only on Tellme Studio, live applications running on Tellme will not encounter this issue.
• The Form element will not function on Tellme with multiple slots unless the "Slot Name" setting is given the name of one of the slots in the grammars.