• Save
Design of small to large multi site solution, based on 8300, 8800 simplex, 8800 dup servers. mbt. lsp-ess and cmmaudio session-1 dcp
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Design of small to large multi site solution, based on 8300, 8800 simplex, 8800 dup servers. mbt. lsp-ess and cmmaudio session-1 dcp

on

  • 3,720 views

AURACA ASD Design MBT Solution S8800 Simplex Duplex Model

AURACA ASD Design MBT Solution S8800 Simplex Duplex Model

Statistics

Views

Total Views
3,720
Views on SlideShare
3,720
Embed Views
0

Actions

Likes
5
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Speaker notes:
  • Speaker Notes: The S8300 server with a G700, G450, G350 or G250 media gateway provides a flexible solution for growing companies to streamline voice and data operations over one networked infrastructure. It can be a standalone solution for a small business or a remote edge device for a larger enterprise network with 8 to 450 stations. In addition to acting as the main controller, the S8300 can also be used as a local survivable processor (LSP). With the CM release 5.1, the S8300 messaging application supports IMAP4 Internet Message Access Protocol. The S8300 media server: Supports 10,000 BHCC in non call center configurations, 5,000 BHCC in call center configurations Supports an S8300 Linux operating system; supports 900 ports by a combination of trunks and stations 450 IP stations, 450 non-IP stations, or a combination of 450 IP and non-IP stations 450 trunks 50 media gateways Has Simplex Reliability options Operation modes include Internal Call Controller (ICC) or Local Survivable Processor (LSP) Includes IA770 messaging software application Can be inserted only into a G250, G350, G450, or G700 media gateway to provide a flexible solution to streamline voice and data operations over one networked infrastructure. With the full capabilities of the CM software and an internal layer 2 Ethernet switch, it can be used as a total converged standalone solution for a small business or as a remote edge device for a larger enterprise network. Avaya IA770 Integrated Messaging Solution The Avaya INTUITY™ AUDIX® 770 (IA770) solution is an integrated messaging application that delivers voice and text messaging.  It is included as an entitlement of the CM license and supports up to 450 users. It provides call answering and messaging capabilities embedded within an Avaya media server to improve communications and simplify information exchange within enterprises. With CM 5.0, it will support the IMAP4 protocol. The IMAP4 Internet Message Access Protocol will allow customers to use their own IMAP client for message retrieval using the standard protocol.
  • Critical Communication Manager application files and translations are loaded onto the SSD. This means that in the event of a hard disk drive failure, many critical functions are still Available.
  • Speaker Notes: The S8400 can be used in the following gateways: The S8400 media server consists of a TN8400 hardware/software platform, a TN8412AP SIPI circuit pack, the Avaya CM , and optionally, the IA770 messaging software. For migration, the S8400 media server is used as an upgrade path for a current PN, based on the G650 and G600 media gateways and CMC carriers. Since the S8400 media server supports only one PN, and different media gateways cannot be mixed in the same PN, a G650 media gateway cannot be added to an S8400 system that carries forward a CMC1 or G600 media gateway as a result of a migration. For new installations, the PN uses the G650 media gateway.
  • For small to medium sized deployments, the S85xx servers can be operated in the PE mode to simplify hardware configuration & reduce costs.
  • The Avaya G450 media gateway provides a scalable, reliable, and secure platform for the delivery of Avaya CM-based IP telephony applications. The G450 can also be configured with an S8300 server blade or a standalone S8500 server to deliver CM-based telephony to standalone or small campus environments. The G450 features include: The Avaya G450 media gateway consists of a 3U high, 19" rack mountable chassis with a field-removable supervisor main board module, power supplies, fan tray, DSP resources and memory.  It has eight media module slots that host a combination of interface boards to support T1/E1, ISDN-BRI, WAN interfaces, digital or analog telephones and analog trunks.  Supported in CM 5.0 and above Supports 450 stations/450 trunks Two base offers – G450-MP20 for the small to mid-size branch and G450-MP80 for the mid-to-large size branch (up to 4 DSP child boards can be mounted on the motherboard)
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Estimated time to complete the session: 90 minutes Speaker notes: The agenda of the ‘CM Survivability and Reliability’ module is to cover, in detail, the various features of the CM which make it reliable and survivable to withstand any kind of failure. It will take about ninety minutes to complete this session. In this session, you will learn about: The 7 layers of resiliency available with an Avaya IP telephony solution The value proposition behind the S87xx stateful failover capability Standard Local Survivability and how to position it in an Avaya solution Local Survivable Processor and how to position it in an Avaya solution Enterprise Survivable Servers and how to position it in an Avaya solution Value proposition in Dial Plan Transparency and Adjunct Survivability Difference between CNA and APC and the value proposition of each
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Estimated time for this topic: 8 minutes Treatment: Static slide Speaker notes: Let us now learn about the resiliency in S87xx servers. This topic also covers the various reliability options available in S87xx servers.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: For every click, each bullet text along with the corresponding figure appears. The speaker notes below must be synchronized with the bullets on the slide. Speaker notes: In the CM, two S87xx servers are used - one active call processing server, and the other server’s memory is shadowed. This is similar to the mechanism described in the first layer of resiliency. Servers can be separated by: Dedicated fiber, up to 10KM (hardware duplication) Gigabit IP network (software duplication) In case of a server failure, any ongoing call is not disconnected. S87xx servers have the feature of preserving a full call state upon server failure.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Estimated time for this topic: 10 minutes Treatment: Static screen Speaker notes: Standard Local Survivability (SLS) is a basic survivability feature suitable for small gateways. We will now see how we use SLS in our gateways and its positioning in our solution as compared to the LSP. We will also talk about the various stations and trunks supported in the SLS mode.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: In two clicks, the text and the black box (showing customer benefit) appear, respectively. The s peaker notes below must be synchronized with the bullets on the slide. Speaker notes: SLS was a new option introduced in CM 3.1. It provides minimal call control without using an S8300 server, and is intended to provide a low-cost alternative for the survivability of small branch offices. SLS works best for an entry level survivability option for a single branch office. SLS is similar to Cisco’s Survivable Remote Site Telephony (SRST). SLS is an alternative to the LSP only if basic telephony survivability is required. It provides survivable call processing integrated in the gateway with its build-in software module. SLS provides call engine and routing functionality for local lines/trunks when the CM or LSP are not reachable. It is administrable via the Personal Information Manager (PIM) or the local gateway Command Line Interface (CLI). The SLS feature was initially supported on the Avaya G250 Media Gateway alone. Now, it is also available in the following gateways: G250 (all models) G350 (hardware suffix C and above) G450 IG550 gateways (4350, 6350) The primary customer benefit SLS offers is integrated no cost survivability for branch gateways.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: The text appears upon clicking. The speaker notes below must be synchronized with the bullets on the slide. Speaker notes: SLS supports calls between local stations and to/from local PSTN trunks Local station support includes analog, DCP, IP phones and IP Softphones (Road Warrior) In this mode, there are no limitations on the number of analog, DCP stations (except G450 – 240 overall maximum stations) In the SLS mode, all analog, ISDN BRI, PRI (all 25 country codes), E1/T1 trunk types are supported The H.323 Gatekeeper supports a maximum of: 12 IP stations for G250 72 IP stations for G350 240 IP stations for G450
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Estimated time for this topic: 15 minutes Treatment: Static screen Speaker notes: We have already learnt about the SLS mode and how it functions for small locations. We will now see how the Local Survivable Processor (LSP) helps stabilize communication when there is broken connectivity between remote sites and the main location. We will also learn about the transitioning and back-up modes of the LSP and how an S85xx server functions as an LSP and Processor Ethernet (PE).
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: The text and the image appear upon clicking. The speaker notes below must be synchronized with the bullets on the slide. Speaker notes: A local S8300 server can be configured as a primary MGC, that is, an Integrated Call Controller and a secondary MGC, that is, an LSP. While the primary controller is unavailable, the local S8300 configured as a secondary MGC prompts into action and provides comprehensive local call processing capabilities. The LSP continues to provide service in case of broken connectivity between remote sites and main locations. The LSP provides redundancy in a variety of configurations (such as call center agents and local announcements) and can be located anywhere in a network of H.248 MGs.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: In three clicks, the bulleted text, the images with labels and the black box (showing customer benefit) appear, respectively. Speaker notes: System translations are automatically propagated to local processors. All station, trunking applications and system programming are up to date if the LSP needs to take over. G250, G350, G450 and G700 MGs support LSP. When “Customer benefit……. protection” appears on the slide: The LSP empowers the administrator with the ability to define how the system behaves in the case of lost network connectivity. The priority can be placed on maintaining a solid network or on a speedy switch to the LSP and short downtime. Thus, LSP provides a complete network outage protection.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: Static screen Speaker notes: The LSP solution requires the CM software license to activate the LSP feature. This software license allows the S8300 media server to be a survivable call-processing server for remote/branch customer locations, as well as a redundant call controller for a standalone S8300 media server. Each gateway is initially administered with a list of gatekeepers. If the link to the primary call controller fails at some later time, the MGs and IP endpoints will try to receive service from the other gatekeepers in the list, including the LSP(s). An LSP will provide service to all MGs and IP endpoints that register with it. The LSP can be administered to either fail-back to the primary automatically, or be moved back manually. This fail-back process will inform the IP endpoints to try their gatekeeper list again, and return to the primary call controller for service. The LSP does not currently provide support for traditional PNs, such as the MCC, SCC or G650, and it is not intended to be the only vehicle to provide reliability for an entire large network. The design intent of an LSP is to serve a subset of the network, such as a remote geographic location with a small or mid-sized office.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: Static screen Speaker notes: Let us now look at how the LSP comes into action when there is a failure. The transition to the LSP is an automatic process. When an endpoint determines that it can no longer communicate with the primary gatekeeper, it searches its list of gatekeeper candidates until it finds one that responds to the registration request and allows the gateway to register. The amount of time an MG takes to transition over to the LSP will vary based on the nature of failure, the transition point, timer settings, and the number of alternate gatekeepers attempted. The MGs send a keep-alive message once in every 20 seconds. If failure occurs in the network, and the MG does not receive a response to three keep-alive messages in a row, it will then enter into a recovery mode and begin the search for a new gatekeeper. This takes a maximum of 60 seconds. If the failure occurs at the CLAN or the primary gatekeeper, the communication link is closed and the gateway is alerted to this closure immediately. The next stage of a failover is the search time to find a new gatekeeper. The MG will try to re-register with the same IP address first. If that address is unreachable, the MG will continue through the list until it is able to register with one of the addresses. Once the MG makes contact with a gatekeeper, the MGP is restarted. Following this, the search starts again at the beginning of the list. This allows the gateway the best chance to be registered with the primary gatekeeper, especially after a short network outage when the primary gatekeeper is still able to provide service and the link between the gateway and the primary gatekeeper has been restored. Until the MG reaches a second gatekeeper, all calls in progress will remain, but without access to features. However, new features and new calls are not accessible until the re-registration is complete.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: The text and image appear upon clicking. Speaker notes: Let us now have a look at the transitioning to/back up modes of the LSP. The LSP preserves the connection for all existing stable calls where the talk path between two or more parties is not dropped. After having failed over to the LSP as per the MGC list, the gateway automatically reconnects to the primary server when it becomes available. This provides automatic reconnect to allow for orderly return to service without manual intervention. Failover or fallback to the LSP takes approximately 3 minutes. Note that the LSP cannot preserve the connection for: Calls not in a stable state such as ‘on-hold’, ‘ringing’, and so on Calls using IP or ISDN-BRI trunks, or ISDN stations
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Estimated time for this topic: 20 minutes Treatment: Static slide Speaker notes: We have seen how the CM preserves the connection for small locations and remote site locations. For a catastrophic failure, we have developed Enterprise Survivable Servers (ESS). Let us now see how the ESS works and the differences between ESS & LSP. We will also learn about Dial Plan Transparency (DPT) and expanded adjuncts survivability. It will take about twenty minutes to complete this topic.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: The text appears upon clicking. Speaker Notes: We have developed the ESS to support larger portions of a network, or the entire network. The ESS allows backup servers to be placed at various places in a network so that communications can continue in the event that a main server(s) fails, or when connectivity to the main server(s) is lost. Deploying the ESS at appropriate points in a network provides flexibility in planning against system failover. Administration for the ESS can be conducted in a central point with automatic synchronization to all ESSs. The ESS now provides a survivability option for S8500 media servers. The ESS can be connected to Asynchronous Transmission Mode (ATM), IP, and Center Stage Switch (CSS) connected PNs. The IPSI card in the PNs automatically obtains service from the ESS if the control signal to the main server is lost. The ESS can also be used in a direct connect configuration. In a direct connect, only one of the PNs has an IPSI and so only that PN will survive to the ESS.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: Static slide Speaker notes: The S85xx media server or S87xx media server can act as an ESS. All ESSs have full translations and can connect to all IPSIs advertising their factors.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: Static slide Speaker notes: The figure shows a catastrophic main cluster failure with all of the PNs failing over to a single ESS cluster. Upon a main cluster failure, PNs lose their control source. If this failure is catastrophic in nature, whereby the main servers are not operational again for an extended period of time, PNs can search out and find ESS servers that will provide them service. Therefore, the ESS protects PNs against extended failures of the main controlling cluster. For most scenarios, the desired failover behavior caused by a catastrophic main server failure is to have all surviving PNs find service from the same ESS server in order to keep the system in a non-fragmented state.
  • © 2009 Avaya Inc. All rights reserved | Avaya-Proprietary & Confidential Under NDA Treatment: Static slide Speaker Notes: Upon a connectivity failure to the main cluster, PNs lose their control source. If this fragmentation continues to exist over an extended period of time, PNs can search out and find ESS servers on their side of the fragmentation that will provide them service. Therefore, the ESS protects PNs against significantly long fragmentations away from the main controlling cluster. For most scenarios, the desired failover behavior caused by a network fragmentation is to have all PNs which can still communicate with each other to agglomerate together, forming a single stand-alone system. The figure shows a network fragmentation with all of the PNs on the right side of the fragment grouping together to form a single autonomous system. It cannot be emphasized enough that the ESS increases the availability of a communication system when faced with catastrophic server failures or extended network outages. The ESS builds upon all of the existing fault recovery mechanisms which are already integrated into the system. For example, when a network outage is detected, the PBX attempts to re-establish PN control by interchanging IPSIs (if the PN has duplicated IPSIs), fallback control through another PN (if the PN is leveraging CSS or ATM PNC), and reconnecting to the PN and warm restarting it (if the outage is persistent for less than 60 seconds) before ESS servers ever get involved. The ESS is the last line of defense to provide service to PNs while in these severely handicapped situations.
  • Complete one-box communication system Targeted for mid-large sized businesses Up to 2400 users Applications included - with same features and capacities as if running standalone Communication Manager 5.2.x Communication Manager Messaging 5.2.x SIP Enablement Services 5.2.x (Home/Edge Combo) Application Enablement Services 4.2.x Media Services (software IP media gateway) Utility Applications
  • Customer One-server makes life simple. Faster time-to-value Less costly to buy: (75% less hardware, overall 15% price reduction) Lower TCO: 75% smaller footprint, less power and cooling. SIP Trunking savings 20-50% on telecom expense 75% less time for system maintenance with integrated services for administrators (upgrades, backup/restore with ease) End user self-administration High Availability option with automated backup server Add applications easier Work from anywhere – mobile, home, remote. Add one-X UC All Inclusive on a single server from CRI and Avaya Serve customers better with an easy to deploy and manage multi-channel contact center solution, Contact Center Express. Reduced foot print, pre-configured solution that can be installed quickly and easily. Add advanced Unified Messaging with Single Server Modular Messaging

Design of small to large multi site solution, based on 8300, 8800 simplex, 8800 dup servers. mbt. lsp-ess and cmmaudio session-1 dcp Presentation Transcript

  • 1. Design Competency Program- Session – I Presented by: Manav Sukhija & Subrat panda© 2009 Avaya Inc. All rights reserved.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA Avaya – Proprietary & Confidential. Under NDA 1
  • 2. Today’s session will cover:  CM servers and gateways for different customer segments.  Resiliency/survivability.  Midsize business template.  Communication Manager messaging.  Creating Design Solutions for various scenarios in ASD 2© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 3. S8800 duplex Server Blades and Appliances 36,000 (12,000 IP) Stations / 600,000 BHCC / Stateful Failover S8800 simplex 2,400 Stations / 100,000 BHCC S8400 900 Stations / 10,000 BHCC Scalability S8300 450 Stations / 10,000 BHCC Performance© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 3
  • 4. Servers and Gateways • Server Current offerings –S8300D under S83xx Series (450 users) –S8400B under S84xx Series (900 users) –S8800 Simplex for medium sites (2400 users) –S8800 Duplex for large customers (36K users) • Gateway Current offerings: –G430 –G450 –G650 (Works with S8400, S8800 simplex/duplex only)© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 4
  • 5. S8xxx Media Server Overview© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 5
  • 6. S8300 Media Server Overview • The S8300 Media Server supports: –10k BHCC –900 ports by a combination of trunks and stations • 450 IP stations, 450 non-IP stations, or a combination of 450 IP and non- IP stations • 450 trunks –50 G700/G450/G350/G250/G150/IG550 Media Gateways • Simplex Reliability options • Operation modes include Internal Call Controller (ICC) or Local Survivable Processor (LSP) • Includes CM Messaging Software Application (Supported only in ICC Mode) • This module is inserted only into a G250, G350, G430, G450, or G700 media gateway.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 6
  • 7. S8300D Overview • The S8300D Server is supported by Communication Manager Release 5.2 and later. • An S8300 Server (version D) is an Intel Core 2 Duo U5700 processor that runs the Linux operating system. The S8300D Server resides in Slot V1 of a Media Gateway and includes: • A 250-GB hard disk • 4 GB DRAM • 8 GB Internal Solid State Drive (SSD) • Three USB ports and a 10/100 Base-T port • One USB port supports a readable DVD/CD-ROM drive, which is used for system installations and upgrades. • One USB port can be used for a USB modem. • Another USB port can be used for a Compact Flash drive. • One services port • One internal Compact Flash drive, which is used as the primary reboot device • Modem support for alarming© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 8. S8400 Server Overview • Supports a single PN composed of G650, G600, or CMC. • The system also supports up to five G150, G250, G350, G450, and G700 media gateways. • Can be an Enterprise Survivable Server (ESS) to a S87xx or a S85xx server with CM 5.2. Also a G700, G350, or G250 Media Gateway that is connected to an S8400 Media Server can have an LSP installed. • 900 Maximum number of stations, IP or TDM. • 400 Maximum number of trunks. • Provides a Voice over Internet Protocol (VoIP) based integrated messaging capability for up to 450 light duty users. • This module is inserted only into a G650, G600, or CMC cabinets.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 8
  • 9. The S8400 can be used in the following gateways For migration For NEW installations CMC (Compact Modular Cabinet) G600 G650© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 9
  • 10. CM S8800 Server Highlights • S8800 servers will be utilized by not only CM but also by 22 other Avaya application configurations • Same S8800 1U server configuration is used by both CM simplex and duplex configurations • Capacity in simplex Mode • Supports up to 3200 ports – 2400 Stations (IP or TDM) – 800 Trunks • Duplex serves will utilize software duplication. • Capacity in duplex Mode • Up to 600,000 BHCC (w/HW dup & Gen Call Mix) • Up to 36K stations, 8K trunks • Runs CM 5.2.1 software and Redhat Enterprise Linux (RHEL) 4 pre-U1 release© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 11. CM S8800 Hardware Summary • Both simplex and duplex CM installations utilize the new Avaya 1U S8800 server which contains: – 1 each new quad core Intel I7 “Nehalem” CPU running at 2.26 GHz MHZ – 4 GB of DRAM – Utilizes a RAID 1 disk array consisting of 2 each SAS 10K 146 GB disk drives. RAID is similar to that used on S8510 and S8730. Uses the MR10i RAID controller. – Employs 5 gigabit NICs (6 NICs are available) – Integrated Management Module (iMM)/Baseboard Management Controller (BMC) system on a chip – Optional: Redundant Power Supply© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 12. S8800 Servers Deployment© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 12
  • 13. Avaya S8800 Media Server with a G650 Media Gateway S8800 PSTN IPSI G650 24xx 96xx Medpro CLAN IPSI = IP Server Interface CLAN = Circuit pack for signaling and registering IP phones Medpro = Circuit pack media flow, codecs© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 13
  • 14. Avaya S8800 Media Server as Processor Ethernet with a G450 S8800 PSTN 24xx 96xx G450 Control of gateways with H.248 (Media Gateway Control Protocol) IP phones registered directly with the Media Server and no longer with the CLAN© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 14
  • 15. Gateways© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 15
  • 16. G650 Media Gateway • High density gateway. Compatible with S8800 simplex/duplex and S8400 servers. • Communicates with the CM server through IPSI circuit pack. • 242 two way communication time slots. • AC/DC Power Supply. • Redundant Power Option (hot swappable) • 14 Slots • Simplified Carrier Addressing • Adherence to the New Avaya Look & Feel • Supports most standard TN packs© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 17. G450 Media Gateway • Next Generation Media Gateway for –Branch offices of medium and large enterprises (w/S8XXX Servers) –Mid-market standalone (w/S8300 or S8800 Server [PE]) –Small campuses (w/S8800 Server [PE]) –Small-Mid Call Centers • Part of the Avaya H.248 Gateway portfolio • Scalable, modular platform© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 18. Key Points • G450 capacity is determined by the server and by the traffic pattern • The G450 is not stackable, but multiple gateways can be deployed in a single location and controlled by single Server. • Two base offers: –G450-MP20 (25 DSPs in CM 5.2.1) for the small to mid-size branch –G450-MP80 for the mid- to large size branch • Supported by CM 5.0 and above© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 19. The Avaya G450 Media Gateway • The G450 gateway can function either as a stand alone system or as a gateway extending a centralized system out to a remote location • Supports 450 stations/450 trunks • 3U chassis, 19” rack, desktop or wall-mount • Field removable Motherboard /PSU/ Fan Tray/DSP resources • Supported in CM5.0 and above • Two base offers – G450-MP20 for the small to mid-size branch and G450- MP80 for the mid- to large size branch (up to 4 DSP child boards can be mounted on motherboard) Field-removable motherboard Fan Tray Server slot for S8300 Eight Media Module Slots© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 19
  • 20. G430 Media Gateway • New Media Gateway for –Small and medium branches (2-150 users) of medium and large enterprises –Small/Medium Contact Centers (Standalone or Branches) • Part of the Avaya H.248 CM Gateways (G250/G350/G450) • Support S8300 • Support SLS as low cost survivability© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 21. G430 – Scalability and Resources • Scalable platform – modular design that – fits the transition toward IP –enables standardization at the branches • 3 Slots and 20 DSP channels on the G430 • Slots –Can add more slots with EM200 • DSP –Can add more DSP channels –Using the same MP20 and MP80 used with the G450 –In addition introduction of the MP10© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 22. Survivability & Reliability© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 22
  • 23. • S88xx Server Resiliency/Reliability options • Standard Local Survivability • Local Survivable Processor • Enterprise Survivability 23© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 24. S88xx Server Resiliency/ Reliability options 24© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 25. Resiliency in S88xx Servers • One active call processing server, and the other server’s memory is shadowed •Servers can be separated by: • Gigabit IP network (software duplication) • During server failure, a full LAN/WAN call state is preserved 25© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 26. Standard Local Survivability (SLS) 26© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 27. SLS Introduction SLS: • Is an entry level option for small branch options • Is similar to Cisco’s Survivable Remote Site Telephony (SRST) • Provides survivable call processing integrated in the gateway • Is available in both G430 and G450 gateways. Customer benefit: integrated, no cost survivability for branch gateways. 27© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 28. SLS: Stations and Trunks Supported SLS supports: • Calls between local stations and to/from local PSTN trunks • Analog, DCP, IP phones, IP Softphones in local stations • Any number of analog, DCP stations • All trunk types The H.323 Gatekeeper supports a maximum of: • 12 IP stations for G250 • 72 IP stations for G350 • 240 IP stations for G450 28© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 29. Local Survivable Processor (LSP) 29© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 30. LSP in H.248 Gateways: Introduction • A S8300 server can be configured as: • Primary MGC i.e. Integrated Optional LSP in G350 Call Controller gateway • Secondary MGC i.e. LSP • While the primary controller is unavailable, the local S8300 configured as a secondary MGC prompts into action • LSP preserves all features available in normal operation 30© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 31. LSP in H.248 Gateways: Introduction • System translations are automatically propagated to local processors • The LSP is available in the following gateways: G250 G350 G700 G450 G430 Customer benefit: Complete network outage protection 31© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 32. LSP in H.248 Gateways Communication Central Manager Data Applications IP Gateway Phones IP IP Phones Router Analog, DCP Media Phones Gateways Analog Digital/Analog Phones Trunks DCP PSTN Phones Central Location Branch Location 32© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 33. Failover to LSP Communication Central Manager Data H248 Registration Attempts Applications Primary Link Failure 23 IP .3 Gateway H Phones 25 H2 IP IP Phones Router Analog, DCP Media Phones r a re Gateways Be ice Vo Analog Digital/Analog Phones Trunks DCP PSTN Phones Central Location Branch Location 33© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 34. LSP in H.248 Gateways: Transitioning to/from Backup Modes LSP: • Preserves the connection during failover/fallback. • Provides configurable auto fallback to the primary connection • Failover/fallback normally takes ~ 3 minutes • Cannot preserve the connection for: • Calls not in a stable state • Calls using IP or ISDN-BRI trunks, or ISDN stations 34© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 35. Enterprise Survivability 35© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 36. Enterprise Survivable Servers (ESS): Introduction ESS allows backup servers to be placed at various places in a network so that communications can continue in the event that a main server(s) fails, or when connectivity to the main server(s) is lost. ESS: • Can be deployed anywhere in a network • Can be connected to ATM, IP and CSS connected PNs • Provide service to IPSI cards 36© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 37. ESS: IP Connect - Normal Main S8800/S85xx S87xx/S8800 ESS Cluster Gateway 1 LAN or WAN Gateway Gateway 4 2 Gateway 3 LAN or WAN Port Network Control Link VoIP Path 37© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 38. ESS: IP Connect - Server Failure Main S8800/S85xx ESS S87xx/S8800 IPSIs request Cluster backup cluster takeover Gateway 1 LAN or WAN Gateway Gateway 4 2 Gateway 3 LAN or WAN Port Network Control Link VoIP Path 38© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 39. ESS: IP Connect – Network Failure Main S87xx/S8800 IPSIs request backup S8800/S85xx Cluster cluster takeover ESS LAN or WAN Gateway 1 Gateway Gateway 4 2 Gateway 3 LAN or WAN Port Network Control Link VoIP Path 39© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 40. Avaya Aura Solution for Midsize Enterprises How It Works… from… Communication Manager / to… Midsize Enterprise Solution CM Messaging with Avaya Aura™ System Platform technology SIP Enablement Services S8800 or S8510 Application Enablement Services Integrated High Up to 2400 Secure install, Availability Utilities Server (DHCP, HTTPS) users, 250 remote backup, backup locations monitoring upgrades server Media Gateways Simple to add further applications on separate + Survivable Servers (for each app) servers + Embedded Survivable Servers UC Modular Meeting Contact Center 3 Party rd all Inclusive Messaging Exchange Express Applications 40© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 41. Better deployment of existing products What stays the same What is new/different? •Uses Avaya Aura™ Enterprise or •Better, faster to deploy, easier to Standard Edition licenses maintain •Uses the same CM, AES, SES •Lower cost to own and operate applications that you are used to •Supports the same capacities Midsize Business Template Standard Enterprise Edition Edition Avaya Aura™ with System Platform technology 41© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 42. Avaya Aura™ Delivers Benefits for Business of All Sizes • Less costly to buy, 75% less hardware • Lower cost to own 75% less footprint, • Green, energy efficient, 75% less power & cooling • SIP trunking saves 20-50% off telecom expense • Rapid deployment of productivity enhancing UC applications • Differentiated, multi-channel customer service • High Availability , secure remote support option for peace of mind • One server for all core communications • Out-of-the box integration,1-2 hour deployment for entire solution • Faster time-to-value • 75% less time spent maintaining with easy-to-use utilities © 2009 Avaya Inc. All rights reserved. 42 42© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 43. CM5.2 Messaging • Avaya Aura Communication Manager Messaging 5.2 is a powerful embedded addition to the Avaya Aura™ Communication Manager R5.2 delivering voice and text messaging to help improve communications and simplify information exchange between enterprises. With Communication Manager Messaging 5.2, the first 500 mailboxes are provided with each Communication Manager R5.2 and additional mailboxes are available for purchase. Note: With the latest change in pricing first 500 mailboxes are free only with CMEE • Can be used with S8300, S8400 and S8800 simplex servers among the current server offering. • Features:  Multimedia Messaging; Voice, Fax, Text, and other media  Full web administration.  Call answer, Call sending, Call forwarding  INTUITY™ AUDIX® Telephony User Interface (TUI)  35 TUI language packages  Outcalling mobility  Multiple personal greetings  Auto Attendants, Bulletin Board, Broadcast  Standards based; H.323/Q.Sig, SMTP/MIME, IMAP4/POP3, TCP/IP, LDAP, SSH/SSL, and more  Migrations; INTUITY AUDIX R4.4, R5.1, and INTUITY AUDIX R1.1, R2.0© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 44. Subscriber Mailbox Capacity Server Platform CMM Release 5.2 S8510/S8800 Maximum Capacities simplex S8500C S8400x S8300x Subscriber Mailboxes 6,000 5,000 900 450 IP trunk Call Answer Ports 210 80 20 12 IP Trunk Total Ports 250 120 30 18 IMAP4 Sessions 2,000 2,000 300 200 MCAPI (f.k.a. IMAPI) Sessions 128 128 128 128 TTS Sessions 30 30 12 8© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 45. Any questions? Subrat panda Technicenter Team© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 46. Creating Design Solutions for various scenarios in ASD with CM5.2.1© 2009 Avaya Inc. All rights reserved.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA Avaya – Proprietary & Confidential. Under NDA 46
  • 47. Scenario 1 • Customer “XYZ” require a small PBX for two sites, Location A with 200 IP users, Location B with 100 IP users. Both sites will have 6 X 9650 for Top executives, and 1603SW (Cost effective) IP Phones for rest of the employees. • There is also a need for 4 fax/modems on each location. • Customer will need 2 conference phones on each location. • For general usage we will assume 5:1 User to trunks ratio. • Need survivability for remote location© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 48. Solution Designing steps Step-1: Find Total number of users i.e. 200 (IP Phone) + 100 (IP Phone) + 4 x 2 (Fax) + 4 (Conference phone) = 312 Step-2: Find the server which can be provided service to these many endpoints. i.e. S8300, S8800 MBT, S8800 Simplex, or S8800 Duplex servers depending on their capacities. For our scenario it’s S8300 Step-3: Choose the gateway for main and remote locations. i.e. G430, G450, or G650. For our scenario it’s G450 Step-4: Create design in ASD based on the above understanding.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 49. France Germany XYZ Industries S8300D/G450 with Analog cards and DS1 card. WAN 6 X 9650 6 X 9650 8 X 1603 SW 8 X 1603 SW© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 50. Scenario 2 • Customer “XYZ” require a SIP based PBX Solution for two sites, Location A with 300 SIP users, Location B with 200 SIP users. Both sites will have 6 X 9650 SIP Phone for Top executives, and 1603SW-I (Cost effective) SIP phones. • There is also a need for 8 analog ports for fax/modems on each location. • Need mail boxes for all users • For PSTN connectivity we need 4E1 Trunks for main site and 3E1 Trunks for remote location. • Need survivability for remote location© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 51. Scenario 3 • Customer “XYZ” require a IP based PBX Solution for two sites, Location A with 300 IP users, Location B with 200 IP users. Both sites will have 6 X 9650 IP Phone for Top executives, and 1603SW-I (Cost effective) IP phones. • There is also a need for 8 analog ports for fax/modems on each location. • Need mailboxes for all the users • For PSTN connectivity we need 4E1 Trunks for main site and 3E1 Trunks for remote location. • Need survivability for remote location© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 52. Solution Discussion for Scenario 2 & 3 Scenario-2: Total users = 500 SIP + 16 Analog Users. We can take care of this solution with S8800 MBT Platform which can take care of maximum 2400 users (SIP/IP/TDM). As the requirement is for SIP we can go with S8800 MBT for which we would not need additional SES server. G450 for main location and G450 with LSP at remote location. We will provide CMM for messaging. Scenario-3: Total users = 500 IP + 16 Analog Users. We can take care of this solution with S8800 Simplex CM Platform which can take care of maximum 2400 users (IP/TDM). As the requirement is for IP, we can go with S8800 Simplex CM platform. G450 for main location and G450 with LSP at remote location. We will provide CMM for messaging.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 53. Scenario 4 • Customer “XYZ” require a IP based PBX Solution for two sites, Location A with 1500 IP users, Location B with 1000 IP users. Both sites will have 6 X 9650 IP Phone for Top executives, and 1603SW-I (Cost effective) IP phones. • Duplicated servers and duplicated PSU for gateways for increased reliability • There is also a need for 8 analog ports for fax/modems on each location. • For general PSTN connectivity we will need 4 E1 at main site and 3 E1 at remote location. • Need Enterprise wide survivability for entire system when main server is down© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 54. Solution Discussion for Scenario 4 Scenario-4: Total users = 2500 IP + 16 Analog Users. We can take care of this solution with S8800 Duplex CM Platform as it can take care of 18,000 IP/SIP users and 18,000 TDM users. Also, this platform provides us with the server duplication. We also need S8800 Simplex/Duplex on remote location for Enterprise wide survivability aka ESS. We will provide G450 at main site and G450 at remote location.© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 55. Design for workout • Customer “ABC” require a IP based PBX Solution for three sites, Location A with 1200 IP users, Location B with 800 IP users, Location-C with 600 users. each site will have 5 X 9650 IP Phone for Top executives, and 1603SW-I (Cost effective) IP phones. • Duplicated servers and duplicated PSU for gateways for increased reliability • There is also a need for 8 analog ports for fax/modems on each location. • For general PSTN connectivity we will need 4 E1 at main site and 3 E1 on remote locations. • Need Enterprise wide survivable server on Location-B • Need local survivability for Location-C© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA
  • 56. Any questions? Manav Sukhija Design Team© 2009 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA