Page 3 - Section 1: Avaya Application Solutions; Contents
Issue 6 January 2008 3 About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Using this b...
Page 6 - Security
6 Avaya Application Solutions IP Telephony Deployment Guide Section 2: Deploying IP Telephony . . . . . . . . . . . . . . . . . . 175 Traffic engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 10 - Index
10 Avaya Application Solutions IP Telephony Deployment Guide Network recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Change control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Layer 2 mechanisms to increase reliability . . . . . . . . . . . . ...
Page 11 - About This Book; Overview; Audience
Issue 6 January 2008 11 About This Book Overview This book, Avaya Application Solutions IP Telephony Deployment Guide , 555-245-600, describes Avaya’s Application Solutions product line, IP Telephony product deployment, and network requirements for integrating IP Telephony products with an IP networ...
Page 12 - Downloading this book and updates from the Web; Go
About This Book 12 Avaya Application Solutions IP Telephony Deployment Guide ● Call processing features ● LAN switching products Section II - Deploying IP Telephony. Use this section to learn about deployment issues including: ● Traffic engineering ● Security ● Voice quality issues ● Network managem...
Page 13 - Related resources; Within the US; Title
Related resources Issue 6 January 2008 13 Related resources For more information on Avaya IP Telephony products, see the following documentation libraries and CDs: Technical assistance Avaya provides the following resources for technical assistance. Within the US For help with: ● Feature administrat...
Page 14 - Trademarks
About This Book 14 Avaya Application Solutions IP Telephony Deployment Guide Trademarks All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. Sending us comments Avaya welcomes yo...
Page 17 - Avaya Application Solutions; Figure 1: Avaya Application Solutions
Issue 6 January 2008 17 Avaya Application Solutions This chapter contains general discussions of the Avaya Application Solutions product line: ● Avaya Communication Manager ● Avaya servers ● Avaya DEFINITY Servers ● Avaya Media Gateways ● Avaya Integrated Management ● Avaya Communication Manager app...
Page 18 - Figure 2: Communication Manager traffic flow
Avaya Application Solutions 18 Avaya Application Solutions IP Telephony Deployment Guide Figure 2: Communication Manager traffic flow Figure notes: 1. SIP phones exchange RTP audio among themselves and with the G700, G650 Media Gateways, and so forth, but not with IP phones. 2. SIP signaling from Av...
Page 19 - Avaya Communication Manager; Avaya servers; Avaya DEFINITY Servers
Avaya Communication Manager Issue 6 January 2008 19 Avaya Media Gateways support voice traffic and signaling traffic that is routed between circuit-switched networks and packet-switched networks. The Gateways support all the applications and adjuncts that can be used with the Avaya DEFINITY Enterpri...
Page 20 - Avaya Media Gateways; Avaya Integrated Management
Avaya Application Solutions 20 Avaya Application Solutions IP Telephony Deployment Guide ● Avaya DEFINITY Server R ● Avaya DEFINITY Server SI ● Avaya DEFINITY Server CSI These servers run on the Oryx/Pecos proprietary operating system, and function in the same way as the servers in Figure 2: Communi...
Page 21 - Avaya communication devices; Avaya Communication Manager applications
Avaya Communication Manager Issue 6 January 2008 21 The Integrated Management applications include the tools that enable you to ● configure, monitor, and optimize the performance of Avaya servers, gateways and ● endpoints ● monitor voice over IP traffic ● manage Quality of Service (QoS) policies ● c...
Page 22 - Avaya SIP solutions
Avaya Application Solutions 22 Avaya Application Solutions IP Telephony Deployment Guide Avaya SIP solutions Session Initiation Protocol (SIP) is an endpoint-oriented messaging standard defined by the Internet Engineering Task Force (IETF). SIP is a text-based protocol, similar to HTTP and SMTP, for...
Page 23 - Avaya Distributed Office
Avaya Distributed Office Issue 6 January 2008 23 ● Exposes composite communication service units expressed in the form of generic web service constructs understood by the business community at large. ● Uses presence and availability computations to route communication to the right device of the user...
Page 24 - Distributed Office Configurations
Avaya Application Solutions 24 Avaya Application Solutions IP Telephony Deployment Guide Avaya Distributed Office contains integrated features, applications, and much more. At each branch location, Distributed Office is implemented in one of two platforms — Avaya Distributed Office i40 or Avaya Dist...
Page 25 - Figure 3: Networked remote sites; Main business location; SES edge
Avaya Distributed Office Issue 6 January 2008 25 Figure 3: Networked remote sites SES home PSTN SIP Apps servers Main business location SIP IVR private WAN SES edge Central Optional components SIP TDM SIP T Manager Communication Manager Branch locations PSTN Feature Server SIP Enablement Services Lo...
Page 26 - Distributed Office benefits; Distributed Office implementation; Selecting a construct
Avaya Application Solutions 26 Avaya Application Solutions IP Telephony Deployment Guide Distributed Office benefits The benefits of Avaya Distributed Office include advanced functionality such as: ● Platform features - Feature server including both PBX and Key-System features - SIP Enablement Servi...
Page 27 - i40 constructs; Table 1: i40 constructs
Avaya Distributed Office Issue 6 January 2008 27 An i40 might provide an adequate number of lines and trunks for the current business requirements but not for increased requirements in two years based on growth assumptions. Or, an i40 might provide enough lines and trunks for the next several years ...
Page 29 - Distributed Office application module and media modules; Avaya AM110 Application Module; Construct
Avaya Distributed Office Issue 6 January 2008 29 Distributed Office application module and media modules Avaya AM110 Application Module The Avaya AM110 Application Module is the heart of the Replace variable w/ short product name system. The AM110 Application Module provides the telephony features, ...
Page 30 - Telephony media modules; Streamlined Deployment
Avaya Application Solutions 30 Avaya Application Solutions IP Telephony Deployment Guide Telephony media modules The ten constructs for Distributed Office i120 contain one or more media modules. Table 3 shows the available media modules, and the slot or slots in which each module can be inserted. St...
Page 31 - Provisioning status; Partially configured.; Configure from scratch.; Fully configured systems
Avaya Distributed Office Issue 6 January 2008 31 ● Custom — The profile is not a Standard profile and needs to be created. ● None (Default)— The default profile associated with the hardware construct will be shipped and the provisioning data will be entered when the system is installed. The deployme...
Page 32 - Partially configured systems; nvram init
Avaya Application Solutions 32 Avaya Application Solutions IP Telephony Deployment Guide Partially configured systems For a partially configured system, a Standard profile is selected or a Custom profile is created that contains some of the provisioning data. The profile contains a section for dynam...
Page 33 - Avaya Application Solutions platforms; Figure 4: Avaya Application Solutions platforms port capacities; IP Connect
Issue 6 January 2008 33 Avaya Application Solutions platforms Overview The Avaya Communication Manager portfolio covers small, medium, and large enterprises with advanced communications needs between 2 and 48,000 ports per system. This chapter provides an overview of the Avaya Communication Manager ...
Page 36 - Terminology; Center Stage Switch -
Avaya Application Solutions platforms 36 Avaya Application Solutions IP Telephony Deployment Guide Terminology The terms IP-PNC and fiber-PNC are used in this chapter to distinguish between the two types of port network connectivity (PNC). Synonyms are IP-connected and Fiber-connected , respectively...
Page 37 - Figure 5: Avaya G700 Media Gateway with the S8300 Server
Small to mid-size enterprise Issue 6 January 2008 37 Small to mid-size enterprise Avaya S8300 Server and Avaya G700, G450,G350, or G250 Media Gateway The S8300 Server and G700 Media Gateway solution ( Figure 5: Avaya G700 Media Gateway with the S8300 Server on page 37) seamlessly delivers voice, fax...
Page 38 - G700 hardware architecture
Avaya Application Solutions platforms 38 Avaya Application Solutions IP Telephony Deployment Guide Multiple G700 Media Gateways can be connected to each other through an Octaplane 8-Gbps stacking fabric, and Avaya P330 Expansion Modules, which allows adding additional Ethernet ports, fiber interface...
Page 40 - VoIP Engine complex
Avaya Application Solutions platforms 40 Avaya Application Solutions IP Telephony Deployment Guide The G700 motherboard hardware design involves three major blocks: ● A DSP engine and associated packet processor complex. This complex performs IP/UDP/RTP processing, echo cancellation, G.711 A/µ, G.72...
Page 41 - Voice Announcement over the LAN
Small to mid-size enterprise Issue 6 January 2008 41 ● Recorded announcement playback (15 playback channels, 1 record channel) ● Tone detection and generation (15 ports of tone detection) ● System clock generation and synchronization to an external network timing reference ● Download agent for the m...
Page 42 - S8300 primary controller architecture
Avaya Application Solutions platforms 42 Avaya Application Solutions IP Telephony Deployment Guide ● Voice quality is impacted when played over IP. However, quality is acceptable even with 2 hops and 10-msec delay. ● The use of G700 VAL sourced announcements impacts that gateway’s overall occupancy,...
Page 47 - G450 physical description; Figure 8: The Avaya G450 Media Gateway Chassis; Supported media modules in the G450; Table 5: Supported media modules
Small to mid-size enterprise Issue 6 January 2008 47 G450 physical description Figure 8: The Avaya G450 Media Gateway Chassis The Avaya G450 Media Gateway is a versatile device with powerful capabilities. To implement the various services that are supported, a variety of swappable internal component...
Page 48 - Additional features; Call center capabilities; WAN media modules
Avaya Application Solutions platforms 48 Avaya Application Solutions IP Telephony Deployment Guide ! CAUTION: CAUTION: The MM340 and MM342 are not supported by the Avaya G700 Media Gateway. Do not insert an MM340 or MM342 media module into an Avaya G700 Media Gateway. Voice over IP (VoIP) The G450 p...
Page 49 - Contact closure; LAN services; Physical media
Small to mid-size enterprise Issue 6 January 2008 49 Emergency Transfer Relay (ETR) The Emergency Transfer Relay (ETR) feature provides basic telephone services in the event of a power outage or a failed connection to Avaya Communication Manager. The ETR supports the connection of two external 808A ...
Page 50 - Port mirroring; WAN services
Avaya Application Solutions platforms 50 Avaya Application Solutions IP Telephony Deployment Guide Rapid Spanning Tree Protocol (RSTP) The IEEE 802.1D (STP) and IEEE 802.1w (RSTP) Spanning Tree Protocols are supported on the ETH LAN ports. Port mirroring The G450 supports network traffic monitoring ...
Page 51 - Media modules necessary for each WAN line; Management access security features; Table 6: Outside WAN lines supported and matching media modules
Small to mid-size enterprise Issue 6 January 2008 51 Media modules necessary for each WAN line The table below lists which media modules to install to connect each type of outside WAN line. Management access security features The G450 features the following management security mechanisms: ● A basic ...
Page 52 - Alarms and troubleshooting features; Converged Network Analyzer (CNA) test plug
Avaya Application Solutions platforms 52 Avaya Application Solutions IP Telephony Deployment Guide - SYN cookies, which protect against a well-known TCP/IP attack in which a malicious attacker targets a vulnerable device and effectively prevents it from establishing new TCP connections. Alarms and t...
Page 54 - Modes of Deployment
Avaya Application Solutions platforms 54 Avaya Application Solutions IP Telephony Deployment Guide ● Fax and modem over IP ● Frame-Relay ● GRE tunneling ● Inter-Gateway Alternate Routing (IGAR) ● MGC automatic switchover, migration, and survivability features ● Modem access for remote administration...
Page 56 - Table 7: Fixed ports on the G350 front panel
Avaya Application Solutions platforms 56 Avaya Application Solutions IP Telephony Deployment Guide G350 Specifications The G350 chassis features six media module slots (V1 to V6) and various fixed ports and buttons. V1 to V5 are G700 form factor media module slots capable of housing existing G700 me...
Page 58 - Table 10: Additional G350 functions and capacities
Avaya Application Solutions platforms 58 Avaya Application Solutions IP Telephony Deployment Guide The MM710, MM711, MM712, and MM720 are existing G700 media modules. Table 10: Additional G350 functions and capacities Function Capacity VoIP DSP engine 32 G.711 or 16 G.729 channels Touch Tone Recogni...
Page 59 - Figure 10: The Avaya G250 analog Media Gateway Chassis,
Small to mid-size enterprise Issue 6 January 2008 59 G250 Configurations Figure 10 shows the G250 Media Gateway chassis. Figure 11 shows the G250-BRI Media Gateway chassis. Figure 10: The Avaya G250 analog Media Gateway Chassis, Figure 11: The Avaya G250 BRI Media Gateway Chassis, Figure notes: 1. V...
Page 60 - Table 11: Fixed ports and buttons on the G250 front panel
Avaya Application Solutions platforms 60 Avaya Application Solutions IP Telephony Deployment Guide Table 11: Fixed ports and buttons on the G250 front panel describes the functions of the fixed ports and buttons on the G250 front panel. Table 11: Fixed ports and buttons on the G250 front panel Port ...
Page 62 - IG550 Integrated Gateway
Avaya Application Solutions platforms 62 Avaya Application Solutions IP Telephony Deployment Guide turning the SOHO branch into a seamless part of the enterprise’s network. For information on the G150 Media Gateway, see Hardware Description and Reference for Avaya Communication Manager , 555-245-207...
Page 67 - IG550 and J4350 Services Router physical description; Slot locations on J4350 Services Router -; Figure 14: Slot numbers on the Juniper J4350 Services Router
Small to mid-size enterprise Issue 6 January 2008 67 IG550 and J4350 Services Router physical description Figure 13: Example of the IG550 Integrated Gateway in a J4350 Services Router Slot locations on J4350 Services Router - The slots on the J4350 Services Router are identified as follows: Figure 1...
Page 68 - IG550 and J6350 Services Router physical description; Figure 15: The IG550 Integrated Gateway in a J6350 Services Router; Slot locations on J6350 Services Router; Figure 16: Slot numbers on the Juniper J6350 Services Router
Avaya Application Solutions platforms 68 Avaya Application Solutions IP Telephony Deployment Guide IG550 and J6350 Services Router physical description Figure 15: The IG550 Integrated Gateway in a J6350 Services Router Slot locations on J6350 Services Router The slots on the J6350 Services Router ar...
Page 69 - TGM550 physical description; Figure 17: The TGM550 Gateway Module; Supported optional modules in the J-series routers and the IG550; Table 12: Supported interface modules
Small to mid-size enterprise Issue 6 January 2008 69 The J-series router chassis has six slots. The TGM550 can be housed in any of the six router slots. The TIMs can also be housed in any slot. Gigabit Ethernet and Fast Ethernet PIMs can be housed only in slots 2, 3, 5, or 6. Other optional PIMs can...
Page 70 - J-series Router Physical Interface Modules
Avaya Application Solutions platforms 70 Avaya Application Solutions IP Telephony Deployment Guide TIM521 4 ISDN BRI trunk ports providing up to 8 bearer channels J-series Router Physical Interface Modules Dual-Port Serial PIM 2 Fast Ethernet ports and two serial ports Dual-Port T1 or E1 PIM 2 Fast ...
Page 71 - Summary of services; Table 13: Interface module capacities
Small to mid-size enterprise Issue 6 January 2008 71 Table 13 shows capacities of the supported interface modules. ! CAUTION: CAUTION: Some capacities may change. For the most up-to-date list, see System Capacities Table for Avaya Communication Manager on Avaya Servers , 03-300511. Summary of servic...
Page 72 - Configuring media gateway options
Avaya Application Solutions platforms 72 Avaya Application Solutions IP Telephony Deployment Guide Voice over IP (VoIP) The IG550 features a VoIP engine that provides voice services over IP data networks. The IG550 allows you to use many types of telephones and trunks that do not directly support Vo...
Page 73 - Backup and restore
Small to mid-size enterprise Issue 6 January 2008 73 ● You can configure the dialer interface to connect to the media gateway’s primary MGC via a modem connected to the J-series router in the event that the connection between the media gateway and the MGC is lost. ● You can configure the Avaya Commu...
Page 74 - IG550 maximum media gateway capacities; Table 14: IG550 media gateway capacities
Avaya Application Solutions platforms 74 Avaya Application Solutions IP Telephony Deployment Guide IG550 maximum media gateway capacities Table 14: IG550 media gateway capacities Description Capacity Comments Busy Hour Call rate (BHCC) 800 Maximum number of TGM550s controlled by an S8500 or S8700-se...
Page 79 - Mid-market to large enterprise
Mid-market to large enterprise Issue 6 January 2008 79 Mid-market to large enterprise S8500 Server The Avaya S8500 Server Platform is a simplex Linux-based server running Avaya Communication Manager software that replaces the DEFINITY SI and R processing platforms for small sites and for customers w...
Page 80 - Standard
Avaya Application Solutions platforms 80 Avaya Application Solutions IP Telephony Deployment Guide Because the inter port network TDM traffic flow is supported by a Center Stage Switch (CSS) or an Asynchronous Transfer Mode (ATM) switch using fiber-optic cables, this configuration is called fiber-PN...
Page 81 - S8700-series external features; Figure 19: Avaya S8700-series external features
Mid-market to large enterprise Issue 6 January 2008 81 S8700-series external features ● Six 10/100 Ethernet NICs per server, which are used as follows: - Dual control network connections - A memory duplication link to the duplicated server - Administrative access from the corporate network - Technic...
Page 82 - Internal hardware elements; Figure 20: Avaya S8700-series Server schematic; Other components
Avaya Application Solutions platforms 82 Avaya Application Solutions IP Telephony Deployment Guide USB modem - Each S8700-series Server supports a Universal Serial Bus (USB) modem. For customers with an Avaya service contract, the modem is used to send alarms to the Avaya Services organization, and ...
Page 83 - Control network through an Avaya Ethernet switch
Mid-market to large enterprise Issue 6 January 2008 83 Figure 21: Avaya S8700/MCC1 fiber-PNC major components Control network through an Avaya Ethernet switch When designing S8700-series fiber-PNC systems, a control network connects the servers to the IPSIs through a 10/100 BaseT Ethernet. It consis...
Page 84 - Circuit packs that support IP signaling and media traffic
Avaya Application Solutions platforms 84 Avaya Application Solutions IP Telephony Deployment Guide Circuit packs that support IP signaling and media traffic Figure 23: S8700-series / MCC1 signaling path Figure 24: S8700-series fiber-PNC — a basic phone call cynds117 KLC 121003 IP IP PN1 PN2 H.323 en...
Page 87 - Figure 25: TN2302AP Media Processor operation
Mid-market to large enterprise Issue 6 January 2008 87 Figure 25: TN2302AP Media Processor operation To do the job, a media processing circuit pack has a set of DSP resources. These resources are deployed dynamically and flexibly to any of a number of tasks, including: ● Originating and terminating ...
Page 88 - Media Gateways
Avaya Application Solutions platforms 88 Avaya Application Solutions IP Telephony Deployment Guide Since H.323 allows any of several different codecs to be used for encoding an audio stream on the IP network, the Media Processor board is able to use any of the following codecs: ● G.711 ● G.723.1 ● G...
Page 89 - Figure 26: MCC1 Media Gateway
Mid-market to large enterprise Issue 6 January 2008 89 Figure 26: MCC1 Media Gateway Single-Carrier Cabinet (SCC1) Media Gateway - The SCC1 Media Gateway consists of a single carrier. Up to four SCC1 Media Gateways can be connected together in one location to form one port network. There are two typ...
Page 90 - Figure 27: SCC1 Media Gateway
Avaya Application Solutions platforms 90 Avaya Application Solutions IP Telephony Deployment Guide Figure 27: SCC1 Media Gateway Non-IPSI connected Media Gateway - Typically, one of every five Port Networks (PNs) contains one or two IPSI circuit packs. The remaining PNs are referred to as non-IPSI c...
Page 91 - Center Stage Switch; ATM network
Mid-market to large enterprise Issue 6 January 2008 91 Remote G700, G450, G350, G250, or G150 Media Gateway - The S8700-series Server can provide the call processing features for a remote G700, G450, G350, or G250 media gateway over an H.248 link, and G150 gateway using H.323. In this configuration,...
Page 92 - S8700-series fiber-PNC configuration for higher availability; Standard reliability configuration
Avaya Application Solutions platforms 92 Avaya Application Solutions IP Telephony Deployment Guide S8700-series fiber-PNC configuration for higher availability When used with the MCC1 and SCC1 Media Gateways, the S8700-series Server has the following reliability options: ● Standard reliability confi...
Page 94 - High reliability configuration
Avaya Application Solutions platforms 94 Avaya Application Solutions IP Telephony Deployment Guide High reliability configuration The high reliability configuration option builds on the standard reliability option. The high reliability option duplicates components, so that no single point of failure...
Page 96 - Critical reliability configuration; Avaya S8700-series Server IP-PNC configuration
Avaya Application Solutions platforms 96 Avaya Application Solutions IP Telephony Deployment Guide Critical reliability configuration The critical reliability configuration option is built upon the high reliability configuration. In the critical reliability configuration, the bearer network has dupl...
Page 98 - Main components
Avaya Application Solutions platforms 98 Avaya Application Solutions IP Telephony Deployment Guide Figure 31: S8700-series Server IP-PNC — a basic phone call on page 98 shows a call through an S8700 IP-PNC system. Figure 31: S8700-series Server IP-PNC — a basic phone call Main components The S8700-s...
Page 100 - S8700-series IP-PNC reliability configurations
Avaya Application Solutions platforms 100 Avaya Application Solutions IP Telephony Deployment Guide The left data rack contains a stack of five G650 Media Gateways that are labeled A through E. The right data rack contains the following (from top to bottom): ● Two USB-compliant modems ● Two S8700-se...
Page 101 - Figure 33: S8700 IP-PNC standard configuration
Mid-market to large enterprise Issue 6 January 2008 101 S8700 IP-PNC configuration Figure 33: S8700 IP-PNC standard configuration Figure notes: 1. Two S8700-series Servers. One server is in a active mode, and the other server is on standby. 2. Duplication Interface. The Ethernet connection between t...
Page 102 - Combined IP and fiber Port Network Connectivity
Avaya Application Solutions platforms 102 Avaya Application Solutions IP Telephony Deployment Guide Combined IP and fiber Port Network Connectivity Communication Manager Release 3.0 enables the S8700-series and S8500 Servers to support configurations that combine IP-connected port networks (IP-PNC) ...
Page 103 - Media Gateway Capacity; Server
Mid-market to large enterprise Issue 6 January 2008 103 The G650, SCC1, and MCC1 Media Gateways can connect to a combined IP-PNC and fiber-PNC system using either IP or fiber connections. The CMC1 Media Gateway can be IP-connected only and cannot be fiber-connected in any of the combined IP-PNC and ...
Page 104 - Capacity limit for media gateways
Avaya Application Solutions platforms 104 Avaya Application Solutions IP Telephony Deployment Guide Capacity limit for media gateways A combined IP-PNC and fiber-PNC system can support up to 250 Media Gateways including the G150, G250, G350, G450, and G700. Configuration rules Combined IP-PNC and fi...
Page 105 - MCC1 Media Gateway with one or more IP- and fiber-connected PNs
Mid-market to large enterprise Issue 6 January 2008 105 MCC1 Media Gateway with one or more IP- and fiber-connected PNs In a combined IP-PNC and fiber-PNC configuration, an MCC1 Media Gateway may contain ● up to 5 fiber-connected PNs. ● up to 5 IP-connected PNs. ● both IP-connected and fiber-connect...
Page 106 - Mixed reliability options; Connection Method for Mixed PNC Configurations; Reliabi
Avaya Application Solutions platforms 106 Avaya Application Solutions IP Telephony Deployment Guide Mixed reliability options The reliability options separately available for each PNC method still apply except that fiber-connected PNs (fiber-PNC) with single control networks cannot be mixed with IP-...
Page 107 - ESS support for combined IP-PNC and fiber-PNC configurations; Processor Ethernet
Processor Ethernet Issue 6 January 2008 107 Networking option of S8700-series Server pair for duplicated and single control networks For an S8700-series Server pair with direct/CSS/ATM PNC and duplicated control networks, control network A and control network B interfaces are administered as dedicat...
Page 108 - Avaya IP Office; Servers
Avaya Application Solutions platforms 108 Avaya Application Solutions IP Telephony Deployment Guide The following table describes the usage of Processor Ethernet as of release 3.1 : Avaya IP Office Avaya IP Office is another standalone Avaya platform that supports IP Telephony for the small to mid-s...
Page 109 - Greenfield deployment; Components needed for Greenfield deployment
Issue 6 January 2008 109 Greenfield deployment This chapter explains how to implement Avaya Application Solutions components in a Greenfield site. A Greenfield site is a business or an organization that does not have an existing communication system. Most Greenfield systems are deployed into new bus...
Page 111 - Media Gateways and Port Networks
Components needed for Greenfield deployment Issue 6 January 2008 111 Avaya Communication Manager Communication Manager IP capabilities and applications support voice over an IP network, and ensure that remote workers have access to communication system features from their PCs. Communication Manager ...
Page 112 - Greenfield configurations
Greenfield deployment 112 Avaya Application Solutions IP Telephony Deployment Guide Greenfield configurations S8300 standalone solution(small-to-midsize enterprise) An S8300 Server with a G700, G250, or G350 gateway is designed for a small to mid-size office. The S8300 fits into a media module slot ...
Page 116 - Required circuit packs for S8700-series configuration
Greenfield deployment 116 Avaya Application Solutions IP Telephony Deployment Guide Figure 38: S8700-series with G150/G250 -- large number of remote branches Required circuit packs for S8700-series configuration The circuit packs that are required for IP Telephony in a Communication Manager system i...
Page 119 - Figure 42: Traditional DEFINITY configuration
Issue 6 January 2008 119 Evolution from circuit-switched to IP Overview The Avaya DEFINITY® Enterprise Communications Server G3r has been the flagship product in the DEFINITY family of communications servers. As technology changed, Avaya was able to leverage the rapid advances in microprocessor tech...
Page 120 - Phase 1: Processor replacement
Evolution from circuit-switched to IP 120 Avaya Application Solutions IP Telephony Deployment Guide With the S8700 fiber-PNC solution, Avaya is delivering a high-capacity server and a migration path from DEFINITY. The S8700-series Server uses an industry-standard Linux operating system on an industr...
Page 122 - Phase 2: IP-enable the Port Networks to support IP endpoints; Figure 44: IP-enabled DEFINITY configuration
Evolution from circuit-switched to IP 122 Avaya Application Solutions IP Telephony Deployment Guide Phase 2: IP-enable the Port Networks to support IP endpoints Port Networks, with the addition of IP enabling circuit packs, are able to serve as Media Gateways, representing the integration of IP and ...
Page 123 - Phase 3: Server consolidation
Migration from DEFINITY Server R to S8700 fiber-PNC Issue 6 January 2008 123 At this stage, the media flow between two IP endpoints can be “shuffled.” That is, the media flow proceeds directly between both endpoints without requiring Media Processor resources. Shuffling may be used across multiple s...
Page 125 - Voice and multimedia networking; Intelligent networking and call routing
Issue 6 January 2008 125 Call processing This chapter explains the features, the strengths, and the architecture of Communication Manager call processing.This chapter emphasizes the call processing components of Communication Manager and its architecture, and briefly discusses IP-related application...
Page 126 - IP Port Network / Media Gateway connectivity
Call processing 126 Avaya Application Solutions IP Telephony Deployment Guide IP Port Network / Media Gateway connectivity IP PNC allows S8700-series Servers and G650 Media Gateways to be connected over IP networks. Avaya Communication Manager uses a proprietary method to package signaling messages ...
Page 127 - Call Processing; Communication Manager gatekeepers; Registration and alternate gatekeeper list
Call Processing Issue 6 January 2008 127 Call Processing Communication Manager gatekeepers A gatekeeper is an H.323 entity on the network that provides address translation and controls access to the network for H.323 endpoints. For Communication Manager platforms, these are the Avaya S8300, S8400, S...
Page 128 - Call signaling
Call processing 128 Avaya Application Solutions IP Telephony Deployment Guide Figure 47: Discovery and registration process to the gatekeeper Call signaling Communication Manager implements the gatekeeper routed call model of H.323. The registration process that is described above allows the endpoin...
Page 129 - Media stream handling; Media processor circuit packs (VoIP resources); DTMF tone handling
Call Processing Issue 6 January 2008 129 Media stream handling Media processor circuit packs (VoIP resources) The basic functions of the TN2302AP IP Media Processor and TN2602AP IP Media Resource 320 circuit packs, and VoIP on the G700/G350 Media Gateways, include: ● Taking media streams off the IP ...
Page 134 - IP tie trunks; Trunk signaling; SIP
Call processing 134 Avaya Application Solutions IP Telephony Deployment Guide IP tie trunks IP tie trunks are used to connect switches to one another. When an IP trunk is used to interconnect two switches, the trunk can also carry standard (QSIG) and proprietary (DCS+) signaling for interswitch feat...
Page 137 - The SES Network; Communication Manager as the SIP Feature Server
SIP Issue 6 January 2008 137 The high level architecture is a shared data approach, where most components do not interact directly with each other, but rather all share and use data in the database. The master admin system populates that data from a single web interface, and run-time components read...
Page 138 - SIP Adjuncts; Table 18: SIP Endpoints
Call processing 138 Avaya Application Solutions IP Telephony Deployment Guide feature using Feature Name URIs, and retrieving state through event packages. Advanced SIP users must be provisioned both on SES as a SIP user and as an OPTIM station on Communication Manager. There must be a SIP trunk con...
Page 139 - SIP deployment scenarios; SIP and DNS
SIP Issue 6 January 2008 139 SIP deployment scenarios SIP and DNS In all SIP configurations it is highly recommended to use both Dynamic Name System (DNS) and Dynamic Host Configuration Protocol (DHCP). The customer must have DNS running in the enterprise for external lookups. Proper DNS configurati...
Page 140 - Multi-home multi-Communication Manager system
Call processing 140 Avaya Application Solutions IP Telephony Deployment Guide Figure 49: Typical home/edge configuration Multi-home multi-Communication Manager system The multi-home system is a distributed version of the home/edge system where the edge is a separate host from the home servers, which...
Page 141 - Figure 50: Multi-home multi-Communication Manager configuration
SIP Issue 6 January 2008 141 Figure 50: Multi-home multi-Communication Manager configuration Figure 51: Message flow for multi-home multi-Communication Manager configuration on page 142 shows the message flow, where the arrows in numerical order represent the path of the initial INVITE message start...
Page 142 - Multi-home single Communication Manager system
Call processing 142 Avaya Application Solutions IP Telephony Deployment Guide Figure 51: Message flow for multi-home multi-Communication Manager configuration Multi-home single Communication Manager system One possible configuration is to only have a single Communication Manager system in the SIP de...
Page 145 - Avaya-Toshiba Solution
SIP Issue 6 January 2008 145 Figure 55: Multi-home multi-Communication Manager configuration with QSIG connection - message flow Avaya-Toshiba Solution Avaya and Toshiba have collaborated to provide a combined Avaya AST solution (Communication Manager and SES) with Toshiba SIP terminals for the Japa...
Page 147 - Avaya G860 Media Gateway
Avaya G860 Media Gateway Issue 6 January 2008 147 Avaya G860 Media Gateway The Avaya G860 media gateway is a DS3-capable, high channel density standards-compliant, VoIP media gateway system. It provides a robust, scalable, and modular solution designed for a large campus or call center with high ava...
Page 149 - System Controller Board; Table 19: G860 Media Gateway components
Avaya G860 Media Gateway Issue 6 January 2008 149 G860 Components The G860 media gateway hardware consists of the chassis, TP6310 (media gateway board), Ethernet Switch, System Controller, and the corresponding Rear Transition Modules (RTM). Table 19 lists the G860 Media Gateway components and redun...
Page 150 - Configuration with Avaya Communication Manager
Call processing 150 Avaya Application Solutions IP Telephony Deployment Guide contains an on-board hard disk, which stores the SC software and the configuration and performance database.The SC board incorporates a 650 Mhz UltraSparc processor with 512 MB memory and uses the robust Solaris operating ...
Page 151 - Example configuration for call center
Avaya G860 Media Gateway Issue 6 January 2008 151 Example configuration for call center The Avaya G860 Media Gateway allows call center customers to consolidate facilities and reduce communications costs. The media gateway concentrates incoming PSTN traffic over several DS3 lines while supporting Vo...
Page 152 - Mobility; IP Telephones or IP Softphones; Communication applications
Call processing 152 Avaya Application Solutions IP Telephony Deployment Guide Mobility IP Telephones or IP Softphones IP Telephones allow access to the features of Communication Manager without having to be tied to one location. One of the major benefits of IP Telephones is that you can move the tel...
Page 153 - Call Center applications
Communication applications Issue 6 January 2008 153 ● Avaya Call Management System (CMS) ● Conferencing systems ● Meet-me conferencing ● Avaya Meeting Exchange Solutions ● Video Telephony Solutions ● Computer Telephony Integration (CTI) ● Application Programming Interfaces (APIs) ● Best Services Rou...
Page 154 - Compact Call Center; Messaging
Call processing 154 Avaya Application Solutions IP Telephony Deployment Guide ● Avaya Call Management System Supervisor ● Avaya Basic Call Management System ● Avaya Business Advocate ● Call Center - Avaya Call Center Basic - Avaya Call Center Deluxe - Avaya Call Center Elite ● Call Recording ● CALLM...
Page 155 - Unified Communication Center; CMS reliability and redundancy
Communication applications Issue 6 January 2008 155 Unified Communication Center Unified Communication Center lets mobile, remote and office workers easily access important communications tools and information via any telephone using simple and intuitive speech commands. Avaya Call Management System...
Page 156 - Avaya Meeting Exchange Solutions; Meeting Exchange Enterprise Edition; User Control of Conference Scheduling and Management -
Call processing 156 Avaya Application Solutions IP Telephony Deployment Guide special hardware. Meet-me conferencing uses a software approach that is based on Vector Directory Number (VDN) vectors and announcements. An announcement source is necessary to use meet-me conferencing. Supported announcem...
Page 157 - Integrated Web Conferencing -
Communication applications Issue 6 January 2008 157 Value-added Features - These capabilities, including reporting, recording and billing, enable enterprises to precisely manage use of their conferencing service by generating customized conference reports and enabling internal bill back systems. Int...
Page 158 - Meeting Exchange Web Conferencing; Strengths and Differentiators -
Call processing 158 Avaya Application Solutions IP Telephony Deployment Guide Meeting Exchange Web Conferencing Target Market: Mid-market, Service Providers Integrated Solution Features: ● PowerPoint push and document annotation, white boarding, chat, polling ● Desktop or application sharing ● Workh...
Page 159 - Meeting Exchange Express Edition
Communication applications Issue 6 January 2008 159 Hardware and Software requirements include: ● Meeting Exchange audio conferencing bridge ● Off-the-shelf server, plus Web Conferencing software (license based capacity) ● Additional servers required for recording and playback (optional) Meeting Exc...
Page 160 - Application Programming Interfaces (APIs)
Call processing 160 Avaya Application Solutions IP Telephony Deployment Guide other H.323 endpoints. With the Avaya Video Telephony Solution, you can provide video for desktop and group communications.The Avaya Video Telephony Solution supports the following features and products: ● Ad-hoc video con...
Page 163 - LAN switching products; Avaya C360 converged stackable switches; Figure 60: C363T Converged Stackable switch
Issue 6 January 2008 163 LAN switching products This chapter discusses how Avaya LAN switches and other LAN switching products add value to an IP Telephony deployment. Avaya C360 converged stackable switches The Avaya C360 converged stackable switch series is a line of stackable, multilayer switches...
Page 164 - Figure 61: C363T-PWR Converged Stackable switch; Figure 62: C364T Converged Stackable switch; Figure 63: C364T-PWR Converged Stackable switch; Features of the C360 converged stackable switches
LAN switching products 164 Avaya Application Solutions IP Telephony Deployment Guide ● C363T-PWR converged stackable switch This switch has 24 10/100 Mbps ports with Power over Ethernet (PoE) and two GBIC SFP ports. Figure 61: C363T-PWR Converged Stackable switch ● C364T converged stackable switch T...
Page 165 - Stacking; Layer 2 features
Avaya C360 converged stackable switches Issue 6 January 2008 165 Stacking ● Up to 10 switches can be stacked together. ● Features such as Spanning Tree, redundancy, VLANs, and SMON are common to the stack. ● The Octaplane stacking system provides 8 Gbps stacking bandwidth to all switches in the stac...
Page 166 - Layer 3; features; Management
LAN switching products 166 Avaya Application Solutions IP Telephony Deployment Guide ● RMON/SMON port statistics provide real-time top-down analysis of network traffic. ● IP multicast filtering (snooping) filters multicast traffic to optimize network bandwidth. ● Classification of ports as regular o...
Page 167 - Switches from Extreme Networks
Avaya C360 converged stackable switches Issue 6 January 2008 167 ● Simple network time protocol (SNTP) or TIME protocols are available to provide a consistent timestamp to all switches from an external source. ● Radius authentication enables centralized user management. ● You can use all appropriate...
Page 168 - Avaya Power over Ethernet (PoE) switches; Available PoE Switch Options; Switch
LAN switching products 168 Avaya Application Solutions IP Telephony Deployment Guide - BlackDiamond 8806 - a 6-slot non-blocking switch for access or core - BlackDiamond 8810 - a 10-slot non-blocking switch for access or core For information on Extreme Networks switches, see http://www.extremenetwor...
Page 169 - Power priority mechanism; Midspan Power Units; Designed usage
Midspan Power Units Issue 6 January 2008 169 Power priority mechanism The priority mechanism is implemented in order to handle cases where the power requested by the PDs exceeds the switch PoE capacity. This priority mechanism determines the order in which ports will be powered on after boot, and po...
Page 170 - Barrel connector through brick transformer; Power using adapters
LAN switching products 170 Avaya Application Solutions IP Telephony Deployment Guide The 1152A1 can be collocated with the data equipment or closer to the endpoints. In all cases, IEEE 802.3af capable IP devices must connect directly to this PDU. The PDU cannot power any device if a hub or a switch ...
Page 171 - 152B Power Distribution Units; Table 21: 1152B Midspan Power Distribution Units
Midspan Power Units Issue 6 January 2008 171 1152B Power Distribution Units The Avaya 1152B Mid-Span Power Distribution Units are Ethernet power supplies that provide power to up to 48 46xx-series or 96xx IP telephones or wireless LAN (WLAN) access points. The 1152B PDUs are designed to deliver powe...
Page 172 - Converged infrastructure security gateways
LAN switching products 172 Avaya Application Solutions IP Telephony Deployment Guide Designed usage The 1152B PDUs are used to power the 46xx series and 96xx series of IP telephones in addition to providing 10/100 megabits per second Ethernet connection. Generation 1 Avaya IP telephones can receive ...
Page 175 - Section 2: Deploying IP Telephony
Issue 6 January 2008 175 Section 2: Deploying IP Telephony
Page 177 - Traffic engineering; Introduction
Issue 6 January 2008 177 Traffic engineering This chapter provides an introduction to traffic engineering. Specifically, this chapter discusses various traffic models, algorithms, and resource sizing.This section includes the following topics: ● Introduction ● Design inputs - Topology - Endpoint spe...
Page 178 - Design inputs; Topology
Traffic engineering 178 Avaya Application Solutions IP Telephony Deployment Guide This discussion of the configuration, engineering, and deployment processes is intended as an overview that is suitable for a fairly general audience. One example that is designed to exercise all aspects of these proce...
Page 180 - Endpoint specifications; Light
Traffic engineering 180 Avaya Application Solutions IP Telephony Deployment Guide Endpoint specifications Normally, a customer who submits a Request for Proposal (RFP) specifies the number of each type of station to place in each site, in each Communication Manager system in the network. Certain cus...
Page 181 - Example 1: Station usage; BHCC seconds per call; Table 23: Example 1 configuration data
Design inputs Issue 6 January 2008 181 The most commonly used default value for a general business system is 0.11 Erlangs per station. The most common way to determine trunk usage rates is to divide the total traffic load that is carried by each trunk group by the number of trunks in the group. It i...
Page 182 - Additional design criteria; Table 24: Example 1 station usage by endpoint type
Traffic engineering 182 Avaya Application Solutions IP Telephony Deployment Guide Additional design criteria ● Each site is to have a suitable number of PSTN trunks (which terminate on PNs in Atlanta and Boston, and on the G350 Media Gateways in Cleveland). ● This is a general business application (...
Page 183 - Call usage rates; Communities of interest
Call usage rates Issue 6 January 2008 183 Call usage rates In the previous section, station usages and overall endpoint usages, including both stations and trunks, were discussed. The overall endpoint usage is sometimes referred to as port usage rate (PUR). The term station usage rate (SUR) applies ...
Page 184 - Intercom
Traffic engineering 184 Avaya Application Solutions IP Telephony Deployment Guide One of the first steps in the process is to distinguish between intercom call usage, inbound PSTN call usage, and outbound PSTN call usage. Inbound and outbound tie trunk usage must also be considered when working with...
Page 185 - SUR
Call usage rates Issue 6 January 2008 185 Alternatively, 100 Erlangs of total station usage could also hypothetically correspond to 35 Erlangs of intercom call usage, 10 Erlangs of inbound PSTN usage, and 20 Erlangs of outbound PSTN usage. Using the procedure from the preceding example to verify thi...
Page 186 - Example 2: Uniform Distribution model
Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide Example 2: Uniform Distribution model In the case of a stand-alone Avaya system, the Uniform Distribution model works on the assumption that when a given station places an intercom call, the call is equally likely to t...
Page 187 - Table 26: Inbound COI matrix for the Uniform Distribution model in
Call usage rates Issue 6 January 2008 187 Communication Manager uses a first-site-preference algorithm for outbound trunk calls. This algorithm specifies that all outbound calls first attempt to seize a trunk within the originating station’s site, and tries to use a trunk in a different site if and ...
Page 188 - Table 27: Outbound COI matrix for Uniform Distribution Model in
Traffic engineering 188 Avaya Application Solutions IP Telephony Deployment Guide Again, Table 26 and Table 27 are constructed without considering overflow traffic.These tables imply that the Site 1 PSTN trunks carry 98 Erlangs (49 inbound and 49 outbound) of traffic, the Site 2 trunks carry 36 Erla...
Page 189 - Uniform Distribution model
Call usage rates Issue 6 January 2008 189 It is assumed that half of each individual station’s usage is associated with calls that the station generates, and the other half is associated with calls that the station receives. Therefore, half of the 97 Erlangs of station usage (that is, 49 Erlangs) in...
Page 190 - Additional comments regarding
Traffic engineering 190 Avaya Application Solutions IP Telephony Deployment Guide The general formulas used to populate the COI matrix entries in Table 26 , Table 27 , and Table 28 , respectively, for the Uniform Distribution model are: Additional comments regarding Example 2: Uniform Distribution m...
Page 191 - Example 3: Empirical approach for existing systems; Expanded COI matrices
Call usage rates Issue 6 January 2008 191 Table 27 , and Table 28 , respectively, for the Uniform Distribution model based on relative SUR are: Example 3: Empirical approach for existing systems Another possible means of populating the COI matrices exists for established systems. In such cases, the ...
Page 192 - Example 4: Expanded COI matrices; From end
Traffic engineering 192 Avaya Application Solutions IP Telephony Deployment Guide Consider the COI matrix for a three-site, stand-alone Communication Manager system, as presented in Table 25 . A suitable expansion of that matrix might take the form of the matrix in Table 29: Expanded COI matrix for ...
Page 193 - Table 30: Endpoints in a three-site system
Call usage rates Issue 6 January 2008 193 First consider the 32 Erlangs of intercom CUR between Site 1 stations ( Table 28 ). Site 1 (Atlanta) has a total of 1755 stations, 1107 of which are IP stations, and 648 of which are circuit-switched stations. So, 63% of the stations in Site 1 are IP, and 37...
Page 194 - Table 31: COI matrix for
Traffic engineering 194 Avaya Application Solutions IP Telephony Deployment Guide In addition, 37% of intercom calls that are generated in Site 1 are generated by circuit-switched stations, and 69% of those calls are terminated by IP stations. Since 69% of 37% is 25.5%, 25.5% of Site 1 to Site 2 int...
Page 196 - Table 32: Completed COI matrix for
Traffic engineering 196 Avaya Application Solutions IP Telephony Deployment Guide The general formula that is used to determine the expanded inbound and outbound CUR entries in Table 32 is: where: ● “Type t ” refers to IP or circuit-switched ● ● Table 32: Completed COI matrix for Example 4: Expanded...
Page 197 - COIs for multiple-site networks; Figure 64: Network of Avaya systems and system sites
Call usage rates Issue 6 January 2008 197 In general, one may choose to expand a COI matrix in any of several different possible ways, depending upon the needs of the problem. In the preceding example, separating the endpoints into IP, circuit-switched, and PSTN makes sense for the upcoming resource...
Page 199 - Signaling resources
Resource sizing Issue 6 January 2008 199 Signaling resources The TN799DP C-LAN and the TN2312BP (IPSI) circuit packs are the primary signaling traffic bearing components residing within a port network. Both have finite internal resources such as sockets and data-link connection identifiers (DLCIs) f...
Page 200 - Media processing and TDM resources; Figure 65: Examples of media streams between Avaya endpoints
Traffic engineering 200 Avaya Application Solutions IP Telephony Deployment Guide the message traffic through C-LANs and IPSIs. Optimal configurations allocate enough of both to maintain traffic levels at or below known stable thresholds. Avaya configuration software tools perform the requisite anal...
Page 201 - Hairpinning
Resource sizing Issue 6 January 2008 201 Although we stated that calls between two circuit-switched endpoints on different port networks use an IP connection, the use of a circuit-switched center stage between the two PNs is also supported. However, using circuit-switched facilities is not viable fo...
Page 205 - Example 5: TDM and media processing usage
Resource sizing Issue 6 January 2008 205 Example 5: TDM and media processing usage Consider the COI matrix in Table 32: Completed COI matrix for Example 4: Expanded COI matrices on page 196 in Example 4: Expanded COI matrices . A set of nine cells corresponds to calls originated in Site 1 and termin...
Page 206 - Table 33: Re-categorization of CURs from
Traffic engineering 206 Avaya Application Solutions IP Telephony Deployment Guide Table 33 provides a summary of call usage rates, which can be mapped to a table of TDM usage rates and media processing usage rates by using the information in Figure 67 and Figure 68 . We assume that there is only one...
Page 207 - media processing usage
Resource sizing Issue 6 January 2008 207 Table 34: TDM and Media Processing usages (Erlangs) for Example 5: TDM and media processing usage Endpoints Site 1 (Atlanta) Site 2 (Boston) Site 3 (Cleveland) Intrasite: I, I TDM: 0 Media: 0 TDM: 0 Media: 0 TDM: 0 Media: 0 Intrasite: I, C or P TDM: 76.8 Medi...
Page 210 - Table 37: TDM and Media Processing Requirements for; Supported by
Traffic engineering 210 Avaya Application Solutions IP Telephony Deployment Guide Table 35 implies that three TN2302AP IP Media Processor circuit packs should be used in Site 1 (Atlanta), and two should be used in Site 2 (Boston). Table 36 implies that the media processing resources on the two G350 ...
Page 211 - Processing occupancy
Resource sizing Issue 6 January 2008 211 Starting with release 3.1 of Communication Manager, the TN2602AP IP Media Resource 320 can be duplicated to provide critical bearer reliability for IP-connected port networks.If more than one PN had been required in a particular site, intrasite calls between ...
Page 213 - SIP traffic engineering
Resource sizing Issue 6 January 2008 213 Therefore, for the given configuration, the specific linear model for the relationship between the sum of static and CP occupancy, as a function of BHCC, has been derived. Using the anticipated BHCC rate in that model yields the expected combined static and C...
Page 214 - C-LAN allocation and SIP trunks
Traffic engineering 214 Avaya Application Solutions IP Telephony Deployment Guide usual. Direct media shuffling between SIP stations and IP trunks is not supported. Therefore, SIP calling between Communication Manager systems connected by IP TIE trunks always require allocation of VoIP media resourc...
Page 215 - SIP specific features; Registration
Resource sizing Issue 6 January 2008 215 3. Allocate enough trunk members to each C-LAN to achieve desired grade of service, based on the known or assumed call traffic. 4. Check SIP message throughput based on the call traffic. 5. If SIP message traffic exceeds desirable threshold for any C-LAN, eit...
Page 216 - Communication Manager and SES server processor occupancy; IP bandwidth and Call Admission Control
Traffic engineering 216 Avaya Application Solutions IP Telephony Deployment Guide Communication Manager and SES server processor occupancy SIP incurs Communication Manager server processing time (as discussed in a previous section), just like any other type of Communication Manager call. Special car...
Page 218 - Example 6: IP bandwidth considerations; Example 6: IP bandwidth
Traffic engineering 218 Avaya Application Solutions IP Telephony Deployment Guide Example 6: IP bandwidth considerations The information in Figure 70 and Figure 71 along with the information in Table 33 produces the following tables of bandwidth usages that are associated with the configuration in E...
Page 219 - Number of bits of
Resource sizing Issue 6 January 2008 219 Table 39 and Table 40 express bandwidth usages in Erlangs, because each such usage actually represents the average number of simultaneous bidirectional media streams through the IP network in question. To convert those usages into bandwidth requirements in un...
Page 220 - Table 41: Payload size per packet
Traffic engineering 220 Avaya Application Solutions IP Telephony Deployment Guide Table 41: Payload size per packet on page 220 is populated using this formula, and provides the payload size per packet (expressed in bits) as a function of packet “size” (that is, ms per packet) and codec. Note that t...
Page 221 - Example 7: LAN bandwidth; Table 43: IP LAN bandwidth requirements in each direction, for
Resource sizing Issue 6 January 2008 221 Example 7: LAN bandwidth In Example 6: IP bandwidth considerations , the total IP LAN bandwidth usage for each site was calculated, and expressed in Erlangs at the bottom of Table 39 . Specifically, the total LAN bandwidth usage in Site 1 is 123.5 Erlangs, in...
Page 222 - Example 8: WAN bandwidth; Table 44: IP WAN bandwidth requirements for media streams
Traffic engineering 222 Avaya Application Solutions IP Telephony Deployment Guide table of WAN bandwidths, Table 44: IP WAN bandwidth requirements for media streams on page 222, which assumes the use of cRTP: This table can be used in the WAN bandwidth calculation for the system in Example 6: IP ban...
Page 223 - Table 45: IP WAN bandwidth requirements in each direction, for
Resource sizing Issue 6 January 2008 223 In Table 45 , the number of simultaneous media streams for “P001” represents the 99.9th percentile for the number of simultaneous streams, as determined by applying the standard infinite-server queueing model.To this point, all the discussion regarding bandwi...
Page 224 - Physical resource placement
Traffic engineering 224 Avaya Application Solutions IP Telephony Deployment Guide Physical resource placement As a default, resources should be balanced as uniformly as possible. For example, if 11 Media Processors are required in a Network Region that has three PNs, two of the PNs should house four...
Page 227 - Your security policy
Issue 6 January 2008 227 Security This chapter discusses the security design and features for Avaya Communication Manager, and how to operate Avaya systems securely. Note: Note: Because this information is valuable both to those who want to protect the system and to those who seek to “hack” into tho...
Page 228 - What are you trying to protect?; Recommendations for your security policy
Security 228 Avaya Application Solutions IP Telephony Deployment Guide What are you trying to protect? The security policy usually attempts to protect information, whether the information is in the form of data (files) or conversations (digitized voice packets). Customers should assess the value of ...
Page 229 - Built-in Linux security features; Proprietary vs. open operating systems
Avaya Communication Manager and Servers Issue 6 January 2008 229 Avaya CommunicationManager and Servers This section discusses Avaya’s security designs: ● Built-in Linux security features ● One-time passwords ● Shell access ● Root access ● Remote access ● Secure access ● Monitoring and alarming ● Da...
Page 230 - Avaya capitalizes on Linux’ security advantage; Shell access
Security 230 Avaya Application Solutions IP Telephony Deployment Guide Avaya capitalizes on Linux’ security advantage The Avaya servers run under the Linux operating system that has two important security features: ● Built-in protection against certain types of Denial of Service (DOS) attack, such a...
Page 231 - Root access; Remote access
Avaya Communication Manager and Servers Issue 6 January 2008 231 Root access On a Linux system, the highest administrative-access level is called root . Direct logins to root-level accounts are not permitted on Avaya servers. Administrative access, which requires root-level permissions, is handled t...
Page 232 - Secure access; Monitoring and alarming
Security 232 Avaya Application Solutions IP Telephony Deployment Guide Secure access Typical server access methods include telnet, Web browser (HTTP), and FTP for file transfers. Each of these mechanisms can support login authentication, but suffer a common weakness. The password that you type durin...
Page 233 - Data encryption
Avaya Communication Manager and Servers Issue 6 January 2008 233 Data encryption Attacks against a system are not limited to attempts to find holes in the access structure. Avaya servers store backup copies of critical configuration information, including authentication and account information, on e...
Page 235 - S8700-series Server with Avaya G650 Media Gateways
Avaya Communication Manager and Servers Issue 6 January 2008 235 Figure 73: Isolated LANs (Avaya S8700-series Server with an MCC1 or an SCC1 Media Gateway) Figure 73: Isolated LANs (Avaya S8700-series Server with an MCC1 or an SCC1 Media Gateway) on page 235 shows how Communication Manager can be co...
Page 236 - Virus and worm protection
Security 236 Avaya Application Solutions IP Telephony Deployment Guide Figure 74: Isolated LANs (Avaya S8700-series Server with a G650 Media Gateway) Virus and worm protection Viruses and worms are most often targeted at Microsoft Windows operating systems or such commonly used applications as IIS, ...
Page 237 - Testing; Recommendations for network security; Security Advisory
Avaya Communication Manager and Servers Issue 6 January 2008 237 Testing During the development of the S8300, S8500, and S8700-series Servers, or in production of upgrades to its software, Avaya subjects the system to a variety of common “attack tools” to find any overlooked or accidentally created ...
Page 238 - IP Telephony circuit pack security; Telnet
Security 238 Avaya Application Solutions IP Telephony Deployment Guide IP Telephony circuit pack security Avaya circuit packs such as those in the G650 Media Gateways have a variety of security measures that combine both voice and data security strategies in to a secure package.The G650 use three di...
Page 239 - FTP
IP Telephony circuit pack security Issue 6 January 2008 239 FTP An FTP service exists, but is disabled by default. Communication Manager must enable the FTP service, and only does so for firmware downloads. Once the FTP service is started, Communication Manager initiates the client-side of the FTP p...
Page 240 - Toll fraud
Security 240 Avaya Application Solutions IP Telephony Deployment Guide TN799DP Control LAN (C-LAN) The C-LAN circuit pack interface not only supports signaling for IP Telephony applications, but also supports asynchronous links to INTUITY AUDIX, Call Management System (CMS), and other adjuncts. This...
Page 241 - Hacking methods
Toll fraud Issue 6 January 2008 241 Avaya’s security design Telecommunications systems face significant and growing problems of theft of customer services. Toll fraud, the unauthorized use of a system and its facilities by a third party, can result in substantial additional charges for telecommunica...
Page 242 - Your toll fraud responsibilities
Security 242 Avaya Application Solutions IP Telephony Deployment Guide Your toll fraud responsibilities No telecommunications system can be entirely free from risk of unauthorized use. But diligent attention to system management and security can reduce that risk considerably. Often a trade-off is re...
Page 245 - Network delay
Issue 6 January 2008 245 Voice quality network requirements In addition to the influence of the telephony terminals at either end of a connection, there are several network parameters that can affect voice quality. This chapter lists some of the more important ones. The concept of voice quality has ...
Page 246 - Codec delay
Voice quality network requirements 246 Avaya Application Solutions IP Telephony Deployment Guide Some of the issues that must be considered when designing a network for VoIP are: ● One-way delays in excess of 250 ms can cause the well-known problem of "talk-over." This occurs when both parti...
Page 247 - Jitter; Packet loss
Jitter Issue 6 January 2008 247 Jitter Jitter is thought of as the statistical average variance of the arrival time between packets received from the IP network. To compensate for jitter, a de-jitter buffer is implemented in VoIP endpoints. The purpose of the jitter buffer is to hold incoming packet...
Page 248 - Network packet loss
Voice quality network requirements 248 Avaya Application Solutions IP Telephony Deployment Guide The effects of packet loss on VoIP service are multifold: ● Problems caused by occasional packet loss are difficult to detect because each codec has its own packet loss concealment method (PLC). Therefor...
Page 249 - Echo
Echo Issue 6 January 2008 249 Packet loss concealment (PLC) Some packet loss can be dealt with by attempting to conceal the loss by generating voice samples to take the place of the missing samples. ITU standards G.711 Annex I and the G.729 standard define methods by which packet loss concealment ca...
Page 250 - Signal levels
Voice quality network requirements 250 Avaya Application Solutions IP Telephony Deployment Guide Resource 320, the Avaya IP SoftPhone, and the Avaya 4600 Series IP Telephone all incorporate echo cancellation designed for IP Telephony to improve voice quality. Signal levels In order to provide more n...
Page 251 - Echo and Signal Levels; Codecs
Codecs Issue 6 January 2008 251 Echo and Signal Levels As mentioned before, in circuit-switched telephony, echo may be caused by acoustic reflection in the remote party's environment, or by electrical reflection from 2-to-4 wire analog hybrid impedance mismatches. Impedance mismatch can occur in ana...
Page 253 - Silence suppression/VAD; Codec
Silence suppression/VAD Issue 6 January 2008 253 ● 320 channels of V.32 SPRT The above channel counts are the same if AES encryption and SHA-1 authentication are enabled.The One-X Deskphones (96xx) support the G.722 codec with 64 kbps and with 20 ms packetsGenerally, G.711 is used on LANs because ba...
Page 254 - Transcoding/tandeming
Voice quality network requirements 254 Avaya Application Solutions IP Telephony Deployment Guide ● Avaya 4600 series IP Telephone ● Avaya IP SoftPhone ● Avaya Media Gateways For procedures to administer QoS parameters, refer to Administration for Network Connectivity for Avaya Communication Manager ...
Page 256 - Available application models
Voice quality network requirements 256 Avaya Application Solutions IP Telephony Deployment Guide Available application models Voice The voice model converts low level statistics (network delay, latency, and loss) into an APR score that takes into account voice requirements. Given the sensitivity of ...
Page 257 - Integrated Management overview documents; Avaya Integrated Management offers
Issue 6 January 2008 257 Avaya Integrated Management This chapter outlines Avaya’s system, network, and device management and monitoring products, and some common third-party tools. It also discusses the distributed and centralized management models, and describes how Avaya management products fit i...
Page 258 - Administration Tools Offer; VoIP Monitoring Management Offer
Avaya Integrated Management 258 Avaya Application Solutions IP Telephony Deployment Guide Administration Tools Offer Administration Tools is a Microsoft Windows solution for Avaya Integrated Management. It is designed for small-to-medium size networks that run Microsoft Windows platforms. The Avaya ...
Page 259 - Enterprise Network Management Offer
Avaya Integrated Management offers Issue 6 January 2008 259 Enterprise Network Management Offer Enterprise Network Management is a Microsoft Windows solution for Avaya Integrated Management. It is designed for VoIP networks of any size that run Microsoft Windows platforms.It provides a complete conv...
Page 260 - Third-party network management products; Multi Router Traffic Grapher
Avaya Integrated Management 260 Avaya Application Solutions IP Telephony Deployment Guide voice and data network from a central location; and manage the Avaya network server and IP endpoints. Note: Note: The most current release of the System Management offer is Release 3.2. System Management Releas...
Page 261 - HP OpenView Network Node Manager; Network management models
Network management models Issue 6 January 2008 261 ● Monitors any SNMP variable that you choose. You can even use an external program to gather the data that MRTG should monitor, for example: - System load - Login sessions - Modem availability For more MRTG information, see: ● http://www.mrtg.org fo...
Page 262 - Figure 76: Tools for distributed network management
Avaya Integrated Management 262 Avaya Application Solutions IP Telephony Deployment Guide Distributed (component) Distributed network management is the default management model for network equipment. As Figure 76 shows, each device is managed separately, and can have its own management interface. Th...
Page 263 - Figure 77: Centralized management model
Network management models Issue 6 January 2008 263 Figure 77: Centralized management model Additional management tools, such as Avaya Network Management Console with VoIP SystemView, attach to the framework ( Figure 77 ). They can be launched directly from the underlying application, and can share d...
Page 265 - Reliability and Recovery
Issue 6 January 2008 265 Reliability and Recovery The purpose of this chapter is to provide the reader an overview of the subject of communication-system “availability,” specific to Avaya Communication Manager and Avaya servers and gateways. The discussion that follows demonstrates Avaya’s long-stan...
Page 266 - Reliability
Reliability and Recovery 266 Avaya Application Solutions IP Telephony Deployment Guide Reliability Customers need the full reliability of their traditional voice networks, including feature richness and robustness, and they want the option of using converged voice and data infrastructures. With the ...
Page 267 - Survivability solutions
Survivability solutions Issue 6 January 2008 267 Use the indicated links to access these documents on the Avaya Support web site. Survivability solutions Avaya Communication Manger release 3.0 introduces new features in support of enhancing high availability and survivability. These features are in ...
Page 268 - S8700-series Server Separation
Reliability and Recovery 268 Avaya Application Solutions IP Telephony Deployment Guide Figure 78: Release 3.0 system example S8700-series Server Separation S8700-series server separation allows the two servers in an S8700-series Server pair to be geographically separated up to a maximum distance of ...
Page 270 - ESS System Capacities
Reliability and Recovery 270 Avaya Application Solutions IP Telephony Deployment Guide ESS System Capacities ESS can be administered as “local only” or as an “enterprise-wide” survivable server(s). When administered as “Local only”, which indicates it will act as the survivable server for a communit...
Page 271 - Connection preserving upgrades for duplex servers
Survivability solutions Issue 6 January 2008 271 Connection preserving upgrades for duplex servers This feature is designed for preserving stable bearer connections for TDM end points and IP stations during an upgrade of S8700/S8710 duplex servers. TDM and IP connection of H.248 Media Gateways, with...
Page 272 - Survivability for branch office media gateways; H.248 Media Gateway recovery via LSP
Reliability and Recovery 272 Avaya Application Solutions IP Telephony Deployment Guide IGAR relies on Call Admission Control. When all VoIP RTP resources have been used the next attempt to get a VoIP RTP resource results in denial of the VoIP connection. Communication Manager 3.0 will attempt to use...
Page 274 - The auto fallback process
Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide The auto fallback process While LSP is the acting call controller, the Media Gateway attempts to register with the primary server every 30 seconds or whenever there are no active calls (this signaling also acts as...
Page 275 - IP endpoint recovery; IP endpoint recovery
IP endpoint recovery Issue 6 January 2008 275 The link recovery process follows these steps: 1. While SLS is enabled and processing, the media gateway continues to seek an alternative media gateway controller. 2. If Avaya Communication Manager accepts the registration then the active IP to IP calls ...
Page 276 - Recovery algorithm
Reliability and Recovery 276 Avaya Application Solutions IP Telephony Deployment Guide A C-LAN provides two basic reliability functions: ● A C-LAN hides server interchanges from the IP endpoints. The signaling channels of the endpoints remain intact during server interchanges, and do not have to be ...
Page 277 - IP Endpoint Time to Service
IP endpoint recovery Issue 6 January 2008 277 While the LSP is not call preserving, the fail-over from primary gatekeeper to LSP is an automatic process, and does not require human intervention. The fail-back from LSP to primary gatekeeper, however, is not currently automatic, and requires a system ...
Page 278 - Changes in IP end points; Converged Network Analyzer for network optimization
Reliability and Recovery 278 Avaya Application Solutions IP Telephony Deployment Guide If re-registration is not required, only the re-establishment of the TCP socket is needed, which is also done in an on-demand fashion. Currently, in a call center environment, the agents must always log-in again w...
Page 283 - IP Telephony network engineering overview
Issue 6 January 2008 283 IP Telephony network engineering overview In the early days of local area networking, network designers used hubs to attach servers and workstations, and routers to segment the network into manageable pieces. Because of the high cost of router interfaces and the inherent lim...
Page 285 - Voice quality
Voice quality Issue 6 January 2008 285 The following WAN technologies are commonly used with IP Telephony: ● MPLS (Multiprotocol Label Switching) ● ATM (Asynchronous Transfer Mode) ● Frame Relay ● Point-to-point (PPP) circuits ● Internet VPNs The first four technologies all have good throughput, low...
Page 287 - Best practices; Switched network; VLANs
Best practices Issue 6 January 2008 287 The Converged Network Analyzer (CNA) can help you measure and report on network delay, jitter, and packet loss. CNA can also provide you with a rating of voice quality using the 0-5 APR score (see CNA Application Performance Rating on page 254). With the optio...
Page 288 - Common issues; Multiple subnets on a VLAN; Too many access lists
IP Telephony network engineering overview 288 Avaya Application Solutions IP Telephony Deployment Guide Common issues Some common negative practices that can severely impact network performance, especially when using IP Telephony, include: ● A flat, non-hierarchical network , for example, cascading ...
Page 289 - Network design; LAN issues; General guidelines
Issue 6 January 2008 289 Network design This section discusses the network design process for IP Telephony. This section focuses on: ● LAN issues ● WAN ● VPN ● NAT LAN issues This section covers Local Area Network (LAN) issues, including speed and duplex, inline power, hubs versus switches, and so o...
Page 290 - Ethernet switches
Network design 290 Avaya Application Solutions IP Telephony Deployment Guide Ethernet switches The following recommendations apply to Ethernet switches to optimize operation with Avaya endpoints. Theses recommendations are meant to provide the simplest configuration by removing unnecessary features....
Page 291 - VLAN defined; show trunk
LAN issues Issue 6 January 2008 291 VLANs Virtual Local Area Networks (VLANs) are an often-misunderstood concept. This section begins by defining VLANs, and then addresses configurations that require the Avaya IP Telephone to connect to an Ethernet switch port that is configured for multiple VLANs. ...
Page 292 - Trunk configuration
Network design 292 Avaya Application Solutions IP Telephony Deployment Guide Trunk configuration A trunk port on an Ethernet switch is one that is capable of forwarding Ethernet frames on multiple VLANs through the mechanism of VLAN tagging. IEEE 802.1Q specifies the standard method for VLAN tagging...
Page 293 - set; WAN
WAN Issue 6 January 2008 293 e. Apply the configured VLANs to the port, and permit only those VLANs (bind-to-all permits all VLANs and not just the configured) by typing set port vlan-binding-mode <mod/ port> bind-to-configured 3. For simplicity, Avaya recommends using the static option for IP...
Page 294 - QoS; Recommendations for QoS; Codec selection and compression
Network design 294 Avaya Application Solutions IP Telephony Deployment Guide Overview QoS In particular, Quality of Service (QoS) becomes more important in a WAN environment than in a LAN. In many cases, transitioning from the LAN to the WAN reduces bandwidth by approximately 99%. Because of this se...
Page 295 - Serialization delay; Routing protocols and convergence
WAN Issue 6 January 2008 295 To conserve even more bandwidth, RTP header compression (cRTP) can be used on point-to-point links. cRTP reduces the IP/UDP/RTP overhead from 40 bytes to 4 bytes. With 20-ms packets, this translates to a savings of 14.4 Kbps, making the total bandwidth required for G.729...
Page 296 - Multipath routing; Overview of frame relay
Network design 296 Avaya Application Solutions IP Telephony Deployment Guide Multipath routing Many routing protocols, such as OSPF, install multiple routes for a particular destination into a routing table. Many routers attempt to load-balance across the two paths. There are two methods for load ba...
Page 297 - A frame relay issue and alternatives
WAN Issue 6 January 2008 297 Figure 79: Data-link connection identifiers over an interexchange carrier Frame Relay network This hypothetical implementation shows the Dallas corporate office connected to three branch offices in a common star topology (or hub and spoke). Each office connects to a LEC ...
Page 298 - Additional frame relay information; MPLS
Network design 298 Avaya Application Solutions IP Telephony Deployment Guide As Figure 80: Committed information rate (burst range) shows, traffic up to the CIR is guaranteed, whereas traffic beyond the CIR usually is not. This is how Frame Relay is intended to work. CIR is a committed and reliable ...
Page 299 - VPN; Convergence advantages
VPN Issue 6 January 2008 299 VPN Many definitions exist for Virtual Private Networks (VPNs). VPNs refer to encrypted tunnels that carry packetized data between remote sites. VPNs can use private lines, or use the Internet through one or more Internet Service Providers (ISPs). VPNs are implemented in...
Page 300 - Managing IP Telephony VPN issues; Communication security
Network design 300 Avaya Application Solutions IP Telephony Deployment Guide Managing IP Telephony VPN issues This section provides information on communications security, firewall technologies, and network management as related to VPN issues. Communication security The public nature of the Internet...
Page 301 - Firewall technologies; Enterprise based; Shared management
VPN Issue 6 January 2008 301 Firewall technologies To reduce security risks, appropriate network access policies should be defined as part of business strategy. Firewalls can be used to enforce such policies. A firewall is a network interconnection element that polices traffic the flows between inte...
Page 302 - Conclusion
Network design 302 Avaya Application Solutions IP Telephony Deployment Guide Conclusion Moving to a multipurpose packet-based VPN that transports both voice and data with high quality poses a number of significant management challenges. Managers must determine whether to operate the network using an...
Page 303 - Figure 81: IP Telephony without NAT
NAT Issue 6 January 2008 303 Solutions based on future standards ICE and STUN are expected to be supported in some NAT traversal scenarios where applicable. Figure 81: IP Telephony without NAT
Page 304 - Converged network design; Design and Management; Design for Simplicity
Network design 304 Avaya Application Solutions IP Telephony Deployment Guide Converged network design Converged networks require the application of good management and control practices to support and sustain the deployment of IP telephony. The first step in implementing an IP telephony system is ma...
Page 305 - Design for Manageability
Converged network design Issue 6 January 2008 305 train. A conscious choice to favor simplicity in design may be the single biggest factor in improving uptime due to its cascading effect on process, documentation and verification. Design for Manageability Studies of operator errors have identified s...
Page 306 - Topologies; Figure 82: Typical Network Topology Design; Server Cluster
Network design 306 Avaya Application Solutions IP Telephony Deployment Guide Topologies The network topology most commonly recommended consists of a redundant core with building blocks of layered routers and switches as shown in the figure below. This is the defacto standard for network design suppo...
Page 307 - Figure 83: Layered Server Cluster Topology; Layers
Converged network design Issue 6 January 2008 307 Figure 83: Layered Server Cluster Topology Assume that each G650 is equipped with redundant TN2602AP Media Resource 320 circuit packs optionally configured for load balancing or IP bearer duplication. Each G650 is also assumed to contain duplicated T...
Page 308 - Figure 84: Integrated high density switch topology; Redundancy
Network design 308 Avaya Application Solutions IP Telephony Deployment Guide configuration complexity with little benefit in terms of availability unless the subnets terminate on different routers, which in turn implies separate modular clusters. An argument can be made that separate subnets simplif...
Page 309 - Figure 85: Redundant connections
Converged network design Issue 6 January 2008 309 Figure 85: Redundant connections It is good practice to have the redundant boards of each PN connected to redundant Layer 2 switches as shown to protect each PN from failure of the Layer 2 switch itself. If asymmetric redundancy is configured through...
Page 310 - Layer 2
Network design 310 Avaya Application Solutions IP Telephony Deployment Guide Layer 2 Layer 2 configuration of the switches supporting the cluster should use IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) to prevent loops and for selection between redundant links. Most modern switches implement this...
Page 311 - Figure 86: Sample spanning tree
Converged network design Issue 6 January 2008 311 Figure 86: Sample spanning tree If the primary router fails, the secondary router becomes both the active router and the root bridge, and traffic from the switches flows on the reconfigured spanning tree along links C & D. If bridge priorities ar...
Page 312 - Figure 88: VRRP configured for Core Access
Network design 312 Avaya Application Solutions IP Telephony Deployment Guide Layer 3 The symmetric or asymmetric question is linked to the configuration of redundancy for the routers serving this cluster. If the single subnet model is used, the router configuration in the direction of the cluster wi...
Page 313 - References for
Converged network design Issue 6 January 2008 313 References for Converged network design on page 304 1. Infonetics 2/11/2004. 2. Network World 10/26/2004. 3. DMreview 2/18/2004. 4. Medium businesses lose $867,000 a year to network downtime 3/09/2006. 5. Gartner Research 7/03/2001. 6. Understanding ...
Page 315 - CoS
Issue 6 January 2008 315 Quality of Service guidelines This chapter contains guidelines for deploying Quality of Service (QoS) for an IP Telephony network. This chapter begins with an overview of Class of Service (CoS) versus QoS. Class of Service refers to mechanisms that tags traffic in such a way...
Page 316 - Table 52: Comparison of DSCP with original TOS
Quality of Service guidelines 316 Avaya Application Solutions IP Telephony Deployment Guide Note that the 802.1Q tag changes the size and the format of the Ethernet frames. Because of this, many switches must be explicitly configured to accept 802.1Q tagged frames. Otherwise, these switches might re...
Page 317 - Layer 2 QoS
Layer 2 QoS Issue 6 January 2008 317 Layer 2 QoS On Avaya and Cisco switches, IP Telephony traffic can be assigned to higher priority queues. The number and the sizes of queues and how the queues function are device dependent, and beyond the scope of this document.However, in general, a fixed number...
Page 318 - QoS guidelines; Serialization Delay
Quality of Service guidelines 318 Avaya Application Solutions IP Telephony Deployment Guide serialization delay for a variety of packet sizes and line speeds. The formula for determining serialization delay is: Because of all these configuration variables, properly implementing QoS on a router is no...
Page 321 - DiffServ; Table 54: IEEE 802.1 precedence and service mapping
DiffServ Issue 6 January 2008 321 Recommendations for end-to-end QoS When end-to-end QoS is desired, Avaya recommends using DiffServ , a Layer 3 CoS method. Modern routers can map DiffServ Code Points (DSCP) to 802.1p priority values, so 802.1p tags can be recreated on each Ethernet link. This funct...
Page 323 - RSVP; Table 55: Original TOS specification
RSVP Issue 6 January 2008 323 policy. The TOS byte is an OSI model Layer 3 solution, and works on IP packets on the LAN and possibly the WAN, depending upon the service provider. RSVP Resource Reservation Protocol (RSVP) is a protocol that hosts can use to request specific QoS parameters through the...
Page 324 - Queuing methods; WFQ
Quality of Service guidelines 324 Avaya Application Solutions IP Telephony Deployment Guide to the better-than-best-effort (BBE) DSCP that is defined on the network region form. By default, this value is 43.If RSVP is enabled on a network region, it is very important that it also be enabled on assoc...
Page 326 - Traffic shaping and policing; Frame Relay traffic shaping
Quality of Service guidelines 326 Avaya Application Solutions IP Telephony Deployment Guide Traffic shaping and policing Traffic shaping is a mechanism to reduce the rate at which data is transmitted over an interface. When people discuss traffic shaping, they are usually referring to the related te...
Page 327 - Fragmentation; MTU
Fragmentation Issue 6 January 2008 327 Thus, the complete configuration for Frame Relay traffic shaping looks like: map-class frame-relay NoBurst no frame-relay adaptive shaping frame-relay cir 384000! (for a 384K CIR) frame-relay mincir 384000 frame-relay be 0 frame-relay bc 3840 interface serial 0...
Page 328 - LFI; RTP; Application perspective
Quality of Service guidelines 328 Avaya Application Solutions IP Telephony Deployment Guide *0.01 second (10 ms)/8 bits/byte = 480 bytes. As the circuit size diminishes, however, care should be taken to never reduce the MTU below 200 bytes. Below that size, telephony signaling and bearer (voice) pac...
Page 329 - Network perspective; Recommendations for RTP header compression; IP header
RTP Issue 6 January 2008 329 It is important to understand that all 20-ms G.729 audio packets, regardless of the vendor, are constructed like this. Not only is the structure of the packet the same, but the method of encoding and decoding the audio itself is also the same. This sameness is what allow...
Page 330 - RTP header compression test
Quality of Service guidelines 330 Avaya Application Solutions IP Telephony Deployment Guide RTP header compression test This section details the results of a simple RTP header compression test that was conducted in a laboratory environment. Although this test was conducted using Cisco routers, the e...
Page 331 - Configuration; ip rtp compression-connections
RTP Issue 6 January 2008 331 For each codec, there was an attempt to verify that the audio packets were received intact. This was done by spot checking the audio packets before and after compression, using two Sniffer protocol analyzers. For every codec except G.711, the RTP header and payload were ...
Page 332 - Examples of QoS implementation
Quality of Service guidelines 332 Avaya Application Solutions IP Telephony Deployment Guide See the Cisco documentation for more specific configurations on other types of WAN links (that is, Frame Relay and ATM). Configuration for the X330WAN router is very similar to Cisco, and is well documented i...
Page 333 - Figure 92: High-quality service across a congested WAN link; Assumptions for Example 1
Examples of QoS implementation Issue 6 January 2008 333 Figure 92: High-quality service across a congested WAN link CB-WFQ/LLQ is a priority-aware queuing strategy that has a strict priority queue for voice packets, and does round-robin queuing for other types of traffic. Non-prioritized traffic is ...
Page 334 - Administration commands for Example 1; Table 58: Administration commands for Example 1; Command; description T1 ip address
Quality of Service guidelines 334 Avaya Application Solutions IP Telephony Deployment Guide Administration commands for Example 1 Table 58: Administration commands for Example 1 Command Meaning 1.class-map match-any VoIP Create a class map called “VoIP.” 2.match ip dscp 46 Any packet with DSCP 46 is...
Page 335 - Example 2: C-LANS cannot tag their traffic; Assumptions for Example 2; Table 59: Administration commands for Example 2; untaggedVoIP
Examples of QoS implementation Issue 6 January 2008 335 Example 2: C-LANS cannot tag their traffic Assumptions for Example 2 ● The C-LANs 192.168.1.10 and.11 cannot tag their traffic (TN-799C or earlier). ● The configuration commands in Table 59 are applied only to the left router. Administration co...
Page 336 - Example 3: More restrictions on the traffic; Assumptions for Example 3; Table 60: Administration commands for Example 3; VoIP
Quality of Service guidelines 336 Avaya Application Solutions IP Telephony Deployment Guide Example 3: More restrictions on the traffic Assumptions for Example 3 ● DSCP 46 is used throughout to simplify the access list. ● A somewhat matching set of configurations is applied to both routers. Administ...
Page 337 - Converged infrastructure LAN switches; description T1 ip; Table 61: X330 WAN Module administration commands; local
Examples of QoS implementation Issue 6 January 2008 337 If any of the endpoints are incapable of tagging, the “dscp 46” can be removed from access list 101. Then any traffic between the two IP Telephony subnetworks, regardless of the tag, is in the class “VoIP.” Converged infrastructure LAN switches...
Page 338 - FabricFastEthernet 1
Quality of Service guidelines 338 Avaya Application Solutions IP Telephony Deployment Guide 5.ip access-list-dscp trust 100 trust-cos-dscp Trust packet tagging. 6.interface FabricFastEthernet 1 Activate the above mapping on ingress traffic to the Fabric Fast Ethernet interface 7.ip access-group 100 ...
Page 339 - Network recovery; Change control
Issue 6 January 2008 339 Network recovery Conventional wisdom holds that network reliability is typically 3-9s (99.9%) on a LAN, and 2-9s (99%) on a WAN. The leading causes of network failure are a WAN link failure, administrator error, cable failure, issues that involve connecting new devices or se...
Page 340 - Layer 2 mechanisms to increase reliability; Spanning tree
Network recovery 340 Avaya Application Solutions IP Telephony Deployment Guide Layer 2 mechanisms to increase reliability Spanning tree IEEE 802.1D spanning tree is an Ethernet loop avoidance protocol. It allows network managers to connect redundant network links within their networks. Prior to the ...
Page 341 - Layer 3 availability mechanisms; Routing protocols; VRRP and HSRP
Layer 3 availability mechanisms Issue 6 January 2008 341 Layer 3 availability mechanisms Routing protocols Routing protocols allow routers to dynamically learn the topology of the network. Should the topology of the network change, routing protocols update their internal topology table, which allows...
Page 342 - Dial backup
Network recovery 342 Avaya Application Solutions IP Telephony Deployment Guide Multipath routing Modern routers and Layer 3 switches allow multiple routes for a particular destination to be installed in the routing table. Depending on the implementation, this can be as high as six routes. Some imple...
Page 343 - Convergence times; Protocol
Convergence times Issue 6 January 2008 343 Convergence times Convergence is the time that it takes from the instant a failure occurs in the network until a new path through the network is discovered, and all routers or switches are aware of the new path. Convergence times vary, based on the complexi...
Page 344 - Visibility
Network recovery 344 Avaya Application Solutions IP Telephony Deployment Guide The Converged Network Analyzer The Converged Network Analyzer (CNA) is an offer from the Avaya Application Assurance Networking (AAN) line of products. It provides two principal value propositions: ● visibility ● path opt...
Page 346 - CNA components
Network recovery 346 Avaya Application Solutions IP Telephony Deployment Guide (Routers R1a, R1b, R1c), and on the branch side (R2a, R2b, and R2c); these routers would then have been able move the traffic to Path B or Path C. In practice, however, some dynamic routing protocols such as Border Gatewa...
Page 347 - Simultaneous monitoring of all paths; Figure 94: Headquarters CNA deployment – Measurement plane
The Converged Network Analyzer Issue 6 January 2008 347 Sites A and B will move away from the outage in less than a second, preventing unintelligibility in the audio bearer, or outages in the voice signaling. Simultaneous monitoring of all paths The ability for CNA to measure all paths simultaneousl...
Page 348 - Controlling edge routers; Configuration and deployment details
Network recovery 348 Avaya Application Solutions IP Telephony Deployment Guide Controlling edge routers CNA maintains a BGP peering with every edge device it needs to control. It is configured as a route reflector to the edge devices, which allows it to (1) receive state of the routing table from th...
Page 349 - Network assessment offer; Problems with data networks
Issue 6 January 2008 349 Network assessment offer Avaya Communication Solutions and Integration (CSI) supports a portfolio of consulting and engineering offers to help plan and design: ● IP Telephony ● Data Networking Services ● Network Security Services. How to contact the CSI ● On the Web — CSI ● ...
Page 350 - What if my network functions well today?
Network assessment offer 350 Avaya Application Solutions IP Telephony Deployment Guide Note: Note: The Basic Network Readiness Assessment Service is available in the U.S. and Canada through direct and indirect channels. ● Detailed network readiness assessment service is typically the second phase in...
Page 351 - Site Configuration Survey; Table 63: Basic Network Readiness Assessment Service components
Avaya network readiness assessment services Issue 6 January 2008 351 Site Configuration Survey The ECLIPS Site Configuration Survey (SCS) is an detailed customer-view of the their network. This survey is required as part of the Customer Infrastructure Readiness Survey process. The ECLIPS SCS questio...
Page 352 - Vital Agent analysis
Network assessment offer 352 Avaya Application Solutions IP Telephony Deployment Guide Vital Agent analysis Vital Agent is a high-level analysis tool that passively monitors and reports throughput and performance statistics and errors and reports any problems that the host computer encounters. The c...
Page 353 - The Detailed network readiness assessment process
Avaya network readiness assessment services Issue 6 January 2008 353 Use these links for more information about the Detailed network readiness assessment service components: ● The Detailed network readiness assessment process ● Customer responsibilities ● Discovery ● Element monitoring ● Synthetic I...
Page 354 - Component
Network assessment offer 354 Avaya Application Solutions IP Telephony Deployment Guide Table 64: Detailed network readiness assessment service components Component Who does this? What does this do? What are the results? What happens with the results? Network Topology Report Customer (may already be ...
Page 355 - Customer responsibilities
Avaya network readiness assessment services Issue 6 January 2008 355 Customer responsibilities In order to successfully complete a Detailed network readiness assessment the customer must: ● Provide technical resource personnel who are well-versed in the network infrastructure. ● Provide complete acc...
Page 356 - Synthetic IP Telephony measurements; Remote analysis; Report generation
Network assessment offer 356 Avaya Application Solutions IP Telephony Deployment Guide Synthetic IP Telephony measurements ● Inject busy hour IP Telephony call traffic simulation into live network segments ● Random CODECs and injection points between pre-defined end points/hosts ● Injections initial...
Page 357 - Customer deliverables
Avaya network readiness assessment services Issue 6 January 2008 357 Customer deliverables ● Avaya networking experts perform discovery of the customer’s network and document findings in a Detailed Network Readiness Assessment Report delivered to the customer. ● Accurate network topology ● Measureme...
Page 359 - Figure 95: Detailed configuration scenario
Issue 6 January 2008 359 Appendix A: CNA configuration and deployment This section provides detailed CNA configuration procedures for the scenario shown in Figure 95 . For the purpose of generality, we assume two routers and three paths. Figure 95: Detailed configuration scenario
Page 360 - Configuring CNA; Basic configuration; Configuring Virtual Module Interfaces; configure terminal; Ethernet Interfaces on Modules; Default Gateway
CNA configuration and deployment 360 Avaya Application Solutions IP Telephony Deployment Guide Configuring CNA Basic configuration Configuring Virtual Module Interfaces Avaya CNA Ethernet interfaces need to be associated with an Ethernet interface and a physical connection to the network. Once the s...
Page 361 - Service Provider Access Links; link; BGP on the Engine Module
Configuring CNA Issue 6 January 2008 361 Service Provider Access Links Each service provider that is to be managed or monitored by Avaya CNA needs a link object defined. From config mode, enter engine configuration mode: module engine To associate a service provider with a link name, create the link...
Page 362 - Assigning USTATs to Providers; USTAT GRE Tunnels; Measurements
CNA configuration and deployment 362 Avaya Application Solutions IP Telephony Deployment Guide Assigning USTATs to Providers module usta t commands now need to be defined for each WAN link: module ustat provider_1 link provider_1 vip 172.25.5.1 The ustat module specifies the association of the USTAT...
Page 363 - Decision making
Configuring CNA Issue 6 January 2008 363 Prefix bearer_1/32 Prefix bearer_2/32 end module engine active-measurement group AM_signaling_targets type icmp rate 5 per-second timeout 200 target group bearer_targets end active-measurement group AM_bearer_targets type icmp rate 5 per-second timeout 200 ta...
Page 364 - Configuring the Routers; Edge Router GRE Tunnel Interfaces
CNA configuration and deployment 364 Avaya Application Solutions IP Telephony Deployment Guide route-assert-filter force decision-policy DP_signaling_targets set-application-model enterprise damped-mode disable end decision-policy DP_bearer_targets set-application-model voice damped-mode disable end...
Page 365 - Route Maps
Configuring the Routers Issue 6 January 2008 365 These are the IOS commands needed to set up the GRE tunnel interface on Ra (see Figure 95 ): interface Tunnel1 description GRE to provider_1 ip address 172.25.5.129 255.255.255.252 ip policy route-map provider_1 tunnel source 172.16.6.1 tunnel destina...
Page 366 - Routing Configuration; IBGP
CNA configuration and deployment 366 Avaya Application Solutions IP Telephony Deployment Guide These commands will have to be repeated for each USTAT module/ISP pair; at which point the configuration would model the network shown in Figure 95 . Routing Configuration Here, the routing to the USTAT VI...
Page 367 - Route Reflection
Configuring the Routers Issue 6 January 2008 367 Route Reflection The CNA system must be a route reflector client to all of the edge routers that will operate within the CNA system’s sphere of influence. When multiple edge routers are being configured for route reflection, a BGP cluster ID is requir...
Page 368 - Command summary; CNA commands
CNA configuration and deployment 368 Avaya Application Solutions IP Telephony Deployment Guide Command summary All of the CNA and router configuration commands described in this document are listed in this section. For more information, please refer to the CNA administrative guide. CNA commands inte...
Page 370 - Router Ra commands
CNA configuration and deployment 370 Avaya Application Solutions IP Telephony Deployment Guide vip 172.25.5.1 ip route 10.6.0.1 255.255.255.255 172.16.6.1 ip route 0.0.0.0 0.0.0.0 tunnel1 end module ustat provider_2 link provider_2 vip 172.25.5.2 ip route 10.6.0.2 255.255.255.255 172.16.6.2 ip route...
Page 371 - Router Rb commands
Command summary Issue 6 January 2008 371 neighbor 172.16.6.4 route-reflector-client neighbor 172.16.6.4 soft-reconfiguration inbound neighbor 172.16.6.4 weight 200 Router Rb commands interface Tunnel2 description GRE to provider_2 ip address 172.25.5.133 255.255.255.252 ip policy route-map provider_...
Page 373 - Numerical
Issue 6 January 2008 373 Index Index Numerical 1152A1 Power Unit . . . . . . . . . . . . . . . . 169 A ACM, see Avaya Communication Manager Alarms and troubleshooting . . . . . . . . . . . . . 52 API . . . . . . . . . . . . . . . . . . . . . . . . 160 ASB button G250 . . . . . . . . . . . . . . . . ...