Brief Solution Description

Transcription

1 Public Brief Solution Description Aastra MX-ONE V.4.0 integration with Microsoft UC products Aastra Telecom Sweden LM Ericssons väg 30, Hägersten Box SE Stockholm, Sweden Doc. ASE/MXO/PM/0031/EN Date: 12/ Rev. A

2 Table of Content 1 OBJECTIVE 3 2 INTRODUCTION 3 3 SOLUTION DESCRIPTION Office Communications Server 2007 R2 (OCS 2007 R Exchange Server 2010 Unified Messaging (UM) Office Communications Server 2007 R2 and Exchange Server 2010 UM 5 4 CONTACT: 5 Table of figure FIGURE 1 MX-ONE AND OCS 2007 R2 4 FIGURE 2 MX-ONE AND EXCHANGE 2010 UM 4 FIGURE 3 MX-ONE AND OCS 2007 R2 AND EXCHANGE 2010 UM 5 Doc. No. ASE/MXO/PM/0031/EN Rev. A Date: /6

3 1 Objective The aim with this document is to provide a brief interworking description between Aastra MX-ONE and Microsoft Unified Communications. 2 Introduction Aastra MX-ONE is a complete IP-based communications system with unbeaten capabilities for mobile users. Not only does MX-ONE provide excellent voice communications, it also provides the applications necessary to offer true mobility and Unified Communications. MX-ONE is based on an open software and hardware environment, using standard servers with a LINUX SUSE operating system. MX-ONE can be integrated with the following Microsoft Unified Communications products: Office Communications Server 2007 R2 (OCS 2007 R2) Exchange Server 2010 Unified Messaging (UM) 3 Solution Description MX-ONE V.4.0 can be connected in the following scenarios with Microsoft Unified Communications: Office Communications Server 2007 R2 (OCS 2007 R2) Exchange Server 2010 Unified Messaging (UM) Office Communications Server 2007 R2 and Exchange Server 2010 UM MX-ONE V.4.0 is connected with OCS 2007 R2 and Exchange 2010 UM via Direct SIP interface specified by Microsoft. MX-ONE requires a SIP trunk connection to each service. MX-ONE supports TLS as the SIP transport mechanism to be used by Mediation Server and Exchange Server UM. Doc. No. ASE/MXO/PM/0031/EN Rev. A Date: /6

4 3.1 Office Communications Server 2007 R2 (OCS 2007 R2) The picture shows an example where an MX-ONE is connected with OCS 2007 R2. A Direct SIP connection is required between MX-ONE and the Mediation Server. Figure 1 MX-ONE and OCS 2007 R2 3.2 Exchange Server 2010 Unified Messaging (UM) The picture shows an example where an MX-ONE is connected with Exchange 2010 UM. A Direct SIP connection is required between MX-ONE and Exchange Server. Figure 2 MX-ONE and Exchange 2010 UM Doc. No. ASE/MXO/PM/0031/EN Rev. A Date: /6

5 3.3 Office Communications Server 2007 R2 and Exchange Server 2010 UM The picture shows an example where an MX-ONE is connected with OCS 2007 R2 and Exchange 2010 UM. Two Direct SIP connections are required between MX-ONE and Exchange Server 2010 and MX-ONE and OCS 2007 R2. Figure 3 MX-ONE and OCS 2007 R2 and Exchange 2010 UM 4 Contact: For more information regarding integration between MX-ONE and Microsoft Unified Communication contact your local Aastra Sales representative. Aastra Worldwide Locations Doc. No. ASE/MXO/PM/0031/EN Rev. A Date: /6

6 Aastra Technologies Limited. All rights reserved. This document contains proprietary information, which is protected by copyright. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, or translated into another language, without the prior written consent of Aastra Technologies Limited, Concord, Ontario, Canada. NOTICE The information in this document is subject to change without notice. AASTRA MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. AASTRA shall not be liable for errors contained herein, neither for incidental nor for consequential damages in connection with the furnishing, performance, or use of these materials. Aastra Technologies Limited Concord, Ontario, Canada. Doc. No. ASE/MXO/PM/0031/EN Rev. A Date: /6