I can't find documentation on the best way to swing the voicemail ports from my existing Unity 4.0.4 server to a new 4.0.4 server with a new IP address in a different subnet. We're running CallManager 4.1-- (I'm using the new server to then upgrade to Unity 5.x and have already done a DiRT restore of the active database). We are migrating voicemails from Exchange to Exchange using ExMerge.
We have two CallManager servers (pub/sub) and end state will be one Unity server (the new hardware only). The old Unity is still running at present.
Just to add to to his post, after you configure the integration as everything the same, you will have to stop the old Unity server. The Unity ports have the same name on different servers will cause issues.
Example: Unity01 CiscoUM-V1
It will screw with CUCM and you will have issues. So stop Unity on the old server, start up the new server and you will not have to configure anything on CUCM. Maybe reset the VM ports for it to register.
If you are trying to test the new server, you will need to create new CUCM VM port names, Hunt group, hunt list, pilot number.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...