| Audium application is accessible via web browser, but not voice browser |
| Categories: Audium Call Services 3.4.x and 3.5 |
| Article ID: | 91 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
When testing an application, it can be accessed via a web browser (e.g. Internet Explorer), but the same application cannot be accessed by calling in (e.g. SIP to voice browser).
SYMPTOMS
For example, there is an Audium application that does not work while being accessed through a SIP phone (after the voice browser has been configured to accept this call), but the same application produces VoiceXML when accessed through a web browser. Additionally, if the voice browser is configured to point to a flat VoiceXML page, the SIP phone will be able to connect and the call will work as expected.
If a standard phone is being used rather than a SIP phone, the symptoms will still be similar.
RESOLUTION
The language or encoding settings of your Audium application may contain invalid values. Since these settings are required by the voice browser to facilitate interpretation, the Audium application will completely fail if these settings are incorrect.
To change these settings, right-click on the Audium application name in the Navigator pane, and choose "Properties". Click on "Audium - General Settings". If you are not sure which value should be used for these settings, leave them blank and defaults will be used. This settings generally only need to be modified if the Audium application will use a language other than U.S. English.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment