Presentation is loading. Please wait.

Presentation is loading. Please wait.

Public Providers Reverse proxy External Edge server Federated Network Hybrid Perimeter network Internal UC end points EE pool IP-PSTN gateway Persistent.

Similar presentations


Presentation on theme: "Public Providers Reverse proxy External Edge server Federated Network Hybrid Perimeter network Internal UC end points EE pool IP-PSTN gateway Persistent."— Presentation transcript:

1

2

3

4 Public Providers Reverse proxy External Edge server Federated Network Hybrid Perimeter network Internal UC end points EE pool IP-PSTN gateway Persistent Chat (optional ) ADMIIS Identity Voic / Archive Monitoring File store Web Access CDR/QoE/ Report DB Exchange SCOM DFS Office Web Apps SQL PBX New!  Mediation Server (optional) PSTN Front-end Back-end Edge More secure federation and interoperability External user ingress Pool Fewer, consolidated servers Virtualized and higher scale Services Consolidated archiving SCOM, AD, DFS

5 Location-Based Routing Support for M:N—MS:GW Session management Improved Caller ID management Improved delegate routing Response Group Manager Support for IPv6 in all Lync components Support for VDI for audio and video Routing enhancements IPv6 VDI Lync Voice

6 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

7

8

9 9 Announcement or Call Park Application 1. Vacant Number Range 2. Call Park Orbit Range Dialing Behaviors Routing & Authorization Normalization Rule Dial Plan PSTN Usage 3. Voice PolicyRoutes 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 and Trunk Configuration Gateway / IP-PBX / SIP Trunk Inbound Routing 404: No matching rule 403: No route found Yes Emergency Call? No PSTN Usage Location Policy Call Park Orbit Range Must Match A Rule Lync Client Normalizes RFC 3966 Starts with + msRTCSIP-Line msRTCSIP-PrivateLine Policy Creates per User Routing Convert # to Local Format Apply Called Party Prefs PSTN Fallback for CAC and Network Outages 14

10 The big picture of the most important elements 10 Voice policies PSTN usages Routes Called number Cost of call Purpose (usage, caller’s intent) Calling location Priority User authorization Class of service Voice feature set

11

12

13

14

15

16

17 Toll Bypass Use the own (WAN) infrastructure as much as possible Egress to the PSTN closest to the destination Avoid international (costly) PSTN charges

18 GOODBAD

19 Enforces that outgoing calls must egress from an allowed PSTN gateway in the caller’s voice policy, based on the callers location Can prevent the incoming call to the Lync client if the endpoint is not in the PSTN gateway’s location Lync Conferencing honors LBR policies for PSTN dial-out

20

21 Call park and response groups Call flows with these scenarios could violate the regulatory principles Either a) do not deploy or b) deploy only to users within a single site Dial-in conferencing Dialing in may create a conference that has PSTN and VoIP users from different sites For strict compliance, do not deploy dial-in access numbers and require dial-out UM routing Denied inbound calls are sent to UM For strict compliance, place the UM server for a group of users in same site as the gateway that terminates their DIDs Consultative transfers When a single Mediation Server serves multiple trunks (PBX and PSTN), LBR may be enforced when not necessary Deploy additional Mediation Servers for trunks to PBX where LBR is not required

22

23 Site One or more Lync subnet(s) assigned to a location Uses existing network sites as defined for LIS, Media Bypass and E911 Voice Routing Policy Voice policy that only contains usages Specifically assigned to a site for LBR Contains all allowed usages for that specific site or trunk Unknown Location Location (subnet) that is not known as a Lync Site Trunk Connects gateways and mediation servers Can be enabled for LBR and must be assigned to site

24 Pool VersionMediation Server VersionSupported Lync Server 2013 February 2013 Cumulative Update Yes Lync Server 2013 February 2013 Cumulative Update Lync Server 2013No Lync Server 2013 February 2013 Cumulative Update Lync Server 2010No Lync Server 2013 February 2013 Cumulative Update Office Communications Server 2007 R2No Lync Server 2013AnyNo Lync Server 2010AnyNo Office Communications Server 2007 R2 AnyNo

25 Client TypeSupportedDetails Lync 2013Yes Including Lync 2013 February 2013 Cumulative Update Lync 2010Yes Office Communicator 2007 R2No Lync Phone EditionYes Lync AttendantYes Lync for Windows 8No Lync Mobile 2013No VoIP must be disabled for Lync Mobile 2013 clients if used by users with Location-Based Routing enabled. Lync Mobile 2010Yes

26 New-CsVoiceRoutingPolicy -Identity -Name -PstnUsages Set-CsNetworkSite -Identity -EnableLocationBasedRouting -VoiceRoutingPolicy Create the Voice Routing Policy Enable Location Based Routing for Network Sites Enable Location Based Routing and assign a Voice Routing Policy to the Network Site New-CsTrunkConfiguration -Identity Set-CsTrunkConfiguration -Identity -EnableLocationRestriction $true -NetworkSiteID Create a Trunk Configuration (Only for PSTN gateways, not Internal PBX routes) Enable Location Based Routing through Trunks Enable Location Based RoutingOn the Trunk

