Slide 1

Slide 2

Slide 3

Slide 4

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

Slide 8

Slide 9

GoodBad 1 (604) 555-1111(604) 555-1111 +1 (604) 555-1111 x234234 +44.20.7123.4567+44.020.7123.4567

Slide 10

Slide 11

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

Slide 12

Slide 13

Slide 14

UK-London-Local IT-Rome-International FR-Paris-Mobile US-NewYork-National US-WA-Seattle-TollFree ES-HeadOffice-AllCalls

Slide 15

Slide 16

Slide 17

Slide 18

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

Slide 24

Slide 25

6+16042226045045

Slide 26

9 +16045551234 6045551234

Slide 27

Rule NamePatternTransla tion NA-National^1?([2-9]\d\d[2-9]\d{6})(\D+\d+)?$+1$1 NA-Service^([2-9]11)$+$1 NA-International^(?:011)?([2-9]\d{6,14})(\D+\d+)?$+$1

Slide 28

Rule NamePatternTranslation UK-London-Local^([378]\d{7})$+4420$1 UK-TollFree^0((80(0\d{6,7}|8\d{7}|01111)|500\d{6}))$+44$1 UK-Premium^0((9[018]\d|87[123]|70\d)\d{7})$+44$1 UK-Mobile^0(7([1-57-9]\d{8}|624\d{6}))$+44$1 UK-National^0((1[1-9]\d{7,8}|2[03489]\d{8}|3[0347]\d{8}|5[56]\d{8}|8((4[2- 5]|70)\d{7}|45464\d)))(\D+\d+)?$ +44$1 UK-Service^(1(47\d|70\d|800\d|1[68]\d{3}|\d\d)|999|112|[\*\#][\*\#\d]*\#) $ +$1 UK-International^(?:00)?((1[2-9]\d\d[2-9]\d{6})|([2-9]\d{6,14}))(\D+\d+)?$+$1

Slide 29

Slide 30

Slide 31

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

Slide 32

Slide 33

Slide 34

X

Slide 35

Slide 36

Slide 37

Slide 38

Ordering and selection of PSTN Usages is critical

Slide 39

Slide 40

Slide 41

Slide 42

Slide 43

Rule NamePatternTranslation UK-London-Local^\+4420([378]\d{7})(;ext=\d+)?$$1 UK-London-Service^\+(1(47\d|70\d|800\d|1[68]\d{3}|\d\d)|999|[\*\#][\*\#\d]*\#)$$1 UK-London-AllCalls^\+44(\d+)(;ext=\d+)?$0$1 UK-London-International^\+((1[2-9]\d\d[2-9]\d{6})|([2-9]\d{6,14}))(;ext=\d+)?$00$1 Rule NamePatternTranslation NA-ON-Toronto-Local ^\+1((905(20[^7]|21[02469]|22[1234]|23[^35]|24[178]|25[^1239]|26[45678]|28[^09]|29[^567]|30[^489]|31[36]|33[04789]|36[^0578]|39[1589]|40[^147]|41[23578]|4 2[^59]|46[^8]|47[^368]|48[^15]|49[^368]|51[034]|53[02349]|55[^1567]|56[^0123]|58[^19]|59[^246]|62[^0378]|64[029]|65[234]|66[039]|67[^459]|68[36]|69[^027]| 6[01]\d|70[23679]|71[237]|72[4679]|73[1789]|74[04789]|75[^3]|76[^589]|77[013]|78[^68]|79[^7]|80[13458]|81[^018]|83[^0456]|85[^3]|86[^589]|87[^01]|88[^5]|89 [01367]|8[24]\d|90[^256]|91[^124]|93[69]|94[^125]|95[16]|96[589]|99[^1234]|326|350|370|542|636|927|970|(27|45|50)\d))) $1 NA-National^\+1([2-9]\d\d[2-9]\d{6})(;ext=\d+)?$1$1 NA-Service^\+([2-9]11)$$1 NA-International^\+([2-9]\d{6,14})(;ext=\d+)?$011$1

Slide 44

Slide 45

Slide 46

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

Slide 58

Slide 59

Slide 60

Slide 61

Slide 62

Slide 63

Slide 64