Quick Setup Guide. Aastra MX-ONE V.4.0 Integration with Microsoft OCS 2007 R2. Doc. Nr. ASE/MXO/PLM/ 0123/EN Rev.A

Transcription

1 Aastra MX-ONE V.4.0 Integratin with Micrsft OCS 2007 R2 Quick Setup Guide Aastra Telecm Sweden AB SE Hägersten, Sweden Dc. Nr. ASE/MXO/PLM/ 0123/EN Rev.A

2 Cntents 1 Intrductin General Scpe f this dcument 3 2 Slutin Descriptin Direct SIP Features Prerequisites MX-ONE Micrsft Office Cmmunicatins Server 2007 R2 7 3 Installatin and cnfiguratin Installatin MX-ONE Installatin Micrsft infrastructure and OCS 2007 R2 Installatin Cnfiguratin MX-ONE Cnfiguratin Micrsft Office Cmmunicatins Server R2 cnfiguratin Basic verificatin Micrsft OC client t OC client verificatin Micrsft OC Client t MX-ONE terminal MX-ONE terminal t Micrsft OC Client PSTN t OC Client 16 4 References 17 Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

3 1 Intrductin Aastra MX-ONE (MX-ONE V.4.0) is a cmplete IP-based cmmunicatins system with unbeaten capabilities fr mbile users. Nt nly des MX-ONE prvide excellent vice cmmunicatins, it als prvides the applicatins necessary t ffer true mbility and Unified Cmmunicatins. MX-ONE Telephny System is based n an pen sftware and hardware envirnment, using standard servers with a LINUX SUSE perating system. Furthermre, MX-ONE integrates with 3 rd party slutins using standards based interfaces, such as SIP and CSTA V3/XML. This pen standards apprach enables Aastra t ffer ur custmers a chice and with this in mind we have wrked tgether with Micrsft t ensure that MX-ONE can be integrated with the latest Micrsft Unified Cmmunicatins prducts. Aastra MX-ONE V.4 is fully certified by the Micrsft Partner Prgram t ensure that custmers have seamless experiences with setup, supprt, and use f MX-ONE Telephny System with Micrsft unified cmmunicatins sftware. Aastra s MX-ONE Telephny System integrates with Micrsft UC slutins directly via a SIP cnnectin t reduce the verall cst and cmplexity f the cmbined slutin. 1.1 General MX-ONE V.4.0 is Aastra s Unified Cmmunicatins slutin and can interwrk with third party UC prducts using standards based prtcls, such as SIP and CSTA V3/XML. Integratin f MX-ONE V.4.0 with the Micrsft Office Cmmunicatins Server (OCS) 2007 R2 is supprted as a cmplementary slutin prviding end user services like instant messaging, cnferencing. Micrsft Partner Prgram has certified the integratin between MX-ONE V.4.0 and Micrsft Office Cmmunicatins Server 2007 R2 via a Direct SIP cnnectin. 1.2 Scpe f this dcument The intent f this guide is t describe the basic integratin between the Aastra MX-ONE and Micrsft OCS 2007 R2. The fllwing sectins describe the slutin integratin that has been certified thrugh the Micrsft partner prgram and cvers nly the Direct SIP integratin. Hwever, MX-ONE integratin with Micrsft OCS 2007 R2 is als supprted via Dual Frking and Remte Call Cntrl. Fr a mre technical descriptin n hw these integratins are set-up and functin, refer t the relevant CPI dcumentatin fr MX-ONE r g t the Micrsft UC prduct websites. Please, always check the latest prducts dcumentatin. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

4 2 Slutin Descriptin The integratin f MX-ONE V.4 and Micrsft OCS 2007 R2 described in this guide is achieved via Direct SIP. Direct SIP that is specified by Micrsft means that a SIP trunk is used t cnnect MX-ONE Telephny System 4.0 and OCS 2007 R2 (Mediatin Server). The SIP trunk cnnectin between the systems can be deplyed with r withut encryptin. MX-ONE Telephny System supprts TLS and SRTP as the SIP transprt mechanism when cnnected with Mediatin Server. Figure 1 - MX-ONETelephny System 4.0 integratin with Micrsft OCS 2007 R2 via Direct SIP Micrsft Office Cmmunicatins Server 2007 R2 (OCS 2007 R2) ffers several capabilities and may be cnfigured based n the specific custmer prject requirements. This guide cvers nly the cmpnents that are required in the integratin between MX-ONE Telephny System 4.0 and OCS 2007 R2 via Direct SIP t ffer the functinality required by the Micrsft certificatin prgram. At least the fllwing Micrsft OCS 2007 R2 cmpnents are required in rder t supprt this integratin: Server Infrastructure Micrsft infrastructure (Active Directry, DNS, etc.) Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

5 Micrsft Office Cmmunicatins Server 2007 R2 Standard r Enterprise Editin Micrsft Mediatin Server Client Micrsft Office Cmmunicatr Client (OC Client) The Micrsft Office Cmmunicatr Client (OC Client) is the end user device in the Micrsft OCS 2007 R2. It may als be used as a sft-client with MX-ONE when the systems are integrated via the ptinal Dual Frking scenari. 2.1 Direct SIP In Direct SIP integratin, referred t as Enterprise Vice by Micrsft,, Office Cmmunicatr users will have dedicated phne numbers that differs frm thse used in the MX-ONE. Figure 2 - Direct SIP user view This enables the Office Cmmunicatr (OC) client t make and receive external calls thrugh a PC. The calls are ruted frm the OCS by the SIP trunk t the MX-ONE and further t the PSTN and vice-versa. Figure 3 - MX-ONE Signaling Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

6 MX-ONE Telephny System 4.0 and OCS 2007 R2 will behave as netwrked PBX s, as typically is the case with all external trunks in the MX-ONE. MX-ONE has features, such as Dual Frking and Parallel Ringing that can hide these different numbers and thse features may be cmbined with the direct SIP integratin in rder t keep nly ne single number visible fr the end user. Fr a mre technical descriptin n hw these integratins are set-up and functin, please refer t the relevant CPI dcumentatin fr MX-ONE. 2.2 Features MX-ONE V.4.0 integrated with Micrsft Office Cmmunicatins Server 2007 R2 via Direct SIP delivers the fllwing end user features: Sftphne features: Make and Receive calls Call Hld/Retrieval Frwarding Call by cntacts Transfer Inband DTMF supprt accrding t RFC 2833, fr services, fr example bank accunt verificatin, where DTMF relay is required. Instant Messaging Cnference Presence between OC clients 2.3 Prerequisites In rder t have the prper integratin between MX-ONE and Micrsft Office Cmmunicatins Server using Direct SIP, there are sme prerequisites n bth sides that must be fulfilled MX-ONE On MX-ONE side, at least ne Telephny Server and ne Media Gateway are required t interwrk with Micrsft OCS 2007 R2. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

7 Main cmpnents: At least the fllwing MX-ONE cmpnents are required: Telephny System Telephny Server MX-ONE Telephny Server 4.0 SP1 r later Supprted Media gateways MX-ONE Classic - 7U 19-inch chassis, using IPLU r MGU bards r MX-ONE Lite - 3U 19-inch chassis, using MGU gateway Terminals All current MX-ONE Analg, Digital, DECT, IP and Mbile extensin terminal types are supprted with this integratin Licenses: The list f apprpriate MX-ONE licenses needed fr this integratin is nt part f the scpe f this guide. Hwever, the license requirements fr this integratin can be fund in the Cmmercial Prduct Descriptin - Aastra MX-ONE V.4.0 Integratin with Micrsft OCS 2007 R2 and Micrsft Exchange Server 2010 UM Micrsft Office Cmmunicatins Server 2007 R2 A Micrsft envirnment needs t be available in the custmer site. Nte that the Micrsft OCS 2007 R2 is nt part f the MX-ONE ffering. It is imprtant that Micrsft cmpetent engineers be used fr installatin and integratin accrding t the MX-ONE cnfiguratin guidelines fr the interface between the systems Main Cmpnents: The main Micrsft cmpnents that are required t intercnnect with MX-ONE are Micrsft OCS Server 2007 R2, the Mediatin Server and the OC client. The OCS 2007 R2 requirements are fund in the Micrsft Office Cmmunicatins Server 2007 R2 dcumentatin, see the item References in the end f this guide License Micrsft licenses needed fr this integratin are nt included as part f the scpe f this guide. Please cntact Micrsft r a qualified Micrsft partner t btain the Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

