Administering Avaya Aura Presence Services 6.0

Transcription

1 Administering Avaya Aura Presence Services 6.0 Issue 1 August 2010

2 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Websites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Website: Please note that if you acquired the product from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by the said Avaya reseller and not by Avaya. Licenses The software license terms available on the Avaya Website, are applicable to anyone who downloads, uses and/or installs Avaya software, purchased from Avaya Inc., any Avaya affiliate, or an authorized Avaya reseller (as applicable) under a commercial agreement with Avaya or an authorized Avaya reseller. Unless otherwise agreed to by Avaya in writing, Avaya does not extend this license if the software was obtained from anyone other than Avaya, an Avaya affiliate or an Avaya authorized reseller, and Avaya reserves the right to take legal action against you and anyone else using or selling the software without a license. By installing, downloading or using the software, or authorizing others to do so, you, on behalf of yourself and the entity for whom you are installing, downloading or using the software (hereinafter referred to interchangeably as you and end user ), agree to these terms and conditions and create a binding contract between you and Avaya Inc. Or the applicable Avaya affiliate ( Avaya ). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS): End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Administering Avaya Aura Presence Services 6.0 2

3 Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU): End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Named User License (NU): End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a Named User may be, without limitation, designated by name, corporate function (for example, webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR): Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). (See Thirdparty Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil, offense under the applicable law. Third Party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Website: Preventing toll fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Website: Administering Avaya Aura Presence Services 6.0 3

4 Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail Trademarks Avaya and Avaya Aura are registered trademarks of Avaya Inc. The trademarks, logos and service marks ( Marks ) displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. All non-avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Website: Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Website: Administering Avaya Aura Presence Services 6.0 4

5 Contents Chapter 1: Introduction to Presence Services... 9 Overview... 9 Components of the Presence Services system External entities Other Avaya applications Configuration Views Areas on the Controller s Main Page The System Area Chapter 2: Integrating Presence Services with Session Manager Adding Session Manager to Presence Services Adding Presence Services as a SIP entity in System Manager Adding an Entity Link Enabling Avaya SIP Client(s) support Enabling required modules in Presence Session Manager Configuring the Authorization Manager on the Presence Server Adding and configuring Resource Lists Configuring Authorization ACLs on System Manager Adding other presentities to a user s resource list Chapter 3: Administering System Manager for Presence Services System Manager and Presence Services Viewing the details of the Presence Services server on System Manager Viewing the status of the Presence Services server on System Manager Presence configuration properties Administering Presence configuration properties Domain Substitution Rule Classes Presence classes Viewing Presence classes Creating Presence classes Modifying Presence classes Deleting Presence classes Access Levels Presence access levels Defining rules Filtering Soliciting confirmation Configuring Presence Access Levels in System Manager Customizing Access Levels Viewing Presence access levels Creating Presence access levels Administering Avaya Aura Presence Services 6.0 5

6 Modifying Presence access levels Deleting Presence access levels Presence access level field descriptions Adding, removing Presence classes to access level Configuring Users in System Manager Viewing Alarms and Logs Logs Configuring dynamic logging Alarms Monit Licensing Checking your Presence Services license status Renewing your Presence Services license PS Admin status check...36 Chapter 4: Configuring Presence Services components Adding and Removing Presence components Configuring Presence Components SIP Proxy Parameter Reference SIP Bulk Subscription Server Configuration...48 SIP Presence Server Parameter Reference Authorization Manager Resource List Management Service (RLMS) Configuration Reference AES Collector Prerequisites Configuring a Communication Manager in System Manager Configuring AES in System Manager AES Collector Configuration Reference The RTC Collector Prerequisites Adding a new RTC Collector Configuring the RTC Collector Configuring the SIP Proxy Configuring the SIP Proxy Transport Prerequiistes Configuring SIP Proxy Remote Host Configuring SIP Proxy Routing Rules Microsoft-side Integration with OCS Gateway Pre-Installation Instructions Launch Microsoft Management Console (MMC) Checking the certificate used by External Interface on MS Edge Server Generate a Certificate with Server and Client Authentication Generate a certificate for OCS Gateway to communicate with MS Edge Server Add Presence Services Server CA certificate to MS Edge Server Trusted Root Certificates Add OCS Gateway as an IM service provider Add a DNS SRV record for the OCS Gateway Testing DNS records from Microsoft Edge Server Restart the MS Edge Server service after completing changes to DNS Presence Services Server side Integration with Microsoft OCS Administering Avaya Aura Presence Services 6.0 6

7 Download the CA which signed the certificate for the External Interface of the Edge server Add CA for MS Edge server to PS trusted list...84 Restart Presence Services Component Verifying the configuration status RTC Collector Configuration Reference SES Collector Configuration Reference Sametime Component Configuration Reference Presence Sametime Distributor and Collector Presence Model Presence Model Component Configuration IM Transcripts Web Service Configuration Reference Configuring Connection Managers Configuring the Basic Connection Manager Connection Manager Parameter Reference Configuring Client Connections Configuring XMPP Connections Configuring HTTP Binding Connections Configure the HTTP Binding Director Configure a Web Command Processor Configuring Polling Connections Server-to-Server Connections Configuring the Basic S2S Connection Manager Configuring an OpenPort Connection OpenPort Configuration Configuring an OpenPort Configuring the Dialback Password Blacklisting and Whitelisting Hosts and IP Addresses S2S Command Processor Parameter Reference Discovery Protocol for Querying the S2S Command Processor Chapter 5: Logging Configuration Changing default logging level Enabling logging for specific components: Chapter 6: Maintenance Operations Presence Commands Quick Reference Backup Restore Update prescert tool swversion.sh tool Get PS Logs Command Changing the IP address of the Presence Services server after installation Update Log Level tool Generate Test Alarm Command Command line tool im_manager Chapter 7: Load Balancing Administering Avaya Aura Presence Services 6.0 7

8 Scalability within a Presence Services server instance Adding and configuring additional SIP Presence Server components for load balancing Specifying the new SIP Presence Server components as Presence Administrators Scalability using multiple Presence Services instances Adding an SDNS component Configuring a Presence Container component Adding and configuring the Presence Server jsm components Setting up the router to router connections Adding sip bulk subscription components from the cluster to each JSM Presence Administrators list configuration Appendix - A Appendix B Communications Address Terminology Network Login Configuring Users Adding Contacts Presence and Instant Messaging Appendix C Adding a new aggregator on SIP Enablement Services Deleting an aggregator on SIP Enablement Services Administering Avaya Aura Presence Services 6.0 8

9 Chapter 1: Introduction to Presence Services Note: This guide contains the features and enhancements made to the XCP Controller for Presence Services 6.0. For all basic administration and configuration of the tools in the XCP Controller, refer to the Presence Services XCP Controller administration guide on the support site. Overview Presence is information that conveys a person's ability and willingness to communicate across a set of services, such as telephony and instant messaging. A person's presence is characterized by states like "busy and "away". These states impact the individual's ability and availability to communicate with other users. Presentity is the overall presence information for a person whose presence is being reported. Watcher is a user who is interested in a presentity. A watcher who is interested in receiving presence updates for a given presentity must subscribe to that presentity for presence updates. Avaya Aura Presence Services is a single point of presence collection. It supports presence information gathering from a diverse range of sources. This information is aggregated on a per user basis, and then made available to presence aware applications. Applications interested in a user's presence must first subscribe to receive presence information. Presence aware applications may use the Local Presence Service (LPS) to subscribe to Presence Services. In doing so, they will receive presence change notifications containing aggregated presence for a user and the communication resources that the user has available to them. LPS runs co-resident on the application server. This information can be used to provide visual indications about a users presence to an end user client Graphical User Interface (GUI). Presence Services uses LPS to efficiently transfer presence information between the Presence Services server and the application servers. Presence Services uses presentities and watchers to do this. Presence Services facilitates the secure exchange of telephony availability and instant messaging (IM) information between applications. In the business world, the exchange of presence information allows users to locate other users in a workplace, know when to contact helpdesk executives to address customer inquiries, help customers services to troubleshoot problems in real time. Avaya Aura Presence Services provides a presence aggregation service that collects and distributes presence information from Avaya and to Avaya tools and also third party sources. It aggregates presence information from a wide variety of Avaya endpoints, including the one-xtm family of clients. Avaya Aura Presence Services also supports the XMPP instant messaging protocol. By using a set of collectors, Avaya Presence Services serves as a conduit between endusers allowing them to use the Presence Services core presence capabilities with these other presence sources. Administering Avaya Aura Presence Services 6.0 9

10 Avaya Presence Services works with client software from Microsoft, IBM Lotus and open source. You can see on-the-phone status on several phones and Internet messaging status in the Microsoft Office Communicator, and other Internet Messaging applications. Some of the main ones are: The AES Collector allows Presence Services to report telephony Presence from Communication Manager endpoints. The collector collects presence from H323 and DCP telephones and SIP telephones administered as OPTIM extensions. The SES Collector allows Presence Services to report telephony presence from SIP terminals connected to SES servers. Note that you do not require the SES collector if the solution deployment includes Avaya Aura Session Manager. The RTC Collector allows Presence Services the ability to report basic presence from Microsoft Office Communicator clients. The Sametime Collector allows Presence Services to collect and distribute the presence information of Sametime clients from and to IBM Sametime servers. The XMPP Collector allows Presence Services to collect and aggregate presence information from XMPP Clients based on federated foreign XMPP servers. Some of the key features of Presence Services: The Presence Model which uses a set of complex rules engaged in an algorithm to arrive at an aggregated presence for a user. Avaya Aura Presence Services ability to support several protocols - SIP/SIMPLE and XMPP protocols to name a few, enabling it to aggregate and federate presence with most major IM and messaging solutions as well as a number of user productivity tools. The architectural design improves on network traffic management. Using serverto-server updates, it is able to efficiently collect and publish presence information effectively, reducing traffic on the network. Components of the Presence Services system Presence Services performs the administration, life-cycle management, and configuration management of these subsystems. Note: Presence Services 6.0 has the ability to support and integrate with multiple presence sources such as Microsoft Office Communicator clients on Microsoft OCS, Sametime IM Clients on IBM Sametime Server, and XMPP clients on XMPP server. The integration and support for these presence sources will depend on the overall solution capability in which you deploy Presence Services. At the time of publication of Presence Serviced 6.0, Avaya one-x Communicator 6.0 does not support any external presence sources. Administering Avaya Aura Presence Services

11 The Presence Services Core extensible Communication Platform (XCP) server. Maintains a list of presence fragments for a given presentity and performs composition of these fragments. The Core XCP is the conduit between the collectors and distributors of presence information in the system. The SIP Bulk Subscription Server: Supports bulk distribution of presence so that the transfer of presence information between Presence Services and LPS is efficient. The SIP Presence Server. Supports SIP-based clients who need to subscribe to and publish presence. LPS uses SIP Presence Server to publish presence. The Presence Server. Collects presence information from various sources, such as Application Enablement Services (AES), Microsoft Office Communicator Server (OCS), IBM Lotus Sametime Server, extensible Messaging and Presence Protocol (XMPP) Server for presentities retrieved from the User Data Store and distributes presence of a given class, such as Phone, Enterprise IM. One-X Communicator to Sametime users. The OCS Gateway. Provides federation capability between the Presence Server and an OCS server, to enable peer-to-peer presence and IM between clients connected to Presence Server and Microsoft Office Communicator. External entities The Presence Services server may interact with the following external entities. Application Servers hosting presence-aware applications. In this case, Presence Services provides an LPS that runs co-resident on the application server. The LPS maintains local subscriptions, performs access control, and exchanges data with the regional/central Presence Services server using the SIP Server-to- Server (S2S) protocol. Applications using the LPS may be requesting presence information (subscribe/notify) from Presence Services or may be providing presence information (publish) to Presence Services for aggregation. Presence Sources. There are a variety of other presence sources from which Presence Services can collect presence information. Communication Manager (through AES) for Avaya telephony devices Microsoft-RTC (OCS) for Microsoft presence XMPP Server for XMPP presence SIP Enablement Server (SES) for presence of endpoints connected to SES IBM Sametime Server (IST) for presence of endpoints connected to IBM Sametime Servers Administering Avaya Aura Presence Services

12 System Manager-User Management Services. There is sizable user data that Presence Services and Avaya Applications must share in order to provide a unified view of a specific user within the enterprise. This data includes the user identities within various presence domains, such as enterprise handle, Avaya Aura Communication Manager extension, and Microsoft-RTC. In addition the user has access control lists that must be shared among various applications and Presence Services components, such as Presence Services server and Presence Services LPS. Presence Services relies on Avaya Aura System Manager to provide all the user data instead of implementing its own User Management administration infrastructure. Presence Services uses Database Replication to retrieve data from a centralized management service and get change notifications. This Overview diagram shows the inflow from all the components that work with Presence Services. Some of the components may interact independently with each other (without involving Presence Services) but those interactions are not depicted in the diagram. Other Avaya applications For the successful operation of Presence Services, you must install a number of other Administering Avaya Aura Presence Services

13 Avaya applications. These applications are compatible with the Avaya Aura framework. Note: It is important to install the correct version of each component. Avaya Aura System Platform 6.0 (optional...) Avaya Aura System Manager 6.0 Avaya Aura Session Manager 6.0 (optional...) Avaya Aura Application Enablement Services or later (optional...) SIP Enablement Services (optional ) Configuration Views The XCP controller offers three levels of configuration, called Configuration views: Basic, Intermediate, and Advanced. The Configuration view menu is located in the top right corner of every controller configuration page. When you select a particular view, it remains in effect on all pages until you change it. The "Basic" configuration view displays the fewest configuration options and primarily uses the server s default values. Configuring your system using this view is sufficient for most server components, and enables you to get your XCP system up and running in the shortest amount of time. The "Intermediate" configuration view displays all of the options that are available in the "Basic" view in addition to some other options, such as those used for host name and command configurations, and for logging. It also includes many of the options for components that are installed with the XCP extras installation package. The components whose configurations require you to use at least the "Intermediate" view include: Message Archiver The "Advanced" configuration view displays all of the options that are contained in the "Basic" and "Intermediate" views in addition to a number of fine-tuning options such as buffer size, run level, and thread count. These options require a more advanced level of XCP server knowledge, and you can use them to adjust the performance of your XCP system. The components whose configurations require you to use the "Advanced" configuration view include: Single Domain Name Support (SDNS) Router-to-Router Connection Areas on the Controller s Main Page The System, Router, and Components areas on the Controller s main page are described in the following sections. Administering Avaya Aura Presence Services

14 The System Area The links in the System area perform the following functions: Summary - Displays the complete jabber.xml file, which contains your configuration settings. Note: If you have modified the configuration of a plugin or component, you must restart the system before the changes take effect and before they display in the Summary. Cluster - Displays a page from which you can access all of the controller s in this cluster. Stop the System - Stops the XCP server and all of its plug-ins and components. Window Help - Displays a help topic for the controller s main page. Full Help System - Opens the controller s complete online help system, which is the online version of this document (Administering Avaya Aura Presence Services) When you stop the system, the XCP Controller page is displayed. From the XCP Controller page, you can: Click start the system now to restart the server. Click view all of the controller s to display the page from which you can access all of the controller s in the current cluster. Administering Avaya Aura Presence Services

15 Chapter 2: Integrating Presence Services with Session Manager Session Manager performs SIP routing and other session processing functions of an Avaya Aura SIP network. It routes SIP (subscribe, publish) requests from Avaya SIP Clients to Presence Services. This routing is based on a SIP request URI containing the IP address (or FQDN) of Presence Services Server(s). Adding Session Manager to Presence Services At the time of installation, you should have added the Asset IP address in the Session Manager Configuration Setting panel for Presence Services to integrate with Session Manager. If you did not enter the Asset IP address then, you can enter it after the Presence Services installation. 1. Log in to Presence Services. 2. Click Edit against the Core Router (Global Router Settings). 3. Scroll down to Mutually Trusted Hostnames and enter the Session Manager server(s) host name. 4. Click Submit. Adding Presence Services as a SIP entity in System Manager 1. Log in to System Manager. 2. Go to Routing > SIP Entities > New 3. Enter the following details: a. Name: Example, PresenceServer b. FQDN or IP Address: PS IP address c. Type: Other d. SIP Link Monitoring: Use Session Manager Configuration 4. Click Commit. Refer to the System Manager documentation for more information. Administering Avaya Aura Presence Services

16 Adding an Entity Link 1. Log in to System Manager. 2. Go to Entity Links > New 3. Enter the following details: a. Name: Link name (Example: PresenceServerLink ) b. SIP Element 1: Select Session Manager from the list c. Protocol: TLS d. Port: 5061 e. SIP Element 2: choose the same PS name you created in the previous procedure (Example: PresenceServer ) f. Port: Select Trusted. 5. Click Commit. Refer to the System Manager documentation for more information. Enabling Avaya SIP Client(s) support For Avaya SIP clients such as Avaya one-x Communicator 6.0 to be able to receive presence information updates, you require the Presence Services SIP-Client support. This support extends the use of open IETF standards based on RFC 2543, 3265, 3903, 3857 and open IETF standards from the family of documents collectively known as SIP SIMPLE The SIP Client Support function utilises several modules. mod_simple to perform SIP SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) functionality. SIMPLE is an open standard based on RFCs that describe the integration of SIP (RFC 3261) with the Instant messaging and Presence (IMP) standards. mod_idmap to allow SIP based clients to publish and subscribe for presence information applying identification of SIP identifiers to internal JID representation using ID Mapping. ID Mapping maps any SIP URI handle registered with System Manager to a single presentity maps any Presence Server presentity to its Primary SIP URI includes support for mapping just the user (number) portion of E.164 handles to appropriate presentity is required for any SIP Presence Subscriptions where the SIP URI lies outside the Presence Server Domain uses Resource list and winfo subscriptions to map the presentity to the most appropriate handle URI provisioned in System Manager mod_authz to allow ACL based Authorization via Authorization Management It allows subscription to a lists of contacts via Resource lists. Administering Avaya Aura Presence Services

