7Revision History .................................................................................................... 18
2 (19)
Page 3
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)
Page 4
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)
Page 5
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)
Page 6
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)
Page 7
4 Installation and configuration
4.1 Installation
4.1.1 MX-ONE Installation
It is assumed that MX-ONE Telephony Server software V.4.1 SP3 or later is installed in the customer
environment. The system installation is not covered in this guide and should be performed by a
qualified Aastra certified partner prior to the start of the integration work.
For Aastra MX-ONE installation, please check the appropriate CPI documentation.
4.1.2 Microsoft infrastructure
It is assumed that Microsoft infrastructure and Microsoft Lync Server are installed in the customer
environment by a qualified engineer.
For Microsoft infrastructure and Microsoft Lync Server requirements please check the appropriate
Microsoft documentation.
4.2 Configuration
The following information was used in Aastra’s laboratory setup during the validation of the solution.
The setup may change depending of the customer specific needs.
Note that Fully Qualified Domain Name (FQDN) needs to be properly specified in the Domain Name
System (DNS).
• MX-ONE Telephony System V.4.1 SP3
• IP address: 192.168.222.84
• FQDN: mxone-lync.as.zr.zeruela.lab.se
• Microsoft Domain Controller, Active Directory, Certification Authority and DNS Server:
• IP address: 192.168.222.45
• FQDN: lync-infra.as.zr.zeruela.lab.se
• Lync Server Standard Edition and Mediation pool
• IP address: 192.168.222.90
• FQDN: lync-stand.as.zr.zeruela.lab.se
4.2.1 Direct SIP Setup
A SIP trunk has to be configured in Aastra MX-ONE as well as the access code for this route.
The setup presented below uses TCP as transport protocol, in this case the destination access is
expected to listening on port 5068 as default. This might be changed using SIP route parameter
“remote port”.
In order to secure a good interoperability between Aastra MX-ONE and Microsoft Lync Server 2010,
Aastra recommend the use of “Forced Gateway”, because it will guarantee the same behavior for all
type of calls passing through MX-ONE and going to Lync Server 2010.
7 (19)
Page 8
1) MX-ONE Direct SIP setup
The figure below shows the Direct SIP configuration used in this guide:
Microsoft® DC,AD, CA and DNS Server
IP= 192.168.222.45
FQDN= lync-infra.as.zr.zeruela.lab.se
T
IP
S
R
P/
T
SR
Lync Server and Mediation Server
IP= 192.168.222.90
FQDN= lync-stand.as.zr.zeruela.lab.se
SIP Traffic: TCP or TLS
SIP Traffic: TLS
SRTP/RTCP Traffic
RTP/TCP or SRTP/RTCP Traffic
S
L
P
C
T
SIP Trunk
RTP/TCP
TCP
Lync
Client
S
D
I
MX-ONE or A700 V.4.1 SP3
IP= 192.168.222.84
FQDN= mxone-lync.as.zr.zeruela.lab.se
o
N
e
R
t
u
o
P
S
I
r
PSTN / PLMN
or SIP operator
Figure 4 – Direct SIP detailed signaling
The following setup needs to be done in MX-ONE in order to configure Direct SIP, please note that
only SIP Route definitions are showed.
In order to finalize the configuration between Aastra MX-ONE and Microsoft Lync Server 2010 the
following needs to be done:
Define PSTN Gateway in the Lync Server 2010 Topology Builder
Open Lync Server 2010, Topology Builder and
define a PSTN gateway in the Mediation
Server to be used between Lync and MX-ONE.
• To define the PSTN gateway, expand
Mediation pools, right click in the
Mediation Server to be used, Choose
Edit Properties
Figure 5 – Meditation pools
• Click in New, the Define New IP/PSTN Gateway dialog box appears, type the following:
• Gateway FQDN or IP Address: specify the MX-ONE IP Address or FQDN
• Listening port for IP/PSTN gateway: specify the port to be used, 5060
• SIP Transport Protocol: TCP
Figure 5 - Define New IP/PSTN Gateway
9 (19)
Page 10
• Publish the topology
Figure 6 - Publish topology
Define a Dial Plan
The Dial Plan configuration is required to allow Lync users to dial to MX-ONE terminals as well as
PSTN. To define it, execute the following:
• Open the Lync Server Control Panel
• Click Voice Routing and choose Dial Plan
• Define Normalization rules that fits your organization needs, at least a rule for Lync users
to dial to MX-ONE terminals and another for PSTN (assuming that MX-ONE is connected
with the PSTN) is required. Please contact Microsoft for the appropriate setup for your
company as needed
Figure 7 - New Normalization Rule, five digits example
• Commit the changes
10 (19)
Page 11
Define Voice Policy
A voice policy is required to make possible Lync users to dial out via the Direct SIP connection using
MX-ONE. Lync client users need to be assigned for this policy afterwards.
To create the Voice Policy:
• Click Voice Routing and choose Voice Policy
• Click in New and choose the type of policy that is applicable for your company setup, site
policy or user policy
• Define a name and description for this voice policy
Figure 8 - New Voice Policy
• Associate a new PSTN for this policy, click New
• Define a name and description for this new PSTN usage record
Figure 9 - New PSTN Usage Record
• Click New to associate a Route with this PSTN usage record
11 (19)
Page 12
• Define a name and description for this New Route
• Associate the MX-ONE gateway created previously with this New Route, to do it click Add
in Associated Gateways
Figure 10 - New route
12 (19)
Page 13
• In the Select Gateway select the MX-ONE gateway created previously
• Click OK for all questions in order to keep the configurations
• Commit all changes
Figure12 – Select Gateway
Define Trunk Configuration
In order to assign the MX-ONE gateway to a site or pool trunk execute the following:
• Click in Voice Routing and then click in Trunk Configuration
• Click in New and choose the type of trunk that is applicable for your company setup, site
trunk or pool trunk
Figure 11 - New Trunk configuration
13 (19)
Page 14
• Select the Encryption support level, in this case, Not supported
Figure 12 - Encryption support level
• Commit all changes
Now the setup is concluded, assign users with the Policy created previously and test the integration
making calls between the systems.
Please check Enable Users for Enterprise Voice setup in the link below:
http://technet.microsoft.com/en-us/lync/gg413011
4.2.2 Direct SIP with security and Media Bypass setup
The figure below shows the Direct SIP with security and Media Bypass configuration used in this
guide:
Microsoft® DC,AD, CA and DNS Server
IP= 192.168.222.45
FQDN= lync-infra.as.zr.zeruela.lab.se
TL
P
I
S
S
Lync
Client
Lync Server and Mediation Server
IP= 192.168.222.90
FQDN= lync-stand.as.zr.zeruela.lab.se
SIP Traffic: TCP or TLS
SIP Traffic: TLS
SRTP/RTCP Traffic
SIP Trunk
TLS
S
D
N
I
MX-ONE or A700 V.4.1 SP3
IP= 192.168.222.84
FQDN= mxone-lync.as.zr.zeruela.lab.se
r
o
e
R
t
u
o
P
S
I
PSTN / PLMN
or SIP operator
Figure 13 - Security and Media bypass detailed signaling
1) MX-ONE Direct SIP with security and Media Bypass setup
The following setup needs to be done in MX-ONE in order to configure Direct SIP with security
(encryption), please note that only SIP Route definitions are showed.
Note that MX-ONE FQDN needs to be properly defined in the DNS Server.
When using security an appropriate certificate needs to be installed in MX-ONE as well as the
encryption licenses.
Note that TLS/SRTP security is required for Media bypass functionality.
Import the server certificate mx-one-certificate.pfx to MX-ONE Telephony Server. On the access
Server, for example, Telephony Server 1 runs the following command:
Certificate installation
Install the certificate in the Telephony Server 1:
cert_install_local mx-one-certificate.pfx
2) Lync configuration
In order to finalize the configuration between Aastra MX-ONE and Microsoft Lync Server 2010 the
following needs to be done:
Define PSTN Gateway in the Lync Server 2010 Topology Builder
Open Lync Server 2010, Topology Builder and define a PSTN gateway in the Mediation Server to be
used between Lync and MX-ONE.
• To define the PSTN gateway, expand Mediation pools, right click in the Mediation Server
to be used, choose Edit Properties
Figure 14 - Mediation pools
15 (19)
Page 16
• Click in New, the Define New IP/PSTN Gateway dialog box appears, type the following:
• Gateway FQDN or IP Address: specify the MX-ONE IP Address or FQDN
• Listening port for IP/PSTN gateway: specify the port to be used, 5061
• SIP Transport Protocol: TLS
Figure 15 - Define New IP/PSTN Gateway
• Publish the topology
Figure 16 - Publish topology
Define Dial Plan, Voice Policy
Define Dial Plan, Voice Policy as explained previously in this guide.
16 (19)
Page 17
Define Trunk Configuration
In order to assign the MX-ONE gateway to a site or pool trunk execute the following:
• Click in Voice Routing and then click in Trunk Configuration
• Click in New and choose the type of trunk that is applicable for your company setup, site
trunk or pool trunk
Figure 17 - New Trunk configuration
• Keep the default Encryption support level, in this case, Required
Now the setup is concluded, assign users with the Policy created previously and test the integration
making calls between the systems.
17 (19)
Page 18
5 Integration Notes
Please note that the following scenarios are currently not supported when MX-ONE is integrated with
Lync Server:
• REFER cases:
• OC Client transfers the inbound call to another PSTN phone after answering it when
REFER is enabled
•Result: Originating phone does not hear ring back during the transfer, but once the
PSTN phone answers the call two way voice paths is present
• Solution: Disable REFER
• Outbound Call: Blind transfer to another Client
• Result: Originating phone does not hear ring back during the transfer, but once the
PSTN phone answers the call two way voice paths is present
• Solution: Disable REFER
• Inbound Call: Blind Transfer to PBX user
• Result: Originating phone does not hear ring back during the transfer, but once the
PSTN phone answers the call two way voice paths is present
• Solution: Disable REFER
• Early Media before answer.
• MX-ONE does not support sending DTMF as a part of early media.
6 References
Please always check the latest documentation. The links below are the ones available at the time of
this guide was written.
Aastra CPI Documentation – Aastra MX-ONE V.4.1 SP3 and Aastra 700 V.1.0.4 or later.
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.