Avaya Aura Application Server 5300 Overview

Transcription

1 Avaya Aura Application Server 5300 Overview Release 3.0 NN Issue 5.43.AA October 2017

2 , 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 Documentation means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees 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 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 Avaya hardware and software. 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: getgenericdetails?detailid=c under the link Warranty & Product Lifecycle or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. Hosted Service means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK Avaya Terms of Use for Hosted Services OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK AVAYA SOFTWARE LICENSE TERMS (Avaya Products) OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. 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 CHANNEL PARTNER; 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 You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License as set forth below in the Designated System(s) License (DS) section as applicable. 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 You. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. Designated Processor means a single stand-alone computing device. Server means a set of Designated Processors that hosts (physically or virtually) a software application to be accessed by multiple users. Instance means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ( VM ) or similar deployment. License types Named User License (NU). You may: (i) install and use each copy or Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of 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 (e.g., 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. Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment.

3 Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product 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 unless expressly authorized by Avaya. 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. Virtualization The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note, unless otherwise stated, that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya s website at: support.avaya.com/copyright or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms. The following applies only if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. 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 Toll 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: or such successor site as designated by Avaya. Security Vulnerabilities Information about Avaya s security support policies can be found in the Security Policies and Support section of support.avaya.com/security. Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow ( support.avaya.com/css/p8/documents/ ). Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, 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, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel,

4 or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates.

5 Contents Chapter 1: New in this release Features Avaya Media Server integration CAC Integration Custom network domains Destination Code Controls Enhanced Password Policies Enhanced 911 Service with automatic location identification using E911 Manager General Dynamics viper phone Platform servers SIP TLS Identity Checking Release 3.0 upgrades Virtualization Support Document changes since last issue Other changes Chapter 2: Overview Chapter 3: Introduction Session Initiation Protocol IP communication VLAN support Application Server 5300 network Chapter 4: Building blocks Application Server 5300 infrastructure Media servers Gateways Access clients Chapter 5: Network element architecture Chapter 6: Application Server 5300 interworking Interworking with Avaya products Interworking with third-party products Chapter 7: Application Server 5300 hardware Application Server 5300 hardware platforms Minimum baseline configurations Application Server 5300 system capacity Chapter 8: Software Chapter 9: Operations, Administration, Maintenance, and Provisioning strategy User interfaces for network administrators AS 5300 Element Manager Console October 2017 Avaya Aura Application Server 5300 Overview 5

6 Contents Provisioning Client Remote provisioning Switch Expert Description Communication methods Northbound Feed SNMP SFTP Pull Management Chapter 10: Features and services Enhanced 911 service Enhanced 911 Service with automatic location identification using E911 Manager MLPP service Custom network domains Call Tracing External Users Features associated with access clients and devices Assistant Support and Assistant Console Call features Instant Messaging, Presence, and Presence-based routing Multimedia services Sharing features Vertical Service Codes Chapter 11: Interfaces and communication protocols Hypertext Transfer Protocol Hypertext Transfer Protocol over Transport Layer Security Internet Protocol Secure Secure File Transfer Protocol Session Initiation Protocol Simple Network Management Protocol version 2c Simple Object Access Protocol Structured Query Language Transmission Control Protocol/Internet Protocol User Datagram Protocol Other network protocols Application Programming Interfaces Open Provisioning Interface Subscriber Open Provisioning Interface IP addressing IPv4 addressing IPv6 addressing IP addressing support in the Application Server 5300 solution Chapter 12: Configuration and administration October 2017 Avaya Aura Application Server 5300 Overview 6

7 Contents Domains Domain types Services Service profiles and service sets Service nodes Licensing and keycoding Chapter 13: Translations and routing Local termination Call transfer service Telephony routing Call routing features Subscriber Lookup and Routing Hybrid Routing Commercial Cost Avoidance Destination Code Controls Route lists SIP aliases Multiple Route Termination Logical entity Network Message Waiting Indicator Routing Chapter 14: Redundancy, fault tolerance, and failover Fault tolerance definitions Application Server 5300 fault tolerance AS 5300 Element Manager fault tolerance AS 5300 Session Manager fault tolerance Database Manager fault tolerance Accounting Manager fault tolerance Provisioning Manager fault tolerance PRI Gateway fault tolerance High Availability fault tolerance Campus redundancy Layer 2 geographic redundancy Overload control Denial of Service Server backup and recovery Chapter 15: Installation and patching Installation strategy Upgrade strategy Patching strategy Software update delivery methods Software update contents Tools and utilities Chapter 16: Fault management October 2017 Avaya Aura Application Server 5300 Overview 7

8 Contents High-level strategy Maintenance procedures Chapter 17: Configuration management Strategy Tools and utilities Chapter 18: Accounting management Strategy Tools and utilities Chapter 19: Performance management Strategy Tools and utilities Chapter 20: Security, administration, and maintenance Security Security strategy Security measures in Application Server Administration and maintenance Tools and utilities Chapter 21: Application Server 5300 fundamentals Chapter 22: AS 5300 Element Manager fundamentals Description AS 5300 Element Manager interfaces Fault management SNMP information Local storage Performance management Operational measurements Local storage of operational measurements AS 5300 Element Manager security AS 5300 Element Manager Console message of the day AS 5300 Element Manager administration AS5300 Element Manager Console fundamentals Chapter 23: AS 5300 Session Manager fundamentals Description Configuration types MFSS and LSC configuration Services and features CallP Checkpointing support Privacy Control service Service set enforcement Authentication services Instant messaging, IM screening and routing services Route codes October 2017 Avaya Aura Application Server 5300 Overview 8

9 Contents Presence Registration: static and dynamic Logging SIP registration Global Address Book Global Routable ID Multiple AS 5300 Session Manager support Preloaded Routes Assured Services Admission Control Session Timer Support Offer/Answer Support AS 5300 Session Manager Call Feature support Reliability and fault tolerance Interfaces Accounting Security Chapter 24: Accounting Manager fundamentals Tools and utilities Accounting files and directories Chapter 25: Database Manager fundamentals Description Architecture Database terminology Replication Synchronization Database states Database related jobs Database backup and recovery Alert logs and trace files Tablespaces Chapter 26: Provisioning Manager and Personal Agent Manager fundamentals Description Web server Security Chapter 27: End-user clients Avaya Aura AS 5300 Personal Agent Avaya Aura AS 5300 UC Client Avaya Aura AS 5300 Office Client Avaya 1100 Series IP Deskphones IP Deskphones and Hotline service General Dynamics viper phone Security Chapter 28: Virtualization support October 2017 Avaya Aura Application Server 5300 Overview 9

10 Contents Chapter 29: Avaya Aura Application Server 5300 document suite Appendix A: Supported features Supported features Appendix B: IPv6 overview IPv4 versus IPv ICMPv IPv6 addressing overview Multicast Address format Address prefix and subnet Stateless and stateful autoconfiguration Address resolution and caching IPv6 address management Multiple IP addresses per interface IPv6 routing Upper layer protocols DNS DHCP FTP SDP IPv6 migration Appendix C: Regulatory and license information Red Hat Software October 2017 Avaya Aura Application Server 5300 Overview 10

11 Chapter 1: New in this release This section details the changes in Avaya Aura Application Server 5300 Overview, NN for Avaya Aura Application Server 5300 Release 3.0. Navigation Features on page 11 Other changes on page 14 Features For information about feature-related changes, see the following sections: Avaya Media Server integration on page 11 CAC Integration on page 12 Custom network domains on page 12 Destination Code Controls on page 12 Enhanced Password Policies on page 12 Enhanced 911 Service with automatic location identification using E911 Manager on page 12 General Dynamics viper phone on page 12 Platform servers on page 12 Release 3.0 upgrades on page 13 Call features on page 63 SIP TLS Identity Checking on page 13 Virtualization Support on page 13 For more information about the features that are new for this release, see Avaya Aura Application Server 5300 Release Delta, NN Avaya Media Server integration Avaya Media Server is now integrated with and managed from the AS 5300 Element Manager through an Avaya Media Server Network Element (NE). Removed content describing the Avaya October 2017 Avaya Aura Application Server 5300 Overview 11

12 New in this release Media Server Element Manager, and updated the section User interfaces for network administrators on page 41. CAC Integration Added new section Common Access Card (CAC) authentication for AS 5300 UC Client configured for high security on page 127. Custom network domains Added the section Custom network domains on page 55 Destination Code Controls Added the section Destination Code Controls on page 104 Enhanced Password Policies Updated section Authentication, password, and user management on page 127. Enhanced 911 Service with automatic location identification using E911 Manager Added Enhanced 911 service with automatic location identification using E911 Manager on page 52 General Dynamics viper phone Added the section General Dynamics viper phone on page 177 Platform servers Application Server 5300 Release 3.0 uses HP ProLiant DL360 G7 platform server. Updated the following sections: Application Server 5300 hardware platforms on page 37 Minimum baseline configurations on page 38 October 2017 Avaya Aura Application Server 5300 Overview 12

13 Document changes since last issue Application Server 5300 system capacity on page 39 SIP TLS Identity Checking Added SIP TLS Identity Checking on page 132. Release 3.0 upgrades The following sections were updated to support Application Server 5300 and Avaya Media Server upgrades. VLAN support on page 21 Upgrade strategy on page 115 Licensing and keycoding on page 100 Virtualization Support Added Virtualization Support on page 178. Document changes since last issue The following changes have been made to this document since it was issued for Application Server 5300 Release 3.0 in June, 2012: Added SIP TLS Identity Checking on page 132. Added Enhanced 911 service with automatic location identification using E911 Manager on page 52. Updated information on supported clients in Assistant Support and Assistant Console on page 62. Updated Vertical Service Codes on page 69 to include more detailed descriptions of Vertical Service Codes (VSC), included the addition of new tables to describe VSC usage, and VSC treatments. Added information about subscriber placing a video call on hold in ASAC budget on page 154. Updated Features associated with access clients and devices on page 56. Updated Supported features on page 180 to include PA Route Advanced routes, PA Route Call Forward Busy, and PA route Call Forward Immediate. October 2017 Avaya Aura Application Server 5300 Overview 13

14 New in this release Other changes Revision History October 2017 Updated the legal page for Avaya Aura Application Server 5300 Release 3.0. March 2016 This document is issued to support Avaya Aura Application Server 5300 Release 3.0 Service Pack 12. July 2015 Updated Product Overview for the Virtualization feature. Added Virtualization Support on page 178. Updated the Call features on page 63 section. September 2014 This document is issued to support Avaya Aura Application Server 5300 Release 3.0 Service Pack 9. April 2013 July 2013 April 2013 April 2013 April 2013 March 2013 March 2013 February 2013 January 2013 Added Enhanced 911 service with automatic location identification using E911 Manager on page 52. Draft AA. This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated Instant Messaging Presence and Presence-based routing on page 68 Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated Supported features on page 180 to include PA Route Call Forward Busy and PA route Call Forward Immediate. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated Supported features on page 180 to include PA Route Advanced routes. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated Features associated with access clients and devices on page 56. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated the following section: Assistant Support and Assistant Console on page 62 Table continues October 2017 Avaya Aura Application Server 5300 Overview 14

15 Document changes since last issue December 2012 December 2012 December 2012 November 2012 September 2012 July 2012 June 2012 August 2010 May 2010 April 2010 Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated the following section: Assured Services Admission Control on page 153 Enhanced 911 service on page 47 Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated the following section: ASAC budget on page 154 Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Added additional information about Vertical Service Codes (VSCs) in the following section: Vertical Service Codes on page 69 Updated the following sections: Call features on page 63 Communication methods on page 44 Destination Code Controls on page 104 Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Restored references to the Avaya Aura AS 5300 Office Client. Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Updated the following section: Features associated with access clients and devices on page 56 Standard This document is issued to support Avaya Aura Application Server 5300 Release 3.0. Standard This document is issued to support Avaya Aura Application Server 5300 Release 2.0. Technical changes were made. Standard This document is issued to support Avaya Aura Application Server 5300 Release 2.0. Editorial changes were made. Standard This document is issued to support Avaya Aura Application Server 5300 Release 2.0. This document contains information previously contained in the following document, now retired: Avaya Aura Application Server 5300 Fundamentals, NN Table continues October 2017 Avaya Aura Application Server 5300 Overview 15

16 New in this release June 2008 Standard This document is issued to support Nortel Application Server 5300 Release 1.0. Changes were made to AS5300 Element Manager Console fundamentals on page 140. June 2008 Standard This document is issued to support Nortel Application Server 5300 Release 1.0. October 2017 Avaya Aura Application Server 5300 Overview 16

17 Chapter 2: Overview This document describes the Avaya Aura Application Server Application Server 5300 is part of the Avaya Multimedia Communication Portfolio (MCP). Navigation Introduction on page 18 Building blocks on page 25 Network element architecture on page 34 Application Server 5300 interworking on page 35 Application Server 5300 hardware on page 37 Software on page 40 Operations, Administration, Maintenance, and Provisioning strategy on page 41 Features and services on page 47 Interfaces and communication protocols on page 84 Configuration and administration on page 95 Translations and routing on page 101 Redundancy, fault tolerance, and failover on page 107 Installation and patching on page 115 Fault management on page 118 Configuration management on page 120 Accounting management on page 122 Performance management on page 123 Security, administration, and maintenance on page 125 Application Server 5300 fundamentals on page 135 Avaya Aura Application Server 5300 document suite on page 179 Supported features on page 180 Regulatory and license information on page 202 October 2017 Avaya Aura Application Server 5300 Overview 17

18 Chapter 3: Introduction The Avaya Multimedia Communication Portfolio (MCP) offers a wide range of next-generation multimedia services in a variety of network configurations, which include the Multimedia Communication Server 5100 (MCS 5100) and the Avaya Aura Application Server The Application Server 5300 solution provides a powerful platform that supports enhanced security and hosts a full set of Session Initiation Protocol (SIP) features, a diverse range of Internet Protocol (IP) based clients, and gateway and media server components for SIP interoperability. Application Server 5300 builds on the strengths of MCS The Application Server 5300 solution is designed for Enterprise deployments where secure operation is required. The solution combines secure SIP multimedia client applications and services, with scalable interworking, trunking, and routing, and integrates into the customer private branch exchange (PBX) environment and migrates PBX clients to IP and next-generation SIP services. You can introduce the Application Server 5300 solution into standalone IP environments and provide the newest SIP multimedia applications, such as instant messaging (IM), Presence, and video calling. The solution enhances the overall communication experience and takes users to the next level of application integration. The Application Server 5300 solution provides a common service development and execution environment for client services infrastructure. Such client services and programmability are key components of evolving multimedia networks. The Application Server 5300 solution can: deliver multimedia services to subscribers over an IP network integrate the communication experience using the Avaya Aura AS 5300 UC Client or Avaya IP Deskphones to replace the traditional Time Division Multiplexing (TDM) telephones integrate IP network resources with real-time oriented conversation so subscribers can converse over an IP network provide enhanced terminal devices and applications to enrich and simplify subscriber experiences provide a full range of services to meet all communication needs, such as call forwarding and redirect, forking and distribution, presence monitoring, and management services provide multiprotocol, multivendor IP network controller and centralized network routing provide end-to-end Quality of Service (QoS) provide number translation, number portability, and accounting services within a SIP-based solution October 2017 Avaya Aura Application Server 5300 Overview 18

19 Session Initiation Protocol provide enhanced SIP use of the offer and answer model to establish and update multimedia sessions using the Session Description Protocol (SDP), and support of a keep-alive mechanism for SIP sessions provide threshold-based Call Access Control (CAC), based on the associated media type (either voice or video) provide enhanced security features, that include: - use of IP Security (IPsec), Hypertext Transfer Protocol Secure (HTTPS), Secure Real-time Transport Protocol (SRTP), Secure Real-time Transport Control Protocol (SRTCP), Secure File Transfer Protocol (SFTP), Secure Unified Network Internet Protocol Stimulus (USec), and SIP over Transport Layer Security (TLS) - support of US Department of Defense Voice Networks Generic Switching Center Requirements (GSCR), which include Multi-Level Precedence and Preemption (MLPP) over SIP - compliance with Security Technical Implementations Guidelines (STIG) and GR-815 The Application Server 5300 solution opens a new realm of secure communication capabilities by unifying voice, video, and data over a single-packet infrastructure. Important: If Application Server 5300 systems do not use TLS and SRTP, they use UDP, TCP, and RTP. AudioCodes Mediant 3000 does not support best effort RTP/SRTP (mixed-mode security). The configuration for all endpoints must be either secure or nonsecure for media. Navigation Session Initiation Protocol on page 19 IP communication on page 20 VLAN support on page 21 Application Server 5300 network on page 23 Session Initiation Protocol The Session Initiation Protocol (SIP) is a service-enabling protocol defined by the Internet Engineering Task Force (IETF). IETF proposed SIP as a standard on February 2, Application Server 5300 is based on RFC 3261 (J. Rosenberg et al., SIP: Session Initiation Protocol, IETF, June 2002, available at SIP is a text-based protocol analogous to the Hypertext Transfer Protocol (HTTP) that can initiate real-time, multimedia sessions to integrate voice, data, and video. The SIP text-based architecture speeds access to new services with greater flexibility and more scalability than many alternative Voice over IP (VoIP) communication protocols. October 2017 Avaya Aura Application Server 5300 Overview 19

20 Introduction SIP is based on User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) transport protocols. For secure communications, Application Server 5300 can use TCP protected by TLS for SIP messaging. SIP allows simplified, interactive multimedia services. With SIP, Application Server 5300 can deliver a range of personalized, media-rich services at any time or place for users connected to the Enterprise network. These SIP-enabled services increase productivity, expand mobility, and enhance interactive communication. IP communication The Application Server 5300 solution enables communication between SIP-enabled client endpoints. Endpoints communicate directly with each other or with endpoints that reside on other access networks. With dynamic addressing schemes, such as Dynamic Host Configuration Protocol (DHCP), the system uses the IP domain concept to define networks of subscribers, allowing subscribers to use more than one device. A domain is an overlay in the IP network, which defines a subset of all subscribers served by a single system. Examples of common domain servers currently in use include servers and Web servers. For real-time communication needs, the Application Server 5300 maintains information related to the actual locations of subscribers in the network, and then proxies communication requests to those locations to reach the particular subscriber. After the system establishes the signaling communication path, the endpoints can transmit data or media between them as indicated during the setup of the communication path. The Application Server 5300 supports gateways to bridge the IP and existing TDM and Public Switched Telephone Networks (PSTN) to enable voice communication between IP endpoints and traditional TDM devices. Application Server 5300 supports Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). Avaya Media Server supports IPv4 and IPv6 addressing for media communications, and IPv4 addressing for all other communications. For more information, see IP addressing on page 89 The Application Server 5300supports a mix of IPv4 and IPv6 communications, as shown in the following table. October 2017 Avaya Aura Application Server 5300 Overview 20

21 VLAN support Table 1: IPv4 and IPv6 communications in the Application Server 5300 solution To From Admin PC Provisioning Manager, Personal Agent Manager AS 5300 Elemen t Manage r AS 5300 Session Manage r Avaya Media Server (MS) Media Gatew ay Subsc riber PC Admin PC IPv4 IPv4 n/a n/a n/a n/a n/a Provisioning Manager, Personal Agent Manager AS 5300 Element Manager AS 5300 Session Manager Avaya Media Server (MS) IPv4 IPv4 IPv4 n/a n/a IPv4 n/a IPv4 IPv4 IPv4 n/a n/a n/a n/a IP Deskph ones n/a IPv4 IPv4 IPv4 IPv4 IPv4 IPv6/ IPv4 Signalin g n/a n/a n/a IPv4 IPv6/ IPv4 Media Media Gateway n/a n/a n/a IPv4 IPv6/ IPv4 Media Subscriber PC n/a IPv4 n/a IPv4 n/a n/a IPv4 IP Deskphones n/a n/a n/a IPv6/ IPv4 Signalin g n/a IPv6/ IPv4 Media n/a n/a IPv4 IPv6/ IPv4 Media IPv6/ IPv4 Media VLAN support The Avaya Ethernet Routing Switch 5500 (ERS 5500) series supports the segregation of IPv4 and IPv6 network traffic from some of the solution components into separate external Voice Local Area Network (VLAN) tagged networks. Customers can use the ERS 5500 to separate traffic into different networks or VLANs based on function, for example, maintenance and signaling traffic. The ERS 5500 supports 802.1q VLAN tagging. The ERS 5500 functions as a Layer 2/Layer 3 (L2/L3) edge switch that supports Ethernet links to the following components: Application Server 5300 SIP core servers October 2017 Avaya Aura Application Server 5300 Overview 21

22 Introduction Avaya Media Server (MS) AudioCodes Media Gateways Gateways and IADs AudioCodes EMS server for Media Switch Expert EMS server The ERS 5500 connects these components into three VLANs: Signaling and Bearer traffic (SIG) Local Network Management System traffic (Local NMS) remote network monitoring traffic (ADIMSS) The Application Server 5300 administrator configures two Application Server 5300 VLANs. The Internal VLAN carries traffic to the ports of the Application Server 5300 Core and Avaya MS. The External VLAN carries traffic to the ports of the SIG, Local NMS, and ADIMSS. The Internal VLAN and External VLAN communicate over the same physical connections as the ERS IPv4 datagrams route to static routes between the Internal VLAN and External VLAN, based on the destination IPv4 address. Destination-based routes implement the policy for separating outgoing traffic from the Application Server 5300 Core and Avaya MS onto the correct VLAN. Avaya recommends that the Local NMS and ADIMSS destinations have individual routes, and that a single default route handles all other destinations using the SIG VLAN. Application Server 5300 supports IPv6 communication between some of the Application Server 5300 Core servers and the SIP clients that are reachable through the SIG VLAN. The ERS 5500 examines all untagged Ethernet frames and assigns them to the SIG VLAN if they contain IPv6 payloads. The Core Network ports support VLAN tagging, while the internal ports are untagged. During upgrades from Application Server 5300 Release 1.0 to Application Server 5300 Release 2.0, existing servers that are configured for VLAN tagging must be reconfigured so that they do not use VLAN tagging. Upgrades from Application Server 5300 Release 2.0 to Application Server 5300 Release 3.0 do not need VLAN reconfiguring. Application Server 5300 deployments with the ERS 5500 support only a single site configuration. A single-site configuration consists of all members of the internal VLAN are collocated in the same physical site. The model of ERS 5500 to be deployed depends on the number of servers, media type, and network configuration. All of these factors directly or indirectly influence the number of Copper (Cu), Small Form Factor Pluggable (SFP) and 10 Gigabit SFP (XFP) ports required for each ERS 5500 model switch in the deployment. The following table summarizes the number and type of each port type for the ERS 5500-series models. October 2017 Avaya Aura Application Server 5300 Overview 22

23 Application Server 5300 network Table 2: Number of Copper, SFP, and XFP ports for ERS 5500-Series switches ERS 5500 Model Cu GigE ports Shared Cu/SFP ports XFP ports ERS T ERS T ERS T-PWR ERS T-PWR ERS T Each site requires at least two ERS 5500 to support redundancy of the Ethernet links. For more information about ERS 5500 requirements and deployments, see Avaya Aura Application Server 5300 Planning and Engineering, NN For information about traffic and network topology, see Avaya Aura Application Server 5300 Planning and Engineering, NN Application Server 5300 network The following figure shows the Application Server 5300 network connectivity. October 2017 Avaya Aura Application Server 5300 Overview 23

24 Introduction Figure 1: Application Server 5300 network connectivity October 2017 Avaya Aura Application Server 5300 Overview 24

25 Chapter 4: Building blocks The Application Server 5300 delivers multimedia services to communication devices over various access media, such as wireline, wireless, and Enterprise networks. The solution uses building blocks that combine in different ways to create SIP-based IP network solutions. The building blocks contain network components required to support Application Server 5300 multimedia, mobility, and personalization services. The following figure shows the categories of SIP-enabled building blocks that comprise the overall portfolio offering. Figure 2: Application Server 5300 building blocks Navigation Application Server 5300 infrastructure on page 26 October 2017 Avaya Aura Application Server 5300 Overview 25

26 Building blocks Media servers on page 29 Gateways on page 29 Access clients on page 30 Application Server 5300 infrastructure The Application Server 5300 infrastructure is a collection of software modules that offer a wide range of next-generation multimedia services in a variety of network configurations. The software components reside on a Java-based application platform that runs on commercially available hardware. The following table describes the software components of the Application Server 5300 infrastructure. Table 3: Application Server 5300 infrastructure components Component AS 5300 Session Manager Description The service execution engine that provides the following software functionality: SIP Proxy Server Back-to-Back User Agent (BBUA) SIP Registrar Call Processing Language (CPL) Interpreter address resolution and routing capabilities As an optional software feature, the SIP Presence Manager processes information for presence subscription and notification. An AS 5300 Session Manager can function as a Local Session Controller (LSC) or a Multifunction Softswitch (MFSS). A system can support multiple AS 5300 Session Manager, providing an increase to the number of users that the system can handle. Additional AS 5300 Session Manager require additional servers. AS 5300 Element Manager For more information, see AS 5300 Session Manager fundamentals on page 142. The AS 5300 Element Manager facilitates communication between the AS 5300 Element Manager Console and other network components. The AS 5300 Element Manager Console is the administrator's interface to the AS 5300 Element Manager. Table continues October 2017 Avaya Aura Application Server 5300 Overview 26

27 Application Server 5300 infrastructure Component Description The AS 5300 Element Manager handles the following functions for the Application Server 5300 components, media server, and gateways: faults configuration performance collects operations, administration, and maintenance (OAM) The AS 5300 Element Manager Console is the administrator's interface to the AS 5300 Element Manager, as described below. For more information, see: AS 5300 Element Manager fundamentals on page 136 Avaya Aura Application Server 5300 Configuration, NN Database Manager Avaya Aura Application Server 5300 Security, NN The Database software and the Database Manager software provide database functionality. Some network components access the database to provide storage and retrieval for: subscriber location information registration status based on the information received with SIP client registration routing and translation entries system configuration data The database functionality resides on the protected Application Server 5300 network. Accounting Manager For more information, see Database Manager fundamentals on page 165. The Accounting Manager receives, stores, formats, and transmits accounting information for billing purposes. For more information, see: Accounting Manager fundamentals on page 163 Avaya Aura Application Server 5300 Configuration, NN Provisioning Manager Avaya Aura Application Server 5300 Accounting Records Reference, NN The Provisioning Manager provides an interface for accessing service packages and other data for clients. The Provisioning Client and Avaya Aura Application Server 5300 Personal Agent are the interfaces for the Provisioning Manager. The Provisioning Manager supports the following tasks: customer domain provisioning through the Provisioning Client Table continues October 2017 Avaya Aura Application Server 5300 Overview 27

28 Building blocks Component Description configuration of network services functions, such as the network address book bulk provisioning, either through an Application Programming Interface (API) or command line interface (CLI) Personal Agent Manager (optional) support for the Personal Agent in small systems. Larger systems require a dedicated Personal Agent Manager. Within the Provisioning Manager, a server processes HTTPS requests to support service package requests and Application Server 5300 Personal Agent-related information. For more information about the Provisioning Manager, see: Provisioning Manager and Personal Agent Manager fundamentals on page 171 Avaya Aura Application Server 5300 Configuration, NN Avaya Aura Application Server 5300 Administration, NN Avaya Aura Application Server 5300 Security, NN For more information about the API and CLI, see Avaya Aura Application Server 5300 Application Programming Interfaces Reference, NN AS 5300 Element Manager Console The AS 5300 Element Manager Console is the secure security management and Element Manager graphical user interface for the Application Server 5300 solution. With the AS 5300 Element Manager Console, you can: administer system, database, and service components configure Application Server 5300 system sites, servers, service components, and services monitor the Application Server 5300 system using alarms, logs, and performance measurements manage the collection of operations, administration, and maintenance information The AS 5300 Element Manager Console runs on a personal computer (PC) and communicates with the AS 5300 Element Manager. For more information about the AS 5300 Element Manager Console, see AS 5300 Element Manager fundamentals on page 136 Avaya Aura Application Server 5300 Configuration, NN Avaya Aura Application Server 5300 Security, NN Avaya Media Server Avaya Media Server (MS) is a software based media application platform. Avaya MS work in conjunction with Media Gateways to provide a voice and data network with distributed IP networking and Table continues October 2017 Avaya Aura Application Server 5300 Overview 28

29 Media servers Component Description centralized call processing. Avaya MS consolidates multiple systems into a single server, enabling you to manage the entire communications infrastructure from one location, and provides scalability, redundancy and high availability. Media servers The following table describes the Application Server 5300 media servers. Table 4: Application Server 5300 media servers Media server Avaya Media Server (MS) Description The Avaya MS is a generic media processing platform. The Avaya MS platform is a stand-alone component that interfaces to both the controlplanes and bearer-planes of the network. The control-plane can use SIP over TLS for signaling, the bearer-plane can use Secure Real-time Transport Protocol (SRTP) and Secure Real-time Transport Control Protocol (SRTCP) for media. TheAvaya MS services supported are Ad hoc audio and video conferencing, Meet Me audio and video conferencing, Announcements, Music on Hold, and Unified Communications. Gateways The following table describes the Application Server 5300 gateways. Table 5: Application Server 5300 gateways Gateway Primary Rate Interface (PRI) Gateway Description The third-party PRI Gateway converts between packet-based and circuit-based voice streams to allow SIP endpoints to communicate with PSTN devices. The gateway: interworks with all SIP clients, existing PRI Gateways, voice mail systems, and TDM switches supports PRI call handling Table continues October 2017 Avaya Aura Application Server 5300 Overview 29

30 Building blocks Gateway Integrated Access Device (IAD) Element Management System and EMS Console Description supports all SIP multimedia services, such as audio conferencing, and Music on Hold For more information about the PRI Gateway, see Avaya Aura Application Server 5300 Planning and Engineering, NN and the vendor documentation. The third-party Integrated Access Device (IAD) converts between SIP and analog telephones, which allows analog telephones to be used with Application Server The IAD interworks with all SIP clients and associated voice mail systems supports SIP multimedia services, such as audio conferencing and Music on Hold For more information about the IAD, see Avaya Aura Application Server 5300 Planning and Engineering, NN and the vendor documentation. A third-party Element Management System (EMS) manages the PRI Gateway and IAD. The EMS provides operation, administration, management, and provisioning (OAMP) support for these gateways. The EMS Console connects to the EMS to perform the management functions. For more information about the EMS, see Avaya Aura Application Server 5300 Planning and Engineering, NN and the vendor documentation. Access clients The Application Server 5300 access clients include SIP user agents that provide access to the SIP network, administrator and subscriber provisioning interfaces, and an interface for administrative system management. User agents can be hardware components, such as an IP telephone, software applications that run on a PC, or software applications that run from a Web browser. Subscriber access to the SIP services network requires one of the supported clients. The following table describes the supported Application Server 5300 access clients. October 2017 Avaya Aura Application Server 5300 Overview 30

31 Access clients Table 6: Application Server 5300 access clients Access client Avaya Aura Application Server 5300 Personal Agent Avaya Aura Application Server 5300 Provisioning Client Avaya Aura AS 5300 UC Client Description With the browser-based Avaya Aura Application Server 5300 Personal Agent client, users can perform network-based management with their own Application Server 5300 services and communication preferences. Features include: Routes: to define call screening and routing behavior Preference: to modify personal information and services Directory: to manage key contact information; to access personal and global address books For a complete list of features, see Features associated with access clients and devices on page 56. For more information about the Application Server 5300 Personal Agent, see Avaya Aura AS 5300 Personal Agent on page 173 Avaya Aura Application Server 5300 Personal Agent User Guide, NN System administrators can use the browser-based Provisioning Client tool to provision administrators domains gateways voice mail servers service packages telephony routing translations For more information about the Provisioning Client, see Provisioning Client on page 42 Avaya Aura Application Server 5300 Using the Provisioning Client, NN Avaya Aura Application Server 5300 Security, NN The standalone, SIP-enabled Avaya Aura AS 5300 UC Client user agent operates on a Personal Computer (PC) and provides access to the following SIP features and services: traditional telephone services multimedia communications - video calls - instant messaging Table continues October 2017 Avaya Aura Application Server 5300 Overview 31

32 Building blocks Access client Description communication management - directory: to access and manage a personal address book - call logs - Friends Online Automatic Software Update (ASU) The Avaya Aura AS 5300 UC Client accesses the SIP services network through the AS 5300 Session Manager. For a complete list of features available for the Avaya Aura AS 5300 UC Client, see Features associated with access clients and devices on page 56. For more information, see Avaya Aura AS 5300 UC Client on page 174 Avaya Aura AS 5300 Office Client Avaya Aura Application Server 5300 UC Client User Guide, NN The standalone, SIP-enabled Avaya Aura AS 5300 Office Client user agent is a plug-in for Microsoft Office. It operates on a Personal Computer (PC) and provides access to the following SIP features and services: traditional telephone services multimedia communications - video calls - instant messaging communication management - directory: to access and manage a personal address book - call logs - Friends Online The Avaya Aura AS 5300 Office Client accesses the SIP services network through the Session Manager. For a complete list of features available for the Avaya Aura AS 5300 Office Client, see Features associated with access clients and devices on page 56. For more information, see Avaya Aura AS 5300 Office Client on page 174 Avaya 1120E IP Deskphone Avaya Aura Application Server 5300 Office Client User Guide, NN The Avaya 1120E IP Deskphone with SIP firmware and Avaya 1140E IP Deskphone with SIP firmware provide SIP-based telephony. SIP IP Table continues October 2017 Avaya Aura Application Server 5300 Overview 32

33 Access clients Access client Avaya 1140E IP Deskphone Description Deskphone downloads the license file (specific to that phone, based on the MAC address) from the Provisioning server. The license file contains 1, 2, or 3 tokens that enable various levels of features for the phone. After the IP Deskphone downloads the license file, the phone can communicate with the call server. The Application Server 5300 supports systems with all SIP IP Deskphones. When ordering a new Application Server 5300 system, the IP Deskphones that are ordered already have the appropriate firmware installed. During the 30-day evaluation period, the IP Deskphones with SIP firmware can operate without a license. To purchase the license files from Avaya, an administrator must provide a list of the Medium Access Control (MAC) addresses for all IP Deskphones. The administrator must also load the license files onto the Provisioning server. In this document: the term IP Deskphones with SIP firmware refers to the Avaya 1120E IP Deskphone with SIP firmware and Avaya 1140E IP Deskphone with SIP firmware. For more information, see the Avaya 1100 Series IP Deskphones documentation. For a complete list of features, see Table 11: Features associated with Application Server 5300 IP Deskphones on page 60. Sectéra viper phone The Sectéra viper is a secure client for VoIP and Analog Networks, and is certified by NSA and Joint Interoperability Test Command (JTIC ) with Integrated security, up to and including Top Secret /SCI, including Sensitive But Unclassified (SBU). For more information about features supported by the viper phone, see the documentation provided in the CD that is shipped with the product. Also, see October 2017 Avaya Aura Application Server 5300 Overview 33

