cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
169
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: null on 22-01-2004 12:41:29 AM
Hi,

Audium 3.3
A minor issue trying to update the application using the updateapp.bat file under application/xx/admin/ . The following is the message displayed. Tomcat runs fine, and loads the application up. I can restart tomcat everitme I do a change in the application. Any idea why this might be happening? I tried resintalling tomcat and audium server. But does'nt fix this problem. The application was built on another machine and imported to this Audium server. Does that make a difference?

Are you sure you want to update application 'xx'? yes
An error has occurred. Please make sure the application server is running and try this command again.
Press any key to continue . . .

Another question, is regarding handling exceptions in the builder. I catch errors like error.badfetch, error.transfer etc with a hotevent. Is there a way to handle an Exception thrown by audium server with a hotevent??

venk.

Subject: RE: Application Update, handling Exceptions
Replied by: Michael Bochynski on 22-01-2004 07:35:14 PM
Hi,

I am wondering whether you see any errors with that application when the server starts up, or only when you run the updateApp script? If so, is it the same error message? Building application on another machine and deploying it on another shouldn't make the difference. However make sure, that all the Java code was compiled with Java 1.3.1. The Audium server uses Java 1.3.1 and this version should be also used for your custom class compilation.

Moreover, could you tell me what changes to the application did you make before running the updateApp script? Try to start the application server and run updateApp script without making any changes and see if you get any errors.

Another thing which you might want to try, is to open the application in the Audium Builder on the machine with the Audium Server. Save and generate the application and run the updateApp script again and see it this fixes the problem.

Regards,
Michael

Subject: Handling errors through hotevent
Replied by: null on 23-01-2004 06:19:11 PM
Hi,
Audium 3.3,

I was trying to catch error events as I posted before. The events error.transfer, error.badfetch are never caught by the Audium Server, when the browser throws them. Only the parent event 'error' is being caught. Is this a known issue with Audium 3.3? We started dropping calls during bridge transfer when there is an error.transfer. From what i understand, these are standard vxml2.0 events! and should've have been caught by the Audium Server.

thank you

venk.

Subject: RE: Handling errors through hotevent
Replied by: Michael Bochynski on 23-01-2004 09:25:07 PM
Venk,

Actually, [i:57613ed26f]error.badfetch[/i:57613ed26f] [b:57613ed26f]is caught[/b:57613ed26f] by the Audium Server. Please run the basic example â¿¿ [i:57613ed26f]Chapter1_HelloWorld[/i:57613ed26f] and check the root document. Among other errors you will find the [i:57613ed26f]error.badfetch[/i:57613ed26f] being caught by Audium Server. This even is definitely caught by Audium Server, as are the other event defined by VXML 2.0 specifications.

A far as the [i:57613ed26f]error.transfer[/i:57613ed26f] is concerned, I could not find this error in the VXML 2.0 specs. The specifications posted on W3C website list transfer errors and events, however I could not find [i:57613ed26f]error.transfer[/i:57613ed26f]. Could you provide me a link to the VXML 2.0 specs listing this error?

Regards,
Michael

Subject: transfer error
Replied by: null on 23-01-2004 10:18:06 PM
Hi Michael,

I apologize for saying that error.transfer is a standard vxml2.0 event. But if the browser throws it, and I have a hot event defined to catch that event, should'nt that work anyway? Or is my understanding of how events work wrong?

venk.

Subject: RE: transfer error
Replied by: Michael Bochynski on 26-01-2004 09:34:49 PM
Venk,

The VXML 2.0 specification, section 5.2.4 defines the event catching order algorithm, and, according to that algorithm, the valid order is the document order. It means, that voice browser will look through the root document to find the closest matching catch. In your case [i:ab2e92422d]error.transfer[/i:ab2e92422d] will be caught by the generic [i:ab2e92422d]error[/i:ab2e92422d] catch, since [i:ab2e92422d]error.transfer[/i:ab2e92422d] is not a part of the VXML 2.0 specification and it's not defined among other specific errors to catch.

Your custom created Hotevent for the [i:ab2e92422d]error.transfer[/i:ab2e92422d] will be added to the end of the root document. The [i:ab2e92422d]error[/i:ab2e92422d] catch will take precedence over your Hotevent, due to the document order of catching events.

In order to catch the [i:ab2e92422d]error.transfer[/i:ab2e92422d] i would suggest discussing with your voice browser vendor changing the name at the voice browser level to something like [i:ab2e92422d]com.voice_browser_name.error.transfer[/i:ab2e92422d]. Renaming will not produce conflicts with the default XVML 2.0 events and errors in terms of event catching procedures.

Regards,
Michael

Subject: RE: transfer error
Replied by: null on 27-01-2004 08:42:10 PM
Hi Michael,

Can you tell me if audium catches the event "error.connection.noroute". I can suggest the change to the browser vendor to throw this event instead of the custom event error.transfer.

venk.

Subject: RE: transfer error
Replied by: null on 27-01-2004 11:45:00 PM
Hi Venk,

The [b:14c770ac28]error.connection.noroute[/b:14c770ac28] event is actually caught in the vxml of the Transfer element. The Transfer element catches all of the error events listed in section 2.3.7.3 (transfer tag section) of the 20 Feb 2003 VXML 2.0 specification except for [b:14c770ac28]error.connection.[i:14c770ac28]protocol.nnn[/i:14c770ac28][/b:14c770ac28]. If any of the transfer error events that are caught in the Transfer element are thrown, the element will exit with an exit state of "phone_error".

On Audium 3.3, the Transfer element will store the error event that causes the Transfer element to exit with "phone_error" in the element data "result". Therefore, you could map the "phone_error" exit state to a decision element that would check the value of the element data for [b:14c770ac28]errror.connection.noroute[/b:14c770ac28], and then handle this error according to your requirements.

If you create a HotEvent to catch [b:14c770ac28]error.connection.noroute[/b:14c770ac28], this will be placed in the root document and this should be executed anytime this event is thrown outside of the Audium Transfer element.

Regards,

Joe
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links