AASTRA MX-ONE_A700_MS Lync 2010 Quick Setup Guide - Manual (Page 4)

4 (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 vice-
versa. 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.