Is it possible to create method in Unity 3.1(5) (or 4.x for that matter) whereby a non-subscriber could address and send a message to a Unity subscriber? Perhaps by creating a new conversation (which is basically the standard conversation w/o the sign-in) and pointing a CH's after-message action to this new conversation? The issue I'm attempting to address is a bunch of former Meridian users wanting to call an "express messaging" pilot from the outside and be prompted for message recipients w/o having to log in first. [Unity 3/1(5) VM only, Ex5.5 SP4 off-box, TSP 6.0(2).] Thanks,
I'm not sure I understand what, exactly, you're wanting to do here...
If outside callers want to find a user in the directory to leave a message they can do so using the name lookup handler (in 4.x you can have many name lookup handlers with different sets of users behind them) - they can find users by name in here just like subscribers can find other subscribers by name.
They don't want to spell the name and then be routed to the matched extension (i.e., they don't want to ring the phone). They want to just punch in the extension (rather than the name) of the destination VM box, record the message, and end the call. (Basically, they would like a separate number than the main pilot number that would skip the opening greeting the sign-on and start out as if they'd selected "Send a Message.")
You can do that using the transfer over ride sequence... from the opening greeting (or any greeting for that matter) you can dial the extension followed by #2 and it'll go right to the greeting of the user without ringing their phone. So if my extension is 1234 you'd dial 1234#2 and get right to my greeting.
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.