| So the Callmanager will not need PIMG to do anything with Unity since it's all IP
The Nortel will need a way to get SMDI and calls to/from the Unity. The SMDI is easy since the CM does not use SMDI, just set up Unity's Com Port to the Nortel. You could also accomplish both with in-band signaling on a T-1 card in the Unity box (brooktrout or the like. Cisco has specific cards they like and support)
But then we are back to the PIMG - If both systems are hooked to the Unity directly and the Nortel also has hooks to a 2nd vm server then why not have the Unity call the Nortel via its existing ports instead of separate PIMG? I'm also wondering why you will need the PIMG later and not right away. Are you piloting Unity for some reason? I would say you could solve this whole thing if you had a good IPT architect that planned for a 1yr out scenario....a lot of times a pilot is planned by the sales guys. FYI, if the Cisco SE is planning your pilot, then you are introuble. Make sure you get a certified Gold Partner to plan this (certified in IPT, not just a generic Cisco Gold partner...Route Switch and Security guys are not the best for planning IPT migration plans and the Cisco SE never has to "plan" anything...they solve immediate needs and sell sell sell)
As for the EaAdmin stuff
1 change the default extension from 99999.... to something real
2 Chang the password but make sure you DO NOT change the Exchange Admin password, DO NOT change the Message Store User Password, DO NOT change the Svcs Admin pwd.....those are TOTALLY different account than EaAdmin (you will notice the garbage characters at the end of the EaAdmin account) and the EaUser accounts. __________________
Deus ex machina |