34 Chapter 5: Network element architecture Network elements belong to one of three categories based on their degree of integration into the Application Server 5300 system: managed elements, monitored elements, and external elements. Managed elements are fully integrated network elements. Use the AS 5300 Element Manager Console to configure, deploy, and maintain managed network elements through the AS 5300 Element Manager. The Fault and Performance Manager (FPM) monitors managed network elements. The system-managed elements consist of the AS 5300 Element Manager, AS 5300 Session Manager, Accounting Manager, Database Manager, Avaya Media Server, and Provisioning Manager. Important: The AS 5300 Element Manager performs the FPM function for the system. The system does not support a standalone FPM. Monitored elements are partially integrated network elements. You cannot deploy monitored elements through the AS 5300 Element Manager. You can use the AS 5300 Element Manager Console to perform configuration (enough to permit monitoring) for these elements. The FPM monitors monitored elements. External elements are not integrated. You cannot deploy or monitor external elements through the AS 5300 Element Manager. You can use the AS 5300 Element Manager Console to perform only a minimal amount of configuration (generally name and network address) for these elements. The system external elements include the Integrated Access Device (IAD), Primary Rate Interface (PRI) Gateway, and their Element Management System. October 2017 Avaya Aura Application Server 5300 Overview 34

35 Chapter 6: Application Server 5300 interworking This chapter describes the interworking aspects of the Application Server Navigation Interworking with Avaya products on page 35 Interworking with third-party products on page 35 Interworking with Avaya products Because SIP is an open standard, the Application Server 5300 works with the following Avaya products through the PRI Gateway: Communication Server 1000 (CS 1000) (Releases 5.0, 5.5, and 6.0) Enterprise IP Private Branch Exchange (PBX) Communication Server 2100 (CS 2100) (Release SE09.1) Important: Some Application Server 5300 features require specific releases of the above products. For more information, see Avaya Aura Application Server 5300 Planning and Engineering, NN The Application Server 5300 can interwork with many communication servers. The Application Server 5300 system acts as a front end between the caller and the communication server, with the communication server continuing to provide its PBX services. In this configuration, the Application Server 5300 system does not provide any services on behalf of the PBX. Interworking with third-party products The Application Server 5300 solution requires a combination of Avaya-developed products and third-party products. For information about all the required products, see Avaya Aura Application Server 5300 Planning and Engineering, NN October 2017 Avaya Aura Application Server 5300 Overview 35

36 Application Server 5300 interworking Avaya offers a formalized process to achieve interoperability with third-party vendors through the Avaya Developer Partner Program (DPP). The DPP offers vendors an infrastructure of testing, legal agreements, processes, and marketing tools to engage third-parties with complementary solutions to perform compatibility testing and establish a commercial relationship with Avaya. October 2017 Avaya Aura Application Server 5300 Overview 36

37 Chapter 7: Application Server 5300 hardware This chapter describes the hardware aspects of Application Server For detailed information, see Avaya Aura Application Server 5300 Planning and Engineering, NN Navigation Application Server 5300 hardware platforms on page 37 Minimum baseline configurations on page 38 Application Server 5300 system capacity on page 39 Application Server 5300 hardware platforms The Application Server 5300 hardware platform includes core infrastructure for redundant small, medium, and large deployments using HP ProLiant DL360 G7 servers Avaya Media Server for small deployments or distributed systems using HP ProLiant DL360 G7 servers PRI Gateway and Element Management System (EMS) using AudioCodes Mediant 3000, Sun Fire V215, and T2000 servers. The ancillary hardware for Application Server 5300 includes: data network equipment to deliver service to desktops, including Layer 2 and Layer 3 switches. Switching products, like the Avaya Application Switch, are required. remote management through Avaya Contivity Integrated Access Device (IAD) for support of analog telephones using AudioCodes MediaPacks Avaya Ethernet Routing Switch 5500-series (ERS 5500), if the system requires a VLAN October 2017 Avaya Aura Application Server 5300 Overview 37

38 Application Server 5300 hardware Minimum baseline configurations The Application Server 5300 supports the following system deployments: small redundant system that supports up to 5000 subscribers medium redundant system that supports up to subscribers (scalable to ) large redundant system that supports up to subscribers (scalable to ) For small redundant systems, the minimum baseline configuration for the Application Server 5300 infrastructure includes one pair of HP ProLiant DL360 G7 servers with the following mapping to software modules: all core software (AS 5300 Session Manager, AS 5300 Element Manager, Accounting Manager, Database Manager, and Provisioning Manager). For medium redundant systems, the minimum baseline configuration for the Application Server 5300 infrastructure includes four HP ProLiant DL360 G7 servers with the following mapping to software modules: one pair of servers for the AS 5300 Session Manager one pair of servers for the AS 5300 Element Manager, Accounting Manager, Database Manager, and Provisioning Manager For large redundant systems, the minimum baseline configuration for the Application Server 5300 infrastructure includes eight HP ProLiant DL360 G7 servers, with the following mapping to software modules: one pair of servers for the AS 5300 Session Manager one pair of servers for the Accounting Manager one pair of servers for the AS 5300 Element Manager and Provisioning Manager one pair of servers for the Database Manager Avaya Media Server (MS) services are provided by separate HP ProLiant DL360 G7 servers, configured in pairs. The following table describes the configuration required to support additional features. Table 7: Additional configuration To support increased user capacity Ad hoc conferencing, Meet Me conferencing, Music on Hold, Recorded Announcements, and Unified Communications package IM Chat service Configure extra HP ProLiant DL360 G7 servers configured for additional AS 5300 Session Managers Avaya MS Avaya MS Table continues October 2017 Avaya Aura Application Server 5300 Overview 38

39 Application Server 5300 system capacity To support calls to PSTN numbers TDM telephones Configure PRI Gateway (requires an EMS) Integrated Access Device (requires an EMS) You cannot configure the IM Chat service on shared servers with other Avaya MS applications. The system requires two ERS 5500 to support VLAN. Application Server 5300 system capacity For more information about system capacity, see Avaya Aura Application Server 5300 Planning and Engineering, NN October 2017 Avaya Aura Application Server 5300 Overview 39

40 Chapter 8: Software The Application Server 5300 solution employs the Red Hat Enterprise Linux operating system. In addition to Application Server 5300 core software components, the solution relies on additional software provided by the Avaya Media Server (MS), AudioCodes, and end-user clients. Application Server 5300 is compatible with Switch Expert by Real Time Monitors Inc. The Application Server 5300 PC-based clients support the use of Microsoft operating systems. For more information about the supported versions, see the following documents: Avaya Aura Application Server 5300 Personal Agent User Guide, NN Avaya Aura Application Server 5300 UC Client User Guide, NN Avaya Aura Application Server 5300 Using the Provisioning Client, NN Avaya Aura Application Server 5300 Configuration, NN For information about software installation, software delivery, and software patch strategy, see: Patching strategy on page 116 the documentation supplied with the software load the Avaya MS documentation suite the AudioCodes documentation the Switch Expert documentation For minimum firmware and software requirements for the supported vendor hardware, see Avaya Aura Application Server 5300 Planning and Engineering, NN October 2017 Avaya Aura Application Server 5300 Overview 40

41 Chapter 9: Operations, Administration, Maintenance, and Provisioning strategy The Application Server 5300 provides a full suite of user interfaces and applications that the operations staff use to perform maintenance and routine functions. This management system offers flexible and scalable architecture to manage significant network growth with ease-of-use and operational cost saving features. Benefits such as High Availability architecture, networking features, and customer support options ensure the network is positioned for the future. For more information about the administrator interfaces, see User interfaces for network administrators on page 41. The AudioCodes Element Management System (EMS) manages the Primary Rate Interface (PRI) Gateway and the Integrated Access Device (IAD) from an Operations, Administration, Maintenance and Provisioning (OAMP) perspective. For more information, see the vendor documentation. Switch Expert provides additional OAMP management. For information about the Switch Expert system, see Switch Expert on page 43. User interfaces for network administrators The Application Server 5300 provides user interfaces for network administrators to deploy, configure, manage, and monitor network elements, and to perform provisioning tasks as described in the following sections: AS 5300 Element Manager Console on page 41 Provisioning Client on page 42 Remote provisioning on page 42 AS 5300 Element Manager Console The AS 5300 Element Manager Console is the primary user interface for Application Server Use it to deploy, configure, manage, and monitor the AS 5300 Session Manager Provisioning Manager, Database Manager, AS 5300 Element Manager, Accounting Manager, and the PRI Gateway. You can also use it to monitor and manageavaya Media Server, and to manage firmware October 2017 Avaya Aura Application Server 5300 Overview 41

42 Operations, Administration, Maintenance, and Provisioning strategy updates for Avaya 1120E IP Deskphone and Avaya 1140E IP Deskphone. The AS 5300 Element Manager Console communications use HTTPS to secure data. The AS 5300 Element Manager Console is a Java application you can access from a Web browser on the management PC. Administrators perform all management functions through this interface, except for some provisioning tasks (Provisioning Client and Personal Agent) and database administration functions. From the console, you can view system topology in a directory tree use maintenance commands browse alarms, logs, and operational measurements monitor administration and operational states For more information, see Avaya Aura Application Server 5300 Configuration, NN Provisioning Client Use the Web-based Provisioning Client to perform overall provisioning of the Application Server Use this interface to provision other administrators, domains, gateways, Avaya Media Servers, voice mail servers, and service packages. The Provisioning Client communications use HTTPS to secure data. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN and Avaya Aura Application Server 5300 Security, NN Remote provisioning The Bulk Provisioning Tool (BPT) is deprecated as of Application Server 5300 Release 2.0. The system provides Application Programming Interface (API) support for third-party client applications through the Open Provisioning Interface (OPI). The OPI is used to remotely provision the Application Server 5300 system. OPI is based on the Simple Object Access Protocol (SOAP) 1.1 and the emerging web services standard. OPI supports the industry standard Web Services Description Language (WSDL) 1.1., which allows the service provider to provision their system with existing and custom applications. The goal of OPI is to allow customer-specific applications to interface with the Application Server 5300 provisioning system. Existing BPT scripts continue to work for services available in Application Server , but for new functions and enhancements to existing functions, you must update any existing scripts. October 2017 Avaya Aura Application Server 5300 Overview 42

43 Switch Expert Switch Expert This section describes the Switch Expert system that the Application Server 5300 solution requires in some deployments. For information about the supported deployments, see Avaya Aura Application Server 5300 Planning and Engineering, NN Navigation Description on page 43 Communication methods on page 44 Northbound Feed on page 45 SNMP on page 45 SFTP Pull on page 45 Management on page 46 Description Switch Expert is a third-party management application for Application Server 5300 that provides the ability to pull logs, alarms, billing information, and traffic measurements from Application Server 5300 products launch management consoles ( AS 5300 Element Manager Console, Provisioning Client, Avaya Media Server (MS), and Element Management System [EMS]) monitor the topology and status of every network element in the Application Server 5300 product use management operations over the Application Server 5300 Open Management Interface (OMI) use provisioning operations over the Application Server 5300 Open Provisioning Interface (OPI) (in the next phase of integration with Switch Expert.) Application Server 5300, Avaya MS, and AudioCodes communicate directly with Switch Expert. The Application Server 5300 product sends only Avaya MS alarms to Switch Expert. Switch Expert monitors the endpoints in the system, and shows their availability (offline or online status). Switch Expert also retrieves alarms (if any exist) and shows them as an indicator of the status of the endpoints. Switch Expert uses the Application Server 5300 TopologyOMI service (SOAP) to obtain Application Server 5300 system topology including the IP addresses of the network elements. Switch Expert then polls the status of each Network Element by querying the SNMP trap table relating to the Avaya Reliable Fault Management Information Bases (MIB). October 2017 Avaya Aura Application Server 5300 Overview 43

44 Operations, Administration, Maintenance, and Provisioning strategy Communication methods For each endpoint, Switch Expert has both a real-time communication method (where possible) and an alternative communication method. In the event of a communication error (including a failover or network failure) the Real Time Connection (Northbound Feed socket) stops. If the Northbound Feed remains stopped for a period of time, untransferred data between Application Server 5300 and Switch Expert accumulates, and the system transfers the accumulated data using the alternative communication method. The following table describes the Switch Expert communication methods. Table 8: Communication methods Endpoint Real-time communication method Alternative communication method AS 5300 Element Manager (logs) AS 5300 Element Manager (OMs) AS 5300 Element Manager(alarms) Accounting Manager (accounting records) Northbound feed (2 TCP Sockets: one for security logs, one for nonsecurity logs) Northbound feed (TCP socket) SNMPv2c trap Northbound feed (TCP socket) SFTP pull (from AS 5300 Element Manager, 2 different SFTP users: one for security log files, one for nonsecurity log files) SFTP pull (from AS 5300 Element Manager) SNMPv2c trap table (Using Avaya Reliable Fault MIBS) SFTP pull (from Accounting Manager) The hardened Avaya Aura AS 5300 UC Client used in Department of Defense (DOD) and Approved Product List (APL) sites is Federal Information Processing Standards (FIPS) aware. The Avaya Aura AS 5300 UC Client works on FIPS enabled and non-enabled computers. The following table describes the manner in which the system secures each communication for FIPS compliance. Table 9: FIPS compliance Communication Northbound Feed SFTP SSH OMI and OPI AS 5300 Element Manager Console Provisioning Client Syslogs FIPS compliance FIPS-compliant IPsec FIPS-compliant IPsec Open SSH HTTPS (FIPS compliant TLS) HTTPS (FIPS compliant TLS) HTTPS (FIPS compliant TLS) rsyslog October 2017 Avaya Aura Application Server 5300 Overview 44

45 Switch Expert Northbound Feed Northbound Feed is a simple TCP socket communication method in which the Application Server 5300 Core (AS 5300 Element Manager) acts as a server. The AS 5300 Element Manager clients (Switch Expert) connect to predefined ports and begin listening. As new data comes to the AS 5300 Element Manager, it prints the new data to the socket. Switch Expert reads the data and stores it appropriately. The format of the data differs according to the type of data. For logs and OMs, the Northbound Feed prints in the same format as the log or OM file. For logs there are two Northbound Feed configurations (different ports), one Northbound Feed transfers nonsecurity logs and the other Northbound Feed transfers security logs. This separation means security logs can be handled in a secure manner by authorized personnel. Switch Expert shows the type of log (security, nonsecurity, both) depending on the privileges (role) of the Switch Expert user. For accounting records, Switch Expert sends every call detail over the socket in the same transaction. Switch Expert uses the MCPV4 record type. The MCPV4 record type is based on the IPDR 3.5 standard. For more information, see Avaya Aura Application Server 5300 Accounting Records Reference, NN SNMP The AS 5300 Element Manager collects all system alarms. The AS 5300 Element Manager uses Simple Network Management Protocol (SNMP) traps to forward the alarms to Switch Expert. If a communication failure occurs (network failure, failover), Switch Expert uses Avaya Reliable Fault MIB to get to the SNMP Table and read all raised alarms. SFTP Pull After a failure of the real-time communication method, Switch Expert detects the failure and uses SFTP Pull to retrieve missing records directly from the AS 5300 Element Manager. An administrator uses the AS 5300 Element Manager Console to configure the Log Storage Rules and Log Filter for records. For more information about how to configure these parameters, see Avaya Aura Application Server 5300 Configuration, NN For each network element (Provisioning Manager, AS 5300 Element Manager, AS 5300 Session Manager) the storage location for the files is different. For each type of log (security or nonsecurity), Switch Expert determines the location of the folder based on the Log Storage Rule, Log Filter, and the network element. For more information, see the following examples: /var/mcp/oss/log/sm/all/mcp/prov1_0 (for PROV1_0 NE nonsecurity logs) /var/mcp/oss/log/sm/security/mcp/prov1_0 (for PROV1_0 NE security logs) /var/mcp/oss/log/sm/all/mcp/sesm1_0 (for SESM1_0 NE logs nonsecurity logs) October 2017 Avaya Aura Application Server 5300 Overview 45

46 Operations, Administration, Maintenance, and Provisioning strategy Switch Expert uses the timestamps included in the file names to determine which files in the folder could have missing records. After it retrieves the files, Switch Expert analyzes the records (based on timestamps) and retrieves the missing records. Management Switch Expert uses the Open Management Interface (OMI) for management operations, and the Open Provisioning Interface (OPI) for provisioning operations. Application Server 5300 shares the following OMI services with Switch Expert: LoginOmi: The LoginOmi defines the interface for administratively log on to the AS 5300 Element Manager. To perform other OMI operations, you must log on successfully. PreLoginBannerRetrievalOMI: This service provides the interface for retrieval of the "Pre Login" banner TopologyOmi: The TopologyOmi provides methods to retrieve topology information about sites, servers, network elements, and monitored elements configured in the Application Server 5300 system. It also provides methods to register for topology changes and receive topology change notifications. October 2017 Avaya Aura Application Server 5300 Overview 46

47 Chapter 10: Features and services This chapter provides information about important features and services in Application Server Navigation Enhanced 911 service on page 47 Enhanced 911 service with automatic location identification using E911 Manager on page 52 MLPP service on page 54 External Users on page 56 Features associated with access clients and devices on page 56 Enhanced 911 service The Application Server 5300 provides enhanced emergency services, also known as Enhanced 911 (E911). E911 differs from basic emergency services in two ways: the emergency call routes to the local Public Safety Answering Point (PSAP) serving the caller's area based on the calling phone location; the PSAP allows access to the calling party's address. the PSAP allows access to a callback number named the Automatic Number Identification (ANI). The PSAP can use this number - to call back the emergency caller in case the PSAP needs additional information after ending the emergency call - to reestablish the emergency call if it gets disconnected E911 services integrate the Application Server 5300 system with existing public and external E911 subsystems. Integration with existing public and external E911 subsystems involves the following steps: 1. The system maintains subscriber location information, and the system includes a mechanism to use the existing Automatic Location Information (ALI) database employed in North American Public Switched Telephone Network (PSTN). 2. The system delivers the caller's information so that the PSAP terminal can query the subscriber's civic address from the ALI database. It is possible for subscribers to place emergency calls without authentication on 11xx series phones. The UC Client does not support this option. October 2017 Avaya Aura Application Server 5300 Overview 47

48 Features and services The following figure shows a flow diagram of the basic information required for Enhanced 911. Figure 3: Outline of basic information required for E911 Each PSAP allows access to an ALI database. This database consists of physical addresses and callback numbers. The database typically updates every 24 hours for existing entries, while new entries update as soon as possible. The National Emergency Number Association (NENA) specifies the format for ALI database records. The Master Street Address Guide (MSAG) must approve ALI database entries. The following figure shows the call route, ALI lookup, and Emergency Response Locations (ERL) service node for E911 calls. October 2017 Avaya Aura Application Server 5300 Overview 48

49 Enhanced 911 service Figure 4: How an E911 call works Figure 5: How an emergency call works October 2017 Avaya Aura Application Server 5300 Overview 49

50 Features and services ERLs are locations associated with local PSAPs. An ERL represents a physical address, a building floor (for multistory buildings), the floor partition (for floors greater than square feet), and the room number (optional). See Figure 6: E911 call support on page 50. An ERL generally supports client mobility. For Application Server 5300 clients, an ERL supports mobility within the enterprise because the subscriber selects an appropriate ERL. E911 also supports residential E911 service by permitting you to designate ERLs as residential. A residential ERL must map to a gateway that allows connectivity to the corresponding PSAP and provides the originating subscriber's Public Charge ID to the PSAP. Figure 6: E911 call support The Location Infrastructure allows you to provision a Location Hierarchy for each domain so that you can define a virtual geographic area serviced by the associated domain. The component locations that constitute this hierarchy can be used by any service, including E911, that can require a knowledge of geography, proximity, or distribution. See Figure 7: Example of a location hierarchy on page 50. Figure 7: Example of a location hierarchy To meet the fundamental requirements for E911 calling functions, the system must have a sense of the geography being served. E911 contains a Location Infrastructure, used by any feature requiring location-based information. Using the Location Infrastructure, the system can configure a virtual topography to describe the system geography as well as the proximity and distribution of system components. See Figure 8: Overview of Enhanced 911 network architecture on page 51. October 2017 Avaya Aura Application Server 5300 Overview 50

51 Enhanced 911 service Figure 8: Overview of Enhanced 911 network architecture On-site notification (OSN) provides a target instant messaging account configured in the Emergency Response Location (ERL). After a subscriber dials the emergency number, the Application Server 5300 sends an instant message to the OSN account and the appropriate designated persons (acting as on-site response personnel) monitor the OSN messages. The messages provide caller information and enable the response personnel to direct the police, fire, or ambulance. The system administrator configures the policy for call hold and transfer of emergency calls, and the ability of the emergency call originator to release the call. E911 calls cannot be preempted by an incoming call, regardless of the incoming call priority. Additional enhancements to the E911 service are optional. The domain administrator logs on to the Provisioning Client and turns the Originator hold feature on in the domain parameters to make these enhancements available. These enhanced features are: Denial of originator-initiated mid-call features on an E911 call: This enhancement provides the capability to deny the originator of an emergency call the ability to invoke a feature that essentially puts the call on hold. This denial of features includes the following capabilities: - Hold - Transfer - Call Park - Conferencing - making a second call from the device (where applicable) - receiving incoming requests outside the emergency session Terminator call control on an E911 call: This enhancement prohibits an Application Server 5300 originator of an E911 call from disconnecting the call. The only party that can disconnect the E911 call is the PSAP. October 2017 Avaya Aura Application Server 5300 Overview 51

52 Features and services These enhancements modify the behavior of the AS 5300 Session Manager Emergency service that performs the following actions: Checkpoint impact: The AS 5300 Session Manager implements a checkpoint mechanism to achieve fault tolerance. During an enterprise emergency call, the AS 5300 Session Manager selects an ANI from a pool and temporarily associates the ANI with the originator. The AS 5300 Session Manager creates this temporary association with the SIP REGISTER method where the expired time is the ANI registration time. The AS 5300 Session Manager checkpoints the ANI registration times so the enterprise PSAP callbacks work after failover. Provisioned data, such as the ERLs, synchronize across all AS 5300 Session Manager using an alternate datasync (NOTIFY) mechanism. Abnormal Disconnect: The system must detect and handle emergency calls that disconnect so that emergency resources can promptly deallocate. E911 support contains a mechanism to detect abnormal disconnects at the AS 5300 Session Manager for emergency calls. During an emergency call, the system initiates an audit (polling) request to the originator. The polling interval is a configuration parameter (EmergencDuration) defaulting to 30 seconds. In the event that the client does not respond to the INFO request or responds with an unacceptable response, the audit fails, indicating an abnormal disconnect. After the audit fails, the AS 5300 Session Manager ends the call. The system creates accounting records each time the audit runs, indicating the outcome of the audit. If you enable the originator hold feature in a service profile, all subscribers assigned this profile inherit the above behavior. For instance, during the E911 call, this feature transitions the client into a mandatory Do-Not-Disturb (DND) mode, thereby rejecting all new inbound requests. Requests subject to being rejected include new calls, instant messages, collaborations, going on hold, starting a conference, making a transfer, starting a camera, or hanging up. After the operator disconnects the call, the client disables this DND behavior. Enhanced 911 Service with automatic location identification using E911 Manager Application Server 5300 provides extended abilities to Enhanced 911 Service if E911 Manager is part of the deployment. E911 Service with E911 Manager differs from the E911 Service in the following three ways: Dynamic emergency caller location determination: The EI physical location determined by E911 Manager using the Network Discovery mechanism based on IP address and MAC of EI. The EI location is used to route an emergency call to the appropriate PSAP that is nearest to the physical location of the emergency caller. Enhanced 911 Service without E911 Manager in the deployment determines the PSAP based on the location that is selected manually by the user at the time of login, which means that it might not match the EI physical location. Enhanced EON (Emergency On-Site Notification): Each emergency call attempt reported by Application Server 5300 to E911 Manager. E911 Manager sends the notification to the internal October 2017 Avaya Aura Application Server 5300 Overview 52

53 Enhanced 911 Service with automatic location identification using E911 Manager authorized security personnel of the organization about the emergency call with the detailed location information retrieved based on the data provided by Application Server Ease PSAP ALI DB update: Application Server 5300 emergency administrator does not need to provide information about ERLs and ANIs to ALI DB directly if it is integrated with E911 Manager. Application Server 5300 emergency administrator must only synchronize the location configuration with E911 Manager. Location granularity on the Application Server 5300 can be much smaller, since E911 Manager can provide the location information with any granularity according to the IP address and MAC of EIs connected to the AS Example of locations synchronization granularity: The following is an example of the locations structure on E911 Manager: At the Application Server 5300 side, the location granularity can be less than on E911 Manager. But all the ELINs must be configured on Application Server So the configuration of ELINs on Application Server 5300 for the same site can be as shown as below: - City1 ERL has: ELIN1; ELIN2; ELIN3; ELIN4; ELIN5; ELIN6; ELIN7; ELIN8; ELIN9; ELIN10; ELIN11; ELIN12; ELIN13; ELIN14; ELIN15; ELIN17; ELIN18; ELIN19; ELIN20; ELIN21; ELIN22 - City2 ERL has: ELIN23; ELIN24; ELIN25; ELIN26; ELIN27; ELIN28; ELIN29; ELIN30; ELIN31; ELIN32; ELIN33; ELIN34; ELIN35; ELIN36; ELIN37; ELIN38; ELIN39; ELIN40 October 2017 Avaya Aura Application Server 5300 Overview 53

54 Features and services Figure 9: How an E911 call works with integrated E911 Manager MLPP service The Multi-Level Precedence and Preemption (MLPP) service acts as a standalone Local Call Controller (LCC). Application Server 5300 provides MLPP service functionality only for the Defense Switched Network (DSN) and tracks Department of Defense (DoD) Application Server 5300 calls by means of a Precedence indicator. The Precedence indicator determines whether the system preempts a call to assure service for a call with a higher precedence (priority). Administrators configure the MLPP service using the Provisioning Client. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN With the MLPP service, subscribers can specify the precedence level of each call they place. Users specify the precedence level for a call at the IP client end or administrators specify precedence through the World Wide Numbering Plan. The user can initiate a call with a precedence level below or equal to the authorized precedence level configured for the user by the administrator. A call automatically defaults to Routine, unless the user chooses a higher precedence. October 2017 Avaya Aura Application Server 5300 Overview 54

55 Call Tracing During call processing, the system uses the precedence level to assure preferential call completion of higher precedence calls within the same MLPP service domain even if that means preempting lower precedence calls. After you specify the precedence level for a call, you cannot change it, and the connection between the two DSN subscribers has the same precedence level. The system disables call forwarding for all call priorities except Routine. Subscribers can use the following Call Forward features with Routine precedence calls: Call forwarding: Call Forwarding Unconditional (CFU) Call Forward Busy (CFB) Call Forwarding No Answer (CFNA) For more information, see Avaya Aura Application Server 5300 Personal Agent User Guide, NN and Avaya Aura Application Server 5300 UC Client User Guide, NN Accounting records contain the precedence level of the MLPP call. For more information, see Avaya Aura Application Server 5300 Accounting Records Reference, NN Custom network domains Application Server 5300 supports user-defined network domains apart from the system-defined DSN, UC, or CUC domains. You can use the Provisioning Client to create a custom network domain if you are unable to use the any of the system-defined network domains. You can define a maximum of five network domains. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Call Tracing Call Tracing enables the identification of nuisance or threatening calls. Two types of call tracing exist: Termination Call Tracing: Information about all incoming calls to a specific DN are recorded in the Malicious Call Tracing (MCT) log file. Outgoing Call Tracing: Information about outgoing calls from a specific DN to a specific DN are recorded in the MCT log file. To enable Terminating Call Tracing, the user s domain must have the MCT service enabled. Users do not require enabling of MCT for Outgoing Call Tracing. October 2017 Avaya Aura Application Server 5300 Overview 55

56 Features and services External Users External Users can be configured on the Application Server 5300 to provide users with the following services: voice mail Time Division Multiplex (TDM) Message Waiting Indicator (MWI) Avaya Media Server (MS) Unified Communication Avaya MS Meet Me Conferencing All calls coming to the Application Server 5300 for this type of user route to Avaya MS for voice mail. Telephony for these users come from their Time Division Multiplex (TDM) switch. To configure an External User, administrators create a user of the type TDM Mirror user. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN and Avaya Aura Application Server 5300 Configuration, NN Features associated with access clients and devices The Application Server 5300 offers a wide variety of multimedia and telephony features to the subscriber. The availability of these features and services depends on the client devices deployed on the system. Table 10: Features associated with Application Server 5300 soft clients on page 56 lists the features associated with Application Server 5300 soft clients. Table 10: Features associated with Application Server 5300 soft clients Feature Personal Agent (See 1 on page 59) Address book (personal) Alias routing Announcements Automatic software update (ASU) Audio conference (Ad hoc) Audio conference (Meet Me) Boss and Admin services Bulletins Call branding Call completion to busy subscriber AS 5300 UC Client Table continues October 2017 Avaya Aura Application Server 5300 Overview 56

57 Features associated with access clients and devices Feature Call decline Call forward Call hold and retrieve Call ignore Call logs client Call logs PA (network based) Call mute Call park Call precedence and preemption Call redirect Personal Agent (See 1 on page 59) (See 5 on page 59) (See 4 on page 59.) Call reject Call reject reasons Call return Call subjects Call transfer (consultative) Call transfer (direct) Call type-based screening Call waiting Call waiting disable Caller ID Calling, called, and connected name and number display Calling and called picture display Click to call PA invocation Click to dial client invocation Click to dial PA invocation Clipboard Codec selection Device restrictions (See 4 on page 59.) Directory (global address book) AS 5300 UC Client (See 5 on page 59) (See 4 on page 59.) (See 4 on page 59.) Table continues October 2017 Avaya Aura Application Server 5300 Overview 57

58 Features and services Feature Personal Agent (See 1 on page 59) Directory (Personal/Local Address Book) Do not disturb File exchange Firewall support (See 2 on page 59.) Friends Online Hotline Import Outlook contacts Inbox Instant message (IM) Instant message broadcast Instant message chat (3+ person IM sessions) Message Waiting Indicator (MWI) Network call log Network ignore Outbox Outlook integration PA Route advanced routes PA route anonymous call handling PA route call forward no answer PA route call rejection PA route push PA route receive IM PA route request PA route respond with IM PA route send to voice mail PA route sequential ring PA route simultaneous ring PA route time-of-day routing Picture ID Presence automatic and manual Presence on the phone indication Privacy Private and public name and number AS 5300 UC Client (See 4 on page 59.) Table continues October 2017 Avaya Aura Application Server 5300 Overview 58

59 Features associated with access clients and devices Feature Profile manager Quality of Service (QoS) Personal Agent (See 1 on page 59) Search options (address books) Secure instant messaging Server selection Sharing Star code service (Vertical Service Codes) Transfer Unified Communications Video (video on demand) Video calling point-to-point Video conferencing ad hoc Avaya Media Server (MS) Video conferencing Meet Me Avaya MS Voice mail (See 3 on page 59.) Voiceless Avaya Aura Application Server 5300 UC Client Web push and cobrowsing Whiteboard Notes AS 5300 UC Client 1. The Personal Agent is optional. Picture ID, screening, and routing features require a Personal Agent. 2. The Personal Agent is supported behind a firewall; however, there are no provisioning parameters for system administrators or end users to configure. 3. Users with access to the Personal Agent can configure screening and routing to automatically send calls to voice mail. 4. This feature is available only for non-dod Federal Civilian agency installations, where subscribers do not have MLPP in their Service Package. 5. This feature is available in three variations: Call Forward Unconditional (CFU), Call Forward Busy (CFB), and Call Forward No Answer (CFNA). Users can activate these variations by configuring them with the Personal Agent, or by using star codes. Table 11: Features associated with Application Server 5300 IP Deskphones on page 60 lists the features associated with supported Application Server 5300 IP Deskphones. October 2017 Avaya Aura Application Server 5300 Overview 59

60 Features and services Table 11: Features associated with Application Server 5300 IP Deskphones Feature Avaya 1120E IP Deskphone Avaya 1140E IP Deskphone Address book (personal) Alias routing Announcements Automatic software update (ASU) Audio conference (Ad hoc) Audio conference (Meet Me) Boss and Admin services Bulletins Call branding Call completion to busy subscriber Call decline Call forward (See and 3 on page 62.) (See and 3 on page 62.) Call hold and retrieve Call ignore Call logs client Call mute Call park Call precedence and preemption Call redirect Call reject (See 2 on page 62.) (See 2 on page 62.) Call reject reasons Call return Call subjects Call transfer (consultative) Call transfer (direct) Call type-based screening Call waiting Caller ID Calling, called, and connected name and number display Calling and called picture display Clipboard Codec selection Device restrictions Table continues October 2017 Avaya Aura Application Server 5300 Overview 60

61 Features associated with access clients and devices Feature Avaya 1120E IP Deskphone Avaya 1140E IP Deskphone Directory (Global Address Book) See 4 on page 62 See 4 on page 62 Directory (Personal/Local Address Book) Do not disturb File exchange Firewall support Friends Online Hold (automatic hold) Hotline Import Outlook contacts Inbox Instant message (IM) Instant message broadcast Instant message chat (3+ person IM sessions) Message Waiting Indicator (MWI) Network call log Network ignore Outbox Outlook integration Picture ID Presence Profile manager Quality of Service (QoS) Search options (address books) Secure instant messaging Server selection Sharing Star code service (Vertical Service Codes) Transfer Unified Communications Video (video on demand) Voice mail Web push and cobrowsing Whiteboard Table continues October 2017 Avaya Aura Application Server 5300 Overview 61

62 Features and services Feature Avaya 1120E IP Deskphone Avaya 1140E IP Deskphone Notes: 1. This feature is available only for non-dod Federal Civilian agency installations, where subscribers do not have MLPP in their Service Package. 2. Users with MLPP in their Service Packages cannot reject non-routine precedence calls. 3. This feature is available in three variations: Call Forward Unconditional (CFU), Call Forward Busy (CFB), and Call Forward No Answer (CFNA). Users can activate these variations by configuring them with the Personal Agent, or by using star codes. 4. Subscribers can use Personal Agent or UC Client to copy entries from the Global Address Book to the Personal Address Book, making those entries available on the IP Deskphone. The following sections describe the features and services available to the access clients and devices: Assistant Support and Assistant Console on page 62 Call features on page 63 Instant Messaging, Presence, and Presence-based routing on page 68 Multimedia services on page 68 Sharing features on page 69 Vertical Service Codes on page 69 For more information, see Avaya Aura Application Server 5300 Personal Agent User Guide, NN Avaya Aura Application Server 5300 UC Client User Guide, NN Avaya Aura Application Server 5300 Using the Provisioning Client, NN Avaya Aura Application Server 5300 Office Client User Guide, NN Assistant Support and Assistant Console The following Assisted user features are supported: Assistant Support allows one subscriber to respond to or screen another subscriber s calls. The individual requesting this assistance is referred as an Assisted user. The individual who provides this assistance is called an Assistant. Assistant Console allows one subscriber to act as an assistant to another subscriber, giving the assistant limited access to the calls of the assisted subscriber. Assistant Console is available on Avaya Aura AS 5300 UC Client and the Avaya Aura AS 5300 UC Client Set. With the Avaya Aura AS 5300 UC Client Set, the IP Deskphone is used for voice only, and the assistant functions are available on the Avaya Aura AS 5300 UC Client. With this functionality, an assistant can monitor, receive, screen, or route calls. The assistant can park calls so that October 2017 Avaya Aura Application Server 5300 Overview 62

63 Features associated with access clients and devices another individual can retrieve them. The assistant can initiate a call on the Assisted user s behalf, and the Calling ID will appear to be that of the Assisted user. The Assistant Console functionality provides a visual reminder that calls are on hold. Administrators provision the timeout period through the Provisioning Client. Subscribers configure the timeout period for parked calls through the Personal Agent. An assistant can override an Assisted user s use of the Make Subscriber Busy feature and can transfer a call or ring an Assisted user s access client. This override capability applies to calls in process; the Assistant cannot activate this feature to apply to calls before they occur. Accounting records track when an Assistant answers calls of an Assisted user, or makes a call on behalf of the Assisted User. The Assisted user is responsible for call routing configuration. The following limitations apply to Assistant Support and Assistant Console: The Calling line ID restriction (privacy functionality) does not work with the Assistant Console service. If an Assistant holds a call for an Assisted user, the autoretrieve capability does not function. Call features Application Server 5300 can provide subscribers with the following call features: Important: Not all services may be available on your Application Server For more information, contact your system administrator. Call Forward: A subscriber can forward a call to another Application Server 5300 subscriber from an IP Deskphone, Avaya Aura AS 5300 UC Client, AS 5300 Web Client, or General Dynamics viper phone. Call Logs: Call logs tracks who calls the Application Server 5300 subscriber. Subscribers can use a soft client to view the call logs and use the call logs to return calls, send instant messages, and save caller information in their Personal Address Book. Call Park and Retrieve: The Call Park feature allows subscribers to temporarily place a call into a holding area and to retrieve parked calls at a later time. The subscribers who parks the call can request a return of the call if it is not retrieved within a specified length of time. Subscribers can park a call at the Avaya Aura AS 5300 UC Client where it can be retrieved by anyone, or they can park a call while waiting for a specific subscriber to retrieve it. Retrieval is based on user IDs. Calls cannot be parked against subscribers outside the Application Server 5300 system. October 2017 Avaya Aura Application Server 5300 Overview 63

64 Features and services Call Pickup: Call Pickup allows subscribers that are part of a common Call Pickup group to answer calls ringing devices belonging to other members in the group. Call Pickup is comprised of the following feature variants: - Group Call Pick-up: allows a subscriber to pick up a call that is presented to any member of the group. Subscribers receive notification about ringing calls. Currently, only Avaya Aura AS 5300 UC Client supports Group Call Pickup. - Directed Call Pick-up: allows a subscriber to pick up a call that is presented to any member of the group by explicitly specifying the Group ID. - Targeted Call Pick-up: allows a subscriber configured with targeted call pickup service to specify the DN or user ID associated with the ringing call within the assigned Call Pickup group. The Call Pickup service is also supported with Vertical Service Code (VSC). A Call Pickup Client that supports Call Pickup must be assigned the Call Pickup Service. Call Pickup service must also be assigned to be a member of at least one Call Pickup group during provisioning. The client is also assigned the Call Pickup variants that can be used to pickup calls. An Application Server 5300 subscriber can subscribe to a group, directed, and targeted call pickup. Call Screening and Routing: The Personal Agent allows subscribers to consolidate various contact numbers for different communication devices, such as an office phone, home phone, and mobile phone. Basic call screening allows subscribers to choose a default route for all incoming calls and to block any anonymous callers. Advanced Screening and Routing rules allow subscribers greater flexibility in directing incoming calls. Advanced routing allows subscribers to program a ring list to: - ring several devices at once (simultaneous) - ring different devices in a specific order (sequential) - automatically send a Web page or request for an to a caller - send an instant message You must enable the Advanced Screening service before subscribers can configure the parameters required to enable advanced screening. Call Subjects: Using this feature, subscribers can send text messages when they make a call. Soft client users can locally save text messages in a drop-down list for reuse. Call Transfer: Using any supported client, subscribers can transfer an active call to another destination. The subscriber can choose to complete the transfer directly without speaking to the third party receiving the transferred call (blind transfer) or speak to the third party before completing the transfer (consultative transfer). Subscribers can select destination addresses from their address book, inbox, and outbox (where applicable) Call Type Based Screening: Subscribers can screen a call based on the dialing patterns (for example, local, long distance, international, or premium calls). Call Waiting and Call Waiting Disable: Subscribers can receive an incoming call on a line that is engaged in another call. All access clients display caller ID information for incoming calls. Call October 2017 Avaya Aura Application Server 5300 Overview 64

65 Features associated with access clients and devices handling options allow subscribers to answer, decline, ignore, instant message, or redirect the second incoming call. The administrator can disable the Call Waiting service and make the feature unavailable to subscribers. Call Waiting must be provisioned before you can disable it. Caller ID: Administrators provision the caller ID information displayed by incoming (SIP) calls. Incoming PSTN or Gateway calls display the telephone number. If a caller is a contact in the receiver s personal address book, then the caller s nickname (for SIP-to-SIP calls) appears. Calling Line ID Restriction: Calling line identification allows subscribers to specify whether their name and number appear when they make calls. A administrator enables this parameter in the service package in order for subscribers to configure the service in their Personal Agents. Click to Call: Click to Call provides subscribers with the ability to click an entry in their personal address book or global address book, and then place a call to that entry. Decline, Ignore, and Redirect: - The Decline feature is available for incoming calls. The Decline feature allows you to specify a reason for declining a call. - The Ignore feature allows subscribers to stop their clients from ringing. The subscriber must configure a call routing list in order to use this feature. - The Redirect feature lets subscribers choose to redirect incoming ringing calls. When selected, this service prompts the subscriber to either enter a destination address or select an entry in the address book, inbox, or outbox (where applicable). Do Not Disturb: The Personal Agent provides a flexible tool with which subscribers can handle incoming calls on a network level. Subscribers also have the ability to locally block calls on a particular client. The local Do Not Disturb (DND) feature blocks all incoming calls from ringing at the client where it is provisioned. If the subscriber has other devices defined in the ring list, then those devices continue to ring. Otherwise, the call passes to the next ring list. The DND feature also blocks incoming instant messages. Fixed Mobile Extension: Fixed Mobile Extension provides mobile handsets with a level of call feature capability normally associated with fixed SIP devices such as phones, terminal adapters, and soft clients. Hold: The Hold feature allows subscribers to interrupt an active call so that both the incoming and outgoing voice and video are suspended. All access clients have a button to place calls on hold. Subscribers can automatically activate the hold feature by switching between two active calls. Hotline: This feature lets administrators designate an IP Deskphone as a hotline that calls a specific address when taken off-hook. Hotline is associated with a user ID rather than a particular device. A system administrator enables the hotline service parameter for a user ID. Any IP Deskphone that this user ID logs on to becomes a hotline device. For more information, see Avaya 1100 Series IP Deskphones on page 175. Hunting and Hunt Groups: Hunting is a feature that allows businesses to improve call completion rates in an office where multiple individuals may answer incoming calls or video session initiations. To enable the Hunting feature, the customer service agents of a business are clustered in groups called hunt groups. A hunt group is organized in such a manner that when an incoming call or video session is presented to a hunt group member who is October 2017 Avaya Aura Application Server 5300 Overview 65

66 Features and services unavailable, hunting is automatically performed within the group for another member who is available. Group members are considered available if they are not currently engaged in a call or session with any of their SIP clients. Group members are considered unavailable if any of their registered devices are busy, set to Do Not Disturb state, or have an Unavailable Busy presence state. Two types of hunting are available: - Circular hunting: searches for an available hunt group member by starting with a particular group member and hunting for the next available group member. If no available member is found after searching the entire hunt group, hunting within the group stops. If all group members are unavailable, calls or sessions can be redirected to a specified destination, treatment, or announcement. - Sequential hunting: searches for an available hunt group member by starting with a particular group member and hunting through a prescribed sequence of group members for the next available group member. If no available member is found in the hunting sequence, hunting stops. If all group members are unavailable, calls or sessions can be redirected to a specified destination, treatment, or announcement. The system performs Hunting for any valid incoming call or video session. Inbox and Outbox: The client maintains a log of all incoming and outgoing calls. - Inbox buttons allow quick access to this log. Subscribers can access the log in order to call back, send an instant message, or save the entry to the address book. Inbox entries for missed calls are highlighted in the Avaya Aura AS 5300 UC Client, Avaya Aura AS 5300 Office Client, and AS 5300 Web Client inbox lists. IP Deskphones have an option that allows subscribers to toggle between the list of missed calls and the list of all calls in the inbox. - Outbox buttons allow quick access to this log. Subscribers can access the log in order to call back, send an instant message, or save the entry to the address book. Instant Messages: The Instant Messaging (IM) feature allows subscribers to exchange text messages with one or more other subscribers, even when in a call. You can send and receive instant messages from the Avaya Aura AS 5300 UC Client, AS 5300 Web Client, Avaya Aura AS 5300 Office Client, and Avaya Aura AS 5300 UC Client Set. Instant Messages are separate from IM capabilities provided by the Avaya Aura Media Server (MS). IM Broadcast allows a subscriber to send instant messages to multiple recipients simultaneously. To begin, a subscriber selects multiple recipients and then opens the IM Broadcast window. Subscribers can repeatedly send messages to all recipients while the window is open. The session remains open until the subscriber manually closes the window. Any replies to a broadcast message launches a new IM Conversation window from the individual replying to the broadcast message. The IM Broadcast window can send messages but it cannot receive messages. The Extensible Messaging and Presence Protocol (XMPP) Gateway optionally provides the ability to exchange IMs and presence information users in external communities. Location selection: Avaya Aura AS 5300 UC Client, AS 5300 Web Client, and IP Deskphone users can select the physical location of their clients. The system uses this location to route emergency calls. The system administrator enters information related to the Location service in the Provisioning Client. October 2017 Avaya Aura Application Server 5300 Overview 66

67 Features associated with access clients and devices Malicious Call Trace: The Malicious Call Trace (MCT) service lets subscribers initiate a call trace on an offensive call using a Vertical Service Code (VSC). Service providers have an option to activate automatic MCT for a subscriber. The automatic trace does not require subscriber initiation. Information collected includes the calling number or URL (even if privacy is configured against the calling party), the called number or URL, the last forwarding number or URL, the time and date of call, the duration of the call, whether the call is intradomain or interdomain, whether call waiting is active, and whether the calling number is configured to private. The information collected is not forwarded to the subscriber, but is handled according to best practices of the service provider, including being forwarded to law enforcement authorities, where appropriate. Personal Address Book, Global Address Book, and Friends: The Personal Address Book and Global Address Book provide subscribers with information about other subscribers. - The Personal Address Book is a subscriber's primary tool for managing addresses (both telephone numbers and SIP addresses). Subscribers can access and edit the personal address book from any client. A change to the address book (from any of the clients) updates the address book for all clients. - The Global Address Book is a system listing of subscribers on the Application Server This address book is built from a company's Lightweight Directory Access Protocol (LDAP) database, and contains information about each subscriber, including name and desk telephone number. - Friends: Within the Personal Address Book, subscribers can designate entries as Friends. If a subscriber includes the SIP address of someone in the list of Friends, then the subscriber can see the online Presence status of the friend in the list. The address books support searching. The Avaya Aura AS 5300 UC Client provides tools that enable subscribers to import contacts from Microsoft Outlook to their personal address books. Outlook contacts that subscribers add to their personal address books are synchronized with the network and are available to all of the subscriber s clients. Picture ID: Subscribers with soft clients can choose to display their own picture IDs to callers. Subscribers upload their pictures to the network using the Personal Agent. The picture ID appears when subscribers call another soft client subscriber. If there is no available picture of the subscriber, the system displays a silhouette of a person. Private and Public Name and Number Display: The Private And Public Name and Number Display feature allows the Application Server 5300 to display the caller s name and number, and applies to calls between SIP domains and to calls between SIP domains and TDM parties that are an extension of a common group. Selective Call Reject: Subscribers configure this service by creating lists to bar (blacklist) an incoming or outgoing call. Teen services: Teen service is not supported. Uniform Call Distribution: Uniform Call Distribution (UCD) is a feature that improves callcompletion rates by matching incoming calls to available answering locations. UCD service is often used in deployments where a number of answering agents can equally serve incoming calls. The service provides even distribution of incoming calls to a specific Listed Directory Number (LDN) or Uniform Resource Indicator (URI) over a group of subscribers, or agents, October 2017 Avaya Aura Application Server 5300 Overview 67

68 Features and services associated with that LDN or URI. This group of agents is called a Uniform Call Distribution (UCD) group. You can assign an agent to only one group at a time. Instant Messaging, Presence, and Presence-based routing The Instant Messaging (IM) feature allows subscribers to exchange messages with one or more recipients and is available even if a subscriber is in a call. Subscribers can send and receive instant messages using any supported soft client. Presence The Presence feature allows subscribers to monitor the online status of selected users on the SIP network. Subscribers can select from a list of Presence status labels to share with other network users. Subscribers can monitor (subscribe to) the Presence status of subscribers in the Friends list. Subscribers use this feature to monitor who is watching their presence status, and can configure Presence Watch Authorization to immediately notifiy the subscriber when a new watcher requests presence authorization. Thus, subscribers can make case-by-case, real-time decisions about who can monitor presence status. Subscribers can allow all subscribers to see the subscriber's presence status, and then block selected subscribers at a later time, and can switch between the two modes at any time. The Presence-based Routing feature determines how the system handles calls when the recipient device is in the Unavailable Busy state. This service allows subscribers to route calls to a specified destination when the subscriber's status is Unavailable Busy. The administrator must enable Advanced Screening before the user can use the Presence-based Routing parameter. IM and Presence communication with external communities When the Extensible Messaging and Presence Protocol (XMPP) Gateway is configured, subscribers can exchange IMs with users of external communities exchange presence status with users of external communities. The following restrictions apply to communication with external users: Application Server 5300 does not support Multiuser chat between subscribers and the external IM community. Subscribers can share a minimal set of emoticons with external community users. Multimedia services Multimedia services require the availability of a Avaya Media Server (MS). Avaya MS supports the following services: The Ad Hoc Conferencing service allows users to join multiple callers into a single line. Up to 20 callers can join an ad hoc conference. Users can initiate the conference call from any client. The user who originates the conference transfers calls to the conference server by clicking Join. Both audio and video Ad Hoc conferences are supported. October 2017 Avaya Aura Application Server 5300 Overview 68

69 Features associated with access clients and devices The Announcements service plays a recording for causes, and treatments. The IM Chat service allows users to create, join and participate in chat rooms. The MeetMe Conferencing Service allows user to set up a reservation-less conference. MeetMe Conferencing users have their own private conferencing resource available for meetings at any time. Use of the personal conference resource is controlled by the conference owner (chairperson), whom the administrator provisions with the service. Both audio and video Meet Me conferences are supported. The Music on Hold service plays music while a caller is on hold. It is possible to implement the Music On Hold service for the following types of hold: end user, transfer, and Call Park. This service continuously plays music for the user on hold. It does not restart the music for each new caller that a user puts on hold. The Unified Communications service provides Application Server 5300 users with a variety of telephony devices (for the IP Deskphones, Avaya Aura AS 5300 UC Client, AS 5300 Web Client, General Dynamics viper phones, or Public Service Telephone Network [PSTN] phones) to access a single mailbox. Messages deposited in this single mailbox can be mailed to a user s client. Users manage their account through a traditional Telephony User Interface (TUI) or though the web-based Personal Agent. For more information, see Avaya Aura Application Server 5300 Configuration, NN Sharing features Sharing (collaboration) features include the following services: Clipboard is a Sharing tool that allows Avaya Aura AS 5300 UC Client users to exchange Windows clipboard content. Users can share text, photos, drawings, Web bookmarks, and address books. The File Exchange tool allows users of the Avaya Aura AS 5300 Office Client and Avaya Aura AS 5300 UC Client service to share files. Web Co-browsing enables a sender to push information so that the receiver s web browser mirrors the activities of the sender s browser. Web co-browsing allows one user to drive another user s web browser. The regular Avaya Aura AS 5300 UC Client is supports Web cobrowsing. Web Push allows subscribers to display a web site on another subscriber s PC. Softclient users can send or receive a web site using this feature. If receivers accept the web push, their browser automatically launches and displays the web site. The Whiteboard is a sharing tool that allows softclient users to share a common drawing window where they can enter text and graphics. Vertical Service Codes A Vertical Service Code (VSC) is a sequence of numbers subscribers can use to access or interact with a feature. Among features that support VSCs, the most common functions are: enable, disable, October 2017 Avaya Aura Application Server 5300 Overview 69

70 Features and services and check status. Some VSCs perform actions specific to a feature, such as Voic _Retrieve, which accesses the subscriber s voic . Note: Most of the features controlled by VSCs can also be controlled using the Personal Agent. For many features, VSCs provide only a subset of the available configuration options, while in a small number of cases, VSCs provide functionality that is not available in the Personal Agent. Vertical service codes are often colloquially referred to as starcodes, calling feature codes, or CLASS codes. VSCs usually begin with a star (*) or pound (#). In some cases, VSCs can be accessed from rotary phones by dialing 11 instead of star (*). The following three tables describe VSCs and the features that support them: Features with VSCs on page 70 lists the features that have VSCs, and describes the VSC functionality available for each feature. VSC Treatments on page 72 describes the Treatments (announcements) that apply to each VSC. VSC Usage on page 74 describes how and when subscribers use each VSC. Table 12: Features with VSCs Service Ad Hoc Conferencing Anonymous Call Rejection Call Forward Conditional Call Forward Disable All Call Forward Immediate Call Forward to Voic Call Forward Variants Busy Description Allows subscribers to originate an AdHoc conference. Automatically rejects incoming calls when the calling number is withheld or the Privacy Indicator (Privacy Header) is configured to restrict the display of caller information. Enables or disabled both Call Forward Variants Busy and Call Forward Variants No Answer. Disables all forms of call forwarding except for Default Route. This option applies to Call Forward Immediate, Call Forward Variants, and Do Not Disturb, and can be used only by subscribers who have one of those services provisioned. Forwards all incoming calls to a specified DN. If the subscriber does not answer, or if the subscriber s primary endpoint is busy, this feature forwards calls to voic . The subscriber must have voic provisioned, or Call Forward to Voic cannot be enabled. Call Forward to Voic applies to Call Forward Immediate and Call Forward Variants, and can be used only by subscribers who have one of those services provisioned. If the subscriber s device is busy, this feature forwards incoming calls. Table continues October 2017 Avaya Aura Application Server 5300 Overview 70

71 Features associated with access clients and devices Service Call Forward Variants No Answer Call Grabber Call Pickup Call Return Call Type Based Screening Calling Line ID Deny All Calls Do Not Disturb Malicious Call Trace Network Call Waiting Disable Number of Rings Override Call Screening Temporarily Selective Call Reject Short Dialing Code Uniform Call Distribution Voic Retrieve Description If the subscriber does not answer, this feature forwards incoming calls. Allows subscribers to use an idle device to retrieve an active call from another device. Both devices must be registered to the subscriber, and must be in a common domain. Allows subscribers to pick up calls that are ringing on another subscriber s DN. Both subscribers must be members of a common Call Pickup Group. Displays information about the most recent incoming call, and allows the subscriber to return the call. Restricts outgoing calls according to call type, thereby blocking or permitting outgoing local, international, premium, or long-distance calls. Allows a caller to provide or conceal identifying information from the called party, irrespective of Privacy service configuration. Blocks all incoming or outgoing calls. Forwards calls to voic so that the subscriber is not disturbed. If voic is not in the subscriber s service package, the caller receives the text message "Do Not Disturb". Traces the current incoming call. Activate, deactivates, or performs a status check for Network Call Waiting Disable. When this feature is activated, Network Call Waiting is disabled, causing all incoming calls to be blocked when the subscriber has an active call, allowing the active call to continue without interruption. This feature can be enabled globally, or on a call-bycall basis. Note: When this VSC is active, the Network Call Waiting feature is disabled. Controls the number of times the system rings the subscriber s primary endpoint before redirecting to other routes, such as voic . This option applies to Call Forward Immediate and Call Forward Variants, and can be used only by subscribers who have one of those services provisioned. Also known as Rollover Timer. Temporarily overrides Call Screening, thereby allowing an outgoing call that would otherwise violate the current Call Screening policy. Blocks all incoming or outgoing calls from/to parties that you specify. A short dialing sequence that initiates a call to a destination previously provisioned by the administrator. Manages Uniform Call Distribution (UCD) groups and queues. Manages voic messages. Subscriber must have a mailbox ID and PIN. October 2017 Avaya Aura Application Server 5300 Overview 71

72 Features and services Treatment names and causes for VSC Use the following table to select the Treatment names and causes when assigning VSC Treatment Files to a domain. Table 13: VSC Treatments Treatment Name / reason Treatment cause Indicates that Used by VSCs associated with these features MCT_SUCCESS 498 Malicious Call Trace succeeded. Malicious Call Trace MCT_FAILURE 499 Malicious Call Trace failed. Malicious Call Trace STARCODE_STATUS_E NABLED STARCODE_STATUS_D ISABLED 1001 The VSC is enabled. Used by most VSCs 1002 The VSC is disabled. Used by most VSCs STARCODE_SUCCESS 1003 VSC execution succeeded. Used by most VSCs STARCODE_CLIR_PER _CALL_SUCCESS STARCODE_CLIP_PER _CALL_SUCCESS STARCODE_NCWD_PE R_CALL_SUCCESS STARCODE_CLI_SUCC ESS STARCODE_CLI_FAILU RE 1004 Calling Line ID Restriction Enable Per Call activated successfully Calling Line ID Presentation Per Call activated successfully Network Call Waiting Disable activated successfully Calling Line Identifier (CLI) Notification VSC has successfully identified the most recent caller Calling Line Identifier (CLI) Notification VSC failed because the most recent caller is anonymous or there is no information about the most recent caller. Calling Line ID Calling Line ID Network_Call_Waiting_D isable_per_call Call Return Call Return STARCODE_FAILURE 1009 VSC execution failed. Used by most VSCs ALL_INCOMING_CALL S_NOT_ALLOWED ALL_OUTGOING_CALL S_NOT_ALLOWED LOCAL_CALLS_NOT_A LLOWED 1050 Called party has Call Screening feature activated and forbids all incoming calls Calling party has Call Screening feature activated and forbids all outgoing calls Calling party has Call Screening feature activated and forbids local calls. Deny All Calls via VSC Deny All Calls via VSC Deny All Calls via VSC Table continues October 2017 Avaya Aura Application Server 5300 Overview 72

73 Features associated with access clients and devices Treatment Name / reason LONG_DISTANCE_CAL LS_NOT_ALLOWED INTERNATIONAL_CALL S_NOT_ALLOWED PREMIUM_CALLS_NOT _ALLOWED SELECTIVE_REJECT_I NCOMING SELECTIVE_REJECT_ OUTGOING Treatment cause Indicates that 1053 Calling party has Call Screening feature activated and forbids long distance calls Calling party has Call Screening feature activated and forbids international calls Calling party has Call Screening feature activated and forbids premium calls. Used by VSCs associated with these features Deny All Calls via VSC Deny All Calls via VSC Deny All Calls via VSC 1056 The calling party is banned. Selective Call Reject 1057 The called party is banned Selective Call Reject QUEUE_CLOSURE 1082 The UCD Group is closed, or the system cannot provide queuing service. QUEUE_MAXIMUM_SIZ E 1081 The maximum queue size of the UCD is exceeded. QUEUE_TIMEOUT 1080 A caller has been in the queue longer than the Maximum wait time, and the call is terminating. UCD_RINGBACK 1083 A caller is waiting in the queue. This treatment plays continuously while a caller waits in the queue (often a looping musical clip). If no treatment is provisioned, no sound plays. UCD_DELAY_ANNOUN CEMENT CALL_PICKUP_FORBID DEN NO_CALL_AVAILABLE_ FOR_PICKUP VSC usage 1084 A caller is waiting in the queue. This treatment plays periodically while the caller waits in the queue (for example Your call is important to us, please continue to hold ). If no treatment is provisioned, no sound plays Call Pickup is not permitted for the incoming call. Uniform Call Distribution Uniform Call Distribution Uniform Call Distribution Uniform Call Distribution Uniform Call Distribution Call Pickup 1091 No call available for pickup. Call Pickup The following table describes when and how subscribers can use each VSC. While VSCs can be dialed at any time, some can have an unwanted impact on active calls. The following table recommends the best time to use each VSC, as well as the duration of the VSC s effect. October 2017 Avaya Aura Application Server 5300 Overview 73

74 Features and services Table 14: VSC usage VSC Name and function Usage Effect duration Usage example Ad_Hoc_Conferencing_Enable (Enable Ad Hoc Conferencing) Ad_Hoc_Conferencing_Disable (Disable Ad Hoc Coferencing) Ad_Hoc_Conferencing_Check_ Status (Check the Status of Ad Hoc Conferencing) Add_DN_to_Incoming_Selectiv e_reject_list (Add a specified DN to the Incoming Selective Call Reject List) Add_DN_to_Outgoing_Selectiv e_reject_list (Add a specified DN to the Outgoing Selective Call Reject List) Add_Last_Inc_Call_to_Inc_Sel ective_reject_list (Add the last Incoming caller to the Incoming Selective Call Reject List) At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN, followed by pound (#), followed by the outgoing DN for which to block incoming calls. This blocks all calls whose username matches the value you enter, regardless of the domain to which they belong. For example, if you enter user1@demo.com, all callers named user1 are blocked, such as user1@otherdemo.com, and user1@demo.net. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN, followed by pound (#), followed by the outgoing DN for which to block outgoing calls. This blocks all calls whose username matches the value you enter, regardless of the domain to which they belong. For example, if you enter user1@demo.com, all callers named user1 are blocked, such as user1@otherdemo.com, and user1@demo.net When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. This blocks the DN of the last incoming caller. Until the subscriber changes the configuration. Until the subscriber changes the configuration. *1000 *1001 na *1002 Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. * om * om * Table continues October 2017 Avaya Aura Application Server 5300 Overview 74

75 Features associated with access clients and devices VSC Name and function Usage Effect duration Usage example Remove_DN_from_Incoming_ Selective_Reject_List (Remove a specified DN to the Incoming Selective Call Reject List) Remove_DN_from_Outgoing_ Selective_Reject_List (Remove a specified DN from the Outgoing Selective Call Reject List) Anonymous_Call_Rejection_En able (Enable Anonymous Call Rejection, thereby rejecting anonymous incoming calls) Anonymous_Call_Rejection_Di sable (Disable Anonymous Call Rejection, thereby allowing anonymous incoming calls) Anonymous_Call_Rejection_C heck_status (Check the status of Anonymous Call Rejection) Note: If you block a caller using Add_Last_Inc_Call_to_Inc_Selective_ Reject_List, you cannot remove that caller from the list using a VSC, but must use Personal Agent to do so. When not in a call, enter the prefix configured for this VSC, followed by the subscriber s PIN, followed by pound (#), followed by the outgoing DN from which to accept incoming calls. When not in a call, enter the prefix configured for this VSC, followed by the subscriber s PIN, followed by pound (#), followed by the outgoing DN for which to allow outgoing calls. At any time, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. * om * om *1113 *1114 na *1115 Call_Forward_Conditional_Ena ble (Enable both Call Forward Variants if Busy and Call Forward Variants No Answer ) Call_Forward_Conditional_Disa ble (Disable both Call Forward Variants if Busy and Call Forward Variants No Answer ) When not in a call, enter the prefix configured for this VSC, followed (optionally) by the DN to which calls are forwarded. If the subscriber does not specify a DN, the system uses a previously-configured DN, if available. When not in a call, enter the prefix configured for this VSC. Until the subscriber changes the configuration. Until the subscriber changes the configuration. *1116 OR *1116user 1@demo. com *1117 Table continues October 2017 Avaya Aura Application Server 5300 Overview 75

76 Features and services VSC Name and function Usage Effect duration Usage example Call_Forward_All_Disable (Disable all forms of Call Forwarding) Call_Forward_Immediate_Enab le (Enable Call Forward Immediate) Call_Forward_Immediate_Disa ble (Disable Call Forward Immediate) Call_Forward_Immediate_Chec k_status (Check the status of Call Forward Immediate) Call_Forward_Variants_To_Voi c _enable (Enable Call Forward to Voic ) Call_Forward_Variants_To_Voi c _disable (Disable Call Forward to Voic ) Call_Forward_Variants_To_Voi c _check_status (Check the status of Call Forward to Voic ) Call_Forward_Variants_Busy_ Enable (Enable Call Forward Busy) When not in a call, enter the prefix configured for this VSC. Call Forward Immediate, Call Forward Variants, and Do Not Disturb are disabled. When not in a call, enter the prefix configured for this VSC, followed (optionally) by the DN to which calls are forwarded. If the subscriber does not specify a DN, the system uses a previously-configured DN, if available. When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, followed (optionally) by the DN to which calls are forwarded when the subscriber s primary endpoint is busy. If the subscriber does not specify a DN, the system uses a previously-configured DN, if available. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. *1118 *1220 OR *1220user 1@demo. com *1221 na *1222 Until the subscriber changes the configuration. Until the subscriber changes the configuration. *1223 *1224 na *1227 Until the subscriber changes the configuration. *1228 OR *1228user 1@demo. com Table continues October 2017 Avaya Aura Application Server 5300 Overview 76

77 Features associated with access clients and devices VSC Name and function Usage Effect duration Usage example Call_Forward_Variants_Busy_ Disable (Disable Call Forwarding Busy) Call_Forward_Variants_Busy_ Check_Status (Check the status of Call Forward Busy) Call_Forward_Variants_No_An swer_enable (Enable Call Forward No Answer) Call_Forward_Variants_No_An swer_disable (Disable Call Forward No Answer) Call_Forward_Variants_No_An swer_check_status (Check the status of Call Forward No Answer) Call_Grabber (Retrieve a call form the subscriber s other device) Call_Pickup_Agent_Active (Activate Call Pickup Agent) Call_Pickup_Agent_Inactive (Deactivate Call Pickup Agent) Call_Pickup_Check_Agent_Sta tus (Check the status of Call Pickup Agent) Call_Pickup_for_GroupDN/ UserDN (Answer a call that is incoming on a Call Pickup Group, or on another subscriber s phone) When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, following (optionally) by the DN to which unanswered calls are to be forwarded. If the subscriber does not specify a DN, the system uses a previouslyconfigured DN, if available. When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. When a call is active on the subscriber s other device, use an idle device to enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, followed by the GroupID from which to retrieve the call. OR Until the subscriber changes the configuration. *1330 na *1331 Until the subscriber changes the configuration. Until the subscriber changes the configuration. *1332 OR *1332user 1@demo. com *1333 na *1334 For the duration of the current call. Until the subscriber changes the configuration. Until the subscriber changes the configuration. *1350 *1398 *1399 na *1400 For the duration of the incoming call. *1405user 1@demo. com OR Table continues October 2017 Avaya Aura Application Server 5300 Overview 77

78 Features and services VSC Name and function Usage Effect duration Usage example Call_Return_Enable (Enable Call Return) Call_Return_Disable (Disable Call Return) When not in a call, enter the prefix configured for this VSC, followed by the DN from which to retrieve the call. When not in a call, enter the prefix configured for this VSC, followed by a the subscriber s VSC PIN. When not in a call, enter the prefix configured for this VSC, followed by a the subscriber s VSC PIN. Note: After disabling Call Return, clear the Calling Line Identifier (CLI) using the Call_Return_CLI_Erase VSC. Until the subscriber changes the configuration. Until the subscriber changes the configuration. * * * Call_Return_Check_Status (Check the status of Call Return) Call_Return_CLI_Notification (Display information about the last incoming call, and optionally dial the last caller) Call_Return_CLI_Erase (Erase information about the last incoming call) Call_Return_Immediate At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. After the system provides information about the last call, enter the Calling Line Identifier number (c). The system dials the last caller. The default value is 3. Note: If Call_Return_CLI_Erase has been activated since the last call, Call_Return_CLI_Notification produces an error, and the call is not returned. Note: Call_Return_CLI_Notification supports only specific clients. Ask your next level of support if this feature is available on your client. When not in a call, enter the prefix configured for this VSC. This erases the Calling Line Identifier. When not in a call, enter the prefix configured for this VSC. The system na *1443 na *1444 (delay) 3 Until new incoming call *1445 na *1448 Table continues October 2017 Avaya Aura Application Server 5300 Overview 78

79 Features associated with access clients and devices VSC Name and function Usage Effect duration Usage example (Dial the last incoming call) immediately dials the last incoming DN. Note: If Call_Return_CLI_Erase has been activated since the last call, Call_Return_Immediate produces an error, and the call is not returned. Calling_Line_ID_Restriction_E nable (Enable Calling Line ID Restriction) Calling_Line_ID_Restriction_pe r_call (Place a call anonymously) Calling_Line_ID_Restriction_Di sable (Enable Calling Line ID Restriction) Calling_Line_ID_Presentation_ per_call (Override Calling Line ID Restriction, and place one outgoing call with identifying information) Calling_Line_ID_Restriction_C heck_status (Check the status of Calling Line ID Restriction) Deny_All_Incoming_Calls_Ena ble (Enable Deny All Incoming Calls) Deny_All_Outgoing_Calls_Ena ble (Enable Deny All Outgoing Calls) When not in a call, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, followed by the DN to call without sending identifying information. When not in a call, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, followed by the DN to dial. Identifying information about the sender is supplied to the call recipient. At any time, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC, followed by the subscriber s PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber s PIN. Until the subscriber changes the configuration. For the duration of the next outgoing call to the specified DN. Until the subscriber changes the configuration. For the duration of the next outgoing call to the specified DN. *1449 *1550user 1@demo. com *1551 *1553user 1@demo. com na *1555 Until the subscriber changes the configuration. Until the subscriber changes the configuration. * * Table continues October 2017 Avaya Aura Application Server 5300 Overview 79

80 Features and services VSC Name and function Usage Effect duration Usage example Deny_All_Incoming_Calls_Disa ble (Disable Deny All Incoming Calls) Deny_All_Outgoing_Calls_Disa ble (Disable Deny All Outgoing Calls) Do_Not_Disturb_Enable (Enable Do Not Disturb) Do_Not_Disturb_Disable (Disable Do Not Disturb) Do_Not_Disturb_Check_Status (Check the status of Do Not Dusturb) Malicious_Call_Trace (Trace the source of an incoming call) Network_Call_Waiting_Disable (Disable Network Call Waiting) Network_Call_Waiting_Disable _per_call (Disable Network Call Waiting for the duration of the next outgoing call) Network_Call_Waiting_Enable (Enable Network Call Waiting) Network_Call_Waiting_Check_ Status When not in a call, enter the prefix configured for this VSC, followed by the subscriber s PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber s PIN. When not in a call, enter the prefix configured for this VSC. When not in a call, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. During or after a call, enter the prefix configured for this VSC. Note: Check with your service provider to determine if this feature is available to you both during and after a call. When not in a call, enter the prefix configured for this VSC. Note that activating this VSC disables Network Call Waiting. When not in a call, enter the prefix configured for this VSC, followed by the DN to call. When not in a call, enter the prefix configured for this VSC. Note that activating this VSC enables Network Call Waiting, by deactivating Network Call Waiting Disable. At any time, enter the prefix configured for this VSC. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. * * *1561 *1562 na *1563 na *1565 Until the subscriber changes the configuration. For the duration of one outgoing call to the specified DN. Until the subscriber changes the configuration. *1567 *1568user 1@demo. com *1570 na *1772 Table continues October 2017 Avaya Aura Application Server 5300 Overview 80

81 Features associated with access clients and devices VSC Name and function Usage Effect duration Usage example (Check the status of Network Call Waiting) Number_Of_Rings (Rollover Timer) (Configure the number of times to ring a device before trying the next route, or going to voic ) Outgoing_International_Calls_ Enable (Enable Outgoing International Calls) Outgoing_International_Calls_ Disable (Disable Outgoing International Calls) Outgoing_Local_Calls_Enable (Enable Outgoing Local Calls) Outgoing_Local_Calls_Disable (Disable Outgoing Local Calls) Outgoing_Premium_Calls_Ena ble (Enable Outgoing Premium Calls) Outgoing_Premium_Calls_Disa ble (Disable Outgoing Premium Calls) Outgoing_Long_Distance_Intra _RA_Calls_Enable (Enable Outgoing Long Distance Intra RA calls) When not in a call, enter the prefix configured for this VSC, followed by the number of rings the system waits, in the range of 1 9. Default value is 4. Note: The VSC prefix you enter for this VSC must not be a substring of any other VSC prefixes defined. For example if you have defined the VSC prefix *110 for another service, do not define the prefix for Number of Rings as *1 or *11. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. *17753 (Changes the Number of Rings to 3) *1800 * * * * * * Table continues October 2017 Avaya Aura Application Server 5300 Overview 81

82 Features and services VSC Name and function Usage Effect duration Usage example Outgoing_Long_Distance_Intra _RA_Calls_Disable (Disable Outgoing Long Distance Intra RA calls) Outgoing_Long_Distance_Inter _RA_Calls_Enable (Enable Outgoing Long Distance Inter RA call) Outgoing_Long_Distance_Inter _RA_Calls_Disable (Disable Outgoing Long Distance Inter RA calls) Override_Call_Screening_Tem porarily_enable (Temporarily override Call Screening) Short Dialing Code (Dial a pre-configured DN, using a short code) Note: When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN. When not in a call, enter the prefix configured for this VSC, followed by the subscriber's PIN, followed by the DN to dial. At any time, enter the prefix configured for this VSC. Until the subscriber changes the configuration. Until the subscriber changes the configuration. Until the subscriber changes the configuration. For the duration of the specified call. Dials one outgoing call. * * * * Short Dialing Code does not appear in the Provisioning Name list of the Vertical Service Code portlet, but is similar in function to other VSCs. Select a VSC prefix that is not used by (or a substring of) other VSCs. UCD_Subscriber_Active (Activate UCD for the UCD group of which the subscriber is a member) UCD_Subscriber_Inactive (Deactivate UCD for the UCD group of which the subscriber is a member) UCD_Subscriber_Check_Statu s (Check whether UCD is active for the UCD group of which the subscriber is a member) UCD_Queue_Active (Activate a UCD Queue) At any time, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. At any time, enter the prefix configured for this VSC. If you are a subscriber, at any time, enter the prefix configured for this VSC. Until the subscriber changes the configuration. Until the subscriber changes the configuration. *187 *1880 *1881 na *1882 Until the subscriber changes the configuration. *1883 (if you are an agent) Table continues October 2017 Avaya Aura Application Server 5300 Overview 82

83 Features associated with access clients and devices VSC Name and function Usage Effect duration Usage example OR OR If you are an administrator, at any time, enter the prefix configured for this VSC, followed by the UCD GroupID to activate. *1883ucd demo.co m (if you are an administr ator) UCD_Queue_Inactive (Deactivate a UCD Queue) If you are a subscriber, at any time, enter the prefix configured for this VSC. Until the subscriber changes the configuration. *1884 (if you are an agent) OR OR If you are an administrator, at any time, enter the prefix configured for this VSC, followed by the UCD GroupID to deactivate. *1884ucd group1@ demo.co m (if you are an administr ator) UCD_Queue_Check_Status (Check the status of a UCD Queue) If you are a subscriber, at any time, enter the prefix configured for this VSC. OR na *1885 (if you are an agent) OR Voic _Retrieve (Retrieve voic messages) If you are an administrator, at any time, enter the prefix configured for this VSC, followed by the UCD GroupID for which to check the status. When not in a call, enter the prefix configured for this VSC. *1885ucd group1@ demo.co m (if you are an administr ator) na *1895 October 2017 Avaya Aura Application Server 5300 Overview 83

84 Chapter 11: Interfaces and communication protocols This chapter describes the interfaces and protocols that Application Server 5300 uses to communicate between its core components and the end users. Navigation Hypertext Transfer Protocol on page 84 Hypertext Transfer Protocol over Transport Layer Security on page 85 Internet Protocol Secure on page 85 Secure File Transfer Protocol on page 85 Session Initiation Protocol on page 85 Simple Network Management Protocol version 2c on page 85 Simple Object Access Protocol on page 86 Structured Query Language on page 86 Transmission Control Protocol/Internet Protocol on page 86 User Datagram Protocol on page 87 Other network protocols on page 87 Application Programming Interfaces on page 88 IP addressing on page 89 Hypertext Transfer Protocol The Provisioning Manager interfaces with external clients and Open Provisioning Interface (OPI) clients using Hypertext Transfer Protocol (HTTP). October 2017 Avaya Aura Application Server 5300 Overview 84

85 Hypertext Transfer Protocol over Transport Layer Security Hypertext Transfer Protocol over Transport Layer Security The Provisioning Manager interfaces with subscriber clients using Hypertext Transfer Protocol over Transport Layer Security (HTTPS). HTTPS provides authentication, data confidentiality, and data integrity protection. The Web-based access clients use HTTPS to communicate with the Web server portion of the Provisioning Manager to enable browser-based communication sessions. The Provisioning Manager transmits the following types of information transmitted: service provider provisioning, customer domain provisioning, subscriber self-provisioning, and user network-based service capabilities. Internet Protocol Secure The system uses Internet Protocol Secure (IPsec) to protect Application Server 5300 internal communications. IPsec uses information contained in the message header to authenticate the originating address of a message. The message contents are encrypted to secure the packet. Secure File Transfer Protocol The system uses Secure File Transfer Protocol (SFTP) to transfer data from the AS 5300 Element Manager to a northbound management system for logs and operational measurements (OMs). Session Initiation Protocol The Provisioning Manager interfaces with the AS 5300 Session Manager by using the Session Initiation Protocol (SIP). The Provisioning Manager uses this interface to notify the AS 5300 Session Manager of provisioning data changes to the Address Book and Monitored Users. The Avaya 1100 Series IP Deskphones with SIP Firmware communicate with the AS 5300 Session Manager using SIP. Simple Network Management Protocol version 2c The system uses Simple Network Management Protocol version 2c (SNMPv2c) to poll the AS 5300 Element Manager for alarm events. The system can also use SNMPv2c polling to report Application Server 5300 alarms to an existing network management system. October 2017 Avaya Aura Application Server 5300 Overview 85

86 Interfaces and communication protocols Simple Object Access Protocol Simple Object Access Protocol (SOAP) is an XML-based lightweight protocol for the exchange of information in a decentralized, distributed environment. The system uses SOAP to communicate requests to the AS 5300 Element Manager over TCP. You can use Transport Layer Security (TLS) to secure SOAP. The Provisioning Manager interfaces with the subscriber clients by using SOAP. SOAP is an XMLbased, lightweight protocol for exchange of information in a decentralized, distributed environment. The implementation uses HTTPS rather than HTTP for security. The Provisioning Manager acts as a SOAP client to connect to Avaya Media Server servers to get data from them. The Open Provisioning Interface (OPI) uses SOAP for connections to external Operation Support System (OSS). The Provisioning Manager depends on Apache Axis 1.1 Final (Web Services Toolkit for SOAP Implementation) and Crimson (XML Parser that is part of Sun Microsystems Java Development Kit 1.4.2). Non-Application Server 5300 applications (such as order management systems) use OPI to get access to the database through the Provisioning Manager. Structured Query Language The system uses Structured Query Language (SQL) over a Java Database Connectivity (JDBC) to store and retrieve system configuration data between the AS 5300 Element Manager and the Database Manager. Secure communication between the AS 5300 Element Manager and Database Manager takes place using Secure TCP. The Provisioning Manager interfaces with the Database Manager using Structured Query Language (SQL) over JDBC. The system uses SQL all database communications. Transmission Control Protocol/Internet Protocol The AS 5300 Element Manager uses Transmission Control Protocol/Internet Protocol (TCP/IP) to communicate management and configuration data to each of the managed network elements. The managed network elements use TCP/IP to communicate performance data, logs, and alarms upwards to the AS 5300 Element Manager or Fault Performance Manager. The Provisioning Manager transmits configuration data, performance data, logs, and alarms to the AS 5300 Element Manager using Transmission Control Protocol (TCP). The Provisioning Manager also uses TCP to notify other network elements of provisioning changes. The system secures these TCP connections with Secure Sockets Layer (SSL). Application Server 5300 uses secure versions of TCP and IP, called Secure Transmission Control Protocol and IP Security (IPsec). October 2017 Avaya Aura Application Server 5300 Overview 86

87 User Datagram Protocol User Datagram Protocol The system uses User Datagram Protocol (UDP) to transmit heartbeats. OSSEC agents use UDP (with a symmetric key for encryption) to communicate with the OSSEC Server. Other network protocols The following table shows other protocols Application Server 5300 uses to communicate with its components and network elements. The system uses these network protocols to report logs and alarms, to allow provisioning of services, and to communicate configuration data. As well, the table shows the external or northbound protocols the system uses to communicate with its components and network elements. Table 15: Internal communication protocols Network protocol Data Transfer Protocol Open Provisioning Interface (OPI) Primary Rate Interface (PRI) Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP) Secure File Transfer Protocol (SFTP) Protocol function The data transfer protocol is a Avaya-proprietary protocol. This protocol uses socket-based TCP/IP communication to transmit collected accounting information from the AS 5300 Session Manager to the Accounting Manager, and to provide acknowledgment of the information received from the Accounting Manager to the AS 5300 Session Manager. Based on the SOAP protocol message structure, encoding style, and messaging rules, the OPI is a Web service that exposes XML remote procedure calls, to enable the provisioning clients to access the provisioning data. OPI uses HTTPS as its transport protocol. Avaya Aura AS 5300 Office Client, Avaya Aura AS 5300 UC Client, and third-party applications use OPI to retrieve, modify, or store provisioning data. OPI integrates the Provisioning Manager with non- Application Server 5300 applications, such as Customer Records Management (CRM) systems. The PRI Gateway performs SIP-to-PRI and PRI-to-SIP protocol conversions to provide access to and from PSTN and PBX callers. The RTP is used to provide audio and video streaming capabilities for SIP call sessions. The system uses RTCP to pass statistical data about SIP call session connections between endpoints. SFTP transfers data from the AS 5300 Element Manager to a northbound management system for logs, Operational Table continues October 2017 Avaya Aura Application Server 5300 Overview 87

88 Interfaces and communication protocols Network protocol Secure Real-time Transport Protocol (SRTP) and Secure Real-time Transport Control Protocol (SRTCP) Session Description Protocol (SDP) Simple Network Management Protocol version 2c (SNMPv2c) SIP over Transmission Control Protocol (TCP) and Transport Layer Security (TLS) Subscriber Open Provisioning Interface (SOPI) Transmission Control Protocol (TCP) Protocol function Measurements, and Performance Measurements (OM and PM). It also transfers accounting data from the Accounting Manager to a northbound management system. The SRTP can be used to provide secure audio and video streaming capabilities for SIP call sessions. The system uses SRTCP to pass statistical data about SIP call session connections between endpoints. Session Initiation Protocol (SIP) uses the offer and answer model and Session Description Protocol (SDP) to establish and update multimedia sessions. The AS 5300 Element Manager uses SNMPv2c and the Avaya reliable fault management information base (MIB) to send traps to its northbound network management system. SNMPv2c is secured using IPsec. SIP is a service-enabling protocol used for real-time, multimedia sessions to integrate voice, data, and video. The AS 5300 Session Manager can use SIP over TLS as a secure signaling protocol to communicate with the PRI Gateway, Provisioning Manager, Avaya Aura AS 5300 UC Client, Avaya Aura AS 5300 Office Client, 1120E IP Deskphone, 1140E IP Deskphone, and Avaya Aura Media Server. SOPI provides an Application Interface using HTTPS for access to the Personal Agent, Avaya Aura AS 5300 Office Client, and Avaya Aura AS 5300 UC Client operations. TCP is used to communicate configuration, performance data, logs, and alarms between the network components and the AS 5300 Element Manager. TCP is secured using IPsec. Application Programming Interfaces Application Server 5300 provides the following Application Programming Interfaces (API): Open Provisioning Interface on page 89 Subscriber Open Provisioning Interface on page 89 For further information, see Avaya Aura Application Server 5300 Application Programming Interfaces Reference, NN Information and support for the APIs are available through the Avaya Developer Partner Program (DPP). October 2017 Avaya Aura Application Server 5300 Overview 88

89 IP addressing Open Provisioning Interface With the Open Provisioning Interface (OPI) you can remotely provision the Application Server OPI uses HTTPS to secure data. Subscriber Open Provisioning Interface The Subscriber Open Provisioning Interface (SOPI) provides an API for access to the AS 5300 Personal Agent, Avaya Aura AS 5300 Office Client, and Avaya Aura AS 5300 UC Client operations. SOPI is based on Java. You can use SOPI to build third-party clients and customer Web portals, and can control access to SOPI functionality through service packages. SOPI uses HTTPS to secure data. IP addressing This section describes the following types of IP addressing: IPv4 addressing on page 89 IPv6 addressing on page 90 IP addressing support in the Application Server 5300 solution on page 92 For information about the planning and engineering aspects of IP addressing for Application Server 5300, see Avaya Aura Application Server 5300 Planning and Engineering, NN IPv4 addressing The requirements for planning single subnet Application Server 5300 SIP core elements IP addresses are summarized in the following table, where A stands for an active NE and S represents a standby NE. The server addresses can be shared by all NEs co-located on the same server (for example, a small configuration SIP core server), but all services addresses must be unique for the specific network element type (for example, AS 5300 Session Manager, EM). They are not shared among different network elements. Table 16: IP addressing single subnet requirements Network Elements Server Address OAM Service Address Signaling Service Address SESM (A) yes yes Table continues October 2017 Avaya Aura Application Server 5300 Overview 89

90 Interfaces and communication protocols Network Elements Server Address OAM Service Address Signaling Service Address SESM (S) yes EM (A) yes yes EM (S) yes FPM (S) yes yes FPM (S) DB (A) DB (S) yes yes yes AM (A) yes yes AM (S) PROV PA yes yes yes The IP addressing requirements for the MultiSubnet configuration are shown in the following table. Table 17: Multisubnet server IP addressing Network Elements Internal OAM Server Address External OAM Server Address Signaling Server Address Internal OAM Service Address External OAM Service Address SESM (A) yes yes yes SESM (S) yes yes EM (A) yes yes yes yes EM (S) yes yes FPM (S) yes yes yes yes FPM (S) yes yes DB (A) DB (S) yes yes AM (A) yes yes yes yes AM (S) yes yes PROV yes yes yes PA yes yes Signaling Service Address IPv6 addressing Application Server 5300 provides IPv6 communications on the SIP and Media interfaces that communicate with end clients. The OAMP interfaces for all Application Server 5300 network elements remain IPv4 only. Currently, only AS 5300 Session Manager supports IPv6 SIP Signaling. October 2017 Avaya Aura Application Server 5300 Overview 90

91 IP addressing The Avaya MS and PRI GW only support IPv6 for media. Signaling between AS 5300 Session Manager and the Avaya MS and PRI GW is over IPv4 transport, but the SIP SDP Media lines grouped using ANAT (Alternative Network Address Types) semantics provide alternative IPv4 and IPv6 network addresses types for negotiating a media stream address type. The preference for IPv6 or IPv4 media is controlled by either placing IPv6 or IPv4 first in SDP ANAT field. If an IPv4 media stream is preferred, the IPv4 must appear first in the SDP ANAT field. Table 18: Application Server 5300 IPv4 and IPv6 support Signaling Media OAMP AS 5300 SESM IPv4, IPv6 IPv4 Only EM FPM DB AM PROV PA IPv4 Only IPv4 Only IPv4 Only IPv4 Only IPv4 Only IPv4 Only PRI GW IPv4 Only IPv4, IPv6 IPv4 Only Avaya Media Server IPv4 Only IPv4, IPv6 IPv4 Only 1120E IP Deskphone 1140E IP Deskphone IPv4, IPv6 IPv4, IPv6 IPv4 Only Audiocodes MP500 IPv4, IPv6 IPv4, IPv6 IPv4 Only Avaya Aura AS 5300 UC Client IPv4, IPv6 IPv4, IPv6 IPv4 Only Because some clients do not support IPv6 SDP ANAT extension, AS 5300 Session Manager first checks the SIP profile of the terminating client when the SDP contains ANAT header for IPv6. If the terminating client SIP profile does not support SDP ANAT, AS 5300 SESM assumes this client is incapable to process IPv6/SPD ANAT. The SDP ANAT header in SIP INVITE will be removed and only IPv4 media will be set in SDP. When 200 OK is received from IPv4 only client, AS 5300 SESM will add the SDP IPv6 ANAT header back to the SDP when sending it back to the originating client. If SDP ANAT support of the client SIP profile is set to true, but a 420 response received from the terminating client, AS 5300 Session Manager assumes that the terminating client does not support SDP ANAT for IPv6. As Avaya MS and Media Gateway do not resend INVITE upon failing to setup call with an IPv6 SDP ANAT capable client, AS 5300 SESM will resend INVITE that contains IPv4 only SDP. The default setting of SDP ANAT is false for all client SIP profile, which means the client does not support SDP ANAT. The administrator can modify the client SIP profile setting using AS 5300 Element Manager Console GUI, if the client supports SDP ANAT. The newer version of AS 5300 SESM in Release 3.0 supports IPv6 SDP ANAT extension. When a call from the originating client uses ANAT in SDP with both AS 5300 SESM and terminating client supporting ANAT, the originating client establishes the call successfully with the terminating client without the 420 response. October 2017 Avaya Aura Application Server 5300 Overview 91

92 Interfaces and communication protocols For older versions of AS 5300 Session Manager that does not support ANAT, when a call from the originating client contains an IPv6 with ANAT, AS 5300 SESM sends 420 response to the originating client telling that AS 5300 SESM does not support ANAT. The originating client then removes the ANAT and resends the INVITE which is received by AS 5300 SESM with IPv4 only media and hence establishes a call with the terminating client successfully. IPv6 configuration for Application Server 5300 server and AS 5300 SESM service address need to be performed after the system is fully installed. For each IPv6 server there needs to be an IPv6 server address configured and for each active AS 5300 SESM there needs to be an IPv6 service address configured. The server address allows debugging of the IPv6 network and is not used for signaling. The IPv6 service address is used for SIP signaling. IPv6 uses the same port numbers configured for IPv4 for IPv6 SIP transport. The configuration of these addresses is accomplished by running the ipv6config script as opposed to using AS 5300 Element Manager Console GUI for IPv4 address configuration. Application Server 5300 controls the availability of IPv6 through a license key. IPv4/IPv6 Dual-Stack feature must be enabled using the license key for AS 5300 SESM to bring up IPv6 service address for signaling. If the feature is not enabled, an IPv6 SESM Service Address is not brought up regardless of configuration. The detail configuration procedure is described in a separate document. IP addressing support in the Application Server 5300 solution The following figure describes the communication paths in the Application Server 5300 solution, and the type of IP addressing supported. October 2017 Avaya Aura Application Server 5300 Overview 92

93 IP addressing Figure 10: Application Server 5300 communication paths and IP addressing The following table describes the IPv6 addressing constraints for specific components in the Application Server 5300 solution. Table 19: IP addressing support Component 1120E IP Deskphone and 1140E IP Deskphone Avaya Media Server (MS) AudioCodes gateway IPv6 support constraints Only supported by SIP firmware Only supported for media paths Only supported for media paths License keys control the use of IPv6 on the Application Server Important: If the system needs to be restored from a backup, IPv6 must be reconfigured. The backup does not include IPv6 information. IPv6 promotes security, configuration, database persistence, and robustness. An Application Server 5300 IPv6 license key controls the ability to use IPv6. If licensed, the IPv6 Dual Stack is enabled after AS 5300 Session Manager deployment. October 2017 Avaya Aura Application Server 5300 Overview 93

94 Interfaces and communication protocols For IPv6 to function correctly in the customer network, all endpoints in the network must be IPv6- capable. When IPv6 is not enabled, communication uses IPv4. The following table describes the communication paths and the IP version in use. Table 20: Communication paths and IP addressing versions To From Admin PC Provisioning Manager, Personal Agent Manager AS 5300 Elemen t Manage r AS 5300 Session Manage r Avaya MS Media Gatew ay Subsc riber PC Admin PC IPv4 IPv4 n/a n/a n/a n/a n/a Provisioning Manager, Personal Agent Manager AS 5300 Element Manager AS 5300 Session Manager IPv4 IPv4 IPv4 n/a n/a IPv4 n/a IPv4 IPv4 IPv4 n/a n/a n/a n/a IP Deskph ones n/a IPv4 IPv4 IPv4 IPv4 IPv4 IPv6/ IPv4 Signalin g Avaya MS n/a n/a n/a IPv4 IPv6/ IPv4 Media Media Gateway n/a n/a n/a IPv4 IPv6/ IPv4 Media Subscriber PC n/a IPv4 n/a IPv4 n/a n/a IPv4 IP Deskphones n/a n/a n/a IPv6/ IPv4 Signalin g n/a IPv6/ IPv4 Media n/a n/a IPv4 IPv6/ IPv4 Media IPv6/ IPv4 Media The Security System Administrator (SSA) enables IPv6 by executing the ipv6config script on the server. IPv6 cannot be enabled from the AS 5300 Element Manager Console. For information on the ipv6config script, see Avaya Aura Application Server 5300 Security, NN October 2017 Avaya Aura Application Server 5300 Overview 94

95 Chapter 12: Configuration and administration This chapter describes Application Server 5300 configuration and administration concepts. For configuration and administration procedures, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Administration, NN For information about security-related configuration, see Avaya Aura Application Server 5300 Security, NN Navigation Domains on page 95 Services on page 98 Service profiles and service sets on page 98 Service nodes on page 99 Licensing and keycoding on page 100 Domains A domain serves as a control mechanism for users, services, devices, and translation. You use the Provisioning Client to provision domains. You can define domains and the service sets available for a given domain by provisioning domains. After you define a domain and service sets, you can define subdomains and assign the following components: service profiles to service sets service sets to domains and users translation information specific to a domain or a subdomain If you have full domain access, you can see all provisioned domains. Otherwise, you see only the domains or subdomains you are provisioned against. The management rights assigned to your account dictate the control you have over domains. After you create a domain (including the system domain created by the system administrator), the domain automatically creates a default location (called other). Because other is the only location present when you create a domain, it is the initial default location for the domain. October 2017 Avaya Aura Application Server 5300 Overview 95

96 Configuration and administration Domain types The types of domains are: local domain: A local domain is a domain whose users are locally hosted by a AS 5300 Session Manager within the 1+1 cluster. Local domains are provisioned for and serviced. Subscribers to a particular system belong to local domains. You use the Provisioning Client to provision local domains. root domain: A root domain is the highest level domain. You can create a root domain. An example of a root domain is avaya.com. subdomain: A subdomain is a category of domains. With subdomains, you can divide subscribers under a domain into smaller groups. You can also control routing and access to services by members of the group. Under each subdomain, you can add subdomains, service sets, users, devices, and telephony routes. The levels of nesting for subdomains is not limited. Each subdomain inherits the parameter values from the root domain. Important: Avaya recommends that you create geographically-based domains and subdomains. The following figure shows an example, using avaya.com as the root domain, with subdomains of Richardson and Ottawa. Additional subdomains can exist under each of these subdomains. October 2017 Avaya Aura Application Server 5300 Overview 96

97 Domains Figure 11: Domain hierarchy example multisite domain: Multisite domains contain multiple Application Server 5300 systems that are configured with the same domain name. An administrator configures each user in the multisite domain with a home AS 5300 Session Manager. SIP users gain access to their accounts from any client within the multisite domain, and thus allow users to move within the domain easily. To support multisite domains, the system requires a Lightweight Directory Access Protocol (LDAP) database, located in an LDAP server. The database stores routing information for the users in the domain. The system uses the LDAP information to determine how to route the call. For more information about special routing features that the LDAP database supports, see Call routing features on page 102. The Application Server 5300 connects to the LDAP server using TLS, secured by certificates and trust stores. The system stores the information obtained from the LDAP server in a routing cache. Routable services that are not associated with a home AS 5300 Session Manager (for example, Meet Me Conferencing) use translations to route calls within the multisite domain. foreign domain: Foreign domains are external domains associated with an external SIP proxy. The term external SIP proxy refers to all SIP proxies that are not part of the AS 5300 Element October 2017 Avaya Aura Application Server 5300 Overview 97

98 Configuration and administration Manager-managed network. An administrator must use the AS 5300 Element Manager Console to define an external SIP proxy. An administrator must configure foreign domains on both the local and the foreign destination system. For example, the local system has an external node configured with the proxy service address of the foreign destination system, and the foreign destination has an external node configured with the proxy service address of the local system. Use the Provisioning Client to administer domains. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Services You can use the Provisioning Client to define and assign services to domains. You can also assign all or a subset of the predefined services to a domain, and define the service parameters for a service set. You configure services much like convenience packages for the domain. Service profiles and service sets After you provision services for a domain, you can create service profiles and service sets for the domain or a subdomain, based on a set of predefined services. A Service Profile is any data that is associated to a service. It is the combination of the global, system, domain, group, and user level data. It is up to the individual service to define this data and the associated level for each piece of data. The profile can be one of two types. - A System profile is service data that can be defined at the system level. There could be single or multiple system profiles for a service, based on the service requirement. Some special services (such as Music on Hold) do not need a system profile. System profiles should be assigned to domains and to users to enable the use of system profile data. For assigning system profiles to domains and user, the respective service should be assigned to the domain and the user. - A User profile is service data that can be defined at the user level. User profile represents the user preferences. All the services do not need a user profile. Some special services (such as Music on Hold) do not need a user profile. For some services (such as presence), system profile data enables or disables the user profile data. With these services, system profile needs to be assigned to user for setting the user profile data. Some services (such as Ad hoc conferencing), user profile data is independent of system profile data. With these services, system profile need not be assigned to the user for setting the user profile data. - If a system profile and user profile are related for one parameter, any change or update in that system profile parameter value does not change the related user profile parameter value. System profile parameter values only control the user profile value. If system profile October 2017 Avaya Aura Application Server 5300 Overview 98

99 Service nodes parameter is enabled, then the user profile parameter can be enabled or disabled. If the system profile parameter is disabled, then the user profile parameter only can be disabled. A Service Set is a collection or group of services that are available at the domain level and that can be assigned to the user. There can be more than one service set at the domain level which will allow us to assign different service sets to different users. - Services need to be assigned to the root domain before creating any service sets in the domain, to control the services that are available in a domain. - Service sets can be created at the domain level and can be used to assign services to the user at user creation time. This service set, when assigned to the user, will define the services that are available to the user. - A service set is only applicable at the time of creating a new user. Any changes to the service set after creating the user are not applied to the user. The service set is intended for an ease of provisioning (by grouping the services) and not directly associated with the subscriber at runtime. After a user is created, any changes to the user s service or service profiles must be done on an individual user basis. - If the administrator removes a service from the domain, the administrator must manually modify each user to remove a service from a domain or subdomain. A service cannot be removed from a domain if it belongs to a service set or user. - When a service is removed from the user or domain, the related service profile data will need to be deleted. Each service set is a collection of predefined services. If you include a service in a service set, you enable the service or feature for the domains associated with the service set. You can also assign service sets that you configure for a domain to its subdomain. A user must be assigned a collection of services and the service profile for each of the services. If a user is assigned a service and no profile for the service, the service defines the default behavior. A service or profile must be assigned to the user s root domain before the service or profile can be assigned to the user. If the service is key coded, the number of units for the service must be assigned to the domain before the service can be assigned to the user. You can upgrade a service set (for example, you want to add services) as long as the service is available at the domain. You can also upgrade a service set to update parameter values, but only to the limit assigned to the domain. You can downgrade a service set (for services with parameters), but only to the upper limit of the parameter values for the user and subdomains. Service nodes A Service node is any network element in the system such as gateways or conference servers. You can change the IP addresses of a service node to accommodate network topology changes and change the IP addresses without reloading or redeploying the Application Server 5300 software. From the Provisioning Client, you can also add logical nodes, which consist of one or more service October 2017 Avaya Aura Application Server 5300 Overview 99

100 Configuration and administration nodes. A service node within a logical node can have additional system- or user-defined parameters, such as a trkgrp, associated with it. Licensing and keycoding Application Server 5300 delivers software that contains all the features and services. However, licenses and keycoding restrict access to some features. licenses: Some features require software licenses because of embedded software and license agreements. Licenses typically cover the number of users that can use a particular feature. keycodes: Some features require software keys to enable the feature to be turned on, configured, and used. A license key file contains both the licenses and keycodes required for the specific system. When an Application Server 5300 system is purchased, the ordering system updates to indicate the specific customer and the system attributes purchased. Before installation, the installer accesses the Keycode Registration System (KRS) to create the customer-specific license key file and download the file to an accessible location. For information on the KRS, see support.avaya.com/krs During installation, the installer installs the license key file into the system. This file can be updated by the administrator when additional features are purchased. For more information and for the list of keycoded features, see Avaya Aura Application Server 5300 Configuration, NN October 2017 Avaya Aura Application Server 5300 Overview 100

101 Chapter 13: Translations and routing This chapter describes Application Server 5300 routing and translation services. Navigation Local termination on page 101 Call transfer service on page 101 Telephony routing on page 102 Call routing features on page 102 Route lists on page 104 SIP aliases on page 105 Multiple Route Termination on page 105 Logical entity on page 106 Network Message Waiting Indicator Routing on page 106 Local termination The AS 5300 Session Manager first determines whether the incoming SIP request terminates to a client in a domain managed by the AS 5300 Session Manager Module. The AS 5300 Session Manager performs local routing lookup through the Location Server, which is part of its internal software. Call transfer service The AS 5300 Session Manager handles the transfer on behalf of clients that do not support the call transfer service. The AS 5300 Session Manager supports unattended Call Transfer (Blind Transfer and Consultative Transfer) through the Refer mechanism. Blind Transfer refers to cases where the transferrer redirects the transferee to the transfer target without first conferring with the transfer target. The transferrer receives a Notify message indicating the transfer success (transferee and new target). If successful, the transferrer releases the original call automatically. If not successful, the transferrer reconnects to the transferee. October 2017 Avaya Aura Application Server 5300 Overview 101

102 Translations and routing Consultative Transfer refers to cases where the transferrer redirects the transferee to the transfer target by first conferring with the transfer target. Telephony routing When the AS 5300 Session Manager receives an incoming call, it looks up the called party in the database. If the called party is not in the database but the AS 5300 Session Manager serves the domain and the user portion of the Uniform Resource Locator (URL) is a telephony routing number, the Location Server telephony software uses the telephony routing number. The telephony routing software must perform digit translation to find a gateway on which to terminate a call. These tables are in the Database Manager. You provision them through the Provisioning Client. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN By using the telephony routing service, the AS 5300 Session Manager can: provide unique dial plans for each subdomain. provide routes to gateways or to other domains: These routes include routes for private-digit dial plans, routes to gateways, and telephony-style routing between SIP domains. apply Class of Service (CoS): CoS is used to block particular types of calls, such as international dialing or long-distance dialing. For example, you can restrict telephones in an office lobby to only local and emergency calls. Call routing features This section describes the following related features: Subscriber Lookup and Routing on page 102 Hybrid Routing on page 103 Commercial Cost Avoidance on page 103 Destination Code Controls on page 104 Subscriber Lookup and Routing Subscriber Lookup and Routing (SLR) requires the configuration of a multisite domain, as discussed in Domain types on page 96. SLR supports SIP users only. When a user dials a call, the system first checks to see if the called party is a user on the same system. If the called party is on the same Application Server 5300 system, the call routes to that person. If the called party is not on the same system, the system checks the multisite Lightweight October 2017 Avaya Aura Application Server 5300 Overview 102

103 Call routing features Directory Access Protocol (LDAP) database. If the LDAP database contains the called party (that is, the person is part of the same multisite domain), the system routes the call to the appropriate system. If the LDAP database does not contain the called party, the system routes the call to the Public Switched Telephone Network (PSTN). SLR is a keycoded service, handled through the AS 5300 Element Manager Console. System administrators provision SLR using the Provisioning Client. Operational measurements show SLR performance metrics. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN , Avaya Aura Application Server 5300 Configuration, NN , and Avaya Aura Application Server 5300 Operational Measurements Reference, NN Hybrid Routing Hybrid Routing determines whether to route a call to the PSTN or to the IP network. Hybrid Routing depends on Commercial Cost Avoidance, and requires a multisite domain as described in Domain types on page 96. When a subscriber in the Application Server 5300 makes a call, the system uses the information stored in the routing cache. If the system determines that the call can be placed on the IP network, the call routes to the next IP hop in the network. If the system determines that the call cannot be placed on the IP network, the call routes using the configured telephony routes. Hybrid Routing requires an LDAP server. The system stores the information obtained from the LDAP server in a routing cache. Within the cache, the system stores information on the Call Control Agent ID (CCA-ID) for the Soft Switch (SS) and Local Session Controller (LSC). A keycode controls the ability to configure Hybrid Routing. The administrator configures Hybrid Routing using the AS 5300 Element Manager Console and Provisioning Client. Hybrid Routing can only be enabled on an SS; it cannot be enabled on an LSC. Operational measurements show Hybrid Routing performance metrics. For more information, see Commercial Cost Avoidance on page 103, Avaya Aura Application Server 5300 Using the Provisioning Client, NN , Avaya Aura Application Server 5300 Configuration, NN , and Avaya Aura Application Server 5300 Operational Measurements Reference, NN Commercial Cost Avoidance Commercial Cost Avoidance (CCA) enables calls to be routed through the private network, even though they were dialed as external calls. Commercial Cost Avoidance depends on Hybrid Routing, and requires a multisite domain as described in Domain types on page 96. CCA is also known as Least Cost Routing. October 2017 Avaya Aura Application Server 5300 Overview 103

104 Translations and routing When dialing a telephone number, the subscriber enters the configured CCA prefix, followed by the external telephone number. The system looks up the called number in the LDAP database to determine if the call can be routed inside the private network. If the call can be routed in the private network, the system uses the private route. If the call cannot be routed in the private network, the system routes the call to the PSTN. Routing calls within the private network reduces long distance charges from the PSTN provider. A keycode controls the ability to configure CCA. The administrator configures CCA using the AS 5300 Element Manager Console and Provisioning Client. To support CCA, the system must be configured as a multisite domain (see Domain types on page 96). Operational measurements show CCA performance metrics. For more information, see Hybrid Routing on page 103, Avaya Aura Application Server 5300 Using the Provisioning Client, NN , Avaya Aura Application Server 5300 Configuration, NN , and Avaya Aura Application Server 5300 Operational Measurements Reference, NN Destination Code Controls Destination Code Controls (DCC) allows you to control calls to specific locations that are difficult to reach. DCC allows only precedence traffic to pass to enclaves or regions. You can configure the percentage of calls that the system blocks. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Route lists To be functional, routes must be part of a route list. Route lists are a set of routes with a particular set of common properties that control access to those routes. By using the incoming call routing parameters, the administrator can determine what happens if the calling party from another domain or subdomain tries to place a call into your domain. For example, to prevent fraud, all incoming calls blocked outside that domain use your gateway. In addition to these properties, you can use a set of routes in the route list domain. A route can appear in more than one route list. Every domain in the system is either a top-level domain or a subdomain of another domain, and forms a domain tree. The following list shows the types of route lists: Incoming Other Domain-Tree Call Routing: This route list controls the behavior of telephony routing if the call or request comes from a domain outside the domain-tree of the calling party. This includes foreign domains or domains unknown to the system. The possible values are - Allow: allows the call to terminate using your route lists. October 2017 Avaya Aura Application Server 5300 Overview 104

105 SIP aliases - Redirect: redirects the call back to the calling party's domain. This means changing the domain in the request Uniform Resource Indicator (URI) to the calling party's domain and terminating there. - Block: rejects the call because the calling party is not permitted to route into the called party's domain. Incoming Same Domain-Tree Call Routing: This route list controls the behavior if both the calling party and the called party share the same domain tree. The possible values are - Allow: allows the call to terminate using your route lists. - Redirect: redirects the call back to the calling party's subdomain. This means changing the domain in the request URI to the calling party's domain and terminating there. - Block: rejects the call because the calling party is not permitted to route into the called party's subdomain. Class of Service (CoS): CoS is used to block particular types of calls, such as international dialing or long-distance dialing. For example, telephones in an office lobby can be restricted to local and emergency calls only. SIP aliases Alias URLs are used to refer to a SIP client in the network. For example, a user sip:usera@domainx.com can also have an alias of sip:41037@domainx.com. If an incoming request specifies the sip:41037@domainx.com alias in a Request-URI, the alias takes precedence over gateway routing translations, and routing information for to usera is retrieved. If an alias of sip:41037@domainx.com is not configured, the system performs gateway routing translations to find out if a terminating gateway exists. Multiple Route Termination If a single SIP user is registered at more than one device (PSTN or SIP), Multiple Route Termination (MRT) routes a session simultaneously or sequentially to multiple devices. The AS 5300 Session Manager connects to the SIP database to determine the user-routing preference, the routes available, and routing options for a particular user. The user defines these options through the Personal Agent. For more information about the Personal Agent, see Avaya Aura Application Server 5300 Personal Agent User Guide, NN With simultaneous ringing, the call terminates to multiple routes at the same time. The first terminating route to answer is accepted and the rest of the routes released. With sequential ringing, the call tries to terminate to multiple routes, one at a time. Route advancement occurs when a route receives an error response, a redirect response, or when a configurable No Answer timer expires. October 2017 Avaya Aura Application Server 5300 Overview 105

106 Translations and routing Logical entity The AS 5300 Session Manager uses logical entities to group various physical resources, such as several conference servers for Ad Hoc, Meet Me, Announcements, or Music On Hold, into a logical pool of resources that are accessed using the provisioned name of the pooled resource. The administrator configures a weight for each physical resource within the pool to determine how often that particular physical resource is used compared to the other physical resources within the pool. If the pooled resource is accessed, the system uses a weighted selection algorithm to select one of the physical resources. The request is sent to the selected physical resource. Logical entities are transparent from a user's perspective. The user knows about the logical pool name (the pooled resource name), but does not know the number of physical resources in a pooled resource. The domain administrator must provision the pooled resource and assign physical resources and associated weights to the pooled resource. Network Message Waiting Indicator Routing Network Message Waiting Indicator (NMWI) Routing supports the propagation of NMWI indicators where the voic system serving the Application Server 5300 subscriber is located behind a trunk gateway. The AS 5300 Session Manager propagates the NMWI message to other AS 5300 Session Manager in the system if the user that the message is for is not registered on the original AS 5300 Session Manager. October 2017 Avaya Aura Application Server 5300 Overview 106

107 Chapter 14: Redundancy, fault tolerance, and failover This chapter provides information about Application Server 5300 redundancy, fault tolerance, and failover. Navigation Fault tolerance definitions on page 107 Application Server 5300 fault tolerance on page 108 High Availability fault tolerance on page 110 Overload control on page 113 Denial of Service on page 113 Server backup and recovery on page 114 Fault tolerance definitions The following definitions apply for fault tolerance: Component labels: - Primary: This is the instance of a component normally accessed by other network components. This label applies to the AS 5300 Element Manager, Accounting Manager, and Database Manager in redundant configurations. - Secondary: This is the instance of a component accessed by other network components if the Primary instance is not available. This label applies to the AS 5300 Element Manager, Accounting Manager, and Database Manager in redundant configurations. Component states: - Active: This is a state of a component where the instance is available on the network and is currently providing, or can provide, service. - Hot standby: This is a state of a component where the instance is available on another server and failover is automatic. - Cold standby: This is a state of a component where the instance is available on another server, and the failover is manual. October 2017 Avaya Aura Application Server 5300 Overview 107

108 Redundancy, fault tolerance, and failover - Offline: This is a state of a component where the instance is available on a server, but it is not running and does not provide service. Application Server 5300 fault tolerance The Application Server 5300 configurations provide full redundancy by pairing servers. Each pair of servers contains the identical deployed software. One of the servers in the pair is active and the other is the warm standby server. If the active server becomes inactive, the warm standby server becomes the active server. The warm standby software becomes the active software. The process of changing from the active (now inactive) server to the standby server is known as failover. The system supports both manual and automatic failover. Each Application Server 5300 manager requires specific configurations to support it, as described in the following sections. The following Application Server 5300 managers support automatic failover: AS 5300 Element Manager AS 5300 Session Manager Accounting Manager The following Application Server 5300 manager uses manual failover: Provisioning Manager The following sections provide more information on the fault tolerance of individual network elements: AS 5300 Element Manager fault tolerance on page 108 AS 5300 Session Manager fault tolerance on page 109 Database Manager fault tolerance on page 109 Accounting Manager fault tolerance on page 109 Provisioning Manager fault tolerance on page 110 PRI Gateway fault tolerance on page 110 AS 5300 Element Manager fault tolerance The AS 5300 Element Manager in a redundant pair uses active and hot standby states and supports automatic failover. However, if failover occurs, operational measurements (OM), accounting records, and alarms and logs remain on the inactive system, and must be retrieved manually. The active AS 5300 Element Manager component owns the logical IP address used to connect with the AS 5300 Element Manager Console. In addition, all the network elements use the logical IP address to send logs, alarms, and OMs to the AS 5300 Element Manager. October 2017 Avaya Aura Application Server 5300 Overview 108

109 Application Server 5300 fault tolerance After the active AS 5300 Element Manager fails, the AS 5300 Element Manager Console loses its connection. Logs and alarms from the managed network elements that use the AS 5300 Element Manager for fault and performance management spool on each network element instance and are not reported until the active AS 5300 Element Manager recovers or until the automatic failover to the standby AS 5300 Element Manager completes. If a AS 5300 Element Manager failover occurs before the standby AS 5300 Element Manager is in hot standby status, all registered users lose presence and message waiting indicator (MWI) function. Presence and MWI restore after the active AS 5300 Element Manager completes the initial re-synchronization. The database stores the system application and configuration data. The standby AS 5300 Element Manager retrieves the latest configuration data from the database after it becomes active. However, information stored on the management server local disk does not transfer during a failover. This information includes archived logs and holding OMs. AS 5300 Session Manager fault tolerance The AS 5300 Session Manager uses the 1+1 redundancy (active and hot standby) for fault tolerance. It supports automatic failover through IP Takeover. After one of the active AS 5300 Session Manager fails, the hot standby manager takes over the IP address. The hot standby manager becomes active and assumes the responsibilities of the failed manager. The AS 5300 Session Manager uses CallP checkpoints for active calls, enabling active calls to remain active if a AS 5300 Session Manager failover occurs. Database Manager fault tolerance The Database Manager uses an embedded database software and runs in replicated mode of the Replication software. Alarms on the AS 5300 Element Manager Console indicate failure. The alarms on the AS 5300 Element Manager Console result from the attempt of the network components to access the database. Accounting Manager fault tolerance The Accounting Manager uses the 1+1 redundancy (active and hot standby) for fault tolerance. It supports automatic failover through IP Takeover. After one of the active Accounting Managers fails, the hot standby manager takes over the IP address. The hot standby manager becomes active and assumes the responsibilities of the failed manager. Each server running an instance of the Accounting Manager provides a unique physical IP address. However, to provide a transparent transfer mechanism for the Accounting Manager to the Record Transfer Agent (RTA) (that is, with no configuration changes), the system uses a logical IP address. Configure the RTA to connect to the logical IP address associated with the active instance of the Accounting Manager. This logical IP address identifies the active instance of the Accounting Manager. The logical IP address is independent of a physical server; it always points to the server October 2017 Avaya Aura Application Server 5300 Overview 109

110 Redundancy, fault tolerance, and failover that hosts the active instance of the Accounting Manager. During the automatic failover procedure, the logical IP address updates to identify the currently active instance after the transfer occurs. Alarms typically indicate failure of the Accounting Manager. There can also be alarms from one or more RTAs executing on the AS 5300 Session Manager component. If the primary instance of the Accounting Manager component fails and the hot standby Accounting Manager does not become active, the RTA loses its connection to the Accounting Manager. In this case, the RTA queues accounting data and (if the problem persists) stores accounting data to its local file storage. When an Accounting Manager becomes active, the RTA resumes sending the data. Provisioning Manager fault tolerance No automatic failover of the Provisioning Manager Web server exists in redundant deployments. If the Web server fails, the services that it provides are interrupted. Subscribers cannot connect to the Web server for self-provisioning sessions. The administrator uses manual intervention to reestablish the services. Watchdog processes on the host server attempt to autostart the Web server. Session processing does not halt. Access to the Personal Agent halts, which affects service package retrieval. To rectify the problem in systems with a backup Web server, administrators can redirect subscribers to the URL of the backup Provisioning Manager. PRI Gateway fault tolerance The PRI Gateway does not support automatic failover. High Availability fault tolerance High Availability fault tolerance is a combination of hardware deployment and software configuration. Application Server 5300 supports: Campus redundancy on page 111 Layer 2 geographic redundancy on page 111 For more information, see Avaya Aura Application Server 5300 High Availability Fundamentals, NN October 2017 Avaya Aura Application Server 5300 Overview 110

111 High Availability fault tolerance Campus redundancy Campus redundancy (also known as Layer 2 stretched redundancy) exists after two Application Server 5300 systems are configured in the same subnet in a network, but in different locations. For instance, the systems can reside in different buildings on the same campus. These two systems are stand-alone systems but contain the same configuration and data. The only differences are the IP addresses. One system is called the Active system and the other the Standby system, as shown in the following figure. Figure 12: Application Server 5300 campus redundant network A pair of Ethernet Routing Switches monitor the health of these systems. After the Ethernet Routing Switch detects the Active system is not accessible, it communicates this information to the Standby system. The Standby system becomes active. The telephones and clients that access the Application Server 5300 communicate through the Ethernet Routing Switch. The Ethernet Routing Switch causes the Standby system to become active, the telephones and clients change from using the now-inactive system to the now-active system. Layer 2 geographic redundancy High Availability is essential for the successful deployment of Application Server 5300 in a missioncritical service network. A service network is highly available if, when failure occurs, the network continues to provide services without interruption, although possibly at a reduced rate. Many different possible Application Server 5300 configurations exist. For simplicity, this document depicts one reference network. shows a typical Layer 2 (L2) geographically redundant Application Server 5300 deployment configuration for a large enterprise. This reference network depicts Application Server 5300 network elements and devices deployed in both primary and secondary data centers. Two pairs of Layer 2/Layer 3 (L2/L3) switches and fiber cables connect the two data October 2017 Avaya Aura Application Server 5300 Overview 111

112 Redundancy, fault tolerance, and failover centers, which reside in two different locations. The switches are Avaya Ethernet Routing Switch 5500 series (ERS 5500) switches deployed as L2/L3 edge switches. The reference network uses two pairs of dedicated fibers to provide full-duplex gigabit Ethernet transmission between the primary and secondary sites. The redundant pairs of switches ensure that no single point of failure exists anywhere in the network because there is a minimum of two physical paths between any two endpoints. To eliminate a trunking failure after a single switch or switching module failure, each pair of fiber connects to a different switch or switch module. These fiber pairs aggregate into a single logical connection using IEEE 802.3ad protocol to provide Ethernet MAC failover transparency for the VLAN trunks. After a failure occurs in the network, all routing devices exchange routing status information (for example, link and device up or down) for the network. For faster recovery from a routing failure, Avaya recommends a link-state based routing protocol such as Open Shortest Path First (OSPF). At the service network edge, the use of Virtual Router Redundancy Protocol (VRRP) (RFC 2338) enables fast default router recovery for endpoints. Figure 13: Reference network L2 geographic redundancy October 2017 Avaya Aura Application Server 5300 Overview 112

113 Overload control Overload control The AS 5300 Element Manager can experience Minor, Major, or Severe levels of overload. The AS 5300 Element Manager response depends on the overload level: Minor: If the AS 5300 Element Manager reaches and stays at the Minor level for a few seconds, the Application Server 5300 stops generating Presence notifications. Major: In a Major level of overload, all traffic, such as instant messages, registrations or new calls, is rejected with a 503 message. However, in-progress calls continue, which means that users can hang up, hold, retrieve, or transfer calls while the AS 5300 Session Manager is in an overload condition. Severe: If the AS 5300 Element Manager reaches the Severe level, all new sessions are blocked. There are two queues with threshold value configurations that trigger the Major level of overload: call processing queue: The Call Processing queue processes work related to calls. database queue: The Database queue processes database requests. If the Call processing queue backs up, the AS 5300 Session Manager goes into a Major overload condition. Major overload means there are too many calls being processed by the system. If the Database queue backs up, a Major overload condition occurs. This condition usually indicates that the database accesses exceed the database capacity. Denial of Service Denial of Service (DoS) attacks flood the system with SIP messaging. When SIP messaging exceeds certain thresholds, system performance can degrade, which can cause service interruptions. The system provides a mechanism to protect the call server from DoS attacks. This mechanism also prevents the call server from wasting computing resources due to SIP messaging that exceeds the configured thresholds. To protect the server, the system tracks repeated SIP requests and monitors incoming messages to determine whether they originate from a blocked source (identified by the IP address and port). DoS attacks cause a temporary blocking of HTTP and HTTPS requests from a particular source. After the system detects an abnormal rate of HTTP or HTTPS traffic, it drops all requests from that particular source. The requests do not reach the applications. Messages from the source remain blocked for a configured amount of time (60 seconds by default), after which an audit restores access. During a DoS lockout, the system discards all subsequent packets from the locked source, regardless of message type or transaction state, and without sending a response. The system continues to process messages from non-blocked sources. October 2017 Avaya Aura Application Server 5300 Overview 113

114 Redundancy, fault tolerance, and failover The system can detect and block up to sources, based on source IP address and port. After a DoS lockout occurs, the system generates a log. The system does not log individual blocked requests during the lockout period. By default, the system generates a minor alarm every 60 seconds to report locked-out endpoints. The system generates a minor alarm at 100 blocked endpoints, a major alarm at 5000 blocked endpoints and a critical alarm at blocked endpoints. External SIP proxies and SIP testing tools can generate significant messaging traffic, potentially exceeding the threshold. To avoid blocking these messages, the administrator can disable DoS mitigation or configure a list of trusted nodes. For information about configuring DoS parameters, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Security, NN Server backup and recovery Avaya strongly recommends that you maintains backups of the Application Server 5300 servers, and that you create a new backup after significant changes, such as: after changing the Linux Operating System on any Application Server 5300 server after you update the Database software on the server running the database after you deploy an Application Server 5300 software maintenance release to the server. For backup and recovery procedures, see Avaya Aura Application Server 5300 Administration, NN October 2017 Avaya Aura Application Server 5300 Overview 114

115 Chapter 15: Installation and patching This chapter describes Application Server 5300 and Avaya Media Server (MS) installation and patching. Important: This section describes installation and patching for the Application Server 5300 and Avaya MS only. For information about installation and patching of other system hardware, firmware, and software, see the vendor documentation. Navigation Installation strategy on page 115 Upgrade strategy on page 115 Patching strategy on page 116 Tools and utilities on page 117 Installation strategy Avaya delivers Application Server 5300 software bundles on one or more compact discs (CD) and digital video discs (DVD). The bundle includes software for the Application Server 5300 core servers and the Avaya Media Server (MS). You load Application Server 5300 software bundles onto the Management Server, where property definitions are unbundled to drive the AS 5300 Element Manager Console, and then deploy the software packages to the appropriate Application Server 5300 components. For information about installing the Application Server 5300 and Avaya MS component software, see the Method of Procedure installation documents supplied by Avaya. Upgrade strategy Application Server 5300 supports upgrades from Release 1.0 to Release 2.0, and from Release 2.0 to Release 3.0. Where possible, configuration data is updated for the new release. New configuration fields are prefilled with default data. For more information, see AS5300 Release Upgrade. October 2017 Avaya Aura Application Server 5300 Overview 115

116 Installation and patching Avaya MS can be updated from Release 6.6 to Release 7.5. For more information, see AS5300 Release Upgrade. Patching strategy The core Avaya components of the Application Server 5300 network support patches. A patch allows the current active application software to be upgraded to address emergency or general maintenance requirements. A patch can update a single piece of software (for example, theas 5300 Element Manager), or multiple pieces packaged in a patch bundle (for example, the Accounting Manager, AS 5300 Session Manager, and Provisioning Manager). A patch bundle can also be called a Maintenance Release by Avaya. Patches to the Linux base use a different mechanism. For more information, see the Application Server 5300 Release Notes. The patch update mechanism includes the following capabilities: supports migration of configuration data from one version to the next provides software rollback capability for use in the event of software or deployment failure bundles the patch software into an update package to decrease the time required to identify the differences between releases and to reduce the time required for the overall update process Both the Application Server 5300 and the Avaya Media Server interfaces install and coordinate patches. Avaya strongly recommends customers enter into Software Release Service (SRS) contracts with Avaya. Customers with an SRS automatically receive any required system software updates. For patching instructions, see the documentation supplied with the patch. Software update delivery methods You can obtain Application Server 5300 patch updates and Application Server 5300 Maintenance Releases (MR) from the Avaya TS Portal. MRs are also available on CD or DVD; to receive MRs on DVD or CD, including Maintenance Releases for AudioCodes and Avaya MS, contact your Avaya representative for information about the SRS. For details about updating component software, see the documentation supplied with the patch or MR. QFE Avaya sometimes releases urgent patches for the Avaya Media Server as Hot Fixes, or Quick Fix Engineering (QFE) patches. Apply QFE patches only to systems that require an immediate fix and cannot wait for an official release, and only when recommended by Avaya. October 2017 Avaya Aura Application Server 5300 Overview 116

117 Tools and utilities For information about applying QFE, see Avaya Aura Application Server 5300 Configuration, NN Software update contents Each Application Server 5300 software patch package contains the following items: core CD and DVD pack (core software, database software patch disc, customer documentation CD) applicable operating system (OS) patches Avaya Media Server (MS) Service pack (includes services updates) Release Notes that outline the content of the patch Tools and utilities All Application Server 5300 software installations and patches deploy from the AS 5300 Element Manager through the AS 5300 Element Manager Console, except the upgrade of the AS 5300 Element Manager itself. Installers load the patch bundles onto the AS 5300 Element Manager and then deploy the patch bundles through the AS 5300 Element Manager Console. Rollbacks also are accomplished from the AS 5300 Element Manager Console. During an upgrade, the installation program stops the current Avaya MS framework, replaces its executable, and restarts the Avaya MS framework. The entire upgrade process typically takes less than one minute to perform. Operating system patches are cumulative, so the latest patch bundle contains all the previous patches. For information about the AS 5300 Element Manager and AS 5300 Element Manager Console, see AS5300 Element Manager Console fundamentals on page 140. For instructions about installing the Application Server 5300 component software, or performing software upgrades and rollbacks, see the documentation supplied with the software load. For information about installing the Avaya MS component software, see AS Avaya Media Server Installation and Commissioning. Installation and patches for other equipment use the vendor-specific methods. For more information, see the vendor documentation. October 2017 Avaya Aura Application Server 5300 Overview 117

118 Chapter 16: Fault management This chapter describes Application Server 5300 fault management. Navigation High-level strategy on page 118 Maintenance procedures on page 119 High-level strategy As part of its functionality, the AS 5300 Element Manager provides fault management for Application Server 5300 system components. Each Application Server 5300 core element collects and sends fault data to the AS 5300 Element Manager. Software and application alarms transmit over TCP and consolidate at the AS 5300 Element Manager. The PRI Gateway collects SNMP traps and sends corresponding alarms to the AS 5300 Element Manager. The AS 5300 Element Manager formats the fault data into Avaya Standard (STD) logs and populates the data into the Avaya Reliable Fault Management Information Base (MIB). The AS 5300 Element Manager Console receives the formatted data. For additional information about the AS 5300 Element Manager, see AS 5300 Element Manager fundamentals on page 136. The software restricts the number of alarms and logs that can be generated. This restriction reduces the instances of multiple logs that are related for the same problem. The Application Server 5300 stores the alarms and logs in a separate partition on the disk. Only users with specific access permissions can access the partition, read, modify or delete the logs. The AS 5300 Element Manager Console displays faults and manages the health of the Application Server 5300 system and its components. For details about using the AS 5300 Element Manager Console, see Avaya Aura Application Server 5300 Configuration, NN , and Avaya Aura Application Server 5300 Security, NN In addition to monitoring logs from the AS 5300 Element Manager Console, you can configure the system to poll alarms from the AS 5300 Element Manager by the Network Management System (NMS) through the use of an SNMP stream, and send them to a northbound system for monitoring. All alarms are logged. The local disk stores the logs for a configured retention period of up to seven days. You use the AS 5300 Element Manager Console to view logs. Logs can be exported from the AS 5300 Element Manager for further evaluation. For further information about alarms and logs, see Avaya Aura Application Server 5300 Troubleshooting and Fault Management, NN , and Avaya Aura Application Server 5300 Alarms and Logs Reference, NN October 2017 Avaya Aura Application Server 5300 Overview 118

119 Maintenance procedures For a comprehensive list of all Application Server 5300 system alarms, see Avaya Aura Application Server 5300 Alarms and Logs Reference, NN Maintenance procedures Maintenance procedures include the following tasks: database backup and restore accounting record backups server backup and restore fault management, including alarm analysis certificate management For more information about these tasks, see Avaya Aura Application Server 5300 Administration, NN , Avaya Aura Application Server 5300 Security, NN , and Avaya Aura Application Server 5300 Troubleshooting and Fault Management, NN For information about procedures used to troubleshoot system problems, and system recovery trees for emergency system recoveries, see Avaya Aura Application Server 5300 Troubleshooting and Fault Management, NN For descriptions of the Application Server 5300 alarms and logs, see Avaya Aura Application Server 5300 Alarms and Logs Reference, NN If Application Server 5300 system hardware fails, the Avaya Repairs and Returns service handles the failed hardware. October 2017 Avaya Aura Application Server 5300 Overview 119

120 Chapter 17: Configuration management This chapter describes Application Server 5300 configuration management. Navigation Strategy on page 120 Tools and utilities on page 121 Strategy Avaya delivers the system without custom configuration. You use the Application Server 5300 documentation to install and configure the system. Avaya Professional Services offer custom installation and engineering at an additional cost. After performing installation and base commissioning, you can use the following checklist to verify completion: All appropriate hardware equipment and software loads are installed and loaded as follows: - Network is cabled and connected. - Cards are installed. - Grounding implemented for safety. All network topology (physical characteristics) implemented as planned. Installation validation procedures are complete, and components are operational. The sequence of translations, internal customer testing, and additional services, applications, and features are planned. You can upload data from the publishable XML format native to the Operation Support System (OSS) of the Provisioning Manager. The OSS defines a suite of operations applicable to the known Provisionable Objects (PO) of the Provisioning Manager. The operations are specified according to the Web Service Definition Language (WSDL). Agents can use this interface to facilitate the automated flow-through of data to and from the Provisioning Manager. The system uses Open Provisioning Interface (OPI) to transport the provisioning data from the OSS to the Application Server October 2017 Avaya Aura Application Server 5300 Overview 120

121 Tools and utilities Tools and utilities To configure the Application Server 5300 SIP-based network, you must deploy and configure the system components and network elements, and provision the system. The tool to deploy and configure all Application Server 5300 components and network elements is the AS 5300 Element Manager Console. For more information, see Avaya Aura Application Server 5300 Configuration, NN The tool to provision the Application Server 5300 is the Web-based Provisioning Client. For more information, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Application Programming Interface (API) support for third-party client applications is provided through the Open Provisioning Interface (OPI). For more information, see Avaya Aura Application Server 5300 Application Programming Interfaces Reference, NN For procedures to install a new Application Server 5300 system and procedures to upgrade or patch an existing system, see the documentation supplied with the software load. October 2017 Avaya Aura Application Server 5300 Overview 121

122 Chapter 18: Accounting management This chapter describes Application Server 5300 accounting management. Navigation Strategy on page 122 Tools and utilities on page 122 Strategy The accounting management system for the Application Server 5300 provides the framework to collect, format, and transmit accounting data from the Application Server 5300 system to the service provider's back-end billing system. The AS 5300 Session Manager collects raw accounting data from active sessions and transfers the data to the Accounting Manager. The Application Server 5300 call model is event-based. Triggers in a call, session, or transaction generate a raw data record on the AS 5300 Session Manager. Trigger examples include service initiation, session answer, session, and reject. The Accounting Manager accepts, formats, and stores the raw data. You can configure the system to transmit data to northbound operations support systems (OSS) for further processing. For additional information about the Accounting Manager, see Accounting Manager fundamentals on page 163. For information about the accounting records, see Avaya Aura Application Server 5300 Accounting Records Reference, NN Tools and utilities Use the AS 5300 Element Manager Console to configure, monitor, and maintain the Application Server 5300 accounting management system. For additional information about the Accounting Manager, see Accounting Manager fundamentals on page 163. For information about using the AS 5300 Element Manager Console to configure, monitor, and maintain the accounting management system, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Administration, NN October 2017 Avaya Aura Application Server 5300 Overview 122

123 Chapter 19: Performance management This chapter describes Application Server 5300 performance management. Navigation Strategy on page 123 Tools and utilities on page 124 Strategy Operational measurements (OM) provide statistical information about server operations and performances. OMs are usually represented in terms of groups, which contain registers (counters and gauges) that provide data related to system performance. For example, call processing can provide data to an OM group related to call control, and an OM group related to call progress. One group provides data like the number of successful calls, the number of calls rejected, and unauthorized attempts; whereas the other group provides data like average call holding time and call duration. There are two types of OMs: active and holding. Active OMs appear as they are reported by the server to the AS 5300 Element Manager Console. Holding OMs are archived to files on the AS 5300 Element Manager. As the OM group registers update, they collect into an OM report. You can view a snapshot of this report using the OM browser located on the AS 5300 Element Manager Console. Application Server 5300 OM data belongs to one of the following categories: platform-related OMs: obtained from the SNMP agents at the Application Server 5300 components and AS 5300 Element Manager node. The OMs channel through the Application Server 5300 management framework. This method applies only to Database Manager and Provisioning Manager, not to the entire system. Application Server 5300 applications-related OMs: obtained through the Application Server 5300 management framework. A service provider can access OMs through Secure File Transfer Protocol (SFTP) or view OMs using the OM browser on the AS 5300 Element Manager Console. The AS 5300 Element Manager collects OMs and archives them in Comma Separated Value (CSV) file format. To view these files, you can use a Performance Management (PM) system that uses SFTP to access the files. October 2017 Avaya Aura Application Server 5300 Overview 123

124 Performance management For more information about OMs, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Administration, NN For a comprehensive list of all Application Server 5300 OMs, see Avaya Aura Application Server 5300 Operational Measurements Reference, NN and the Avaya Media Server documentation suite. For information about performance configuration and administration, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Administration, NN Tools and utilities The AS 5300 Element Manager provides the performance management framework for all Application Server 5300 components. Configure performance data collection and reporting from the AS 5300 Element Manager Console by selecting a deployed application, or the System node in the system hierarchy tree, and in the shortcut menu choose the OAM Configuration menu command. In addition, you can monitor performance data from the OM browser on the AS 5300 Element Manager Console. For information about using the AS 5300 Element Manager Console to perform performance management tasks, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Administration, NN October 2017 Avaya Aura Application Server 5300 Overview 124

125 Chapter 20: Security, administration, and maintenance This chapter describes Application Server 5300 security, administration, and maintenance. Navigation Security on page 125 Administration and maintenance on page 133 Security This section outlines the security strategy, and specific measures that improve system security. Security strategy The Application Server 5300 incorporates security mechanisms within Session Initiation Protocol (SIP) for registration and invite messages. The user is authenticated with a user name and password. Endpoints are identified by unique Uniform Resource Locators (URL). For more information about the Application Server 5300 security strategy, see Avaya Aura Application Server 5300 Security, NN and Avaya Aura Application Server 5300 Planning and Engineering, NN Application Server 5300 can provide secure communication between elements using Transport Layer Security (TLS), IP Security (IPsec), Hypertext Transport Protocol Secure (HTTPS), Secure Real-time Transport Protocol (SRTP), and Secure Real-time Transport Control Protocol (SRTCP). These protocols protect the transmitted data from tampering and ensure that the data is kept private. Important: Application Server 5300 systems that do not use TLS and SRTP use UDP, TCP, and RTP. AudioCodes Mediant 3000 does not support best effort RTP/SRTP (mixed-mode security). The configuration for all endpoints must be either secure or non-secure for media. October 2017 Avaya Aura Application Server 5300 Overview 125

126 Security, administration, and maintenance Security measures in Application Server 5300 The following security measures are supported: SIP Denial of Service mitigation on page 126 Encryption on page 126 FIPS on page 126 Common Access Card (CAC) authentication for AS 5300 UC Client configured for high security on page 127 Authentication, password, and user management on page 127 Access control on page 129 Host-based intrusion detection system on page 130 Traffic separation on page 130 SIP TLS Identity Checking on page 132 Other security measures on page 132 SIP Denial of Service mitigation SIP Denial of Service (DoS) attacks have a serious impact on system performance. To protect the Application Server 5300 system, the AS 5300 Session Manager monitors repeated SIP requests to the AS 5300 Session Manager, Provisioning Client, and Personal Agent. After the configured threshold number of requests is exceeded, subsequent requests are temporarily blocked and the Application Server 5300 drops all SIP requests from the request source. The activity from the particular IP address is blocked for a configurable amount of time before access is restored. Use the AS 5300 Element Manager Console to configure the threshold detection and lockout characteristics for the AS 5300 Session Manager, Provisioning Client, and Personal Agent. Alarms and logs are generated at certain thresholds. OMs are also pegged. Encryption Web transactions for the Provisioning Client and Personal Agent use secure socket layer (SSL) for authentication, data confidentiality, and data integrity protection. As well, the use of digital certificates improves security. SIP interface transactions can be protected by TLS, which ensures integrity, authentication, and confidentiality. FIPS The National Institute of Standards and Technology (NIST) issued the Federal Information Processing (FIPS) 140 Publication Series to coordinate the requirements and standards for cryptography modules, which include both hardware and software components. Federal agencies and departments can validate that a module in use is covered by existing FIPS and FIPS certificates that specify the exact module name, hardware, software, firmware, and applet October 2017 Avaya Aura Application Server 5300 Overview 126

127 Security version numbers. The private sector or open source communities produce these cryptographic modules for use by the U.S. government and other regulated industries (such as financial and health-care institutions) that collect, store, transfer, share and disseminate sensitive, but unclassified (SBU) information. FIPS establishes the Cryptographic Module Validation Program (CMVP) as a joint effort by NIST and the Communications Security Establishment (CSE) for the Canadian government. FIPS defines four levels of security; Level 4 is the highest. Security Level 1 specifies basic security requirements for a cryptographic module (for example, at least one approved algorithm or approved security function). A Security Level 1 cryptographic module requires no specific physical security mechanisms beyond the basic requirement for production-grade components. An example of a Security Level 1 cryptographic module is a personal computer (PC) encryption board. Application Server 5300 is FIPS Level 1 compliant by ensuring all cryptographic modules in the solution use FIPS certified cryptographic modules and approved security functions. An administrator uses the Group Policy Editor to enable FIPs mode in the operating system (OS). CAC authentication for AS 5300 UC Client configured for high security The Avaya Aura AS 5300 UC Client supports ActivClient Common Access Card (CAC) for Department of Defense (DoD) deployments. When CAC is required, subscribers insert the CAC, and enter a personal identification number (PIN) for the ActivClient, followed by a user name and password for Avaya Aura AS 5300 UC Client. Avaya Aura AS 5300 UC Client with CAC authentication requires the following hardware and software: Common Access Card Reader: used to enable card reader in the operating system. Common Access Card (CAC): a smart card used by DoD as a single authentication device, which stores important personal information, including SSL certificates that are used for encryption and electronic signatures. ActivClient software: software which makes the SSL certificates (stored on CAC) available to the operating system. Authentication, password, and user management Application Server 5300 uses authentication to confirm the identity of the users. Passwords are used for authentication by the AS 5300 Element Manager Console, Provisioning Client, and Personal Agent. Each user and administrator logs on with a user name and password. Log on rules permit the administrator to specify the following items for each user account: idle session timeout maximum number of time a user can log on after a password expires number of failed log on attempts permitted before the account is locked duration of the lock out, which includes the requirement for an administrator to unlock the account October 2017 Avaya Aura Application Server 5300 Overview 127

128 Security, administration, and maintenance Password rules are configured using the AS 5300 Element Manager Console. The rules specify minimum password length maximum password length minimum number of numerical characters minimum number of lowercase letters minimum number of uppercase characters minimum number of special characters maximum number of identical consecutive characters minimum number of characters different from the previous password. password history (number of passwords stored, used to ensure that passwords are not reused) restricts the use of user ID or reverse user ID in the password restricts the use of dictionary words in the password initial password reset lockout after a configurable number of failed authorization attempts maximum password life password expiry notification minimum password life lockout due to account inactivity idle session timeout All passwords are encrypted before they are stored in the database. The system provides the ability to: configure the authorized methods for all users. The methods display in the Authorized Methods menu of the AS 5300 Element Manager Console. configure the system wide grace period and nonce usage count using the Authentication configuration parameters in the AS 5300 Element Manager Console. enable in-session authentication. validate the nonce-count parameter using a parameter in the AS 5300 Element Manager Console. The AS 5300 Session Manager configuration parameters support the nonce parameters. The subscriber can change the password for their Personal Agent, Avaya Aura AS 5300 Office Client, and Avaya Aura AS 5300 UC Client. If this password expires or changes during an active call, the call is not disconnected during re-registration. Logs are generated after an administrator accesses (successfully or unsuccessfully) the AS 5300 Element Manager Console or the Provisioning Client, or uses the Open Provisioning Interface. The Application Server 5300 system also generates logs after passwords change. October 2017 Avaya Aura Application Server 5300 Overview 128

129 Security User administration provides the ability to: create or delete a user account assign a role to a user force the user to change the password on next log on designate a user password to never expire enable or disable a user account unlock a user account if it becomes locked due to failed log on attempts view the last time a user logged on Access control Application Server 5300 controls access using IPsec. The following figure shows the main communication paths and access points. Figure 14: Application Server 5300 access control The system uses Transport Layer Security (TLS) to secure the signaling interfaces to: PRI Gateway IAD clients IP Deskphones with SIP firmware Avaya Aura AS 5300 UC Client Avaya Media Server The system supports two types of secure channels that use TLS: SIP call signaling October 2017 Avaya Aura Application Server 5300 Overview 129

130 Security, administration, and maintenance HTTPS: OMI, OPI and SOPI TLS mutual authentication requires that all network elements and endpoints must exchange X.509 certificates. When a client connects with a server, both endpoints exchange certificates to authenticate each other. To support TLS mutual authentication for end devices (for example, the Avaya Aura AS 5300 UC Client and 1120E IP Deskphone), a network configuration parameter disables (default) and enables the mutual authentication for end user devices. To support TLS mutual authentication for system and subscriber HTTPS interfaces, a network configuration parameter disables (default) and enables the mutual HTTPS authentication. To support both the end user and administration authentications, certificates must be installed on the devices and the computer for the administration user interfaces (including the AS 5300 Element Manager Console). To implement certificates, the AS 5300 Element Manager Console supports the PKCS12 secure container for private key, signed certificate, and Certificate Authority (CA) certificates. This secure container uses an additional password to ensure security. Certificates need to be checked for validity, because CA can revoke the certificate. System uses the CRL and OCSP to validate the certificates. TLS uses X.509 certificates for authentication. Application Server 5300 is compliant with United States Department of Defense (DoD) Public Key Infrastructure (PKI) requirements for the use of X. 509 certificates. Important: The secure debug port is for Avaya use only. The system generates a log each time the port is accessed. The secure debug port uses authentication and authorization during the logon process. The system limits the number of simultaneous access sessions. During the connection process to the secure port, the system hides the input password. After establishing a connection, communication uses raw mode. The debug port also supports security banners, which require the user to acknowledge the banner. Host-based intrusion detection system Federal requirements specify that each server must run a Host-Based Intrusion Detection System (HIDS) to detect potential attacks on the system. Application Server 5300 includes OSSEC agents. OSSEC is an actively updated open source HIDS solution. OSSEC uses agents (clients) to monitor individual servers, and these agents report events to an external (customer-provided) OSSEC Server. The OSSEC Server is not part of the Application Server 5300 solution. For more information, see Avaya Aura Application Server 5300 Security, NN Traffic separation Traffic separation causes routing of messages, based on their contents and type. Traffic separates onto different physical or logical interfaces. October 2017 Avaya Aura Application Server 5300 Overview 130

131 Security Application Server 5300 separates traffic into four main areas: Internal OAMP traffic: contains OAMP traffic internal to the enclave. Examples include messages from the AS 5300 Element Manager, and messages to local operation support systems (OSS) like Switch Experts. External OAMP traffic: contains OAMP traffic external to the enclave. An example is messages from the AS 5300 Element Manager to an external OSS. Signaling: contains call signaling and Personal Agent signaling. Examples include all SIP traffic and the downloading of service profiles. Media: contains bearer traffic. An example is Avaya MS communications using Real-time Transport Protocol (RTP). Each of these areas results in the configuration of a separate subnet within the Application Server 5300 system. A source IP address-based routing scheme separates the traffic onto different physical or logical interfaces. When a message comes to the Application Server 5300, the system determines the subnet based on the information received, and routes the traffic according to the information in the following table. Table 21: Traffic type and routing requirements Requested address type Requested traffic type First choice route Second choice route Third choice route Final choice Server address Internal OAM Internal OAM (Default) Server address Internal OAM (Default) server address External OAM External OAM Server address Internal OAM (Default) server address Signaling Signaling Server address Internal OAM (Default) server address Media Media Server address Internal OAM (Default) server address Service address Internal OAM Network element Internal OAM service address Internal OAM (Default) server address External OAM Network element External OAM service address Network element Internal OAM service address External OAM server address Internal OAM (Default) server address Table continues October 2017 Avaya Aura Application Server 5300 Overview 131

132 Security, administration, and maintenance Requested address type Requested traffic type First choice route Second choice route Third choice route Final choice Signaling Network element Signaling service address Signaling Server address Internal OAM (Default) server address Media Network element Media Service address Media Server address Internal OAM (Default) server address Traffic separation is typically set up during system installation. During the installation, installers use command line tools and the AS 5300 Element Manager Console to configure the interfaces and subnets. After installation, routing takes place as shown in the following table. Source IP address Destination IP address Next-hop behavior In the non-default subnet Inside the subnet Route direct on the subnet interface. In the non-default subnet Outside the subnet Route to the default router in the subnet. Other In any local subnet Route direct on the local subnet. Other Not in any local subnet Route to the default router of the default subnet. The following restrictions apply: Up to four subnets per server can be configured. Subnets cannot overlap. Network interfaces cannot be disabled by the administrator. For more information, see Avaya Aura Application Server 5300 Network Separation Installation Method. For information about traffic and network topology, see Avaya Aura Application Server 5300 Planning and Engineering, NN SIP TLS Identity Checking The SIP TLS Identity Checking feature prevents spoofing and other attacks directed on SIP TLS connections. It protects TLS connections between AS 5300 clients and the AS 5300 Session Manager servers. In addition to standard TLS protocol used to secure SIP signaling channels an identity check is added for the SIP-request transmitted through these channels. If the identity check fails, then the SIP-request is rejected. An alarm is raised and the potential security breach is logged. Other security measures The Application Server 5300 uses the following measures to enhance security: (optional) pre-log on warning banner, requires acknowledgement before the user can continue (optional) post-log on warning banner, requires acknowledgement before the user can continue October 2017 Avaya Aura Application Server 5300 Overview 132

133 Administration and maintenance security logs capture access information (for example, log on success, log on failure, account lockout, account log on timeout) HTTP port disabling for the AS 5300 Element Manager, Provisioning Manager, and Personal Agent Manager certificate management encrypted database password hardened operating system with file system integrity tools, an open source host-based intrusion detection system (HIDS) called OSSEC, and optional antivirus software increased database security with the following measures: - no command line access to database programs (for example, mysql) - security hardening during system installation to remove access to database executables and to autogenerate user names and passwords to the database accounts message appears on the Personal Agent to indicate the last time the account was last used and when the last data update occurred message appears on the AS 5300 Element Manager Console and Provisioning Client to indicate the last time the account was last used audit logs track accesses and changes to the data (through the Personal Agent, Avaya Aura AS 5300 UC Client, Avaya Aura AS 5300 Office Client, SIP Clients, third-party clients, and Subscriber Open Provisioning Interface) audit logs are protected to prevent unauthorized access, modification, or deletion alarm activates when user or administrator accounts become locked because of failed access attempts. The alarm does not indicate the user information. The alarm clears when the lockout time expires. Common Access Card (CAC) support for two-factor authentication for the Linux shell (command line access) and the AS 5300 Element Manager Console. The browser on a PC supports CAC authentication for Web-based clients (for example, Provisioning Client). Administration and maintenance This section outlines Application Server 5300 administration. Tools and utilities The tools to perform Application Server 5300 administration functions include: AS 5300 Element Manager Console: Depending on the level of administration access and security privileges, use this software to enable or disable security features, and to configure thresholds and other security-related parameters. October 2017 Avaya Aura Application Server 5300 Overview 133

134 Security, administration, and maintenance Provisioning Client: Use this tool to manage subscribers at the provider and Enterprise domain level. Personal Agent: Use this Web-based software to manage features and routes. Subscriber also use the Personal Agent, for example, to register and add personal details according to the limits you define. For further information, see the following documents: Avaya Aura Application Server 5300 Personal Agent User Guide, NN Avaya Aura Application Server 5300 Using the Provisioning Client, NN Avaya Aura Application Server 5300 Configuration, NN Avaya Aura Application Server 5300 Administration, NN October 2017 Avaya Aura Application Server 5300 Overview 134

135 Chapter 21: Application Server 5300 fundamentals The Application Server 5300 contains a number of building blocks. The following chapters describe these building blocks. Navigation AS 5300 Element Manager fundamentals on page 136 AS 5300 Session Manager fundamentals on page 142 Accounting Manager fundamentals on page 163 Database Manager fundamentals on page 165 Provisioning Manager and Personal Agent Manager fundamentals on page 171 End-user clients on page 173 October 2017 Avaya Aura Application Server 5300 Overview 135

136 Chapter 22: AS 5300 Element Manager fundamentals The AS 5300 Element Manager is a core component of the Application Server 5300 infrastructure. It supports the services used to communicate with and manage the network elements and servers. Navigation Description on page 136 Fault management on page 137 Performance management on page 138 AS 5300 Element Manager security on page 139 AS 5300 Element Manager administration on page 140 AS5300 Element Manager Console fundamentals on page 140 Description The AS 5300 Element Manager network element provides the services that support communication amongst the Application Server 5300 network elements and management requests issued from the AS 5300 Element Manager Console. In conjunction with the AS 5300 Element Manager Console, AS 5300 Element Manager supports the following functionality: system operations administration system software management - software inventory, a list of available software loads - software updates - deployment, start, and monitoring system configuration - add, modify, delete network elements - service-specific parameters system maintenance - start, stop, kill, and restart network element services October 2017 Avaya Aura Application Server 5300 Overview 136

137 Fault management fault monitoring - logs - alarms - archival of logs (which includes fault events) system performance monitoring - operational measurements - configurable collection period and archival of operational measurements network management interfaces - Simple Object Access Protocol (SOAP) over Hypertext Transport Protocol Secure (HTTPS) - AS 5300 Element Manager Console AS 5300 Element Manager interfaces In the Application Server 5300 system communications scheme, the AS 5300 Element Manager sits between the Application Server 5300 network elements and the AS 5300 Element Manager Console. For more information about the interfaces of the AS 5300 Element Manager, see: Transmission Control Protocol/Internet Protocol on page 86 Structured Query Language on page 86 Simple Object Access Protocol on page 86 Simple Network Management Protocol version 2c on page 85 Secure File Transfer Protocol on page 85 Fault management This section contains the following topics SNMP information on page 137 Local storage on page 138 SNMP information The following information about how the AS 5300 Element Manager uses Simple Network Management Protocol (SNMP) is useful for integrating the Application Server 5300 with an OSS system such as Switch Expert. October 2017 Avaya Aura Application Server 5300 Overview 137

138 AS 5300 Element Manager fundamentals To forward traps northbound, configure the OSS host as the destination host in the SNMP Manager. The SNMP Manager profile associates the OSS host with the AS 5300 Element Manager in the Application Server 5300 network. Ensure that the SNMP agent on the destination host allows SNMPv2c for communication. For the configuration procedures, see Avaya Aura Application Server 5300 Configuration, NN For networks that poll the AS 5300 Element Manager for data, the AS 5300 Element Manager offers an SNMP port. After you configure SNMP parameters for the host that collects the data, the client and SNMP Manager use the same community string. For more information, see Avaya Aura Application Server 5300 Administration, NN Local storage Log, alarm, and operational measurement (OM) data is recorded to disk on the AS 5300 Element Manager that a network element is configured to use. Those records are stored in the directory /var/mcp/oss/ In this directory, the system uses a subdirectory for each network element instance that reports data to the AS 5300 Element Manager. Performance management Administrators use the AS 5300 Element Manager Console to monitor performance metrics of the AS 5300 Element Manager and its hosting server. The Logical View and Physical View windows of the AS 5300 Element Manager Console provide an indication of the AS 5300 Element Manager and server operational state. For each server, the system monitors CPU, memory, disk, and network interface usage. Operational measurements (OM) for the AS 5300 Element Manager processes, consist of counters and gauges. While the server monitor runs, the system records server OMs to disk on the active instance of the AS 5300 Element Manager. To see these operational measurements, use the OM browser in the AS 5300 Element Manager Console. Operational measurements OMs consist of counters and gauges that monitor the activity of the AS 5300 Element Manager processes. For more information about viewing AS 5300 Element Manager operational measurements, see Avaya Aura Application Server 5300 Troubleshooting and Fault Management, NN For more information about OMs, see Avaya Aura Application Server 5300 Operational Measurements Reference, NN Operational measurements tally in memory and recorded in an active file stored in the /var/mcp/ spool directory on the network element that is generating the OMs. After the interval provisioned in October 2017 Avaya Aura Application Server 5300 Overview 138

139 AS 5300 Element Manager security the OfficeTransferPeriod configuration parameter expires, the data flushes to the active file, the file closes, and then the file transfers to the AS 5300 Element Manager. The AS 5300 Element Manager records the data in the /var/mcp/oss directory as a holding file. This file closes after it reaches the size or interval configured in the OM Format Path. Use the AS 5300 Element Manager Console OM browser to view OMs generated by the AS 5300 Element Manager. By default, the active OMs display. These OMs are not recorded to disk and represent the events that occurred since the last OfficeTransferPeriod interval expired. To display the most recent holding OMs, select Holding from the Type list. These OMs are stored to disk after the last OfficeTransferPeriod interval expires. To view older OMs, configure an FTP Push job to an OSS server and view the historic information there. The administrator configures the OM file retention period at the system level. For more information about the procedure for configuring the retention period, see Avaya Aura Application Server 5300 Configuration, NN Local storage of operational measurements The system records OM data to disk on the AS 5300 Element Manager. These records are stored in the directory /var/mcp/oss/om/ Under this directory, a suddirectory exists for each network element instance that reports data to the AS 5300 Element Manager. AS 5300 Element Manager security This section describes the server-level security of the AS 5300 Element Manager. The AS 5300 Element Manager operates within the protected Application Server 5300 network, isolated from public network security risks. Passwords protect the AS 5300 Element Manager and hosting servers from unauthorized access. Access must be limited to trusted administrative personnel. To prevent unauthorized access to the servers, Avaya recommends that the server password and server IP addresses remain confidential. After initial provisioning, the system administrator can create an administrative role without IPAddressService privileges and assign administrators with maintenance responsibilities to this role. Administrators with this role cannot view IP addresses, add servers to the network, or perform most configuration tasks. This role is appropriate for an alarm and log monitoring-only administrative account. To increase network security, change the default SNMP community string values for the server from the default value (public) to some other value. The SNMP message traffic of the hosted components use the configured SNMP community string value. For more information about configuring an SNMP October 2017 Avaya Aura Application Server 5300 Overview 139

140 AS 5300 Element Manager fundamentals Profile to use the new community string, see Avaya Aura Application Server 5300 Configuration, NN AS 5300 Element Manager Console message of the day You can configure a message of the day (motd) file by using the AS 5300 Element Manager. The contents of this file appear at the AS 5300 Element Manager Console interface after a successful log on. If the motd file does not exist, no motd window appears. The motd file does not persist after software patches. During the AS 5300 Element Manager software patching, the directory that holds the motd file is overwritten. The motd file is not automatically created or updated on the second AS 5300 Element Manager instance. Transfer the file to or create a second version of the file on the second AS 5300 Element Manager instance. AS 5300 Element Manager administration The AS 5300 Element Manager uses software loads to determine the versions of software available for use. Administrators add software loads onto the server hosting the AS 5300 Element Manager using zip files. After an administrator performs an add or update task from the AS 5300 Element Manager Console, the AS 5300 Element Manager accesses the installed software loads and generates the load list displayed in the AS 5300 Element Manager Console. To free up disk space on the server, administrators with the appropriate privileges can remove old and unused software versions by removing the associated directory and zip file from the server hosting the AS 5300 Element Manager. Use Application Server 5300 server backups to recover from a catastrophic hardware failure where a complete restore of the server software (both third-party and Application Server software) is required. Avaya recommends backups of the AS 5300 Element Manager hosting servers after thirdparty software updates, such as an applied operating system patch. For information about the backup procedures, see Avaya Aura Application Server 5300 Administration, NN AS5300 Element Manager Console fundamentals Administrators use the AS 5300 Element Manager Console to configure and maintain the Application Server 5300 system. Administrators load the AS 5300 Element Manager Console software onto a personal computer (PC) that is operating a supported version of Microsoft Windows. Figure 15: AS 5300 Element Manager Console on page 141 shows the AS 5300 Element Manager Console display. October 2017 Avaya Aura Application Server 5300 Overview 140

141 AS5300 Element Manager Console fundamentals Figure 15: AS 5300 Element Manager Console The AS 5300 Element Manager Console provides the following functions: administer system, database, and service components deploy and configure system sites, servers, components, and component services monitor the system using alarms, logs, and operational measurements manage the collection of operations, administration, and maintenance information The system limits the number of administrators that can access the system at the same time. For more information about the AS 5300 Element Manager Console, see Avaya Aura Application Server 5300 Configuration, NN October 2017 Avaya Aura Application Server 5300 Overview 141

142 Chapter 23: AS 5300 Session Manager fundamentals This chapter describes the Application Server 5300 Session Manager. The AS 5300 Session Manager handles Session Initiation Protocol (SIP) services. Navigation Description on page 142 Services and features on page 146 Reliability and fault tolerance on page 159 Interfaces on page 159 Accounting on page 161 Security on page 161 Description The AS 5300 Session Manager is a service execution engine that provides the following functionality: core signaling functionality enabling communication among SIP clients Back-to-Back User Agent SIP Registrar Call Processing Language (CPL) interpretation location server optional presence subscription and notification The AS 5300 Session Manager handles SIP sessions and applications, and provides the core services that enable communication between SIP clients. October 2017 Avaya Aura Application Server 5300 Overview 142

143 Configuration types Configuration types This section describes the configurations possible for the AS 5300 Session Manager in an Application Server 5300 deployment: MFSS and LSC configuration on page 143 MFSS and LSC configuration With the appropriate licence keys, administrators can configure each AS 5300 Session Manager in an Avaya Aura Application Server 5300 deployment to perform the function of either a softswitch (SS) or a Local Session Controller (LSC). A multifunction switch (MFS) and an SS provide Multifunction Softswitch (MFSS) functionality. Application Server 5300 supports the following configurations: LSC configuration on page 144 MFSS and LSC combo-configuration on page 145 An administrator must configure all the SS and LSC AS 5300 Session Managers and any Edge Border Controllers (EBC) in a system as external nodes. For each local AS 5300 Session Manager, an administrator must use the AS 5300 Element Manager to configure all the external SS and LSC AS 5300 Session Managers. Optionally, a third-party EBC, which faces the access link, connects to the SS AS 5300 Session Managers and the LSC AS 5300 Session Managers. To simplify configuration, consider each remote SS AS 5300 Session Manager and EBC or remote LSC AS 5300 Session Manager and EBC group as a single external network element. Configure each group (external network element) as either SS or LSC on the AS 5300 Element Manager. The IP address of each remote SS and EBC and of each remote LSC and EBC external element combination is the IP address of the EBC that fronts the remote SS or LSC AS 5300 Session Manager. If a local EBC fronts a local SS or LSC AS 5300 Session Manager, the administrator must configure the IP address of that local EBC on the AS 5300 Element Manager as well. For example, the following points apply to Figure 16: MFSS and LSC configuration simplified network diagram on page 144: Configure SS AS 5300 Session Manager (SESM) A with the IP addresses of: local EBC A, remote EBC 1 (for communication with LSC SESM 1), and remote EBC B (for communication with SS SESM B). Configure SS SESM A with the functional role of SS. Configure LSC SESM 1 with the IP addresses of: local EBC 1 and remote EBC A (for communication with SS SESM A). Configure LSC SESM 1 with the functional role of LSC. Configure SS SESM B with the IP addresses of local EBC B, remote EBC A, and remote EBC 2. Configure SS SESM B with the functional role of an SS. October 2017 Avaya Aura Application Server 5300 Overview 143

144 AS 5300 Session Manager fundamentals Configure LSC SESM 2 with the IP addresses of local EBC 2 and remote EBC B. Configure LSC SESM 2 with the functional role of LSC. Configure the SS SESM as an SS network element with the same IP address as that of its local EBC. Configure the LSC SESM as an LSC network element with the same IP address as that of its local EBC. Configure EBC an EBC network element. For more information about configuring network elements, see Avaya Aura Application Server 5300 Configuration, NN Figure 16: MFSS and LSC configuration simplified network diagram For information about LSC and MFSS system support for multiple AS 5300 Session Managers, see Multiple AS 5300 Session Managers for MFSS and LSC configurations on page 145. LSC configuration Application Server 5300 supports a single active LSC AS 5300 Session Manager for each system. The following points apply to an LSC mode configuration: All AS 5300 Session Managers function as LSCs. An EBC fronts the LSC AS 5300 Session Manager. Each LSC AS 5300 Session Manager services predetermined ranges of DNs, unless the system supports Hybrid Routing. Each LSC AS 5300 Session Manager has a unique Call Control Agent ID (CCA-ID). Each LSC AS 5300 Session Manager has its own Assured Service Admission Control (ASAC) budget. October 2017 Avaya Aura Application Server 5300 Overview 144

145 Configuration types MFSS and LSC combo-configuration Application Server 5300 supports a single active LSC AS 5300 Session Manager for each system and an MFSS AS 5300 Session Manager. The following points apply to an MFSS and LSC mixedmode configuration: Each AS 5300 Session Manager in the system functions as either an SS or an LSC. An EBC fronts each SS AS 5300 Session Manager. An SS AS 5300 Session Manager in each system tends the LSC AS 5300 Session Manager in that system. Each SS AS 5300 Session Manager has a unique Call Control Agent ID (CCA-ID). Each LSC AS 5300 Session Manager has a unique CCA-ID. Each SS AS 5300 Session Manager has its own ASAC budget. Each LSC AS 5300 Session Manager has its own ASAC budget. The enclave includes a CS2100 to handle TDM routing. Multiple AS 5300 Session Managers for MFSS and LSC configurations An extra AS 5300 Session Manager supports additional users by becoming a secondary SS AS 5300 Session Manager or slave LSC AS 5300 Session Manager. The following figure shows four enclaves with multiple AS 5300 Session Manager. Figure 17: Multiple AS 5300 Session Manager deployments The following configuration rules apply: For an enclave that does not have an SS (Enclaves 3 and 4 in the previous figure): - One AS 5300 Session Manager must be configured as a Master LSC. - All other AS 5300 Session Managers must be configured as Slave LSCs. October 2017 Avaya Aura Application Server 5300 Overview 145

146 AS 5300 Session Manager fundamentals - Assured Service Admission Control (ASAC) must be enabled on the Master LSC and disabled on the Slave LSCs. - Each LSC must have a unique Call Control Agent ID (CCA-ID). - All interenclave calls must route through the Master LSC. - If an EBC fronts the enclave, the EBC must route all incoming calls to the Master LSC. The Master LSC will route the call to the end user or to the appropriate Slave LSC. - The PRI Gateway must route all incoming calls to the Master LSC. For an enclave that has one or more LSCs and SSes (Enclaves 1 and 2 in the previous figure): - One AS 5300 Session Manager must be configured as a Master LSC. - At least one AS 5300 Session Manager must be configured as an SS. The system can have multiple SSes. - Each additional AS 5300 Session Manager must be configured as a Slave LSC. - The Master LSC must be associated with the single SS. - Each LSC and SS must have a unique CCA-ID. - Each SS must be associated with all the LSCs that it serves. - All interenclave calls must route to the Master LSC and its serving SS. - The PRI Gateway must route all calls to a local SS. In cases where there are multiple SSes, any SS can be used. To support multiple AS 5300 Session Managers: the EBC, if configured, must support multiple network interfaces and must allow incoming messages from one interface to be configured to forward the message to a specific interface. every AS 5300 Session Manager can only interface with one EBC. only one Master LSC can be configured in an enclave. For more information about ASAC, see Assured Services Admission Control on page 153. For more information about configuring multiple AS 5300 Session Manager, see Avaya Aura Application Server 5300 Configuration, NN For information about configuring users and domains, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Services and features This section describes the following AS 5300 Session Manager services and features: CallP Checkpointing support on page 147 Privacy Control service on page 148 Service set enforcement on page 148 October 2017 Avaya Aura Application Server 5300 Overview 146

147 Services and features Authentication services on page 148 Instant messaging, IM screening and routing services on page 149 Route codes on page 149 Presence on page 150 Registration: static and dynamic on page 151 Logging SIP registration on page 152 Global Address Book on page 152 Global Routable ID on page 152 Multiple AS 5300 Session Manager support on page 153 Preloaded Routes on page 153 Assured Services Admission Control on page 153 Session Timer Support on page 155 Offer/Answer Support on page 157 AS 5300 Session Manager Call Feature support on page 158 CallP Checkpointing support With CallP Checkpointing, the system can preserve calls in failure conditions. During a failure condition, CallP Checkpointing does not preserve the availability of advanced features (for example, Music on Hold). CallP Checkpointing provides the following AS 5300 Session Manager capabilities: The ability to checkpoint active calls to the standby instance of a AS 5300 Session Manager. For the purposes of checkpointing, an active stable call is one that is answered. Answering a SIP call means that the 200 OK response to the initial invite is received or sent by the active AS 5300 Session Manager. The ability to checkpoint subscriptions to the standby instance of a AS 5300 Session Manager. Subscriptions refer to SIP SUBSCRIBE messages for a particular event package. Because of this checkpointing, failover preserves the subscription to services, such as Presence or Call Park. The ability to checkpoint network call logs to the standby instance of a AS 5300 Session Manager. The call log information is preserved so that users can get a record of their calls from the Personal Agent even after a failover. The database write occurs upon call completion or rejection. Enhanced presence processing and recovery of On the Phone presence after failover. After a failover, the newly active instance of the AS 5300 Session Manager can recover a user's presence state to an On the Phone state if the user is active in a call. October 2017 Avaya Aura Application Server 5300 Overview 147

148 AS 5300 Session Manager fundamentals Application Server 5300 provides four overload levels: none, minor, major, and severe. As the system reaches each overload level, the behavior of the system changes so the system can recover. The changes are cumulative. - If Minor overload is reached and the system stays there for a few seconds, Application Server 5300 stops generating Presence notifications. - If Major overload is reached, all Instant Messaging in the system are halted. - If the Severe level is reached, all new sessions are blocked. For each of the overload conditions, the same alarm is raised but different severities are assigned to the alarm. Privacy Control service The AS 5300 Session Manager supports Privacy Control based on draft-ietf-sip-privacy. This draft defines a mechanism that permits clients to supply a network server with their private user information while at the same time instructing the server not to pass that information outside the boundaries of the trusted network. The information is passed in a Remote-Party-ID header with the privacy indicator configured to full. The AS 5300 Session Manager removes this header any time it forwards the message out over a public network interface. Service set enforcement The AS 5300 Session Manager enforces the service set. A service set defines a user's enabled network services, such as audio conferencing and subscriber profile. The service provider defines the available service sets for the domain. The domain administrator assigns a specific service set to a subscriber. Authentication services The AS 5300 Session Manager authenticates SIP messages that establish a new session or a new connection outside of an existing session. The AS 5300 Session Manager performs user authentication after the server receives an incoming SIP request. The AS 5300 Session Manager supports the challenge-based Digest method for SIP Client-to-Proxy authentication. In Digest authentication, the AS 5300 Session Manager challenges a client if a SIP request is received. The SIP Client resends a SIP request with a valid password and user name attached. The authenticated request types can be configured. For more information, see Avaya Aura Application Server 5300 Configuration, NN Application Server 5300 supports only US ASCII for user names. The software performs authentication using the password of the subscriber originating the call. Only subscribers from a local domain have a password stored in the database to authenticate against. If a subscriber from a foreign domain places a call and the call requires authentication for a known October 2017 Avaya Aura Application Server 5300 Overview 148

149 Services and features foreign domain, the authentication fails because the database does not have the subscriber's information. As a result, the call is blocked. System administrators can also specify foreign proxies in the NodalAuth field of the AS 5300 Element Manager Console Authentication tab of AS 5300 Session Manager Configuration. For more information, see Avaya Aura Application Server 5300 Configuration, NN By specifying foreign proxies, no requests originating from those proxies fail because of authentication. Nodal Authentication is the process by which a AS 5300 Session Manager identifies that another node in the system is Trusted. An administrator designates a node as Trusted by configuring its address in the Trusted Nodes field on the Authentication tab provided by the console. If a node is Trusted, the AS 5300 Session Manager does not require further credentials for any requests originating from the node. If trusted nodes are configured, devices such as gateways that do not have valid user and password information can originate requests to the AS 5300 Session Manager. Trusted nodes can also be configured to permit foreign domain proxies to send requests that are otherwise blocked, because they are not valid users on the system. Instant messaging, IM screening and routing services Instant Messages route simultaneously only to a subscriber's dynamically registered routes. Upon receipt of an instant message, a client can respond back to the address supplied in the Contact header to make sure that the response is sent back to the same client device that originally sent the message. AS 5300 Session Manager provides the IM screening and routing service. Using the IM screening and routing service, a user can block incoming IMs from individuals or groups whose names appear in the user's personal address book, global address book, directory, or predefined list of addresses using the Route Wizard of the Personal Agent. IM screening and routing information is converted into CPL script and then uploaded to the AS 5300 Session Manager and stored in Database Manager against the user's profile. Route codes The Public Switched Telephone Network (PSTN) routes calls over specific circuits (commonly referred to as trunks) between Time Division Multiplexed (TDM) circuit switches. A group of trunks that connect to the same target switch or network is called a trunk group. Trunk groups have labels, which provide information about the previous and next TDM switch that participates in the routing of the call. A route code is a special purpose code that informs the switch about special routing or termination requirements. According to the route codes, the AS 5300 Session Manager configures tgrp and trunk group parameters to the user portion of Request URI on the originating side. The AS 5300 Session Manager adds these tgrp and trunk-context parameters and a PRI Gateway uses the parameters to choose which trunk to route the call on. There must be a correspondence between the Route Code and the value for the tgrp parameter and the trunk-context parameter. For more information about tgrp and the trunk-context parameters, see RFC October 2017 Avaya Aura Application Server 5300 Overview 149

150 AS 5300 Session Manager fundamentals Table 22: Route code usage and trunk context Route code Use tgrp Trunk context 10 Voice Call (default) NA NA 11 Circuit Switched Data ccdata dsn.mil 12 Satellite Avoidance nosat dsn.mil 5 Hotline voice grade hotline dsn.mil 6 Hotline data grade hotline-ccdata dsn.mil The system uses codes 5 and 6 Hotline routes. Hotline users do not dial route code 5 or 6. Non Hotline users add the 10, 11, or 12 route code as a prefix to the directory number (DN). Because 10 is the default route code for a voice call, users have the option to not dial route code 10. For example, User A wants to place a Circuit Switched Data call to User B (DN ). User A must dial Users can also add a Multi-Level Precedence and Preemption (MLPP) access code and precedence code. For example, User A wants to place a Circuit Switched Data call to User B (DN ) with a precedence of Priority. User A must dial (where 9 is the access code, 1 is the precedence level, 11 is the route code, and is the DN for User B). Table 23: MLPP precedence mapping Precedence level Numeric level Flash Override 0 Flash 1 Immediate 2 Priority 3 Routine 4 Presence After a subscriber initially registers, the presence status changes to online in the SIP registration message by default. Subscribers can subscribe to watch the status of other users, and to coordinate the status of their own devices. This information is maintained in an in-memory table on the AS 5300 Session Manager (Presence software). The information stored in this table includes: the user to watch the party who requests the subscription the correlation information that identifies the particular subscription request the contact information about where to send the notifications that the system generates if the subscription is active October 2017 Avaya Aura Application Server 5300 Overview 150

151 Services and features If a user's presence changes (for example, to Unavailable - Busy), the AS 5300 Session Manager automatically sends a registration message. The AS 5300 Session Manager then checks its in-memory table to see what the previous presence state was. If the update causes a material change in the presence state, the AS 5300 Session Manager looks up the subscribers that need to be notified of the change (also in memory). After the lookup is done, the AS 5300 Session Manager sends a Notify message to each subscribed user. When a person requests a presence subscription, the user that is to be watched receives a message in the Avaya Aura AS 5300 UC Client or Avaya Aura AS 5300 Office Client that a new watcher has requested the information. The subscriber must accept or reject the presence subscription request before the person can see presence changes. The administrator configures the Presence service. When Presence is enabled, subscribers can enable or disable the feature from their Personal Agent. For more information, see the following documents: Avaya Aura Application Server 5300 Personal Agent User Guide, NN Avaya Aura Application Server 5300 UC Client User Guide, NN Avaya Aura Application Server 5300 Using the Provisioning Client, NN Avaya Aura Application Server 5300 Office Client User Guide, NN Registration: static and dynamic Registration can take two forms: Static: Users or administrators can perform static registrations. With static registration, the user can obtain a presence if not logged into the network. The user can obtain a presence and an account in one of the following ways: - Using the Provisioning Client, the administrator can add a user account and assign a static route. - User account contact information, such as PSTN numbers or cell phone numbers, can be added to the routing information. Dynamic: Dynamic Registration is the automated process by which SIP clients bind their device address with the well-known address for the user. This process uses the SIP Register method. - After a Register message is received from the client, the AS 5300 Session Manager writes the client's device address to persistent storage in the database. An individual subscriber can register on multiple client devices simultaneously, and each individual address is stored in the database. After a request arrives addressed to the well-known address for a subscriber, the AS 5300 Session Manager sends the request to those device addresses stored against the specified subscriber. - Each individual device address has an expiration time associated with it (by the client device in the Register message). After the expiration period, the device address is removed. The client device must refresh the address by resending a Register message before the expiry time. After a user logs on, reregistration is automatic with SIP Clients. October 2017 Avaya Aura Application Server 5300 Overview 151

152 AS 5300 Session Manager fundamentals Important: Only level domains support registration. If you configure end-user client devices to reference the subdomain instead of the top-level domain, services can be impacted adversely. For instance, if the user is moved from one AS 5300 Session Manager to another because of a subdomain change, the client must be reconfigured. Additionally, some telephony translation configurations can prevent calls from completing if users are logged on under their subdomains. Therefore, end users must not be made aware of anything other than the top-level domain they belong to after configuring their client devices. Logging SIP registration About this task To meet the requirements of the Instant Messaging Security Technical Implementation Guide (or Guidelines) (STIG), the system must log all successful and unsuccessful initial registrations of subscribers as security logs. By default, the system logs unsuccessful registrations as security logs. An administrator can use the AS 5300 Element Manager Console to enable the logging of successful (initial) SIP registrations as a security log. They system does not log re-registrations. Global Address Book The system stores Subscriber address book information in the network so that the data can be accessed from all clients. The information downloads in bulk after a client comes online using a Simple Object Access Protocol (SOAP) interface. To receive updates to the Global Address Book after the initial download, the client subscribes to the Global Address Book event package. After an update occurs through the Personal Agent or one of the clients, a Notify message is sent to the client indicating the entries that have changed. The client can then incrementally update the view of the information. The Global Address Book includes a List of Friends. Each subscriber must create a personal Address Book and designate a List of Friends. For each of these specified entries, the client automatically subscribes to a presence event package. This permits the client to monitor and update the network presence of each Friend (for example, online or offline). Global Routable ID The transfer service uses the Global Routable ID during interenclave REFER scenarios. An administrator uses the AS 5300 Element Manager Console to configure the Global Routable ID parameter. This parameter contains the userinfo portion of a URI, which identifies the AS 5300 Session Manager as an addressable node. An administrator must either add translations for AS October 2017 Avaya Aura Application Server 5300 Overview 152

153 Services and features 5300 Session Manager in other systems, or ensure that the translations already exist, to send messages for this ID to the associated AS 5300 Session Manager. For information on configuring a Global Routable ID, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Multiple AS 5300 Session Manager support When an AS 5300 Session Manager becomes overloaded, additional AS 5300 Session Manager can be added to alleviate the overload. Extra AS 5300 Session Manager require separate servers, and in redundant deployments these additional servers must be deployed in pairs. After deploying additional servers, administrators can assign users to particular AS 5300 Session Manager. In this case, the selected AS 5300 Session Manager is the user's home AS 5300 Session Manager. For information about supporting multiple AS 5300 Session Manager in an LSC or MFSS configuration, see Multiple AS 5300 Session Managers for MFSS and LSC configurations on page 145. For more information on configuring multiple AS 5300 Session Manager, see Avaya Aura Application Server 5300 Configuration, NN For information on configuring users and domains, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Preloaded Routes The Preloaded Routes service determines whether to route a call to an EBC before the next destination. To route the call to an EBC, the service inserts two route headers into the INVITE. The first route header points to the local EBC and the second route header points to the next destination (for example, SS AS 5300 Session Manager, LSC AS 5300 Session Manager, or EBC). After the EBC receives the INVITE, the EBC removes the first route header (the route header that matches the EBC) and routes call to the destination in the second route header. With this strategy, the EBC does not perform translations that were already run on the previous AS 5300 Session Manager. Assured Services Admission Control The Application Server 5300 architecture consists of three network layers: the Edge layer, Access layer, and Defense Information Systems Network (DISN) Core layer. The Edge Layer is associated with the local Campus Area Network at a particular Base, Camp, Post, or Station. The DISN Core is the Department of Defense (DoD) wide area backbone network. The Access Layer consists of network facilities that connect the Edge Layer to the DISN Core. Assured Services Admission Control (ASAC) applies to Multifunction Soft Switch (MFSS) and Local Switch Controller (LSC) configurations. Private Branch Exchange (PBX) configurations do not support ASAC. October 2017 Avaya Aura Application Server 5300 Overview 153

154 AS 5300 Session Manager fundamentals The access link between the Customer Provider Edge (CPE) router and the Provider Edge (PE) router (PE-R) is resource-constrained. To ensure the Quality of Service (QoS) and availability of Access Network bandwidth for mission critical sessions (for example, command- and control-related sessions), the Application Server 5300 uses an engineered, threshold-based, Call Admission Control (CAC) mechanism to regulate Access Network usage. Figure 18: Application Server 5300 architecture layers CAC provides improved Quality of Service (QoS) and ensures that mission-critical voice and video sessions have adequate network bandwidth. CAC applies to interenclave voice or video calls. ASAC does not apply to intraenclave calls. The system can block new calls or preempt existing calls when voice or video traffic exceed the configured thresholds. The thresholds (also known as budgets) can be assigned to incoming and outgoing calls, with either separate or combined thresholds. The system tracks interenclave calls that are in progress, as well as calls being created (originating or receiving calls). If the budget is reached and a new call is being originated or received, the system looks for a lower priority call that can be preempted. A call can preempt only calls of a lower priority. If no lower priority call exists, the system rejects the new call. If a lower priority call exists, the parties on the lower priority call receive a warning and their call drops; then the higher priority call is established. E911 calls cannot be preempted by an incoming call, regardless of the incoming call priority. A call can preempt only calls in the same budget group. For example, if incoming and outgoing voice calls have separate budgets, a high priority incoming voice call can only preempt a lower priority incoming voice call. Voice calls and video calls use separate thresholds. ASAC functionality is extended for calls made by Type3 users who are located behind the EBC. ASAC provides threshold-based Call Admission Control (CAC) for Type3 users according to their location. ASAC budget Assured Services Admission Control (ASAC) provides threshold-based Call Admission Control (CAC) based on the associated media type (either audio or video). An administrator uses the AS October 2017 Avaya Aura Application Server 5300 Overview 154

155 Services and features 5300 Element Manager Console to configure budget profiles at the network level. The budget profile defines the call counts for audio and video media. Multiple nodes can share a single budget profile. For example, an administrator can define an audio budget profile with 50 calls and a video budget profile with 20 video calls. The administrator can then assign these profiles as the ASAC budget for both LSC AS 5300 Session Manager 1 and LSC AS 5300 Session Manager 2. The configured ASAC budget profiles apply to the access link used by interenclave calls. Calls inside the enclave do not travel over the budget-controlled access link. The budget can be nondirectional, where incoming and outgoing calls share the same budget, or it can be directional, where separate budgets exist for incoming and outgoing calls. The Local Session Controller (LSC) enforces the budget. The Multifunction Softswitch (MFSS) provides a policing function to protect the access links between the LSC and the MFSS. The LSC and MFSS keep track of all active interenclave active calls as well as new calls being created. If traffic for the LSC exceeds the configured threshold and there is no lower priority call to preempt, the LSC and MFSS reject new calls. If a lower priority call is in progress, the LSC and MFSS preempt the lower priority call and allow the new precedence call (priority above routine) to complete. A call can preempt only lower priority calls that share the same budget. With a directional budget, a call can preempt only lower-priority calls in the same direction (incoming or outgoing). When a subscriber places a video call on hold, the ASAC video budget assigned to the call is not released. When a subscriber who has an active video call drops the video, but continues with an audio-only call, the video budget is released. If a precedence video call is placed, and no bandwidth remains in the budget, the system can preempt a held call, thus making video bandwidth available for the preempting call. For more information about configuring ASAC budget profiles, see Avaya Aura Application Server 5300 Configuration, NN Originating and terminating call models The ASAC service runs on both originating call model and terminating call model. The system identifies a call as interenclave if there is CCA-ID parameter in the contact header of the incoming invite or if the call terminates to another external LSC and MFSS. For the originating call model, the ASAC service uses either the CCA-ID or source address of the packet to look up the ASAC budget. For the terminating call model, ASAC uses the provisioned CCA_ID of the terminating node to look up the ASAC budget. After ASAC locates the budget, ASAC checks whether there is enough bandwidth for the call. If sufficient bandwidth exists, ASAC decrements the appropriate call counts and allows the call to continue. If there is not enough budget and a lower-priority call exists, ASAC preempts the lower-priority call, and then decrements and increments the appropriate call counts to allow the new call to complete. If no lower-priority call exists to preempt, ASAC rejects the new call. Session Timer Support With Session Timer Support, the AS 5300 Session Manager supports a keep-alive mechanism for SIP sessions. All SIP sessions periodically refresh using UPDATE requests (or re-invites for the October 2017 Avaya Aura Application Server 5300 Overview 155

156 AS 5300 Session Manager fundamentals clients that do not support UPDATE). The system sends these requests during an active call leg to allow endpoints or proxies to determine the status of a SIP session. As part of the Session Timer support, the AS 5300 Session Manager acts as a proxy for the following requests: outbound requests from SIP end instruments that support keep-alive call requests from another Assured Service Session Initiation Protocol (AS SIP) signaling appliance where the destination is a served SIP end instrument that supports keep-alive As a proxy, the AS 5300 Session Manager stores information for the request and response messages received. The AS 5300 Session Manager examines the headers in received request and response messages. If required, the AS 5300 Session Manager inserts or modifies certain values before forwarding the SIP message. The AS 5300 Session Manager can handle the 422 response type and the following headers: Session-Expires in INVITE/UPDATE requests Min-SE in INVITE/UPDATE requests timer option in each request (except ACK) Require and Proxy-Require with the timer option in requests and 2xx responses A successful session refresh creates a Long Call accounting record. The audittype field indicates if the record is generated because of a Long Call audit of a Session Timer keep-alive mechanism. When the session interval on the AS 5300 Session Manager expires and the client has not refreshed or terminated the session, the AS 5300 Session Manager terminates the session. Session-Expires header The SIP Session-Expires header delivers the session interval and provides information about the entity that performs the refreshes. The period between refreshes is the session interval. The client sends the Session_Expires header during refresh; only the client can configure this value. However, if the AS 5300 Session Manager must insert the Session-Expires header into a 200ok response, the AS 5300 Session Manager uses the Min-SE value configured in the AS 5300 Element Manager Console, and specifies one of the following refresh values: A value of uac indicates that the originating endpoint performs the refresh. A value of uas indicates that the terminating endpoint performs the refresh. A successful refresh generates a billing record. For more information, see Avaya Aura Application Server 5300 Accounting Records Reference, NN Min-SE header The Min-SE header indicates the minimum value for the session expiration in units of delta-seconds. The presence of the Min-SE header in an INVITE, UPDATE request or a 422 response informs the terminating endpoint (and any proxies) of the minimum session timer duration value that the originating endpoint accepts. When present in a 422 response, the Min-SE header indicates the minimum session value the terminating endpoint accepts. When present in a request or response, October 2017 Avaya Aura Application Server 5300 Overview 156

157 Services and features the value must be 90 seconds or more. If the Min-SE header is not present, the default value is 90 seconds. An administrator uses the AS 5300 Element Manager Console to configure the minimum session interval. The minimum value for this parameter is 90 seconds and the recommended value is 1800 seconds (30 minutes). This header can be received in INVITE, UPDATE request messages and 2xx responses to an INVITE or UPDATE. For more information about how to configure this parameter, see Avaya Aura Application Server 5300 Configuration, NN Timer option headers The Session Timer supports the following headers: Supported header: includes the timer option tag in a Supported header, in a request or response, indicating that the user agent supports the SIP session timer and can perform refreshes. Require header: includes the timer option tag in a request Require header, indicating that the opposite endpoint (terminating endpoint) must understand the session timer extension to process the request. Typically, the timer option tag is not included in the request Require header (recommended behavior). Inclusion of the Require header in a response indicates that the opposite endpoint (originating endpoint) must look for the Session-Expires header field in the response and process it accordingly. Proxy-Require header: includes the timer option tag in a request Proxy-Require header, indicating that proxies must support the SIP session timer to correctly process the request. Session Interval Too Small message When the AS 5300 Session Manager receives a request that contains a Session-expired header with a duration less than the minimum timer for the server, the system generates a 422 (Session Timer Too Small) response. The terminating endpoint or proxy generates the 422 response, which includes a Min-SE header that indicates the minimum session value the endpoint accepts. The originating endpoint can then retry the call with a larger session timer value. Offer/Answer Support Session Initiation Protocol (SIP) uses the offer/answer model to establish and update multimedia sessions by using the Session Description Protocol (SDP). In the offer/answer model, one User Agent (UA) sends a session description (the offer), which contains a proposed description of the session. The offer indicates the desired communication means (audio, video, or games), the parameters of those means (such as codec types), and addresses for receiving media from the other UA. The other UA responds with another session description (the answer), which indicates the accepted communication means, the parameters that apply to those means, and the addresses for receiving media from the first UA. October 2017 Avaya Aura Application Server 5300 Overview 157

158 AS 5300 Session Manager fundamentals To facilitate the update of a session, a SIP dialog associates an offer/ answer exchange with the session. Only the offer/answer exchange in the SIP dialog can update the session that the dialog manages. If a SIP INVITE results in multiple dialogs, each is a separate offer/answer exchange. The offer and answer model is independent of the higher-layer application protocols which use it. SIP is one of the applications using the offer/answer model. RFC 3264 defines the offer/answer model, but does not specify which SIP messages should convey an offer or an answer. The offer and answer module supports offer and answer exchanges for the six patterns shown in the following table. This model follows the offer/answer model defined in RFC 3264, with particular attention to offer/answer exchanges in early dialogs that use PRACK and UPDATE. Table 24: Offer/answer support patterns Offer Answer RFC Ini Est Early INVITE Req 2xx INVITE Resp RFC 3261 Y Y N 2xx INVITE Resp ACK Req RFC 3261 Y Y N INVITE Req 1xx-rel INVITE Resp RFC 3262 Y Y N 1xx-rel INVITE Resp PRACK Req RFC 3262 Y Y N PRACK Req 200 PRACK Resp RFC 3262 N Y Y UPDATE Req 2xx UPDATE Resp RFC 3311 N Y Y Notes: 1. In the Answer column, 1xx-rel corresponds to the reliable provisional response, which contains the 100rel option as defined in RFC The Ini column indicates the ability to exchange the offer/answer to initiate the session. Y indicates that the pattern can be used in the initial offer/answer exchange, while N indicates that the pattern cannot be used. Only the initial INVITE transaction can exchange the offer/answer to establish a multimedia session. 3. The Est column indicates whether the pattern has the ability to update an established session. 4. The Early column indicates which patterns can modify an established session in an early dialog. For more information, see Avaya Aura Application Server 5300 Planning and Engineering, NN AS 5300 Session Manager Call Feature support The AS 5300 Session Manager generates and sends notifications of available calls to the Call Pickup group. Call Pickup data is stored and dynamically maintained, along with the ability to monitor state changes. October 2017 Avaya Aura Application Server 5300 Overview 158

159 Reliability and fault tolerance Reliability and fault tolerance To achieve reliability and fault tolerance, deploy the AS 5300 Session Manager servers in a 1+1 mode. The AS 5300 Session Manager is fully synchronized with the Provisioning Manager. To achieve synchronization, the AS 5300 Session Manager run-time cache tables must synchronize with the data maintained by the Provisioning Manager. The Provisioning Manager communicates with the active and warm standby AS 5300 Session Manager The AS 5300 Session Manager loads and maintains the subscriber run-time cache tables while in standby mode. The AS 5300 Session Manager does not load subscribers from the database during call processing. All subscribers are loaded into the Subscriber run-time cache table before any session activity. Interfaces The AS 5300 Session Manager uses various protocols to communicate with SIP clients, AS 5300 Element Manager, Database Manager, and the PSTN Gateways. The AS 5300 Session Manager interacts with numerous other components as shown in the following figure. October 2017 Avaya Aura Application Server 5300 Overview 159

160 AS 5300 Session Manager fundamentals Figure 19: AS 5300 Session Managers interfaces The following table gives details about how the AS 5300 Session Manager uses these protocols. Table 25: AS 5300 Session Manager protocols Using this protocol Data Transport Protocol (DTP) Session Initiation Protocol (SIP) Structured Query Language over Java Database Connectivity (SQL over JDBC) The AS 5300 Session Manager can send raw accounting information to the Accounting Manager for format and storage. originate and terminate media sessions (including voice, data, and video). connect to the database. The AS 5300 Session Manager writes registration information to the database as subscribers register within the network. In addition, it accesses the database during the course of a session to obtain subscriber and telephony routing information. Table continues October 2017 Avaya Aura Application Server 5300 Overview 160

161 Accounting Using this protocol Transmission Control Protocol (TCP) Internet Protocol Secure (IPsec) The AS 5300 Session Manager can communicate configuration and performance data, logs, and alarms with the AS 5300 Element Manager. provides extra security for all server communications. IPsec is optional. For more information about protocols, see Interfaces and communication protocols on page 84. Accounting The accounting management system for the Application Server 5300 provides the framework for collecting, formatting, and transmitting accounting data from the Application Server 5300 system to the service provider's back-end billing system. The accounting system is made of two logically separate entities: Record Transfer Agent (RTA): part of the AS 5300 Session Manager Accounting Manager (AM) The primary function of the RTA is to collect raw accounting data from active sessions on the AS 5300 Session Manager and transport it to the AM. The RTA runs in the AS 5300 Session Manager. Because many AS 5300 Session Managers can run in a site, there are many RTAs connecting to the AM. For more information about accounting, see Accounting Manager fundamentals on page 163. Security All signaling traffic goes through the AS 5300 Session Manager, which is the only node to which clients terminate SIP signaling. The AS 5300 Session Manager provides client authentication. To provide security, the system: improves password strength through password rules minimizes unnecessary processes enables debug logs restricts access to telnet and file transfer protocol (FTP) provides the option to use IPsec, TLS, and SRTP to secure communication The following communications protocols use FIPS cryptographic modules: SIP/TLS October 2017 Avaya Aura Application Server 5300 Overview 161

162 AS 5300 Session Manager fundamentals IPSEC IKE HTTPS PKI (for key encryption) SSH SFTP Application Server 5300 supports United States Department of Defence (DoD) Public Key Infrastructure (PKI), which includes the following security measures: TLS mutual authentication Support for Online Certificate Status Protocol (OCSP) Automatic Certificate Revocation List (CRL) retrieval Certificate revocation check DoD PKI X.509 certificate extensions. Important: Application Server 5300 systems that do not use TLS and SRTP use UDP, TCP, and RTP. AudioCodes Mediant 3000 does not support best effort RTP/SRTP (mixed-mode security). The configuration for all endpoints must be either secure or nonsecure for media. October 2017 Avaya Aura Application Server 5300 Overview 162

163 Chapter 24: Accounting Manager fundamentals This chapter describes the Application Server 5300 Accounting Manager. Navigation Tools and utilities on page 163 Accounting files and directories on page 163 Tools and utilities The AS 5300 Element Manager Console is the interface for the AS 5300 Element Manager. Use the AS 5300 Element Manager Console to configure the Accounting Manager. For more information about the AS 5300 Element Manager Console, see Avaya Aura Application Server 5300 Configuration, NN Accounting files and directories The Accounting Manager (AM) file and directory naming conventions are: Record Transfer Agent spool directory: The Record Transfer Agent (RTA) spool directory is /var/mcp/spool/acct/. The RTA writes recovery files to the spool directory of the AS 5300 Session Manager. These files contain raw accounting information and this information must not be used for deleting or modifying information. Record Transfer Agent spool file naming convention: The Record Transfer Agent uses the following file naming convention for recovery files that it writes to the AS 5300 Session Manager server spool directory: where <date> is the date the file was created in <year><month><day> format <time> is the time the file was created in <hours><minutes><seconds><milliseconds> format <extension> indicates the status of the spool file and can be one of the following extensions: -.active: represents an open spool file that is currently being written by the record transfer agent October 2017 Avaya Aura Application Server 5300 Overview 163

164 Accounting Manager fundamentals -.closed: represents a closed spool file that is written, but is not sent to the Accounting Manager -.reading: represents a spool file that is currently being transferred to the AM through the recovery stream -.err: represents files that cannot be read completely by the spool subsystem The system reads all records that are intact; however, due to corruption, the system is unable to process the entire contents of the file. AM output file directory: The directory that contains the accounting information is: /var/mcp/oss/acct/<release_id>/<am_name>/<session_manager_instance_name>/ <format_path_name> AM file naming convention: The Accounting Manager uses the following file naming convention for IPDR-formatted files: <Session_manager_instance_name>_Standard_<format_name>_<format_name><date>@<ti me>.<extension> where <date> is the date the file was created in <year><month><day> format <time> is the time the file was created in <hours><minutes><seconds><milliseconds> format <extension> is in one of the following strings: -.active: represents an open accounting file that is currently being written by the AM -.closed: represents a closed accounting file that is available for retrieval by the operation support system (OSS) -.error: represents an accounting file that is not closed correctly -.zip: represents a file that is compressed, if this option is chosen during configuration -.transferred: represents a file transferred through FTP push (for example, the file is successfully sent through FTP to the customer OSS) Important: Some of the preceding extensions listed can be used in conjunction with each other. For example, a file that is closed, compressed, and then transferred using FTP push uses the following extension:.closed.zip.transferred. For information about the contents of the accounting records, see Avaya Aura Application Server 5300 Accounting Records Reference, NN October 2017 Avaya Aura Application Server 5300 Overview 164

165 Chapter 25: Database Manager fundamentals The Application Server 5300 Database Manager controls the database containing the system and subscriber configuration. Navigation Description on page 165 Architecture on page 165 Database terminology on page 166 Description The database functionality includes the following software components: Oracle database software: third-party software that implements basic database functionality. Database Monitor component: gathers operational status information from the database and sends it to the Management Module. This information displays on the AS 5300 Element Manager Console as logs, alarms, and operational measurements (OM). Database Manager component: contains schema information for the Application Server 5300 system and subscriber data. The schema information defines the required database tables for the Application Server 5300 system to store configuration and subscriber data to the database. Architecture In the Application Server 5300 database architecture, one server runs as the primary database and that data replicates to a secondary database that is on the other server. Configure the database in a master-master replication configuration, where either database can forward (replicate) changes to the other database. For a graphical representation, see Figure 20: Redundant database architecture on page 166. October 2017 Avaya Aura Application Server 5300 Overview 165

166 Database Manager fundamentals Figure 20: Redundant database architecture Network elements normally send and receive data directly to and from the primary database. However, if a network element identifies a problem with the connection to the primary database, a failover state arises. At this point, network elements access the secondary database to query data. To reduce the number of conflicts that can occur while both databases are being written to, the secondary database limits the writes permitted. Only registrations, voice mail messages waiting, and network element instance state changes can be written to the secondary database. The failover state continues until the network element recognizes that the connection to the primary database reestablishes. Any changes made to the secondary database automatically push to the primary database. Database terminology The following sections explain basic database terminology. Replication on page 167 Synchronization on page 167 Database states on page 167 Database related jobs on page 168 Database backup and recovery on page 169 Alert logs and trace files on page 169 Tablespaces on page 169 October 2017 Avaya Aura Application Server 5300 Overview 166

167 Database terminology Replication Replication is the automatic process of duplicating data between the primary database and the secondary database as changes are received from the network elements. As data is added or updated by the network elements, data transactions are queued for transfer to the secondary database through the replication software. All database information is divided into groupings, called objects. Each database includes some objects that are replicated between the databases and some objects that are not replicated. Replicated objects consist only of tables. Non-replicated objects include stored procedures, functions, and tables. Important: Deployment of the database creates or updates both replicated objects and non-replicated objects on both databases. Software updates can modify table structures. Synchronization Replicated databases must always be in synchronization because of the preceding data transfer process. In the unlikely event that changes made to one database do not successfully propagate to the other database, a data transaction error (conflict) is encountered. In this case, the two databases are out of synchronization and must be synchronized manually. Database states The databases have the states of operation identified in Table 26: Database state definitions on page 167. The primary database ordinarily operates in the normal state, while a secondary database operates in a read-only state at all times. Table 26: Database state definitions States Normal (Primary database) Read-only (Secondary database) Description Fully writable for the network elements. Inserts, updates, or deletions are permitted to the primary database. The primary database continuously transfers new data to the secondary database. Read-only for the network elements. In the unlikely event of failure of the primary database, the network elements start using the secondary database. Table continues October 2017 Avaya Aura Application Server 5300 Overview 167

168 Database Manager fundamentals States Quiesced (maintenance mode) Description The system allows the following three exceptions to the read-only status of the secondary database: registrations to enable calls to proceed notification of incoming voice mail messages changes to the administrative state of the network elements Writes are not permitted to either database. After the database is quiesced, network elements can only query the database and cannot insert, update, or delete information. Within a redundant architecture, the primary and secondary databases automatically enter this state whenever changes are being made to the replication environment, including modifying replication objects and synchronizing the two databases. Database related jobs Jobs are scripts written by the Application Server 5300 design team that execute specific maintenance tasks at scheduled times. During installation and commissioning, the following types of jobs are created: Daily job: Update Sequence Numbers Job: Used to update the "current value" of the Sequence Numbers on the secondary database. The default schedule for this job is daily at 1:25 am. Daily job: Clear Excess Network Call Logs Job: Used to delete nonessential network call logs from the database. The default schedule is daily at 3:15 a.m. Daily job: E911 Cleanup Job: Used to delete old E911-related information (for example, locations, Emergency Response Locations) from the database. The default schedule is daily at 3:45 a.m. Important: Avaya recommends that you back up the database daily. Administrators configure the backups after installation. For more information, see Avaya Aura Application Server 5300 Administration, NN Weekly job: Analyze Large Tables Job: Used to analyze the large tables within the database to optimize access to the data required. The default schedule is every Sunday at 2:00 a.m. Monthly job: Analyze Small Tables Job: Used to analyze the small tables within the database to optimize access to the data required. The default schedule is the fourth Sunday at 2:00 a.m. October 2017 Avaya Aura Application Server 5300 Overview 168

169 Database terminology Database backup and recovery The database functionality supports the ability to back up the database by using the Application Server 5300 system scripts. Important: Avaya recommends that you back up the database daily. Recovery of an database restores the database to the state of the database (or secondary database) after it was backed up. All changes made to the database since the last backup are lost. Two types of backups are necessary: Backup of the data in the database Backup of the server, to recover the server after a catastrophic failure or some other circumstance that requires reinstalling the operating system. Important: Avaya recommends that you back up the Application Server 5300 servers in certain situations, based on the software resident on the server. These include situations after the database software and the Application Server 5300 software are updated. Alert logs and trace files The system stores other database status information in an alert log file for the corresponding database. This file holds a chronological log of messages and errors, such as all internal errors, block corruption errors, and deadlock errors. After a process detects an error, it creates an alert log file and a corresponding trace file. The alert log file stores database status information for a specific database. This file holds a chronological log of messages and errors, including all internal, block corruption, and deadlock errors. The trace file includes detailed information about the error. Tablespaces Tablespaces are entities that hold table information (network element, subscriber, and database data in the form of tables). Tablespaces are allocated a certain amount of disk space initially and can expand. Important: Avaya recommends that you monitor disk space regularly from the AS 5300 Element Manager Console to ensure that the servers do not run out of disk space. October 2017 Avaya Aura Application Server 5300 Overview 169

170 Database Manager fundamentals After a Critical disk threshold alarm is raised at the AS 5300 Element Manager Console for the primary database server (or secondary database server, in a redundant architecture) against the /var/mcp file partition, Avaya recommends that you examine the tablespace size in the /var/mcp/db/data/mcpdb directory. October 2017 Avaya Aura Application Server 5300 Overview 170

171 Chapter 26: Provisioning Manager and Personal Agent Manager fundamentals This chapter describes the Application Server 5300 Provisioning Manager and Personal Agent Manager. Navigation Description on page 171 Security on page 172 Description The Provisioning Manager is the central provisioning component of the Application Server 5300 infrastructure. The Provisioning Manager provides a secure interface between the provisioning clients and the Database Manager where the provisioning data resides. The Provisioning Manager hosts the Web server that responds to HTTP or HTTPS requests from browser-based access clients and Open Provisioning Interface (OPI)-based clients. Use the following tools to provision the system: Provisioning Client: For more information about the Provisioning Client, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN Open Provisioning Interface: The Open Provisioning Interface (OPI) permits development of third-party applications to provision the Application Server 5300 system. For more information, see Avaya Aura Application Server 5300 Application Programming Interfaces Reference, NN Subscriber Open Provisioning Interface: The Subscriber Open Provisioning Interface (SOPI) permits development of third-party applications to provision the Application Server 5300 system. For more information about Subscriber Open Provisioning Interface (SOPI), see Avaya Aura Application Server 5300 Application Programming Interfaces Reference, NN The Personal Agent Manager supports the Personal Agent, a web-based software component that allows a user to view and modify the following services or settings: IP Deskphone settings October 2017 Avaya Aura Application Server 5300 Overview 171

172 Provisioning Manager and Personal Agent Manager fundamentals IP Deskphone routes, call rejects, and subjects User name and address User picture User address book User friends list User banned parties list Web server The Web server software handles Web-related interactions of the Provisioning Manager. The Web server is on the same server as the Provisioning Manager. It processes HTTP requests from OPI clients, Avaya Aura AS 5300 UC Client, Avaya Aura AS 5300 Office Client, Personal Agent, and Provisioning Client to support self-provisioning and network-based services. Deploy the Web server software during Provisioning Manager deployment. Security Administrators use the web-based Provisioning Client to access the Provisioning Manager. Passwords (with defined complexity rules) and privileges control administrator access. For more information, see Avaya Aura Application Server 5300 Security, NN October 2017 Avaya Aura Application Server 5300 Overview 172

173 Chapter 27: End-user clients This chapter describes the Application Server 5300 end-user clients. Navigation Avaya Aura AS 5300 Personal Agent on page 173 Avaya Aura AS 5300 UC Client on page 174 Avaya Aura AS 5300 Office Client on page 174 Avaya 1100 Series IP Deskphones on page 175 General Dynamics viper phone on page 177 Security on page 177 Avaya Aura AS 5300 Personal Agent The Personal Agent manages user services and communication preferences. With the Personal Agent, you can define incoming call treatment, including which devices (office telephone, home telephone, mobile phone) to ring and the ringing sequence view and customize personal information manage, track, and maintain key contact information establish a call between you and another person launch the Application Server 5300 Web Client. For more information, see Avaya Aura AS 5300 UC Client on page 174. share files with other Personal Agent users or Avaya Aura Application Server 5300 Web Client users. For more information about the Personal Agent, see Avaya Aura Application Server 5300 Personal Agent User Guide, NN October 2017 Avaya Aura Application Server 5300 Overview 173

174 End-user clients Avaya Aura AS 5300 UC Client The Avaya Aura AS 5300 UC Client provides advanced Internet Protocol (IP) telephone features including: IP calls advanced call logs to track incoming, outgoing, and missed calls Automatic Software Update (ASU) personal and global address books presence control of a 1120E IP Deskphone or 1140E IP Deskphone (known as the Client Set configuration) call features such as call hold, call retrieve, call transfer, and do not disturb video calls conference calls (requires Avaya Media Server) You can configure the Avaya Aura AS 5300 UC Client as a Voiceless UC Client. A lighter version, known as the Application Server 5300 Web Client, runs from the Personal Agent. The Application Server 5300 Web Client cannot control an IP Deskphone, nor does it have all the functions available in the Avaya Aura AS 5300 UC Client. For more information about Avaya Aura AS 5300 UC Client and Application Server 5300 Web Client, see Avaya Aura Application Server 5300 UC Client User Guide, NN Avaya Aura AS 5300 Office Client The Avaya Aura AS 5300 Office Client is a plug-in for Microsoft Office. It provides the features of the Avaya Aura AS 5300 UC Client within Microsoft Office. This transforms the application into a complete communications center that provides the following advanced IP telephony features: SIP calls: to make calls from inside Outlook advanced call logging: to keep track of incoming, outgoing, and missed calls in Outlook folders personal address book: to use Outlook contacts as your Avaya Aura AS 5300 Office Clientt directory presence: to see who is online and let others know that you are online control of Avaya 1100 Series IP Deskphones file transfer: to send files to and receive files from contacts with a SIP address sharing tools: to push web pages, whiteboards, and clipboards call handling: to decline, redirect, or ignore incoming calls October 2017 Avaya Aura Application Server 5300 Overview 174

175 Avaya 1100 Series IP Deskphones instant messaging: to send and receive text messages conference calls (requires Avaya MS) ability to provide limited call control for wireless devices For more information, see Avaya Aura Application Server 5300 Office Client User Guide (NN ). Avaya 1100 Series IP Deskphones The 1100 Series IP Deskphones provide basic telephone functions as well as functions that use the Internet connection. The telephone provides buttons for quick access to functions and a multifield Liquid Crystal Display (LCD) to display information and functions that use soft keys. Application Server 5300 supports the following 1100 Series IP Deskphones: 1120E IP Deskphone with Session Initiation Protocol (SIP) firmware 1140E IP Deskphone with SIP firmware The 1100 Series IP Deskphones must run SIP 3.0 or later firmware. The 1100 Series IP Deskphones with SIP firmware operate in SIP and communicate with the AS 5300 Session Manager to provide telephony. SIP-enabled telephones receive future firmware and configuration updates through a Hypertext Transport Protocol Secure (HTTPS) configuration. For more information about configuring the IP Deskphones for Application Server 5300, see Avaya Aura Application Server 5300 Configuration, NN and Avaya Aura Application Server 5300 Using the Provisioning Client, NN For more information about the IP Deskphones, see the IP Deskphone documentation suite. IP Deskphones and Hotline service Hotline service allows a user to initiate a call as soon as the designated Hotline 1120E IP Deskphone or 1140E IP Deskphone goes off hook. Hotline service has two modes: Service Protection enabled and Service Protection disabled. You configure the Service Protection at the user level using a Hotline System profile from the AS 5300 Element Manager Console. The Hotline Service profile contains the following information: Hotline indicator - Voice - Data October 2017 Avaya Aura Application Server 5300 Overview 175

176 End-user clients Hotline type - Origination Only Hotline User - Termination Only Hotline User - Both Origination and Termination Hotline User When a hotline user places a call, the system ensures that the caller has the correct type of hotline service. The type hotline indicator must match and the hotline types must be compatible. For example, termination user cannot originate a call, and a voice user cannot call a data user. Protected hotline calls can only go to protected hotline users (that is, hotline to hotline only). Services like Hold, Redirect, Transfer, and Conference cannot be invoked on hotline calls. The following table shows the permitted calls when User A calls user B. Table 27: Valid and invalid calls between hotline users User B Voice User B Data Originatio n only Termination only Origination and Termination Origination only Terminatio n only Origination and Termination User A Voice Origination only Termination only not permitted not permitted permitted permitted not permitted not permitted not permitted not permitted not permitted not permitted not permitted not permitted Origination and Termination not permitted permitted permitted not permitted not permitted not permitted User A Data Origination only Termination only not permitted not permitted not permitted not permitted not permitted not permitted not permitted not permitted permitted not permitted permitted not permitted Origination and Termination not permitted not permitted not permitted not permitted permitted permitted Origination only the hotline user can only originate calls but cannot receive any incoming calls Termination only the hotline user can only receive calls but cannot make any outgoing calls Origination and Termination the hotline user can make calls to other hotlines and can also receive calls from other hotlines Each hotline has an assigned Designated Call Party (DCP). So, when a user picks up the hotline telephone receiver, the DCP automatically receives the call. The call goes through at the maximum configured precedence level. October 2017 Avaya Aura Application Server 5300 Overview 176

177 General Dynamics viper phone General Dynamics viper phone The Sectéra viper is a secure client for VoIP and Analog Networks, and is certified by NSA and Joint Interoperability Test Command (JTIC ) with Integrated security, up to and including Top Secret / SCI, including Sensitive But Unclassified (SBU). For more information about features supported by the viper phone, see the documentation provided in the CD that is shipped with the product. Also, see Security Subscriber user names (or user IDs) and passwords provide secure access to the Application Server 5300 clients (soft clients and deskphones). Administrators create subscriber user names and passwords, and configure the system to control password policies. Administrators can force subscribers to change the password on first logon, and can configure password complexity rules, including minimum password length, password character content, and password aging. Administrators can configure subscriber lockout so that after a configurable number of failed log on attempts, the system blocks the subscriber from accessing the system for a period. Administrators restrict or allow the use to features and services at the system, domain, and subscriber levels. For more information about subscriber accounts, domains, passwords, and security, see Avaya Aura Application Server 5300 Using the Provisioning Client, NN and Avaya Aura Application Server 5300 Security, NN October 2017 Avaya Aura Application Server 5300 Overview 177

178 Chapter 28: Virtualization support AS 5300 small Simplex and Duplex deployment models can be deployed on VMWare hypervisor- ESXi 5.5 on HP ProLiant DL360p G8 or HP ProLiant DL360 G9 servers to support 5,000 subscribers. In this model, all core software such as AS 5300 Session Manager, AS 5300 Element Manager, Accounting Manager, Database Manager, and Provisioning Manager runs on one virtual machine. All Avaya Aura Media Server applications such as MeetMe, Ad-Hoc, Tones, Announcement, Music on Hold, and Voice Mail run on another virtual machine. The small Simplex model can run these two virtual machines on the same physical server. The small Duplex model can run active and standby virtual machines instances across the two physical servers. SIP Core AMS SM/FPM, DB, AM, PROV/PA, SESM SM/FPM, DB, AM, PROV/PA, SESM Tone, Annoc, MoH, UCOM, Ad hoc, MeetMe Tone, Annoc, MoH, UCOM, Ad hoc, MeetMe 4 servers to 2 servers reduction with VMs Active SM/FPM, DB, AM, Prov/PA, SESM VM-1 Standby Tone, Ann, MoH, UCom, Ad-hoc, MeetMe VM-2 vsphere Hypervisor (ESXi 5.5) CS 3 Server 1 ( e.g. HP Proliant DL360 G9) SM/FPM, DB, AM, Prov/PA, SESM Standby VM-1 Active Tone, Ann, MoH, UCom, Ad-hoc, MeetMe VM-2 vsphere Hypervisor (ESXi 5.5) CS 3 Server 2 ( e.g. HP Proliant DL360 G9) Figure 21: DoD LSC Small, Duplex (Redundancy) October 2017 Avaya Aura Application Server 5300 Overview 178

179 Chapter 29: Avaya Aura Application Server 5300 document suite The Application Server 5300 documents are available at For more information about the documentation suite, including a complete list of the available documents, see Avaya Aura Application Server 5300 Documentation Roadmap, NN October 2017 Avaya Aura Application Server 5300 Overview 179

180 Appendix A: Supported features This chapter describes the features are supported in Application Server 5300 Release 3.0. Supported features Table 28: Service support feature matrix Service/Capability Department of Defence Federal Civilian with MLPP Federal Civilian without MLPP and Enterprise Accounting Supported Supported Supported Address Book - Global Supported Supported Supported Address Book - Personal/Local Supported Supported Supported Alias Routing Supported Supported Supported Assured Services Admission Control (ASAC) Supported Unsupported Unsupported Audio Conferencing - Ad hoc conferencing Supported Supported Supported Audio Conferencing - Meet me conferencing Supported Supported Supported Assisted User Unsupported Unsupported Supported Call Branding / Announcements Unsupported Unsupported Supported Call Decline Supported Supported Supported Call Forward to Announcement for unregistered user Unsupported Unsupported Unsupported Call Grabber Unsupported Unsupported Supported Call Hold Supported Supported Supported Call Ignore Supported Supported Supported Call Logs Client Supported Supported Supported Call Logs Personal Agent (PA) (network based) Supported Supported Supported Call Mute Supported Supported Supported Call Park Unsupported Unsupported Supported Call Redirect Supported Supported Supported Table continues October 2017 Avaya Aura Application Server 5300 Overview 180

181 Supported features Service/Capability Department of Defence Federal Civilian with MLPP Federal Civilian without MLPP and Enterprise Call Reject Supported Supported Supported Call Reject Reasons Supported Supported Supported Call Return Supported Supported Supported Call Subjects Supported Supported Supported Call Transfer (Consultative) Supported Supported Supported Call Transfer (Direct) Supported Supported Supported Call Type Based Screening Supported Supported Supported Call Waiting Supported Supported Supported Call Waiting Disable Supported Supported Supported Calling / Called / Connected Name / Number Display Supported Supported Supported Calling / Called picture display Supported Supported Supported Class Of Service Call Routing Supported Supported Supported CLI Notification Unsupported Unsupported Unsupported Click to Call - PA invocation Unsupported Unsupported Supported Click to Dial - Client invocation Supported Supported Supported Click to Dial - PA invocation Unsupported Unsupported Supported Clipboard Push Unsupported Unsupported Supported Colorful Ringback Tones Unsupported Unsupported Unsupported Converged Desktop (CD2) with CS 1000 Unsupported Unsupported Unsupported Converged Desktop (CD2) with CS 2000 Unsupported Unsupported Unsupported Custom Country Tones Unsupported Unsupported Unsupported Deny All Calls Unsupported Unsupported Supported Destination Code Controls Supported Supported Supported Do Not Disturb Supported Supported Supported Dual CLI Unsupported Unsupported Unsupported Enhanced 911 (E911) Supported Supported Supported Enterprise Dialing Plan Support Supported Supported Supported Equal Access Loop-around Unsupported Unsupported Unsupported File Exchange Unsupported Unsupported Supported Friends List Supported Supported Supported Group Call Pickup Unsupported Unsupported Supported Gateway Route List Support Supported Supported Supported Hot Line Supported Supported Supported Hunting Unsupported Unsupported Supported Table continues October 2017 Avaya Aura Application Server 5300 Overview 181

182 Supported features Service/Capability Department of Defence Federal Civilian with MLPP Federal Civilian without MLPP and Enterprise Instant Messaging Supported Supported Supported Instant Messaging Broadcast Supported Supported Supported Instant Messaging Chat (3+ person IM sessions) Unsupported Unsupported Supported IP Restrictions Unsupported Unsupported Unsupported Known Product Indicators (specialized OMs) Supported Supported Supported Legal/Lawful Intercept Unsupported Unsupported Unsupported Malicious Call Trace Supported Supported Supported Avaya Media Server (MS) Based Digit Collection Unsupported Unsupported Unsupported Media Portal Insertion Unsupported Unsupported Unsupported Message Waiting Indicator Supported Supported Supported Multilevel Precedence and Preemption (MLPP) Supported Supported Unsupported Mobile Converged Desktop (CD3) Unsupported Unsupported Unsupported Multiple Login Restriction Supported Supported Supported Music on Hold Supported Supported Supported Network Call Waiting Disable (CallReject) Supported Supported Supported Network Ignore Unsupported Unsupported Supported Network Message Waiting Indicator (MWI) Supported Supported Supported PA Route - Advanced routes Supported Supported Supported PA Route - Anonymous Call Handling Supported Supported Supported PA Route - Call Forward Busy Supported Supported Supported PA Route - Call Forward Immediate Supported Supported Supported PA Route - Call Forward No Answer Supported Supported Supported PA Route - Call Forward Unregistered Unsupported Unsupported Unsupported PA Route - Call Rejection Supported Supported Supported PA Route - Push Supported Supported Supported PA Route - Receive IM Supported Supported Supported PA Route - Request Supported Supported Supported PA Route - Respond with IM Supported Supported Supported PA Route - Send to Voic Supported Supported Supported PA Route - Sequential Ring Supported Supported Supported PA Route - Simultaneous Ring Supported Supported Supported PA Route - Time of Day Routing Supported Supported Supported ParleyX Unsupported Unsupported Unsupported Presence Authorization/Watchers Supported Supported Supported Table continues October 2017 Avaya Aura Application Server 5300 Overview 182

183 Supported features Service/Capability Department of Defence Federal Civilian with MLPP Federal Civilian without MLPP and Enterprise Presence - automatic & manual Supported Supported Supported Presence On the Phone indication Supported Supported Supported Privacy Supported Supported Supported Private/Public Name Display Supported Supported Supported Private/Public Number Display Supported Supported Supported Public Service Identifiers/Aliases Unsupported Unsupported Unsupported Quality of Service (QoS) Supported Supported Supported Registrar/Registration Supported Supported Supported SBC Support Supported Supported Supported Secure Instant Messaging Supported Supported Supported Selective Call Reject Supported Supported Supported SIP Endpoint Profiles Supported Supported Supported SIP Lines Unsupported Unsupported Unsupported SIPPBX (not to be confused with general PBX interworking) Unsupported Unsupported Unsupported Starcode Ringback Service Unsupported Unsupported Unsupported Teen Service Unsupported Unsupported Unsupported Telefonica PBX Communicator Unsupported Unsupported Unsupported Tones (Busy, treatment) Supported Supported Supported Translations Supported Supported Supported UC Client Control of SIP Terminal Supported Supported Supported PC Client Control of UNISTIM Terminal (Raiderset) Unsupported Unsupported Supported Unified Communications / Voice Mail (no support) Supported Supported Supported Uniform Call Distribution Unsupported Unsupported Supported URL Dialing Unsupported Unsupported Supported VCAC (with DQOS+) Unsupported Unsupported Unsupported Vertical Service Codes (VSC) Supported Supported Supported Video Calling - Point to Point Supported Supported Supported Video Conferencing - Ad Hoc (using Avaya MS) Supported Supported Supported Video Conferencing - Meet Me (using Avaya MS) Supported Supported Supported Web Co-Browsing Unsupported Unsupported Supported Web Collaboration (Application Sharing, Publish Mode, ) Unsupported Unsupported Unsupported Whiteboard Unsupported Unsupported Supported October 2017 Avaya Aura Application Server 5300 Overview 183

184 Appendix B: IPv6 overview This section presents an overview of the Internet Protocol version 6 (IPv6) for those unfamiliar with the protocol. The section is based on the protocol specifications, and not on Application Server 5300 implementation. For detailed information about IPv6 support in Application Server 5300, contact Avaya. With the introduction of always-on broadband technology and large numbers of mobile devices, the Internet will need a very large address space to continue its growth. The Internet Protocol version 6 (IPv6) aims to eliminate the barriers to globally unique addressing and to complement the QoS and security features of Internet Protocol version 4 (IPv4) to deliver a secure mechanism to differentiate levels of service per user within the global Internet. IPv6 introduces a much larger 128-bit address space than the 32-bit addresses of IPv4. It is 64 billion times the size of the IPv4 address space. IPv6 introduces a complete replacement network layer for IP networks. The basics of IPv6 are described in the IETF standard Internet Protocol, Version 6 (IPv6) Specification (RFC2460). IPv4 versus IPv6 on page 184 ICMPv6 on page 186 IPv6 addressing overview on page 188 Upper layer protocols on page 198 IPv6 migration on page 200 IPv4 versus IPv6 The following figure compares the IPv4 and IPv6 headers. October 2017 Avaya Aura Application Server 5300 Overview 184

185 IPv4 versus IPv6 Figure 22: Comparison of IPv4 and IPv6 headers The basic header of an IPv6 packet is 40-byte, which is twice the size of an IPv4 packet header. IPv6 does not uses the checksum found in IPv4 headers because the commonly used Layer 2 technologies provides a checksum for detecting corruption during transmission on each separate link and IP transport protocols provide checksum for end-to-end payload corruption detection. The considerable extra processing load needed to calculate the checksum at the sender and subsequent nodes is not justified and could be considered an added risk for corruption. To ensure that a transport layer checksum is provided in all cases, the UDP checksum is mandatory for IPv6, while it is optional for IPv4. All IPv6 nodes and links are required to handle packets up to 1280 octets long. IPv6 routers are no longer expected to fragment packets if the Maximum Transmission Unit (MTU) of the next link is too small for the size of packet. A host uses Path MTU Discovery (PMTUD) to find out what is the minimum MTU for the set of links on which a packet will traverse in reaching a destination. Hosts may still have to fragment large packets for transmission and reassemble them on receipt. Routers drop any that exceed the available MTU and report the error back to the source with an Internet Control Message Protocol (ICMP) Packet Too Big error message. IPv4 packets allow a fixed maximum amount of space for optional fields. IPv4 packets carrying options are classed as special cases and diverted from the hardware supported fast path in larger routers. The processing of packets with options carries a large performance penalty; as a result, IPv4 options are little used. By contrast, IPv6 is designed with an extensible header system that is intended to be flexible and future proof. The extension headers, when needed, are inserted between the basic header and the data payload. Multiple extension headers can be daisy-chained onto the basic IPv6 header. Each extension header is identified by the Next Header field in the preceding header. RFC2460 recommends the order of extension headers should be chained in an IPv6 packet: IPv6 main header, Hop-by-Hop Options header (supporting support of Jumbo-grams or the Router Alert), Destination Options header (supporting applications, processing by the first destination), Routing header (supporting source routing), Fragment header (supporting source packet fragmentation), Authentication header (RFC2402), Encapsulating Security Payload header (RFC 2406), Destination Options header (processing only by the final destination), Upper-layer header (UDP, TCP). October 2017 Avaya Aura Application Server 5300 Overview 185

186 IPv6 overview The following table summarizes the differences between the two headers. Table 29: Comparison of IPv4 and IPv6 header fields IPv4 Twenty octet header Four octet (32 bit) addresses QoS Specification in Service Type octet Limited options Packet fragmentation in routers Fragmentation information in main header fields always present Header has checksum Protocol field identifies type of Packet Time To Live field Total Length: combined length of header plus payload IPv6 Forty octet header Sixteen octet (128 bit) addresses QoS Specification in Flow Label and Traffic Class octet Extensible header extension Packet fragmentation only at source Fragmentation information in extension header present only when needed No header checksum Next Header field in main header and each extension identifies next component Hop Limit Payload Length: basic header is fixed length, extension headers each include length ICMPv6 The Internet Control Message Protocol (ICMP) is an integral part of IPv6 protocol. The set of functions that ICMPv6 performs is essential for IPv6. ICMPv6 has been enhanced to include the Address Resolution Protocol (ARP), Reverse ARP, Internet Group Management Protocol (IGMP), Path MTU Discovery, and Neighbor Discovery for plug and play connection to the network. The ICMPv6 functions are summarized below: ICMP error messages return to the source if a packet could not be delivered (RFC 4443). See Table 30: IPv6 messages on page 187. Echo Request and Echo Response Messages for monitoring connectivity through used by the ping and traceroute utilities (RFC 4443). Neighbor Solicitation and Neighbor Advertisement Messages (RFC 2461) for: - Link layer address resolution (equivalent to IPv4 ARP): finding neighbors connected to the same link and determines their IP and link layer addresses - Neighbor Unreachability detection: ensures that neighbors remain reachable using the same IP and link layer address by applying Neighbor Unreachability Detection (NUD) and notifies neighbors changes of link layer addresses - Duplicate Address Detection (RFC 2462): checking the uniqueness of any addresses that an interface proposes to use through Duplicate Address Detection (DAD). DAD can be turned October 2017 Avaya Aura Application Server 5300 Overview 186

187 ICMPv6 off if the network administrator believes that the configuration method used is bound to generate unique addresses. Router Solicitation and Router Advertisement Messages [RFC 2461] for: - Finding routers and determining how to obtain IP addresses to join the subnets supported by the routers. - Providing prefixes and other configuration information (including the link MTU and suggested hop count default) from routers to hosts if stateless autoconfiguration of hosts is enabled. Note with IPv6, routers relies on senders to fragment packets and do not fragment packets anymore. - Supporting renumbering of networks by allowing the prefixes advertised by routers to be altered. RFC 4192 describes details of re-numbering process. - Providing support for some aspects of Mobile IPv6, especially dealing with the IPv6 Mobile Home Agent functionality provided in routers and needed to support a Mobile node homed on the link. Redirect Message [RFC 2461] informing a node: - a more appropriate router on the local link for the destination address - the destination is a neighbor one the same link and a remote node Multicast Listener Discovery [RFC 2710 MLDv1 and RFC 3810 MLDv2] based on IPv4 IGMPv2 [RFC 2236] and IGMPv3 [RFC 3376] for: - Discovering which Multicast groups have listeners on a link (Multicast Listener Query) - Registering for a Multicast group membership (Multicast Listener Report) - De-registering for a Multicast group membership (Multicast Listener Done) Table 30: IPv6 messages Type Meaning 1 Destination Unreachable 2 Packet Too Big 3 Time Exceeded 4 Parameter Problem The following table is a list of IPv6 information messages. Table 31: ICMP information messages Type Meaning 128 Echo Request (RFC 4443) 129 Echo Reply Table continues October 2017 Avaya Aura Application Server 5300 Overview 187

188 IPv6 overview Type Meaning 130 Multicast Listener Query (RFC 2710) 131 Multicast Listener Report 132 Multicast Listener Done 133 Router Solicitation (RFC 2461) 134 Router Advertisement 135 Neighbor Solicitation 136 Neighbor Advertisement 137 Redirect 138 Router Renumbering (RFC 2894) 139 Node Information Query 140 Node Information Response 141 Inverse Neighbor Discovery Solicitation (RFC 3122) 142 Inverse Neighbor Advertisement 143 Multicast Listener Report v2 (RFC 3810) 144 Home Agent Address Discovery Request (RFC 3775) 145 Home Agent Address Discovery Reply 146 Mobile Prefix Solicitation (RFC 3971) 147 Mobile Prefix Advertisement 148 Certification Path Solicitation (RFC 3971) 149 Certification Path Advertisement 151 Multicast Router Advertisement (RFC 4286) 152 Multicast Router Solicitation 153 Multicast Router Termination Private experimentation (RFC 4443) 255 Reserved IPv6 addressing overview IPv6 provides both Unicast and Multicast addressing as in IPv4. IPv6 also introduces a new variant of Unicast called Anycast, which is a Unicast address assigned to multiple interfaces (typically belonging to different nodes). A packet sent to an Anycast address is only delivered to the closet Anycast interface. This is different from the Multicast packet delivery where the Router will deliver the packet to all Multicast interfaces. Anycast addresses are used to provide redundancy and load balancing where multiple servers provide the same services. It is also more efficient and more scalable to access the nearest server depending on where the request is made from rather than accessing the centralized servers. At October 2017 Avaya Aura Application Server 5300 Overview 188

189 IPv6 addressing overview present, Anycast is only implemented on routers. The router is responsible for knowing the correct server corresponding to an Anycast address and forwarding the message accordingly. The IPv6 Addressing Architecture [RFC3879, RFC 4193, and RFC 4291] lists the various types and scopes for IPv6 addresses by using pre-assigned address prefix types (Table 32: IPv6 address types on page 189). Using well-known prefixes allow easy filtering at the scope boundaries. A large part of the address space is currently left unassigned. However, any address that does not fall into one of the assigned spaces should be assumed to be a global Unicast address. Table 32: IPv6 address types Type Unspecified ::/128 Loopback ::1/128 Multicast Link Local Unicast Unique Local Unicast Hex Notation FF00::/8 FE80::/10 FC00::/7 Global Unicast 2000::/3 IPv6 introduced the concept of address scopes which do not allow addresses with a particular scope be propagated and used outside that scope. The link-local addresses (FE80::/10), assigned through autoconfiguration, are used on a single link and should never be routed. The Unique Local IPv6 Unicast addresses (FC00::/7) are globally unique but should not be routed to the global Internet [RFC4193]. The Unique Local IPv6 addresses are self-generated (without needing any central coordination or assignment) using a pseudo-random algorithm with a extremely high probability of being unique. The global Unicast addresses (2000::/3) are unique Unicast addresses and routable in the global Internet [RFC 4291]. The aggregatable global Unicast addresses are usually constructed by adding a 64 bit prefix to a 64 bit IID (Interface Identifier). Often the IID will be a globally unique number that can be combined with any address prefix to make an address. The IID can be derived from the MAC address of the interface, manually configured or generated cryptographically [RFC3041]. At present, the address prefix would be delegated from a provider that would also provide routing of IPv6 traffic to and from nodes using this address prefix. This provider addressing (PA) is designed to support the strict aggregation policy of the Internet. Multicast on page 190 Address format on page 191 Address prefix and subnet on page 191 Stateless and stateful autoconfiguration on page 192 Address resolution and caching on page 195 IPv6 address management on page 196 Multiple IP addresses per interface on page 197 October 2017 Avaya Aura Application Server 5300 Overview 189

190 IPv6 overview IPv6 routing on page 197 Multicast The broadcast address available on each subnet in IPv4 has no analog in IPv6 because IPv6 does not use broadcast mechanisms at the IP layer at all. IP Multicast has a much more important role in IPv6 than it does in IPv4 because various link layer specific support protocols (for example, ARP, RARP) have been integrated into IPv6. Many of these functions rely on the ability to send messages to groups of interfaces on a link according to their roles (for example, to all nodes or to all routers) even before the sending interface knows what other nodes are attached to the link. As a result, IPv6 is heavily dependent on Multicast packet delivery at least at the level of one link. The Solicited-node Multicast address is a Multicast address that every node must join for every Unicast and Anycast address it is assigned. This address is formed by taking the lower-order 24 bits of an IP address and appending them to the well-known prefix FF02:0:0:0:0:1:FF00::/104. IPv4 broadcasts ARP messages to resolve an IP-MAC address mapping. IPv6 sends Neighbor Solicitation messages to the Solicited-node Multicast address to resolve the interface MAC address. As a result, only the nodes registered to this Multicast address will receive the messages. In order to optimize the delivery of Multicast, nodes have to inform routers about the Multicast groups to which they are listening (that is, the Multicast addresses for which they will accept packets). Routers then only need to propagate Multicast packets onto links where there is at least one listener. The information needed is maintained by exchanges using the Multicast Listener Discovery protocol (MLD v1 [RFC2710] or v2 [RFC3596]), which replaces the IGMP used for the same purpose in IPv4. Although Multicasting with the local link scope is needed for the correct operation of all IPv6 networks, but this operation does not require any dynamic Multicast routing protocols to be deployed. However, the networks that use Multicast services beyond the link scope will need to deploy one or more of the Multicast routing protocols such as Protocol Independent Multicast Dense Mode, Protocol Independent Multicast Sparse Mode, Distance Vector Multicast Routing Protocol, Source-Specific Multicast for IP, and Border Gateway Multicast Protocol. The Multicast routing protocols are still mostly under development; refer to IETF Web site for more details. The following table is a partial list of well-known IPv6 multicast addresses that are registered with the Internet Assigned Numbers Authority (IANA). Table 33: IPv6 well-known prefixes Address ff02::1 ff02::2 ff05::1 ff0x::fb Description All nodes on the local network segment All routers on the local network segment All nodes on the local network site Multicast DNS Table continues October 2017 Avaya Aura Application Server 5300 Overview 190

191 Address format Address ff0x::108 ff05::1:3 Description Network Information Service All DHCP servers on the local network site Address format There are three conventional forms for representing IPv6 addresses as text strings. The preferred form of a fully expanded IPv6 128 address is written as a group of up to four hexadecimal digits, with the fields separated by colons (RFC2373, RFC3513). For example, a fully expanded IPv6 address might look like the following: FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 When many of the fields of an address are all zeroes as shown below: 1080:0000:0000:0000:0008:0800:200C:417A The address can be shortened by removing leading zeroes from each field: 1080:0:0:0:8:800:200C:417A Care must be taken not to leave out trailing zeroes (for example 0800 :: 800). A further simplification can be achieved by leaving out a group of adjacent zeroes using a pair of colons :: 1080::8:800:200C:417A. Therefore, the address 12AB: 0000:0000:CD30:0000:0000:0000:0000 can be represented as either 12AB::CD30:0:0:0:0 or 12AB:0:0:CD30::. Note, the "::" can only appear once in an address. In mixed IPv4 and IPv6 environments, an IPv4 address can sometimes be embedded as the last 32 bits of an IPv6 address (0:0:0:0:0:0: ), using the :: syntax, the address can be written as (:: ). The IPv6 address prefixes are written in Class-less Interdomain Routing (CIDR) notation similar to the way IPv4 addresses prefixes. An IPv6 address prefix is represented by the IPv6-address/prefixlength notation, for example, 12AB::CD30:0:0:0:0/60. To use an IPv6 address in a URL, the address should be enclosed in "[" and "]" characters, as shown in the following examples: sip:u2@[2221:812:1::15] Address prefix and subnet In IPv4, the address is logically split into a network part and a host part. In IPv6, each interface has an Interface Identifier (IID) replacing the host part. The rest of an IPv6 address is the Subnet Identifier corresponding to the IPv4 network part. As in IPv4, a contiguous set of bits starting from October 2017 Avaya Aura Application Server 5300 Overview 191

192 IPv6 overview the left-hand end of the address is known as an (Address) Prefix. The count of significant bits in the Prefix is the Prefix Length. The same notation used in IPv4 CIDR (Classless Inter-Domain Routing) is used to specify prefixes (for example, 1080:0:0:2C0/58 indicates that the 58 (decimal) most significant bits make up the address prefix). A subnet in IPv6 is a set of interfaces that share a Subnet Identifier. An IPv6 node relies on information from the routers on the link to determine which Subnet Identifiers are on link. Stateless and stateful autoconfiguration IPv6 supports plug and play autoconfiguration process using both stateless (using only routers) and stateful (using both router and DHCP servers) mechanisms described in [RFC2461] and [RFC2462]. When a network interface connects to a new network, IPv6 will normally create a Link Local address by combining the well-known link local subnet prefix FE80:: with the interface identifier (IID). The IID is just a 64 bit long pattern, intended to be unique to the interface within the scope of the link to which it is attached. The Link Local address is a tentative address because it has not yet been shown to be unique. The node joins the all-nodes Multicast group (FF02::1) and the Solicited-node Multicast group for the tentative address. The Duplicate Address Detection (DAD) process then uses Neighbor Solicitation messages sent to this Solicited-node Multicast group to verify that no other node on the link is using this address. A node that is already using the tentative address will also be listening on this Multicast address and will respond with a Neighbor Advertisement message sent to the all-nodes Multicast address. The Neighbor Solicitations being used for DAD use the unspecified address (all zeros) as the IP source address. An IPv6 interface may use several addresses derived by combining a single IID with a number of different prefixes. The use of the solicited node Multicast group reduces the number of groups that the node has to join to monitor DAD solicitations and reduces the number of Neighbor Solicitations that need to be processed above the link layer. If no other node responds claiming prior rights on the address, it can be marked as a preferred address and used for future communications of link scope. Up to this point, the process is the same for both hosts and routers. Newly connected routers now join the All-routers Multicast group (FF02::2) and send out unsolicited Multicast Router Advertisements to the All-nodes Multicast address (FF02::1) to let all connected hosts know that a new router is available. Newly connected hosts send out a Router Solicitation message to the all-routers Multicast group to find out what routers are connected to the link and what subnets they can join. Routers on the link reply to the host with a targeted Router Advertisement. The Router Advertisements contain the following information: Router lifetime: nodes should not use routers that have not sent Router Advertisements for more than the lifetime Managed (M) flag: If configured to 1, nodes on this link should use a management system such as DHCPv6 to obtain addresses rather than stateless auto-configuration. Zero means use stateless auto-configuration. October 2017 Avaya Aura Application Server 5300 Overview 192

193 Stateless and stateful autoconfiguration Other (O) flag: If configured to 1, nodes should use a management system such as DHCPv6 to obtain non-address related configuration information and should use stateless autoconfiguration to get addresses. Reachable Time: used by Neighbor Unreachability Detection algorithm, it indicates the time a host assumes that neighbors are reachable after receiving a Reachability confirmation from its neighbors. Zero means unspecified. Retransmission Time: time between retransmissions of Neighbor Solicitation messages during address resolution and Unreachability detection Link-layer address of the router interface from which the message was sent (optional) MTU size for the link (optional) Prefixes used on the link: router advertises all the prefixes and the advertising router that the node on the link needs to know. Each prefix has some associated information: - A flag : If configured, indicates that this prefix can be used for stateless (autonomous) address auto-configuration by nodes on the link. - L flag : If configured, indicates that addresses using this prefix are on-link so that packets can be sent direct rather than through a router (it is possible that some of the addresses belonging to a prefix might be on-link and others off-link for example, addresses used for Mobile IPv6 nodes would not be on-link unless the node was at home. Packets sent to a mobile node from another node connected to its home link need to go to the router to be redirected if the node is not at home. Consequently, the values of the A and L flags are completely independent.) - Lifetime, during which a prefix should be considered valid After a host has received Router Advertisements, the stateless and stateful auto-configuration processes diverge. If a Router Advertisement has the Managed (M) flag set, the host can use DHCPv6 to obtain addresses usable for communication beyond the local link. Otherwise, the host uses one or more prefixes, with the A flag set, found in the Router Advertisement to build global or local use addresses by adding its IID. The host should use DAD to check the uniqueness of the created address again. But if the previous DAD checks made for the Link Local address using the same IID were successful, the new addresses can be assumed to be unique and used immediately for communications as preferred addresses. This process is known as Stateless Auto-configuration (Figure 23: IPv6 autoconfiguration on page 194) because the router doesn't need to maintain any additional information about which hosts obtain configuration from the router. Stateful autoconfiguration emulates the current process for IPv4 using an updated version of DHCP. Using DHCP, a host can contact an on-link DHCPv6 server directly using a Multicast address, or an on-link router can provide a DHCPv6 relay function that allows DHCP information to be obtained from a server elsewhere on the same site. DHCPv6 can also be used to provide additional configuration when Neighbor Discovery and Stateless Auto-Configuration are used to set up addresses by setting the Other (O) flag in the Router advertisements. October 2017 Avaya Aura Application Server 5300 Overview 193

194 IPv6 overview Figure 23: IPv6 autoconfiguration An autoconfigured address can be in one of the following states: Tentative: the address is in the process of being verified as unique. Preferred: the address has been verified as unique. Deprecated: the address is still valid, but using it for new communication is discouraged. Existing sessions can continue to use a deprecated address. Valid: this state covers both the preferred and deprecated states. The valid lifetime must be greater than or equal to the preferred lifetime. Invalid: the address can no longer send Unicast traffic to or receive it from a node. An address enters this state after the valid lifetime expires. Autoconfigured addresses are almost always obtained on limited-lifetime leases. The length of the lease will be specified by means of a preferred and a valid lifetime when the prefix or address is obtained. Address leases can be extended either by Router Advertisements for stateless autoconfiguration or through DHCPv6 for stateful autoconfiguration. The initial Link Local address has an infinite lifetime and never needs renewing. October 2017 Avaya Aura Application Server 5300 Overview 194