Avaya and Microsoft Integration Options Luke Kannel, Director of Operations - ConvergeOne © Copyright 2015. Private and confidential.

What’s Available? Many Options – Changing with “Cloud” and “Clients” Click to call with an Existing Avaya handset Remote Call Control Avaya Communicator for Microsoft Lync Call via Work Avaya/Skype for Business Voice and Conferencing Services Session Manager TDM Gateway SBC Cloud Connector Edition © Copyright 2015. Private and confidential.

Click to Call (With Avaya Handset)

Click to call comparisons Avaya Voice Avaya Communicator for Microsoft Lync 6.4 Leverages existing telephony infrastructure (no additional QoS, network capacity, or hand/headsets needed) SIP or H323 Options By default, disables Lync/SfB Voice and Video Works with Skype for Business Online Avaya and Microsoft Voice Call via Work SIP Integrated to Avaya telephony Leverages “dial out” capabilities of Skype for Business Enterprise Voice (MSFT PBX) is selectable by end user 2 “side by side” PBXs © Copyright 2015. Private and confidential.

Avaya Communicator for Microsoft Lync 2010/13/SfB* Enhances Lync user experience Click-to-call, telephony/video presence, multi-call handling Escalate from IM to voice to video call Mid-call Control (Release, Hold and Retrieve, DTMF, Transfer and Conference, Handoff and Dial Pad Dialling) Simultaneous ringing (Extensions, Devices, Clients) Lync Skype for Business sign-in Client-side integration Uses Lync Client SDK No Lync /SfB voice licenses or devices Multi-platform support On-premise & Office 365 options Avaya Aura®, CS 1000 / Aura, IPO Extending the stack Click-to-call from Office, Outlook, SharePoint, Internet Explorer, Firefox and Chrome VDI Experience with Communicator for Lync Virtual machines in the data center running client Desk Phone or VDI Communicator: Media presented locally With Avaya Communicator for Microsoft Lync 6.4 we have an integration into Lync that preserves the Lync IM and presence user experience. We are dealing with customers who have decided from a Microsoft perspective that they want Lync on the desktop. The user performs their normal Lync sign-in. With the integration Avaya brings click to call, Telephony and video presence and multi-call handling. We are offering a choice of calling modes including: desk phone were you control calling through your desk phone through Lync, computer mode (VOIP) were a call control and media is through your computer and other phone mode where you control a call through you mobile device or CS 1000 desk phone through the Lync integration interface. You can escalate from IM to an Avaya voice or video call. And you have mid-call controls such as release, hold and Retrieve, DTMF, Extend Call and Transfer and Conference. Please note that with SIP deployments, video is only supported for AC for Lync when in computer mode. There is a simple client side install of an add-in for Lync. From a Microsoft perspective the integration requires a minimum of Microsoft standard CAL licensing which supports Microsoft IM and presence capabilities. The integration utilizes Lync application program interfaces (APIs) through Microsoft's client solution development kit (SDK). There is multi-platform support for deployment. Lync integration can deployed in the enterprise on-premise or into a Microsoft cloud environment with Office 365. AC for Lync is a client side deployment to the desktop and does not require specialized Microsoft server integration. There is support for Avaya Aura® and CS 1000 when deployed with Avaya Aura®. CS1000/ACE deployments end with ACA for Lync 6.3 and won’t be carried forward into 6.4 As we have just mentioned, Collaboration Services provides click to call from Office, Outlook, SharePoint, Internet Explorer and Google Chrome. *SfB = Skype for Business 2015/2016 5

Local Call History Supports Passed from Aura to Outlook Incoming Calls Outgoing Calls Missed Calls Passed from Aura to Outlook Conversation History Inbox (Missed Calls) Accessible from Outlook Lync Conversations Contact Card provides details of call activity Start time & Duration Call History is gathered as long as the Communicator for Lync client is logged into Aura.

Avaya Communicator for Microsoft Lync Click to Call From: Lync/SfB client, Internet Explorer (requires plug-in) & Microsoft Outlook (requires plug-in) H.323 TDM / Analog

Multiple Device Access (MDA) and Dual Registration MDA allows up to 10 SIP devices registered simultaneously to a single Extension One physical device only can be a controlled by AC for Lync Dual Registration allows for AC for Lync (H323) and a SIP client to registered simultaneously Both support Join Call functionality

Join Call (MDA and Dual Registration) All Users devices Ring User see toast pop up on PC User Answers on Mobile Phone On PC User see conversation window with Tag “Remote call in progress” User Clicks on Phone Icon to extend call to AC for Lync User can end call on mobile and continue on Desk phone

