Skye For Business Enterprise Voice

Module2
Configuring Basic Enterprise Voice Functionality
MVA Jump Start

Module Overview
• Introduction to Lync Voice Routing

• Configuring Enterprise Voice
• Defining Voice Policies
• Assigning DID Numbers
• How to Design a Dial Plan
Lesson 1: Introduction to Lync Voice Routing
• Voice Routing
• Number Normalization and E.164
Voice Routing
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Normalization Rule No No
Global Emergency
Normalization Rule ? Call?
404: No
matching Call Park Orbit Range Yes
Yes
Dialing rule
Behaviors
Reverse Number Lookup
Routing &
Authorization No match Match
3. Voice Policy Routes Location Policy

1. Vacant Number
Range
PSTN Usage Route PSTN Usage
PSTN Usage Route
2. Call Park Orbit Route
Range PSTN Usage Route
Mediation Server and

Announcement or 403: No Trunk Configuration
Call Park Application route
found
Gateway / IP-PBX / SIP Trunk Inbound Routing
External Endpoint Receives Call UC Endpoint Receives Call

4
1 of 14
1 User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

5
2 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule 2
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

6
3 of 14
User Initiates Call

Dial Plan
RFC 3966 User=phone SIP URI
Starts with +
Normalization Rule
Global Emergency
3
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

7
4 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Lync Client
Normalization Rule Normalizes
4 Normalization Rule No
Global
No
Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

8
5 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Must Match Global Emergency
A Rule
5 404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

9
6 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
matching 6 Call Park Orbit Range Yes
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

10
7 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
7 msRTCSIP-Line
msRTCSIP-PrivateLine
Routing &

1. Vacant Number
Range
PSTN Usage Route

found

11
8 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &
Authorization No match 8 Match

1. Vacant Number
Range
PSTN Usage Route
PSTN Fallback for
CAC and Network
Outages

Call Park Application route Apply Called
found Party Prefs

12
9 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
9 Range
PSTN Usage Route

Call Park Application route Apply Called
found Party Prefs

13
10 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

10 Call Park Application route
found

14
11 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &
Policy Creates
3. Voice
per User RoutingPolicy Routes Location Policy
1. Vacant Number
Range
PSTN Usage Route
11

found

15
12 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
12
PSTN Usage Route

found

16
13 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

Announcement or 403: No 13 Trunk Configuration
route Convert #
Call Park Application to Local Format
found

17
14 of 14
User Initiates Call

Dial Plan
User=phone SIP URI
Normalization Rule
Global Emergency
404: No
Yes
Dialing rule
Behaviors
Routing &

1. Vacant Number
Range
PSTN Usage Route

found
14 External Endpoint Receives Call UC Endpoint Receives Call

18
Number Normalization and E.164
Country Code National Destination Code Subscriber

(Optional) number
National (significant) number
1 to 3 digits Maximum = 15 – cc = 12 to 14 digits
31 (Netherlands) 20 (Amsterdam) 500 1500
1 (US) 425 (Washington) 882 8080
Country Code Group Identification Subscriber number

Code
3 digits 1 digit Max = 15 – (cc + gic)
= 11 digits
599 (Netherlands 7 (Bonaire) 500 1500
Antilles)
Lesson 2: Configuring Enterprise Voice
• Scoping configuration items and policies

• Dial Plans
• Normalization & Regular Expressions
• Address Book Normalization
Scoping configuration items and policies
Global Contoso
Site Chicago London
Dublin-
Pool Chicago-1 Chicago-2
1
User
Dial Plans
• A dial plan is a named set of normalization rules that translates

phone numbers for a named location, individual user, or contact
object into a single standard (E.164) format for purposes of phone
authorization and call routing.
http://technet.microsoft.com/en-us/library/gg413082.aspx
Normalization & Regular Expressions
• Dial plans perform normalization using regular expressions

• Lync Control Panel
• Or built from scratch using
standardized regular
expressions
Address Book Normalization
• Converts phone numbers from external address books into E.164

format for use by Lync Server 2013.
– Active Directory
• Customizing Address Normalization rules
1. Create or edit \\server\CSShare\Site-WebServices-
N\ABFiles\Company_Phone_Number_Normalization_Rules.txt
2. Add regular expressions
3. Run ABServer.exe -TestPhoneNorm “…” to load file
Lesson 3: Defining Voice Policies
• Routing and Authorization, the Big Picture

• Voice Policies
• PSTN Usage
• Call Forwarding & Simultaneous Ring
• Routes
• Trunk Configuration
• Truck Configuration Example
Routing and Authorization, the Big Picture
Voice Policies PSTN Usages Routes
• User authorization • Purpose (usage, • Called number

• Class of service caller’s intent) • Cost of call
• Voice feature set • Calling location
• Priority
Voice Policies
• Can be assigned per user, site or global

• Not only for users. Also useful to address Common Area Device
requirements:
• Assign a Voice Policy to a common area phone to prevent misuse and high
cost
• Provides admins with flexibility to control user voice entitlements:
PSTN Usage
• Control Dialing capabilities (Class of Service) by assigning PSTN Usages

• A Public Switched Telephone Network (PSTN) usage record specifies a
class of call (such as internal, local, or long distance) that can be made by
various users or groups of users in an organization
• By themselves, PSTN usage records do not do anything. For them to work,
they must be associated with the following:
– Voicepolicies, which are assigned to users
– Routes, which are assigned to phone numbers
Call Forwarding & Simultaneous Ring
• Lync Server 2010: An administrator can enable or disable call

forwarding and simultaneous ring through the user voice policy
• Lync Server 2013: Enables call controls to introduce a flexible call-
authorization mechanism for forwarding and simultaneous ring calls
• By using this feature, a company can restrict calls forwarded by users
or through simultaneous ring
– Local numbers only, to aid in cost control
– Internal Lync users only, for security policies
– Any custom authorization rule set up by the administrator
Call Forwarding & Simultaneous Ring
Voice Policy
“Redmond”
“Call PSTN
Usages”
Call Forwarding
“Internal
Lync users
only”
Simultaneous
30
Ring “Custom
PSTN
Usages”
Routes
• A voice route associates destination phone numbers with one or

more public switched telephone network (PSTN) gateways or SIP
trunks, and one or more PSTN usage records
• A route is selected based on a matching pattern
• PSTN Usages control if a user is allowed
to use the route
• Routes are associated with one or more
trunks defined in Topology builder
Trunk Configuration
• Trunk configuration is applied to Trunks defined in Topology Builder

• Trunk configuration settings define the configuration and capabilities
between a Mediation Server and the PSTN gateway, an IP-PBX, or a
SBC at the service provider
• Settings include:
• Whether media bypass should be enabled on the trunks
• The conditions under which real-time transport control protocol (RTCP) packets are sent
• Whether or not secure real-time protocol (SRTP) encryption is required on each trunk
Truck Configuration Example
• Allow for centrally managing number formatting prior to routing to

PBX/PSTN for both the calling and called number
Lesson 4: Assigning DID Numbers
• Assigning DIDs to a User

• Specifying Line URI
• Internal-Only – Users Without DID
Assigning DIDs to a User
• Direct Inward Dialing (DID)

• DID numbers are globally unique
• DID ranges / blocks are acquired from the Telecom Provider
• DID numbers allow external users to connect to a Lync user directly.
• Assigned to a user when enabling for Enterprise Voice
Specifying Line URI
• DID numbers can be defined in two formats:

• tel:+14258828080;ext=8080
• tel:+14258828080
• Recommendation: Specify extensions (ext=) for all users to:

– Optimize PIN authorization for devices and dial-in conferencing
– May need to deal with “;ext=“ in trunk normalization for cases of PSTN reroute
Internal-Only – Users Without DID
• The full URI points to the switchboard or Exchange AA number:

– Users each will have a unique “ext=xxxx”
– Example:
• User A tel:+14258828080;ext=51855
• User B tel:+14258828080;ext=51856
• User C tel:+14258828080;ext=51857
• Base number should point to Exchange AA with number:

– tel:+14258828080;ext=1
• Normalization of inbound number should add “;ext=1” so that

unique number of AA can be found via reverse number lookup:
– ^(\+14258828080)$ → $1;ext=1
Lesson 5: How to Design a Dial Plan
• Dial Plan Design Approach

• Real World Scenarios & Recommendations
• Route Planning – A Real World Example
• Route Planning Details
• Number Blocking
Dial Plan Design Approach
• Document all existing dialing habits

• Consider the current dial plan
• Understand gateway & Mediation Server locations
• Understand your customer requirements
Dial Plan Design Approach
• Define a strategy
– Keep the existing DIDs or new numbers when migrated to Lync?
– Implement changes or copy the existing numbering plan?
– Lync or PBX Phone vs. Lync and PBX phone?
• Start with defining the routes

• Define user voice policies (Classes of Service)
– Incorporate requirements for least-cost routing and PSTN rerouting and
fallback if needed
• Use PSTN Usages to associate routes to voice policies
Real World Scenarios & Recommendations
• Copying existing dialing habits is not always a good idea

• Some are just there to accommodate the PBX
Scenario Remark Recommendation

Dial a “9” to seize an outside line PBX specific behavior Avoid creating normalization rules for this
Example: 9 0031205001500 habit
Dial “00” for an international number Country specific behavior Create a normalization rule that
Example: 00 31205001500 Not required but everybody uses it translates to E.164
Prefix an internal number with a PBX PBX specific behavior Avoid creating normalization rules for this
specific trunk number (Steering Code) Created to overcome the lack of support habit
Example: 203 1111 for E.164 for PBX
Route Planning – A Real World Example
Routes for the gateways in Europe – DE -

Munich
DE Internal ^\+49895550[12]
International
DE Munich ^\+4989
Local
National Premium
Europe DE Germany ^\+49
National
Gateway DE Europe ^\+(49)|(31)|(33)|(32)|(34
)|(351)|…
Local
DE ^\+
International Internal
Asia
Gateway USA
International Gateway
National Premium International
National National Premium
Local National
Internal Local
Internal
Exercises
Starting
Name Match Pattern Digits Length Normalization rule Example dial string translation
Redmond operator ^(0)$ 0 Exactly 1 +14255550101 0 to +1425550101
Redmond 3 digit ^1(\d{2})$ 1 Exactly 3 +14255550$1 1** to +142555501**
internal
Redmond 7 digit ^(\d{7})$ Any Exactly 7 +1425$1 ******* to +1425*******
Redmond 10 digit ^(\d{10})$ Any Exactly 10 +1$1 ********** to +1**********
Redmond 11 digit ^(1\d{10})$ 1 Exactly 11 +$1 1********** to +1**********
long distance
Redmond ^011(\d*)$ 011 Any +$1 011 + any number of digits to + (any
International number of digits). Leading 011 is stripped.
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be
registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the
current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this
presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skye For Business Enterprise Voice

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Skye For Business Enterprise Voice

Uploaded by

Copyright:

Available Formats

Module2

Configuring Basic Enterprise Voice Functionality

MVA Jump Start

• Introduction to Lync Voice Routing

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

1 User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

3. Voice Policy Routes Location Policy

Mediation Server and

14 External Endpoint Receives Call UC Endpoint Receives Call