Transcription

1

2

3

4

5

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

7 On-premises Lync Server 2013 Private cloud/dedicated Lync 2013 Single domain and directory Users split server/online Cloud Microsoft Office 365, Lync Online Partner-hosted or multi-tenant

8 8.

9 Lync Voice

10

11 10 9 Must Match A Rule 5 Dialing Behaviors 404: No matching rule Routing & Policy Creates Authorization per User Routing 1. Vacant Number Range 2. Call Park Orbit Range 11 Announcement or Call Park Application 7 4 Dial Plan Normalization Rule Normalization Rule Normalization Rule msrtcsip-line msrtcsip-privateline 6 No match 3. Voice Policy Routes 403: No route found Call Park Orbit Range PSTN Usage PSTN Usage PSTN Usage 13 Lync Client Normalizes 12 No 3 Mediation Server and Trunk Configuration Route Route Route Route Global? Yes Reverse Number Lookup Gateway / IP-PBX / SIP Trunk 1 RFC 3966 Starts with + Convert # to Local Format User=phone 2 No 8 Location Policy PSTN Usage User Initiates Call Emergency Call? Yes Match SIP URI PSTN Fallback for CAC and Network Outages Inbound Routing User Focused Infrastructure Focused Apply Called Party Prefs 14 External Endpoint Receives Call UC Endpoint Receives Call 11

12 Voice policies PSTN usages Routes 12 User authorization Class of service Voice feature set Purpose (usage, caller s intent) Calling location Priority Called number Cost of call

13 13

14 14

15 15

16 .

17

18

19 is not Free!

20

21

22 22

23

24 Call park and response groups Dial-in conferencing UM routing Consultative transfers

25 Compliance / Toll Bypass Prevention Call Flow Optimization Trying to combine the two is complex

26 Support & Configuration

27 27

28 Pool Version Mediation Server Version Supported Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 Lync Server 2010 Office Communications Server 2007 R2 Lync Server 2013 Any No Lync Server 2010 Any No Office Communications Server 2007 R2 Any Yes No No No No 28

29 Client Type Supported Details Lync 2013 Lync 2010 Office Communicator 2007 R2 Lync Phone Edition Lync Attendant Lync for Windows 8 Lync Mobile 2013 Lync Mobile 2010 Yes Yes No Yes Yes No No Yes Including Lync 2013 February 2013 Cumulative Update VoIP must be disabled for Lync Mobile 2013 clients if used by users with Location-Based Routing enabled. 29

30 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>

31 Set-CsVoicePolicy -Identity <voice policy ID> -PreventPSTNTollBypass <$true $false> Set-CsRoutingConfiguration -EnableLocationBasedRouting $true

32

33 Logic

34 34

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

36 Start Is Global LBR switch on? Yes Is from Phone? Yes Is source trunk LBR? Yes Get site associated with the trunk No No No Route to endpoint Yes Is endpoint in the No Route to UM gateway site? Stop 36

37 Start Is source trunk LBR enabled? No Is request FWD/XFER/ Simulring? Yes Yes No Use usages from source trunk associated site Use the usages specified in the trunk config Use the usages of the user s voice policy Select next applicable usage. Select next applicable usage. Yes Are there additional usages? No Yes No Are additional usages in the site? No Are source and destination trunks sites the same? Is destination trunk LBR enabled? Yes Are source and destination trunks sites the same? Do not allow call No No Do not allow call Yes Normal Processing Yes 37 Stop

38 38

39 Sample Scenario s

40 40.

41 41

42 42

43

44

45 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 Port A Port B Port n Trunk 1 Trunk 2 Trunk n Port A1 Port B1 Port n1 IP-PBX

46 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 Trunk 1 MED-10<->PBX-10 PBX-10 port : 5060 Signaling IP : PBX-1 Media IP : MTP-1 MED-10 Trunk 2 MED-10<->PBX-10 PBX-10 port : 5061 Signaling IP : PBX-1 Media IP : MTP PBX-10 PSTN Gateway PBX-10 MTP-1 Media Bypass MTP-2 Media Bypass PBX Extension PBX Extension

47 Trunks and resiliency Gateway F connects to two Mediation Servers Mediation Server C Gateway F Resiliency does not require multiple MS listening ports. The main reason for multiple MS listening ports is interoperability. Port A Trunk 1 Port B PSTN Gateway FQDN F Fully supports TLS Example Mediation Server D 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 Port C Trunk 3 Port E Gateway G PSTN Gateway FQDN G

48 PSTN SBC sbc1.provider.com 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 Trunk 1 Trunk 2 MPLS Site 01 Site 02 Mediation Pool Mediation Pool Lync Pool

49 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.

50 a.k.a. Session management

51 From:

52 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

53 PSTN PSTN Local & LD Trunks Local & LD Trunks Avaya CM 1.3 SiteC SiteH Avaya CM 5.0 4xT1 SiteI Cisco CUCM Local & LD Trunks PSTN PSTN PSTN Local & LD Trunks 4xT 1 3 xt1 3xT1 40 x IP 96 x IP 4xT1 Avaya G 3 siv 9 SiteG Local & LD Trunks SiteB 3xT1 Avaya CM x IP 9xT1 2xT1 2xT1 PSTN Local & LD Trunks 4 x T1 2xT1 81 x IP Contoso IP Network 2xT 1 Enterprise Contact Center PSTN Local & LD Trunks 66 x IP 32 x IP PSTN Avaya CM x T1 SiteA 4xT1 2xT 1 6xT1 Avaya G 3 xv 12 SiteE Local & LD Trunks SiteD SiteF Avaya CM 1. 3 Avaya G 3 csiv 6. 3 Local & LD Trunks PSTN Private Fiber SiteD Expansion Port Network Local & LD Trunks PSTN DCS QSIG Inter -PBX VoIP

54 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 Inbound Trunk PSTN Usage Lync Pool Route Outbound Trunk Qualified IP-PBX Lync Mediation Server Lync Mediation Server Qualified Gateway Trunk Trunk PSTN MEDIA Inbound Trunk PSTN Usage Lync Pool Route Outbound Trunk PBX User Qualified IP-PBX Lync Mediation Server Lync Mediation Server Qualified IP-PBX PBX User Trunk Trunk 55 MEDIA

56 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

57 Configuration

58

59

60 Using the Lync Management Shell New-CsVoiceRoute -Identity RedmondRoute Redmond"} Set-CsTrunkConfiguration Identity TrunkId Redmond } Or through the Lync Control Panel

61 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

62

63

64 ios (version 6 or below): Please input the below URL: Other platform: QR Code:

65