17 Authorization allows you to use Access Control Lists (ACL) set up in System Manager (SMGR) to make Authorization decisions. ALLOW and BLOCK are SIP Subscribe requests. They can be used to solicit explicit intervention from the requested presentity to ALLOW or BLOCK a SIP subscription. This is the case when with the SPARK phone a winfo based pop-up requires the presentity to ALLOW/DENY a watcher The flow of information between these tools and the other components in Presence Session Manager is as shown below: SIP client A subscribes to SIP Client B The SIP Proxy receives SIP client A s subscription and passes it on to the SIP Presence Services. The SIP Presence Services asks ID Mapping for the internal JID representation of both SIP clients URI. The SIP Presence Services uses these JIDS to request an internal temporary subscription between users from the Presence Server core. The Presence Server core requests an Authorization from the Authorization Manager. The Authorization Manager uses System Manager ACLs on the local database to determine the result of whether the subscription is allowed or denied Enabling required modules in Presence Session Manager 1. Log in to Presence Services. 2. Click Edit against the Presence Session Manager. 3. Under Optional Modules select: mod_idmap mod_authz mod_simple mod_winfo mod_pep 4. Scroll down to Module Configuration to select and set SIP URI Mapping Configuration to Yes. 5. Click Submit to save your choices. 6. Go back to the home page to see if the Authz component, the IdMapper component have been added to the Components page. 7. Click Edit against the SIP Presence Server under Components to open the SIP Presence Service Configuration page. 8. Scroll down to set Enable ID Mapping to Yes. 9. Click Submit to save your changes. Administering Avaya Aura Presence Services

