Step-By-Step: Integration between Exchange 2013 UM and Cisco Unified Communication Manager

04/29/2014

4 minutes to read

In this article

Integrating the latest version of the UM board now directly in Exchange 2013 with Cisco telephony system is a hot topic in our projects.

In terms of architecture, the approach with Microsoft Exchange Server 2013 is completely different from the Exchange Server predecessors 2007 and Exchange Server 2010. In previous versions , UM was a role that could be deployed if the need was there. In Exchange 2013 , these roles are combined into two types of servers. components or services can be collocated on the same server or separate two name servers CAS and MBX.

Unified Messaging Exchange 2013 requires the use of multiple TCP and UDP ports for communication between servers Exchange 2013 and other devices. Features and services offered by UM depend on various static TCP / UDP ports and dynamic . Proper functioning is ensured by the CAS server running the service call routing and MAILBOX server running the Unified Messaging service.

Services are:

SESworker (GFW )(TCP -In )

UMCallRouter (GFW )(TCP -In )

UMCallRouter (TCP -In )

UMService (GFW ) (TCP -In )

UMService (TCP -In )

UMWorkerProcess - RPC (TCP -In )

UMWorkerProcess (GFW ) (TCP -In )

UMWorkerProcess (TCP -In ) Regarding signage, like the previous versions , Microsoft Exchange 2013 UM only supports the SIP protocol. Service call UM CAS server routing uses the SIP protocol transported TCP (Transmission Control Protocol) or TLS (Transport Layer Security) to communicate with MBC running the Unified Messaging service servers. By default, a CAS server listens for SIP requests on TCP port 5060 in unsafe mode and TCP port 5061 Safe mode. By default, a MBX server listens for SIP requests on TCP port 5062 in unsafe mode and TCP port 5063 in Safe mode. Ports: The purpose of this introduction is to highlight the fact that significant changes in the mode of operation of Microsoft Exchange 2013 UM needed review the traditional integration with Cisco environment. The context of this step by step: 1 Microsoft Exchange Server 2013 1 Server Cisco Call Manager 9.1.2 publisher and one subscriber



Integration TCP

The test environment:

Step 1: Configuring the Cisco Call Manager:

Creation of SIP profile: Device-> Device Settings-> SIP Profile

Creating a security profile SIP : System -> Security - > SIP Trunk Security Profile

Creation of pilot issue of our voicemail system : Advanced features -> ; Voice Mail - > Voice Mail Pilot

Creating a profile for our voicemail system : Advanced features -> Voice Mail - > Voice Mail Profile

Creating a profile for our voicemail system : Advanced features -> Voice Mail - > Voice Mail Profile

Creating a SIP trunk pointing to the Exchange 2013 server: Device - > Trunk

In our example, a single Exchange 2013 server is present , where CAS and MBX servers are separated, the Trunk 1 must be directed to 5060 CAS server, other ports to the MBX server. Creating a routing domain , the goal is that when the CAS server responds fqdn with the Mailbox server , the Cisco phone system can know which answer Trunk This was necessary to repeat this step for each Mailbox server environment Call Routing - . > SIP Route Pattern

Creating a route pattern to send the desired numbers to Exchange UM Call Routing -> Route / Hunt -> Route pattern In this example, 6991 is automated reception , in 6999 voicemail.

Configuring a phone test: Tests will be carried out with the " Christopher " user with the extension number " 1103 ."





Step 2: Configuration Microsoft Exchange 2013 UM