* Please note this is a new service and not a standard setup. Please contact Nehos Sales on 1300 726 889 or email email@example.com for further information.
Microsoft Lync requires a static public IP address to be able to use Nehos.
You will need to provide us with your public IP address and port number that your Lync server is using to communicate with us.
To enable inbound calls to use Microsoft Lync you will need to inform us what DID number/s will be terminating on your equipment from Nehos along with the IP address and port of your equipment.
We do not support TLS only TCP with Lync so this needs to be set at TCP only.
The default SIP domain needs to be sip.nehos.com.au
NEHOS LYNC 2013 CONFIG GUIDE
* This document presumes a basic working knowledge of Lync 2013
Our Lab environment
- Working Lync Server (this document is based on Single Lync 2013 with Edge server)
- Firewall rules enabled as per Microsoft recommendations shown below
Configure Lync Topology with Nehos connection
Open Lync server 2013 Topology Builder and select New IP/PSTN Gateway shown below
The PSTN gateway is sip.nehos.com.au
You can accept the default for the IP address
The port settings should match you setup noting that the protocol MUST be TCP and Nehos use 5060 as there default port
Click finish to complete and confirm you should now see the following configuration in Topology Builder
The last step is to Publish the new topology
Configure Lync Server
Open the Lync Server 2013 Control Panel
Select Voice Routing
Create a New User Dial plan
Name the Dial plan appropriately
Normalisation rules are extremely important, they provide a standard way of defining all calls and making the dial sequences consistent.
By default the dial plan will have a “Keep all” normalisation rule, you can leave this in place however it is suggested that you amend this to match PSTN numbers or numbers with at least 6 digits if you are using Nehos extensions as internal users otherwise 7 digits if the recommended setting.
Add normalised rules so that all calls are rewritten into E.164 format, suggested names shown, click New to add the additional rules.
|Name||Starting digits||Length||Remove||Digits to Add|
|Local code||[2-9]||=8||0||+61 < Your local area|
When you are finished the setup should look like the above, click OK to continue
Commit all changes
Next Select Trunk Configuration and create a new Site Trunk
Your PSTN Gateway created in the Topology should appear in the list, select and click ok
The settings here are specific to Nehos, The encryption should be set to “Not supported” and Refer Support set to none, Nehos does not currently provide TLS support.
Scroll down to translation rules and add a rule for E.164 calls as follows
Click ok to close to save translation rules and ok to close Site trunk, then commit all changes
You will be prompted to confirm changes as follows
Select the Route tab to configure routing options for calls, create New Route
Since we normalised all calls with a + and E.164 format we need to add + in the pattern to match and then select add to associate with Nehos PSTN trunk configured earlier.
Click ok to close and commit all changes
Now you need to select the Voice policy and create new Voice Policy for users
Check all the options you wish to make available and then
Select New to associate PSTN usage options
Click Select and choose the Nehos Voice Route created earlier
Click OK and then commit all changes and confirm
The last step in Voice Routing is to test the configuration, if at this point you get any failures one of the steps above is either incorrect or incomplete, you should review before continuing.
Select Test Voice routing and create a New Test case.
You can create many test cases however at a minimum the following should work, this is a test to confirm you can call Nehos, on selecting Run you should get results as per below.
Finally we need to setup users to be able to make calls, in order to achieve this a user needs to have “Enterprise Voice” enabled and have a telephone number, these are entered as
If you have completed all the steps above you are ready to test, please ensure you have provided Nehos with your Public IP address and have the relevant firewall rules in place, if so provide these details to Nehos.