18 Configuring the Authorization Manager on the Presence Server 1. Log in to the Presence Services web interface as an administrator. 2. Click Edit against the Core Router Settings on the Router section to open the Global Settings Configuration page. 3. Scroll down to SIP Gateway Domains to add the domain names of the Microsoft Office Communicator (MOC) clients you want to connect to. 4. Return to the home page. 5. Click Edit against Presence Session Manager in the Router section. 6. Scroll down to the Authorization Configuration section. 7. Fill in the following fields: JID matching rules bare Query local in Include original stanza in request yes Default handling Default behavior pass Default permission force Force the use of default values for all requests No Click Help for information on each of these fields 8. Go to Exceptions to default handling > Add a new Stanza Exception 9. Click Details and ensure that the filter matches the Presence filter. 10. Click Submit. Adding and configuring Resource Lists 1. Log in to the Presence Services web interface as an administrator. 2. Go to Components > Add a new OpenPort. 3. Enter an ID to open the configuration page for example, rlms 4. Scroll down to Hostnames for this component. 5. Enter the host filters. Hostname filters must match listmanager.<ps domain> where <PS domain> is the domain of the Presence Services. For example, pres.example.com. 6. Go down to OpenPort Configuration and ensure that it reads: <op:config xmlns:op=" 7. Click Submit 8. Go to Components > Add a new Resource List Management Service. 9. Click Go to open the configuration page. 10. Scroll down to Connection to PS Core Configuration. 11. Enter the correct values in the following fields: Component Name PS Realm Name PS Host IP address PS Host port PS connection password. Click Help for information on each of these fields Administering Avaya Aura Presence Services