8 prper license requirements fr each cmpnent f the Micrsft Office Cmmunicatins Server 2007 R2 slutin. 3 Installatin and cnfiguratin 3.1 Installatin MX-ONE Installatin It is assumed that MX-ONE V.4.0 SP1 r later is installed in the custmer envirnment. The system installatin is nt cvered in this guide and shuld be perfrmed by a qualified Aastra certified partner prir t the start f the integratin wrk. Fr MX-ONE V.4.0 installatin, please check the apprpriate CPI dcumentatin fr MX- ONE Micrsft infrastructure and OCS 2007 R2 Installatin It is assumed that Micrsft infrastructure and Micrsft Office Cmmunicatins Server 2007 R2 are installed in the custmer envirnment by a qualified engineer. Fr Micrsft infrastructure requirements and Micrsft Office Cmmunicatins Server 2007 R2 installatin, please check the apprpriate Micrsft dcumentatin. Fr mre details f Micrsft deplyment, g t: Deplying Micrsft Office Cmmunicatins Server 2007 R2 ( 3.2 Cnfiguratin The fllwing infrmatin is used in this guide, based in Aastra s labratry setup: MX-ONE Telephny Server IP address: FQDN:sn3112.radrunner.as.zr.zeruela.lab.se Micrsft OCS Server 2007 R2, Active Directry, Certificatin Authrity and DNS Server: IP address: Mediatin Server: FQDN: stcsr2.as.zr.zeruela.lab.se IP address: FQDN: stexc2.as.zr.zeruela.lab.se Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

9 3.2.1 MX-ONE Cnfiguratin A SIP trunk has t be cnfigured in MX-ONE Telephny System as well the access cde fr this rute. The setup presented belw uses TCP as transprt prtcl, in this case the destinatin access is expected t listening n prt 5060 as default. This might be changed using SIP rute parameter remteprt In rder t secure a gd interperability between MX-ONE and Micrsft OCS 2007 R2, we recmmend the use f Frced Gateway because it will guarantee the same behavir fr all type f calls passing thrugh MX-ONE and ging t OCS 2007 R2. number_initiate -numbertype ED -number 2110 number_data_initiate -externalnumber minlength 4 -maxlength 5 sip_rute -set -rute 51 -uristring sip:?@ frmuri0 sip:?@ prtcl tcp -cdecs PCMA,PCMU sip_rute -set -rute 51 -accept REMOTE_IP -match ROCAI:ROU=51,SEL= ,SIG= A0,TRAF= ,TRM=4,SERV= ,BCAP=000100; #varc d5=1 frced gateway RODAI:ROU=51,TYPE=TL66,VARI= ,VARC= ,VARO= ; RODDI:ru=51,dest=2110,adc= ,srt=1; Server 1 has the IP address , s the rute needs t be defined in the Server 1. ROEQI:ROU=51,TRU=1-1; Micrsft Office Cmmunicatins Server R2 cnfiguratin This guide describes the Micrsft OCS R2 Standard Editin cnfiguratin with ne pl. Micrsft Deplying Enterprise Vice dcumentatin is used fr this setup. ( Open the Office Cmmunicatins Server 2007 snap-in. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

10 as.zr.zeruela.lab.se Figure 4 - Micrsft Office Cmmunicatins Server 2007 snap-in Creating Lcatin Prfiles A Lcatin Prfile is required, please fllw the dcument belw t create it: Fr Create Lcatin Prfiles dcument, g t: ( The screen belw shws an example f Phne number nrmalizatin fr 5 digits. Figure 5 - Lcatin Prfiles Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

11 Assigning Lcatin Prfile t Pl Assign the lcatin prfile t the pl is required, please fllw the dcument belw: Fr Assign Lcatin Prfile t Pl dcument, g t: ( ) The screen belw shws an example f Assign Lcatin Prfile t Pl. Figure 6 - Prfile assciated with a Pl Deplying Mediatin Server Mediatin Server needs t be deplyed, please fllw the dcument belw: Fr Deply Mediatin Server dcument, g t: ( The screens belw shw an example f Mediatin Server deplyment using TCP. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

12 stmedir2.as.zr.zeruela.lab.se Prperties stmedir2.as.zr.zeruela.lab.se Prperties stmedir2.as.zr.zeruela.lab.se stcsr2.as.zr.zeruela.lab.se stmedir2.as.zr.zeruela.lab.se Prperties stmedir2.as.zr.zeruela.lab.se Prperties stmedir2.as.zr.zeruela.lab.se Figure 7 - Mediatin Server Prperties Outbund Call Ruting Outbund Call Ruting needs t be cnfigured, please fllw the dcument belw: Fr Outbund Call Ruting dcument, g t: ( The screens belw shw an example f Outbund Call Ruting: Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

13 stmedir2.as.zr.zeruela.lab.se:5060 Figure 8 - Outbund Call Ruting Enable Users fr Enterprise Vice and PBX Integratin In rder t enable Users fr Enterprise Vice, please fllw the dcument belw: Fr Enable Users fr Enterprise Vice dcument, g t: ( Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

14 The screen belw shw an example f a User with Enterprise Vice: stcsr2.as.zr.zeruela.lab.se Figure 9 - User Setup 3.3 Basic verificatin After the cnfiguratin, we shall check that the setup is k. The fllwing setup is used by the basic verificatin: MX-ONE terminals: (H.323) and (SIP). Micrsft OC Clients: OC Client OC Client 2 Figure 10 - MX-ONE integratin with Micrsft OCS 2007 R2 example Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

15 3.3.1 Micrsft OC client t OC client verificatin T verify the Micrsft OCS 2007 R2 cnfiguratin pen tw OC clients and establish a call between then Micrsft OC Client t MX-ONE terminal T verify the MX-ONE and Micrsft OCS 2007 R2 cnfiguratin pen OC client and establish a call t an MX-ONE terminal. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

16 3.3.3 MX-ONE terminal t Micrsft OC Client T verify the MX-ONE and Micrsft OCS 2007 R2 cnfiguratin pen OC client, frm MX- ONE terminal establish a call t OC client PSTN t Micrsft OC Client Frm a PSTN r a mbile phne, establish a call t OC Client. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

17 4 References Please always check the latest dcumentatin. The links belw are the nes available at the time f this guide was written. CPI dcumentatin fr MX-ONE V.4.0 SP1 r later Micrsft Office Cmmunicatins Server 2007 R2: ( Office Cmmunicatins Server Infrastructure Requirements ( Internal Office Cmmunicatins Server Cmpnent Requirements ( Envirnmental Requirements ( Hardware Requirements fr Office Cmmunicatins Server 2007 R2 ( Client System Requirements ( Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18

18 Aastra Technlgies Limited. All rights reserved. This dcument cntains prprietary infrmatin, which is prtected by cpyright. N part f this dcument may be reprduced r transmitted in any frm r by any means, electrnic r mechanical, including phtcpying, recrding, r by any infrmatin strage and retrieval system, r translated int anther language, withut prir written cnsent f Aastra Technlgies Limited, Cncrd, Ontari, Canada. NOTICE The infrmatin in this dcument is subject t change withut ntice. 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 nt be liable fr errrs cntained herein nr fr incidental r cnsequential damages in cnnectin with the furnishing, perfrmance r use f this material. Aastra Technlgies Limited Cncrd, Ontari, Canada. Dc. N. ASE/MXO/PLM/ 0123 / EN Rev. B Date: /18