Guia de Inicio

INTELLIGENT COMMUNICATIONS
5U00041I
Avaya Aura® Communication Manager

Administration
Please note that this course does not have audio. Click the forward/backward arrows to
navigate this course.
© 2012 Avaya, Inc. All rights reserved. Page 1

Module 01
Communication Manager System Overview
ModuleDuration:
Module Duration: 4.5 Hours
© 2012 Avaya, Inc. All rights reserved.
Module 01, Lesson 01
Course Introduction
LessonDuration:
Lesson Duration: 15 Minutes
Welcome to 5U00041I – Avaya Aura® Communication
Manager Administration
 Participants will learn to perform  This course addresses CM releases
Communication Manager (CM) R5.2x through R6.2.
administration tasks. Through lecture  For this course, you need the
and lab work, this entry-level course following materials:
teaches:
– Student Guide
– Basic features and functions
– Lab Workbook
– How to create a dial plan
– How to set up Class of Service and
Class of Restriction
– Endpoint administration
– System maintenance
– System report generation

Course Objectives
Upon completion of this course, you will be able to:
 Define Avaya configuration and solutions with Avaya Aura®.
 Discuss hardware components.
 Describe system duplication and backup options.
 Identify different types of telephones.
 Describe the core boards and media modules.
 Perform basic troubleshooting.
 Produce Communication Manager reports.
 Interpret report data.

Course Objectives (continued)
Use Avaya Site Administration to manage the following:
 Dial plan and feature access codes
 Analog and digital stations
 IP stations
 Call park, bridged call appearance, and other basic features
 Class of Service (COS) and Class of Restriction (COR)
 Abbreviated dialing
 Call forwarding
 Call coverage
 Call pickup and hunt groups
 Trunk groups
 Routing

Course Agenda ‒ Day 1
DAY 1 ACTIVITIES
Module Duration Topics
Module 1 Communication Manager System Overview
2.5 hours  Overview of Communication Manager (CM)
 Hardware overview
 Duplication and survivability
 Interfaces for administration
− Avaya Site Administration – ASA (Lab 1)
− System Management Interface (SMI)
− PuTTY (Lab 2)
 License settings in the Lab
Module 2 Administration
3.5 hours  System Access Terminal (SAT command structure)
 Determine CM software release
 Capacity limits of license
 Authentication, Authorizations, Accounting (AAA) services (Lab 3)

DAY 2 ACTIVITIES
Managing Endpoints
 Overview of endpoints
Module 3
 Dial plan (Lab 4)
1.5 hours
 Adding digital and analog endpoints
 IP telephones (Lab 5)
Basic Features
 Feature access code (FAC) list
 Terminal Translation Initialization (TTI)
 Personal Station Access – PSA (Lab 6 – covers TTI and PSA)
 Copy, Alias, and Duplication (Lab 7)
Module 4  Hold/transfer (Lab 8)
4.5 hours  Conference (Lab 9)
 Class of Service (COS)
 Automatic callback (Lab 10)
 Call forwarding (Lab 11)
 Priority calling (Lab 12)
 Console permissions

DAY 3 ACTIVITIES
Module 4 Basic Features (continued)
1.5 hours  Class of Restriction (COR)
 Calling permissions (Lab 13)
 Service observing (Lab 14)
Module 5 Enhanced Features
2.5 hours  Bridged call appearance (Lab 15)
 Team button (Lab 16)
 Call park
 Hunt group (Lab 17)
 Call coverage (Lab 18)
 Station lock
Module 6 Group Features
1.0 hour  Call pickup
 Abbreviated dialing (Lab 19)

DAY 4 ACTIVITIES
Module 7 Trunk Types
6.0 hours  Trunk groups
 ISDN-PRI (Lab 20)
 Automatic alternate routing (AAR) (Lab 21)
 Automatic route selection (ARS)
 Calling privileges (that is, facility restriction level [FRL])

DAY 5 ACTIVITIES
Module 8 Maintenance/Security Overview
2.5 hours  Backup (CM translations) (Lab 22)
 Alarms and errors
 Reset levels
 Maintenance commands
 Security
Module 09 System Status and Reports
1.5 hours  Real-time monitoring
 Reports

Course Agenda ‒ Day 5(continued)
DAY 5 ACTIVITIES
Appendix A
 Attendant Consoles
Appendix B
 Meet-Me Conferencing (Lab)
Appendix C
 Enterprise Mobility User (EMU) (Lab)
Appendix D
 Extension to Cellular (Lab)
Appendix E
 Country Customization (Lab)

Getting to Know You
Provide your background information:
 Your name
 Where you live
 Your professional background
 Your experiences with other Avaya products
 Your hobbies
 Your expectations from this class

Getting to Know You (continued)
Expectations and ground rules:
 Start/end times
 Breaks/lunch
 Mobile phones
 E-mail
 Teamwork

Overview of Avaya Aura® for Communication Manager
LessonDuration:
Lesson Objectives
Upon completion of this lesson, you will be able to:
 Define the purpose of Avaya Aura®.
 List the core components of Avaya Aura.

Overview – Avaya Aura®
 Avaya Aura is a unified communications solution introduced by Avaya in March
2009.
 The purpose of Avaya Aura is to help reduce the complexity and cost of integrating
and managing devices, systems, applications, and infrastructure from many
vendors.
 Avaya Aura gives business users rapid, easy access to the applications they need,
whatever their location, access device, or type of network.
Architecture
Communication
services
Applications

Avaya Aura® Key Capabilities
Provides user flexibility Single SIP/session-

and choice based infrastructure
Key Capabilities
Centralization of Reduces total cost of

application and services ownership

Avaya Aura® is an Architecture
3-Tier
Integrated stack 2-Tier (Enterprise IMS)
Applications Applications Apps Apps
Connections Connections SIP Presence
Access Connections
H.323 SIP
ISDN and TDM SIP

Access
Access
3-tiered approach delivers flexibility…
ISDN: Integrated Services Digital Network

TDM: Time-Division Multiplexing
SIP: Session Initiation Protocol
Avaya Aura® Streamlines the Architecture
Collaboration
Video applications
Customer Communications
interaction applications
SIP
SOA
SIP
SOA: Service Oriented Architecture

Avaya Aura® is a Suite of Communication Services
Profile-based delivery
Video Sequenced applications
Session management
Bandwidth management
Network normalization
Telephony Centralization Federation
Security
Survivability
Conferencing
Instant messaging
Presence

Avaya Aura® is a Set of Applications
Session Communication Presence Application System Manager

Manager Manager Services Enablement
Services
 Session  Collaboration  Collaboration  Application  Profile-based
management services (video, services integration services
 Bandwidth telephony, (presence, IM, services
management conferencing) federation)
 Network
normalization
Centralization services
Survivability services
Security services
System Platform

Avaya Aura® Communication Manager
Key components of Avaya Aura:
 Organizes and routes voice, data, image, and
video transmissions
 Delivers rich voice and video capabilities
 Provides a distributed network for gateways, analog,
digital, and IP-based communication devices
 Delivers PBX features, high reliability and SERVICES PROVIDED:
scalability, and multi-protocol support  Collaboration
services (video,
telephony,
conferencing)
 Centralization
 Security
 Survivability

Avaya Aura® Communication Manager (continued)
Key features
Robust
set of telephony,
mobility, conferencing,
and contact center
capabilities
Integrated
applications to
support business
collaboration Integrated
support for SIP
environments

Unified Communications ‒ Architecture View
Messaging Conferencing and Collaboration Mobility
Meeting Exchange 1X Clients
Applications and Aura Messaging HMSR2
MAS
services Modular Mess.
Call Pilot MCS 5100
Application and Integration Services Management

Subsystem
ACE AES
TM
System Manager
Core
Voice/Video Teleservice Presence Services UC Manager
communications
CM - FS Presence Server IPTCM
Session Management AIM

Session Manager
Communications Infrastructure – Access Element Data Infrastructure

CM - AE CS1K - AE CS21K - AE VSP 9000 ERS Switches WLAN 8100
Infrastructure
IPO - AE BCM - AE SCS - AE Secure Routers ID Engines UCM
Avaya Clients GWs and SBCs Video Endpoints

9600 1600 1100 G860 Aura SBC MoJo 1X-Comm
Access
1200 MoJo 1x-Com Audio Codes Acme SBC Life Size

Checkpoints
1. The purpose of Avaya Aura® is to:
A. Help reduce the complexity of network devices.
B. Keep network devices separate and independent of each other.
C. Keep the need to have many different vendors.

Checkpoints
2. Which of the following is a core component of Avaya Aura?
A. Fan Modules
B. System Manager
C. Firefox
D. Raid Controller

Hardware ‒ Servers and Gateways
LessonDuration:
Lesson Duration: 1.5 Hours
Lesson Objectives
Upon completion of this lesson, you will be able to:
 Identify the various servers that can support Avaya CM.
 Identify the various gateways that can support Avaya CM.
 Define the gateway protocols.
Resources:
 Hardware Description and Reference.
 System Capacities Table.
Lesson Duration: 1.5 Hours

Servers

Embedded vs. Main Servers
Particulars Embedded (ICC) Main (ECC)
An external server is one on which all
An internal server is one that resides of the server’s hardware components
entirely within a gateway. reside on a single chassis.
Definition An embedded server resides in a A main server resides in an
media module slot on a gateway. Also independent chassis that is separate
called an internal server. from any gateway. Also called an
external server or remote server.
Embedded servers receive electricity
Remote servers do not share hardware
from the gateway’s power supply.
Shared with any other devices.
Embedded servers share hardware
components Main servers do not share hardware
components, such as the power
components with any other devices.
supply, with their host gateways.
The S8400 is inserted into a G650 S8800

Gateway supporting one port network S85xx (migration)
Examples plus five H.248 Gateways. HP DL360
S85xx (migration) make it S8510. Dell R610

Avaya S8300D Server
 Avaya-branded embedded server
 Installs into slot v1 in an H.248 Media
Gateway
 Capacities:
– Processor: Intel 1.06-GHz Core 2 Duo
processor running on a Linux operating system
– Memory:
– 250-GB hard disk
– 8 GB of RAM
– 4-GB internal solid state drive (SSD)
– Connectors:
– Three USB ports
– The USB port supports a readable DVD/CD-ROM
drive used for system installations and upgrades.
– One 10/100 Base-T Services port

Avaya S8800 Server – Legacy Server
 Avaya-branded server
 No longer sold, but used during CM upgrades:
– Quad core Intel I7 “Nehalem” Processor, 2.26 GHz
– 12 GB of DRAM
– Three 146-GB SAS 10K RPM hard disk drives
– Utilizes a RAID 5 disk array
– Total of six Gigabit per second Ethernet NICs: two on motherboard, two on
daughterboard, two on PCI board if needed

S8800 1U Front and Rear Panels
Front
Rear
eth0 Corp.LAN eth1 Services port

S8800 2U Front and Rear Panels
Front
Rear
eth0 Corp.LAN eth1 Services port

For Reference Purposes
 The following servers are no longer sold:
– Avaya S8400 Server
– Avaya S8510 Server
– Avaya S87xx Series
 However, they may be found at customer sites.
 The following slides provide more details about these Avaya
legacy servers.
– Avaya is moving towards the Avaya common server model.
– Avaya-branded servers are being phased out.
– Older legacy Avaya servers still exist in customer sites.

 Embedded, not rack mounted:
– Same form-factor as a TN circuit pack
– Fits into a slot in the G650 Gateway
 No longer sold but may see at customer sites
 Capacities:
