Collecting Caller Inputs - best way to handle this?
My apologies in advance, I'm sure this has been asked before and I did try the search function.
So we have a need to collect, and report on, caller inputs on a couple of menus. For example - one menu offers three options, and based on your choice you could go to another menu with five options, etc. And we're trying to get a handle on the best way to collect and report on callers inputs at the various levels. We know UCCX comes with ten custom variables however, if we have custom variables doing other things can we reuse them? Or, once they are designated to do something are they no longer available?
Would it be best to use a log file of some kind/type?
If there are posts (somewhere) discussing this, a link would be spectacular.
For those of you who have dealt with this your insights would be appreciated.
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.