This document was generated from CDN thread
Created by: Ryam Hilfers on 12-07-2011 03:04:34 PM
This is more of a curiousity question then a bothersome issue but I'm wondering if anyone out there could provide some insight into the microapp error_code 1. From the CVP7.0(2) config guide this is supposed to be a "caller hangup"
What i'm really wondering is why wouldn't this generate an abort on Run Ext. Script node? 99.9% of the caller abandons do but every day I see maybe 10-15 calls out of 15k+ that sit in queue exit the fail path with an error_code = 1.
Can anyone explain how an error code 1 is generated rather than an abort?
Thank you,
Ryan
Subject: RE: MicroApp Error_Code = 1 "Caller Hangup"
Replied by: Bill Westby on 14-07-2011 02:07:20 PM
For my education, is there a difference between "Abort on Run Ext. Script node" vs. the fail path? Is this referring to an "abort" cause code as the error_code? I'm curious how you handle hang-ups in your CVP app? I used to trap them and return a hang-up but after stern warning (thx Janine!) I stopped trapping them and just use On Call End class to figure out what happened. Maybe it's a timing isue of between the hand-off back to ICM that reports the result differently? Sorry just thinking out loud, I'd probably be aking the same quesiton as well.
Bill W, Medtronic.
Subject: RE: MicroApp Error_Code = 1 "Caller Hangup"
Replied by: Ryam Hilfers on 14-07-2011 02:41:25 PM
Thanks for the reply Bill. I should have stated explicitly that i was using a PM_ Micoapp here. I have always been under the assumption that aborts on the Run Ext. Script node are caller hangups while anything taking the exit path is an error, when using studio/vxml server, improperly handled error events can trigger aborts as well but this is a PM Microapp.
There is a user.microapp.error_code that is supposed to provide the information for Microapp failures. However a code of 1 "caller hangup" is confusing.
Thanks
Created by: Ryam Hilfers on 12-07-2011 03:04:34 PM
This is more of a curiousity question then a bothersome issue but I'm wondering if anyone out there could provide some insight into the microapp error_code 1. From the CVP7.0(2) config guide this is supposed to be a "caller hangup"
What i'm really wondering is why wouldn't this generate an abort on Run Ext. Script node? 99.9% of the caller abandons do but every day I see maybe 10-15 calls out of 15k+ that sit in queue exit the fail path with an error_code = 1.
Can anyone explain how an error code 1 is generated rather than an abort?
Thank you,
Ryan
Subject: RE: MicroApp Error_Code = 1 "Caller Hangup"
Replied by: Bill Westby on 14-07-2011 02:07:20 PM
For my education, is there a difference between "Abort on Run Ext. Script node" vs. the fail path? Is this referring to an "abort" cause code as the error_code? I'm curious how you handle hang-ups in your CVP app? I used to trap them and return a hang-up but after stern warning (thx Janine!) I stopped trapping them and just use On Call End class to figure out what happened. Maybe it's a timing isue of between the hand-off back to ICM that reports the result differently? Sorry just thinking out loud, I'd probably be aking the same quesiton as well.
Bill W, Medtronic.
Subject: RE: MicroApp Error_Code = 1 "Caller Hangup"
Replied by: Ryam Hilfers on 14-07-2011 02:41:25 PM
Thanks for the reply Bill. I should have stated explicitly that i was using a PM_ Micoapp here. I have always been under the assumption that aborts on the Run Ext. Script node are caller hangups while anything taking the exit path is an error, when using studio/vxml server, improperly handled error events can trigger aborts as well but this is a PM Microapp.
There is a user.microapp.error_code that is supposed to provide the information for Microapp failures. However a code of 1 "caller hangup" is confusing.
Thanks