– Supports 900 stations
– Supports up to 400 trunks
– Supports a maximum single port network
– Can support up to five additional H.248 Gateways

 Avaya-branded rack-mounted simplex server
 Can run System Platform
 No longer sold, but used during CM upgrades:
– Rack mounted
– Memory: 4 GB, expand to 8 GB for upgrade
– Disks: two 146-GB disks

Avaya S87xx Series Server – Legacy Server
 Legacy server ‒ no longer sold
 May see at customer sites
 Characteristics:
– Operating system:
– Linux
– Processors:
– AMD – S8720/S8730
– Redundant and scalable architecture
– Up to 250 locations per server S8730 Server
– Maximum up to 36,000 stations

Avaya Common Server Models Specs and Configurations
HP ProLiant DL360 G7 Dell PowerEdge R610
Choices Based On Alternatives

Processors Intel Xeon 5600 Series E5620 2.4 GHz, 4-Core
X5670 2.93 GHz, 6-Core for high-
requirement applications
Memory 2 or 4 GB DDR3 RDIMMs @1333 Hz Up to 12 GB per E5620 processor
Up to 24 GB per X5670 processor
Hard drive 146 GB SAS 6 GBPS hard drive 10K RPM or 15K RPM for high-
300 GB 10K for high-requirement applications requirement applications
RAID option HP – P410i RAID Controller w/256 MB cache, battery backup RAID 1 – 2 146 GB drives
Dell – H700 RAID Controller w/512 MB cache, battery backup RAID 5 – 3 146 GB drives
RAID 10 – 4 146 GB drives
Network interfaces 4 integrated ENET Gigabit NIC ports Standard
PCI interfaces HP – 2 PCI-E 2 expansion slots Standard
Dell – 2 PCI-E risers for Gen 2 slots
Power supply HP – 460 W AC HP – 750 W AC, 1200 W DC
Dell – 502 W AC Dell – 717 W AC with X5670
USB HP – 1 front, 2 back, 1 internal Standard
Dell – 2 front, 2 back, 1 internal

HP DL360G7 Server
Front
Rear
eth0 Corp. LAN eth1 Services port

Dell R610 Server Front and Rear View
eth0 Corp. LAN eth1 Services port

Gateways

Gateway Overview
Gateways are grouped based on their functionality as:
 H.248 Gateways
 Port networks (cabinet)
 SIP gateways
Avaya utilizes specific protocols that are based on the
gateway configuration:
 Time Division Multiplexing (TDM)
– Analog protocol
– Avaya proprietary Digital Communications Protocol (DCP)
 Transmission Control Protocol/Internet Protocol (TCP/IP)
 Session Initiation Protocol (SIP)
Note
A port petwork is a logical/physical arrangement of
cabinets containing telephony switching components.

G430 Interfaces
 2 Fast Ethernet LAN interface
 1 Fast Ethernet WAN interface
 Contact closure adjunct
 ETR (emergency transfer relay) capability performed by MM714B (detailed later)
 Service port
 2 USB ports (for modem and DOK [direct option keyboard])
 Compact Flash slot
 MOH (music on hold) jack

G430
 The G430 Gateway supports three MM slots
 Each EM200 supports two MM slots
 Can host S8300D, embedded and LSP modes, using Slot V1 only
 Modular resources:
– RAM and Compact Flash to support future needs and application
– Onboard 20 channels and one slot for DSP daughterboard
 Expansion modules (up to two) allow for scalability using existing gateway media
modules:
– 1.5U chassis, 19” rack, desktop or wall-mount
G430 and EM200, back view

G450
 Eight media module slots
 DSP channels: 20/80 on daughterboard scale to 320
 Dynamic call admission control
 Power supplies: 2
 Enhanced security support (that is, VPN, SSH/SCP, and so on)
 Interoperable with other Avaya media gateways
 Main headquarters location
 Mid-size to large branch office
with MB

G650 Overview
 Mounted in a 19-inch rack, 8U height G650 Media Gateway
 14 slots for TN circuit packs
 Important circuit packs:
– TN2312BP IP Server Interface
– TN799DP Control LAN (C-LAN) Interface
– TN2302AP IP Media Processor, or
– TN2602AP IP Media Resource 320
 Optional circuit packs:
– Trunks: T1/E1, analog, E&M (ear/mouth)
– Lines: digital, analog
– Announcement
 Supports AC/DC power
 Optional redundant power supply
(sharing the power load)
Inside view

G650 Port Network
 The architectures for the S8800, HP DL360, and
Dell R610 Servers can be configured to support a
port network (PN) through the G650 Gateway.
 A PN uses combinations of G650* gateways to provide
physical ports and interfaces for handling calls.
 A port network can be one of the following:
– One single-carrier G650 Gateway
– A stack of single-carrier G650 Gateways that are connected
with a TDM bus cable and share connections to the server
or port circuit packs
Note
A PN with multiple G650s must use a stack configuration.

G650 Connections
 Connectivity between G650s:
– A maximum of five G650s can be stacked per
port network. E
– TDM/LAN cable is required to connect
multiple G650s.
– Carrier addresses from A to E. D
 Connectivity between PNs:
– IP-PNC
TN2302AP or TN2602AP (required) C
 G650 connects the server and the PN:
– Control network between PNs and server
B
– Optional duplicated control network
– Duplicated TN2312BP IPSIs
– One in Carrier A, another in Carrier B A

G860 SIP Gateway Overview
 The G860 SIP Gateway is a high-channel-density, standards-compliant, VoIP
media gateway.
 High-density interfaces–DS3, OC3, STM-1.
 Small footprint (5U) and lower cost:
– Reduction of carrier access charges.
– Lower costs associated with acquiring and maintaining data center floor space.
– Operational and maintenance cost savings by eliminating a large number of G650
Gateways (less power, UPS, cooling requirement).

G860 SIP Gateway Overview (continued)
 SIP connectivity to Avaya Communication Manager
 Carrier-grade reliability
 Works with the S8710/S8720/S8730/S8800 Servers
 Works in conjunction with G650s and B5800
 Targeted to large IP-based contact centers and campuses
 Installed and supported by Avaya Global Services

B5800 Branch Gateway
 Single-platform solution for the “collaborative branch”
 Based on the IP Office architecture
 Deployment model:
– Distributed – Call processing provided locally

TNxxxx Circuit Packs
 Circuit packs contain solid-state circuits
mounted on printed wiring boards and are
approximately 20 cm (8 in.) by 33 cm (13 in.).
They have connectors attached at one end to
tie the circuit packs to the gateway backplane.
 TNxxxx circuit packs can be installed only
in gateways that are components of a
port network (G650 Gateway).
 The circuit pack faceplate has:
– A metal latch for electrostatic discharge
(ESD) protection
– A label displaying the type and vintage
– LEDs that indicate status
– A barcode identifying the comcode of the circuit pack

TNxxxx Circuit Pack LEDs
LEDs on the circuit pack faceplate indicate the following
conditions:
 Red – Alarm
A failure has been detected on the pack.
 Green – Test
The system is running a test on the pack.
 Amber – Busy
The circuit pack is in use; removal will cause
service interruption.

Types of TN Circuit Packs
Port circuit packs:
 The port circuit packs provide links between analog lines, digital
lines, trunks, external communications devices, and the TDM bus
and the packet bus.
 You can install these circuit packs in any universal slots.
 Examples: TN2464CP DS1 interface
TN2214CP DCP digital line
Service circuit packs:

 Service circuit packs provide tone production and detection, call
classification, recorded announcements, and speech synthesis.
 You can install these circuit packs in any universal slots.
 Examples: TN2501AP voice announcements over LAN (VAL)
TN2602AP IP media resource 320

Types of TN Circuit Packs (continued)
Interface circuit packs:
 Enable the server to communicate with the media gateways
 Connect two or more media gateways together
 Connect port networks together by way of switch nodes
You must install the interface circuit packs in dedicated slots.
Example:
 TN2312BP IP server interface (slot 1 only)

Media Modules
 Media modules can be installed only in H.248 Gateways.
– Similar in functionality to TNxxxx circuit packs.
Although some media modules contain additional LEDs, each media module faceplate
has a standard pattern of three LEDs that indicate the following conditions:
 ALM: Red indicates a fault condition. This LED is also on when the media module
is physically inserted, and should turn off when the board initializes.
 TST: Green indicates a test condition.
 ACT: Amber indicates an in-use condition.
 The T1/E1 media module (MM710) has an additional LED:
– SIG: Indicates the MM710 is receiving a valid signal.
MM710

Checkpoints
1. Avaya offers (at least) ______ servers that can support the
CM 6.x.
A. 9
B. 4
C. 5
D. 12

Checkpoints
2. Only the G430 Gateway can support CM 6.x.
A. True
B. False

Checkpoints
3. ________ is the gateway protocol (H.248) used by CM 6.x.
A. POP3
B. SMTP
C. DCP
D. NNTP

Duplication, Failover, Availability, and Survivability
LessonDuration:
Lesson Objectives
Upon successful completion of this lesson, you will be able to:
 Describe Survivable Remote Server.
 Define the purpose of Standard Local Survivability (SLS).
 Identify the System Platform survivability.
Resources:
 Avaya Aura® Communication Manager Survivability Options

Definitions
 Duplication – System design and configuration that uses
redundant standby equipment that is ready to take over call
processing in the event of equipment or network failures.
– Avaya legacy systems: Redundant equipment, connections, and
networks for standard, high, and critical reliability configurations.
– Prior to 6.0: Redundant equipment, connections, and networks for
standard, high, and critical reliability configurations.
– Release 6.0+: High Availability option in System Platform plus
supported Solution Template configurations.

Definitions (continued)
 Failover – Events that cause loss of call processing
(server failure) or inability of system components to
communicate with the call processing server, resulting
in the standby hardware or software assuming the call
processing functions.
– Conditions for failover differ for Release 6.0 compared to
earlier releases.
– Redundant equipment takeover timelines are different for
Release 6.0 compared to earlier releases.
 Availability – The percentage of time the system is
available for use (minutes down/year divided by total
minutes in a year).
– “Five 9s” = 99.999% reliable means that the system is
down no more than 0.001% of the time.
– “Four 9s” = 99.99% or 99.95 reliable means that the
system is down no more than 0.01% or 0.05% of the time.

Definitions (continued)
 Survivability – Business continuity through
unscheduled outages (for example, network failure,
congestion) as well as scheduled outages, such as
server upgrade.
 Standard Local Survivability (SLS) – Software
resident in H.248 Gateways that provides call
processing to the gateway when the connection to its
designated Communication Manager server is down.
– Supported gateways: G430 and G450
– Administered at the gateway and not in Communication
Manager

Survivability – ESS*
 ESS is a backup server that is strategically located at
various places in the network so that communications
can resume in the event that the main server fails.
 Release 6.0 equivalent is the Survivable Core (SC) ESS
configuration:
– Formerly known as ESS (and some larger LSP
configurations)
– S8800 (simplex and duplex) only
*ESS = Enterprise Survivable Server.

Survivability – LSP*
 Release 6.0 equivalent is the Survivable
Remote (SR) configuration that requires
different hardware depending on the number
of endpoints:
– Provides redundancy to H.248 Gateway only
– S8300D for small remote branches
– S8800 (simplex) for large remote branches
*LSP = Local Survivable Processor.

Survivability – SLS
 SLS is software resident in H.248 Gateways
that provides call processing to the gateway
when the connection to its designated
Communication Manager server is down.
 This engine is resident in the H.248 Gateway
firmware.
 Provides basic telephony functions at the
branch location without being
registered to Avaya Communication Manager.
 Supported gateways:
– G430
– G450
*SLS = Standard Local Survivability

CM – Feature Server and Evolution Server
 Communication Manager is deployed in two modes:
– Feature Server (CM-FS): supports SIP-only endpoints deployment.
– Evolution Server (CM-ES): supports non-SIP endpoints (analog, DCP, and/or H.323)
and can also support SIP endpoints.
 Simple to administer – a single field in the configuration of the SIP trunk between
Communication Manager and Aura® Session Manager (ASM) determines CM-FS
versus CM-ES.
Session Manager Communication Manager

Gateway
DCP phone Analog phone

SIP phone
SIP phone SIP phone
CM as an Evolution Server
 Evolution server – supports both SIP and non-SIP endpoints:
– H.323/digital/analog endpoints register with Communication Manager.
– SIP endpoints register with Session Manager.
– All endpoints receive feature service from Communication Manager.
– Supports all current Communication Manager gateways and port networks.
Media
System Manager
gateway
Session Manager
Communication Manager
SIP phone SIP phone SIP phone

CM as a Feature Server
 Feature Server – supports only SIP endpoints:
– SIP endpoints register with Session Manager.
– Session Manager forwards SIP requests to CM which then invokes features.
System Manager
Session Manager Switch
Communication Manager
SIP phone SIP phone SIP phone

Avaya Aura® System Platform and Solution Templates
 Every release of Communication Manager 6.0+ is on the Avaya Aura System
Platform.
 System Platform is a virtualization layer that allows several applications to run on
the same server.
 Applications that run on System Platform are called “virtual machines.”
 A Solution Template is a define set of virtual machines running on System
Platform.
Solution
Template
Aura
Aura Applications
Applications
System Platform

Avaya Aura® System Platform and Solution Templates
(continued)
 Avaya Aura Communication Manager Solution Templates (Release 6.0)
 Avaya Aura CM Main for Survivable Core (duplex)
 Avaya Aura CM Main for Survivable Core (simplex)
 Avaya Aura for Survivable Remote (simplex)
 Avaya Aura for Survivable Remote Embedded
 Avaya Aura CM Main Embedded
Solution
Template
Aura
Aura Applications
Applications
System Platform

Avaya Aura® Solution Templates – R6.0
Avaya Aura CM Avaya Aura CM Avaya Aura for Avaya Aura for Avaya Aura CM
Main/Avaya Main/Avaya Survivable Remote Survivable Remote Main
Aura for Aura for Embedded version
Simplex version Embedded version
Survivable Core Survivable Core
Duplex version Simplex version
Template CM_Duplex CM_Simplex CM_SurvRemote CM_SurvRemoteEmbed CM_onlyEmbed

name
Domain Hypervisor Hypervisor Hypervisor (Dom0) Hypervisor (Dom0) Hypervisor (Dom0)

0/1 (Dom0) (Dom0) CDOM (Dom1): SAL CDOM (Dom1): SAL CDOM (Dom1):
CDOM (Dom1): CDOM (Dom1): SAL
SAL SAL
Dom 2 CM 6.0 Utility Services Utility Services Utility Services Utility Services
Dom 3 CM/CMM 6.0 CM 6.0 CM 6.0 CM/CMM 6.0
Dom 4 Session Manager Session Manager 6.0 for

6.0 for Survivable Survivable Remote
Remote
HW 2 - S8800 S8510* S8510* S8300D S8300D
HP DL360 S8800 S8800 HP DL360 HP DL360
Dell R610 HP DL360 HP DL360 Dell R610 Dell R610
Dell R610 Dell R610
*Memory and hard disk drive upgrade required.

Avaya Aura® Communication Manager Templates CM R6.2
New for 6.2
Avaya Aura CM Avaya Aura Avaya Aura for Avaya Aura for Avaya Aura CM Main Utility Services
Main/Avaya CM Main/ Survivable Survivable Remote Embedded version Standalone
Aura for Avaya Aura for Remote Embedded version+ *Support for Duplex
Survivable Survivable CM (6.2)
Simplex version#
Core Core
Duplex version Simplex
version
Template
Name CM_Duplex CM_Simplex CM_SurvRemote CM_SurvRemote CM_onlyEmbed “US_Simplex”
Embed
Domain Hypervisor (Dom0) Hypervisor (Dom0) Hypervisor (Dom0) Hypervisor (Dom0) Hypervisor (Dom0) Hypervisor (Dom0)
0/1 CDOM (Dom1): CDOM (Dom1): CDOM (Dom1): SAL CDOM (Dom1): SAL CDOM (Dom1): SAL CDOM (Dom1): SAL
SAL SAL
Dom 2 CM 6.x Utility Services Utility Services Utility Services Utility Services Utility Services
Dom 3 CM/CMM 6.x CM 6.x CM 6.x CM/CMM 6.x
Dom 4 Session Manager 6.x Session Manager 6.x for

for Survivable Remote Survivable Remote
HW 2 - HP DL360G7 HP DL360G7 HP DL360G7 S8300D S8300D HP DL360G7

2 - Dell R610 Dell R610 Dell R610 Dell R610
2 - S8800 S8510 ** or S8800 S8510 ** or S8800 or S8800
#Emulates “ESS-like” or “LSP-like” functionality.

+Emulates “LSP-like” functionality.
*Appropriate engineering consultation required for high-capacity configurations.

**Memory (8 GB) and hard disk drive upgrade required.
Avaya Aura® Solution Templates (continued)
 Supported servers: S8300D, S8510D*, S8800, HP DL360, and Dell R610.
 Virtual machines (application bundle) vary by template.
 Survivable Remote templates provide ESS and LSP equivalent functionality.
 Embedded templates are installed only on S8300D Servers.
 Dom0 is the System Platform domain; cdom is the System Platform management