19 12. Click Submit. 13. Go back to the home page. 14. Click Edit under the SIP Presence server under Components to open the SIP Presence Server Configuration page. 15. Under the section SIP Presence Server Configuration set the send immediate 202 pending for Subscribed requests? field to yes. 16. Click Submit. Configuring Authorization ACLs on System Manager 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Go to Users > System Presence ACLs 3. Set the default policy. Policies can be defined system wide or on an individual presentity/watcher basis. If you set it to "Allow" any SIP subscriptions will succeed as long as there is no explicit higher priority ACL for the watcher, presentity pair blocking access. If you set it to "Block" then the reverse becomes true. If you set it to "Confirm" then the client will have to explicitly choose to use "Allow" or "Block" for each subscription. Refer to the System Manager documentation for more information. Adding other presentities to a user s resource list You can add presentities using the Avaya SIP devices like One-X Communicator. However, you can also add them in System Manager, if required. 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Go to Users > Manage Users. 3. Select the relevant user. 4. Click Edit to open the User Profile Edit page. 5. Click the default contact list and click Add under Associated Contacts to add a new presentity to the Resource list when the sub-menu appears. 6. Select the presentity to add and click Select. 7. Click Commit on the User Profile Edit page to save your changes. Refer to the System Manager documentation for more information. Administering Avaya Aura Presence Services

