Make plans now to attend XMPP integration with CVP 2012/06/14 @ 10:00 AM at Cisco Live! in San Diego. ...Read More

 



Cisco Developer Network will be presenting a CDN Developer Track at Cisco Live! London the week of January 31, 2011.

We are presenting technical sessions which highlight Application Programming interfaces (APIs) and Software Developer Kits (SDKs) for Cisco technologies such as Unified Communications, IOS, and Access Routing Technologies ¿ including the new Cisco Cius ...Read More

 

Recently noticed that there have been repeated questions from our developer community complaining that they can't seem to get the beep to work with <record>. They have set the beep attribute to "true" alright, and the reference guide even says this is supported but why doesn't it work?
...Read More

 

August 01, 2006
Earlier today, as I was typing a comment in our internal issuing-tracking system, I hit backspace to correct a typo. WHAM! I go back to the previous page, and my long-winded comment is gone. Apparently I somehow left the context of the text area (did I tab, or spuriously click, or??), which causes backspace to act as a hotkey for "Back". The web browser was not very forgiving of my mistake.

Are your IVR applications forgiving? They should be.
...Read More

 

Mark Gibbs over at Network World has put together a spiffy little scoring system for customer service systems (including many criteria for IVR systems). How would callers score your IVR using Mark's guidelines? Place a call and find out, you may be surprised.
...Read More

 

If you're using JNDI to connect to your database through Tomcat, then it's possible you've had to deal with database connection pool leaks. Your code tests fine, it's been reviewed, but in load tests or in production your app is unable to acquire database connections, the pool is empty!

Fear not, there are some handy parameters which can be set in your application's XML configuration file (in tomcat/conf/Catalina/YOUR_IP/YOUR_APP.xml):
...Read More

 

Showing 6 results.
Items per Page 50
of 1
First Previous Next Last

CVP Forum

« Back to General Discussion - All Versions

Not Ready Reason Code Undefined [0] and 999

Combination View Flat View Tree View
Threads [ Previous | Next ]
Not Ready Reason Code Undefined [0] and 999
Answer
2/6/13 10:31 AM
Hi all ,
In my CUIC report "Agent Not Ready Detail"  I was getting two reason codes Undefined [0]  and 999 which I had not configured in Reason Code List in Config Manager . I found out that 999 gets stored in the database when agent state is changed from Supervisor Toolkit . But I have no idea when does  this reason code 0 get stored in the database ? Is it a default system generated reason code ? I read it in one of the Cisco docs that it is system generated reason code when agent is made Not ready automatically by the software ?
Does anyone has better idea when does this Not ready reason code 0 gets stored ?
Flag

RE: New Message from Dipika Gupta in Customer Voice Portal (CVP) - General
Answer
2/6/13 1:02 PM as a reply to Dipika Gupta.
When a agent logs in and waits some time before going ready, the system automatically puts the agent in not ready state. The code 0 is used then. It represents a agent going not ready without a reason code.
Hemal

From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Wednesday, February 06, 2013 4:32 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Dipika Gupta in Customer Voice Portal (CVP) - General Discussion - All Versions: Not Ready Reason Code Undefined [0] and 999

Dipika Gupta has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Hi all ,
In my CUIC report "Agent Not Ready Detail" I was getting two reason codes Undefined [0] and 999 which I had not configured in Reason Code List in Config Manager . I found out that 999 gets stored in the database when agent state is changed from Supervisor Toolkit . But I have no idea when does this reason code 0 get stored in the database ? Is it a default system generated reason code ? I read it in one of the Cisco docs that it is system generated reason code when agent is made Not ready automatically by the software ?
Does anyone has better idea when does this Not ready reason code 0 gets stored ?
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11604816 or simply reply to this email.
Flag