Avaya 555-245-600 User Manual
Avaya Application Solutions:
IP Telephony Deployment Guide
555-245-600
Issue 6
January 2008
© 2008 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.
For full legal page information, please see the documents,
Avaya Support Notices for Software Documentation, 03-600758, and
Avaya Support Notices for Hardware Documentation, 03-600759.
These documents can be accessed on the documentation CD and on the
Web site, http://www.avaya.com/support
document number in the Search box.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, or deletions to
the original published version of this documentation unless such modifications,
additions, or deletions were performed by Avaya. Customer and/or End User
agree to indemnify and hold harmless Avaya, Avaya's agents, servants and
employees against all claims, lawsuits, demands and judgments arising out of,
or in connection with, subsequent modifications, additions or deletions to this
documentation to the extent made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web
sites referenced elsewhere within this documentation, and Avaya does not
necessarily endorse the products, services, or information described or offered
within them. We cannot guarantee that these links will work all of the time and
we have no control over the availability of the linked pages.
Warr anty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the following Web site:
http://www.avaya.com/support
Copyright
Except where expressly stated otherwise, the Product is protected by copyright
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense under the
applicable law.
Avaya support
Avaya provides a telephone number for you to use to report problems or to ask
questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site: http://www.avaya.com/support
.
. On the Web site, search for the
.
Contents
About This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Using this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Downloading this book and updates from the Web . . . . . . . . . . . . . . . . . 12
Related resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Technical assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Within the US. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Sending us comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Section 1: Avaya Application Solutions
product guide . . . . . . . . . . . . . . . . . . . . . . . 15
Avaya Application Solutions . . . . . . . . . . . . . . . . . . . . . . . . 17
Avaya Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Avaya servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Avaya Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Avaya Integrated Management . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Avaya communication devices . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Avaya Communication Manager applications . . . . . . . . . . . . . . . . . . 21
Avaya SIP solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Avaya SIP application enablement . . . . . . . . . . . . . . . . . . . . . . . . 22
Avaya Distributed Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Distributed Office Configurations . . . . . . . . . . . . . . . . . . . . . . . . 24
Distributed Office benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Distributed Office implementation . . . . . . . . . . . . . . . . . . . . . . . . 26
Streamlined Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Avaya Application Solutions platforms . . . . . . . . . . . . . . . . . . 33
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Small to mid-size enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Avaya S8300 Server and Avaya G700, G450,
G350, or G250 Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . 37
G450 Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
G250 and G350 Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . 52
G150 Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Issue 6 January 2008 3
IG550 Integrated Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
TGM550 physical description . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Avaya S8400 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Mid-market to large enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
S8500 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Avaya S8700-series Server, fiber-PNC configuration . . . . . . . . . . . . . . 79
Avaya S8700-series Server IP-PNC configuration . . . . . . . . . . . . . . . . 96
Combined IP and fiber Port Network Connectivity . . . . . . . . . . . . . . . 102
Processor Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Avaya IP Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Greenfield deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Components needed for Greenfield deployment . . . . . . . . . . . . . . . . . . 109
Servers (H.323 Gatekeeper) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Avaya Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . 111
Media Gateways and Port Networks . . . . . . . . . . . . . . . . . . . . . . . 111
Greenfield configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
S8300 standalone solution
(small-to-midsize enterprise) . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Medium-to-large enterprise solutions . . . . . . . . . . . . . . . . . . . . . . 113
Required circuit packs for S8700-series configuration . . . . . . . . . . . . . 116
Evolution from circuit-switched to IP . . . . . . . . . . . . . . . . . . . 119
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Migration from DEFINITY
Server R to S8700 fiber-PNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Phase 1: Processor replacement . . . . . . . . . . . . . . . . . . . . . . . . . 120
Phase 2: IP-enable the Port Networks to support IP endpoints . . . . . . . . 122
Phase 3: Server consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Call processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Voice and multimedia networking . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Intelligent networking and call routing . . . . . . . . . . . . . . . . . . . . . . 125
IP Port Network / Media Gateway connectivity . . . . . . . . . . . . . . . . . 126
H.248 Media Gateway control . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Communication Manager gatekeepers . . . . . . . . . . . . . . . . . . . . . . 127
Call signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Media stream handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Separation of Bearer and Signaling (SBS) . . . . . . . . . . . . . . . . . . . . 130
4 Avaya Application Solutions IP Telephony Deployment Guide
Multi-location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Modem/Fax/TTY over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
IP-based trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
IP tie trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Trunk signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Avaya SIP Enablement Services (SES). . . . . . . . . . . . . . . . . . . . . . 135
Communication Manager as the SIP Feature Server . . . . . . . . . . . . . . 137
SIP Adjuncts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
SIP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
SIP deployment scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Avaya G860 Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
G860 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Configuration with Avaya Communication Manager . . . . . . . . . . . . . . 150
Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
IP Telephones or IP Softphones . . . . . . . . . . . . . . . . . . . . . . . . . 152
Extension to Cellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Communication applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Call Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Unified Communication Center . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Avaya Call Management System (CMS) . . . . . . . . . . . . . . . . . . . . . 155
Conferencing systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Meet-me conferencing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Avaya Meeting Exchange Solutions . . . . . . . . . . . . . . . . . . . . . . . 156
Computer Telephony Integration (CTI) . . . . . . . . . . . . . . . . . . . . . . 160
Application Programming Interfaces (APIs) . . . . . . . . . . . . . . . . . . . 160
Best Services Routing (BSR) polling . . . . . . . . . . . . . . . . . . . . . . . 161
LAN switching products . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Avaya C360 converged stackable switches . . . . . . . . . . . . . . . . . . . . . 163
Features of the C360 converged stackable switches . . . . . . . . . . . . . . 164
Switches from Extreme Networks . . . . . . . . . . . . . . . . . . . . . . . . 167
Avaya Power over Ethernet (PoE) switches . . . . . . . . . . . . . . . . . . . 168
Midspan Power Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
1152A1 Power Distribution Unit . . . . . . . . . . . . . . . . . . . . . . . . . 169
1152B Power Distribution Units . . . . . . . . . . . . . . . . . . . . . . . . . 171
Converged infrastructure security gateways . . . . . . . . . . . . . . . . . . . . 172
VPN Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Issue 6 January 2008 5
Section 2: Deploying IP Telephony . . . . . . . . . . . . . . . . . . 175
Traffic engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Design inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Endpoint specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Endpoint traffic usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Call usage rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Communities of interest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Expanded COI matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
COIs for multiple-site networks. . . . . . . . . . . . . . . . . . . . . . . . . . 197
Resource sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Signaling resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Media processing and TDM resources . . . . . . . . . . . . . . . . . . . . . . 200
Processing occupancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
SIP traffic engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
IP bandwidth and Call Admission Control . . . . . . . . . . . . . . . . . . . . 216
Physical resource placement . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Final checks and adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Avaya Distributed Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Your security policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Avaya Communication
Manager and Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
LAN isolation configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Virus and worm protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
IP Telephony circuit pack security . . . . . . . . . . . . . . . . . . . . . . . . . . 238
TN2312BP IP Server Interface (IPSI) . . . . . . . . . . . . . . . . . . . . . . . 238
TN2302AP and TN2602AP Media Processors . . . . . . . . . . . . . . . . . . 239
TN799DP Control LAN (C-LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Toll fraud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Avaya’s security design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Hacking methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Your toll fraud responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Toll fraud indemnification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Additional toll fraud resources . . . . . . . . . . . . . . . . . . . . . . . . . . 242
6 Avaya Application Solutions IP Telephony Deployment Guide
Voice quality network requirements . . . . . . . . . . . . . . . . . . . . 245
Network delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Codec delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Network packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Packet loss concealment (PLC). . . . . . . . . . . . . . . . . . . . . . . . . . 249
Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Signal levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Echo and Signal Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Tone Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
G.726 Codec and H.248 Media Gateways . . . . . . . . . . . . . . . . . . . . 253
Silence suppression/VAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Transcoding/tandeming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
CNA Application Performance Rating . . . . . . . . . . . . . . . . . . . . . . . . 254
Translating low level statistics to an Application Performance rating . . . . . . . 255
Available application models . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Avaya Integrated Management . . . . . . . . . . . . . . . . . . . . . . . 257
Integrated Management overview documents. . . . . . . . . . . . . . . . . . . . 257
Avaya Integrated Management offers . . . . . . . . . . . . . . . . . . . . . . . . 257
Administration Tools Offer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
VoIP Monitoring Management Offer . . . . . . . . . . . . . . . . . . . . . . . 258
Enterprise Network Management Offer . . . . . . . . . . . . . . . . . . . . . 259
System Management Offer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Third-party network management products . . . . . . . . . . . . . . . . . . . . . 260
Multi Router Traffic Grapher . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
HP OpenView Network Node Manager . . . . . . . . . . . . . . . . . . . . . . 261
Network management models . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Distributed (component) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Centralized (hybrid) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Reliability and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Reliability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Survivability solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
S8700-series Server Separation . . . . . . . . . . . . . . . . . . . . . . . . . 268
Enterprise survivable servers (ESS) . . . . . . . . . . . . . . . . . . . . . . . 269
Issue 6 January 2008 7
Connection preserving upgrades for duplex servers . . . . . . . . . . . . . . 271
Inter Gateway Alternate Routing (IGAR) . . . . . . . . . . . . . . . . . . . . . 271
Survivability for branch office media gateways . . . . . . . . . . . . . . . . . . . 272
H.248 Media Gateway recovery via LSP . . . . . . . . . . . . . . . . . . . . . 272
Modem dial-up backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Auto fallback to primary Communication Manager for H.248 media gateways 273
Connection preserving failover/failback for H.248 media gateways . . . . . . 274
G250 and IG550 Media Gateway standard local survivability function (SLS) . 274
IP endpoint recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
IP endpoint recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Recovery algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
IP Endpoint Time to Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Converged Network Analyzer for network optimization . . . . . . . . . . . . 278
Section 3: Getting the IP network ready for telephony . . . . . . . 281
IP Telephony network engineering overview . . . . . . . . . . . . . . . 283
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Voice quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Common issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Network design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
LAN issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
General guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
WAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Convergence advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Managing IP Telephony VPN issues . . . . . . . . . . . . . . . . . . . . . . . 300
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Converged network design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Design and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Design for Simplicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Design for Manageability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
8 Avaya Application Solutions IP Telephony Deployment Guide
Design for Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Quality of Service guidelines . . . . . . . . . . . . . . . . . . . . . . . . 315
CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Layer 2 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Layer 3 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
QoS guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
IEEE 802.1 p/Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Recommendations for end-to-end QoS . . . . . . . . . . . . . . . . . . . . . 321
DiffServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
RSVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Queuing methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
WFQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
PQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Round-robin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
CB-WFQ / LLQ / CBQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
RED / WRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Traffic shaping and policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Frame Relay traffic shaping. . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
LFI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
FRF.12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
RTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Application perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Network perspective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
RTP header compression test . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Examples of QoS implementation . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Example 1: Cisco router configuration for point-to-point WAN links . . . . . 332
Example 2: C-LANS cannot tag their traffic . . . . . . . . . . . . . . . . . . . 335
Example 3: More restrictions on the traffic . . . . . . . . . . . . . . . . . . . 336
Converged infrastructure LAN switches . . . . . . . . . . . . . . . . . . . . . 337
Issue 6 January 2008 9
Network recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Change control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Layer 2 mechanisms to increase reliability . . . . . . . . . . . . . . . . . . . . . 340
Spanning tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Link Aggregation Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Layer 3 availability mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Routing protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
VRRP and HSRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Multipath routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Dial backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Convergence times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
The Converged Network Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . 344
CNA components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Configuration and deployment details . . . . . . . . . . . . . . . . . . . . . . 348
Network assessment offer . . . . . . . . . . . . . . . . . . . . . . . . . 349
Problems with data networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Avaya network readiness assessment services. . . . . . . . . . . . . . . . . . . 349
Basic network readiness assessment service. . . . . . . . . . . . . . . . . . 350
Detailed network readiness assessment service . . . . . . . . . . . . . . . . 352
Appendix A: CNA configuration and deployment . . . . . . . . . . . . . 359
Configuring CNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Basic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Decision making . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Configuring the Routers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Edge Router GRE Tunnel Interfaces . . . . . . . . . . . . . . . . . . . . . . . 364
Route Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Routing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Command summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
CNA commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Router Ra commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Router Rb commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
10 Avaya Application Solutions IP Telephony Deployment Guide
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 network. The guide can
be used as a tool to provide a better understanding of the benefits of Avaya IP solutions and of
the many aspects of deploying IP Telephony on a customer’s data network.
This book does not contain procedural information for installing, configuring, or maintaining IP
telephony products. This type of procedural information is contained in other product
documentation available at http://www.avaya.com/support
Audience
.
The primary audiences for this book are:
● Avaya employees and Business Partners working in sales and sales-support
organizations.
● Customers considering the purchase of Avaya’s IP Telephony products.
● Avaya customers who have purchased IP Telephony products and are seeking
suggestions for their implementation.
Secondary audiences include the Technical Service Center (TSC), training, and development.
Using this book
This book is organized in three major sections:
Section I - Avaya Application Solutions product guide. Use this section to learn about Avaya’s
IP Telephony products including:
● Communication Manager
● Servers and gateways and their configurations and capacities
● Migration from circuit-switched to packet-switched products
Issue 6 January 2008 11
About This Book
● 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 management
● Reliability and recovery
Section III - Getting the IP network ready for telephony. Use this section to learn about
preparing an IP network for telephony, including:
● Network design and engineering
● Quality of service
● Network recovery
● Network assessment
Appendix A - covering Converged Network Analyzer configuration.
Downloading this book and updates from the Web
You can download the latest version of the Avaya Application Solutions IP Telephony
Deployment Guide, 555-245-600, from the Avaya Support Web site. You must have access to
the Internet, and a copy of Acrobat Reader must be installed on your personal computer.
Avaya makes every effort to ensure that the information in this book is complete and accurate.
However, information can change after we publish this book. Therefore, the Avaya Web site
might also contain new product information and updates to the information in this book. You can
also download these updates from the Avaya Web site.
To download the latest version of this book:
1. Access the Avaya web site at http://www.avaya.com/support
2. On the upper left of the page, type 555-245-600 in the Search Support box, and then click
Go.
.
The system displays the Product Documentation Search Results page.
3. Scroll down to find the latest issue number, and then click the book title that is to the right of
the latest issue number.
12 Avaya Application Solutions IP Telephony Deployment Guide
Related resources
For more information on Avaya IP Telephony products, see the following documentation
libraries and CDs:
Title Number or Link
Related resources
Documentation for Avaya Communication Manager
Release 3.1, Media Gateways and Servers
Avaya Communication Manager Quick Reference Set 03-300366
Avaya IP Telephony Implementation Guide iImplementation_Guide
Documentation Ordering Instructions 03-300440
Technical assistance
Avaya provides the following resources for technical assistance.
Within the US
For help with:
● Feature administration and system applications, call Technical Consulting System Support
(TCSS) at 1-800-225-7585
03-300151
● Maintenance and repair, call the Avaya National Customer Care Support Line at
1-800-242-2121
● Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353
International
For all international resources, contact your local Avaya authorized dealer.
Issue 6 January 2008 13
About This Book
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 your comments about this book. To reach us by:
● Mail, send your comments to:
Avaya Inc.
Product Documentation Group
Room B3-H13
1300 W. 120th Ave.
Westminster, CO 80234 USA
● E-mail, send your comments to:
document@avaya.com
● Fax, send your comments to:
1-303-538-1741
Ensure that you mention the name and number of this book, Avaya Application Solutions IP
Telephony Deployment Guide, 555-245-600.
14 Avaya Application Solutions IP Telephony Deployment Guide
Section 1: Avaya Application Solutions
product guide
Issue 6 January 2008 15
16 Avaya Application Solutions IP Telephony Deployment Guide
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 applications
● Avaya SIP solutions
● Avaya SIP application enablement
The next-generation Avaya Application Solutions portfolio powered by Avaya Communication
Manager delivers on the promise of IP by offering a no-compromise approach to convergence
in terms of reliability and functionality. “No compromise” means that Avaya allows customers to
migrate to IP Telephony without compromising on features (all features are maintained or
expanded), interfaces (all existing telephones and lines are supported, along with new IP
Telephones, Softphones, and IP trunks), or reliability. Avaya Communication Manager is the
centerpiece of Avaya Application Solutions.
Communication Manager runs on a variety of Avaya servers, provides control to Avaya Media
Gateways and Avaya Communications Devices, and can operate in a distributed or network call
processing environment. Figure 1:
Figure 2:
Communication Manager traffic flow on page 18 summarize the Avaya Application
Avaya Application Solutions on page 17 and
Solutions.
Figure 1: Avaya Application Solutions
Issue 6 January 2008 17
Avaya Application Solutions
Figure 2: Communication Manager traffic flow
SIP Signaling
Avaya Media Servers
Communications
Applications
Communications
Manager
SIP Signaling
SES
SIP Signaling
CCMS Signaling over IP
Circuit-switched
Telephone
SIP
Phone
RTP Audio
Avaya Media
Gateways
G650
MCC1
SCC1
Circuit-switched
Telephone
IP
Communications
Device
H.323 Signaling
RTP Audio
RTP Audio
PSTN
RTP Audio
H.248 Signaling
Avaya G700
cynds222 LAO 012506
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 Avaya Communication Manager is always to/from SES.
3. SIP signaling can go through a C-LAN (on a G650, etc.), or directly Communication Manager
(if the server is the S8300 or S8500).
Note:
Note: This is actually true for both H.323 and H.248 signaling. The diagram gives the
impression that H.248 comes directly from Communication Manager and H.323
goes through the media gateways, when in fact both protocols can go both ways
depending on server type.
Communication Manager is the next generation of Avaya call processing software.
Communication Manager is an open, scalable, highly reliable, and secure telephony
application. Communication Manager operates on Avaya servers, and on the existing family of
DEFINITY servers.
Communication Manager carries forward all the current DEFINITY capabilities, plus all the
enhancements that enable enterprises to take advantage of new, distributed technologies,
increased scalability, and redundancy. Communication Manager is evolved from DEFINITY
software and delivers no-compromise, enterprise IP Telephony.
18 Avaya Application Solutions IP Telephony Deployment Guide
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 Enterprise
Communications Servers (DEFINITY ECS). These Gateways work with standards-based data
networks and easily connect with the Public Switched Telephone Network (PSTN).
Communication Manager is extensible to IP, digital and analog telephones, and wireless
business solutions. Avaya Communication Devices work with the full feature set of
Communication Manager to help enterprises be more productive by providing anytime,
anywhere access to maximize business continuity.
Avaya Communication Manager
Avaya Communication Manager provides user and system management functionality, intelligent
call routing, application integration and extensibility, and enterprise communications networking.
Communication Manager operates on Avaya servers, and on the existing family of DEFINITY
servers. For more information on the Avaya Application Solutions related features of
Communication Manager, see
Call processing on page 125.
Avaya Communication Manager
Avaya servers
An Avaya server provides centralized, enterprise-class call processing. This call processing can
be distributed across a multi-protocol network (including IP) to support a highly diversified
network architecture that consists of headquarters, branch, remote, small, and home offices.
Linux-based servers
The Avaya S8300, S8400, S8500, S8700-series, and SES-SIP are Linux-based servers. These
servers support:
● Distributed IP Networking and centralized call processing across multi-service networks
● Dual server design with hot fail-over (S8700-series Server only)
● Redundant LAN Interfaces and remote survivable call processing
For more information on the architecture and the functionality of the servers, see Hardware
Description and Reference for Avaya Communication Manager, 555-245-207.
Avaya DEFINITY Servers
Avaya Communication Manager also runs on the following DEFINITY Servers, which can be
IP-enabled:
Issue 6 January 2008 19
Avaya Application Solutions
● 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:
fit into Avaya CMC1, SCC1, and MCC1 Media Gateways.
The focus of this document is network design incorporating the newer Communication Manager
platforms. Therefore, the DEFINITY Servers are only discussed briefly here.
Avaya Media Gateways
An Avaya Media Gateway supports both bearer traffic and signaling traffic that is routed
between packet-switched networks and circuit-switched networks. Communication Manager
running on Avaya servers controls voice and signaling over a variety of stackable and modular
Media Gateways:
● Avaya G150 Media Gateway
● Avaya G250 Media Gateway
Communication Manager traffic flow on page 18. These servers
● Avaya G350 Media Gateway
● Avaya G450 Media Gateway
● Avaya G650 Media Gateway
● Avaya G700 Media Gateway
● Avaya G860 High Density Media Gateway
● Avaya CMC1 Media Gateway
● Avaya SCC1 Media Gateway
● Avaya MCC1 Media Gateway
● MultiTech MultiVoIP Gateway
● Avaya IG550 Integrated Gateway
The Media Gateways contain the network and the endpoint interfaces, as well as call
classification, announcement boards, and so on. Through these interfaces, Communication
Manager performs gateway/gatekeeper functions. For more information on the Media
Gateways, see
Small to mid-size enterprise on page 37 and Mid-market to large enterprise on
page 79.
Avaya Integrated Management
Avaya Integrated Management is systems-management software for managing converged
voice and data networks.
20 Avaya Application Solutions IP Telephony Deployment Guide
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
● control network quality
For more information on Avaya Integrated Management, see:
● Avaya Integrated Management on page 257
Avaya communication devices
Avaya Communication Manager provides intelligent control for a variety of smart
communication devices, including the one-X Deskphone family of IP telephones, IP Softphones,
digital telephones, attendant consoles, analog telephones, and wireless telephones. For
information on these devices, see Hardware Description and Reference for Avaya
Communication Manager, 555-245-207.
Avaya Communication Manager
Avaya Communication Manager applications
Avaya Communication Manager supports the following communication capabilities and
applications:
● Call Center
● Messaging
● Unified Communication Center
● 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 Routing (BSR) polling
For more information on these applications, see Communication applications on page 152 and
ttp://www.avaya.com/support.
h
Issue 6 January 2008 21
Avaya Application Solutions
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 initiating interactive communication sessions between users. Such sessions include
voice, video, instant messaging, interactive games, and virtual reality.
As implemented by Avaya for Communication Manager release 3.0 and beyond, SIP "trunking"
functionality is available on any of the Linux-based servers (S8300, S8400, S8500 or
S8700-series). SIP trunking allows Avaya Communication Manager to communicate with SIP
endpoints and gateways across an IP network. SIP trunks allow an enterprise to connect its
server(s) to an Avaya SIP-Enablement Server (SES), a SIP-enabled proxy server, and through
this proxy to an external SIP service provider, if desired. The trunk support in Communication
Manager complies with SIP standards, specifically IETF RFC 3261, and so interoperates with
any SIP-enabled endpoint/station that also complies with the standard.
Avaya Communication Manager supports SIP endpoints, including the Avaya 4602 SIP
Telephone and Avaya IP Softphone Release 5. In addition to its IP telephony capabilities, IP
Softphone R5 also includes Instant Messaging (IM) client software, which is a SIP-enabled
application that connects to the SES for IM control. By means of having SIP-enabled endpoints
managed by Communication Manager, many features can be extended to these endpoints.
Avaya SIP application enablement
Avaya Communications Process Manager is middleware software that uses customizable web
services to integrate Avaya communications solutions into customer business processes.
Communications Process Manager achieves this integration by detecting events from a
customer business application. Different events trigger Communications Process Manager to
invoke different communication applications to escalate the situation to people and resources
that can address it.
Communications Process Manager performs the following functions:
● Integrates the following Avaya communication resources. This integration makes it
possible for the resources to communicate with Communications Process Manager and
ultimately with each other.
- Communication Manager — provides telephony capabilities.
- SIP Enablement Services (SES) — serves as the SIP proxy. All communication
resources use SIP to communicate through Communications Process Manager.
- Meeting Exchange Express — provides audio conference capabilities.
- Voice Portal — provides interactive voice response (IVR) capabilities for phone
interactions between Communications Process Manager and its users.
● Orchestrates interactions between the communication resources.
22 Avaya Application Solutions IP Telephony Deployment Guide
Avaya Distributed Office
● 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.
Communications Process Manager makes it possible for customers to combine their data
related activities with communication to:
● Rapidly mobilize the right people for decision making (no matter where they are, or on
what device)
● Significantly reduce the human latency required today in contacting people
● Incorporate automatic alerts into business process decisions.
Communications Process Manager uses internal service-oriented architecture (SOA) with both
loose coupling between its internal components and a scriptable orchestration engine. This
architecture provides a high degree of customizability and very loose coupling between the
customer business processes and the communications systems that are used to implement the
Communications Process Manager Web services. The various components of Communications
Process Manager can be included or excluded to meet customer needs.
Avaya Distributed Office
Note:
Note: See www.avaya.com/support for a complete set of documentation for Avaya
Distributed Office.
As enterprises evaluate replacements for traditional Key-Hybrid telephone systems at the
branch, they must carefully consider investments that reduce total cost of ownership, lower
operational expenses, and enable better interaction with customers.
Distributed Office provides large and medium multi-site enterprises an elegant migration from
branch-office Key-Hybrid systems to an IP-based solution. Distributed Office is a distributed and
scalable Session Initiation Protocol (SIP) solution that delivers local telephony and
communications applications to multiple locations. Target markets include financial services
outlets, retail stores, transportation depots, and regional offices for government and other
industries. Replace variable w/ short product name supports centralized administration and can
be rapidly deployed as either individual branch locations or as a network of branch locations.
Distributed Office is based on open standards using SIP and Web-Services for maximum
investment protection.
This highly available solution does not depend on WAN health for local branch operation
because call processing is distributed to each branch location. Yet customers can still link
branches together, routing voice, presence, and instant messaging, and also leverage
connections to corporate headquarters to provide enhanced customer service.
Issue 6 January 2008 23
Avaya Application Solutions
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 Distributed Office i120. These platforms are available in numerous
configurations.
Distributed Office Configurations
An Avaya Distributed Office system can be configured as
● an individual branch location
● an individual branch location with centralized management
● a Networked branch location
The diagram in Figure 3
shows a Distributed Office solution with networked branch locations.
This configuration supports:
● SIP calls between the branch and main locations over the private WAN or public Internet.
● Inter-branch SIP calls through an SIP Enablement Services (SES) edge proxy at the main
location.
● Integrated Management for Distributed Office at the main location provides centralized
management to the branch locations.
● Optional connection to Communication Manager server through the SES home proxy.
24 Avaya Application Solutions IP Telephony Deployment Guide
Figure 3: Networked remote sites
Avaya Distributed Office
Optional
components
Traps sent to the Avaya
Secure Enhanced Alarming
receiver via customer VPN
(requires SAC-Lite)
PSTN
Distributed Office
Feature Server
SIP Enablement Services
Local Manager
CTI and TAPI applications
Automated Attendant
Voice mail
Secure Enhanced Alarming
SIP, H.323, and analog
telephones, fax
SES home
i40
Main business location
SIP
Apps
Communication
servers
Central
Manager
Manager
SES edge
private WAN
Branch locations
SIP
IVR
SIP
SIP
Management
TDM
T
Distributed Office
i120
Feature Server
SIP Enablement Services
Local Manager
CTI and TAPI applications
Automated Attendant
Voice mail
Secure Enhanced Alarming
SIP, H.323, and analog
telephones, fax
PSTN
Issue 6 January 2008 25
Avaya Application Solutions
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 Services
-Voice Mail
- Announcements
- Auto attendant
- Call Detail Recording
- Secure Enhanced Alarming
● Application Enablement Services
- Extend Avaya’s rich features in an IP environment to get the most from your current investment.
- Integrate communications & business applications to leverage existing infrastructure and
maximize efficiency.
- Support some third-party application integration to provide mission-critical support for key
business processes.
- Computer-telephony integration services.
Distributed Office implementation
The Distributed Office solution provides a set of standard hardware configurations or constructs
and set of provisioning profiles. A construct is chosen that best satisfies the hardware
requirements for one ore more locations. A provisioning profile, consisting of a set of files
containing provisioning data, is selected and loaded onto the hardware platform.
Selecting a construct
When you use the Avaya Solution Designer to create a configuration template for a group of
branch locations, the choice of a construct is the most important parameter. The choice of
construct determines the number of lines and trunks of each type. The goal is to choose the
smallest construct that accommodates the maximum requirements assuming growth.
The first consideration when choosing a construct is the Distributed Office model, i40 or i120. A
construct that uses the i120 model provides a larger number of lines and trunks than the i40, as
well as higher capacities for several other parameters such as the number of voice mail boxes,
the number of DSPs, and the busy hour call completion rate.
26 Avaya Application Solutions IP Telephony Deployment Guide
Avaya Distributed Office
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 but another parameter,
such as the number of DSPs to handle large Fax volumes might not be sufficient. In either case,
one of the i120 constructs would be a better choice.
Table 1:
i40 constructs on page 27 and Table 2: i120 constructs on page 29 provide the
information needed to choose a construct.
Note:
Note: The list of available constructs might change over time. Check on the Avaya
Distributed Office web site for the latest set of available constructs.
i40 constructs
Each i40 construct contains the following ports:
● One console cable port
● One interface USB port (located on the chassis where you connect the Disk on Key)
● One Contact Closure Adjunct (CCA) port
● One Ethernet WAN port (not used with Distributed Office)
● Eight Ethernet LAN Power over Ethernet (PoE) ports
● One USB port (for use with a USB modem for servicing the platform)
● One Ethernet services port
● Two analog line ports
In addition to these ports, the i40 contains additional ports based on its construct. Table 1
the three i40 constructs, and a description of what additional ports are available for each.
shows
Table 1: i40 constructs
Construct
Analog
trunk
ports
ISDN BRI
trunk
ports
i40 - Analog 4
i40 - BRI 1 2
i40 - DS
2
1. The T1/E1 interface port can be configured for ISDN PRI,
Robbed Bit, or CAS signaling.
1
2. The i40 - DS1 construct also contains three pairs
of test jacks that are used by service personnel
only.
T1/E1
interface
1
port
1
Issue 6 January 2008 27
Avaya Application Solutions
i120 constructs
Each i120 construct contains the following ports:
● One analog trunk port
● Two analog line ports
● One Contact Closure Adjunct (CCA) port
● One Ethernet WAN port (not used with Distributed Office)
● One Ethernet LAN PoE port
● One console cable port
● One interface USB port (located on the chassis where you connect the Disk on Key)
● One USB port (for use with a USB modem for servicing the platform)
● One Ethernet services port
Note:
Note: If you need additional ports, additional Media Modules are available for the i120
platform constructs. See your Avaya representative for details.
In addition to these ports, the i120 contains additional ports based on its construct. Table 2
shows the ten i120 constructs, and a description of what additional ports are available for each.
The legend for the various construct names is a follows:
Legend:
A = Analog (RJ-11, 2-wire)
B = BRI
D = Digital (DS1, T1, E1, and PRI)
H = High Capacity (24 analog ports using a single connector)
P = Power over Ethernet (PoE)
28 Avaya Application Solutions IP Telephony Deployment Guide
Table 2: i120 constructs
Avaya Distributed Office
Construct
Analog
ports for
lines or
trunks
Analog
line ports
10/100
Ethernet
Base-T
PoE ports
T1/E1
interface
1
port
ISDN BRI
trunk
ports
i120 - A 8
i120 - AH 8 24
i120 - A2H 8 48
i120 - AP 8 40
i120 - 2AP 16 40
i120 - D2H2
8 48 1
i120 - DP2 8 40 1
i120 - BH 8 24 8
i120 - B2H 8 48
i120 - BP 8
1. The T1/E1 interface port can be configured for ISDN PRI, Robbed Bit, or CAS signaling.
40 8
2. The i120 - DH and i120 - DP constructs also contains three pairs of test
jacks and a connector that are used by service personnel only.
8
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, voice mail,
automated attendant, SES, and TAPI. The AM110 Application Module also contains a Freescale
processor and replaceable Compact Flash and SO-DIMM memory.
The AM110 Application Module is included with both the i40 and i120 platforms. The Avaya
AM110 Application Module can be inserted only in slot V1 of either the i40 or the i120.
Issue 6 January 2008 29
Avaya Application Solutions
Telephony media modules
The ten constructs for Distributed Office i120 contain one or more media modules. Tab le 3
shows the available media modules, and the slot or slots in which each module can be inserted.
Table 3: Supported media modules
Module Description Permitted slots
MM710 One T1/E1 ISDN PRI trunk port V2, V3, V4, V5
MM711 Eight universal analog ports V2, V3, V4, V5
MM716 Twenty-four analog line ports V2, V3, V4, V5
MM720 Eight ISDN BRI trunk ports V2, V3, V4, V5
Telephony modules
LAN module
MM316 Forty 10/100 Ethernet ports with Power over Ethernet (PoE),
and one 10/100/1000 Ethernet copper uplink/access port
Streamlined Deployment
A major goal of the Distributed Office offering is to minimize the time to deploy the Distributed
Office systems at the branch locations. The total deployment time includes:
● Unpacking, assembling, and cabling the hardware
● Enter site-specific and other dynamic data
● Acceptance testing
The first and third deployment items require a fixed amount of time for each construct. The time
required for the second item, completing the provisioning data, varies according to the amount
of data that needs to be added or changed in the profile that was loaded onto the system or onto
a USB portable storage device, or "Disk on Key" (DoK).
The design activities described previously determine the type and the number of the Distributed
Office hardware components for each branch location. The implementation process then uses
data files called profiles to load the translations and other parameter values onto the i40 or i120
Distributed Office platform before it is shipped to the customer site.
V6
In the design phase, the Sales Engineer uses the Avaya Solution Designer to create a purchase
order that specifies the Distributed Office hardware for each branch location. For each branch
location or group, the Sales Engineer specifies that the provisioning profile is:
● Standard — The profile is one of a set of profiles that have been previously defined and
associated with a hardware construct.
30 Avaya Application Solutions IP Telephony Deployment Guide
Loading...