Microsoft Lync Ignite. Microsoft Lync 2013

Transcription

1 Microsoft Lync Ignite Microsoft Lync 2013

2

3 Address Resiliency Within a Site Front-End Server Mediation Server 1 MPLS SBC PSTN In Lync Server 2010, you must define virtual gateways to achieve resiliency Virtual gateway FQDNs all resolve to the same IP address Virtual gateways do not work when there is no control over the certificate used for TLS interactions Gateway-specific inbound policy cannot be applied when virtual gateways are used sbc1.provider.com Mediation Server 2

4 SBC Address Multiple Sites Connecting to the Same Service Provider In Lync Server 2010, virtual gateways must be defined to allow connectivity from multiple MS pools to the same Session Border Controller (SBC) Fully Qualified Domain Name (FQDN) TLS could not be used because the SBC certificate does not contain the virtual gateway s name Site 1 Site 2 Preferred MS Pool Trunk 1 Trunk 2 MS Pool 1 MS Pool 2 FE Pool 1 Backup MS Pool PSTN GW Trunk 3 Address IP-PBX Interworking for Bypass Head Office Lync to IP-PBX call Site 1 In Lync Server 2010, you need to define virtual gateways to achieve bypass between a PBX endpoint and a Lync endpoint at the same site Front End Server MT Resource Virtual gateway FQDNs all resolve to the same IP address of the IP-PBX SIP call control termination point GW1 is associated with MT Resource at Site 1 in the CMS; Route 1 to all extensions in Site 1 has GW1 IP-PBX SIP Site 2 Extension GW2 is associated with MT Resource at Site 2 in the CMS; Route 2 to all extensions in Site 2 has GW2 Bypass can now happen for calls between a Lync endpoint and an IP-PBX endpoint at the same site Onerous task for admin when dealing with tens of sites Mediation Server Signaling Path Non-Bypass Media Path Bypass Media Path MT Resource Extension

5 Trunk Definition In Lync Server 2013, a trunk is defined as a combination of: MS FQDN, Mediation Server Session Initiation Protocol (SIP) listening port, Gateway FQDN, Gateway SIP listening port This 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 with Lync 2010, where a route consisted of a list of gateways Trunks and IP-PBX Interworking Define multiple trunks between MS 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 FQDN A Port A Port B Port N Trunk 1 Trunk 2 Trunk N PSTN Gateway FQDN B Port A1 Port B1 Port N1

6 Trunks and Resiliency Mediation Server FQDN C Note that a single MS listening port is needed for trunks to multiple gateways 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 Resiliency does not require multiple MS listening ports The main reason for multiple MS listening ports is interoperability Mediation Server FQDN D Port D Port C Trunk 2 Trunk 1 Trunk 3 Port B PSTN Gateway FQDN F PSTN Gateway FQDN G

7

8 Quicker Failover Based on Options Polls If all trunks on that MS have failed in at least their most recent options poll, the MS will immediately instruct the Front-End Server by means of a 503 to retry other MS in the pool for the call a. SIP MS Pool MS1 Options Options GW 1 GW 2 FE b. 503 MS2 d. SIP c. SIP MS3 GW 3 Quicker Failover Based on Options Polls If at least one other trunk has been successful in its most recent options poll, the MS will immediately instruct the Front-End Server by means of a 504 response that the trunk is down and a different trunk should be tried for the call MS Pool MS1 Options Options GW 1 FE a. SIP b. 504 MS2 GW 2 c. SIP MS3 d. SIP GW 3

9 OBR Retries to Next Trunk if No Timely 18X Received For non-bypass calls, the MS automatically sends a 183 response to OBR in Lync 2010 This results in the timer being immediately stopped, even though the gateway never answers with an 18x; the net result is that misconfigured and/or nonfunctioning gateways are masked, and OBR recovery to alternate routes is thwarted In Lync Server 2013, the autogenerated 183 response from the MS to OBR will not cause the OBR timer to stop 10-sec timer Invite Timer stopped 183 Lync 2010 FE MS GW Lync 2013 FE MS GW GW2 10-sec timer 1 Timer1 continues Timer1 exp 10-sec Timer2 Invite (Trunk 1) 183 Cancel Invite (Trunk 2) Timer2 stopped x Invite 18x

10

11 Outbound Calls Survivable Branch Appliance (SBA) Lync Server Supported Lync Server 2013 Lync Server 2010 Lync Server 2013 OCS 2007 R2 Inbound Calls Supported Supported Supported Not Supported Lync 2010 SBA Supported Supported * Lync 2013 SBA Not Supported Supported * Contents from Lync 2010 SBA will write monitoring and archiving contents to Lync 2010 store. Lync Server Supported Lync Server 2013 Lync Server 2010 Lync Server 2013 OCS 2007 R2 ** Assumed certified gateways for the release of Mediation Server shown in the tables above Supported Supported Supported Supported

12

13

14 Routing of IP-PBX Calls to Another IP-PBX System via Lync Inbound Trunk PSTN Usage Route Outbound Trunk 1. Incoming call from the PBX trunk Front-End Server 2. Validate incoming trunk associated PSTN usages 3. Determine a route 4. Apply outbound translation rules 5. Route to outgoing PBX trunk via Lync Trunk Trunk PBX User IP-PBX Mediation Server Mediation Server IP-PBX PBX User Media Routing of IP-PBX Calls to PSTN via Lync Inbound Trunk PSTN Usage Route Outbound Trunk 1. Incoming call from the PBX trunk 2. Validate incoming trunk associated PSTN usages 3. Determine a route 4. Apply outbound translation rules 5. Route to outgoing gateway trunk Front-End Server Trunk Trunk PBX User IP-PBX Mediation Server Mediation Server Gateway PSTN Media

15 New PSTNUsages property in CsTrunkConfiguration Configure a voice route New-CsVoiceRoute -Identity RedmondRoute Redmond"}

16 Voice policy PSTN usages Restrict to Lync users only Custom set of PSTN usages

17 New CallForwardingSimulRingUsageType & CustomCallForwardingSimulRingUsage properties in CsVoicePolicy

18 Lync user call to PSTN network Voice Policy Redmond Called # Trans. Use 011 prefix PSTN Usage International Calling # Trans. Remove + Route Redmond-Int Route call Outbound Trunk Redmond-GW 1. An administrator can associate a set of translation rules to a trunk configuration to enable calling number manipulation 2. A trunk to route the call is determined based on the user voice policy and destination number 3. From the trunk configuration, a translation rule is applied for the calling number Lync User Front-End Server MS Trunk Gateway PSTN

19 New, Get, Set,and Remove CsOutboundCallingNumberTranslationRule cmdlets

20

21 Managed Unmanaged Management Managed by an administrator or a manager Managed only by an administrator Delegation Sharing Managed by an administrator or the response group manager Cannot share the response group queues or agent groups with any other response group Delegation not supported Can share queues and agent groups with other unmanaged response groups Visibility Visible to the response group manager Visible to the administrator Not visible to other managers Visible only to the administrator Not visible to any manager Administrator(s) Manager 1 Manager 2 Workflow Workflow Workflow Workflow Managed Manager 1 Managed Manager 2 Unmanaged Unmanaged Queue Queue Queue Queue Queue Agent Group Agent Group Agent Group Agent Group Agent Group

22 New Managed and ManagersByUri properties in CsRgsWorkflow

23