27 Set-CsVoicePolicy -Identity -PreventPSTNTollBypass Modify the Voice Policy Enable LBR through Voice Policy Set-CsRoutingConfiguration -EnableLocationBasedRouting $true Create a Trunk Configuration (Only for PSTN gateways, not Internal PBX routes) Enable Location Based Routing Globally

28 When using LBR, the site routing policy must include a route for all possible calls It’s possible that a call would be allowed by the user’s policy, but if it weren’t allowed by the site’s policy it would be blocked. Trunks are associated with one network site For LBR, your campus must be represented as one site if using centralized SIP Trunks.

29

30

31 One policy for authorization and a different policy for routing Authorization Routing Decision

32

33

34 The LBR conferencing application ensures that a single conference does not contain VoIP users from different sites and PSTN dial-out. If there are users in a given conference joining via Lync VoIP clients from a single network site, the following endpoints will be allowed to join the conference: a PSTN endpoint, another Lync VoIP client user from the same site, another Lync VoIP client user from a different site, or a Lync VoIP client user from an unknown network site. If there are organizers or participants from different or unknown network sites in a given conference, a PSTN endpoint will not be allowed to join the conference via a trunk that is enabled for Location-Based Routing. If there are organizers or participants from a single site and participants joining via PSTN in a given conference, a Lync client endpoint from a different site will not be allowed to join the conference.

35

36 Incoming PSTN calls Behavior for Incoming calls through Site 1 Gateway Calls to Users in “Site 1”  OK Calls to Users in Other Sites  Blocked Calls to Users without a location  Blocked Configuration Trunk to Site 1 Gateway enabled for LBR Site 1 Gateway associated to Site 1 Location

37 Outgoing PSTN calls Behavior for Outgoing calls Calls from Lync User 2: Route through Site 1 Gateway Calls from Lync User 1 Do not route through Site 2 Gateway Route through Site 2 Gateway instead Configuration Trunk to Site 1 Gateway enabled for LBR Site 1 Gateway associated to Site 1 Location Site 1 Voice Routing Policy -Route through Site 1 Gateway Lync User 2 Voice Policy - Route through Site 1 Gateway Lync User 1 Voice Policy - Route through Site 2 Gateway

38 Call Forwarding Configuration Trunk to Site 1 Gateway enabled for LBR Site 1 Gateway associated to Site 1 Location Lync User 2 forwards calls to Lync User 3 Lync User 1 forwards calls to Lync User 4 Behavior for Call Forwarding Incoming call to Lync User 2 Forwarded to Lync User 3 Incoming call to Lync User 1 Forwarding to Lync User 4 NOT allowed

39

40 Microsoft Office Communications Server 2007 R2 One Mediation Server (MS) was associated with one PSTN gateway and vice versa (1:1) Lync Server 2010 Multiple PSTN gateways can be associated with the same MS pool (1:N); a single PSTN gateway is associated with a single MS pool; a single SIP listening port on the MS and on the gateway are used in the association Lync Server 2013 Multiple PSTN gateways can be associated with the same MS pool, also a particular PSTN gateway can be associated with multiple MS pools or the same MS pool with multiple unique associations

41 Trunks and IP-PBX interworking Trunks 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 A1 Trunk 1 Port B Port B1 Trunk 2 Port n Port n1 Trunk n

42 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 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 MTP-1 PSTN Gateway PBX-10 MTP

43 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 B Trunk 1 Port C Port B Trunk 2 Port C Port E Trunk 3 Mediation Server D Gateway G PSTN Gateway FQDN F PSTN Gateway FQDN G

44 Trunks & Gateways Separation 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

45 Trunk definition In Lync Server 2013, a trunk is defined as a combination of: MS FQDN Mediation SIP listening port Gateway FQDN Gateway 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.

46

47 “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: Incoming PSTN calls to an IP-PBX system via Lync Outgoing IP-PBX calls to a PSTN network via Lync Outgoing IP-PBX calls to another IP-PBX system via Lync

48

49 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 The same call authorization applies to all calling endpoints connected via the trunk

50 New-CsVoiceRoute -Identity RedmondRoute Set-CsTrunkConfiguration –Identity “TrunkId”

51

52

53

54

55 Appendix: Implementation

56 Create a voice routing policy New-CsVoiceRoutingPolicy –Identity -Name -PstnUsages, User’s assigned voice policy is used for authorization Voice routing policy assigned to site is used to select gateway

57 Global flag Set-CsRoutingConfiguration -EnableLocationBasedRouting $true User’s voice policy Set-CsVoicePolicy -PreventPSTNTollBypass $true Network site Set-CsNetworkSite -Identity -EnableLocationBasedRouting $true -VoiceRoutingPolicy Trunk Set-CsTrunkConfiguration -Identity -EnableLocationRestriction $true -NetworkSiteID

58

59


Download ppt "Public Providers Reverse proxy External Edge server Federated Network Hybrid Perimeter network Internal UC end points EE pool IP-PSTN gateway Persistent."

Similar presentations


Ads by Google