20 Chapter 3: Administering System Manager for Presence Services The presence administration pages of Avaya Aura System Manager allow the administrator to manage: System Manager and Presence Services Viewing the details of the Presence Services server on System Manager Viewing the status of Presence Services server on System Manager Presence configuration properties Presence classes Presence access levels System Manager and Presence Services By default, when you install Presence Services, PS automatically registers itself to System Manager. The Presence Services installation script makes System Manager aware of the Presence Services hostname and the Presence Services ports required for System Manager monitoring. This registration is an automatic process and so unlike some other Avaya Aura products, you do not have to manually add the new Presence Services server to the System Manager inventory. If you require changes to the Presence Services host name, Avaya recommends reinstalling the Presence Services instance rather than editing the Presence Services host name details on System Manager. For this reason, the editing steps are not included here. The creation of the Presence Services instance on System Manager is automatic. For this reason, the steps required for adding a server are not included here. Using the System Manager Web GUI, you can view the details of the Presence Services server on System Manager. You can also view the status of the Presence Services server on System Manager. Viewing the details of the Presence Services server on System Manager 1. Log in to System Manager by entering the System Manager virtual machine IP address in a Web browser, as follows: System Manager IP address>/smgr 2. Navigate to Elements > Inventory > Manage Elements. 3. Select an instance of Presence Services by clicking the associated check box and click View to view the details of the Presence Services server. Administering Avaya Aura Presence Services

