Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
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.
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.
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
The test environment:
Step 1: Configuring the Cisco Call Manager:
Step 2: Configuration Microsoft Exchange 2013 UM
Creating the gateway representing the CUCM Publisher with the IP address 10.0.100.52