ACCELERATOR 8.0 CISCO UNIFIED PRESENCE INTEGRATION GUIDE

Transcription

1 ACCELERATOR 8.0 CISCO UNIFIED PRESENCE INTEGRATION GUIDE April 2017 Tango Networks, Inc. phone: Network Blvd, Suite 200 fax: Frisco, TX USA

2 Tango Networks, Inc. This software is protected by copyright law and international treaties, and is the confidential and proprietary information of Tango Networks, Inc. Unauthorized reproduction, use, or distribution of this software, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. The software described in this document is furnished under license agreement and may only be used in accordance with the terms of the agreement. Tango Networks and Abrazo are trademarks of Tango Networks, Inc. All other trademarks used herein are the property of their respective owners and are used for identification purposes only Tango Networks, Inc. Tango Networks, Abrazo and E=fmc2 are trademarks or registered trademarks of Tango Networks, Inc. All other trademarks or service marks are the property of their respective owners. Specifications and features are subject to change without notice. April 2017 CONFIDENTIAL Page 2 of 14

3 TABLE OF CONTENTS INTRODUCTION... 4 DEPLOYMENT ARCHITECTURE... 5 PUBLISHING PRESENCE... 6 Mobile Originations... 6 Mobile Terminations... 6 CISCO LICENSE REQUIREMENTS... 7 ACCELERATOR PROVISIONING FOR CISCO PRESENCE... 8 ADD PRESENCE SERVER... 8 SERVICE PROFILE MOBILE UC ENHANCED... 9 ASSOCIATING SUBSCRIBERS WITH AN CISCO UNIFIED PRESENCE SERVER...10 CISCO PROVISIONING REQUIREMENTS UPDATING INCOMING ACL ON CISCO UNIFIED PRESENCE SERVER...11 KNOWN LIMITATIONS April 2017 CONFIDENTIAL Page 3 of 14

4 Introduction The Accelerator extends enterprise PBX and Unified Communications (UC) functionality to mobile devices allowing end users to be more productive and accessible when out of the office. In environments where Cisco Unified Presence Server solution is being used, the Accelerator extends the UC features of the solution out to the mobile device. Currently the Accelerator supports CUPS 7.0. This document covers only the steps necessary to integrate the Accelerator with Cisco Unified Presence Server and is therefore intended for users that already possess in-depth knowledge of Cisco Presence Server products. This document addresses how the Accelerator integrates with Cisco Unified Presence Server Exchange in the following three areas: Deployment Architecture Provisioning Feature interactions April 2017 CONFIDENTIAL Page 4 of 14

5 Deployment Architecture Cisco Unified Presence consists of a SIP presence engine and a SIP proxy function. The presence engine collects user presence information as well as user capabilities and compiles the data in a repository for each user. The Accelerator service adds to this repository presence information about the user when they are on their mobile phone. Initially, this will be on/off the mobile phone presence with future releases including location information. Figure 1 Cisco Unified Presence Server Integration The Accelerator integrates to the Cisco Unified Presence Server (CUPS) via a SIP interface. This is accomplished via the SIP Proxy server that is part of the Cisco Unified Presence Serer The following figure shows the manner in which the Accelerator integrates with the Cisco Unified Presence server Accelerator sends a publish method when new presence information is available concerning the user. This includes the following types of presence states o o User is on the phone User is available The Accelerator uses the Address of Record (AOR) as the identifier in order to publish information into the Cisco Unified Presence Server. April 2017 CONFIDENTIAL Page 5 of 14

6 Publishing Presence The Accelerator publishes two types of presence information On the Phone presence this is triggered by the mobile phone being connected (i.e. answer state) Available presence this is triggered by the mobile being disconnected from an active call. The Accelerator solution publishes presence in the following situations Mobile Originations When an Accelerator subscriber is making a call on their mobile phone, mobile origination policy is applied to the call. The following presence behavior is supported for these various policies: Route Via Enterprise presence will reflect on the phone when a mobile origination call is made with this policy. Route Direct - presence will reflect on the phone when a mobile origination call is made with this policy. Personal presence will not be affected by this type of call. Deny presence will not be affected by this type of call. Mobile Terminations When an Accelerator subscriber is receiving a call on their mobile phone, mobile termination policy is applied to the call. The following presence behavior is supported for these various policies: Route Via Enterprise presence will reflect on the phone when a mobile termination call is received with this policy. Route Direct - presence will reflect on the phone when a mobile termination call is received with this policy. Personal presence will not be affected by this type of call. Deny presence will not be affected by this type of call. Do Not Disturb presence will not be affected by this type of call. April 2017 CONFIDENTIAL Page 6 of 14