console.
 Utility Server, and Branch Session Manager in some templates.
 Communication Manager Messaging (CMM) not available in all templates.
 Secure Access Link (SAL) for remote access and alarming in all templates.
 Avaya Aura Session Manager required whenever SIP endpoints are used.
Note
S8510 with memory and HDD upgrades.

Avaya Aura® Business Continuity – Levels of Redundancy
Avaya Aura for Survivable Core – PSTN Avaya Aura for Survivable Core –
Duplex (CM as Feature Server) Duplex (CM as Feature Server)
1 2
Session Manager 6.0 3 Session Manager 6.0

System Manager R6
Data Center 1 Data Center 2
4
SM/CM on System Platform
5 5
Avaya Aura® for

AudioCodes (Thin
Survivable Remote
Survivable Branch)
Location 1: Location 2:
Non-critical remote site, basic Critical remote site, requires full feature
survivability during WAN outage survivability in case of WAN outage
Levels of redundancy
SIP Remote Office Survivability
Communication Manager Feature Server
SIP ISC SIP ISC

Avaya Aura®for Survivable
Remote (Simplex) Core Avaya Aura for Survivable
SM
SM Remote (Embedded)
SM
Secondary, SIP SIP

rainy day Primary Secondary,
SIP Primary
service rainy day SIP
service
100% SIP endpoints utilize

CM Feature Server.

SIP Remote Office Survivability (continued)
 SIP Survivability: System Platform with Branch Session Manager and
Communication Manager Feature Server on either a simplex S8800, or an
upgraded S8510, or the embedded S8300D server.
 96xx SIP phones register to (1) the main Session Manager, (2) a backup main
Session Manager, (3) and the Local Branch Session Manager. On a WAN outage,
the local Session Manager and Communication Manager Feature Server take
over.
 Media services are provided by the local H.248 Gateway during both sunny day
and rainy day scenarios.

System Platform ‒ High Availability
Public network
Network switch Public network connection
SP node 1 SP node 2
(active) (standby)
Heartbeat pings
Domain0s are
synchronized from
active to standby
node in real time. Dom0 Dom0
Utility Svcs Private crossover Utility Svcs

CM
network CM
connection
AES AES
Session Mgr Session Mgr
Sync of virtual machines
HDD HDD

System Platform ‒ High Availability (continued)
 The Communication Manager duplex Solution Template includes:
– High Availability (HA) option
– Active/standby configuration (two physical servers) for hardware redundancy.
 This is a System Platform capability:
– It is not Communication Manager duplication.
– Release 6.0 Solution Templates emulate ESS and LSP functionality.
– System Platform HA monitors heartbeat pings, not state of health as in earlier releases.
 Memory is not shadowed.
Duplex
Solution High Active/
Template Availability standby

System Platform ‒ High Availability (continued)
 Active/standby mechanism is transparent to external
applications:
– “One active node only" approach‒does not permit some
resources to run on one node and some on another.
– Configuration is restored at the last synchronization point.
 At failover, the standby server must boot up, which takes 3
to 5 minutes, depending on the Solution Template installed.

Interfaces for CM Administration
LessonDuration:
Lesson Objectives
 Define the interfaces that can be used to access Avaya servers
and gateways.
 Describe the interface that should be used to administer IPSI,
C-LAN, and Media Processor/Resource circuit packs.
Resources:
 Administering Avaya Aura® Communication Manager
 Hardware Description and Reference

Access Avaya Servers
There are several connection types and access tools used to “talk with” the servers:
 Connection types:
– Direct connection from laptop to server
– Over the customer network:
– Any computer connected through the LAN will be able to access the server. Use the
CM IP address to access the server.
Customer network

Access Avaya Servers (continued)
 Access tools:
– Avaya Site Administration (ASA)
Provides a comprehensive graphical user interface tool that is ASA
installed on a Microsoft Windows client PC. It helps simplify the
day-to-day administration and maintenance tasks of Avaya servers
and Avaya messaging platforms.
– System Management Interface (SMI)
Configures server-specific parameters such as IP address, subnet,
and backup/restore user translation data. SMI
– SSH client, such as PuTTY and TELNET
SSH
client

Direct Connection IP Address Assignment
 Server 192.11.13.6
255.255.255.252
 Service PC 192.11.13.5
255.255.255.252
Services port
on S8300D

Direct Connection S8300D and S8510 Servers
S8300D
S8510

Direct Connection S8800 – 1U Server
S8800 1U
S8800 2U

Direct Connection HP and Dell Servers
HP DL360
Dell R610

Access H.248 Gateways
 Access the Avaya H.248 Gateways using the CLI, the IW, the GIW, the PIM.
– Configure all interfaces and assign parameters to interfaces:
– Interfaces such as the VLAN and Fast Ethernet interfaces
– Parameters such as IP address and port number
 Access H.248 Gateway over the customer network.
– Access the gateway from any computer connected through the LAN.
– To access either gateway, use the IP address of any gateway interface for the host
address by using SSH, PuTTY, or Telnet.
CLI = Command Line Interface IW = Installation Wizard

GIW = Gateway Installation Wizard PIM = Provisioning and Installation Manager

Access H.248 Gateways (continued)
 The G450 provides Console port and a Services port.
G450
 The G430 provides only a Services port (no Console port available).
G430

IP Interface Circuit Packs Gateway G650
 TN2312BP IP Server Interface IPSI
– Assign IP addresses and other parameters to the IPSI circuit packs using SSH, PuTTY,
or Telnet.
 C-LAN TN799DP
IP MP/MR TN2302AP/TN2602AP
– Assign IP addresses and other parameters using ASA.
Control network
Medpro
C-LAN
IPSI
Checkpoints
1. Which of the following tools is NOT used to access an
Avaya server?
A. SSH
B. DHCP
C. SMI
D. ASA

