Article ID:	17
Last updated:	November 02, 2006

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.

• 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.
• 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.
• On all VoiceGenie browsers, when using the Currency_With_Confirm Audium Voice Element, an entry of "*" entered by the caller will cause the element to throw an error. Additionally, the Number_With_Confirm Audium Voice Element will throw an error if the caller entered "*"or "#". The issue occurs when trying to play back those values and hence the Currency and Number Audium Voice Elements are not affected. Audium is working on a fix to be implemented in a future version.
• On all VoiceGenie browsers, a voice hotlink will not be active within any element when its input mode is set to DTMF. Additionally, a speech hotlink cannot be activated within Audium Elements that contain a confirmation menu within them regardless of input mode.
• 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.
• 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 rare occasions, if an error occurs on the Audium Server not affiliated with a single application, the VoiceXML error page generated will assume a pure VoiceXML 1.0 voice browser, thereby triggering the voice browser's default error page. This issue is described in more detail in Knowledgebase Article #1011.
• Along the same lines, if an application's settings refers to a non-Nuance voice browser but a call is made from a Nuance voice browser, the Audium port handling the call will not be closed. Knowlegebase Article #1011 provides more detail on this issue as well.
• SayItSmart playback of dates using TTS only on Voice Web Server 2.0 reads back years digit by digit. Additionally, year values may be read incorrectly, with zeros being inserted in the playback. Audium suggests using pre-recorded audio files to properly read back dates on this voice browser.
• 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 2.0 and NVP, a DTMF keypress will cause dead silence to be heard when 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. The silence will end if the caller utters something. This primarily affects DTMF hotlinks. Audium recommends setting the input mode for these elements to "both" if DTMF hotlinks are to be used. Nuance is aware of this and lists it as a known issue.

SpeechWorks Browsers

• The OSB 1.1 browser is incompatible with the BEA Weblogic Java application server running Audium.
• The root document used for VoiceXML Insert Elements will not be cached by OSB 1.1 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.
• OSB 1.1 does not support audio in the WAV format. As a result, all the audio Audium provides (in the Chapter1_HelloWorld tutorial, on hold audio, error audio, etc.) will not be heard. To resolve this, present all audio content in a format other than WAV.
• The OSB 1.1 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.

Verascape

• Only the following Audium Voice Elements will function on the Verascape voice browser:
• Audio
• Transfer
• Currency and Currency_With_Confirm
• Digit and Digit_With_Confirm
• Form
• All menus
• Number and Number_With_Confirm
• Record and Record_With_Confirm
• Yes_No_Menu
• Verascape does not allow the use of a DTMF (touchtone) only application. As a result, background noise can interrupt number input and throw nomatch events. If a DTMF only application is desired, consider using another voice browser.
• Verascape does not send ANI, DNIS, UUI, and IIDIGITS information to the Audium Server.
• Entering DTMF input in rapid succession may cause the entry to be cut off abruptly or may throw a noinput event.
• The Verascape voice browser cannot utilize external DTMF grammar files. For hotlinks and the Form Audium Voice Element, use the inline options.
• When creating a new voice element, do not use the literals 'true' and 'false' in if statements as Verascape converts this to boolean values, even if they are surrounded by single quotes.