AASTRA MX-ONE, A700 User Manual
Quick Setup Guide
Integration of Aastra MX-ONE™ / Aastra 700 and
®
Microsoft
Aastra MX-ONE
Lync Server™ 2010
TM
and Aastra 700 running Telephony Server software V.4.1 SP3 and later
Aastra Telecom Sweden AB
Box 42214, SE-126 17 Stockholm, Sweden
Tel +46 8 568 67000
www.aastra.com
Date: 2011-12-01
Doc. no.: ASE/MXO/PLM/0244/0/1/EN Rev.B
Contents
1 Introduction .............................................................................................................. 3
1.1 General ................................................................................................................................................... 3
1.2 Scope of this document ........................................................................................................................ 3
2 Integration Description ............................................................................................ 4
2.1 Direct SIP ............................................................................................................................................... 4
2.2 Direct SIP signalling overview ............................................................................................................. 5
2.3 Direct SIP supported features .............................................................................................................. 5
3 Prerequisites ............................................................................................................ 6
3.1 MX-ONE requirements .......................................................................................................................... 6
3.1.1 Main components: ................................................................................................................................................. 6
3.1.2 Licenses ................................................................................................................................................................. 6
3.2 Microsoft Lync Server 2010 ................................................................................................................. 6
3.2.1 Main components .................................................................................................................................................. 6
3.2.2 Licenses ................................................................................................................................................................. 6
4 Installation and configuration ................................................................................. 7
4.1 Installation ............................................................................................................................................. 7
4.1.1 MX-ONE Installation .............................................................................................................................................. 7
4.1.2 Microsoft infrastructure ........................................................................................................................................ 7
4.2 Configuration ......................................................................................................................................... 7
4.2.1 Direct SIP Setup ..................................................................................................................................................... 7
4.2.2 Direct SIP with security and Media Bypass setup ............................................................................................ 14
5 Integration Notes ................................................................................................... 18
6 References ............................................................................................................. 18
7 Revision History .................................................................................................... 18
2 (19)
1 Introduction
Aastra MX-ONE and Aastra 700 communications systems running Telephony Server software V.4.1
SP3 or later can be integrated with Microsoft Lync Server 2010 via Direct SIP integration. As Aastra
MX-ONE and Aastra 700 run the same software, in the next chapters only Aastra MX-ONE is referred
to. However, if there are differences between them it will be mentioned in this guide.
Aastra MX-ONE is a complete IP-based communications system with unparalleled capabilities for
mobile users. Not only does Aastra MX-ONE provide excellent voice communications, it also provides
the applications necessary to offer true mobility and Unified Communications (UC).
Aastra MX-ONE communications system is based on an open software and hardware environment,
using standard servers with a Linux SUSE operating system. Furthermore, Aastra MX-ONE
integrates with third party solutions using standards based interfaces, such as SIP and CSTA
V3/XML. This open standards approach enables Aastra to offer our customers a choice and with this
in mind we have worked together with Microsoft to ensure that Aastra MX-ONE can be integrated with
the latest Microsoft UC products. Aastra MX-ONE V.4.1 SP3 is fully certified by the Microsoft Partner
Program to ensure that customers have seamless experiences with setup, support, and use of Aastra
MX-ONE communications system with Microsoft UC software. Aastra MX-ONE integrates with
Microsoft UC solutions directly via a SIP connection to reduce the overall cost and complexity of the
combined solution.
1.1 General
Integration of Aastra MX-ONE with the Microsoft Lync Server 2010 is supported as a complementary
solution providing end user services like instant messaging, conferencing etc. Microsoft Partner
Program has certified the integration between Aastra MX-ONE communications system running
Telephony Server software V.4.1 SP3 and Microsoft Lync Server 2010 via a Direct SIP connection.
1.2 Scope of this document
The intent of this guide is to describe the basic integration between the Aastra MX-ONE and Microsoft
Lync Server 2010. The following sections describe the solution integration that has been certified
through the Microsoft Partner Program and covers only the Direct SIP integration. For a more
technical description on how these integrations are set-up and function, please refer to the relevant
CPI documentation for MX-ONE or go to the Microsoft UC product websites.
As a general rule, it is always recommended to check the latest products documentation.
3 (19)
2 Integration Description
The integration of Aastra MX-ONEand Microsoft Lync Server 2010 described in this guide is achieved
via Direct SIP. Direct SIP that is specified by Microsoft means that a SIP trunk is used to connect
Aastra MX-ONEand Microsoft Lync Server 2010 (Mediation Server). The SIP trunk connection
between the systems can be deployed with or without encryption. Aastra MX-ONE supports TLS and
SRTP encryption protocols as the SIP transport mechanism when connected with Mediation Server.
Figure 1 - Direct SIP topology
This guide covers only the components that are required in the integration between Aastra MX-ONE
V.4.1 SP3 or later and Lync Server 2010 via Direct SIP to offer the functionality required by the
Microsoft UC Open Interoperability Program for enterprise telephony services and infrastructure.
At least the following Microsoft Lync Server 2010 components are required in order to support this
integration:
• Server Infrastructure
• Microsoft infrastructure (Domain Controller, Active Directory, DNS, etc.)
• Microsoft Lync Server 2010 Standard or Enterprise Edition
• Microsoft Mediation Server
• Client
• Lync 2010
2.1 Direct SIP
In Direct SIP integration, referred to as Enterprise Voice by Microsoft Lync 2010 users will have
dedicated phone numbers that differs from those used in the MX-ONE.
Figure 2 - Direct SIP type of users
This enables the Lync 2010 client to make and receive external calls through a PC. The calls are
routed from the Lync Server 2010 by the SIP trunk to the MX-ONE and further to the PSTN and viceversa. MX-ONE and Microsoft Lync Server 2010 will behave as networked PBX’s, as typically is the
case with all external trunks in the MX-ONE.
4 (19)
2.2 Direct SIP signalling overview
Aastra MX-ONE supports SIP/TCP or SIP/TLS as the SIP transport mechanism when connected with
Mediation Server.
The ports used for such connections are:
• SIP/TCP: 5060
• SIP/TLS: 5061
SI
P
/T
5067
LS:
Figure 3 - Solution integration Direct SIP signaling
2.3 Direct SIP supported features
During the certification process the following Lync features were validated with MX-ONE Telephony
Server software V.4.1 SP3.
• Basic Call services between MX-ONE and Lync end-points over SIP trunks
• Anonymous user calls
• Caller ID on both sides
• Decline call
• Call forwarding and simultaneously ring feature
• Inbound and outbound calls
• Media bypass (a.k.a. direct media between MX-ONE and Lync clients). Encryption (TLS
and STRP) is required for this functionality.
• Inbound call from MX-ONE user device to Lync client
• Outbound call from Lync client to MX-ONE user device
• Outbound call: Call Forward All (CFA) to another Lync client
• Outbound call from Lync with by-pass enabled and CFA enabled to another Lync
user
• Outbound call: PBX CFB (Call Forward on Busy) to another Lync user
• Outbound call from Lync with by-pass enabled and CFB enabled to another Lync user
• Conference
• Failover (to secondary Lync gateway)
• Security (support for TLS/SRTP encryption)
5 (19)
3 Prerequisites
In order to have the proper integration between Aastra MX-ONE and Microsoft Lync Server using
Direct SIP, there are some prerequisites on both sides that must be fulfilled.
3.1 MX-ONE requirements
On the Aastra MX-ONE side, at least one Telephony Server and one Media Gateway are required to
interwork with Microsoft Lync Server 2010.
3.1.1 Main components:
At least the following MX-ONE components are required:
• Aastra MX-ONE communications system
• Telephony Server
• MX-ONE Telephony Server V.4.1 SP3 or later
• Supported media gateways with the latest compatible firmware with V.4.1 SP3
• MX-ONE Classic - 7U 19-inch chassis, using IPLU or MGU boards or
• MX-ONE Lite - 3U 19-inch chassis, using MGU board
• Aastra 700 V.1.0.4 or later
• Telephony Server
• MX-ONE Telephony Server V.4.1 SP3 or later
• Supported media gateway with the latest compatible firmware with V.4.1 SP3
• MX-ONE Lite - 3U 19-inch chassis, using MGU board
• Terminals
• All current MX-ONE terminal types are supported with this integration:
SIP, H.323, analog, digital, DECT and mobile extension
3.1.2 Licenses
The Aastra MX-ONE licenses needed for this integration are:
• SIP trunk licenses, please note that the quantity of licenses depend on how the system is
deployed.
• Encryption licenses are required if security is used.
Please always check with your Aastra partner that your system has the correct licenses, before
beginning the integration deployment.
3.2 Microsoft Lync Server 2010
A Microsoft environment needs to be in place in the customer site. Note that the Microsoft Lync is not
part of the MX-ONE offering. It is important that Microsoft competent engineers are used for
installation and integration according to the MX-ONE configuration guidelines for the interface
between the systems.
3.2.1 Main components
The main Microsoft components that are required to interconnect with Aastra MX-ONE are Microsoft
Lync Server, the Mediation Server and the Lync client. The Lync requirements are found in the
Microsoft Lync Server documentation, see the chapter References in the end of this guide.
3.2.2 Licenses
Microsoft licenses needed for this integration are not included as part of the scope of this guide.
Please contact Microsoft or a qualified Microsoft partner to obtain the proper license requirements for
each component of the Microsoft Lync Server solution.
6 (19)
Loading...