3 What is Avaya Aura®?Avaya Aura® is the communications solution for next generation, people-centric collaboration.Session (SIP) based communicationsUnified Communications and CollaborationUsers, not technology, define the experienceThe basis for collaborative, barrier-free business environments that drive business results for our customers:Industry leading levels of flexibility, scalability and reliabilityHard dollar cost benefits for customers through simplification and access savingsOpen standards and 3rd Party solutions integrationA migration path forward for every customer

6 Optimized Bandwidth Management Avaya Aura® Session ManagerAvaya Aura Core(Session Manager)Site 1Site 2Site 4Site 3Allows locationspecific allocationof bandwidth betweenvoice and multimedia withvideo down-speeding as required25% Expect video will consume half of all bandwidth in 12 months33% Expect bandwidth consumption to increase by more than 50% in next two yearsNetwork Instruments' Fifth Annual State of the Network Global Study March 2012Avaya: Optimized bandwidth management for multimedia and video based communications while minimizing network strain and latencyIntegrate voice and multimedia bandwidth on a single networkEstablish and assure voice quality on a location by location basisMonitor and flexibly optimize bandwidth to meet business needs

9 Lifecycle - What is CI, GA, EOS, EOMS, EOSS, and EMSSP?CI - Controlled IntroductionMost Products are GA ready, but a component(s) is not ready for complete SolutionGA - Generally AvailableAll components and the Solution are readyEOS - End of SaleEOMS - End of Manufacturer SupportNo new patches are delivered; diagnostic services still availableEOSS - End of Extended Services SupportDiagnostic services no longer available*EMSSP - Extended Manufacturer Software Support PolicySelect products/solutions will be sold for minimum of 2 years, and have software support for minimum of 3 yearsNo New System SalesNo System Upgrade SalesExpansion of new user licenses permittedFeatures expansion or new features ceasedNew Service Contracts permitted with terms not past EOSS dateTier IV support till EOMS with valid Avaya Services ContractNew Service Packs available till EOMSTier III support till EOSS with valid Avaya Services Contract

10 Avaya Aura® EMSSPExtended Manufacturer Software Support Policy (EMSSP) offers an additional category of support for certain releases of products allowing those products to be sold and supported for a extended and predictable period of time.Permits Partners and Customers to standardize on a longer term productFor designated EMSSP release, Avaya willsell the EMSSP release for a minimum period of two (2) years andsupport the release for a minimum of three (3) years from its date of first sale.Current EMSSP Release 5.2 over 4 years availability – May > June 2013*Communication Manager 5.2.1Mid-size Business Template 5.2.1*SIP Enablement Services 5.2.1*Integrated Management 5.2.1Call Center Elite 5.2.1Application Enablement Services 5.x*

12 The Feature Pack ConceptIn addition to regular major and minor (“dot”) releases, provide a feature release mechanism that:Supports lightweight deployment:Remote installation, no upgrade requiredMinimizes time, cost and disruption to the customer’s networkRequires minimal or no customer lab testingAllows customer selectable content:Customer implementation of valuable features, not every featureIncrease deployment confidenceReduces potential impact of features that are not of interestProvides full testing rigor:System verificationRegression testingAlpha and Beta as appropriate for content

13 Feature Pack Content Selection CriteriaNo infrastructure / architectural changesMinimal or no management changesMinimal number of interdependent componentsContent will become a candidate for a future major or minor releaseWhat if content fails to meet this criteria?

19 Improving Simplicity, Security, and Presence InteroperabilityAvaya Aura® CY2012 & CY2013Avaya Aura R6.2GA July’12Avaya Aura R6.2 FP1Dec 3, 2012Avaya Aura R6.2 FP2May 6, 2013Intra-enterprise federation with multiple OCS/ Lync domainsExchange calendar integrationSupports Video SRTPToll Bypass for IndiaV.150 for GatewaysExpand to 2K Network RegionsParallel ForkingExtended Manufacturer Software Support ReleaseImproving Simplicity, Security, and Presence InteroperabilityBest in class business continuity with the addition of System Manager Geo-RedundancyEMSSP = We will sell the last dot.dot load of any given load line for at least 2 years post GA of the release, and then normal 1 year Manufacturing support after EOS.XMPP Federation with OpenFire: Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). This is the same technology used by Avaya Presence Services. Federating Avaya Presence Services to OpenFire enables Avaya to share IM and Presence between Avaya clients (Flare, 1xC, etc) and clients connected to OpenFire.Access Control List Enhancements: This release adds support for 9 new ACL use cases primarily around Confirm, Deny and Revoke user access commands. The enhancements are required for two lead customers ZDF and Bosch. Presence enhancements: XMPP Federation with OpenFire & Access Control List (ACL) enhancements(SA9120) Automatic Mute for Remote Off-hook Attempts GRIP 3587(SA9119) - Exclusion Event Notification to SIP Phones GRIP 4901Transmit Agent ID to H.323 phones to support Agent Greeting FeatureSIP / H.323 Dual Registration (Concurrent Login)19

