Configure Lync 2010 voice using a SIP gateway and an uncertified SIP trunk, step-by-step – Part 2

This post takes on right where post 1 in this series ended and we will jump right into it. We will cover PSTN Gateway configuration, Trunk configuration, Normalization rules and Voice Routes.

PSTN Gateway

Head over to you Lync Server 2010 and open up Lync Server Topology Builder, then choose Download Topology existing deployment and click Ok.

ix7825

Choose a location and enter a name for you topology file and then click Save.

ix7826

Expand Mediation pools and then click Edit Properties… in the Actions pane.

ix7827

Select New to create a PSTN gateway.

ix7828

Enter the FQDN or IP address for your gateway, ensure TCP is set as we configured TCP in the Intertex IX78 in the previous post and change the default port to 5060. When finished click Ok.

ix7829

Make sure that the gateway is listed in the The following gateways are associated with this mediation server and  then click Ok.

ix7830

Go ahead and publish your new topology. I will not cover the publishing in this post, instead we will continue with configuring our trunk.

Trunk Configuration

Open the Lync Server control Panel and navigate to Voice, Trunk Configuration and click New.

ix7831

Make sure your settings match mine and then create a translation rule by clicking New.

ix7832

I will create a Translation Rule that looks for the +00 prefix, and makes sure that the number is more then 3 digits long, then it replaces 0 digits (in other words it does not replace anything). We will use Normalization Rules to make sure that the dialed numbers have an ok syntax. When finished click Ok to save our Translation Rule.

ix7834

Take a quick look at the configured settings and then click Ok to save your Trunk configuration.

ix7835

 

Normalization Rules

Normalization rules define how phone numbers expressed in various formats are to be routed for the named location. It is a way of forming an E. 164 number from the number dialed by an Lync Server 2010 user. It is necessary for call routing because users may dial numbers in various formats.

I will list all my 5 Normalization Rules, you might not need all of them but this is what works for me in my lab in Sweden. Feel free to add a comment if you need help with forming these rules, it can be quite tricky. More information regarding Normalization Rules can be found here and here.

Navigate to Voice Routing and Dial Plans and open your Global Dial Plan.

ix7836

In my example you can see the 5 Normalization Rules that I use for my lab environment. Create a new rule by clicking New.

ix7837

This rule initiates on the starting digits 00, it does simply that and nothing more. The reason for this is that I want to normalize all numbers to include both country code and area code, for example 0046855566677. I would recommend you to try different Normalization Rules until you have a combination of rules that fits your needs and demands.

ix7838

To make sure that your rule works you can test it before clicking Ok and saving it. If I enter a number that I believe should match the rule and then click Go it should display the normalized number in green.

ix7839

My next Normalization Rule initiates if a number starts with a single 0 and is at least 1 digit long. In Sweden our area codes starts with a single 0. Then it adds the prefix 0046 to make it a standard Swedish number including the country code.

ix7840

When I enter a number with Stockholm’s area code it should Normalize it to a number that that removes the initiating 0 and then adds the prefix for the Swedish country code.

ix7841

My next Normalization Rule initiates on any number starting with one of the numbers 1 to 8. A local number in Sweden can start with any of those numbers. It must also be at least 5 numbers long since no telephone number in Sweden has less then 5 numbers. Then it adds the local area code of both Sweden and Stockholm.

ix7842

And when I test this rule with a local number it should add a prefix of 00468.

Note: This Normalization Rule assumes that this server is placed in Stockholm and that all numbers missing an area code is meant for Stockholm.

ix7843

This next rule initiates based on the staring digit +, as in +46855566677. It then removes the + and adds 00.

ix7844

And when tested it does exactly that…

ix7845

And last but not least, this rule initiates when the number starts with 33 and is exactly 3 digits long. This indicates that it is a local number and it should not be normalized in any way.

ix7846

When tested it does seem to match, note that I have also checked Internal Extension.

ix7847

When you have added all your Normalizations Rules you can make more tests if you want and then click Ok to save your Dial Plan.

ix7848

I am by far no expert in normalization rules, if you have any thought on the rules I use please feel free to post a comment or contact me and I will be happy to optimize my lab.

Route Configuration

Our final step towards a working Lync Server 2010 voice implementation is to configure routing. A Voice Route looks for a specific pattern in numbers and then decides which gateway that it will route the call to. Navigate to Voice Routing and then Route. Click New to create a new route.

ix7849

Give the Voice Route a Name and then add the pattern that you want this route to match. In my case I have normalized everything that is supposed to leave the Lync Server with 00 I add 00. In your case this might differ depending on your Normalization Rules.

ix7850

The next step is to add an Associated gateway. Click on Add to open the gateway selection.

ix7851

Search for and select the gateway you would like to add and then click Ok to save your selection.

ix7855

Next we must add an Associated PSTN usages, click Select to open the PSTN usage record selection.

ix7856

Select your PSTN record and then click Ok.

ix7857

Now it is time to test our routing. Enter a suitable number that you think should match the pattern and click Go.

ix7854

Also, to make sure that all is well, enter a number that should not match the pattern.

ix7853

When finished save the Voice Route by clicking Ok.

Now make sure that you Commit all changes properly!!

After this you should be all set and ready for testing. This concludes part 2 of this series, I hope you have enjoyed reading it and that you find it useful. If you have any thoughts or questions regarding the configuration please do not hesitate to post a comment.

Part 1 in this series can be found here!

Part 2 in this series can be found here!

Advertisements

10 Responses to Configure Lync 2010 voice using a SIP gateway and an uncertified SIP trunk, step-by-step – Part 2

  1. Pingback: Configure Lync 2010 voice using a SIP gateway and an uncertified SIP trunk, step-by-step – Part 1 « Martin's Wonderful World of Unified Communications

  2. Mkt bra artikel.

  3. Tommy says:

    Japp mycket bra Martin.

  4. Ry says:

    At last something you can read and actually learn from!
    Awesome work!

    • Martin Sundström says:

      Thank you so much for the feedback, I´m glad that you find it helpfull. Thanks for reading!

  5. Praakassh Ghaitadke says:

    Hey Hi, Is that possible to add 2 PSTN Gateways on same port 5060?

  6. Tjena

    Jag sitter och testar av med Lync 2013 och Windows Server 2012. Jag har ett problem då jag kan ringa till mina klienter i Lync men kan ej ringa ut till de nummer som jag ringt in med.
    Har du några idéer var felet kan ligga ?

  7. Jim says:

    saya sudah melakukan tips poin 2 dan 3 untuk point 1 menyusul , Aerona

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: