I was looking at http://technet.microsoft.com/en-us/library/ee364753.aspx under "Supported IP PBXs" section, and it says:

IP PBXs are also supported by Unified Messaging. The following table shows the IP PBXs that are supported using a direct SIP connection to Exchange 2010 Unified Messaging.

IP PBXs supported when using a direct SIP connection

PBX manufacturer	PBX model/type	Required software version
Aastra	MX-ONE	4.0
Avaya	Aura	5.2.1 with Service Pack 5 (SP5)
Avaya	Communication Server 2100	CS2100 SE13
Cisco	Call Manager, Unified Communications Manager	5.1, 6.x, 7.0 and8.0

This is on a page for Exchange 2013, and I was confused. Could anyone verify that the above table for supported IP PBX's refelect Exchange 2013, not

The SIP connection is not changed in Exchange 2013 so the above list should be right

The architecture has changed in 2013. The UM role is gone and the CAS sip redirects the call to the correct mailbox server. I am having the issue whereby CUCM won't action the SIP 302 redirect due to way it's sent in the contact section of the header

I currently have the 2010 config working fine with Exchange 2010 UM but not 2013

If anyone has got CUCM working with Exchange 2013 UM are you able to advise on your trunk settings?

-Daniel

Does anyone have a Solution to getting UM 2013 to work with CUCM.  I'm about to move from Exchange 2010. 

Hello

I have integrated CUCM 8.6 and 9.1 with Exchange 2013 UM. Can you describe what is the problem? 

Hello

I have integrated CUCM 8.6 and 9.1 with Exchange 2013 UM. Can you describe what is the problem? 

Hi

We are trying to intergrate CUCM 9.1 and Exchange 2013 UM.

I can call into the UM from CUCM, although none of call forwards out of AutoAttendant (UM)  are working, I am getting message "Sorry I could not transfer you to the extension".

Dial Rules appear to be configured correctly

• Edited by Alexander Troussov 9 hours 22 minutes ago

See https://supportforums.cisco.com/message/4054488 this is how I got the two working.

If your CUCM does not have DNS point your trunk directly to port 5062

Hello

I have integrated CUCM 8.6 and 9.1 with Exchange 2013 UM. Can you describe what is the problem? 

Hi

We are trying to intergrate CUCM 9.1 and Exchange 2013 UM.

I can call into the UM from CUCM, although none of call forwards out of AutoAttendant (UM)  are working, I am getting message "Sorry I could not transfer you to the extension".

Dial Rules appear to be configured correctly

• Edited by Alexander Troussov Tuesday, October 01, 2013 1:24 AM

Hi

I followed instructions but I am getting following messagein CUCM 9.1 (when I am trying to save second trunk)

Unmapped Exception The Destination Address "ex1.test.eu" conflicts with the Destination Address in "ex1.test.eu". Both have the same Incoming Port "5060" specified in their SIP Trunk Security Profiles. Update so that the Destination Addresses and Incoming Ports are unique.

we also have combined roles Mailbox and CAS on 2 servers (justlike the example on CISCO site)

i can not create tranks to mailbox and CAS servers using same SIP security profile (i.e. same incoming port 5060) and same server names (like described in the example)

Maybe I am missing something in this instruction

• Edited by Alexander Troussov 15 hours 0 minutes ago