21 o o o On the View screen, in the Application area, you can view the server name, host name, and an optional description. In the Port area, you can view any configured ports. In a default installation, no ports are required. In the Access Point area, you can view the access points, which are the ports that System Manager uses to access Presence Services. By default, System Manager displays two access points for each new Presence Services server. One of the access points defines the port that System Manager uses to view the status of Presence Services components. The other access point defines the port that System Manager uses to launch the XCP Web Controller, which is also known as the Presence Services Web GUI for administrators. Viewing the status of the Presence Services server on System Manager 1. Log in to System Manager by entering the System Manager virtual machine IP address in a Web browser, as follows: System Manager IP address>/smgr 2. Navigate to Elements > Inventory > Manage Elements. 3. Click the name of the Presence Services instance. 4. On the Presence System Information screen, you can view the name, host name, and an optional description. 5. Click Open to launch the Presence Services Web GUI, which is also known as the XCP Controller. 6. Click Show to display the status of the Presence Services components in a Presence System Status area at the bottom of the page. The Presence System Status area displays the Presence Services components as a list of folders, which you can expand to view more detail. Administering Avaya Aura Presence Services

22 Presence configuration properties Administering Presence configuration properties 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Configuration in the left navigation pane. You can review all global presence configuration properties on this page. Next steps: Modifying a configuration property: 1. Click Edit. 2. Change the value of the property. 3. Click Save. Related topics: Domain substitution rule Domain Substitution Rule System Manager has a domain substitution rule backed by string substitution. Presence Services uses this rule to convert a user's ID in System Manager to a valid ID in Presence Services. The conversion happens as explained in the example here: For example, if you have a user Jane Doe working for a company "example" then her user log-in could be janedoe@example.com in System Manager. Jane Doe's company domain: example.com Jane Doe's user login in System Manager: janedoe@example.com In the Presence Services domain (ROUTER_SERVICE_NAME) Jane Doe s domain would change to: presence.example.com Jane Doe s ID in Presence Services will be: janedoe@presence.example.com Setting the domain substitution rule 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Navigate to Elements > Presence > Configuration and set the values as: Domain Substitution Domain Substitution Domain Substitution Default (blank) Note: Notice that there is a dot after the word, presence. Administering Avaya Aura Presence Services

