Hi ,
 
I would like to know is there  a way to handle any kind of runtime error so i can make application play the error message and drop the call to an agent.
 
For example , I play a date using Say-it smart plugin , defined a format for the date as YYYYMMDD , date comes from external system (D , there is possibility of date coming in a different format so Say-it smart plugin ends up throwing an custom element error and call disconnects
 
Another example , Say-it smart plugin cannot able to find the audio files instead of throwing batch-fetch , it is throwing an custom element error and call disconnects
 
All this cases i dont want the caller to be disconnected rather attended by an agent
 
Awaiting your feedback
 
regards,
Prince Christopher.J

Hi,
If you are in a standalone environment, then you can bring in a Transfer
element, configure it to tell the caller 'we're having difficulty,
please hold' and then configure the transfer number. Then in the
workspace, Right-Click on the element and select Error Element >> Yes.
This designates that this element should execute upon a Java Exception.



On 3/23/2011 1:08 AM, Cisco Developer Community Forums wrote:
> prince christopher joseph has created a new message in the forum "CVP
> - All Versions":
>
> --------------------------------------------------------------
> Hi ,
> Â
> I would like to know is there a way to handle any kind of runtime
> error so i can make application play the error message and drop the
> call to an agent.
> Â
> For example , I play a date using Say-it smart plugin , defined a
> format for the date as YYYYMMDDÂ , date comes from external system
> (Demoticon , there is possibility of date coming in a different
> format so Say-it smart plugin ends up throwing an custom element error
> and call disconnects
> Â
> Another example , Say-it smart plugin cannot able to find the audio
> files instead of throwing batch-fetch , it is throwing an custom
> element error and call disconnects
> Â
> All this cases i dont want the caller to be disconnected rather
> attended by an agent
> Â
> Awaiting your feedback
> Â
> regards,
> Prince Christopher.J
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3233656>
>
> or simply reply to this email.

--
Janine Graves

I am in a comprehensive environment :-) , is there any ways to do this in comprehensive env
 
Thanks for your help so far in this
 
 
 

Use a CVP_Subdialog_Return element, right-click on it, select Error
Element >>Yes.
Pass back 'error' as CallerInput this will go to ICM in the
user.microapp.caller_input array.
Pass back the other data you'd like to return in the FromExtVxml0, 1, 2, 3

In the ICM routing script, it'll go down the Success path of the
RunExtScript(GS, Server, V) node when you have an Error element in your
application.
So, the ICM script must check the caller_input variable to see if it
says 'error'
If so, ICM must play an error messgae to the call.
It can now look at the FromExtVxml[0] through [3] for other data you've
returned and Queue accordingly.



On 3/23/2011 9:27 PM, Cisco Developer Community Forums wrote:
> prince christopher joseph has created a new message in the forum "CVP
> - All Versions":
>
> --------------------------------------------------------------
> I am in a comprehensive environment :-) , is there any ways to do this
> in comprehensive env
> Â
> Thanks for your help so far in this
> Â
> Â
> Â
> Hi,
> If you are in a standalone environment, then you can bring in a Transfer
> element, configure it to tell the caller 'we're having difficulty,
> please hold' and then configure the transfer number. Then in the
> workspace, Right-Click on the element and select Error Element >> Yes.
> This designates that this element should execute upon a Java Exception.
>
>
>
> On 3/23/2011 1:08 AM, Cisco Developer Community Forums wrote:
> > prince christopher joseph has created a new message in the forum "CVP
> > - All Versions":
> >
> > --------------------------------------------------------------
> > Hi ,
> > ÿ
> > I would like to know is thereÿ a way to handle any kind of runtime
> > error so i can make application play the error message and drop the
> > call to an agent.
> > ÿ
> > For example , I play a date using Say-it smart plugin , defined a
> > format for the date as YYYYMMDDÿ , date comes from external system
> > (Demoticon , there is possibilityÿ ofÿ date coming in a different
> > format so Say-it smart plugin ends up throwing an custom element error
> > and call disconnects
> > ÿ
> > Another example , Say-it smart plugin cannot able to find the audio
> > files instead of throwing batch-fetch , it is throwing an custom
> > element error and call disconnects
> > ÿ
> > All this cases i dont want the caller to be disconnected rather
> > attended by an agent
> > ÿ
> > Awaiting your feedback
> > ÿ
> > regards,
> > Prince Christopher.J
> > --
> > To respond to this post, please click the following link:
> >
> >
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3233656>
> >
> > or simply reply to this email.
>
> --
> Janine Graves
>
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3247212>
>
> or simply reply to this email.

--
Janine Graves

Hi Neil,

In your subdialog apps, you should use a "Subdialog Return" (not
"CVP_Subdalog_Return") as an error element - so you return back to
whichever app invoked you. You can return something to let the main app
know that an error occurred, and then (if you like) the main app can go
back to ICM using CVP_Subd_Return (or in this case, the main app can
continue processing as the error has been 'handled').

The idea is, that you always want the Main app to be the one that goes
back to ICM.

Janine


On 4/4/2011 3:02 PM, Cisco Developer Community Forums wrote:
> Neil Fluhr has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> Hi, Janine -
>
> I have a follow-up question to your answer. We have a transactional,
> self-service application that involves 10-12 separate CVP Studio
> applications. We have a "main" app that is called by ICM and then it
> invokes the other apps via a sub-dialog invoke. Normally, when a
> caller completes a task in the other modules it will return to the
> main and there is a "CVP Subdialog Return" that returns control to ICM.
>
> Should we add a "CVP Subdialog Return" error element to each one of
> these apps for graceful call handling?
>
> Thanks!
> Neil
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3491299>
>
> or simply reply to this email.

--
Janine Graves