tag:blogger.com,1999:blog-2156539095375223979.post7289427367563425265..comments2024-03-20T03:35:01.157-04:00Comments on Ken's Unified Communications Blog: Complete Guide to the Lync OptimizerKen Laskohttp://www.blogger.com/profile/14298995806059683301noreply@blogger.comBlogger168125tag:blogger.com,1999:blog-2156539095375223979.post-52604383338717590712021-09-21T10:39:57.961-04:002021-09-21T10:39:57.961-04:00The site has supported Teams for a number of years...The site has supported Teams for a number of years now. Ken Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-58295304901346308792021-09-21T09:54:11.855-04:002021-09-21T09:54:11.855-04:00This is a good tool but do you plan to update for ...This is a good tool but do you plan to update for Teams cmdlt?<br />Since SfB cmdlt is going away.Sunilhttps://www.blogger.com/profile/00018860132548994273noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-30842440894377535152019-06-14T11:36:36.359-04:002019-06-14T11:36:36.359-04:00They are supposed to represent every service numbe...They are supposed to represent every service number in the UK. It was provided to me by a telephony guy from the UK years ago.Ken Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-59105686153267292022019-06-14T06:30:33.661-04:002019-06-14T06:30:33.661-04:00Great article and tool, The only thing I don't...Great article and tool, The only thing I don't understand is the UK-Non-Geographic-Service usage, what numbers are they for? Mike Listerhttps://www.blogger.com/profile/11377444324710584343noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-76993271004688750852014-05-26T02:48:13.541-04:002014-05-26T02:48:13.541-04:00Ken,
Never mind. I just figured it out. I needed...Ken,<br />Never mind. I just figured it out. I needed to manually edit the rule vs. let the rule be built for me. I used ^\+\d{11};ext=(\d{4})$ . <br />Your tool is fantastic.<br />Thanks again,<br />LukeAnonymoushttps://www.blogger.com/profile/08672530435223905239noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-47808683416948811932014-05-26T02:27:25.247-04:002014-05-26T02:27:25.247-04:00Thanks Ken,
I took your advice and everything is w...Thanks Ken,<br />I took your advice and everything is working great. I only have one issue at this time.<br /><br />I have a range of internal extensions 4100-4700. I added them to the list of internal extensions as +13235497155;ext=4XXX. the generated rule works perfectly, dial 4xxx and it transforms to e.164. <br /><br />But most of these extensions are still over on my CallManger. So I have updated the route and changed to the internal trunk to my CallManager. Now I am trying to get my Called Number Translation Rule on the Trunk to strip the +13235497155;ext= and just send the last 4 digits and I can't seem to get it to work.<br /><br />When I add the ; to the starting digits in the rule I get an unexpected character warning. Any idea what I am doing wrong? <br /><br />In short I am trying to strip everything but the last 4 digits when I send it over the internal trunk to my callmanager.<br /><br />Thanks,<br />LukeAnonymoushttps://www.blogger.com/profile/08672530435223905239noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-4078945276648287792014-05-23T15:51:14.080-04:002014-05-23T15:51:14.080-04:004th Lync installation I've done using this (2 ...4th Lync installation I've done using this (2 2010s and 2 2013s) and it's worked flawlessly every time. UCKen FTW!OldGreyBeasthttps://www.blogger.com/profile/18082754201358343208noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-24418838119028207452014-05-20T21:00:42.020-04:002014-05-20T21:00:42.020-04:00The easiest way to go about this is to create a ru...The easiest way to go about this is to create a ruleset for both LA and SF, including the extensions bound for Call Manager. Run the resulting scripts twice each (LA, SF, LA, SF), making sure to say "Yes" to the prompt for doing least cost routing. <br /><br />Then modify the route for the internal extensions to point to the relevant Call Manager at each site, and copy the trunk translation rule that strips the E.164 number down to the extensions to the CM trunk (you may need to create the trunk config in Lync Control Panel first).<br /><br />Then copy the internal extension normalization rules between each of the dial plans, so everyone can dial extensions for each site and it will route correctly.<br /><br />That should be pretty much all you need to do to get it going. That will give you least cost/failover routing to both SF and LA, and also ensures that called extensions will go to the right place.<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-53771824104173489632014-05-20T19:21:06.111-04:002014-05-20T19:21:06.111-04:00Hi Ken,
I saw your video from the Lync Conference ...Hi Ken,<br />I saw your video from the Lync Conference and learned that I was not setup correctly for failover simply by including trunks for different sites to my routes, round robin not top down. Thanks for that.<br /><br />I want to see what your guidance would be for our scenario. <br /><br />We have two sites, LA and San Francisco. Each site has an AudioCodes Gateway for PSTN access and a second Trunk to our Cisco CallManager node at that site for internal extensions.<br /><br />So<br />LA AudioCodes for PSTN<br />LA CM for internal extensions<br />SF AudioCodes for PSTN<br />SF CM for Internal extensions<br /><br />How should I use your tool to support the two different gateways at each site and still be able to benefit from failover between the sites. I need internal extensions that are not assigned to Lync Users to route over the internal trunks to CallManager and calls bound for the PSTN to go out via the AudioCodes Gateways.<br /><br />And then ideally have the benefit of failover between the site trunks for the two routes Internal and PSTN.<br /><br />Hopefully that makes sense.<br />Thanks<br />LukeAnonymoushttps://www.blogger.com/profile/08672530435223905239noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-61776893448796626042014-05-20T10:32:28.623-04:002014-05-20T10:32:28.623-04:00Thank you for alerting me to this. You'll see ...Thank you for alerting me to this. You'll see a fix in the next few days.<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-54079993704155078772014-05-19T14:48:30.142-04:002014-05-19T14:48:30.142-04:00I was trying to create some rules and added option...I was trying to create some rules and added option for 7 digit dialing for area code 206 with prefix 438.<br />The 7 digit normalization rule for 206 area code does not work. The rule ends with an extra close parenthesis and when testing by entering 7 digits it does not normalize at all - gives an error. It looks like that rule is trying to generate a rule set to exclude any number that begins with any of the 3 digit area codes and then if that passes take the 7 entered digits and add +1206 as the last part of the rule is (\d{7}) which would be any 7 digits. <br />It looks very different from the 425 local 7 digit rule which looks for match on existing 3 digit prefixes in that area code + any 4 digits.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-22728143675402215712014-05-13T12:22:36.162-04:002014-05-13T12:22:36.162-04:00Hey Ken,
it will be nice to have Nigeria in this...Hey Ken, <br /><br />it will be nice to have Nigeria in this tool. Can you consider that pls.<br /><br />TheoTheo Tingirnoreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-57214818043700799172014-02-14T13:00:31.051-05:002014-02-14T13:00:31.051-05:00OK, I get what you're doing. Sadly, there'...OK, I get what you're doing. Sadly, there's no support in the Optimizer for that scenario, but you can enable it, and hopefully not make a mess by going to line 163 where it says: <br />If (((Get-CsDialPlan $CSSite.Identity | Where-Object {$_.NormalizationRules -like '*NA-*'}) -eq $NULL) -and ((Get-CsDialPlan $CSSite.Identity) -ne $NULL))<br /><br />and modify that line to look like:<br /><br />If ( (Get-CsDialPlan $CSSite.Identity) -ne $NULL) <br /><br />It should let you create a user-level dial plan the way you want. Let me know how it works out, and I may make that change permanently, after I consider why I put it there in the first place.<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-60800818075082833812014-02-14T12:35:19.910-05:002014-02-14T12:35:19.910-05:00We have a centralized SIP trunk for several DID ra...We have a centralized SIP trunk for several DID ranges by city. The effective purpose would be to accommodate the behavior of 7 digit dialing for all users in each of their city. Yes all the calls break out of one location but I'd like for the user, not matter which DID range, be able to dial 7 digits. I'm assuming I'll create dial plans for each city and have a unique 7 digital normalization rule for that locale. Does that make sense or a good workaround?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-18910561732992771232014-02-13T17:01:30.577-05:002014-02-13T17:01:30.577-05:00And its done. Only took 3 months to do. Check it...And its done. Only took 3 months to do. Check it out and let me know what you think.<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-70005879194795001482014-02-13T17:00:41.020-05:002014-02-13T17:00:41.020-05:00What do you need multiple dial plans for? Won'...What do you need multiple dial plans for? Won't the dialing behaviour be the same for each of them? Or are you looking to add extension dialing that's specific to each site and can't be shared for whatever reason? Or am I missing something...it's always possible, I'm not as smart as my picture would imply.<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-67766051151029992132014-02-13T16:53:41.784-05:002014-02-13T16:53:41.784-05:00Single Lync Site, Singe Mediation Pool (3 servers)...Single Lync Site, Singe Mediation Pool (3 servers), Single Trunk, Single Gateway, Single SIP Trunk (breakout). I ran it once. I want to run a second set of rules for a different Area Code. So in the end I can have a Seattle dialplan, San Francisco dialplan, New York dialplan, etc. all in a single Lync site. I think you second paragraph answers it though. I guess my option is to manually create what I need correct? Any recommendations on that?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-48703051095298870632014-02-12T19:53:40.545-05:002014-02-12T19:53:40.545-05:00So, what exactly are you trying to accomplish? Wha...So, what exactly are you trying to accomplish? What's your topology look like? How many Lync servers/sites/PSTN trunks/gateways do you have and where are they pointing? If you only have one Lync server with one PSTN gateway, then the Optimizer will do a full run the first time. If you download a second set of rules for a different country, then it will create a user-level dialplan to give remote users localized dialing rules, even though their calls are routing via a different country. <br /><br />The Optimizer is not designed to handle a scenario where you run two different rulesets from the same country against a single Lync server/site/GW combination.<br /><br />If you describe what you're trying to do, maybe I can help you better.<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-55135243308306274982014-02-12T18:55:56.800-05:002014-02-12T18:55:56.800-05:00Hi Ken,
I'm experiencing DUlrich1227's sam...Hi Ken,<br />I'm experiencing DUlrich1227's same issue. I ran the Optimizer to create my original dial plan, voice policy, etc. It created it as a site scope dial plan since there wasn't any existing ones. I reran the Optimizer with a new NPA, etc. and ran the PS1 file hoping that I would just create another User scope dial plan. So the intention here is multiple area codes in one central site. Any ideas?<br /><br />Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-58209461347468749332014-01-10T08:22:13.263-05:002014-01-10T08:22:13.263-05:00Thanks Garry,
I've updated the rule so it will...Thanks Garry,<br />I've updated the rule so it will accept just a single 0 in front of the number and will strip it on normalization. Thanks for the heads up!<br /><br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-51999693885047459822014-01-10T06:40:26.265-05:002014-01-10T06:40:26.265-05:00Hi Ken,
I wanted to thank you for the DRO - it is...Hi Ken,<br /><br />I wanted to thank you for the DRO - it is a fantastic piece of work. I used it recently for a company with multiple small offices around Europe. I only hit one bug related to the normalisation rule created for German toll free numbers: the script creates a matching regex entry of ^(((0|00)800\d{7}))$ but this retains the leading 0 or 00 in the output. I modified it to ^(0|00)((800\d{7}))$ and the translation rule to +49$2 to omit the leading 0 or 00.<br /><br />Cheers,<br />GarryGarry Williamshttp://unifiedme.co.uk/guestauthor/noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-71442007667691073482013-12-05T19:57:26.034-05:002013-12-05T19:57:26.034-05:00To answer your questions:
1. I use Wikipedia to fi...To answer your questions:<br />1. I use Wikipedia to find out details of other countries, as well as references from the ITU (http://www.itu.int/oth/T0202.aspx?parent=T0202). The Optimizer has 34 countries, with more added all the time, so if you ask nicely, I may move some up the queue<br /><br />2. I'm starting to add non-geographic area codes to the Optimizer, starting with the UK for 3 and 5. You'll see them at the very bottom of the area code list. Others will follow (again, let me know what countries you need).<br /><br />Hope this helps.<br />KenKen Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-3131642939338542072013-12-05T11:54:27.322-05:002013-12-05T11:54:27.322-05:00Hi Ken,
Your site has been very helpful. I have a...Hi Ken, <br />Your site has been very helpful. I have a couple questions. About dialing rules and the optimizer. We are a company based in the US, though we have conference calls with several different countries. In an effort to reduce cost to these other companies we have purchased local numbers in the different countries. <br /><br />1. Is there a reference that I could use to setup the dialing plan/normalization rule for the different countries<br />2. Some of the international numbers that we have - like the UK is a national number and foes not have an area code that matches up on your optimizer. What can I do in this case?Anonymoushttps://www.blogger.com/profile/17737083714787815612noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-87060055884207839752013-11-25T21:32:38.367-05:002013-11-25T21:32:38.367-05:00Been looking into it. Have always thought it was t...Been looking into it. Have always thought it was too hard, but may be able to work something out.Ken Laskohttps://www.blogger.com/profile/14298995806059683301noreply@blogger.comtag:blogger.com,1999:blog-2156539095375223979.post-33972521440692402242013-11-25T20:52:06.351-05:002013-11-25T20:52:06.351-05:00Hi Ken, how about adding NZ?Hi Ken, how about adding NZ?Hamishnoreply@blogger.com