ACML Mid Call Control features Call Transfer: 1st call established Call 2nd party Select Transfer icon Select original established call (#1) Avaya Conferencing: Establish 1st call Call 2nd party Select Conference icon Select original established call (#1)

Call via Work Enterprise Voice for PBX Users User experience Features Skype for Business users can make voice calls using any PSTN phone, including existing PBX endpoints Leverages existing Direct SIP connectivity between PBX systems and Lync/Skype for Business User experience Skype for Business dials out to PSTN or desk phone number to connect user, then connects with far-end destination Features Presence update and call control from Skype for Business client Mid-call control capabilities preserved on PBX phone © Copyright 2015. Private and confidential.

Call via Work – Outbound User instantiates call from Skype for Business rich client Skype for Business client places call to user’s PBX station set (or to any other PSTN phone number) PBX routes call and local user answers When Skype for Business client sees this call answered, places far-end call. Here Skype for Business will use PBX user’s DID as ANI PBX routes call out to PSTN with user’s DID (or to any other local PBX endpoint) Far-end call answers and call is established, with  Skype for Business acting as control channel 1 2 3 4 5 6 PBX PSTN Destination Skype for Business pool Skype for Business client PBX Station Local call Far-end call

Inbound Infrastructure Cloud Call via Work - Inbound 1 2 3 4 5 6 PBX PSTN Destination Skype for Business pool Skype for Business client PBX Station Local call Far-end call Inbound Call via Work has specific requirements for an inbound experience Infrastructure Should operate with any supported PSTN egress May find complexity with numbering support Cloud Not available in SfB Online

Call via Work - Inbound Delivering inbound calls to Skype for Business client and PBX phone Need to consider both calls from PSTN and calls from other Skype for Business users Forward and simultaneous settings are tied with activation of CvW feature If using CvW for outbound, incoming calls automatically forward/simulring to client and configured PBX phone Configured DID # for both user and PBX phone is the same Using ms-skipRnl header for the PBX phone number with the simulring settings for CvW

Call via work - Caveats These Features are NOT available when using call via work: * Call Park via Skype * Transfer via Skype * Hold via Skype * Mute/Unmute via Skype * Record a meeting (no audio) * Response Group Features * Team Call * Boss/Admin Delegation * E911 and Malicious Trace * Call escalation with media * Conferencing (adding additional callers) * Desk Phone Pairing * VDI Plugin

SIP Trunking Integration (Conferencing and Enterprise Voice)

C1 Data Center C1 Data Center Internet Minnetonka Philadelphia Mobile Skype Users Internet Remote Skype Users C1 Data Center Minnetonka C1 Data Center Philadelphia Office 365 (Exchange UM) 50 Sessions 50 Sessions Audio Codes Audio Codes SIP Cloud IM/Presence A/W/V Collaboration Ent. Voice PC/Mobile IPT Users Agent Users CMS Exp. Portal AES Verint 500 Sessions 500 Sessions IPT Users Agent Users CMS Exp. Portal AES IM/Presence A/W/V Collaboration Ent. Voice PC/Mobile MPLS 100MB 100MB Existing G450 w/LSP Existing G4x0 w/LSP POTS POTS Agents Existing G450 w/LSP Existing G450 w/LSP Existing G450 w/LSP Reno 31 Remote Sites 1 PRI 1 PRI 1PRI Agents Agents Bradenton San Leandro Fort Mill

Deploying Skype for Business Voice SIP Integration Options Key Scenarios SfB Server SfB Hybrid Cloud PBX O/P PSTN Cloud PBX w/PSTN DESCRIPTION On-Premises or Hosted SfB Server Split users b/w SfB Server and SfB Online Cloud PBX w/ On-Premises PSTN Cloud PBX w/ Microsoft Provided PSTN Calling CALL MANAGEMENT SFB Server Mix b/w Server and Online (Cloud PBX) SfB Online (Cloud PBX) SfB Online (Cloud PBX) PSTN CALLIN G Connectivity to PSTN Providers Connectivity to PSTN Providers Connectivity to PSTN Providers Cloud PSTN Calling NOTES Full PBX Features Req’d for Skype Meeting Broadcast Missing advanced calling features Express Route Recommended © Copyright 2015. Private and confidential.

CCE (Skype for Business Online Only) Cloud PBX O/P PSTN DESCRIPTION Cloud Connector Edition CALL MANAGEMENT SfB Online (Cloud PBX) PSTN CALLIN G Connectivity to PSTN Providers Missing advanced calling features NOTES ExpressRoute Recommended

https://technet.microsoft.com/en-us/library/mt612869.aspx Cloud Decision Tree – from Technet

Hybrid: PBX Replacement If one of the following applies, deployment will most likely have to implement a hybrid solution (some users in the cloud PBX, but some on the server infrastructure – on-prem or hosted) Additional requirements such as voice recording Analog Devices and Fax Integration with on-premise contact center solutions Integration with on-premise video systems Existing telco contracts with on-premise termination ExpressRoute costs and configuration O365 datacenter (and tenant) locations Client app customization (currently no server API)

Thank you! © Copyright 2015. Private and confidential.