Checkpoints
2. In a G650, which of the following interfaces can be used to
administer the IPSI?
A. SIP
B. TCP/IP
C. FTP
D. PuTTY

Lesson 01, Lesson 06
Avaya Site Administration (ASA)
LessonDuration:
Lesson Objectives
 Distinguish the difference between GEDI (Graphically Enhanced
DEFINITY Interface) and terminal emulation.
 Connect to S8300D and S8800 along with HP DL360 and Dell
R610 Servers using Avaya Site Administration (ASA).
 Create a voice system in Avaya Site Administration.
Lesson Duration: 45 minutes

Overview – Avaya Site Administration (ASA)
 PC-based tool (application) that runs on Windows 2000,
XP, Windows 2003 Server, Windows Vista, and Windows
7 to administer CM.
 To run Avaya Site Administration, your computer must
meet the following requirements:
– 1.2 GHz Pentium IV
– 512 MB of RAM
– 1 GB hard disk space
 Avaya Site Administration provides graphical station and
system administration screens and easy-to-use wizards for
basic administration tasks.
 Additionally, ASA provides terminal emulation and GEDI
for access to Communication Manager for other
administrative operations.

ASA Features
 Administration wizards including add/change/remove
user and change user extension
 Ability to use templates for adding new objects
 Native name entry for station, hunt group, trunk group,
and VDN objects
 Import/export of admin fields for select objects
 Report generation
 Ability to schedule tasks to run at a later time
 Button label printing
 Basic fault and performance capabilities
 Secure connection to voice and messaging systems
through SSH

Logging In to CM With ASA

ASA Application
Download the application from: http://www.support.avaya.com.

User Interface
Menu and toolbar
View tabs
Dialog area
Status/history window

Add a Voice System Name
Note
The first time you sign in, a voice system needs to be created.
Add a Voice System Network Connection
IP address of Services port

or
IP address of the server (CM)

Add a Voice System SSH or TCP/IP
Connect CM SAT with SSH

(default setting).
OR
Clear the Use SSH check box and
enter a TCP/IP port number if you
want to connect with Telnet.

Add a Voice System Login
OR

Add a Voice System Login (continued)
OR
Log in automatically.
Log in manually each time.
For class – we will

use manual.

Add a Voice System Summary
Summary
Only shown when

1 “Log in manually”
Is selected. 2

CM Login ‒ Using GEDI

Log In to CM using GEDI Primary Screen
Gray
background
with GEDI

Successful Login with GEDI
Connection status

Successful Login with GEDI (continued)
Example if you have

an invalid license or
a license that will
expire shortly.

End GEDI
Log off

CM Login ‒ Using the Terminal Emulator

Log In to CM Terminal Emulator
3
1 Only shown when
“Log in manually”
2 is selected.

Log In to CM Terminal Emulator (continued)
Blue
background
enter with terminal
emulation

Terminal Emulator Primary Screen

Log Out of CM Terminal Emulator
Logoff

Checkpoints
1. To distinguish that you are in terminal emulation, the
background is _________ ?
A. White
B. Gray
C. Blue
D. Green

Checkpoints
2. ASA is a _________ tool that enables administration of the
Communication Manager system.
A. PC-based
B. Modem-based
C. Gateway-based
D. Server-based

Checkpoints
3. You can only create one voice system.
A. True
B. False

Lab 1
Avaya Site Administration (ASA)

System Management Interface (SMI)
LessonDuration:
Lesson Objectives
 Connect to a S8300D, S8510, S8800, HP DL360, or Dell R610
Server using System Management Interface (SMI).
 Describe the functions that can be performed using SMI.
 Differentiate between using ASA and SMI.
Resources:
 Administering Avaya Aura® Communication Manager
 Hardware Description and Reference

Overview – System Management Interface (SMI)
 SMI is a browser-based server administration and maintenance tool for
Communication Manager:
– Easy-to-use graphical user interface (GUI)
– Server administration and maintenance tasks
 Supported browsers: Microsoft Internet Explorer, Netscape, and Firefox
 Functions:
– Back up and restore user translation data, server system data, and security data.
– Check server state of health and process status.

Overview – System Management Interface (SMI) (continued)
 Functions:
– Server-specific configurations such as subnets, routing.
– Upgrade software (the upgrade of CM software is applicable only to CM5.2 and below).
– Perform routine diagnostics and troubleshooting, run tests if needed, and view alarms
and system logs (also available in System Platform.
– Wizards for installation and administration.

Access Server System Management Interface (SMI)
Firefox example
Internet Explorer
example

Access Server SMI – Login
1 3
1 = Opening page – select Continue.
2 = Login (craft/crftpw).
3 = Suppress Alarm (yes).

SMI Server Maintenance
1 = Main page
2 = Drop-down menu

SMI Server Administration Primary Screen
M
E
N
U

SMI Server Administration Primary Screen (continued)
M
E
N
U

SMI Server Role ‒ Example

SMI Logoff
Make sure that you log off of SMI completely so that you do not keep the session open.

Checkpoints
1. SMI is used to access CM in which of the following hardware?
A. Gateways
B. Servers
C. Routers
D. Switch

Checkpoints
2. ASA and SMI are accessed in the same manner.
A. True
B. False

Checkpoints
3. SMI can be used for data backups.
A. True
B. False

Alternative Access Tools (PuTTY and Telnet)
LessonDuration:
Lesson Objectives
 Connect to the Avaya servers using the PuTTY tool or a Telnet
session to administer CM.
 Perform SAT commands using PuTTY (or Telnet).

Log In to Linux Server with SSH Client PuTTY
Download application from: http://www.support.avaya.com.

PuTTY Host Name
 Host name or IP
 SSH
SSH = Secure Shell

PuTTY Login
Note
Working with the shell requires knowledge of Linux.

Definity Help: dhelp
 "Definity Help"
Avaya-specific commands within the Linux bash (shell)

Access CM SAT from Linux
R016x.-2.0.818.0

Access CM SAT from Linux (continued)

Access CM SAT from Linux Using Terminal Type SUNT

Log Off
"Fallback" to Linux level
Step 1 = logoff
Step 2 = exit

Lab 2
PuTTY Application

CM Login – Using Telnet

Telnet Login to a Linux Server
 Start the DOS prompt.
 Enter the command telnet 192.11.13.6 through the Services port.
Note
Logging in to the Linux Server with Telnet is possible only when
Telnet port 23 on the Avaya Server is activated (default: deactivated).
Directly Access CM SAT from Telnet Command
Note
Logging in to Communication Manager with Telnet is possible only when
SAT Telnet port 5023 on the Avaya Server is activated (default: deactivated).
Checkpoints
1. PuTTY is launched from the ______________.
A. Desktop
B. ASA
C. GEDI
D. Terminal emulator

Checkpoints
2. In the lesson, when accessing PuTTY, the port used for SSH is?
A. 5035
B. 5027
C. 5022
D. 5013

Lab Environment License Settings
LessonDuration:
Lesson Objectives
 Confirm what license features are enabled in CM for the
training (lab) environment.
 Describe the differences between the training environment and
the customer environment.

Purchased CM Features
 System-parameters customer-options
– This screen shows you which optional features are enabled for your system, as
determined by the installed license file.
– The fields on this screen are populated by the license file, and are display only.
– A license file is an encrypted file that you use to activate software features such as
capacities, release, and offer categories.
– Purchased features should be displayed with yes (y).
– The fields on this screen cannot be changed by any users.
 If you have any questions about disabling or enabling one of these features,
contact your Avaya representative.
Display system-parameters customer-options

Settings for the Lab Environment
Display system-parameters customer-options

Settings for the Lab Environment (continued)





Checkpoints
1. Which of the following commands are used to verify the current
license settings in the lab environment?
A. Change station xxxx
B. Change COS group
C. Display system-parameters customer-options
D. Change system-parameters features

Checkpoints
2. The lab environment and the customer environment will have
the same license settings.
A. True
B. False

Guia de Inicio

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Guia de Inicio

Caricato da

Copyright:

Formati disponibili

INTELLIGENT COMMUNICATIONS

Avaya Aura® Communication Manager

© 2012 Avaya, Inc. All rights reserved. Page 1

Communication Manager System Overview

© 2012 Avaya, Inc. All rights reserved. Page 4

© 2012 Avaya, Inc. All rights reserved. Page 5

© 2012 Avaya, Inc. All rights reserved. Page 6

© 2012 Avaya, Inc. All rights reserved. Page 7

© 2012 Avaya, Inc. All rights reserved. Page 8

© 2012 Avaya, Inc. All rights reserved. Page 9

© 2012 Avaya, Inc. All rights reserved. Page 10

© 2012 Avaya, Inc. All rights reserved. Page 11

© 2012 Avaya, Inc. All rights reserved. Page 12

© 2012 Avaya, Inc. All rights reserved. Page 13

© 2012 Avaya, Inc. All rights reserved. Page 14

Overview of Avaya Aura® for Communication Manager

Lesson Duration: 15 Minutes

© 2012 Avaya, Inc. All rights reserved. Page 17

Provides user flexibility Single SIP/session-

Centralization of Reduces total cost of

© 2012 Avaya, Inc. All rights reserved. Page 18

Applications Applications Apps Apps

Connections Connections SIP Presence

ISDN and TDM SIP

3-tiered approach delivers flexibility…

ISDN: Integrated Services Digital Network

SOA: Service Oriented Architecture

© 2012 Avaya, Inc. All rights reserved. Page 20

© 2012 Avaya, Inc. All rights reserved. Page 21

Session Communication Presence Application System Manager

© 2012 Avaya, Inc. All rights reserved. Page 22

© 2012 Avaya, Inc. All rights reserved. Page 23

© 2012 Avaya, Inc. All rights reserved. Page 24

Application and Integration Services Management

Session Management AIM

Communications Infrastructure – Access Element Data Infrastructure

Avaya Clients GWs and SBCs Video Endpoints

© 2012 Avaya, Inc. All rights reserved. Page 25

© 2012 Avaya, Inc. All rights reserved. Page 26

© 2012 Avaya, Inc. All rights reserved. Page 27

Hardware ‒ Servers and Gateways

Lesson Duration: 1.5 Hours

© 2012 Avaya, Inc. All rights reserved.

The S8400 is inserted into a G650 S8800

© 2012 Avaya, Inc. All rights reserved. Page 31

© 2012 Avaya, Inc. All rights reserved. Page 32

© 2012 Avaya, Inc. All rights reserved. Page 33

eth0 Corp.LAN eth1 Services port

© 2012 Avaya, Inc. All rights reserved. Page 34

eth0 Corp.LAN eth1 Services port

© 2012 Avaya, Inc. All rights reserved. Page 35

© 2012 Avaya, Inc. All rights reserved. Page 36

© 2012 Avaya, Inc. All rights reserved. Page 37

© 2012 Avaya, Inc. All rights reserved. Page 38

© 2012 Avaya, Inc. All rights reserved. Page 39

Choices Based On Alternatives

© 2012 Avaya, Inc. All rights reserved. Page 40

eth0 Corp. LAN eth1 Services port

© 2012 Avaya, Inc. All rights reserved. Page 41

eth0 Corp. LAN eth1 Services port

© 2012 Avaya, Inc. All rights reserved. Page 42

© 2012 Avaya, Inc. All rights reserved.

© 2012 Avaya, Inc. All rights reserved. Page 44