The WHYs behind the HOWs of Lync Enterprise Voice How to best
structure your Enterprise Voice deployment Dial plans Voice
Policies Routes etc Assume you already have a good understanding of
Lync Enterprise Voice core concepts Demo of the Lync Dialing Rule
Optimizer
Slide 5
Slide 6
Defines the format for telephone numbers in SIP Internationally
recognized telephone number format Tel URI Global number in E.164
format Extension (optional) Country Code Area Code Local
number
Slide 7
Get to know regex basics: http://hanytaha.wordpress.com/
2012/01/15/regular-expression- regex-and-lync-2010/ Test your
regex: http://www.regextester.com/ ^ start of pattern (or not) $
end of pattern \dsingle digit \d{3}3 digits \d{1,5}1 to 5 digits
\d+1 or more digits \d*0 or more digits \Dnon-digit135 [135]1, 3 or
5 [^135]Not 1, 3 or 5 [1-5]1 to 5 ?not required \+plus sign |or
(123)Store 123 $1Return 123
Not necessary to change every phone number in AD Use the
Company_Phone_Number_Nor malization_Rules.txt Found in
\\LyncFileShare\x- WebServices-x\ABFiles Lync Address book process
parses AD-based numbers using this file Check by using ABServer.exe
-TestPhoneNorm Examples: ([2-9]\d{9})\D+(\d+) +1$1;ext=$2
([2-9]\d{9}) +1$1
Every call can be sent to an all encompassing route (think *.*)
Easier to manage and troubleshoot, especially in large deployments
CON Cant leverage several Lync features No least cost routing Cant
limit calling or call forwarding for users
Slide 19
Very granular routing/call control possibilities Least-cost
routing CON Its.ummmits complicated Many routes/PSTN usages Can be
difficult to troubleshoot
Slide 20
Slide 21
Slide 22
Slide 23
Normalize to E.164, using the main office number for the
location as the base: +12125551234;ext=2345 Strip back down to 2345
as the call leaves Lync Most normalization rules are the same
countrywide, so consider that in your naming convention
UK-London-Local UK-National UK-International Doing so will mean not
normalizing to E.164 Use the External Access Prefix option
instead
Use site-level policies by default Automatically assigned to
all users homed on Lync servers within a site Assign the most
typical call classes to capture the most users (ie. Local and
National PSTN Usages) Example: Assign a site- level National voice
policy for users who dont require international dialing Use
user-level policies for exceptions Manually assigned via Lync
Control Panel or Powershell Assign additional or remove call
classes for smaller groups of users (ie. International PSTN Usage)
Example: Assign a user-level International policy to executives and
others that require international dialing
Normalize dialed extensions to E.164 2345 +14165551111;ext=2345
^(2\d{3})$ 14165551111;ext=$1 Assign a route to the appropriate PBX
^\+14165551111 PBX_Gateway Add a trunk translation rule to strip
back down to extension +14165551111;ext=2345 2345
^\+14165551111;ext=(2\d{3})$ $1 or ^\+\d+\D+(\d+)$ $1
Slide 47
Easier to deal with routing and trunk translation when
everything follows same standard Extremely important when migrating
away from PBX to Lync Scenario: Normalization/routing rules created
specifically for PBX extensions 2xxx normalized to 2xxx (not E.164)
Lync migrated users configured with E.164 Tel URIs
tel:+12125551111;ext=2xxx Original extension scheme maintained How
to dial Lync user by extension? Normalization becomes a nightmare
Need to create user-specific normalization rules for every migrated
user
Slide 48
Use a normalization rule to map the main number to an extension
(E.164 format, of course) When creating auto- attendant or response
group extensions, make sure to follow E.164 standards
Slide 49
Slide 50
Slide 51
Slide 52
Slide 53
Applies to all location-based routing enabled users at the site
Check out Doug Lawtys deep-dive session on Location- based Routing
(VOICE303)
Slide 54
Slide 55
Dialing rules for 67 countries Location- based routing Custom
localized dialing rules for all of North America Least-
cost/failover routing ExtensionsPremium number blocking Call Park
Simple or complex dial rules Use your own naming convention
Slide 56
Slide 57
E.164 Understand the interplay between voice policies, routes,
PSTN usages and trunk translation rules Read Technet, blogs,
everything Or just use the Lync Dialing Rule Optimizer
