Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer

Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer - welcome to our blog Techno Live, now we will discuss information about the Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer, our admins on this blog has been around to collect information you are looking for so that we usakan to display complete information for you, and in this blog, you can also search for other information, ok please continue reading may be easily understood:

This is about : Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer
And this article : Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer

You can also see our article on:


    Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer

    The Lync Dialing Rule Optimizer tries to take care of all the Enterprise Voice configuration necessary for all deployments.  On most fronts, it does a pretty good job (IMHO).  One area that has been lacking is the ability to automatically arrange PSTN usages to provide least-cost/failover routing for multi-site Lync deployments. Once an administrator has run the Optimizer for all their sites, they have to manually configure the voice policies to provide least-cost/failover routing.

    If you're not familiar with how least-cost/failover routing works in Lync, please refer to http://liveeconcerts.blogspot.com /2011/01/enterprise-voice-best-practices-in-lync_21.html" target="_blank">my post on the subject in my http://liveeconcerts.blogspot.com /search/label/EV%20Best%20Practices" target="_blank">Lync Enterprise Voice Best Practices series.

    With version 9.0 of the Lync Dialing Rule Optimizer, Lync administrators now have the option to create least-cost/failover routing between all sites that have been deployed using the Optimizer (or at least follows the same naming conventions used by the Optimizer).

    When the Optimizer-generated script detects multiple Lync sites, it will prompt the user if they want to apply least-cost/failover routing to the voice policy being generated.  If the user allows it, the Optimizer will add PSTN usages for all the other sites to the new voice policies.  This assumes the existing PSTN usages are named with the country abbreviation first, and ends with either Local, National, International etc in any of the languages currently supported by the Optimizer as in the following examples:  UK-Leeds-113-Local, IT-Rome-06-Nazionali.

    The output can be best summarized by way of example.  Assume a company has Lync Enterprise Voice deployed in the following locations:
    Toronto, Canada
    Vancouver, Canada
    London, UK
    Rome, Italy
    Belém, Brazil

    After running the Optimizer script against all sites, the PSTN usages for the Toronto International user voice policy would look like this (you might want to sit down for this):
    NA-ON-Toronto-416567-Local
    NA-BC-Vancouver-604678-Local
    NA-ON-Toronto-416567-National
    NA-BC-Vancouver-604678-National
    NA-ON-Toronto-416567-Premium
    NA-BC-Vancouver-604678-Premium
    NA-ON-Toronto-416567-Service
    UK-London-20-Local
    IT-Roma-06-Locali
    BR-Belém-91-Local
    UK-London-20-Mobile
    IT-Roma-06-Cellulari
    BR-Belém-91-Celular
    UK-London-20-National
    IT-Roma-06-Nazionali
    BR-Belém-91-Nacional
    NA-ON-Toronto-416567-International
    NA-BC-Vancouver-604678-International
    UK-London-20-International
    IT-Roma-06-Internazionali
    BR-Belém-91-Internacional


    The Optimizer will group PSTN usages from the same country near the top, using the assumption that most of the calls will be made to in-country locations and that the fewer PSTN usages the system needs to evaluate for each call, the better.

    The ordering is such that least-cost routing and failover routing will occur.  PSTN usages from other countries will be placed lower in the list while still providing least-cost and failover routing for all calls.  If there are multiple Lync sites out-of-country, the ordering of PSTN usages within the National and International usages will be somewhat random. Administrators should review the PSTN ordering to make sure it suits their needs.

    It is assumed that premium numbers can only be dialed from in-country locations, so out-of-country premium PSTN usages are not assigned. Also, only the local service PSTN usage is assigned for similar reasons.

    All calls will use the least-cost route where possible. If a route assigned to a specific usage is unavailable, calls will use a route in another site, again keeping the call in-country if possible.

    With the inclusion of least-cost/failover routing in the Lync Optimizer, administrators now have a tool that can completely build the Enterprise Voice environment for even the largest enterprise-level Lync deployment.

    As always, feedback is greatly appreciated. Let me know if you come across any issues with functionality or scalability as I haven't tested if there is a limit to the number of PSTN usages that can be assigned to a voice policy.




    Articles Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer finished we discussed

    A few of our information about the Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer, I hope you can exploit carefully

    No've You've finished reading an article on Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer and many articles about modern home in our blog this, please read it. and url link of this article is https://liveeconcerts.blogspot.com/2013/01/least-costfailover-routing-in-lync.html Hopefully discussion articles on provide more knowledge about the world of tech gadgets.

    Tag :

    Related Posts :

    0 Response to "Least-Cost/Failover Routing in the Lync Dialing Rule Optimizer"

    Post a Comment