The original CALLED party number is used when forwarding calls to VM by default.
You can fix this a number a ways. Using a custom VM profile, or setting up a call routing rule on Unity to send the call to a certain subscriber/call handler, etc when a call comes in for x number. Open up call viewer on the unity server and then make your call to see what numbers are being seen on the unity server to better create the routing rule.
You can also put an alternate extension on the subscriber profile but that may not work well.
This is a very common question that comes up all the time, and as of now if you are using Unity or Avaya voicemail this is working as expected.There is hope coming in Unity 5.0 though :)
Have a look at Michael's excellent posts, there is a fix on the horizon for this exact problem in (Unity 5.0),(ECSBU Test Engineer, CISCO SYSTEMS )
"The situation you describe here (getting Unity to recognize the last forwarding station rather than the first forwarding station), will be a system-wide option added to Unity 5.0. There is not a way to do this with a configuration setting on earlier versions of Unity. I'm not aware of any CallManager settings that will address this issue either."
"We use the OriginalCalledParty and OriginalCdpnRedirectReason fields in SCCP StationCallInfo message from CallManager. The feature in Unity 5.0 will allow admin to configure Unity to look at LastRedirectingParty and LastRedirectingReason fields instead, on a system-wide basis."
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.