If all of your incoming calls go through CallManager first you can setup a translation pattern in CallManager to send the calls coming into your VM pilot to go to the attempted sign in.
Let's say your VM pilot is 2020. Setup the translation pattern to take any calls coming in on 2020 and change the calling number to 9090. Then you setup the routing rules in Unity to take any call coming from 9090 and send it to the attempt sign in.
You can use the Call Viewer from the Unity Tools Depot to watch the incoming calls to see where the calls are coming from to make sure your translation pattern is working.
Yeah, there's lots of things you can do with Translation Patterns before you send the call off to Unity so you can take full advantage of the Unity Routing Rules. Just be sure to take full advantage of the Unity Call Viewer to see what's getting passed to Unity and if it's a direct call or a forward.
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.