23 Classes Presence classes Presence classes are essentially types of presence information sources. For example, all presence updates from desktop phones are assigned to class Phone, all presence updates from enterprise IM (Instant Messaging) clients are assigned to class Enterprise IM, and so on. The presence classes, once defined, can then be used to define presence access control rules, presence aggregation rules, and so on. Normally, the system comes with a pre-configured set of supported presence classes. However, as new devices are integrated, it might be necessary to add new presence classes. Viewing Presence classes 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Classes in the left navigation pane. The page displays all currently defined presence classes. Creating Presence classes 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Classes in the left navigation pane. 3. Click Add. 4. Fill in the name of the new class. 5. Click Save. Modifying Presence classes 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Classes in the left navigation pane. 3. Select a row with the class that you want to modify. 4. Click Edit. 5. Change the name of the class. 6. Click Save. Deleting Presence classes 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Classes in the left navigation pane. 3. Select a row with the class that you want to delete. 4. Click Delete. Administering Avaya Aura Presence Services

24 Access Levels Presence access levels Presence access levels are defined in terms of presence classes. An access level can contain a single presence class or a set of classes. Access rules defined in the Presence ACLs (Access Control Lists) then apply to all classes in an access level. Presence information is partitioned into several areas called presence access levels for the purpose of access control. Examples of presence access levels: Instant Messaging Presence Telephony All The All access level is always defined and always includes complete Presence information. Other access levels can be created by administrators as necessary. An access level can also contain an inversion of a set of classes for convenience. In other words, it can be defined to contain all classes that are not in the selected set of classes. This makes it easier to define access levels such as all classes except Phone. Defining rules If you define a specific rule to an ACL then that takes precedence over a generic rule. For example, in the same ACL, levels including just 1 class have precedence over multiple class levels which in turn have precedence over the level All. The ACLs in each band are arranged in such a way that ACL applicable to single watcher/presentity pair (more specific) take precedence over more generic ACLs applicable to all watchers (or all presentities) and also ones applicable to all pairs. Filtering Presence information is filtered, so each watcher can see only part of presence it is allowed to see. Both the presence owner and system administrator can control the level of presence allowed to the watcher. Presence filtering is done with granularity of tuple. The filtering is based on the value of the class element. The person element of presence is not affected by filtering. Soliciting confirmation You can create an ACL, apply the levels and then solicit confirmation from the user. If you have set the ACL to CONFIRM. then the system sets the ACL level to Pending till it receives confirmation from the presence owner (presentity) when online the next time. That allows presentity to decide to set this level to Allow or Block or any other level of access for the watcher (using LPS). If you do not set the Confirm level the system will work with no user interaction. Note: Only System Wide ACL can be managed by the System Manager console. There is no Web console to manage User ACL. It is the responsibility of PS client(s) to manage user ACL. Administering Avaya Aura Presence Services

