04-02-2009 12:40 PM - edited 03-14-2019 03:53 AM
So, the MicroApp works just fine, however if there's a no entry, it generates an error in the CVP logs. The error talks about a "[NO_ENTRY(17)]". Is there a way to suppress this error?
Thank you,
david
04-02-2009 12:48 PM
No. We are of like minds - and it's a total bummer.
What happens is customers coming from an old IVR school seem to want menus constructed like:
"Press 1 to use our automated system, or just stay on the line to talk to a customer service agent".
I hate these indecisive menus, but I get them all the time. The only time a "NO ENTRY" is really appropriate, in my opinion, is to deal with rotary phones (there are still some in Canada).
But with microapps (either M or GD) you can set the number of no entry tries to 1 and supply a silence.wav as the
If you have a lot of these, as I do at one customer, the CVP log files fill up with these errors and you can't find real errors.
It would be a most sensible enhancement to enable these to be supressed. Are you listening, Cisco?
Regards,
Geoff
04-03-2009 05:45 AM
I was afraid of that. :( Oh well, I love me some clean logs, but I guess the CVP logs are not going to fall under that category. Thanks Geoff.
david
11-09-2010 12:57 AM
Hello Cisco,
Do we need to raise a TAC case to get this enchamentment initiated to supress this error?
We have an obscene number of these "ERRORS" in a customer CVP logs. They clearly are not errors.
It makes it difficult as Geoff has already stated to spot any actual errors.
Please can we get a response?
Gerard.
11-09-2010 04:31 AM
You could just delete them from the logs when viewing them. I don't see Cisco making this change any time soon.
david
11-09-2010 04:57 AM
David,
You are probably correct. It might take Cisco a long time to put in this sort of enchament. I have no expectation that it will be done soon.
However I have raised a partnership request to see if / when it can be done, ast least for future CVP implemetations.
I do think Cisco should implement these sort of enchaments as they are important.
As a workaround I have created a simple batch file to filter out these errors from the syslog log file.
See attached.
Regards,
Gerard.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide