Installation Guide: Microsoft Lync with MyNetFone SIP Trunking · Installation Guide: Microsoft...

My Net Fone Australia Pty Ltd, ABN 73 109 671 285, Address Level 2, 10-14 Waterloo St, Surry Hills NSW 2010

Commercial in Confidence

Installation Guide:

Microsoft Lync with

MyNetFone SIP Trunking

Note:

This document only provides the settings required to make and receive calls via the MyNetFone SIP

Trunk service. The document is not a tutorial on setting up and/or troubleshooting Microsoft Lync

Server. It is assumed that the installer has a thorough understanding of setting up and

troubleshooting Microsoft Lync server and Communicator client.

The Microsoft Lync server configuration is quite complex with many different settings required, and

therefore even if the instructions in this guide are followed exactly, calls may still fail or the

configuration may fail to apply due to a problem elsewhere. It is assumed that the installer will

carry out any required troubleshooting to resolve any such issue.


Commercial in Confidence of 62

Table of Contents System Requirements ............................................................................................................................. 3

Configuring MyNetFone SIP proxy as a PSTN gateway in the Lync Server Topology Builder ................. 4

Applying Topology changes using the Lync Server Deployment Wizard ................................................ 9

Configuring Call Routing details in the Lync Server Control Panel ....................................................... 21

Setting up Office Communicator Client logins for Users ...................................................................... 57



System Requirements

1. Microsoft Lync server must already be installed and configured, other than for settings

required to connect to the MyNetFone SIP Trunk service.

2. The configuration changes required to connect to the MyNetFone SIP Trunk service must be

done from an account in the Domain Administrator group.

3. There are no other PSTN gateways/providers configured - all outbound calls will go via

MyNetFone SIP proxy only.

4. The Lync front-end and meditation servers are co-hosted.

5. The Lync front-end/meditation server host has a public IP address, or if a private IP address

is used then there is a NAT Firewall with a SIP ALG that can change all private IPs in the SIP

messages to the MyNetFone SIP proxy into a valid public IP.

6. TCP port 5060 is used for SIP signalling.

7. Any firewalls have been configured to allow SIP messages and RTP to and from the

MyNetFone SIP Trunk service.

8. There is only a single site, will all users at that site have the same call routing settings.

9. A DNS server is available to resolve the MNF SIP Trunk service DNS name.

10. A Certificate Authority has been configured in the Active Directory domain.

11. NTP or some other mechanism is used to keep the clock on the front-end/mediatation

server in sync with a proper time source.

12. The user dial plans format dialled numbers to be in +E164 format, therefore no translations

are required on the SIP trunk section.

13. The users that require Lync Communicator client have already been configured in the Active

Directory.



Configuring MyNetFone SIP proxy as a PSTN gateway in the Lync

Server Topology Builder

Open the Lync Topology Builder and the choose “Download Topology from Existing Deployment”.

Click on “OK”, and then choose a file to save the config to.

Go to the “PSTN Gateways” section in the left pane.

Click on “New IP/PSTN Gateway” in top right corner.



The new gateway dialog box will be displayed.

In the “Gateway FQDN or IP Address” field - enter “sip30.mynetfone.com.au”.

In the “Listening port for IP/PSTN Gateway” field – enter 5060.

For “SIP Transport Protocol” – choose TCP.

Then click on “OK”.

The new gateway will be displayed under the “PSTN Gateways” section.



Next, the gateway must be linked with a Mediation Pool before calls can be made or received.

Go to “Mediation Pools” and click on “Edit Properties”.

Scroll down to the “Mediation Server PSTN Gateway” section. Verify that under “Listening Ports” the

TCP port is set to 5060, and that the “enable TCP Port” is selected.

Next, in the “following gateways are not associated with any mediation server” section, click on the

“sip30.mynetfone.com.au” gateway and click “Add”.



The MyNetFone SIP proxy should now be listed in the “the following gateways are associated this

mediation server” section.

Click on “OK”.



Next click on “Topology”, then “Publish in the top right corner”. The Publish Topology dialog box

should be displayed.

Click on “Next”.

Verify that all the Status indicators are showing “Success”, then click on “Finish”. If there are any

with errors, check the configuration and resolve any errors before continuing.

At this point the configuration changes have still not been activated; the changes must be activated

via the Lync Server Deployment Wizard.



Applying Topology changes using the Lync Server Deployment Wizard

Open the Lync Server Deployment Wizard. Click on “Install or Update Lync Server System”.

If “Install Local Configuration Store” is not ticked, click on “Run” next to it.



Click “Next”.

It may take a while for the “SqlExpressRtcLocal…Installing…” step to be completed.



Once Task Status shows ‘Completed’, click on “Finish”.

There should now be a green tick on the “Install Local Configuration store” option.

Next click on “Run” for “Setup or Remove Lync Server Components”.



Click on “Next”.

Click on “Finish”.



There should now be a green tick for the option “Setup or Remove Lync Server Components”.

If the “Request, Install or Assign Certificates” option doesn’t have a green tick next to it, click on

“Run”.

Click on “Request”.



If a Certificate Authority has been configured in the Active Directory it will be listed in the drop down

list “select a CA from the list detected in your environment”. If there are none listed, setup a

Certificate Authority and then come back to this step.

Choose a certificate authority and click “Next”.

Click “Next”, assuming that the install is running under a login in the Domain Administrator group.



Click “Next”.

Enter the name “Lync certificate” and the key length of 2048 bits. Click “Next”.



Enter the Organisation name, then click “Next”.

Enter the location details and click “Next”.



On the Subject Alternate Names dialog box click “Next”.

Tick the SIP domain(s) enabled, then click on “Next”.



Click “Next”.

Check the details in the summary and then click on “Next”.



Click “Next”.

Click on “Finish”.



Once Task Status shows ‘Completed’, click on “Finish”.

Verify that the certificate status is “Assigned”, and check that the expiry date is valid, then click on

“Close”.

Then close the Lync Server Deployment Wizard.



Configuring Call Routing details in the Lync Server Control Panel

Run the Lync Server Control Panel.

If you have not installed SilverLight already, you will see a prompt to do so now.

Otherwise the login prompt will appear.



Enter the Administrator password and click “OK”. Use a login that has administration rights to Lync

server settings.



Go to “Voice Routing”.

Choose “New”, then “User Dial Plan”.



Enter a name and description.

Double click on the normalisation rule “Prefix All”.



Change name to “E164” and update description.

Also update:

- Length: “at least 7”

- Digits to remove: “0”

- Digits to add: “+”



Add Dial Rule to convert 0NSN to +E164 format.



Add Dial Rule to convert 13xxxx numbers to +E164 format.



Add Dial Rule to convert 1300xxxxxx to +E164 format.



Add Dial Rule to convert 1800 to +E164 format.



Add Dial Rule to convert 0011* to +E164 format.



Add Dial Rule to convert 8-digits numbers without an area code to +E164 format. The example

below assumes that the Lync server is based in NSW and therefore that the area code is+612. For

other states it should be:

a) +613 for VIC and TAS

b) +617 for QLD

c) +618 for SA/WA



Add Dial Rule to convert 000 to +E164 format.



Add Dial Rule to pass through +E164 formatted numbers without changing.



The rules should be ordered such that the most specific matches are at the top, and the most

generic ones are at the bottom. This is because the Lync server does not do a ‘best match’, it starts

at the top of the list and stops at the 1st

match. Therefore the shorter prefixes should be at the

bottom, and the longer prefixes at the top.

Click “OK” once all required translation entries have been entered. At this point the new entries are

still in the “Uncommitted” state.



Click on the option “Commit” to activate the changes.

The “Commit” dialog box will pop up. Click on “Commit” to apply the changes.



The Commit Confirmation dialog box should appear once the changes are applied. Click “Close”.



Next click on “Trunk Configuration” in the top menu (the other options are Dial Plan, Voice Policy,

Route, PSTN Usage, Test Voice Routing).

Click on “New”, then “Pool Trunk” to setup the SIP Trunk to the MyNetFone SIP proxy.



The list of PSTN gateways that are configured in the “Lync Server Topology Builder” under the “PSTN

Gateways” section will be displayed.

Select the gateway for the MyNetFone SIP proxy and click “OK”.

If the instructions for setting up the MyNetFone SIP proxy in the Lync Server Topology Builder

section were followed, then the MyNetFone SIP proxy should show up under the name

“sip30.mynetfone.com.au”.



The trunk configuration page should be displayed for that PSTN gateway.

Change Encryption level to “Not Supported” (MyNetFone can provide IPSec VPN tunnels if

encryption is required).

Disable “Refer support”.

Disable “Centralised Media Processing” (since MyNetFone SIP proxy uses separate IPs for SIP and

RTP).



Add a translation rule to allow +E164 formatted numbers and click “OK”.

The user dial plans would have formatted the numbers to be in +E164 format already, therefore the

Trunk dial plan only has to allow +E164 numbers through. There is no need to do any further

translations.



Click “OK” once all settings have been entered. At this point the new entries are still in the

“Uncommitted” state.

The ‘Uncommitted Voice Configuration Settings’ dialog box will pop up. Click on “Commit” to

activate the changes.



The commit confirmation dialog box should appear once the changes are applied.

Click “Close”.



Next click on “Route” in the top menu (the other options are Dial Plan, Voice Policy, Route, PSTN

Usage, Test Voice Routing).

Click on “New”. The New Voice Route window should open.



For the Name and Description - enter “MyNetFone Calls”.

For “Build a Pattern to Match” enter only “+” and click “Add”. This is because the user dial plan

configured earlier would have converted external numbers to start with “+”.

Scroll down to the lower part of the page, where you will need to associate a PSTN gateway with this

Route.



In the “Associated Gateways” section click on “Add”.

The list of PSTN gateways that are configured in the “Lync Server Topology Builder” under the “PSTN

Gateways” section will be displayed. Select the gateway for the MyNetFone SIP proxy and click “OK”.

If the instructions for setting up the MyNetFone SIP proxy in the Lync Server Topology Builder

section were followed, then the MyNetFone SIP proxy should show up under the name

“sip30.mynetfone.com.au”.

Click “OK” to continue.



The MyNetFone SIP proxy should now be listed in the “Associated Gateways” section.

Click “OK”. At this point the new entries are still in the “Uncommitted” state.

The “Uncommitted Voice Configuration Settings” dialog box will pop up. Click on the option

“Commit” to activate the changes.



The commit confirmation dialog box should appear once the changes are applied.

Click “Close”.



Next click on “Voice Policy” in the top menu (the other options are Dial Plan, Route, PSTN Usage,

Test Voice Routing).

Click on “New”, then “User Policy” to create a new policy.



The “New Voice Policy” window will be displayed.

For the Name and Description – enter “HeadOfficeUsers”.

Click on “Calling Features” to show the expanded list of features. Verify that the following features

are enabled:

a) Call forward

b) Call delegation

c) Call transfer

d) Call park

e) Simultaneous ringing

f) Team call

g) PSTN reroute

Next click on “New” under “Associated PSTN Usages”.



The “New PSTN Usage” window will be displayed.

Enter a name for the PSTN usage.

Next, in the “Associated Routes” section, click on “Select”.

The list of Routes configured previously should be displayed. Among the list, there should be the

route for the MyNetFone SIP proxy that was configured earlier. It will be named “MyNetFone Calls”

if the instructions in this guide were followed. Select it and click on “OK” to continue.



The “MyNetFone Calls” route should now be displayed in the “Associated Routes” section.

Click “OK”.

“MyNetFone Calls” should now be displayed in the “Associated PSTN Usages” section.

Click “OK”.



At this point the new entries are still in the “Uncommitted” state. Click on the option “Commit” to


The “Uncommitted Voice Configuration Settings” dialog box will pop up. Click on “Commit” to apply

the changes.



The commit confirmation dialog box should appear once the changes are applied. Click “Close”.



Next click on “Test Voice Routing” in the top menu (the other options are Dial Plan, Route, PSTN

Usage).

Click on “New” and the new test case configuration window will open.

Enter a number to test the configuration. To test a 1300 number, enter the settings as shown in the

screen shot below, then click on “Run”.



If the configuration is valid, then the “Test Result” should show as “Passed”. Verify that the

“normalisation rule”, “normalised number”, “First PSTN usage” and “First Route” are as shown in the

screenshot above.

Click on “OK” to save the test case.

At this point the new entries are still in the “uncommitted” state. Click on the option “Commit” to




The “Uncommitted Voice Configuration Settings” dialog box will pop up. Click on “Commit” to apply

the changes.

The commit confirmation dialog box should appear once the changes are applied. Click “Close”.



Setting up Office Communicator Client logins for Users

Click on the “Users” option in the left pane. Then click on “New” to add in a new user.

Click on “Add” in the “Users” section.

The Active Directory search dialog box will be displayed.



Enter the name to search and click on “Find”. The list of users matching the search criteria will be

displayed.

In this example, the name “Test” is searched.

NOTE: the users would have to already exist in the active directory. It is not possible to activate Lync

server via the Lync control panel until the user has already been created in the Active Directory.

Select the required user and click on “OK”.



The chosen user should now be listed in the “Users” section.

In the “Assign users to a pool” select a Front-end pool that has been configured in the Lync Server

Topology Builder.

The “Generate user’s SIP URI” is configured next. Configure it to use the option

“<firstname>.<lastname>@domain”. The domain is the Windows Active Directory Domain.



Next set the “Telephony” option to “Enterprise Voice”.

Set the “Dial Plan Policy”, “Voice Policy” to the policies configured previously (i.e.

“HeadOfficeUsers”).



Set the “Line URI” to the DID assigned to this user. For example, to +61280047874.

NOTE: the DID must be in +E164 format.

Click on “Commit”.



The “Users” main page should now be displayed.

It should now be possible for the users listed in the Lync Control Users window to make and receive

calls via the Communicator client.

If you have any questions about the MyNetFone SIP Trunking setup with Microsoft Lync server,

please contact the MyNetFone Technical Support team on 1300 887 899 during business hours

(AEST).

For any other issues related to the Lync server, please contact Microsoft Support.

Installation Guide: Microsoft Lync with MyNetFone SIP Trunking · Installation Guide: Microsoft...

Documents

Transcript of Installation Guide: Microsoft Lync with MyNetFone SIP Trunking · Installation Guide: Microsoft...