7 Cisco License Requirements Cisco Unified Presence Server has a license requirement on the Cisco Unified Call Manager. The Accelerator leverages this license requirement if available. If the Accelerator subscriber has already been enabled with Cisco Unified Presence Capabilities, no additional licenses are needed. If the Accelerator subscriber has not been enabled with Cisco Unified Presence Capabilities, in order to enable this capability, 1 DLU is required for each new subscriber on the Cisco Unified Call Manager. Note: License Name is Cisco Unified Presence Server End User Feature License. April 2017 CONFIDENTIAL Page 7 of 14

8 Accelerator Provisioning for Cisco Presence The following steps are required to add a Cisco Unified Presence Server to the Accelerator. Note that only fields unique to this integration are addressed in this document. For all others please consult the Accelerator Provisioning Guide or online help text. 1. Add Presence Server to Accelerator 2. Ensure Mobile UC Voice Enhanced is enabled in the Service Profile. 3. Associate Tango subscriber to Cisco Unified Presence Server and provide the appropriate User ID (Address of Record). Add Presence Server 1. The Accelerator supports supplying Cisco Unified Presence Server with presence information (available/on the phone presence). If the administrator wants to support presence for a subscriber, the Cisco Unified Presence Servers used by the enterprise must be provisioned before the administrator can assign them to a subscriber. The Accelerator 8.0 release supports the Cisco Presence 7.0 server. To add a presence server, select Voice Network Presence Server Add. Figure 2 Add Presence Server Screen The Add Presence Server screen contains the following fields: Presence Server Name Identifies the Presence server. Maximum length is 45 characters. Presence Server Type Identifies the type of Presence server. Select Cisco Presence. Host Address Host address to use for the Presence server. The host address can either take the form of an IPV4 address or a host address that can be looked up in the DNS servers. May contain any character on April 2017 CONFIDENTIAL Page 8 of 14

9 the keyboard after the first alpha character. Maximum length is 100 characters. Port Port number to use for the Presence server. Valid entries are from URL Parameters Not required for the Cisco Unified Presence Server Transport Type Identifies the transport type used for this presence server. Choices are either UDP or TCP. Service Profile Mobile UC Enhanced 2. Ensure that a Service Profile exists that includes the Mobile UC Voice Enhanced option enabled. You will assign this profile to the subscriber in step 3. For a complete description of all the Profile fields, refer to the Accelerator Provisioning Guide, Services, Profile section. Figure 3 Add Accelerator Subscriber Screen April 2017 CONFIDENTIAL Page 9 of 14

10 Associating Subscribers with an Cisco Unified Presence Server 3. Add a Tango Subscriber and associate the Presence Server created in Step 1. Also provide the SIP address for the subscriber. Figure 4 Add Tango Subscriber Screen The Add Accelerator Subscriber screen has the following fields that pertain to the Cisco Unified Presence Server SIP Address This should be the SIP User ID (i.e. Address of Record) for the Cisco Unified Presence Server (refer to Known Limitation section for more information). Presence Server Subscriber s presence server. This drop down appears depending on the subscriber s profile. April 2017 CONFIDENTIAL Page 10 of 14

11 Cisco Provisioning Requirements The following step is required to interface the Accelerator into the Cisco Unified Communication environment. Identify the Accelerator to the Cisco Unified Presence Server as a trusted source of presence information. This is done by updating the incoming ACL list. Note: If the subscriber that is being provisioned does not already have Cisco Unified Presence service, please follow the Cisco documentation to set the subscriber up for Cisco Unified Presence. This is required for each Accelerator user that wants presence service. Updating Incoming ACL on Cisco Unified Presence Server To add a new ACL on the Cisco Unified Presence Server for the Accelerator, choose System > Security > Incoming ACL and click Add New. Figure 5 Navigating to Incoming ACL April 2017 CONFIDENTIAL Page 11 of 14

12 Select Add New on Incoming ACL screen Figure 6 Add New ACL Selection To add the new ACL, put in the IP address of the Accelerator server (or the host name if one has been assigned). You can save the information by clicking the save button. Figure 7 Identifying New Incoming ACL April 2017 CONFIDENTIAL Page 12 of 14

13 Known Limitations The User ID of the Cisco Unified Presence Server needs to match the SIP URI assigned to the user. This SIP URI corresponds to digest user configured on 3 rd party SIP line associated with the subscriber. Two separate values for the user ID on the Cisco Unified Presence Server and the Cisco Unified Communication Manager are not supported in the 8.0 Accelerator software. April 2017 CONFIDENTIAL Page 13 of 14

14 Tango Networks, Inc Network Blvd, Suite 200 Frisco, TX USA phone: fax: