You are right. CTI route points fails to register with CallManager=CM. Everything was going fine until I restarted the Primary CM due to a system crash. The Secondary CM took over for a while, and that's when everything went bad. After restarting the Primary CM, all IP phones registered back to it. Then I expected the CTI route points to work at that moment, but I was wrong.
Yes. CTI route points are used for AutoAttendant. The application administraton needs a user name and password to connect to the CM, and it's already there. The DN is distinct for each CTI route point. Also, the IP of the CM is specified correctly.
The IVR application failed to connect because it had only one IP for the CM, and when this CM crashed and the secondary CM took over, the application couldn't know the secondary IP to use, and that caused the IVR to fail to run.
But later on, I specified both two IP's to the IVR and restarted the system hoping it'll work. Now CTI route points are still not found!
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.