1 mx-one installation, 2 microsoft infrastructure, 1 direct sip setup – AASTRA MX-ONE_A700_MS Lync 2010 Quick Setup Guide User Manual
Page 7: Installation and configuration, Installation, Mx-one installation, Microsoft infrastructure, Configuration, Direct sip setup, 4installation and configuration
7 (19)
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.