I'd like to set up a call handler on Unity that users from an IP phone can dial directly rather than having to dial into Unity to get to.
I'd also like to be able to have a user forward their extension to this call handler so that calls to their extension are handled by the call handler and not sent to their mailbox greeting.
I see a couple of options:
1) use a translation
2) use a device profile with CFA set to vm pilot
3) use call routing rules
Each has their own benefits, but I don't personally like number 3 since we might have a dozen or so of these call handlers, and a call to the TAC once said that these rules should never really be modified.
I would use a CTI route point which is set to CFA to the DN of the Call Handler. This will allow you to dial a Call Hander directory from CallManager.
As for forwarding a call to that CTI route point and having it forward to the Call Handler -- you will need a call routing rule in Unity because integration occurs based on the first forwarding station data. Forwarding station data cannot be manipulated with a translation pattern.
There is no reason that the rules can't be modified. Doing so is supported and it wouldn't really make sense for us to give you an interface to do it with if that wasn't the case. If you run in to any problems with support for this please dope me an email. :-)
CTI Route Points - interesting, would you extend this to voicemail pilots as well? We like to use an easily remembered number for our pilots 50000 and then translate this to the first Unity port. Could we use a CTI route point for this as well?
What benefits do you see using a CTI route point vs a translation?
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.