65
Reverse
proxy
External
Edge
serverFederated
Network
Hybrid
Perimeter
networkInternal
UC end points
EE pool
IP-PSTN
gateway
Persistent
Chat (optional)
ADMIIS
Identity
Voicemail/
Archive
Monitoring
File store
Web Access
CDR/QoE/
Report DB
Exchange
SCOM
DFS
Office Web Apps
SQLPBX
New!
New!
Mediation Server
(optional)
PSTN
Front-end
Back-end
EdgeMore secure
federation and
interoperability
External user
ingress
PoolFewer,
consolidated
servers
ServicesConsolidated
archiving
SCOM, AD, DFS
Microsoft Office 365, Lync Online
Partner-hosted or multi-tenant
Single domain and directory
Users split—server/online
Lync Server 2013
Private cloud/dedicated
Lync 2013 On-premises Cloud
.
8
Lync Voice
11
Announcement orCall Park Application
1. Vacant Number Range
2. Call Park Orbit Range
DialingBehaviors
Routing &Authorization
Normalization Rule
Normalization Rule
Normalization Rule
Dial Plan
PSTN Usage
PSTN Usage
PSTN Usage
3. Voice Policy Routes
Route
RouteRoute
Route
External Endpoint Receives Call UC Endpoint Receives Call
User Initiates Call
User=phone
Yes
Global?
No
SIP URI
Match
Reverse Number Lookup
No match
Mediation Server andTrunk Configuration
Gateway / IP-PBX / SIP Trunk Inbound Routing
404: No matching
rule
403: No route found
Yes
EmergencyCall?
No
PSTN Usage
Location Policy
Call Park Orbit Range
1
2
3
4
56
7
8
9
10
11
12
13
Must MatchA Rule
Lync ClientNormalizes
RFC 3966Starts with +
msRTCSIP-LinemsRTCSIP-PrivateLine
Policy Createsper User Routing
Convert #to Local Format
Apply CalledParty Prefs
PSTN Fallback forCAC and Network
Outages
14
User
Focused
Infrastructure
Focused
12
Voice policies PSTN usages Routes
Called numberCost of call
Purpose (usage, caller’s intent)Calling locationPriority
User authorizationClass of serviceVoice feature set
13
14
15
.
is not Free !
22
Call park and response groups
Dial-in conferencing
UM routing
Consultative transfers
Compliance / Toll Bypass Prevention
Call Flow Optimization
Trying to combine the two is complex
Support & Configuration
27
28
Pool Version Mediation Server Version Supported
Lync Server 2013 February 2013
Cumulative Update
Lync Server 2013 February 2013 Cumulative
UpdateYes
Lync Server 2013 February 2013
Cumulative UpdateLync Server 2013 No
Lync Server 2013 February 2013
Cumulative UpdateLync Server 2010 No
Lync Server 2013 February 2013
Cumulative UpdateOffice Communications Server 2007 R2 No
Lync Server 2013 Any No
Lync Server 2010 Any No
Office Communications Server
2007 R2Any No
29
Client Type Supported Details
Lync 2013 YesIncluding Lync 2013 February 2013
Cumulative Update
Lync 2010 Yes
Office Communicator 2007 R2 No
Lync Phone Edition Yes
Lync Attendant Yes
Lync for Windows 8 No
Lync Mobile 2013 No
VoIP must be disabled for Lync
Mobile 2013 clients if used by users
with Location-Based Routing
enabled.
Lync Mobile 2010 Yes
New-CsVoiceRoutingPolicy-Identity <voice routing policy ID> -Name <voice routing policy name> -PstnUsages <usages>
Set-CsNetworkSite-Identity <site ID> -EnableLocationBasedRouting <$true|$false> -VoiceRoutingPolicy <voice routing policy ID>
New-CsTrunkConfiguration-Identity <trunk configuration ID>
Set-CsTrunkConfiguration-Identity <trunk configuration ID> -EnableLocationRestriction $true -NetworkSiteID <site ID>
Set-CsVoicePolicy-Identity <voice policy ID> -PreventPSTNTollBypass <$true|$false>
Set-CsRoutingConfiguration-EnableLocationBasedRouting $true
Logic
34
One policy for authorization and a different policy for routing
Authorization
Routing Decision
Start
Is Global LBR switch on?
Is from Phone?Get site associated
with the trunkYes Yes
Is source trunk LBR ?
Yes
Is endpoint in the gateway site?
YesRoute to endpoint No Route to UM
Stop
No
No
No
36
37
Stop
Is source trunk LBR enabled?
Select next applicable usage.
Are source and destination trunks
sites the same?
Yes
Normal Processing
No
Select next applicable usage.
Is destination trunk LBR enabled?
No
Do not allow callYesNoAre additional usages
in the site?
Do not allow call
No
Yes
Use usages from source trunk associated site
Use the usages of the user s voice policy
Yes
Are there additionalusages?
NoYes
Use the usages specified in the trunk config
Is request FWD/XFER/Simulring?
No
Yes
Are source and destination trunks
sites the same?
No
Yes
Start
38
•
•
•
•
•
•
•
Sample Scenario’s
40
.
41
42
Trunks and IP-PBX interworkingTrunks associate Mediation Servers with PSTN Gateways
Multiple trunks can be defined between Mediation Server and PSTN gateway representing IP-PBX SIP termination.
Each trunk will be associated with the appropriate route for outbound calls from MS to IP-PBX.
For inbound calls, per-trunk policy will be applied.
Trunk configuration will be scoped globally or per trunk; similarly, dial plan can be scoped per trunk.
Representative media IP is a per-trunk parameter.
Mediation Server IP-PBX
Port A Port A1Trunk 1
Port B Port B1Trunk 2
Port n Port n1Trunk n
Typical PBX deployment:
Central Call Control (PBX-10)
Decentralized Media Termination Points (MTPs / Gateways)
Technical requirements
Use MTPs on same site as Lync Client,keep media local
Enable Media Bypass
Deployment and configuration:
1. Define PBX-10 as PSTN Gateway
Use MTP1 as Alternate Media IP-Address
The First Trunk is created automatically
2. Add Additional trunks for remaining MTPs:
Use different PBX Listening ports
3. Use PS to define RepresentativeMediaIP for each MTP/Trunk
PBX-10
PBX Extension
PBX Extension
MTP-2
MED-10
Trunk 1
MED-10<->PBX-10
PBX-10 port : 5060
Signaling IP : PBX-1
Media IP : MTP-1
Trunk 2
MED-10<->PBX-10
PBX-10 port : 5061
Signaling IP : PBX-1
Media IP :
Media Bypass
Media Bypass
MTP-1
PSTN Gateway
PBX-10
MTP-2
5060
5061
Trunks and resiliency Gateway F connects to two Mediation Servers
Resiliency does not require multiple MS listening ports.
The main reason for multiple MS listening ports is interoperability.
Fully supports TLS
Example
Port C : 5061, can be used as the MS listening port for Gateway 1 and Gateway 2
Port D : 5068 can be used on SAME MS for a different gateway or IP-PBX if required
Mediation
Server C
Gateway F
Port A Port BTrunk 1
Port C Port ETrunk 3
Mediation
Server D
Gateway G
PSTN
Gateway
FQDN F
PSTN
Gateway
FQDN G
Trunks & GatewaysSeparation of Configuration between Gateways and Trunks
Gateways define the next hop
Trunks define the relation between Mediation Server and Gateway
Allows for TLS, eliminates the need for Virtual Gateways
Allows for Gateway-specific inbound policies
Site 02Site 01
Lync Pool
Mediation Pool
SBC
sbc1.provider.com
Mediation Pool
Trunk 1 Trunk 2
PSTN
MPLS
Trunk definitionIn Lync Server 2013, a trunk is defined as a combination of:
MS FQDNMediation SIP listening portGateway FQDNGateway SIP listening port
This approach provides for:
Better resiliency—both service and on-premises scenarios
Better interworking with IP-PBXs for bypass
Using TLS plus Secure Real-Time Transport Protocol (SRTP) for multiple SIP trunks to the same SBC FQDN
When outbound routing matches a dialed PSTN number to a route, the route will consist of a list of trunks.
Contrast this approach with Lync 2010, where a route consisted of a list of gateways.
a.k.a. Session management
From: http://technet.microsoft.com/en-us/library/jj721940.aspx
“Better integration with systems certified to connect with Lync”
A possible alternative for PBX integration scenarios
Lync Server can support call routing from an incoming trunk to an outgoing trunk to provide routing functionalities to other systems
By enabling intertrunk routing, the following routing paths (among others) are enabled:
Lync Server 2013 serves as the glue (that is, the interconnection) between different telephony systems
Local & LD Trunks
PSTN
4 xT 1
4 xT 1
3 xT 1
9 xT 1 2 xT 1
2 xT 1
DCS QSIG Inter - PBX VoIP
6 xT 1
32 x IP
96 x IP
40 x IP 3 xT 1
4 x T 1
41 x IP
4 xT 1
4 xT 1
2 xT 1 81 x IP
3 xT 1
2 xT 1
2 xT 1
Enterprise Contact Center
66 x IP
Contoso IP Network
1 x T 1
Local & LD Trunks
PSTN
SiteB Avaya CM 1 . 3
Local & LD Trunks
PSTN
SiteC Avaya CM 1 . 3
Local & LD Trunks
PSTN
SiteH Avaya CM 5 . 0
Private Fiber
Local & LD Trunks
PSTN
SiteD Avaya CM 1 . 3
SiteD Expansion
Port Network
Local & LD Trunks
PSTN
SiteA Avaya CM 1 . 3
Local & LD Trunks
PSTN
SiteG
Avaya G 3 siV 9
Local & LD Trunks
PSTN
SiteI Cisco CUCM
6 . 1 . 3
Local & LD Trunks
PSTN
SiteE
Avaya G 3 xV 12
Local & LD Trunks
PSTN
SiteF Avaya
G 3 csiV 6 . 3
Lync supports the association of a set of PSTN usages on an incoming trunk to determine a call route to an outgoing trunk
Intertrunk configuration remains familiar for the administrator with the use of existing routing configuration concepts
Media bypass in intertrunk routing calls is supported
Intertrunk routing call authorization scope is at the trunk level
55
LyncPool
LyncMediation Server
LyncMediation Server
QualifiedIP-PBX
Trunk Trunk
InboundTrunk
PSTNUsage
RouteOutbound
Trunk
MEDIA
QualifiedGateway
PSTN
LyncPool
LyncMediation Server
LyncMediation Server
QualifiedIP-PBX
Trunk
QualifiedIP-PBX
Trunk
InboundTrunk
PSTNUsage
RouteOutbound
Trunk
MEDIA
PBX User PBX User
Lync is now a first class citizen with other PBXs in the customer’s telecom network
No need for dependency on existing PBX for PSTN access
Replaces “smart” gateway AD-based routing solutions with Lync plus basic gateways
Configuration
Using the Lync Management Shell
•
Or through the Lync Control Panel
New-CsVoiceRoute -Identity RedmondRoute -PstnUsages@{add=“Redmond"}
-PstnGatewayList @{add="PstnGateway:redmondgw1.contoso.com"}
Set-CsTrunkConfiguration –Identity “TrunkId” -PstnUsages @{add=”Redmond”}
Translation rules can be applied at the trunk level
Translate numbers on outbound calls
Can manipulate both caller and callee numbers
Use to accommodate dial plans of connected PBXs
ios (version 6 or below):
Please input the below URL:
http://aka.ms/UNC393
Other platform:
QR Code:
