Alternate Extension for Exchange 2010 UM

[fieryhail]

Hello All,

I'm quite new to Exchange however have a background in Cisco. We're running a Cisco Unified Communications Manager system, 7.1.5. We currently use Cisco Unity Connections (also 7.1.5). We were running a voicemail only system with IMAP relay to the message store, recently we've been trying out Exchange 2010 Unified Messaging features. So far pretty nice. However, I'm running into a difficulty with alternate extensions. I've already setup a voicemail profile and SIP trunk in CUCM to get to the Exchange 2010 UM server. CallManager is using Active Directory for user sync. If I have 2 extensions setup in CallManager for a user, say 2005 (primary) and 2006 (Alternate) it is a simple matter in Unity Connections to assign alternate extensions where CallForwardNoAnswer or CallForwardBusy go to the same voicemail box for either the primary extension or the secondary. They all go to the Inbox for the primary extension. Is there such a way to accomplish this with Exchange 2010 UM? So that calls from either 2005 or 2006 both go to the inbox for 2005? I tried assigning the Exchange 2010 UM VM Profile to extension 2006 but when the call goes to Exchange UM, it says there is no valid user for that extension. How would I accomplish such a thing? Or is there no provision to do such with Exchange, only Unity Connections? Thanks again for any insight.

 

[fieryhail]

I got it. Was unfamiliar with the EUM option under the user's mailbox. Added an additional EUM for 2006 and tied it to the dial plan and all works as it ought to.

Still not sure if I'd replace Cisco Unity Connections with Exchange 2010 UM, but it's a nice system so far. Some users are using Exchange UM for VM/unified messaging, others (most) still using Unity Connections. We're going to upgrading to Unity Connections 8 in the near-ish future, and probably CUC 8.5 shortly thereafter. Unity Connections 7 does not support Exchange 2010 as a message store so some functionality is broken from 2007. CUC 8.5 promises more Unified Messaging features so it ought to be interesting. Still trying to work through the Exchange AutoAttendant features. Probably quite powerful, but am so used to Unity Connection's Call Handlers and call routing, it may be me who is making things more complicated than they are in reality. Thanks again.