We just set it up the same way you described. You install extended services auto attendant app. It will install a "cutdown" verison of CRA with the engine and all. Then you need to configure the TAPS app in CRA and the CTI ports and CTI route points in the call manager. Just an FYI, also, we ran into a problem with the TAPS service not staying started, even though the engine was running. Found that our java client was down rev. We had to point our "wrapper.properities" file to a newer version of the java applet to fix it. This was a bug in 3.3(2).
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.