25 Configuring Presence Access Levels in System Manager System Manager offers basic access levels grouped into default ACLs. They allow you to set filtering to Allow, Block, Confirm, Undefined or Pending states. Each ACL may have multiple level definitions. The list of default ACLS are as follows and in the order of priority: System ACL for each watcher, always HIGH priority System Rule (High/Low) all watchers and all presentities System Default all watchers and all presentities, the lowest precedence User ACL for each watcher/presentity pair (controlled by User) User Default for each presentity (controlled by User) Enforced User ACL (High/Low) for each watcher/presentity pair The last one gives the administrator fine-grained control over the level of presence available for the watcher Customizing Access Levels 1. Log in to Avaya Aura System Manager web interface as an administrator. 2. Go to Users > System Presence ACLs 3. Click New under the section High Priority Enforced ACL to define a new access between a presentity and a watcher. 4. Click New under the section System ACL to assign a user the permission to view everyone s presence 5. Click New under Default Policy to define default access to all users. Refer to the System Manager documentation for more information. Viewing Presence access levels 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Access Levels in the left navigation pane. The page displays all currently defined presence access levels. Refer to the System Manager documentation for more information. Creating Presence access levels 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Access Levels in the left navigation pane. 3. Click Add. 4. Fill in details of the new access level. 5. Click Save. Refer to the System Manager documentation for more information. Administering Avaya Aura Presence Services

26 Modifying Presence access levels 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Access Levels in the left navigation pane. 3. Select a row with the access level that you want to modify. 4. Click Edit. 5. Change details of the access level. 6. Click Save. Note: The System Manager Access level All is predefined and cannot be modified or deleted. Refer to the System Manager documentation for more information. Deleting Presence access levels 1. Log in to the Avaya Aura System Manager web interface as an administrator. 2. Click Elements > Presence > Access Levels in the left navigation pane. 3. Select a row with the access level that you want to delete. 4. Click Delete. Note: Access level All is predefined and cannot be modified or deleted. Refer to the System Manager documentation for more information. Presence access level field descriptions The following fields are defined for a presence access level. Name Label Unique name of the access level. Classes A set of presence classes that are included in this access level. Adding, removing Presence classes to access level To add presence classes to the access level: 1. Select the new classes in the Available Classes list. 2. Click [>] to include them in the Selected Classes list. Refer to the System Manager documentation for more information. Next steps To remove presence classes from the access level: 1. Select the classes in the Selected Classes list. 2. Click [<] to remove them. Administering Avaya Aura Presence Services