1. Manuals
  2. Brands
  3. Avaya Manuals
  4. IP Phone
  5. Application Solutions
  6. Deployment manual

Avaya Application Solutions Deployment Manual

Hide thumbs
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
Table of Contents

Advertisement

Quick Links

Download this manual

Avaya Application Solutions:

IP Telephony Deployment Guide
555-245-600
Issue 3.4.1
June 2005

Advertisement

Table of Contents
loading

Related Manuals for Avaya Application Solutions

Summary of Contents for Avaya Application Solutions

  • Page 1: Avaya Application Solutions

    Avaya Application Solutions: IP Telephony Deployment Guide 555-245-600 Issue 3.4.1 June 2005...
  • Page 2 • Installation documents Warranty • System administration documents Avaya Inc. provides a limited warranty on this product. Refer to your • Security documents sales agreement to establish the terms of the limited warranty. In • Hardware-/software-based security tools addition, Avaya’s standard warranty language as well as information...
  • Page 3 • A reorder tone is received. 04DU9-IKN 6.0Y RJ48C Avaya attests that this registered equipment is capable of providing users access to interstate providers of operator services through the use of 04DU9-ISN 6.0Y RJ48C access codes. Modification of this equipment by call aggregators to block...
  • Page 4 Contact the state public utility commission, public service E-mail: totalware@gwsmail.com commission or corporation commission for information. For the most current versions of documentation, go to the Avaya support This equipment, if it uses a telephone receiver, is hearing aid compatible. Web site: http://www.avaya.com/support.

  • Page 5: Table Of Contents

    Avaya Communication Manager ......Avaya Media Servers .......
  • Page 6 Other Avaya IP Telephony servers ......Avaya IP Office ........
  • Page 7 Avaya IP Agent ........
  • Page 8 Toll fraud ........Avaya’s security design ......
  • Page 9 Avaya S8300 Media Server with G350 or G700 Media Gateway ..Avaya DEFINITY Server R ......
  • Page 10 Powering IP Telephones ......10 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 11 WAN......... . . Overview .
  • Page 12 Introduction ........Network connectivity between Avaya S8700 servers and port networks . . .
  • Page 13 Problems with data networks ......Avaya network assessment solutions ......
  • Page 14 TFTP Generic Setup ....... . Avaya TFTP (Suite Pro) configuration ..... .

  • Page 15: About This Book

    IP Telephony products with an IP network. The guide can 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.

  • Page 16: Using This Book

    About This Book 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...

  • Page 17: Downloading This Book And Updates From The Web

    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.

  • Page 18: Technical Assistance

    For access to all international resources, contact your local Avaya authorized dealer. 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. 18 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 19: Sending Us Comments

    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. Issue 3.4.1 June 2005...
  • Page 20 About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 21: Section 1: Avaya Application Solutions Product Guide

    Section 1: Avaya Application Solutions product guide Issue 3.4.1 June 2005...
  • Page 22 22 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 23: Avaya Application Solutions

    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.
  • Page 24 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 Media 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.

  • Page 25: Avaya Communication Manager

    Communication Manager operates on Avaya Media 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.

  • Page 26: Avaya Definity Servers

    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 Media Servers controls voice and signaling over a variety of stackable and modular Media Gateways:...

  • Page 27: Avaya Integrated Management

    Through these interfaces, Communication Manager performs gateway/gatekeeper functions. For more information on the Media Gateways, see Call processing. The following additional resources provide even more details on the Avaya Media Gateways: For US Business Partners: https://www.avaya.com/doc/gpp/public/pss/category/cs/eclips/ media_servers_gateways/index.html Avaya Integrated Management Avaya Integrated Management is systems-management software for managing converged voice and data networks.

  • Page 28: Avaya Communication Devices

    Avaya communication devices Avaya Communication Manager provides intelligent control for these smart devices: Avaya IP Telephones: 4600 Series (4602, 4606, 4612, 4620, 4624, 4630) Avaya digital telephones: 6400 Series, 2402, and 2420 Avaya analog telephone (6200 Series, 2500, and 2554)

  • Page 29: Compact Call Center

    Avaya Communication Manager Call Center The Avaya Call Center solution is built on proven and innovative automatic call distribution (ACD) technology. This technology offers a suite of call routing capabilities that help agents handle calls more effectively. Customers can select from a powerful assortment of features,...

  • Page 30: Conferencing Systems

    For more information on CTI, see: US Business Partners: https://www.avaya.com/doc/gpp/public/pss/category/ call_center_crm.html Messaging The following messaging systems are supported by Avaya Communication Manager: INTUITY™ Messaging Systems Aria® Messaging Systems Serenade® Messaging Systems Modular Messaging® For more information on Avaya messaging products, see: For US Business Partners: https://www.avaya.com/doc/gpp/public/pss/category/...

  • Page 31: Avaya Application Solutions Platforms

    Avaya Application Solutions platforms The Avaya Communication Manager portfolio covers small, medium, and large enterprises with advanced communications needs between 2 and 36,000 stations per system. This chapter provides an overview of the Avaya Communication Manager platforms architecture that supports Avaya Application Solutions components and features.
  • Page 32 Avaya Application Solutions platforms Table 1: Avaya Application Solutions comparison matrix contains an overview of the different Avaya Media Servers that are discussed in this chapter. Table 1: Avaya Application Solutions comparison matrix Avaya Avaya S8500 Avaya S8700 Avaya S8700...

  • Page 33: Small To Mid-Size Enterprise

    34) seamlessly delivers voice, fax, and messaging capabilities over an IP network. This unique solution converges the power of the Avaya Communication Manager feature set with the power of distributed Ethernet switching from the P330 Stackable Switching System.
  • Page 34 Media Server in the configuration. 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 interfaces, ATM access or WAN access modules without additional switches. The system can be networked to other PBXs and Communication Manager platforms through an IP network.
  • Page 35 Small to mid-size enterprise Figure 5: Avaya S8300/G700 or G350 in a stand-alone configuration PSTN Stand alone Office with IP Trunk link to Avaya PBXs ISDN-PRI ISDN-PRI E1/T1 EIA 530A DCE EIA 530A DCE E1/T1 EIA 530A DCE OK TO...

  • Page 36: G700 Hardware Architecture

    Figure 6: Avaya G700 Media Gateway (front view) on page 37 shows the Media Gateway enclosure. 36 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 37 Small to mid-size enterprise Figure 6: Avaya G700 Media Gateway (front view) E1/T1 EIA 530A DCE SHUT DOWN OK TO REMOVE SERVICES USB 1 USB 2 cynds111 KLC 121003 Figure notes: 1. LED board 5. Avaya P330 Expansion Module 2. S8300 Media Server 6.
  • Page 38 Tone detection and generation (15 ports of tone detection) System clock generation and synchronization to an external network timing reference Download agent for the media modules License/translation storage System maintenance H.248 signaling Connection management 38 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 39: Voice Announcement Over The Lan

    Messaging H.323 integration on the S8300 without the daughter card. Voice Announcement over the LAN Voice Announcement over the LAN (VAL) capabilities are co-resident on the Avaya G700 Media Gateway. This G700 VAL announcement capability allows backup and restore of announcements to an external PC or a file server on the customer’s local area network (LAN),...

  • Page 40: S8300 Primary Controller Architecture

    Avaya Application Solutions platforms S8300 primary controller architecture The S8300 Media Server has the same form factor as the Avaya media modules. The S8300 is installed in slot V1 of the G700 or G350 Media Gateway. The S8300 can be configured as either a primary controller (a.k.a.
  • Page 41 Small to mid-size enterprise G350 Media Gateway The Avaya G350 Media Gateway is a standalone converged networking device that provides the following voice and data networking services: Voice over IP Media Gateway based on H.248 protocol WAN (data) connectivity and routing...
  • Page 42 The G350’s internal router enables you to connect directly to an outside WAN, without needing additional routing equipment. The G350 provides telephone services through an Avaya media server, such as the S8300. The media server controls the routing of voice traffic through the G350. The media server can be either internal (S8300) or external (S8700, S8500, or S8300).
  • Page 43 Small to mid-size enterprise 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 media modules. V6 is a high-density media module (HDMM) slot for housing new high capacity media modules (see below).
  • Page 44 Table 7: Additional G350 functions and capacities Function Capacity VoIP DSP engine 32 G.711 or 16 G.729 channels Touch Tone Recognition 15 channels (TTR) Announcement 6 playback, 1 record Number of stations 40 (18 analog) 1 of 2 44 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 45: Definity Server Csi And Cmc1 Media Gateway

    2 of 2 DEFINITY Server CSI and CMC1 Media Gateway The Avaya Communication Manager with an Avaya DEFINITY® Server CSI offer is targeted at small to mid-size customers, or the satellite offices of large corporations who require sophisticated applications. This solution supports 50 to 500 telephones. The small to mid-size customer segment tends to be multi-site with 2 to10 locations.

  • Page 46: Mid-Market To Large Enterprise

    The S8500 system supports the Avaya MCC1, SCC1, CMC1, and G650 Media Gateways. The Avaya G700 and G350 Media Gateways are also supported, provided that there is a TCP/IP connection between the media gateway and a C-LAN circuit pack located in a MCC1, SCC1, CMC1, or G650 Media Gateway.
  • Page 47 Mid-market to large enterprise S8500 capacities Table 8: Capacities for S8500 Feature Capacity General Business Busy Hour Call Completion Up to 100,000 Number of stations + trunks Up to 3200 Number of IP users Up to 3200 (IP trunks + IP stations) Number of trunks Up to 800 (up to 800 SIP trunks) (IP trunks and non-IP trunks)

  • Page 48: S8700 Media Server Multi-Connect Configuration

    Avaya Application Solutions platforms S8700 Media Server Multi-Connect configuration The Avaya S8700 series Media Server with an MCC1 or SCC1 Media Gateway is targeted at Avaya’s largest customers. These customers are typically experiencing rapid growth, and looking for ways to consolidate their network. These are customers who require high-end...
  • Page 49 S8700 series Media Server The Avaya S8700 series Media Server always consists of two Intel-based servers running on a Linux operating system. In S8700 Multi-Connect and IP-Connect configurations, the S8700 Media Server provides the main feature and management processing capabilities of the system.
  • Page 50 USB modem - Each S8700 series Media 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 to facilitate maintenance by Avaya Services personnel.
  • Page 51 Other components The S8700 in a Multi-Connect solution also includes the following components: An Avaya P133, P134, P333, or P334 Ethernet switch with duplication option One or more IP Server Interface (IPSI) circuit packs (TN2312AP) A Center Stage Switch (CSS) or an ATM Switch for bearer connectivity One or more MCC1 or SCC1 Media Gateways, also known as port networks (PNs) Issue 3.4.1 June 2005...
  • Page 52 When designing S8700 Multi-Connect systems, a control network connects the servers to the IPSIs through a private 10/100 BaseT Ethernet. It consists of two separate Ethernet networks made from Avaya Ethernet switches. Control network A connects to the primary IPSIs, and control network B connects to the secondary IPSIs (Figure 12: S8700 Multi-Connect control network).
  • Page 53 Mid-market to large enterprise Circuit packs that support IP signaling and media traffic Figure 13: S8700 / MCC1 signaling path S8700 H.323 endpoint or H.248 Gateway Phone Center Stage (non-IP) E1/T1 EIA 530A DCE EIA 530A DCE SHUT DOWN SHUT DOWN REMOVE OK TO OK TO...
  • Page 54 Each IPSI typically controls up to five gateways by tunneling control messages over the center stage (TDM) network to the PNs that do not have IPSIs. For locations with high IP Telephone traffic, Avaya recommends a greater number of IPSI circuit packs. An IPSI cannot be placed in:...
  • Page 55 Mid-market to large enterprise The C-LAN circuit pack is used for all IP call signaling for both IP trunks and stations. This circuit pack also provides TCP/IP connectivity to such adjuncts and synchronous applications as Call Management System (CMS) and INTUITY AUDIX. This circuit pack also supports firmware download capability for all firmware-downloadable circuit packs in a PN, which allows administrators to remotely update the firmware or application code of circuit packs such as the TN799DP (C-LAN) or TN2302AP Media Processor.
  • Page 56 DSP resources to the required task and connecting multiple resources into a chain that performs the desired media processing function. In addition, the Media Server sends the information to the destination of these audio streams. 56 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 57: Media Gateways

    G.729 (A, B) In the same way that a MedPro interfaces with IP Telephony endpoints, it can connect to another MedPro to interconnect two or more Avaya switches in an IP network over an IP trunk. Media Gateways The MCC1, SCC1, G700, and G350 Media Gateways are supported in a Multi-Connect configuration.
  • Page 58 There are two types of SCC1 Media Gateways: An Expansion Control Cabinet that contains service slots and port slots. A Port Cabinet that contains ports and interfaces to an Expansion Control Cabinet. 58 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 59 MCC1 or SCC1 Media Gateway can be extended to an IPSI in a remote media gateway. But for cost effectiveness and straightforward installation, Avaya recommends that all of the IPSI-connected media gateways be collocated with the S8700 and Ethernet switches. The circuit-switched network dictates the available options.
  • Page 60 The Asynchronous Transfer Mode (ATM) switch is a replacement option for the CSS, or for the direct-connect switch. Several Avaya ATM switch types can provide Port Network connectivity. Non-Avaya ATM switches that comply with the ATM standards that are set by the European Union can also provide Port Network connectivity.
  • Page 61 Mid-market to large enterprise S8700 Multi-Connect configuration for higher availability When used with the MCC1, SCC1, G700, or G350 Media Gateways, the S8700 series Media Server has the following reliability options: Standard reliability configuration High reliability configuration Critical reliability configuration Standard reliability configuration The standard reliability option is the most basic option that consists of the following components:...
  • Page 62 S8700 Multi-Connect Media Server must be administered to prevent conflicts with other equipment that shares the network. In the default S8700 Multi-Connect configuration, all other Ethernet connections operate on their own closed LANs. 62 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 63 Mid-market to large enterprise 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 exists in the control network. The high reliability configuration consists of the following components: Two S8700 series Media Servers Two IPSI circuit packs in each IPSI-connected port network Two Ethernet switches...
  • Page 64 S8700 Multi-Connect Media Server must be administered to prevent conflicts with other equipment that shares the network. In the default S8700 Multi-Connect configuration, all other Ethernet connections operate on their own closed LANs. 64 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 65: Avaya S8700 Series Media Server Ip-Connect Configuration

    S8700 / G650 / G700 / G350 IP-Connect solution on page 68 shows the IP-Connect G700/ G350 capacities. Figure 20: Avaya S8700 with remote G650 / G700 / G350 Media Gateways on page 66 shows an example of an S8700 with remote G700 Media Gateways.
  • Page 66 Avaya Application Solutions platforms Figure 20: Avaya S8700 with remote G650 / G700 / G350 Media Gateways Location with another Avaya IP PBX Avaya IP PBX (S8300,S8700) S8700 system with remote G650/G700 sites and IP TIE Trunk links to other Avaya PBXs...
  • Page 67 Mid-market to large enterprise Figure 21: S8700 IP-Connect - a basic phone call Table 12: Capacity limits for S8700 / G650 / G700 / G350 IP-Connect solution Feature Capacity General Business Busy Hour Call Completion Up to 100,000 Number of stations Up to 12,000 Number of IP users (IP trunks + IP stations) Up to 12,000...

  • Page 68: Main Components

    The G650 Media Gateway Avaya Communication Manager Figure 22: S8700 Media Server IP-Connect major components on page 69 shows the main S8700 IP-Connect components mounted in an open EIA-310-D- compliant, 19-inch data rack. 68 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 69 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 series Media Servers One Avaya Ethernet switch Two AS1 UPS units Issue 3.4.1 June 2005...
  • Page 70 S8700 Media Server can server through a telnet session. communicate with the Port Networks. 4. Connection from the servers to the Ethernet 9. Customer LAN. switch. 10. TN799 Control-LAN (C-LAN) 70 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 71: Definity Servers R And Si

    S8710 system supports the Avaya MCC1, SCC1, CMC1, and G650 Media Gateways. The Avaya G700 and G350 Media Gateways are also supported if there is a TCP/IP connection between the media gateway and a C-LAN circuit pack located in a MCC1, SCC1, CMC1, or G650 Media Gateway.

  • Page 72: Service Provider - Blade Server

    2 of 2 Service Provider — Blade Server Avaya’s Hosted IP Telephony offer uses the IBM eServer Blade Center Media Server to facilitate service provider IP Telephony deployments. The Blade Server supports CM 2.2 running on up to 14 server blades per chassis, or 82 blades per rack.

  • Page 73: Other Avaya Ip Telephony Servers

    Avaya IP Office is another standalone Avaya platform that supports IP Telephony for the small to mid-size market. Avaya IP Office is an IP PBX for 10 to180 stations. Avaya IP Office is not part of the Avaya Application Solutions offer, and thus is not covered extensively in this document. More information about the IP Office is available on the Avaya Support web site.
  • Page 74 Avaya Application Solutions platforms 74 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 75: Greenfield Deployment

    In general, most organizations want to protect their investment in their PBX communications system. Avaya provides ways for our circuit switched PBX customers to evolve from circuit switched systems to IP-enabled systems. This solution provides most of the advantages of IP Telephony with minimal equipment upgrades to an enterprise’s existing PBX.

  • Page 76: Media Server (H.323 Gatekeeper)

    Figure 25: A Greenfield IP Telephony deployment Media Server (H.323 Gatekeeper) The Media Servers are responsible for running Avaya Communication Manager and controlling the Media Gateways and endpoints. The Media Servers control the dial plan translations and call routing, call setup and teardown, Call Detail Record (CDR) generation, traffic management.

  • Page 77: Avaya Communication Manager

    In a Greenfield installation, the recommended gateways are the G350, G650, and the G700. The G650 houses traditional circuit switch boards and boards that support IP Telephony. The G700 and G350 house Avaya Media Modules that provide ports for non-IP endpoints, including analog and DCP telephones.

  • Page 78: Greenfield Configurations

    Telephony module has the same functionality as the TN2302AP Media Processor (MedPro) circuit pack. An extra VoIP Media Module can be inserted in the G700 for extra media-processing resources. Other Media Modules support traditional endpoints. 78 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 79: Medium-To-Large Enterprise Solutions

    Greenfield configurations Figure 26: An S8300/G700/G350 system Medium-to-large enterprise solutions S8700 / G650 IP-Connect The S8700 IP-Connect system (Figure 27: S8700 IP-Connect system on page 80) is a scalable solution that supports up to 64 G650 Media Gateways, each of which house up to four rack-mounted cabinets.
  • Page 80 Media Server is the call controller that communicates with the G700 or G350 Gateways through the C-LAN. In this configuration, the C-LAN circuit pack acts as the front-end processor for both the G700/G350 Media Gateways and IP endpoints. 80 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 81: Required Circuit Packs For S8700 Configuration

    Greenfield configurations Figure 28: S8700 IP-Connect with remote G700 or G350s Medium/Large Enterprise Remote Office Backup S8700 S8700 H.225 E1/T1 E1/T1 EIA 530A DCE EIA 530A DCE IPSI SHUT DOWN SHUT DOWN REMOVE OK TO OK TO SERVICES SERVICES USB 1 USB 1 USB 2 USB 2...
  • Page 82 IP Telephone, the media stream might shuffle (be redirected to the other endpoint) without requiring MedPro resources. Media Processors are also used to transport media streams in IP tie trunks. 82 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 83 Greenfield configurations Figure 30: Media flow path (S8700 IP-Connect configuration) For detailed characteristics of the IPSI, C-LAN, and Media Processor circuit packs, see the Avaya Application Solutions platforms chapter. Figure 31: Signaling flow Issue 3.4.1 June 2005...

  • Page 84: Communication Devices

    Greenfield deployment Communication devices Avaya stations include IP Telephones and IP Softphones. Avaya also supports IP trunks. In addition, all the Media Gateways support traditional terminals, such as analog, BRI, and DCP telephones. For detailed descriptions of Avaya IP Telephony endpoints, see the Terminals chapter.

  • Page 85: Evolution From Circuit-Switched To Ip

    Evolution from circuit-switched to IP 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 technology to increase the capacity and...

  • Page 86: Migration From Definity Server R To S8700 Multi-Connect

    Evolution from circuit-switched to IP There are three stages to upgrading from a DEFINITY G3r to an Avaya Communication Manager IP PBX: 1. Replace the G3r processor with industry-standard S8700 servers. 2. Add IP circuit packs (C-LAN and MedPro) to support IP endpoints.
  • Page 87 Migration from DEFINITY Server R to S8700 Multi-Connect 4. Install UPS units. 5. For IPSI-connected port networks, upgrade each EPN. 6. Connect the duplication links. 7. Connect the servers and the IPSIs to the control LAN. 8. Sequentially bring up the duplicated servers. Figure 33: S8700 Media Servers (Multi-Connect configuration) shows the completion of Phase 1, an S8700 Multi-Connect system that supports only traditional endpoints.

  • Page 88: Phase 2: Ip-Enable The Port Networks To Support Ip Endpoints

    Phase 2 but not Phase 1 cannot support as many IP endpoints as a system that implements both Phase 1 and Phase 2 (see DEFINITY Servers R and SI page 71). Figure 34: IP-enabled DEFINITY configuration 88 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 89: Phase 3: Server Consolidation

    Today, through the use of IP Telephony technology and the enhanced processing capabilities of the S8700 Media Servers, Avaya has a solution to consolidate smaller remote DEFINITY servers, such as ProLogix or DEFINITY ONE into an S8700 Multi-Connect system, while maintaining remote site survivability in the event of a network or processor failure.
  • Page 90 DCP endpoints. Analog trunks and ISDN trunks are also supported. To decrease operational expenses, the circuit-switched trunks back to the main site can be replaced with IP trunks. 90 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 91: Call Processing

    This chapter explains the features, the strengths, and the architecture of Communication Manager call processing. Communication Manager capabilities This section lists and explains the major features of Avaya Communication Manager that are over and above traditional PBX features: Terminal mobility...

  • Page 92: Voice And Multimedia Networking

    H.248 Media Gateway control Communication Manager uses the standards-based H.248 media gateway control protocol to perform call control of Avaya G700 and G350 Media Gateways. H.248 defines a framework of call control signaling between the intelligent Media Servers and multiple Media Gateways.
  • Page 93 All IP endpoints (IP Softphones, IP agents, and IP Telephones) H.323 voice applications should register with an Avaya gatekeeper before any calls are attempted. Communication Manager enforces call signaling (Q.931) and call control (H.245) channels from endpoints to terminate on the gatekeeper.

  • Page 94: Call Signaling

    DTMF tones. By sending tones out of band, fidelity is maintained. This method is useful when connecting to a voice mail or an integrated voice response (IVR) system, where DTMF digits are used to navigate through prompts. 94 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 95 Call Processing When this capability is used on an H.323 tie trunk between Communication Manager switches, the switch that receiving the H.245 tone message plays the required tone onto all the ports receiving the audio stream. Media stream for audio conferencing When calls between IP endpoints are conferenced, the media streams must be routed through the MedPro circuit pack.

  • Page 96: Separation Of Bearer And Signaling (Sbs)

    Figure 38: MedPro support of a three-party audio conference Separation of Bearer and Signaling (SBS) In an Avaya IP Telephony system, call signaling and bearer traffic may be routed over separate paths. This is useful for a remote branch office with only limited WAN bandwidth back to headquarters.

  • Page 97: Modem/Fax/Tty Over Ip

    This feature is enabled by default on IP trunks and inter-gateway calls, and is capable of toggling between text and voice modes. Avaya’s support for modem, fax, and TTY over IP can be summarized as follows: TTY over IP continues to be supported Modem Pass-through is supported between Avaya gateways Modem Relay at 9.6K is supported between Avaya gateways...
  • Page 98 Call processing Avaya’s modem, fax, and TTY over IP support is subject to the following limitations: QOS is required, even on LAN. Avoid MoIP where possible (especially over a WAN environment) Use circuit-based resources on the same gateway Use different classes of service and restrictions...

  • Page 99: Ip-Based Trunks

    IP-based trunks IP-based trunks In circuit switched networks, trunks provide the means to interconnect PBXs with each other and to the PSTN. Connection to the public network allows PBX station users to call and be called by terminals that are not part of the PBX private network of the PBX. An analogous arrangement exists in packet-switched IP networks.

  • Page 100: Ip Tie Trunks

    IP network. In addition, 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 will also include Instant Messaging (IM) client software, which is a SIP-enabled application that connects to the Avaya Converged Communication Server for IM control.

  • Page 101: Converged Communication Server

    Messaging and SIP trunking. SIP-enabled endpoints need only register with the CCS; they can be but do not need to be managed by Avaya media servers. In addition, the CCS supports the SIP-enabled Instant Messaging application between users of IP Softphone R5.x client software;...

  • Page 102: Mobility

    ID-enabled analog telephone that is connected directly to the Avaya Communications Server. Extension to Cellular provides this capability regardless of the cell phone’s cellular service provider or the cellular standard in use.

  • Page 103: Communication Applications

    Communication applications Call Center The Avaya Call Center provides a total solution for a customer’s sales and service needs. Building on the performance and flexibility of the Avaya Communication Manager, customers can select from a powerful assortment of features, capabilities, and applications that are specially designed to enhance call center operations.

  • Page 104: Computer Telephony Integration (Cti)

    Avaya Computer Telephony that enables integration to Communication Manager ASAI. Telephony Application Programming Interface (TAPI). Telephony Services Application Programming Interface (TSAPI) is an open API supported by Avaya Computer Telephony that allows integration to Communication Manager ASAI. 104 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 105: Best Services Routing (Bsr) Polling

    Communication applications Best Services Routing (BSR) polling Best Service Routing (BSR) polling over QSIG Call Independent Signaling Connections (CISCs) and Temporary Signaling Connections (TSCs) provides the ability to do BSR polling between multiple site over H.323 IP trunks without requiring an ISDN PRI B-channel. QSIG CISC/TSCs are used by BSR polling software to reduce the need for the IP Media Processor circuit pack, thereby making BSR a cost-effective, multi-site solution for an enterprise-wide contact center.
  • Page 106 Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 107: Avaya Lan Switching Products

    Converged infrastructure LAN switches C360 converged stackable switches The Avaya C360 converged stackable switch series is a line of stackable, multilayer switches that provide high availability, quality of service (QoS), and Power over Ethernet (PoE) to enhance converged network infrastructure operations. With a range of PoE and non-PoE configurations, the C360 series is a powerful, yet cost-effective option for enterprise applications.
  • Page 108 Avaya C360 switches are multilayer switches and can be upgraded with a license to provide routing (Layer3) functionality. 108 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 109 Converged infrastructure LAN switches Features of the C360 converged stackable switches The C360 Converged Stackable switches offer features in the following categories: Stacking Layer 2 features Layer 3 features Management Power over Ethernet (PoE) Stacking Up to 10 switches can be stacked together. Features such as Spanning Tree, redundancy, VLANs, and SMON are common to the stack.
  • Page 110 - Telnet (up to five simultaneous connections) or SSHv2 (up to two simultaneous connections) over the IP network You can use TFTP for the download/upload of configuration files or the download of firmware files 110 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 111 Radius authentication enables centralized user management. You can use all appropriate tools of the Avaya Integrated Management suite for administration. System logging can occur by terminal, internal file, or Syslog server.

  • Page 112: P330 Ethernet Stackable Switch

    Figure 43: Avaya P330 Ethernet stackable switching system The Avaya P330 family of stackable Ethernet switches can operate as part of a total workgroup solution. You can stack the P330 switches to allow for pay-as-you-grow scalability, from a few to hundreds of ports and N+1 redundancy.
  • Page 113 The stacked switches connect using the Avaya X330STK stacking sub-modules that plug into a slot in the back of the Avaya P330. If the stack is split between two racks you can connect the P330 by using the X330SC or X330LC cables. The Avaya X330RC cable connects the top and bottom switches in the stack and provides redundancy and hot-swappability in the same way that modules can be swapped in a modular switching chassis.
  • Page 114 Auto-negotiation simplifies configuration of LAN connections by automatically selecting the port transmission mode for devices — either half- or full-duplex. Traffic prioritization (802.1p) allows real-time traffic classification into 8 priority levels mapped to 4 queues. 114 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 115 Converged infrastructure LAN switches The use of the IEEE 802.1Q tagging for VLANs and per-port VLAN is supported. Multiple VLANs per port allow access to shared resources by stations that belong to different VLANs. The use of the IEEE 802.1w standard for Rapid Spanning Tree Protocol (RSTP) provides rapid convergence of the spanning tree in case of link failure.
  • Page 116 Simple network time protocol (SNTP) or TIME protocols are available to provide a consistent timestamp to all switches from an external source. You can use all appropriate tools of the Avaya Integrated Management suite for administration. You an restrict access to management interfaces by IP address.

  • Page 117: C460 Converged Multi-Layer Switch

    C460 converged multi-layer switch For enterprises looking to deploy Avaya Communication Manager Communications Applications, the Avaya C460 converged multi-layer switch is a highly resilient network platform designed to provide high-availability support for mixed data and IP Telephony deployments. The Avaya C460 features a compact modular six-slot chassis with the following main...

  • Page 118: Avaya Power Over Ethernet (Poe) Switches

    Avaya LAN switching products For enterprises deploying Avaya Communications Manager for mission-critical call center and large-scale campus environments, the C460 offers an ideal IP Telephony platform that combines fault tolerance, network responsiveness for business continuity, and integrated management and monitoring for converged networks.

  • Page 119: Midspan Power Unit

    Midspan Power Unit 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 powered off if the power resources of the module are exhausted.
  • Page 120 The 1152A1 power unit powers only through pairs 4/5 (+) and 7/8 (-). Barrel connector through brick transformer This brick type transformer provides 5 watts of power to the telephone. The Avaya telephone treats this brick as the primary power source, and will not accept power from the Ethernet cable if the barrel is seated into the telephone, with or without the brick attached to AC power.

  • Page 121: Converged Infrastructure Security Gateways

    This is expected because Ethernet is an open standard. Interoperability with Wireless Access Point products The 1152A1 unit can also power Avaya’s Wireless Access Point systems. The AP1, AP2, or AP3 act as a bridge between the wireless and the wired LAN. This system requires a 5-volt...
  • Page 122 The VSU 100 Gateway for small and medium businesses The VSU 2000 Gateway for branch offices The VSU 5000 Gateway, the VSU 7500 Gateway, and the Avaya SG208 Security Gateway for large enterprises and managed data service providers Note: The Avaya SG208 Security Gateway replaced the VSU 10000 in 2003.

  • Page 123: Vpn Client

    VPNremote Client not only provides support for data applications, but also delivers voice-over-VPN that enables you to use the Avaya IP Softphone for secure, convenient telephony from your laptop computer. To protect the integrity and...
  • Page 124 Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 125: Terminals

    Avaya IP Softphone Figure 45: Avaya IP Softphone Avaya IP Softphone is for employees who work remotely, on the road or at home. Accessed through a simple graphical interface on the screen of a PC or laptop computer, the IP Softphone gives mobile workers the full suite of Avaya Communication Manager features and functions, whenever and wherever they need them.

  • Page 126: Softphone Operating Modes

    Avaya IP Telephone mode The Avaya IP Telephone mode enables users to log into and control their Avaya IP Telephone from the Avaya IP Softphone. Users can speak and listen through their telephone, but unlike the Telecommuter configuration, users can make and handle calls from both the Avaya IP Softphone interface and the IP Telephone.

  • Page 127: Avaya Ip Agent

    Avaya IP Agent Avaya Digital Telephone The Avaya Digital Telephone mode is similar to the Avaya IP Telephone mode in that it enables users to log into and control their Avaya Digital (or IP) Telephones from the Avaya IP Softphone.

  • Page 128: Avaya Softconsole

    Terminals Avaya Softconsole Avaya Softconsole™ is a software attendant console that builds on the features of the popular Avaya 302 Attendant Console. Searches internal and external directories Displays detailed caller information on up to six calls simultaneously New interface Comprehensive setup wizards...

  • Page 129: Features

    Avaya IP Softphone for Pocket PC Figure 46: Avaya IP Softphone for Pocket PC The Avaya IP Softphone for Pocket PC is a downloadable application for customers who own an Avaya IP Softphone license. It delivers the full set of Communication Manager call features through a graphical display of your Avaya multiline telephone, with its identical extension number, speed dial buttons, and personal feature settings.

  • Page 130: Avaya 4600 Series Ip Telephones

    Ability to modify the look and feel of the graphical user interface with a swap skin capability. Call log history. Avaya 4600 Series IP Telephones Figure 47: Avaya 4602 IP Telephone Figure 48: Avaya 4606 IP Telephone 130 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 131 Avaya 4600 Series IP Telephones Figure 49: Avaya 4612 IP Telephone Figure 50: Avaya 4620 IP Telephone Figure 51: Avaya 4624 IP Telephone Issue 3.4.1 June 2005...

  • Page 132: Networking Coordination

    Avaya Communication Manager directly to the desktop. They are an essential part of converged voice and data networks that are built with the Avaya Application Solutions components. These telephones deliver an extensive set of features, high audio quality, and have an attractive streamlined design.

  • Page 133: Features And Applications

    Avaya 4600 Series IP Telephones The 4600 series IP Telephones require the Avaya Application Solutions Circuit packs TN799C or higher C-LAN board for registration to the gatekeeper and signaling stream, and the TN2302AP (MedPro) for call setup and media stream. In the case of the G700 Media Gateway, the VoIP Engine or VoIP Media Module provides the support for media stream.
  • Page 134 Terminals Table 18: Avaya 4600 series IP Telephone features and applications (continued) Feature Application Web Browser (4620 and 4630 sets only) Application This feature provides Web Access to HTML Web-based information. The 4620 Web Access application is analogous to the application on the 4630. However, different display capabilities cause the 4620 telephones to have a simpler, less capable Web interface than 4630 sets.
  • Page 135 Avaya 4601 IP Telephone The Avaya 4601 IP Telephone is a low-end phone designed for reception areas and other applications where cost is the driving factor. It is similar to the 4602, however, it lacks a display. Figure 53: Avaya 4601 IP Telephone...
  • Page 136 SIP phone by downloading SIP firmware from the file server. When operating in SIP mode, the 4602 uses the Avaya CCS proxy server as its call controller, rather than connecting to CM. An administrative web interface on the phone allows administrators to set up the SIP dial plan and administer features and other parameters.

  • Page 137: Communication Manager Support For The 4600 Ip Telephone Series

    Communication Manager platforms, the endpoints also operate with Avaya DEFINITY ECS G3r or G3si, DEFINITY ProLogix, as well as Avaya IP Office. The 4630 telephone has been developed as an IP endpoint for the Avaya Media Servers using Avaya Communication Manager and DEFINITY Servers. DEFINITY Release 10 and Communication Manager Release 1.0 are the first releases of software to provide native...

  • Page 138: Wireless

    This is software that, when combined with a cellular phone, offers one-number access for business connectivity anytime, anywhere with no missed calls. Avaya Communication Manager enables the Avaya Extension to Cellular to transparently bridge calls from the Avaya server to any digital cellular phone, regardless of service provider or cellular standard.

  • Page 139: Section 2: Deploying Ip Telephony

    Section 2: Deploying IP Telephony Issue 3.4.1 June 2005...
  • Page 140 140 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 141: Traffic Engineering

    Introduction 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 specifications Endpoint traffic usage Call usage rates Communities of interest Expanded COI matrices COIs for multiple-site networks...

  • Page 142: Design Inputs

    This section summarizes the essential design elements that the customer must specify. Topology An Avaya Communication Manager system consists of a server and all of the equipment under that server’s control. Such equipment may be geographically dispersed among a variety of sites, and the equipment at each site may be segregated into distinct logical collections known as Network Regions.
  • Page 143 Communication Manager systems in the network, or through the public switched telephone network (PSTN). Although Avaya products are IP enabled, the products must interface with circuit-switched endpoints and systems. For example, Communication Manager systems require circuit-switched trunks to access the PSTN because central offices today are not equipped for IP trunking.

  • Page 144: Endpoint Specifications

    Common defaults for station traffic usage in general business scenarios are: Light traffic—0.056 Erlangs per station (stations average 5.6% usage) Moderate traffic—0.11 Erlangs per station (stations average 11% usage) Heavy traffic—0.17 Erlangs per station (stations average 17% usage) 144 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 145 Design inputs 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 is difficult to assign a typical default value for usage per trunk.

  • Page 146: Call Usage Rates

    So, SUR represents the average number of stations in a particular group that are simultaneously in use, while PUR represents the average number of endpoints, including stations and trunks, in a particular group that are simultaneously in use. 146 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 147: Communities Of Interest

    Call usage rates Similarly, the term call usage rate (CUR) represents the average number of simultaneous calls that are carried by a particular facility. In an environment where essentially every call is either inbound or outbound (such as a call center), CUR and SUR are equal, because there is exactly one Communication Manager station used in each call.
  • Page 148 Intercom station usage = 40 Erlangs (2 Avaya stations per call x 20 Erlangs of intercom call usage) Inbound station usage = 30 Erlangs (1 Avaya station per call x 30 Erlangs of inbound call usage) Outbound station usage = 30 Erlangs (1 Avaya station per call x 30 Erlangs of outbound...
  • Page 149 Intercom station usage = 70 Erlangs (2 Avaya stations per call x 35 Erlangs of intercom call usage) Inbound station usage = 10 Erlangs (1 Avaya station per call x 10 Erlangs of inbound call usage) Outbound station usage = 20 Erlangs (1 Avaya station per call x 20 Erlangs of outbound...
  • Page 150 Traffic engineering 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 terminate at any of the other stations in the entire system. Analogous statements regarding this model can also be made for inbound trunk calls and outbound trunk calls.
  • Page 151 Call usage rates 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 only if it is blocked at its local trunks.
  • Page 152 Atlanta site for intercom calls. Similarly, there are 72 - 18 - 18 = 36 Erlangs of station usage in the Boston site for intercom calls, and 34 - 8 - 8 = 18 Erlangs of station usage in the Cleveland site for intercom calls. 152 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 153 Call usage rates 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 the Atlanta site corresponds to intercom calls originated in the Atlanta site.
  • Page 154 Outbound CUR from Site i total outbound CUR total station usage total intercom CUR total station usage in Site j ------------------------------------------------------------------ Intercom CUR from Site i to Site j total station usage originating in Site i 154 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 155: Expanded Coi Matrices

    Call usage rates Example 3: Empirical approach for existing systems Another possible means of populating the COI matrices exists for established systems. In such cases, the necessary information can be read from traffic reports. This method is particularly useful for customers who are considering an upgrade from their current equipment. Expanded COI matrices So far, all the discussion pertaining to COI matrices has focused on a macroscopic view of sites.
  • Page 156 Those usage rates can be broken down into finer components. Table 26: Endpoints in a three-site system on page 157 reviews the various endpoints in each site. 156 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 157 Call usage rates Table 26: Endpoints in a three-site system Endpoints Atlanta Boston Cleveland IP stations 1107 (1080 IP (450 IP (270 IP Telephones + 27 Telephones) Telephones) Road Warriors) Circuit-switched stations (540 DCP stations (180 DCP stations (36 analog stations) + 108 analog + 18 analog stations)
  • Page 158 Example 4: Expanded COI matrices (intercom CUR values only) To endpoints in site ___ 12.7 0.37 0.22 0.85 0.16 0.85 0.37 0.54 0.07 0.54 0.78 0.10 0.37 0.22 0.16 0.07 0.10 0.01 158 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 159 Call usage rates The general formula that is used to determine the expanded intercom CUR entries in Table 27: COI matrix for Example 4: Expanded COI matrices (intercom CUR values only) page 158 is: CUR generated by stations of type t in Site i intercom CUR from Site i to Site j and terminated by stations of type t in Site j where:...
  • Page 160 Site i --------------------------------------------------------------------------------- - total number of stations in Site i number of type t stations in Site j ----------------------------------------------------------------------------------- - total number of stations in Site j 160 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 161: Cois For Multiple-Site Networks

    Figure 55: Network of Avaya systems and system sites shows. Figure 55: Network of Avaya systems and system sites Figure 55: Network of Avaya systems and system sites shows three distinct Communication Manager systems, that are interconnected by IP trunk groups. This network has a total of seven sites, which are labeled “S1”...

  • Page 162: Resource Sizing

    156, can also be constructed. However, when multiple systems are networked together, the additional step of engineering the tie trunk groups must be performed. To do this, the COI matrices are used to determine the traffic flow between each pair of Avaya systems.

  • Page 163: Signaling Resources

    The TN799 C-LAN circuit pack provides the interface for a signaling channel between an IP endpoint and a packet bus (which ultimately interfaces with the Avaya server). When an IP endpoint, G350 MG, or G700 MG registers to a C-LAN circuit pack, a software object known as a C-LAN socket is allocated for that endpoint or gateway to use, for as long as it remains registered.
  • Page 164 Traffic engineering Figure 56: Examples of media streams between Avaya endpoints 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.
  • Page 165 Resource sizing Hairpinning Unlike the IP-TDM-IP connectivity option, hairpinning requires that all media processing resources for a given call reside on a single TN2302 Media Processing circuit pack or a single G350 or G700 Media Gateway VoIP Media Module. A hairpinned call is originally set up as an IP-TDM-IP call, but once the set-up process is complete, no TDM resources are required.
  • Page 166 TDM resource and one media processing resource. Each of these resources is furnished by the PN or the Media Gateway to which the circuit-switched endpoint is administered. See Figure 56: Examples of media streams between Avaya endpoints on page 164 for an example.
  • Page 167 Resource sizing being used (as opposed to a center stage), each interport network call requires two TDM resources and two media processing resources. One of each of these resources is supplied by each of the PNs that is involved in the call. In the preceding discussion, everything that applies to a PN also applies to a Media Gateway.
  • Page 168 Figure 58: Intra-site TDM and Media Processing resource requirements on page 167 and Figure 59: Inter-site TDM and Media Processing resource requirements on page 168. To illustrate, Example 4: Expanded COI matrices will be further expanded. 168 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 169 Resource sizing Example 5: TDM and media processing usage Consider the COI matrix in Table 28: Completed COI matrix for Example 4: Expanded COI matrices on page 160 in Example 4: Expanded COI matrices. A set of nine cells corresponds to calls originated in Site 1 and terminated in Site 1 (that is, the upper left group of nine cells, arranged in a three-by-three submatrix).
  • Page 170 TDM: 0 TDM: 0 TDM: 0 Media: 0 Media: 0 Media: 0 Intrasite: I, C or P TDM: 76.8 TDM: 26.7 TDM: 14.4 Media: 76.8 Media: 26.7 Media: 14.4 1 of 2 170 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 171 Resource sizing Table 30: TDM and Media Processing usages (Erlangs) for Example 5: TDM and media processing usage (continued) Endpoints Site 1 Site 2 Site 3 (Atlanta) (Boston) (Cleveland) Intrasite: C or P, C or P TDM: 40.6 TDM: 11.4 TDM: 1.9 Media: 0 Media: 0...
  • Page 172 76.8 + (2 x 12.6) = 102.0 Erlangs. Similarly, the total media processing loads in Sites 2 and 3 are 43.9 Erlangs and 17.6 Erlangs, respectively. Those numbers are also based on the assumption that media encryption was not used. 172 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 173 Resource sizing Table 31: Number of TN2302 Media Processors or G700 Media Gateway VoIP Modules required for a given carried load Carried Required Carried Required load number of load number of (Erlangs) TN2302 circuit (Erlangs) TN2302 circuit packs packs 1,001 1,063 1,125 1,187...

  • Page 174: Tn2312 Ipsi Circuit Packs

    If the number of port networks needs to be increased to satisfy the IPSI requirements, then the TDM and media processing engineering processes must be redone (since an increased number of port networks implies an increase in inter-port-network traffic). This is an iterative process. 174 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 175: Processing Occupancy

    Resource sizing Processing occupancy The Busy Hour Call Attempt (BHCA) rate of a system is the total number of calls that are attempted within that system, during its busy hour. This is distinct from the Busy Hour Call Completion (BHCC) rate of a system, which counts only those calls that have actually been completed.

  • Page 176: Ip Bandwidth And Call Admission Control

    IP endpoints requires a single bidirectional media stream through the LAN at that site. Figure 56: Examples of media streams between Avaya endpoints on page 164 indicates that each intrasite call between an IP endpoint and a circuit-switched endpoint (including PSTN trunks) also requires a single bidirectional media stream through the LAN at that site.
  • Page 177 Resource sizing The preceding discussion is summarized in Figure 61: Required number of bidirectional IP media streams for intra-site calls Figure 62: Required number of bidirectional IP media streams for inter-site calls on page 178. Figure 61: Required number of bidirectional IP media streams for intra-site calls Issue 3.4.1 June 2005...
  • Page 178 Table 28: Completed COI matrix for Example 4: Expanded COI matrices on page 160 page 169 produces the following tables of bandwidth usages that are associated with the configuration in Example 4: Expanded COI matrices. 178 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 179 Resource sizing Table 34: IP LAN bandwidth usages (Erlangs) for Example 6: IP bandwidth considerations Endpoints Site 1 Site 2 Site 3 (Atlanta) (Boston) (Cleveland) Intrasite: I, I 12.7 0.78 Intrasite: I, C or P 76.8 26.7 14.4 Intrasite: C or P, C or P Calls from site 1 to site 2 12.0 12.0...
  • Page 180 The size of the payload depends on certain parameters that relate to the codec that is used. The two most common codecs that are used with Avaya products are uncompressed G.711 and compressed G.729. The transmission rates that are associated with those codecs are 64 kbps for G.711 (this is the Nyquist sampling rate for human voice) and 8 kbps for G.729.
  • Page 181 Resource sizing Table 36: Payload size per packet 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. Table 36: Payload size per packet Packet G.711 G.729...
  • Page 182 UDP, and RTP from 40 bytes to between 2 and 4 bytes (4 bytes are assumed for this example). Using the PPP overhead of 7 bytes (which would vary if ATM, HDLC, or Frame Relay were 182 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 183 Resource sizing used) implies a total overhead of 11 bytes (88 bits) in this example. This implies the following table of WAN bandwidths, Table 39: IP WAN bandwidth requirements for media streams, which assumes the use of cRTP: Table 39: IP WAN bandwidth requirements for media streams Packet “size”...
  • Page 184 The bandwidth that is required for signaling is generally negligible in comparison to the bandwidth that is required for bearer traffic. However, since Avaya products use Separation of Bearer and Signaling (SBS), the bearer traffic and signaling traffic use distinct paths. Therefore, signaling bandwidth must be given its due consideration, despite the fact that it is negligible in comparison to bearer bandwidth.

  • Page 185: Physical Resource Placement

    Resource sizing 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 Media Processors each, and the other PN should house the final three Media Processors. Advanced users should be able to manually override the resource-placement defaults.
  • Page 186 Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 187: Security

    Security This chapter discusses the security design and features for Avaya Communication Manager, and how to operate Avaya systems securely. Note: Because this information is valuable both to those who want to protect the system Note: and to those who seek to “hack” into those systems, the information in this section is deliberately incomplete.
  • Page 188 Recommendations for your security policy Avaya recommends that you continuously review your security policy, and keep up with new threats and to make improvements each time a weakness is found. To effectively support your security policy, your company must allocate long-term resources to the development, implementation, and reassessment of the policy.

  • Page 189: Avaya Communication Manager And Media Servers

    To some extent this is true, but it is important to understand why Oryx-Pecos, Avaya’s proprietary operating system for its legacy products, is more secure than an open operating system because it does not support the types of network connections that converged voice and data network configurations demand.

  • Page 190: One-Time Passwords

    Security Avaya capitalizes on Linux’ security advantage The Avaya S8700 and S8300 Media 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 as SYN floods, ping floods, malformed packets, oversized packets, sequence number spoofing, ping/finger of death, etc.

  • Page 191: Remote Access

    Remote access Avaya S8700 and S8300 servers have a modem port for remote maintenance access, and for sending maintenance alarms calls. The server logins that establish this remote connection are separate from other logins that allow administrative functions. One login account can establish a connection, and once the link is established, a second login is necessary to administer the system.

  • Page 192: Secure Access

    FTP service that is disabled by default. Each time a file is to be transferred to the Avaya server, an administrator must log in and enable the FTP server. The file is then transferred using anonymous FTP, and the FTP server can then be disabled.

  • Page 193: Lan Isolation Configurations

    Avaya Communication Manager and Media Servers Data encryption Attacks against a system are not limited to attempts to find holes in the access structure. Avaya S8700 and S8300 servers store backup copies of critical configuration information, including authentication and account information, on external systems. If this information is stored in clear text, and the file server on which it is stored is compromised, the servers also can be compromised.
  • Page 194 Security Figure 63: Avaya S8700 Media Server with an Avaya MCC1 or an SCC1 Media Gateway To provide the most secure environment that is possible for the system, network access should be divided into separate zones of control. These zones are sometimes referred to as DMZs.
  • Page 195 Avaya Communication Manager and Media Servers Figure 64: Isolated LANs (Avaya S8700 Media Server with an MCC1 or an SCC1 Media Gateway) Figure 64: Isolated LANs (Avaya S8700 Media Server with an MCC1 or an SCC1 Media Gateway) shows how Communication Manager can be configured to allow only certain types of access to specific LAN interfaces on its PNs.

  • Page 196: Virus And Worm Protection

    Security Figure 65: Isolated LANs (Avaya S8700 Media 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, Exchange, Outlook, or Word. Because the S8300, S8500, and S8700 Media Servers are Linux-based and do not interface with these Microsoft products, they have some degree of natural immunity.
  • Page 197 During the development of the S8300, S8500, and S8700 Media 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 security holes. The exact set of tools that are used varies to keep up with the technology.

  • Page 198: Ip Telephony Circuit Pack Security

    Security 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 different Ethernet interfaces to help isolate the traffic, and protect the...

  • Page 199: Tn2302 Media Processor (Medpro)

    UDP sessions, the TN2302 is very secure, and is difficult to take out of service. Regardless, the TN2302 is completely independent of the administration, maintenance, or reliability of the Avaya Media Gateways, so it cannot be used a “jumping point” to the Media Gateways. Issue 3.4.1 June 2005...

  • Page 200: Tn799 Control Lan (C-Lan)

    IP endpoints. For more information on the security of Avaya circuit packs, see: http://support.avaya.com/elmodocs2/multivantage/95933.pdf Toll fraud This section contains information about Avaya’s design for preventing toll fraud, and includes these topics: Avaya’s security design Hacking methods Your toll fraud responsibilities...

  • Page 201: Avaya's Security Design

    Toll fraud, the unauthorized use of a system and its facilities by a third party, can result in substantial additional charges for telecommunications services. Avaya makes every effort to assist customers in their battle against “hackers” through the technology that goes into every Avaya product. Avaya Communication Manager is designed...

  • Page 202: Your Toll Fraud Responsibilities

    The indemnification enhancement is offered at no additional cost to your service agreement during warranty, or as part of a multiyear Avaya Service Agreement. The only requirement is to follow and maintain the sound security practices that every business should implement. A complete list of these security practices can be obtained from your Avaya Account Team.
  • Page 203 Toll fraud Security Audit Service The Avaya Security Audit Service is a fee-based, consultation service that provides a security evaluation of a customer’s telecommunications system. The Security Audit is conducted by a Avaya team of experts and includes: 1. Preliminary telephone interview 2.
  • Page 204 Security 204 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 205: Voice Quality Network Requirements

    The concept of voice quality has different aspects that need to be properly understood and considered. Voice quality issues are a key element in the Avaya commitment to international standardization. IP Telephony quality can be engineered to several different levels to accommodate differing business needs and budget.

  • Page 206: Codec Delay

    The purpose of the jitter buffer is to hold incoming packets for a specified period of time before forwarding them to the de-packetization (and decompression) process. A jitter buffer is designed to smooth packet flow. In doing so, it will also add packet delay. 206 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 207: Packet Loss

    The network topology can also affect jitter. Multiple paths between endpoints with load balancing enabled can contribute significant amounts of jitter. The following Avaya products all have dynamic jitter buffers to minimize delay by automatically adjusting the jitter buffer size:...

  • Page 208: Network Packet Loss

    Network packet loss Like delay, Avaya offers customers a tiered approach of packet loss recommendations to balance new network costs and limitations with business directives. Tools such as Avaya’s VoIP Monitoring Manager (VMM), the Agilent (HP) Internet Advisor, Finisar's Surveyor Explorer, Radcom's Prism, NAI's Sniffer, and others measure packet loss.

  • Page 209: Packet Loss Concealment (Plc)

    Avaya's G350 and G700 Medial Gateways, the Avaya TN2302 Media Processor (in the G650 Media Gateways), the Avaya IP SoftPhone, and the Avaya 4600 Series IP Telephone all incorporate echo cancellers designed for IP Telephony to improve voice quality.

  • Page 210: Signal Levels

    To allow for multi-country deployment of Avaya telephones and gateways, these devices facilitate programmable loss control values. In order to ensure that the signal levels are controlled properly within the scope of the voice network consisting of Avaya systems, the appropriate country-dependent loss plan should be administered.

  • Page 211: Tone Levels

    In general, it is not advised to use loss plan administration in this way without consultation with Avaya Services personnel. It is better to reduce the echo by strategic deployment of echo cancelers.
  • Page 212 Number of compressed calls Generally, G.711 is used within LANs because bandwidth is abundant and inexpensive whereas G.729 is used across WAN links because of the bandwidth savings and adequate voice quality. 212 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 213: Silence Suppression/Vad

    When no activity is detected for the configured period of time, the Avaya software informs the Packet Voice Protocol. This prevents the encoder output from being transported across the network when there is silence, resulting in bandwidth savings.
  • Page 214 Voice quality network requirements 214 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 215: 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 into those models. The links in Table 42: Integrated Management Applications take you to the corresponding product descriptions.

  • Page 216: Avaya Integrated Management Products

    Avaya Voice Announcement Manager Avaya MultiSite Administration Avaya MultiSite Administration enables multiple administrators to access a network of multiple voice communications systems including DEFINITY Release 9 and later and Linux-based systems running all releases of Communication Manager. The Avaya MultiSite Administration application provides a web based GUI client that runs in the supported browsers and allows administrators access from any workstation on the network.
  • Page 217 Avaya media servers and other supported devices. Avaya Proxy Agent Avaya Proxy Agent provides the interface between the Fault and Performance Manager and the Avaya Media Servers that run Avaya Communication Manager. Avaya Proxy Agent: Runs on Linux, and acts as a protocol converter between the proprietary OSSI protocol and Simple Network Management Protocol (SNMP) Sends and receives alarm traps, and can filter alarms by system, type, day, and hours.

  • Page 218: Monitoring Management Applications

    G350/G700 Media Gateway and to the TN2501AP circuit packs located in voice systems. Voice Announcement Manager enables storage of announcements in WAV files, which can be sent to an Avaya G350/G700 Media Gateway or a TN2501AP without converting them. Voice Announcement Manager also provides a repository to backup and restore announcement files, the ability to broadcast .wav files to multiple voice announcement over LAN sources, and the...

  • Page 219: Avaya Network Management Applications And Device Managers

    Avaya VoIP Monitoring Manager Avaya VoIP Monitoring Manager is a client/server Voice over IP (VoIP) monitoring application that tracks the quality of voice transmissions over the network. Avaya VoIP Monitoring Manager product runs on Windows 2000/2003, and offers these features: Receives quality of service (QoS) statistics from Avaya IP endpoints and displays this data in graphs and reports.
  • Page 220 Avaya QoS Manager The Avaya QoS Manager is the main tool for administration of access policy and QoS in Avaya voice and wireless gateways and Avaya edge/core switches providing a complete coverage of an Avaya-based network.
  • Page 221 Avaya Web site and recommends updates when newer versions are available. Software Update Manager can also be used as an inventory tool for Avaya data and wireless gateway devices, providing a list of Avaya devices residing in the network.
  • Page 222 Avaya Device Managers Avaya Device Managers are applications that simplify the configuration, fault diagnosis, and management of specific Avaya data products. Device managers provide an in-depth look at network behavior, delivering the tools required for end-to-end device management. The device managers provide a real-time graphical view of each device using color-coding to indicate individual port and LAG status.

  • Page 223: Third-Party Network Management Products

    This section describes some third-party monitoring tools that might provide benefit to companies implementing IP Telephony. Avaya is not involved with the development of these products. Inclusion on this list is not exhaustive, nor does it represent an endorsement from Avaya.

  • Page 224: Hp Openview Network Node Manager

    Network Node Manager to fit your particular needs. The NNM serves as a SNMP manager, trap collector, and connectivity tester. It also acts as a framework for the attachment of other programs, such as Avaya MultiService Network Manager. Topology discovery visually shows the interconnection of routers, switches, and endpoints.

  • Page 225: Distributed (Component)

    Many of the tools are included with the purchase of networking equipment, and many are open source. Also, many of these tools are more specialized on a specific platform or task than centralized management tools. Most Avaya Integrated management products, including Avaya VoIP Monitoring Manager, fall into this category.

  • Page 226: Centralized (Hybrid)

    SNMP trap receiver for alarm data sent by networking devices. It also provides network topology discovery and availability testing. Figure 67: Centralized management model Additional management tools, such as Avaya MultiService Network Manager, attach to the framework (Figure 67: Centralized management model).
  • Page 227 Network management models In practice, it is rare for an enterprise to completely embrace the centralized model. Some applications may not “bolt on” to a particular framework, for example. Also, sometimes an enterprise writes a “homegrown” application to cover an outage with the management server. In addition, the distributed model is useful for times when the central management tool is unavailable.
  • Page 228 Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 229: Reliability And Recovery

    Hardware-design considerations, software-design and recovery considerations, IP Telephone and remote media gateway recovery, and overall maintenance strategy are also described. The reliability tables specify the reliability performance of Avaya Application Solutions building blocks. This chapter contains information on these topics:...

  • Page 230: Reliability

    For large systems, Avaya S8700 Media Servers provide server redundancy, with call preserving fail-over, on the strength of a Linux operating system. The Avaya S8300 Media Servers can further enhance redundancy by serving as Local Survivable Processors (LSPs) within networks.

  • Page 231: High Availability - General Design Considerations

    Reliability Table 43: Expected range of typical availability shows the range of availability that is typically expected of communications systems: Table 43: Expected range of typical availability Availability Downtime Reliability Who might need this per year level 99.95 4 ½ hours “Standard”...
  • Page 232 30% of the software code for Avaya Communication Manager is dedicated to the maintenance subsystem. The firmware that runs the circuit packs, which also interacts with the maintenance software, is similarly designed.
  • Page 233 4. Based on an internal survey of reputable vendors. The data in Table 45 shows that in several cases Avaya’s subassemblies are so reliable that it would take twice the number of industry-typical subassemblies to reach the same availability level.

  • Page 234: S8700 Server Complex

    Reliability and Recovery S8700 Server Complex The high availability philosophy is scrupulously implemented the Avaya S8700 server complex: Linux is the operating system (OS) for many reasons: - Provides access to full source for quicker bug-fix turnaround - Allows easy system customization for high availability enhancements...

  • Page 235: Avaya S8700 Media Server

    Avaya S8700 Media Server While all businesses require solid performance from their communications systems, there are increasing levels of “availability” performance needed. To meet that need, the Avaya S8700 Media Server and its associated gateways accommodate three availability levels, as shown in Table 46: S8700 configuration reliability levels.
  • Page 236 This availability does not include availability of the customer’s data networks, Note: PSTN contributions, or contributions due to power outages. A conservative MTTR of 4 hours is assumed, which includes travel and repair time. 236 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 237 Reliability S8700/G650 IP-Connect hardware availability Table 48: S8700 IP-Connect hardware availability in two reliability configurations lists the IP-Connect hardware that is available in the two reliability configurations. Table 48: S8700 IP-Connect hardware availability in two reliability configurations Sub- Standard (duplex) reliability High reliability system Failures/...
  • Page 238 Reliability and Recovery Configuration drawings Figure 68: S8700 Media Server in a standard reliability configuration 238 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 239 Reliability Figure 69: S8700 Media Server in a high reliability configuration Issue 3.4.1 June 2005...

  • Page 240: Avaya S8500 Media Server

    Co-resident Remote Maintenance Board, which provides the following functionality regardless of the state of the server: - Ability to report alarms to Avaya Services over the modem dial out - Ability to report alarms over the LAN - Ambient temperature, power supply voltage and fan monitoring, and administration...

  • Page 241: S8500/G650

    The S8500 system supports the Avaya MCC1, SCC1, CMC1, and G650 Media Gateways. The Avaya G700 and G350 Media Gateways are also supported, provided that there is a TCP/IP connection between the media gateway and a C-LAN circuit pack located in a MCC1, SCC1, CMC1, or G650 Media Gateway.

  • Page 242: Avaya S8300 Media Server With G350 Or G700 Media Gateway

    PN 3 PN 4 Avaya S8300 Media Server with G350 or G700 Media Gateway The S8300 Media Server, like the S8700 Media Server, accommodates several levels of availability performance. In contrast to the S8700 that uses various levels of duplication for processing and Port Network (PN) connectivity for bearer and signaling to add heightened layers of availability, the S8300 is designed to use a Local Spare Processor (LSP).
  • Page 243 IP endpoint is homed to at least 2 systems that are run by Communication Manager (S8300, or otherwise). Avaya IP Telephones have multi-homing abilities, and can be configured to re-home to any Communication Manager-run system. For example, in a configuration with @8700 at a main site and S8300-ICC or G700 at remote site, the telephones at the remote site could re-home to main S8700 through separate Ethernet switches.

  • Page 244: Avaya Definity Server R

    This availability does not include availability of the customer’s data networks, Note: PSTN contributions, or contributions due to power outages. A conservative MTTR of 4 hours is assumed, which includes travel and repair time. Table 51: Avaya DEFINITY Server R hardware availability for three reliability configurations Sub- Standard reliability...

  • Page 245: Avaya Definity Server Si And Csi

    Maintenance architecture Avaya DEFINITY Server SI and CSI Table 52: Avaya DEFINITY Server SI and CSI hardware availability for two reliability configurations Sub- Standard reliability High reliability system (single processor carrier) (CSI only) Failures/ MTBO Availability Failures/ MTBO Availability year...

  • Page 246: Software Failure Recovery Levels

    All systems are provided with remote diagnostics capability, which enables rapid troubleshooting and maintenance, in the cases where the system cannot repair itself. Studies have shown that most problems experienced by Avaya systems are self-corrected without impact to the customer. Even with the highly reliable hardware components discussed previously, this sophisticated maintenance management implementation is required to attain the 99.99 –...
  • Page 247 Maintenance architecture Figure 73: Avaya Communication Manager’s recovery levels Restarts These automatic recovery levels are listed from mildest to strongest, which is also from quickest to slowest and more frequent to less frequent: Single process restarts System warm restarts System cold restarts...

  • Page 248: S8700 Multi-Connect And Ip-Connect Software Availability

    2 The above reflects availability due to software reliability and recovery only and does not reflect the effects of hardware failures, network failures, software upgrades, media gateway failures, IP phone failures, or failures due to improper system configuration 248 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 249: Ip Endpoint And Remote Media Gateway Recovery

    (early-introduction and in-house) systems. IP endpoint and remote media gateway recovery Avaya’s distributed IP-based systems can also enjoy increased availability by virtue of the “alternate gatekeeper.” When IP Telephones register with Communication Manager, they are given a list of “alternate gatekeepers” to which they can re-register in the event of a failure.
  • Page 250 Reliability and Recovery IP endpoint recovery The Avaya server is designed to have a scalable architecture with different server components. These components provide processing and relay signaling information between Communication Manager and the Avaya IP endpoints. The architecture is inherently distributed, thus allowing the system to be scalable to handle large number of endpoints, and flexible to work in different network configurations.
  • Page 251 This procedure is used for the H.225.0/RAS signaling channel, and depends on the exchange of RAS keepalive messages between an IP endpoint and the server. The Avaya server uses this procedure to determine if a currently registered endpoint is still available. The endpoint uses the procedure to determine whether the server is reachable or not.
  • Page 252 Local Survivable Processors (LSP) as secondary addresses. This practice gives a media gateway the best possible chance of registering with its primary call controller before registering with the LSP and entering into survivable mode. 252 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 253: Disaster Recovery And Business Continuity Solution

    G350 configuration, up to 50 LSPs are available and ready for the fail-over process. The LSP (an S8300 media server running Avaya Communication Manager software) is always ready to acknowledge service requests from IP telephones and gateways that can no longer communicate with their main controller.

  • Page 254: Remote Ip Telephony And Media Gateway Survivability

    IP telephones and media gateways will be forced to switch back to their original gatekeepers. The process of "switching back" can take under 3 minutes. Using Avaya Site Administration, this task could even be automated and run at times when user impact would be minimized.

  • Page 255: Design For High Availability

    Design for High Availability Design for High Availability As enterprises accelerate their migration from traditional circuit-switched telephony services to IP Telephony solutions, a major consideration is their ongoing concern as to the potential reliability of the proposed IP voice services versus that of their current infrastructure. Indeed, in many call center environments, the potential cost of downtime is often greater than the implied benefits of migrating to IP Telephony.

  • Page 256: Assessment Methodology And Criteria

    Definition of Critical Outages and Downtime The industry recognized criteria used for defining failure, outages and the downtime minutes experienced is based on the Telecordia (Bellcore) GR-512 Reliability Model requirements for telecommunications equipment. 256 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 257: Hardware Availability Assessment

    "planned," and by definition, will not count against the availability of the system. * Outages of the enterprise’s IP data network and failure of non-Avaya products will not count against the availability score for the Avaya furnished solution components (products).
  • Page 258 Evaluation of the model along with the failure rates and repair/recovery rate leads to the estimation of the individual steady-state probabilities and failure rates. Example: - Consider an Avaya solution that features duplex Avaya S8700 Media Servers, which are operating in an active/standby mode. The corresponding Markov state-transition...
  • Page 259 For example, consider a configuration with a remote media gateway in a branch office that generates approximately 10% of the total enterprise traffic. Upon failure of the Avaya Media Gateway serving the branch office site, the contributed downtime of that gateway being off-line...

  • Page 260: Software Availability Assessment

    The outcome of the data analysis puts the availability (uptime) for the Avaya Communication Manager software application in the range of 99.999% to 99.9999% (with 90% confidence). For the purpose of projecting the full system availability, the average of the two numbers (99.9995%) for the software availability value is used.

  • Page 261: Example: A Geographically Distributed Solution

    As such, the responsibility for LAN availability rests with the enterprise. With proper engineering and redundancy planning efforts, Avaya believes that a enterprise’s LAN has the potential of meeting 99.99% to 99.999% availability. Such high availability depends on proper...
  • Page 262 The quantity of C-LAN and Media Processor circuit packs or media modules follow the recommendations in Section 2.1 for supporting the calculated traffic load, and have not been engineered with N+1 reliability. 262 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 263 Design for High Availability Figure 75: Case Study I: Configuration of the Three Sites Boston Site 2: Branch Office End Users: 648 Atlanta WAN Edge S8700 IPSIs: 1 Routers MedPros: 2 C-LANs: 2 G650 PSTN Cleveland G650 G650 PSTN Site 3: Branch Office End Users: 270 Site 1: Headquarters PSTN...
  • Page 264 Configuration Availability and Impact of WAN Outages on Each Site on page 264 represent Avaya Communication Manager solution availability values. The site availability values listed in column 4 include the impact of the enterprises’ data network availability value on each site’s solution.
  • Page 265 Design for High Availability A similar approach assesses the availability in Cleveland, and is shown in Table 58: Weighted System Availability in Cleveland. Table 58: Weighted System Availability in Cleveland Full Solution Availability Projected Weighted Downtime minutes. % of traffic generated in Atlanta Annual (43.3% + 14.2%) 263 = 151...
  • Page 266 LSP (S8300) Site 3: Branch Office Site 1: Headquarters End Users: 306 End Users: 1755 2 G700 Media Gateways IPSIs: 2 C-LANs: 6 cydfcas2.pdf KLC 121103 Alternate Call Control signaling path to LSP 266 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 267 Design for High Availability Table 59: Case Study II: Cleveland and Boston Local Availability values are improved by LSP. Atlanta’s Availability value is improved by N+1 IP resources. Avaya Product Complete Solution including data network Availability Site Availability Annual Availability...
  • Page 268 Redundant WAN links are present and properly configured to converge rapidly in case of an outage. Signaling and media traffic may take different routes across the network. IP phones have at least three valid gatekeeper addresses that do not depend on the same WAN link. 268 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 269 Design for High Availability Figure 77: Figure 4: Case Study III: Three-site configuration with Boston Atlanta S8700 WAN Edge Site 2: Branch Office Routers G650 End Users: 648 IPSIs: 1 MedPros: 3 C-LANs: 3 PSTN G650 G650 Cleveland Customer LAN PSTN PSTN Site 1: Headquarters...
  • Page 270 Cleveland % of traffic between Atlanta and Cleveland (2.7% + 2.2%) 263 = 47 Annual downtime minutes due to failure in Atlanta, WAN and in Cleveland 1 of 2 270 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 271 Case Study IV (99.999% availability in Atlanta, 99.99% full system availability) With Avaya Communication Manager 2.0, the Avaya G650 Media Gateway can provide the optimum 99.999% availability using redundant IPSI connections. The G650 configuration supports two IPSI circuit packs in active/standby mode.
  • Page 272 S8700 Servers Avaya Product Complete Solution including data network availability Site Availability Annual Availability Per Site Downtime Annual Minutes Downtime Minutes Atlanta 99.999% 99.999% Boston 99.997% 15.8 99.995% Cleveland 99.99% 99.989% 272 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 273 As shown by the examples, Avaya IP Telephony solutions offer flexibility for designing a highly available system. The optimum 99.999% availability within a site must include redundancy and optimized data network design.
  • Page 274 Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 275: Section 3: Getting The Ip Network Ready For Telephony

    Section 3: Getting the IP network ready for telephony Issue 3.4.1 June 2005...
  • Page 276 276 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 277: Ip Telephony Network Engineering Overview

    Overview 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 limitations of shared-media hubs, network design was generally well done.
  • Page 278 WAN. If links are not properly sized or queuing strategies are not properly implemented, the quality and the timeliness of voice and data traffic will be less than optimal. 278 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 279: Voice Quality

    IP trunk that links the west coast of the United States to India. This link could add a fixed delay of 150 milliseconds (ms) into the overall delay budget. Perfectly acceptable voice quality is attainable, but will not be “toll” quality. Therefore, Avaya presents a tiered choice of elements that make up the requirements.
  • Page 280 To ensure good and consistent levels of voice quality, Table 66: Factors that affect voice quality lists Avaya’s suggested network requirements. These requirements are true for both LAN only and for LAN and WAN connections. Table 66: Factors that affect voice quality...

  • Page 281: Best Practices

    VLANs. Placing voice packets on a separate VLAN or subnetwork from data packets is a generally accepted practice to reduce broadcast traffic. When data is on a shared LAN, this practice also reduces contention for the same bandwidth as voice. Note that Avaya IP Telephones provide excellent broadcast storm protection. Other benefits become available when using VLANs, but there can be a substantial cost with initial administration and maintenance.

  • Page 282: Common Issues

    Virtual Private Network (VPN). Large delays are inherent in some VPN software products due to encryption, decryption, and additional encapsulation. Some hardware-based products, including Avaya VPN products, encrypt at near wire speed, and can be used. In addition, if the VPN is run over the Internet, sufficient quality for voice cannot be guaranteed unless delay, jitter, and packet loss are contained within the parameters that are listed above.

  • Page 283: Network Design

    IP Telephones, the uplink to the Ethernet switch should be a 100-Mbps link, so that there is more bandwidth to be shared between the telephone and the computer. Sometimes enterprises are unable to follow these guidelines, and Avaya’s solutions can be made to work in some less-than-ideal circumstances. If IP Telephones will share a subnetwork...
  • Page 284 10-Mbps links. Perhaps a worst-case example is the scenario where Avaya IP Telephones are deployed on a large subnetwork that is running IPX or other broadcast-intensive protocol, with broadcasts approaching 500 per second. Although the performance of the IP Telephones and the voice quality can be satisfactory in this environment, this type of deployment is strongly discouraged.

  • Page 285: Vlans

    VLANs. The IP Telephone is on one VLAN, and a personal computer that is connected to the telephone is on a separate VLAN. Four sets of configurations are given: Avaya Cajun P330 v3.2.8 and later, Avaya Cajun P330 pre-3.2, Cisco CatOS, and some Cisco IOS.
  • Page 286 If no routing process is associated with a VLAN, devices on that VLAN can only communicate with other devices on the same VLAN. For more information, use the links below to see Avaya’s white paper, “LANs and VLANs: A Simplified Tutorial.”...
  • Page 287 VLAN binding feature. In addition, the port does not need to be a trunk at all to forward multiple VLANs. For one application, connecting to an Avaya IP Telephone, the port must not be a trunk (do not issue the set trunk command).
  • Page 288 VLAN binding (single-VLAN scenario) With Avaya, it is possible to set the Layer 2 priority on the IP Telephone, even if the telephone is not connected to a trunk or multi-VLAN port. That is, the Avaya switch does not need to be explicitly configured to accept priority-tagged Ethernet frames on a port with only the port VLAN or the native VLAN configured.

  • Page 289: Ip Addressing

    Cisco switches behave differently in this scenario, depending on the hardware platforms and OS versions. Table 70: Cisco hardware characteristics shows Avaya’s laboratory test results with a sample of hardware platforms and OS versions. Table 70: Cisco hardware characteristics Hardware platform /...

  • Page 290: Overview Of Ip Addressing

    Address Translation (NAT). If a company is connecting its network to another company, it must take care that their RFC 1918 addresses do not overlap. Overlapping address ranges prohibit unimpeded communication across affected networks. 290 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 291: Dhcp

    DHCP is a broadcast protocol. which means that request messages from DHCP clients such as Avaya IP Telephones are seen by all devices on the local network, but are not forwarded to additional subnetworks. If the DHCP server is present on a different network, DHCP forwarding must be enabled on the router.

  • Page 292: Ip Terminals Deployment

    Telephone Basics Basic information on IP telephones is covered in the following sub-sections: Speed and duplex 30A base switch Sequence of operation Connecting a personal computer to an IP Telephone 292 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 293 (one port receives at 100 mbps, but the other can only send at 10 mbps). The Avaya IP Telephone is designed with a single-speed bus in the hub, and does not perform these functions. Instead, these functions are transferred to the enterprise Ethernet switch, where they really belong.
  • Page 294 Note that this step is bypassed if the telephone is manually configured with all the necessary information. Also note that a protocol analyzer that is attached to the PC port of an Avaya IP Telephone with a: Switch (4602SW, 4620), sees only broadcast packets.

  • Page 295: An Ip Telephone And An Attached Pc On Different Vlans

    Each request message is answered by the media controller with a RAS-Registration Confirm (RCF) message. 9. Unregistration messages. If the Avaya Media Server intentionally unregisters a set, or if the set intentionally unregisters itself, the message sent by either the media controller or the set is a RAS-Unregistration Request (URQ).

  • Page 296: An Ip Telephone And An Attached Pc On The Same Vlan

    L2 signaling. Layer 2 CoS tag for Ethernet frames that contain signaling packets. Set this to a value between 0 and 7. This value is sent to the telephone by Avaya Communication Manager, as configured on the IP Network Region form.

  • Page 297: Dhcp And Tftp

    IP Telephone on the network individually. Trivial File Transfer Protocol (TFTP) provides a way to transfer files that does not require user intervention. TFTP is used by Avaya IP Telephones to download their configuration files, and the latest firmware.
  • Page 298 TFTP server path should not be used. Avaya can use a special option, Option 176, to pass these values. Avaya has done significant testing of and had good success with Option 176 on the Microsoft Windows 2000 DHCP server and the ISC DHCP server (common on Linux and Unix platforms).

  • Page 299: Powering Ip Telephones

    IP terminals deployment Powering IP Telephones The Avaya 4600 Series IP Telephones were designed to use flexible powering methods. Some of these powering solutions require the use of special cables that are designed specifically for the Avaya 4600 Series telephones.
  • Page 300 Configuring the IP Telephones for power The Avaya 4600 Series IP Telephones are comprised of the following models: 4602 IP Telephone (no barrel connector, one RJ45 jack, no switch, no hub) 4606 IP Telephone (barrel connector, two RJ45 jacks, built-in hub)
  • Page 301 Greenfield installations, or an 1152A1 Mid-Span Power Distribution Unit for legacy systems. The Avaya P333T-PWR switch with Power over LAN capability can use either the data (pins 1/2 and 3/6) or spare (pins 4/5 and 7/8) pairs for power feeding. A Category 5 Ethernet cable from an Ethernet LAN Switch carrying DATA is connected to the “data”...

  • Page 302: Wan

    Avaya recommends using strict priority queuing for voice packets, and weighted-fair queuing for data packets. Voice packets should always get priority over non-network-control data packets. This type of queuing is called Class-Based Queuing (CBQ) on Avaya data networking products, or Low-Latency Queuing (LLQ) on Cisco routers.
  • Page 303 The processing power of the router determines the amount of compressed RTP traffic that the router can handle. Avaya testing indicates that a typical small branch-office router can handle 768 Kbps of compressed traffic. Larger routers can handle greater amounts. cRTP is available on Avaya and Cisco routers.

  • Page 304: Frame Relay

    IP Telephony does not operate well over per-packet load-balanced paths. This type of setup often leads to “choppy” quality voice. Avaya recommends that in situations with multiple active paths, per-flow load balancing is preferable to per-packet load balancing.
  • Page 305 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 CO over a fractional T1 circuit, which terminates onto a Frame Relay port at the CO, and onto a Frame Relay capable router at the customer premise.

  • Page 306: Vpn

    Obviously, VPNs can represent a significant source of delay, and therefore have a negative affect on voice performance. Avaya VPN products encrypt traffic with less than 1ms of delay, and thus are appropriate for IP Telephony. Also, because most VPN traffic runs over the Internet and there is little control over QoS parameters for traffic crossing the Internet, voice quality may suffer due to excessive packet loss, delay, and jitter.

  • Page 307: Convergence Advantages

    For more information, see: IP Voice Quality Network Requirements Website IP Voice Quality Document (.PDF) The following sections cover the topics: Convergence advantages Managing IP Telephony VPN issues Conclusion Convergence advantages For increasing numbers of enterprises, the VPN carries not only data, but voice communications.
  • Page 308 Firewalls can be used to enforce such policies. A firewall is a network interconnection element that polices traffic the flows between internal (protected) networks and external (public) networks such as the Internet. Firewalls can also be used to “segment” internal networks. 308 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 309: Conclusion

    The application of firewall technologies only represents a portion of an overall security strategy. Firewall solutions do not guarantee 100% security by themselves. These technologies must be complemented with other security measures, such as user authentication and encryption, to achieve a complete solution. The three technologies that are most commonly used in firewall products are packet filtering, proxy servers, and hybrid.

  • Page 310: Nat

    IP header, which results in a mismatch that prohibits the control of calls. Avaya suggests using a firewall to guard against intruders, but the firewall should not provide NAT functions for IP Telephony packets unless it is Avaya Q.931 friendly.

  • Page 311: Quality Of Service Guidelines

    IEEE 802.1p/Q at the Ethernet layer (Layer 2) and DSCP at the IP layer (Layer 3) are two standards-based CoS mechanisms that are used by Avaya products. These mechanisms are supported by the IP Telephone, the S8300 Media Server, and the C-LAN and MedPro circuit packs.
  • Page 312 DSCP of 46 still does not work, because it requires 2 traffic parameter bits to be set high. When these mismatches occur, the older device mighty reject the DSCP tagged IP packet, or exhibit some other abnormal behavior. Most newer devices support both DSCP and the original ToS scheme. 312 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 313: Layer 2 Qos

    Layer 2 QoS 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.

  • Page 314: Qos Guidelines

    It is good practice to baseline the IP Telephony response on a network without QoS, and then apply QoS as necessary. Avaya Network Consulting Services can help with baselining services. Conversely, it is bad practice to enable multiple QoS features simultaneously, not knowing what effects, if any, each feature is introducing.
  • Page 315 Sufficient memory is required: device dependent. Newer IOS is required: 12.0 or later. Avaya Layer 3 switches and the X330 WAN module support both 802.1 p/Q and DiffServ QoS. Several things should be examined whenever QoS is enabled on a network device. First, the network administrator should examine the processor load on the device, and compare it to levels before QoS was enabled.

  • Page 316: Ieee 802.1 P/Q

    Communication Manager users can add the 802.1Q bytes and set the priority bits as desired. Avaya suggests that a priority of 6 be used for both voice and signaling. The Avaya line of data switches can switch frames with or without these VLAN headers, with no configuration time spent.

  • Page 317: Recommendations For End-To-End Qos

    When end-to-end QoS is desired, Avaya recommends using DiffServ, a Layer 3 CoS method. Modern can map DiffServ Code Points (DSCP) to 802.1p priority values, so 802.1p tags can be recreated on each Ethernet link. This functionality is supported in Avaya Layer 3 switches, and the X330 WAN module.
  • Page 318 Note that older routers might require a DSCP setting of 40 (101000), which is backward compatible to the original TOS byte definition of critical. But again, Avaya products and software allows users to set any of the 64 possible DSCP values to work with your voice quality policy.

  • Page 319: Rsvp

    IP Telephones and media processors attempt to establish a reservation for each call. If the reservation fails, Avaya endpoints still try to place a call, but lower the DiffServ priority of the call to the better-than-best-effort (BBE) DSCP that is defined on the network region form. By default, this value is 43.

  • Page 320: Queuing Methods

    This mechanism works very well for IP Telephony traffic (where IP Telephony bearer and signaling are inserted in the high-priority queue), but might work less well for routine data traffic that is starved out if sufficient high-priority traffic arrives. 320 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 321: Round-Robin

    Queuing methods Round-robin Round-robin (sometimes called custom) queuing sorts data into queues, and services each queue in order. An administrator manually configures which type of traffic enters each queue, the queue depth, and the amount of bandwidth to allocate to each queue. Round-robin queuing is not particularly suited to IP Telephony.

  • Page 322: Traffic Shaping And Policing

    3. Set be, the excess burst rate, to 0 4. Set bc, the committed burst rate, to cir/100. This accounts for at most a 10-ms serialization delay. 5. Apply this map class to an interface, subinterface, or VC. 322 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 323: Fragmentation

    Fragmentation 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 frame-relay class NoBurst Fragmentation One large cause of delay and jitter across WAN links is serialization delay, or the time that it takes to put a packet on a wire.

  • Page 324: Lfi

    Avaya recommends use of LFI functionality instead of MTU manipulation when transmitting IP Telephony packets over PPP links. As with MTU, Avaya recommends sizing packets so that the serialization delay is approximately 10 ms or less.

  • Page 325: Application Perspective

    RTP header compression is a mechanism that routers use to reduce the 40 bytes of protocol overhead to approximately 2 to 4 bytes. Cisco routers use this mechanism, as does the Avaya X330WAN router, which is a module for the P330 chassis. RTP header compression can drastically reduce the IP Telephony bandwidth consumption on a WAN link when using 20-ms G.729 audio.

  • Page 326: The Test

    The Frederick Engineering Parascope WAN probe was tapped into the V.35 serial link to take bandwidth measurements. This test was performed using PPP encapsulation on the WAN link. A single call was placed between the Chariot endpoints using various codecs, all sending 20-ms voice packets. 326 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 327: Configuration

    Table 76: Test call (20ms-packets) results shows the results with and without RTP header compression. Note that these are rough measurements. Table 76: Test call (20ms-packets) results Codec Payload Packets Avg WAN BW bytes consumption (kbps) reduction per packet second without with compressi...

  • Page 328: Examples Of Qos Implementation

    X330WAN User Guides. For this documentation, see the P330 section http://www.avaya.com/support Examples of QoS implementation This section contains sample commands for QoS implementation on Avaya products and Cisco products. Examples given include: Example 1: Cisco router configuration for point-to-point WAN links...
  • Page 329 Examples of QoS implementation Figure 85: 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 still forwarded, however, so this should not interfere with a customer’s data network.

  • Page 330: 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 78: Administration commands for Example 2 page 331 are applied only to the left router. 330 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 331: Example 3: More Restrictions On The Traffic

    Examples of QoS implementation Administration commands for Example 2 Table 78: Administration commands for Example 2 Command Meaning The command “access-list 101...” permits 1.access-list 101 permit any IP traffic from the 2 C-LANs to the ip host 192.168.1.10 192.168.2.0/24 network. There is an 192.168.2.0 0.0.0.255 implicit “deny any”...
  • Page 332 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.” 332 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 333: Converged Infrastructure Lan Switches

    Examples of QoS implementation Converged infrastructure LAN switches P330 family By default, P330 LAN switches accept 802.1Q frames on all ports, and use the 802.1p priority tags. There are two queues within the P330s. The high-priority queue represents 802.1p values 4 to7.
  • Page 334 Serial 1. Activate “VoIP queue management mode” 10.voip-queue on the serial interface. 11.exit Apply the following commands to Interface 12.interface Serial 1 Serial 1. Enable cRTP (optional). 13.ip rtp header-compression 2 of 2 334 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 335: Implementing Communication Manager On A Data Network

    Implementing Communication Manager on a data network This section presents several examples of implementing Communication Manager on a data network. Topics covered include: S8700 Multi-Connect S8700 IP connect S8700 / S8300 LSP S8300 / G700 /G350 (ICC) Sample Multi-Connect deployment Issue 3.4.1 June 2005...

  • Page 336: S8700 Multi-Connect

    IPSIs and the S8700 pair is done on a private LAN utilizing one (or more) switches. This is one of the simpler network configurations, as control traffic is completely isolated from the production data network. 336 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 337: Ipsi Configuration

    Control Network on Customer LAN (CNOCL) Prior to Avaya Communication Manager 2.0, the S8700 Multi-Connect Control Network was required to be implemented on a private, dedicated network. A private, dedicated Control Network provides the much needed and desired system reliability and availability. The system is isolated and hence much more secure, and less prone to security attacks from the likes of virus attacks, Denial of Service (DoS) attacks, and broadcast storms.
  • Page 338 Protocol (IGP) that can achieve network convergence within 10 seconds. OSPF also supports multipath routing, where parallel paths are used concurrently. When properly configured, OSPF is an appropriate choice for a routing protocol across the control network. 338 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 339: Security Concerns

    Avaya recommends isolating the control network from the enterprise network as much as possible. Should an enterprise decide to combine the control and public networks, Avaya recommends implementing firewalls or access control lists in order to protect the system from attacks and unwanted traffic.

  • Page 340: S8700 Ip Connect

    The S8700 IP-Connect configuration requires IP connectivity between S8700 Media Server interfaces and Avaya media gateways. The port networks in an IP-Connect configuration use IPSI cards in the port networks to communicate to the S8700 Media Server. This connection will be referred to as the control connection throughout this document.

  • Page 341: Single Site With A Dedicated "Control" Network Connected

    Voice network cydfipt1 KLC 121003 This design connects all Avaya media servers and IPSIs to a dedicated control network. With CLANS and MedPros are connected to a separate voice VLAN. Additional separation from the infrastructure can be achieved by using a separate isolated media server for the dedicated control network providing resiliency from spanning tree calculations and DoS attacks that could potentially bring down a media server connected to the enterprise infrastructure.

  • Page 342: Multi-Site With A Dedicated "Control" Network Routed

    Web interface of the S8700 Media Servers. Once again, IP connectivity is required between media server clusters and the IPSIs of any port network requiring control. This is the most prevalent design in large corporate infrastructures supporting the Avaya S8700 Media Server IP-Connect configuration.

  • Page 343: Conclusion

    S8700 IP connect Conclusion The examples above show various ways to connect the Avaya S8700 Media Server IP-connect configuration to a customer network. Each method provides for resiliency against specific types of failures. TDM connectivity can be protected even in the event of an enterprise network failure, by protecting the control connection between Avaya media servers and IPSI cards.

  • Page 344: Ipsi Configuration

    PSTN. Because stability is a concern, G650s should not be connected on the same subnet as user PCs. One such configuration of G650 media gateways is shown in Figure 90: Server farm placement in network configuration. 344 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 345: Provisioning Network Regions

    Security Because the S8700 servers have modems for Avaya services access, it is advisable to use an external firewall or router access-lists to filter traffic to and from the S8700 servers.

  • Page 346: S8700 / S8300 Lsp

    Appendix B has information necessary for establishing access-lists or setting up a firewall policy. Avaya has worked on hardening Avaya Application Solutions products against penetration and denial of service attacks. For more information see Security.

  • Page 347: S8300 / G700 /G350 (Icc)

    H.248 signaling. Stacking The G700 can be stacked with other switches in the Avaya P330 family. It uses an 8-Gbps stacking cable connecting the switches. As with other members of the P330 family, it can be managed by the switch designated as the stack master, freeing customers from managing each switch separately.

  • Page 348: Sample Multi-Connect Deployment

    TrunkI TrunkI Avaya Avaya G700/S8300LSP G350/S8300LSP Optional cards Media Gateway Media Gateway installed in G700s to support analog trunks Phones Phones for failover Branch Office #1 Branch Office #2 cynds304 KLC 121003 348 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 349 Sample Multi-Connect deployment Figure 91: S8700 /G700 /G350 Multi-Connect system (gateways deployed at remote offices) on page 348 illustrates a typical S8700 Multi-Connect system with G700 or G350 gateways deployed at two remote offices. It demonstrates a number of the features previously discussed: The network as designed is highly resilient.
  • Page 350 Implementing Communication Manager on a data network 350 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 351: Network Recovery

    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 services, and malicious activity, including DoS attacks, worms, and viruses.

  • Page 352: Layer 2 Mechanisms To Increase Reliability

    Link Aggregation Groups (LAGs) are a mechanism for combining multiple real inter-switch links (typically four, Avaya products are configurable from two to eight) into one point-to-point virtual interswitch link. The advantage of this mechanism over spanning tree is that an organization can have the redundant links in if a failure occurs in one of the LAG links, the two switches will quickly discover it, and remove the failed link from the LAG., which reduces the convergence...

  • Page 353: Layer 3 Availability Mechanisms

    Layer 3 availability mechanisms 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 them to route around failure. There are two types of routing protocol, distance vector and link state.

  • Page 354: Multipath Routing

    If this is a physical link failure, the detection time is nearly instantaneous. Therefore, Avaya recommends the use of multipath routing, where available, across multiple links to a particular location.

  • Page 355: Convergence Times

    Convergence times 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 complexity and size of a network.
  • Page 356 Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 357: Network Assessment Offer

    Many customer IP infrastructures appear to be stable and perform at an acceptable levels but have performance and stability issues that create problems for Avaya IP Telephony. While the customer network appears to be ready for full-duplex IP Telephony, Avaya cannot assure performance and quality without a Network Assessment.

  • Page 358: Customer Infrastructure Readiness Survey (Cirs)

    Sometimes customers already know that their existing network is not configured to support Avaya IP Telephony, and they can order a NANO without first completing a CIRS. The assessment requires that the customer complete a CIRS-like analysis as the first phase).
  • Page 359 1. If the network fails to meet the minimum criteria required for network throughput, configuration, or additional resources are needed, Avaya recommends the more in-depth analysis of the Network Analysis Network Optimization (NANO). Site Configuration Survey The ECLIPS Site Configuration Survey (SCS) is an detailed customer-view of the their network.

  • Page 360: Network Analysis Network Optimization (Nano)

    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 customer must install and run the Vital Agent software on all desktops targeted for Avaya IP Telephony.
  • Page 361 To begin the NANO process, the customer must have completed the Customer Infrastructure Readiness Survey (CIRS). If a customer has already concluded that their network is not ready for the implementation of Avaya IP Telephony, they can skip the CIRS.
  • Page 362 Network assessment offer Table 84: Network Analysis Network Optimization components shows the NANO components and the information exchange between Avaya and the customer. Table 84: Network Analysis Network Optimization components Component Who does this? What does this do? What happens...
  • Page 363 Avaya network assessment solutions Customer responsibilities In order to successfully complete a NANO the customer must: Provide technical resource personnel who are well-versed in the network infrastructure. Provide complete access to the network. Provide passwords for networking equipment. Provide access to personnel for interviews.
  • Page 364 Traffic analysis reports, including archive on CD-ROM of all captured data for all segments monitored and injected with simulated busy hour IP Telephony calls Recommendations of Avaya Engineering team to resolve infrastructure problems discovered and/or make-ready for proposed Avaya IP Telephony...
  • Page 365 Avaya network assessment solutions Customer deliverables Avaya networking experts perform discovery of the customer’s network and document findings in a NANO Report delivered to the customer. Accurate network topology Measurements of actual usability performance levels, throughput performance of the LAN,...
  • Page 366 Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 367: Appendixes

    Appendixes Issue 3.4.1 June 2005...
  • Page 368 Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 369: Appendix A: Change Control

    Introduction Appendix A: Change control This appendix contains an overview of the change control process, why it is important, and the trade-offs that are associated with it. Major topics covered include: Critical steps for creating a change management process High-Level process flow High-Level process flow for emergency change management Performance indicators for change management Introduction...

  • Page 370: Planning

    - Acceptable hardware chassis and modules - Deployment guidelines Document your network standards for: - Configuration - Software version - Supported hardware - Domain Name System (DNS) - Device naming - Design - Supported services 370 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 371: Managing

    Critical steps for creating a change management process Managing Change management is the process that approves and schedules the change to ensure the correct level of notification and minimal user impact. The main activities involved in change management are to: Assign an individual to act as a change controller.

  • Page 372: High-Level Process Flow

    Scope Risk assessment Test and validation Change planning Change controller Change management team Communication Implementation team Test evaluation of change Network management update Documentation Figure 92: Process flow during a network change 372 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 373: Scope

    Moderate-risk. These network changes can have a critical impact on user environments or affect an entire site, but backing out of the change is a reasonably attainable scenario. You should research moderate-risk changes the Avaya Support Centre Web site, and possibly review the change with Avaya Services personnel. Avaya recommends notifying all users of a moderate-risk change.
  • Page 374 No user or service impact, including adding individual users to the network, and standard configuration changes such as password, banner, Simple Network Management Protocol (SNMP), or other standard configuration parameters. No expected network downtime. 374 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 375: Test And Validation

    High-Level process flow Test and validation After the risk level of the potential change has been assessed, the appropriate amount of testing and validation can be applied. Table 86: Testing and validation recommendations demonstrates how testing and validation may be applied to the five-level risk model. Table 86: Testing and validation recommendations Risk level Recommendations...

  • Page 376: Change Planning

    Change planning includes the generation of a change request, which should be sent to the change controller. Recommendations for change request information Avaya recommends including the following information on the change request form: Name of person requesting change Date submitted...

  • Page 377: Change Controller

    High-Level process flow Target system name and location User group contact (if available) Lab tested (yes or no) Description of how the change was tested Test plan Backout plan If successful, will the change migrate to other locations (yes or no) Prerequisites of other changes to make this change successful The technical description of the change is an important aspect of the change request, and may include the following: current topology and configuration, physical rack layouts, hardware and...

  • Page 378: Change Management Team

    The change management team does not investigate technical accuracy of the Note: change. Technical experts who better understand the scope and the technical details should complete this phase of the change process. 378 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 379: Communication

    Avaya recommends creating a matrix to help define who will be affected by a change, and what the potential time out of service might be for each application, user group, or server. Remember that different groups might require varying levels of detail about the change.

  • Page 380: Test Evaluation Of Change

    Standard SNMP configuration entered on devices, including community string, location, support contact, syslog server, trap server, and SNMP server host. Trap source, syslog source, and SNMP source configured for loopback. 380 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 381: Documentation

    Global configuration standards. Inventory database for all physical connectivity and contact information. In addition, Avaya recommends that you develop a matrix that contains information about user groups, the applications they require, and the servers (addresses and locations) that host these applications.

  • Page 382: High-Level Process Flow For Emergency Change Management

    For Avaya equipment, you should include the appropriate Avaya Services personnel in the troubleshooting process. In many cases, problems with Avaya equipment will be fixed by Avaya Services expert systems, or a technician will be dispatched before users are aware of the problem.

  • Page 383: Limited Risk Assessment

    Many of the ideas given in the section on Planned Change Management can be adapted to the emergency change environment, but on a more limited scale. For instance, you can use the Avaya Support Centre Web site (support.avaya.com/), or even use a limited test bed simulation, depending on your situation.

  • Page 384: Implementation

    384 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 385: Performance Indicators For Change Management

    Performance indicators for change management Performance indicators for change management Performance indicators provide the mechanism for you to measure the success of your change management process. We recommend that you review these indicators monthly to ensure that change planning and change management are working well. The topics are: Change management metrics by functional group Targeting change success...

  • Page 386: Change History Archive

    Change quantity and risk level Change failure quantity and post mortems Emergency changes and post mortems Change management goals Undocumented changes The functional manager should review the metrics, and report to the appropriate teams for improvement. 386 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 387: Appendix B: Access List

    This appendix provides guidelines for configuring access lists to facilitate basic Avaya IP Telephony functionality. The ports used by the Avaya call server are fairly fixed and well known. The ports used by the endpoints are more variable and random. As a result, it is simpler to tailor access lists based on call server ports.
  • Page 388 Permit Any IP TFTP TFTP Telephone server(s) (hardphone) Permit TFTP TFTP Any IP servers Telephone (hardphone) Permit SNMP UDP any Any IP UDP 161 management Telephone (snmp) stations (hardphone) 2 of 3 388 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 389 Reply device 3 of 3 Table 88: Access list guidelines for Avaya S8300, S8500, S8700 Media Servers on page 390 contains access list guidelines that pertain to Communication Manager platforms, including the S8700 and S8300 Media Servers. The S8700 enterprise interface, which is the one that is connected to the enterprise network (versus the control network), is eth4 on Multi-Connect systems and eth0 on IP-Connect systems.
  • Page 390 Access list Table 88: Access list guidelines for Avaya S8300, S8500, S8700 Media Servers Action From TCP/UDP TCP/UDP Notes port port or protocol or protocol Permit S8700 TCP any S8300 LSP TCP 514 Both S8700 and LSP enterprise running pre-CM2.x:...
  • Page 391 Table 88: Access list guidelines for Avaya S8300, S8500, S8700 Media Servers (continued) Action From TCP/UDP TCP/UDP Notes port port or protocol or protocol Permit S8300, TCP 80 Web admin TCP any S8500, or station(s) S8700 enterprise interface Permit Web admin...
  • Page 392 Access list Table 88: Access list guidelines for Avaya S8300, S8500, S8700 Media Servers (continued) Action From TCP/UDP TCP/UDP Notes port port or protocol or protocol Permit S8300 or TCP 2945 G700 or TCP any other G350 call server Permit...
  • Page 393 Table 89: Port requirements for file synchronization (continued) TCP 21874 (opens TCP 21874 TCP 21874 (opens automatically) automatically) Backward compatibility (CM1.3 primary; CM2.x LSP) TCP 514 TCP 512 - 1023 TCP 21873 (opens automatically) Backward compatibility (CM2.x primary; CM3.x LSP) TCP 21873 (opens TCP 21873 TCP 21874 (opens...
  • Page 394 Access list 394 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 395: Appendix C: Multi-Vlan Example

    Figure 93: Sample Multi-VLAN scenario for Cajun P330 code 3.2.8 and Cisco G600/G650 C-LAN MedPro vlan 10 vlan 10 192.168.10.2 192.168.10.1 vlan 1 192.168.10.7 f0/1 AVAYA IP Phone Cisco Router Cajun P330 192.168.1.254 1/12 192.168.10.254 vlan 1 vlan 1 192.168.1.100 192.168.1.7...
  • Page 396 In addition to v1, v10 statically bound to port, but not a trunk port. set port spantree disable 1/5 Port 1/12 for the DHCP/TFTP server already has port/native VLAN 1. 2 of 5 396 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 397 Table 90: Command set and explanations for multi-VLAN example (continued) Command Notes P330 configuration (bind-to-configured option) set vlan 1 (VLAN 1 configured) set vlan 10 (VLAN 10 configured) set port vlan-binding-mode 1/1 Port bound to configured VLANs 1 and bind-to-configured set trunk 1/1 dot1q Port connected to Cisco router is an 802.1Q trunk port.
  • Page 398 FastEthernet0/2 switchport access vlan 10 Port/native VLAN changed to 10 on this port. spanning-tree portfast interface FastEthernet0/3 switchport access vlan 10 spanning-tree portfast interface FastEthernet0/5 4 of 5 398 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 399: Ip Telephone Configuration

    IP Telephone configuration Table 90: Command set and explanations for multi-VLAN example (continued) Command Notes switchport trunk encapsulation dot1q802.1Q trunk port switchport trunk native vlan 1 Since most PCs do not understand the tag, the Cisco native VLAN must be set as the PC’s VLAN.

  • Page 400: Pc Configuration

    VLAN 10, and tagging could result in an incompatibility with the Ethernet switch. PC configuration The PC can be statically addressed with a VLAN 1 address, or it can receive a VLAN 1 address through DHCP. No special configurations are required. 400 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 401: Appendix D: Dhcp / Tftp

    Before you start, it is important that you understand your current network WARNING: configuration. An improper installation can cause network failures or reduce the reliability and performance of your network. See the Network assessment offer for more information about Avaya’s comprehensive network performance assessment. Issue 3.4.1 June 2005...

  • Page 402: Dhcp Software Alternatives

    Set up of a DHCP server involves the following top-level tasks: 1. Install the DHCP server software according to vendor instructions. 2. Configure the DHCP server with the available IP addresses for the Avaya IP Telephones. 3. Administer the lease duration (“Infinite” is recommended).
  • Page 403 DNS server is specified in Option 6, and the Domain Name is specified in Option 15, you can use the configured names “AvayaTFTPServer” and “Avaya Call Server” for TFTPSRVR and MCIPADD, respectively. The Call Server Name, TFTP Server Name, and SMTP Server Name must each be no more than 32 characters in length.

  • Page 404: Windows Nt 4.0 Dhcp Server

    3. Verify that Microsoft DHCP Server is listed as one of the Network Services on the Services Tab. 4. If it is listed, continue with the Initial configuration section below. If it is not listed, install the DHCP server. 404 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 405: Initial Configuration

    DHCP Initial configuration The Windows NT 4.0 DHCP server configuration involves setting up a scope for the IP Telephone. A DHCP scope is essentially a grouping of IP devices (in this case IP Telephones) running the DHCP client service in a subnet. The scope is used to define parameters for each subnet.

  • Page 406: Editing Custom Options

    You should exclude the ranges 135.254.76.81 to 135.254.76.89 and 135.254.76.201 to 135.254.76.224. Note: Avaya recommends that the IP Telephones be provisioned with sequential IP Note: addresses. 6. Under Lease Duration, select the Limited To option and set the lease duration to the maximum.

  • Page 407: Adding The Dhcp Option

    2. Select Scope under DHCP OPTIONS. 3. Select the 176 option that you created from Unused Option List. Avaya recommends that the IP Telephones be provisioned with sequential IP addresses. You will activate the scope when all options have been set.

  • Page 408: Windows 2000 Dhcp Server

    2. Under Services and Applications in the Computer Management tree, find DHCP. 3. If DHCP is not installed, install the DHCP server. Otherwise skip directly to Creating and configuring a DHCP Scope (Windows 2000) for instructions on server configuration. 408 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 409 DHCP Creating and configuring a DHCP Scope (Windows 2000) Use the following procedure to create and configure a DHCP scope (Windows 2000): 1. Select Start >Programs >Administrative Tools>DHCP. 2. In the console tree, click the DHCP server to which you want to add the DHCP scope for the IP Telephones.
  • Page 410 20. Under Lease duration for DHCP clients, select Unlimited and then click OK. WARNING: IP Address leases are kept active for varying periods of time. To avoid having WARNING: calls terminated suddenly, make the lease duration unlimited. 410 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 411 DHCP Adding DHCP options (Windows 2000) Use the following procedure to add DHCP options to the scope (Windows 2000): 1. On the DHCP window, right-click the Scope Options folder under the scope you created in the last procedure. A menu is displayed. 2.

  • Page 412: Tftp

    This allows the IP Telephone to display the progress of the transfer by displaying the total number of data blocks. 4. Download the upgrade script file and application file from the Avaya Web site (www.avaya.com/support) to the directory as specified by the file path.

  • Page 413: Avaya Tftp (Suite Pro) Configuration

    1. Select Start->Programs->Avaya TFTP Server >TFTPServer32 to run the TFTP Suite Pro server. The TFTP server starts. WARNING: You must restart Avaya TFTP manually every time you reboot your TFTP server. WARNING: 2. Select System->Setup. On the Outbound tab (page 1) the Outbound path should be the TFTP file path.
  • Page 414 DHCP / TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide...

  • Page 415: Index

    ....business continuity ..Avaya DEFINITY Servers R and SI ....remote survivability .
  • Page 416 ... . Communication Manager ..Avaya Call Management System ....components .
  • Page 417 Index ..Integrated Management applications management applications, (continued) ... . monitoring management applications Integrated Management ..monitoring management applications Integrated Management Database (IMD) .
  • Page 418 ..H.248 media gateway control ....IP connectivity 418 Avaya Application Solutions IP Telephony Deployment Guide...
  • Page 419 ....SMON Manager Avaya S8300 Media Server with G350 or ....
  • Page 420 ........X330 WAN module 420 Avaya Application Solutions IP Telephony Deployment Guide...

Table of Contents