I had a couple of Exchange 2010 voicemail questions from a school district from northern California replacing Cisco Unity voicemail with Exchange 2010 UM.
Where can I check if my PBX has been tested with Exchange 2010 UM?
We have an updated Telephony Advisor list for Exchange 2010. You can check SIP gateways, TDM PBXes that have been tested as well as SIP PBXes that have been tested with Exchange 2010 Unified Messaging.
To visit Exchange 2010 Telephony Advisor go here.
I have heard Exchange 2010 UM does not work with Cisco Call Manager 5 or higher, true?
No, we have tested Exchange 2010 UM using direct SIP to CCM 5,6, and 7.
How do I upgrade to Exchange 2010 UM from Exchange 2007 UM?
It is a fairly basic process, you install Exchange 2010 UM server into the same dial plan as Exchange 2007 UM, point the SIP gateways or direct SIP PBXes to the new 2010 UM server, migrate mailboxes to 2010, migrate any custom prompt autoattendants, decommission Exchange 2007 UM server.
Exchange 2010 UM supports coexistence as well and will route any Exchange 2007 voicemails to Exchange 2007 UM servers.
More on the UM upgrade process here.
Can I connect multiple PBXes to Exchange 2010 UM and leverage the same dialplan and subscriber access (pilot) number?
Yes, this works and is supported. Here is a list of supported scenarios:
For more on 2010 dial plans visit here.
Where can I find some good Exchange 2010 UM training?
Training http://www.microsoft.com/learning/en/us/training/exchange-server.aspx Virtual Labs Configuring Exchange Server 2010 Unified Messaging and OCS 2007 R2 Integration Transitioning from Exchange Server 2007 to Exchange Server 2010 (Beta) Configuring Exchange Server 2010 Unified Messaging Free eLearning Unified Messaging in Exchange 2010
I think you should also put here some OCS-integration-related things, namely:
Office Communications Server Communications Server 2007 can't determine the version of the mailbox for a UM-enabled user. So when a call is received by Communications Server 2007, and it redirects the call to another UM server in the same dial plan, either an Exchange 2007 UM server or an Exchange 2010 UM server might take the call. This causes a problem when you perform a partial upgrade, because the incoming call will fail if it's received by an Exchange 2007 UM server and the UM-enabled user's mailbox is on an Exchange 2010 Mailbox server. The call will fail because Exchange 2007 UM servers can't process calls for UM-enabled users who have Exchange 2010 mailboxes.
The reason the incoming call will fail is that Communications Server 2007 can't tell whether the UM server that it redirected the call to is an Exchange 2007 UM server or an Exchange 2010 UM server.
If Communications Server 2007 is used as an IP gateway, and there are Exchange 2007 mailboxes that are enabled for UM, a new SIP URI dial plan will be required. The new SIP URI dial plan must contain only Exchange 2010 UM servers. The new dial plan is required to ensure that incoming calls are redirected only to Exchange 2010 UM servers.
Is this true if you route all incoming OCS calls to Exchange 2010 UM only? My understanding is the 2010 UM server can hand off the call to the 2007 UM server which replaces the need for OCS to be able to route to the correct voicemail account.
my experience shows, that in my prod. environment using a single dialplan that is shared bethween a UM 2007 and UM 2010 server, if the 2010 UM server received the call (you can recognize the new greeting sound effect at the beginning of the call, so it is definitely answered by 2010 UM) it was not able to recognize the caller as an identifed user. User was hosted on 2007 mbox, so no redirection happened.
Our solution was finally to give the already existing migration from 2007 mbox to 2010 mbox a high priority, so the UM role was also migrated at the end. After all the mailboxes are on 2010 mbox server, and UM is also a 2010 server, we have nothing to talk about.