20 Getting Ready for Release 6.2: Supported HardwareCommunication Manager:S8300D: Embedded blade for Avaya Aura Gateways (G450/30,350,250,700)S8510 Server - not used for duplicationUse in a simplex migration by adding memory (6 GB) to total of 8 GBMost have 250GB HDD but if 146G HDDs, add third 146GB HDD and RAID 5Avaya Common Servers and S8800Session ManagerSystem ManagerSystem Manager 6.2 (standalone) on the following Avaya Servers:Avaya Aura® Solution for Midsized Enterprise 6.2 HAAvaya Common ServerMBT 5.x transition to ME 6.x requires a server replacementPrevious Hardware versions not listed above are not supported2020

21 Scale and Performance: Avaya Aura ScalabilityUp to 250,000 Total End PointsUp to 100,000 Total SIP End PointsCommunication Manager 6.2Up to 36,000 SIP End PointsUp to 24,000 SIP TrunksSession Manager 6.2Up to 12,000 SIP End Points per Session Manager (standalone)Up to 10 Session Managers in a single networkUp to 500 Communication Manager InstancesSystem Manager 6.2Avaya Aura Solution for Midsized EnterpriseUp to 1000 Total End PointsUp to 1000 Total SIP End PointsUp to 350 SIP Trunks

22 Standalone Utility Services 6.2Seems ASD needs a little more programming. Open a case to have manually added to the quotematerial code is the Utility Services mediamaterial code is the CSR1 HP server as defaultStandalone Utility Services 6.2 provides support for Duplex CM configurationsCDR is not available with this configuration presently

24 Thank You For more information:Products and Solutions technical supportTechnical documentationSpeaker Notes/Script:Thank the participant for listening to this session. Then discuss the additional resources for this product/offer. Mention the links, but it is not necessary to read them.

26 Scale and Performance: Call PreservationApplicable to Session Manager (SM) Cores with Multiple SMsIn the event of a SM failure:Connections in progress and Calls in queue are preservedIncludes calls to AACC as long as they are routed through VP or CMG860/M3000 and SBCs SupportedCustomer Admin-able by time of day, immediate or manualAACCMXVPMMCSPSAAMCMMMAA SBCSIPTrunksCoreSMSMSMSMSMPSTNSMSMSMSMSMTDMTrunksG860Avaya Aura™ CMAvaya Aura™ CM

27 Scale and Performance: Survivable Core Connection PreservationPrevention of split registrations of media gateways and H.323 endpoints between the main Communication Manager or Survivable Core or Survivable Remote serversControls the registrations to provide the best system functionality in various outage scenarios by preserving the desired connections

28 Scale and Performance: System ManagerManage 250,000 total usersCommon provisioning with single LDAP synchronization for Avaya Aura and CS1000 usersSingle authorization (RBAC) for Avaya Aura and CS1000 systemsCentral provisioning of B5800 branch gateways including upgradeAdministration of advanced SIP featuresNative administration of new 94xx and 96xx endpointsSupport for hospitality solutions by enabling CM to control “endpoint display name”

29 Scale and Performance: System ManagerReal time notification of CM changesAudit trail of CM changes made by System Manager administratorCentral administration of management parameters for System Manager and its adoptersTrust Management certification management providing simple provisioning of secure UC communicationHardened System Manager security via OS hardening and password complexitySection 508 compliance assessmentVPAT (Voluntary Product Accessibility Template)Targeted at Federal and State Government

31 Session Initiation Protocol: SIP Call FeaturesEnhanced Call ForwardingSupports call forwarding on “Unconditional” “Busy” and “No Reply”Permits user to differentiate between treatment of internal and external callsSame operation as on H.323 end points (User receives visual and audio feedback on feature activation and visual guidance on invoking feature)Each of the 6 permutations can have a different destination

32 Session Initiation Protocol: SIP Call FeaturesEnhanced Call Pickup AlertingWhen any member of a pick up group is called, the displays of all members of the pickup group are updated with the calling and called party information, enabling a member to decide whether to pick up the call or not.The following alerting options are available: Intercom ring, Silent if busy (if the user is busy on another call, the audible alerting is skipped.), half-ring, continuous, single if busy, no ring, single ring.The timing of the display and audible notifications are separately administrable.Same functionality as on H.323 end points

33 Session Initiation Protocol: SIP Call FeaturesSIP Team ButtonThe assignment of a team button on a station brings it automatically into the virtual team, establishing a data relation between the monitored station and the monitoring station.The Team Button has two functions:Display function: Allows any member of a team (monitoring station) to observe the station state of other team members (monitored station).Execution function: Allows the Team Button to be used as a Speed Dial Button or Pick-Up Button. Depending on the state of the monitored station, when the Team Button on the monitoring station is pushed, a call to the monitored station is established directly or a ringing call is picked from the monitored station.The number of monitored stations that can be monitored by other stations is limited to a maximum of 15.Same functionality as on H.323 end points

34 Session Initiation Protocol: SIP Call FeaturesGroup Paging to SIP PhonesPage groups are created by assigning extensions as members of the group and an extension number which users dial to page the group.When a user dials the extension of the paging group, Communication Manager activates the speakers on all the telephones in the group. Speakerphone paging is one-way communication: Group members hear the person place the page, but cannot respond directly.Same functionality as on H.323 end pointsSIP Auto Dial ButtonsOne-touch access to frequently called numbers