Since going live with an automated self service script in UCCX (v8.5) i am getting feedback on almost a daily basis that customers are complaining that 'it doesnt work'. Ive added some information that the callers input to the custom variables so at least i can quickly look in the HR cleint and see what the caller has typed in. In most cases it shows the wrong customer ID or DOB.
However some calls are showing as the correct customer ID and it appears in the basic knowledge i can get from the HR client they have been passed to an agent. This should only happen if something goes wrong with the DB lookup or the customer does something wrong.
Ive grabbed the MIVR logs and found the session for one of the examples but im thinking im barking up the wrong tree. Ive used MIVR in the past to debug connectivity issues but what i am looking for is more of a retropsective 'reactive debug' like you get in the scripting tool. I basically need to know why they got transfered to the agent, the ID was right so was it a DB lookup issue or did they not type in the DOB and timed out.
So, is there a different trace i can get out of RTMT to show that?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.