Quick Setup Guide

A Mitel Company

Setup Guide for Aastra 400 and

Microsoft Lync 2013

.................................................................................................................

Aastra Telecom Schweiz AG

Ziegelmattstrasse 1
CH-4503 Solothurn

13.03.2014 - depl-2033/1.1

Table of Contents
1

Introduction .................................................................................................................. 4
1.1
1.2
1.3
1.4

Aastra 400 and Lync 2013 Interoperability................................................................. 6

2.1
2.2
2.3

Aastra 400 as Gateway ....................................................................................................................10

Aastra 400 as Gateway with Simultaneously ring on Lync 2013 ..............................................10
Aastra 400 as IP-PBX with One Number........................................................................................10

Aastra 400 Requirements / Limitations .................................................................... 12

4.1
4.2
4.3

Direct SIP and Aastra 400 .................................................................................................................6

Direct SIP signalling ..........................................................................................................................7
Direct SIP supported features ..........................................................................................................7
2.3.1 Basic features..............................................................................................................................7
2.3.2 DNS Load Balancing Support .....................................................................................................8
2.3.3 Fail-over Routing Enhancements ................................................................................................8
2.3.4 SIP Trunking Enhancements for M:N redundancy support .........................................................9
2.3.5 Additional SIP Header support ....................................................................................................9

Use Cases ................................................................................................................... 10

3.1
3.2
3.3

Purpose ..............................................................................................................................................4
Summary ............................................................................................................................................4
References .........................................................................................................................................4
Definitions and Abbreviations..........................................................................................................4

Hardware/Software ..........................................................................................................................12
Licences ...........................................................................................................................................12
Limitations .......................................................................................................................................12

General Configuration Settings ................................................................................ 13

5.1

General Aastra 400 Configuration .................................................................................................13

5.1.1 Certification Handling ................................................................................................................13
5.1.2 FQDNs ......................................................................................................................................13
5.1.3 Lync 2013 trunk .........................................................................................................................16
5.1.4 Fail-over Routing .......................................................................................................................16
5.1.5 DNS Load Balancing Support ...................................................................................................17
5.2 General Lync 2013 Configuration ..................................................................................................18
5.2.1 Configuration without Encryption ...............................................................................................18
5.2.2 Lync 2013 configuration with encryption ...................................................................................27

Configuration as Gateway ......................................................................................... 29

6.1

Aastra 400 Configuration ................................................................................................................29

6.1.1 PISN user ..................................................................................................................................29
6.1.2 Direct Dialling In (DDI numbers)................................................................................................29
6.1.3 Aastra 400 licences ...................................................................................................................29
6.2 Lync 2013 configuration .................................................................................................................29

Aastra 400 Configuration as Gateway with Simultaneously ring on Lync 2013 . 30

7.1

Aastra 400 Configuration ................................................................................................................30

7.1.1 Aastra 400 Licences ..................................................................................................................30
7.2 Lync 2013 Configuration.................................................................................................................30
7.2.1 Define a additional Dial Plan .....................................................................................................31
7.2.2 Lync 2013 Client configuration ..................................................................................................32

Aastra 400 Configuration as IP PBX with One Number ........................................ 33

8.1

Aastra 400 configuration ................................................................................................................34

8.1.1 Direct Dialling In (DDI numbers)................................................................................................34
8.1.2 Aastra 400 Licences ..................................................................................................................34
8.1.3 AMC/GSM Terminal ..................................................................................................................34
8.1.4 Route configuration ...................................................................................................................35

...........

8.2

8.1.5 Trunk group configuration ......................................................................................................... 36

Lync 2013 configuration ................................................................................................................. 37
8.2.1 User configuration Lync 2013 ................................................................................................... 37
8.2.2 Define a Dial Plan ..................................................................................................................... 38
8.2.3 Define Voice Policy ................................................................................................................... 38
8.2.4 Define Trunk Configuration ....................................................................................................... 38

A Appendix .................................................................................................................... 39
A.1
A.2

Create a certificate for Aastra 400 from the MS Certification Authority .................................... 39
Supported features with integrated Lync 2013 client .................................................................. 47

...........

Introduction

1.1

Purpose

This document describes the interoperability of Microsoft Lync 2013 with the communication server Aastra
400. It lists the supported features and the specific configuration needed for the Aastra 400 and the Microsoft
Lync 2013. The document is addressed to people who need to install or setup a communication system
including MS Lync 2013 and Aastra 400. It may interest people who want to see which MS Lync features are
supported by Aastra 400.
This document does not describe a full configuration of the Aastra 400 and Microsoft Lync 2013. For
standard configuration issues please refer to the Aastra 400 System manual or the Microsoft Lync 2013
documentation.

1.2

Summary

The Aastra 400 Release R3.1 is an officially qualified endpoint for the Microsoft Unified Communication (UC)
network. It is certified as a so-called IP-PBX which uses the Direct SIP approach to communicate with the
Microsoft Lync Mediation Server. The Aastra 400 supports the following Microsoft Lync 2013 features:

Basic call features (Inbound, Outbound, Caller-Id, Hold, Call-Transfer, Conference)

Certificate Requirement Enhancement

Additional SIP Header Support

Fail-over Routing Enhancements

M:N Routing

DNS Load Balancing Support

It does not support the IPv4/IPv6 support which is optional.

The Microsoft UC qualification was done with the Aastra 470.

1.3

References

[1] Microsoft Partner Specification V3.0 Direct SIP Incremental Feature Spec W15
( only for Microsoft Lync 2013 partners )
[2] Aastra 400 Business Communication Solution Documentation Set English
http://www.aastra.com/docfinder
( only for Aastra 400 partners )

Further information on the Microsoft Homepage

Lync Server

http://technet.microsoft.com/en-us/library/gg293124.aspx

Deploying Enterprise Voice

http://technet.microsoft.com/en-us/library/gg412876.aspx

Enable Users for Enterprise Voice

http://technet.microsoft.com/en-us/lync/gg413011

1.4

Definitions and Abbreviations

CA

Certificate Authority

DDI number

Direct Dialling In number, also called DID number Direct Inward Dialing number

DECT

Digital Enhanced Cordless Telecommunications

DHCP

Dynamic Host Configuration Protocol

...........

DNS

Domain Name Service

DTMF

Dual-tone multi-frequency

FQDN

Fully Qualified Domain Name

IP-PBX

Private Branch Exchange that supports IP communication (VoIP)

ISDN

Integrated Services Digital Network

PISN

Private Integrated Services Network

PISN user

a user located on another networked Communication Server

PFX

see PKCS 12

PKCS 12

In cryptography, PKCS #12 defines an archive file format for storing many cryptography
objects as a single file. It is used to bundle a private key with its X.509 certificate and to
bundle all the members of a chain of trust.

PSTN

Public Switching Telephony Network

RTCP

RTP Control Protocol

RTP

Real-time Transport Protocol (Media/voice data)

SIP

Session Initiation Protocol

SRTP

Secure Real-time Transport Protocol (secure Media/voice data)

TLS

Transport Layer Security

VoIP

Voice over IP

X.509

In cryptography, X.509 is an ITU-T standard for a public key infrastructure (PKI) and
Privilege Management Infrastructure (PMI). X.509 specifies, amongst other things,
standard formats for public key certificates, certificate revocation lists, attribute
certificates, and a certification path validation algorithm.

...........

Aastra 400 and Lync 2013 Interoperability

The interoperability of Microsoft Lync 2013 and Aastra 400 described in this document is achieved by using
the Direct SIP approach offered by Microsoft. Direct SIP is specified by Microsoft Lync, which means that a
SIP connection, e.g. SIP networking or SIP Trunk, is used to connect one or more Lync 2013 Mediation
Servers with Aastra 400.

2.1

Direct SIP and Aastra 400

The figure below shows the Direct SIP approach with the Lync Mediation Server and the Aastra 400 using
the SIP protocol for signalling and the Real Time Protocol (RTP) for media, between the two entities. The
Aastra 400 receives calls e.g. from the PSTN and routes them via the SIP trunk to the Lync Mediation Server.
The Lync Mediation Server passes each call to the Lync Server, and the Lync Server routes the call to its
destination, e.g. to a Lync User. The media related to the call is established in the same way as the
signalling, i.e. from the PSTN to the Aastra 400, to the Lync Mediation Server and from thereto the Lync
Server or to the Lync User/client . A call from the Lync User to the PSTN follows the same route as described
above in the reverse direction.
Lync 2013
Server
Lync
User
Lync
User

Aastra 400
User
User

External / Public
User
User

Direct SIP

Lync 2013
Mediation
Server

Aastra 400 R3.1

Communication
Server

ISDN or
SIP trunk

PSTN /
SIP

Signalling and Media

traffic
Figure 1: Direct SIP connection Microsoft Lync - Aastra400

...........

2.2

Direct SIP signalling

The Aastra 400 supports the transport protocol TCP for non-secure signalling connections. At the next
layer, the Session Initiation Protocol (SIP) is used. The default port for the SIP service is 5060. For secure
signalling connections, the Transport Layer Security (TLS) is used on top of the TCP connection. The SIP
protocol is carried with the TLS layer. The default port for the secure SIP connection is 5061.
The media streaming for non-secure calls uses the Real Time Protocol (RTP). For secure calls, the media
stream is encrypted using the Secure Real Time Protocol (SRTP). Both kinds of media streams (secure and
non-secure) are processed by the media gateway module located on the Aastra 400. This module is also
responsible for handling the Real Time Control Protocol (RTCP) for both kinds of media streams between the
Lync Mediation Server and the Aastra 400 or, when Media Bypass is used, between the Lync client and the
Aastra 400. The picture below shows the possible signalling and media/audio connections described above.
Lync 2013
Server
Lync
User
Aastra 400
User
User

Lync
User

Lync 2013
Mediation
Server(s)

Aastra 400 R3.1

Communication
Server

External / Public
User
User

ISDN or
SIP trunk

PSTN /
SIP

SIP Traffic: TCP or TLS

Audio Traffic. RTP/RTCP or SRTP/RTCP
Audio Traffic. RTP/RTCP or SRTP/RTCP,
when Media Bypass is active on Lync 2013

Figure 2: Signalling and Media traffic overview

2.3
2.3.1

Direct SIP supported features

Basic features
Basic Call services between Aastra 400 and Lync 2013 end-points
o

Anonymous user calls

Caller ID on both sides

Decline call

Call forwarding and Simultaneously ring feature

...........

Inbound and outbound calls

Internal calls to and from Aastra 400 users

Hold / Retrieve

Call Transfer

Conference

Secure communication with encrypted signalling (TLS) and encrypted audio (SRTP)

Comfort noise support (saves IP network bandwidth)

RTCP support

Reliable early media

DTMF

Media bypass (a.k.a. direct media between Aastra 400 and Lync 2013 clients). Encryption (TLS and
STRP) is required for this functionality.

2.3.2

DNS Load Balancing Support

Aastra 400 does a load balancing of calls towards Lync 2013 over a list of Lync 2013 Mediation Servers that
are defined by a FQDN. The DNS server resolves the FQDN into multiple DNS A responses.
Load balancing means that the Aastra 400 resolves the FQDN and keeps an IP address list (Mediation
Server list). The Aastra 400 distributes its outgoing calls among the resolved IP addresses of the list. The
Aastra 400 re-resolves the FQDN according to the TTL (time to live) of the DNS response.

2.3.3

Fail-over Routing Enhancements

The Aastra 400 supported fail-over routing enhancements are implemented as follows:

2.3.3.1

Monitor the Status of each Mediation Server

Fail-over routing can be based on the load-balancing feature described in the previous section. Each
Mediation Server is actively monitored and is marked out of service in the following situations (as mentioned
in [1]):
1.

Not responding to SIP OPTIONS requests for more than five minutes.

2.

Mediation Server responds with a SIP 503 status message to a SIP INVITE request.

3.

Mediation Server does not respond to a SIP INVITE request. The detection timeout can be
configured in Aastra 400.

If a Mediation Server is marked as out of service then the next destination is used automatically. If a
Mediation Server is marked as out of service during call establishment then the next destination is used
automtaically.
As soon as a Mediation Server responds again to a SIP OPTIONS request it is put back in service and is
used again for call establishment.

2.3.3.2

Definition of a Secondary FQDN

The Aastra 400 allows the definition of a secondary FQDN for a Lync 2013 trunk. If all Mediation Servers
defined by the primary FQDN are out of service then a Mediation Server of the secondary FQDN is used for
the call establishment. The Mediation Servers from the second FQDN are in charge until a Mediation Server
from the primary FQDN becomes active again (responds to a SIP OPTIONS message with 2xx).

...........

2.3.4

SIP Trunking Enhancements for M:N redundancy support

Aastra 400 supports several Lync 2013 Mediation Servers.

In addition several independent Aastra 400s can be connected to one Lync 2013.

2.3.5

Additional SIP Header support

The Aastra 400 supports all required SIP headers mentioned in [1].

...........

Use Cases

The Aastra 400 can operate with Lync 2013 in two different configurations:
a)

the Aastra 400 operates as a gateway to connect Lync 2013 with the PSTN, e.g. via ISDN or SIP
trunk lines. The main purpose of this is to allow the Lync users to call to or be called from the PSTN
with a dedicated number.

b)

the Aastra 400 operates as Communication Solution (IP-PBX) which is connected to the Lync 2013.
With this scenario, the Lync 2013 and its clients (Lync client) are quasi integrated as a terminal of an
Aastra 400 user.

Note: The connection to Lync 2013 is done in both cases with Direct SIP.

3.1

Aastra 400 as Gateway

This use case describes the scenario where all users have Lync 2013 clients on their PC. Each user has his
own DDI number (Direct Dialling In / public number).
Inbound calls, identified by the received DDI, are routed through the Aastra 400 directly to Lync 2013.
Outbound calls from the Lync 2013 are routed depending on the dialled target, either to the PSTN via the
configured route or to an Aastra 400 internal destination.
The access to the PSTN can be done on the Aastra 400 via an ISDN Primary or Basic Rate access or via SIP
to a SIP provider.
Additional FAX machines, door intercoms or normal analogue and digital terminals can be attached to the
Aastra 400. These can be reached from the public network or the Lync 2013 clients but there is no tight
integration if a user has a desk/DECT phone and a Lync 2013 client. Such a user is then reachable via two
different numbers, one for the Lync 2013 client and one for the desk/DECT phone.
A Lync 2013 client in a gateway configuration cant make use of many Aastra 400 features, because it isnt
known as an internal user.

3.2

Aastra 400 as Gateway with Simultaneously ring on

Lync 2013

This is a similar configuration as described in 3.1. However in addition to his Lync 2013 client a user has a
DECT phone, a mobile phone or some other phone connected to the Aastra 400.
This setup uses the Lync 2013 feature called Simultaneously ring to call the Aastra 400 phones of the same
user, when someone calls the Lync 2013 client.
The Lync 2013 client and the Aastra 400 phones of the user have different numbers.
Example: The Lync 2013 client has 4123 and the Aastra 400 phones have 3123. The Lync 2013 client 4123
is configured to call simultaneously the 3123 number when someone calls 4123.
Depending on whether the call originates from the Lync 2013 client or one of the Aastra 400 terminals, a
different caller id is shown, 3123 or 4123.

3.3

Aastra 400 as IP-PBX with One Number

In this scenario the Lync 2013 client is configured as one of several terminals of an Aastra 400 user. A user
with just a Lync 2013 client is supported too. A maximum of one Lync 2013 client per user is allowed.
When the user is called, the Aastra 400 calls all configured terminals of the user. Therefore, his desk phone,
his DECT, mobile phone and his Lync 2013 client will ring. Individual terminals can be deactivated depending
on the current presence state. The call can be answered on any of the ringing terminals.
If the user starts a call from the Lync 2013 client or from one of his other phones, always the same caller id is
used.
...........

10

The user is reachable via just one number and he is seen from all his terminals under this one number.
However, the user cannot use all Aastra 400 internal user features from his Lync 2013 terminal. Mainly
features controlled by * and # codes dont work.
As long as the calls from the Lync 2013 client go via the Aastra 400, the TeamKeys and/or BusyLampField
are updated correctly on all the terminals of the Aastra 400.
If a user calls another user with a Lync 2013 client from his Lync 2013 client, then Lync 2013 would naturally
connect both together without informing the Aastra 400. In such a case, the Aastra 400 would not get
informed and the other terminals of the user (One Number) would not be called. The Lync 2013 has to be
configured appropriately, so that calls are routed via the Aastra 400 (see 8).

...........

11

Aastra 400 Requirements / Limitations

4.1

Hardware/Software

For the connection with Lync 2013 at least the following Aastra 400 components are required:

Aastra 470 Communication Server Version R3.1

o

Media gateway module (EIP)

Trunk modules (Primary or Basic rate or analogue trunk lines), depending on the desired PSTN
access.

Terminals
o

All current Aastra 400 terminal types are supported with this interoperability including:
Analogue terminals
FAX devices
Aastra 6860i terminals
Aastra 6700i terminals
Aastra BluStar terminals (Hard- and Softphones)
Aastra Mobile Clients (Mobile phone integration)
DSI digital 2-wire system terminals
DECT terminals
IP system terminals
Standard SIP terminals

4.2

Licences

The following Aastra 400 licences are needed:

SIP access licences: One for each parallel call to Lync 2013.

Lync option licences for SIP access channels: One for each parallel call to Lync 2013.

Secure VoIP licence: Required if TLS/SRTP is used.

Depending on the PSTN access, the Use case chosen and other features the Aastra 400 has to support,
other licences might be required.
Microsoft licenses needed for this interoperability 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 Lync 2013 Server solution.

4.3

Limitations

1)

The Aastra 400 does not support IPv6 addressing on the Lync 2013 interface.

2)

The Aastra 400 does not support the redundancy format RED (RFC 2198).

...........

12

General Configuration Settings

5.1
5.1.1

General Aastra 400 Configuration

Certification Handling

The Aastra 400 is able to import an X.509 host certificate from an external CA. To support mutual TLS with
Lync 2013 the Aastra 400 host certificate must be issued by the same CA as for Lync 2013 and its
Mediations Servers.
When using the MS domain controller CA then the private key for the Aastra 400 must be marked as
exportable. In addition the Aastra 400 checks if the host part of the CN (Canonical Name) belongs to it. It
resolves the host part of the CN and the corresponding IP address must match the current IP address
configuration of the Aastra 400.
The creation process for the Aastra 400 is described in more detail in A.1
The host certificate has to be imported to the Aastra 400 using the WebAdmin configuration tool. The import
procedure expects a PKCS 12 file (pfx file) that contains the Aastra 400 host certificate, the private key and
the trusted CA. The trusted CA is used to verify the signing chain of the server certificates that are presented
from the Mediation Servers to the Aastra 400 during TLS negotiation.

Figure 3: Aastra 400 WebAdmin Import a certificate for Lync

5.1.2

FQDNs

FQDNs are used by the Aastra 400 to support load balancing. Whenever the DNS resolved FQDN returns
multiple DNS A responses then load balancing takes place between these IP addresses.
FQDNs are required when secure communication is to be used (TLS/SRTP).
If non-secure communication is used with Lync 2013 (TCP/RTP) then fixed IP addresses (e.g. 10.100.94.23)
could be used for the Mediation Server(s).
Note: Load Balancing is not supported with fixed IP addresses.

...........

13

Customer site

DNS server
FQDN =
IP addr Mediation Server 1
IP addr Mediation Server 2
IP addr Mediation Server 3

Lync 2013
Server

IP
PSTN /
SIP
Aastra 400

Lync 2013
Mediation Server(s)
Figure 4: The FQDNs are resolved in the DNS server to an IP address or a list of IP addresses

5.1.2.1

Aastra 400 IP-addressing

When the use of a secure connection to Lync 2013 (TLS/SRTP) is required, then FQDN has to be used to
access Lync 2013.
Lync 2013 also accesses the Aastra 400 with an FQDN and therefore the correct hostname and domain has
to be configured in the Aastra 400.

Figure 5: Aastra 400 WebAdmin Configuration of the IP addressing

...........

14

5.1.2.2

DNS server

When the Aastra 400 is in DHCP mode then the DNS server is automatically set. If the Aastra 400 has a
fixed IP address (DHCP off), then the correct DNS server has to be configured so that the Aastra 400 can
resolve the FQDNs of the Lync 2013 Mediation Servers. See Figure 5.
The DNS server itself has to be configured so that all the FQDNs can be resolved.
The FQDNs of the Lync 2013 Mediation Servers can represent a pool of several Lync 2013 Mediation
Servers. In this case, the DNS server returns a list of A records mentioning all the Mediation Servers the
Aastra 400 shall use. See also 5.1.5.

5.1.2.3

FQDN for Lync 2013

As part of the configuration of the Lync 2013 on the Aastra 400 the FQDN of the Mediation Server(s) has to
be configured.

Figure 6: Aastra 400 WebAdmin Configuration of the FQDN of a Lync 2013 trunk

...........

15

5.1.3

Lync 2013 trunk

The access to Lync 2013 is configured under the Private networking menu with the Aastra 400 WebAdmin.
This is only available in the expert mode. Go to SIP networking and Lync and create a new Lync 2013
trunk.
Enter the FQDN/fixed-IP-address under which the primary and the secondary (fail-over) Lync 2013 Mediation
Server(s) are reachable. See 5.1.2
When such a Lync 2013 trunk is created a Trunk group containing this Lync 2013 trunk is automatically
created too. This trunk group has to be added to a route, which is used for all calls to Lync 2013. If the
communication to the Lync 2013 needs to be secure, then the Transport protocol has to be set to TLS.
Furthermore, the SRTP mode shall be set to SRTP forced and the box Requires client certificate shall be
ticked. The address for the Lync 2013 has to be a FQDN.
If the communication to the Lync 2013 Mediation Servers is not to be encrypted, then the Transport protocol
has to be set to TCP, SRTP mode has to be SRTP disabled. The address of the Lync 2013 Mediation
Server(s) can be either an FQDN or a fixed IPv4 address.
Make sure the following settings in the Lync 2013 trunk have these values:
Music on Hold

Off

Call transfer method

REFER

PRACK support

Yes

RTCP support

On

Comfort noise support

On

Enable keep alive

On

Relay RTP stream via communication server

Yes

Use '+' as international prefix

In the newly created Trunk group the following settings should be on
Ring back tone for incoming calls

Generate

Ring back tone for outgoing calls

Generate

Transit CLIP format

Unknown with international prefix

Allow GSM CLIP authentication even if CLIP is not

screened

For later reference it is good practice to give the Lync 2013 trunk, the trunk group and the route containing
this trunk group a self-explanatory name.

5.1.4

Fail-over Routing

There are several possible ways to achieve a fail-over routing:

1.

In the Lync 2013 trunk settings, a Secondary server is configured.

2.

The IP address of the Lync 2013 trunk is an FQDN that resolves to a list of Mediation Servers. If
one or several Mediation Server(s) are down, then the routing fails-over to the next working one.

3.

For each Mediation Server a Lync 2013 trunk is configured. Then in the Route to Lync 2013 a list
of up to 8 Lync 2013 trunks can be configured. The call tries always to use the first in the list, if that
is not successful; it fails-over to the next in the list and so on.

...........

16

5.1.5

DNS Load Balancing Support

Load balancing support requires an FQDN entry in the Lync 2013 trunk.
The DNS server returns a list of Mediation Servers for this FQDN.
The Aastra 400 checks all of these Mediation Servers regularly. If they are online, the Aastra 400 spreads the
calls amongst them (Load Balancing). If one of the Mediation Servers is out of service or not reachable for
any reason, then calls are routed to the next available Mediation Server in the list.
The Aastra 400 Load Balancing is only applied by the Aastra 400 in the direction towards Lync 2013.

...........

17

5.2
5.2.1
5.2.1.1

General Lync 2013 Configuration

Configuration without Encryption
Define PSTN Gateway in the Lync Server 2013 Topology Builder

Open Lync Server 2013 Topology Builder and define a PSTN gateway in the Mediation Server to be used
between Lync and Aastra 400.

To define the PSTN gateway, expand Shared Components, right click in the PSTN gateways.

Figure 7: Lync 2013 Topology Builder New IP/PSTN Gateway

Use the FQDN ot the Aastra 400

Figure 8: FQDN for the new gateway

...........

18

Define the IP address: in this example the default is kept. Click Next.

Figure 9: Define the IP address

...........

19

Define the root trunk

Trunk name: FQDN (Aastra 400)
Listening port for IP/PSTN gateway: 5060 (Aastra 400 SIP TCP port)
SIP Transport Protocol: TCP
Associated Mediation Server: lyncix.aquarium.local
Associated Mediation Server Port: 5068 (default)

Click Next

Figure 10: Define the root trunk

Publish the topology

Figure 11: Publish the new topology

...........

20

5.2.1.2

Define a Dial Plan

The Dial Plan configuration is required to allow Lync users to dial to Aastra 400 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 fit your organizations needs: at least one rule for Lync 2013 users to
dial to Aastra 400 terminals and another for PSTN (assuming that Aastra 400 is connected with the
PSTN) are required. Please contact Microsoft for the appropriate setup for your company as needed

Figure 12: Lync 2013 Dial plan new normalization rule

Commit the changes

5.2.1.3

Define Voice Policy

A voice policy is required to make it possible for Lync 2013 users to dial out via the Direct SIP connection
using Aastra 400. Lync 2013 client users need to be assigned to this policy.
To create the Voice Policy:

Click Voice Routing and choose Voice Policy

...........

21

Click 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 13: New Voice Policy

Associate a new PSTN for this policy, click New

...........

22

Define a name and description for this new PSTN usage record

Figure 14: New PSTN Usage Record

...........

23

Click New to associate a Route with this PSTN usage record

Define a name and description for this New Route

Associate the Aastra 400 gateway created previously with this New Route - click Add in Associated
Gateways

Figure 15: New Voice Route

In the Select Gateway select the Aastra 400 gateway created previously

Figure 16: Select Trunk

Click OK for all questions in order to keep the configurations

Commit all changes

...........

24

5.2.1.4

Define Trunk Configuration

In order to assign the Aastra 400 gateway to a site or pool trunk execute the following:

Click Voice Routing and then click Trunk Configuration

Click New and choose the type of trunk that is applicable for your company setup, site trunk or pool
trunk

Figure 17: Trunk Configuration

...........

25

Select the Encryption support level, in this case, Not supported

Figure 18: Encryption support levels

Commit all changes

Now that the setup is concluded, assign users with the Policy created previously and test the interoperability
by making calls between the systems.
Please check Enable Users for Enterprise Voice setup in the link below:
http://technet.microsoft.com/en-us/library/gg413011.aspx

...........

26

5.2.2

Lync 2013 configuration with encryption

5.2.2.1

Define PSTN Gateway in the Lync Server 2013 Topology Builder

In order to finalize the configuration between Aastra 400 and Lync Server 2013 the following steps need to be
done:
Define the PSTN Gateway in the Lync Server 2013 Topology Builder. Open Lync Server 2013 Topology
Builder and define a PSTN gateway in the Mediation Server to be used between Lync 2013 and Aastra 400.
To define the PSTN gateway, expand Mediation pools, right click in the Mediation Server to be used, choose
Edit Properties

Define the root trunk

Trunk name: FQDN (Aastra 400)
Listening port for IP/PSTN gateway: 5061 (Aastra 400 SIP TLS port)
SIP Transport Protocol: TLS
Associated Mediation Server: lyncix.aquarium.local
Associated Mediation Server Port: 5069

Figure 19: Define root trunk with encryption

Click Next

...........

27

5.2.2.2

Define Trunk Configuration in Lync 2013

In order to assign the Aastra 400 gateway to a site or pool trunk execute the following:

Click Voice Routing and then click Trunk Configuration

Click New and choose the type of trunk that is applicable for your company setup, site trunk or pool
trunk

Figure 20: Trunk configuration with encryption

Select the Encryption support level, in this case, Required

Commit all changes

...........

28

Configuration as Gateway

Only the differences or additional settings in the Aastra 400 compared to the configuration described in 5.1
are mentioned in this section.
This setup refers to the setup mentioned in 3.1
Lync 2013
Server
Lync
User
4523
Lync
User
4567

External / Public
User
User

PISN user
45XX
4500..
4599

Lync 2013
Mediation
Server(s)

Aastra 400 R3.1

Communication
Server

DDI
numbers
326554500..
326554599

PSTN /
SIP

ISDN or
SIP trunk

Figure 21: Overview Aastra 400 operation as Gateway between Lync 2013 and the PSTN

6.1
6.1.1

Aastra 400 Configuration

PISN user

Assuming all the Lync 2013 clients have 4-digit internal numbers in the range 4500-4599, then a PISN user
with the number 45XX has to be created.
The route this PISN user has to use, needs the Trunk group containing the Lync 2013 trunk created earlier.

6.1.2

Direct Dialling In (DDI numbers)

Each Lync 2013 client should have a matching Direct Dialling In number. All these DDI numbers are then
routed to the internal Lync 2013 client number (PISN user).
The DDI numbers are usually sent by the ISDN providers in national format. (e.g. E.164/national 326554523)

6.1.3

Aastra 400 licences

See 4.2 for the necessary licences.

6.2

Lync 2013 configuration

This is described in 5.2. No additional configuration is necessary.

...........

29

Aastra 400 Configuration as Gateway with

Simultaneously ring on Lync 2013
Lync
client
4572

Lync 2013
Server

Simultaneous
ringing to 6572

User 6572

Lync
client
4567
Simultaneous
ringing to 6567

External / Public
User
User

User 6567

PISN user
45XX
4500..4599
Lync 2013
Mediation
Server(s)

Aastra 400 R3.1

Communication
Server

DDI
numbers
326554500..
326554599

PSTN /
SIP

ISDN or
SIP trunk

The two phones belong to the same user but have different phone numbers
Figure 22: Overview Aastra 400 operation with Dual forking on Lync 2013

The Simultaneously ring to the corresponding number has to be configured in the Lync 2013 client.

7.1

Aastra 400 Configuration

The configuration of the Aastra 400 is the same as in 6.1 with the following additional step:

7.1.1

Create the necessary terminals on the Aastra 400.

Aastra 400 Licences

See 4.2 for the necessary licences.

7.2

Lync 2013 Configuration

The configuration of the Lync 2013 is the same as described in 5.2 with for the following additional step:

Configure the Simultaneously ring to the corresponding number in the Lync 2013 client.

...........

30

7.2.1

Define a additional Dial Plan

Figure 23: Dial Plan for PSTN users

...........

31

7.2.2

Lync 2013 Client configuration

Figure 24: Lync 2013 Client Simultaneously Ring

...........

32

Aastra 400 Configuration as IP PBX with One

Number

Here the Lync 2013 client of a user is one of his terminals.

This has several advantages for the user:

He can make use of the Aastra 400 user related features (e.g. Voicemail, BusyLampField and many
more.

He can set up profiles defining which terminals shall be called. These profiles are activated manually
or by the changing of the presence state (e.g. from Microsoft Outlook)

the full integration of the users mobile phone is possible. All phones of the user are reachable under
one internal and one external number.

Lync 2013
Server

Lync
client
74571
Other phone
of user 4571

User 4571
Lync
client
74567

User 4567

Other phone
of user 4567

DDI
numbers
326554500..
326554599

74500..74599
Lync 2013
Mediation
Server(s)

External / Public
User
User

Aastra 400 R3.1

Communication
Server

PSTN /
SIP

ISDN or
SIP trunk

The phones in the box are configured in the PBX to belong to the
same user. Both have the same number
Figure 25: Overview Aastra 400 operation as IP-PBX with 'One number'

...........

33

8.1
8.1.1

Aastra 400 configuration

Direct Dialling In (DDI numbers)

Each user should have a matching Direct Dialling In (DDI) number. This DDI number is then routed to the
Aastra 400 user.

8.1.2

Aastra 400 Licences

In addition to the licences mentioned in 4.2 Mobile phone extension licences are needed one for each
Lync 2013 client.
With the help of this licence, a full IP-PBX integration is possible for each Lync 2013 client.

8.1.3

AMC/GSM Terminal

An AMC/GSM terminal is used to integrate the Lync 2013 client into the Aastra 400 configuration.
Create an AMC/GSM terminal and enter the Lync 2013 client number and the route to the Lync 2013 trunk as
the external number
Assign this AMC/GSM terminal to the list of terminals of this user. The AMC/GSM terminal representing the
Lync 2013 client could be the only terminal of a user.
Note: For each AMC/GSM terminal, an additional licence is required.

Number translation
For this One number set-up it is necessary (see 3.3) to configure the Lync 2013 user with a special
number. The easiest way is to add a prefix (e.g. 7). For the AMC/GSM terminal, add the 4-digit extension in
Mobile call number.
To dial the number to Lync 2013 add the digit 7 in the route configuration (Send access code).
For the incoming call from Lync 2013 cut the 7 in the trunk group configuration.

Figure 26: Aastra 400 WebAdmin Configuration of a GSM terminal used to integrate a Lync client into
the Aastra 400
...........

34

8.1.4

Route configuration

Figure 27: Aastra 400 WebAdmin Configuration of the Route used to call the Lync 2013 clients. See
the chosen prefix that is added to each dialled number sent to Lync 2013.

...........

35

8.1.5

Trunk group configuration

Figure 28: Aastra 400 WebAdmin Configuration of the Lync 2013 Trunk group. Here the chosen prefix
is removed again for calls from Lync 2013 to Aastra 400

...........

36

8.2
8.2.1

Lync 2013 configuration

User configuration Lync 2013

Configure the Line URI for the Lync User as 5-digit number with a leading 7.

Figure 29: Lync 2013 User configuration

...........

37

8.2.2

Define a Dial Plan

Figure 30: Define Dial Plan

8.2.3

Define Voice Policy

See chapter 5.2.1.3

8.2.4

Define Trunk Configuration

See chapter 5.2.1.4

...........

38

Appendix

A.1

Create a certificate for Aastra 400 from the MS

Certification Authority

Open IIS Manager on Lync 2013 Server

Open Server Certificates

Figure 31: IIS Manager Server Certificates

Click on the right pane: Create Domain Certificate

Figure 32: IIS Manager Create Domain Certificate

...........

39

Create the certificate for the Aastra 400.

In the field Common name enter the FQDN of the Aastra 400.
Click Next

Figure 33: Create Certificate Step 1

...........

40

Use the same Certification Authority as for the Mediation Servers

Click Finish

Figure 34: Create Certificate Step 2

Open MMC Add Certificates Snap-in Computer account (local computer)

Figure 35: MMC Certificates Local Computer

...........

41

Export the newly created certificate

Figure 36: Export Certificate

Click Next

Figure 37: Certificate Export Wizard Step 1

...........

42

Mark Yes, export the private key

Figure 38: Certificate Export Wizard Step 2

...........

43

Mark the two boxes, see below.

Figure 39: Certificate Export Wizard Step 3

...........

44

Enter a password, but do not forget it.

Figure 40: Certificate Export Wizard Step 4

...........

45

Save the certificate in .pfx format

Figure 41: Certificate Export Wizard Save As

Check the settings and press Finish

Figure 42: Certificate Export Wizard Step 5

...........

46

A.2

Supported features with integrated Lync 2013 client

When the Lync 2013 client is integrated according the use case described in 3.3 (using the Mobile or External
Phone extension) then the following features are supported:
Make calls to Aastra 400 internal destinations

According to the Lync dial-plan setup

Make calls to external destinations

According to the Lync dial-plan setup

Calls to the Aastra 400 Emergency number

According to the Lync dial-plan setup

Calls to Abbreviated Dialling number of the PBX

According to the Lync dial-plan setup

Calls to the Aastra 400 Voicemail system

(AudioGuide)

According to the Lync dial-plan setup

Calls to a Door Intercom system

According to the Lync dial-plan setup and if the Door

Intercom is connected as a normal internal terminal
to the Aastra 400.

Exchange access

Normally the Global/Business exchange access is

used, but if the Lync dial-plan is setup accordingly the
Route-selection, the Cost-centre-selection or the
Private exchange access is possible to use.

Call charges
Reject inbound calls
Display callers number (CLIP / COLP)
Display callers name (CNIP / CONP)
Suppress the call number display (CLIR)

If Lync suppresses the calling number then the

Aastra 400 cant assign the call to a certain user and
then many features wont work as expected.

DTMF dialling
Call forwarding unconditional
all call forwarding types are possible with the
Self-Service-Portal (Web configuration of the
user settings)
Busy Lamp field

Locally on Lync
These are done on the Aastra 400.

1)

System terminals can see the state of the user, when

1)
he is using the Lync 2013 client.

Put the current connection on hold

Retrieve a held connection
Music on Hold

Lync plays its own Music on Hold

Start an inquiry call

In the Aastra 400 these are two independent calls.

Brokering between an active and a held call

This is done by Lync

Call transfer (Blind or with announcement)

Conference

Done on Lync

Conversation recording

Only the automatic mode is supported.

List of callers

Lync 2013 clients own list

Phone Lock

PCs Screen Saver prevent access to the Lync 2013

client

1)

1)

Direct calls from one Lync client to an other are not supported.

...........

47

---------------------------------------------------------------------------------------------------------------------- 2014 Aastra Technologies Limited. All rights reserved.

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.
Aastra Technologies Limited
Concord, Ontario, Canada

...........

48