Avaya 555-245-600 manuel d'utilisation
- Voir en ligne ou télécharger le manuel d’utilisation
- 378 pages
- 5.12 mb
Aller à la page of
Les manuels d’utilisation similaires
-
IP Phone
Avaya 555-250-701
56 pages 0.52 mb -
IP Phone
Avaya 4600
14 pages 0.35 mb -
IP Phone
Avaya 6
454 pages 4.73 mb -
IP Phone
Avaya IP Office H323
94 pages 0.26 mb -
IP Phone
Avaya NN43112-101
400 pages 2.14 mb -
IP Phone
Avaya 4622SW IP
88 pages 0.69 mb -
IP Phone
Avaya 1616-I
50 pages 0.68 mb -
IP Phone
Avaya 4601
86 pages 0.55 mb
Un bon manuel d’utilisation
Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Avaya 555-245-600. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Avaya 555-245-600 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.
Qu'est ce que le manuel d’utilisation?
Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Avaya 555-245-600 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.
Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.
Donc, ce qui devrait contenir le manuel parfait?
Tout d'abord, le manuel d’utilisation Avaya 555-245-600 devrait contenir:
- informations sur les caractéristiques techniques du dispositif Avaya 555-245-600
- nom du fabricant et année de fabrication Avaya 555-245-600
- instructions d'utilisation, de réglage et d’entretien de l'équipement Avaya 555-245-600
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes
Pourquoi nous ne lisons pas les manuels d’utilisation?
Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Avaya 555-245-600 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Avaya 555-245-600 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Avaya en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Avaya 555-245-600, comme c’est le cas pour la version papier.
Pourquoi lire le manuel d’utilisation?
Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Avaya 555-245-600, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.
Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Avaya 555-245-600. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.
Table des matières du manuel d’utilisation
-
Page 1
A vaya Application Solutions: IP Telephony Deployment Guide 555-245-600 Issue 6 January 2008[...]
-
Page 2
© 2008 A vaya Inc. All Right s Reserved. Notice While reasonable ef forts were made to ensure that the information in this document was complete and accurate at the time of printi ng, Avaya Inc. can assume no liability for any errors. Chan ges and corrections to the information in this document may be incorporated in futur e releases. For full leg[...]
-
Page 3
Issue 6 January 2008 3 About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Using this book . . . . . . . . . . . . . . . . . . . . . . .[...]
-
Page 4
4 Avaya Application Solutions IP Telephony Deployme nt Guide IG550 Integrated Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 TGM550 physical description . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Avaya S8400 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Mid-market to large enterprise . .[...]
-
Page 5
Issue 6 January 2008 5 Multi-location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Modem/Fax/TTY over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 IP-based trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3 IP tie trunks . . . . . . . . . . . . . . . . . . . . . .[...]
-
Page 6
6 Avaya Application Solutions IP Telephony Deployme nt Guide Section 2: Deploying IP T elephony . . . . . . . . . . . . . . . . . . 175 T raffic engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Design input s . . . . . . . . . . . .[...]
-
Page 7
Issue 6 January 2008 7 V oice quality network requirements . . . . . . . . . . . . . . . . . . . . 245 Network delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 45 Codec delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[...]
-
Page 8
8 Avaya Application Solutions IP Telephony Deployme nt Guide Connection preserving upgrades for duple x servers . . . . . . . . . . . . . . 271 Inter Gateway Alternate Routing (IGAR) . . . . . . . . . . . . . . . . . . . . . 271 Survivability for branch office media gateways . . . . . . . . . . . . . . . . . . . 272 H.248 Media Gateway recovery via[...]
-
Page 9
Issue 6 January 2008 9 Design for Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Layers . . . . . . . . . . . . . . . . . . . . . . . . . . .[...]
-
Page 10
10 Avaya Application Solutions IP Telephony Deployment Guide Network recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Change control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 9 Layer 2 mechanisms to increase reliability . . . . . . . . . . . . . . . . . . . . . 340 Spanning tree . . . . . . [...]
-
Page 11
Issue 6 January 2008 11 About This Book Overview This book, A vaya Application Solutions IP T eleph ony Deployment Guide , 555-245 -600, describes A vaya’s Applicatio n Solutions product line, IP T elephony product deployment, and network requirement s for integrating IP T e lephony products with an IP network. The guide can be used as a tool to [...]
-
Page 12
About This Book 12 Avaya Application Solutions IP Telephony Deployment Guide ● Call processing features ● LAN switching products Section II - Deploying IP T elephony . Use this sect ion to learn about deployment issues including: ● T raffic engineering ● Security ● V oice quality issues ● Network management ● Reliability and recovery [...]
-
Page 13
Related resources Issue 6 January 2008 13 Related resources For more information on A vaya IP T elephony product s, see the following do cumentation libraries and CDs: T echnical assist ance Avaya provides the following resources for technical assist ance. Within the US For help with: ● Feature administration and system applications , call T echn[...]
-
Page 14
About This Book 14 Avaya Application Solutions IP Telephony Deployment Guide T rademarks All trademarks identified by the ® or ™ are regi stered trademarks or tra demarks, respectively , of A vaya Inc. All other trademarks are the property of their respe ctive owners. Sending us comment s Avaya welcomes your comments about this book. T o reach u[...]
-
Page 15
Issue 6 January 2008 15 Section 1: A vaya Application Solutions product guide[...]
-
Page 16
16 Avaya Application Solutions IP Telephony Deployment Guide[...]
-
Page 17
Issue 6 January 2008 17 A vaya Application Solutions This chapter contains general di scussions of the A vaya Appl ication Solutions product line: ● Avaya Communication Manager ● A vaya servers ● Av aya DEFINITY Se rvers ● Avaya Media Gate ways ● A vaya Integra ted Management ● A vaya Co mmunication Manager applications ● A vaya SIP s[...]
-
Page 18
Avaya Application Solutions 18 Avaya Application Solutions IP Telephony Deployment Guide Figure 2: Communication Manag er traffic flow Figure notes: 1. SIP phones exchange RTP audio among themselve s and with the G700, G650 Media Gateways, and so forth, but not wit h IP phones. 2. SIP signaling from A vaya Communica tion Manager is always to/from S[...]
-
Page 19
Avaya Communication Manager Issue 6 January 2008 19 Avaya Media Gateways support voice traf fic and signaling traf fic that is routed between circuit-switched networks and p acket-switched networks. The Gateways support all t he applications and adjuncts that can be used with the A vaya DEFINITY Enterprise Communications Servers (DEFINITY ECS). The[...]
-
Page 20
Avaya Application Solutions 20 Avaya Application Solutions IP Telephony Deployment Guide ● Av aya DEFINITY Se rver R ● Av aya DEFINITY Server SI ● Av aya DEFINITY Server CSI These servers run on the Oryx/Pecos propriet ary operating system, and function in the same way as the servers in Figu re 2: Communication Manager traf fic flow on page 1[...]
-
Page 21
Avaya Communication Manager Issue 6 January 2008 21 The Integrated Management applica tions include the tools that enable yo u to ● configure, monitor , and optimize the performance of Avaya servers, gateways and ● endpoint s ● monitor voice over IP traf fic ● manage Quality of Service (QoS) policies ● control network quality For more inf[...]
-
Page 22
Avaya Application Solutions 22 Avaya Application Solutions IP Telephony Deployment Guide A vaya SIP solutions Session Initiation Protocol (SIP) is an end point-oriented messaging standard defined by the Internet Engineering T ask Force (IETF). SIP is a text-based protocol, simila r to HTTP and SMTP , for initiating interactive communication session[...]
-
Page 23
Avaya Distributed Office Issue 6 January 2008 23 ● Exposes composite commun ication service unit s expressed in the form of generic web service constructs understood by th e business community at large. ● Uses presence and availability co mputations to route commu nication to the right device of the us er . Communications Process Manager makes [...]
-
Page 24
Avaya Application Solutions 24 Avaya Application Solutions IP Telephony Deployment Guide Avaya Distributed Of fice contains integ rated features, applications, and much more. At e ach branch location, Distributed Office is imp lement ed in one of two plat forms — Avaya Distributed Office i40 or A vaya Distributed Office i120. These p latforms are[...]
-
Page 25
Avaya Distributed Office Issue 6 January 2008 25 Figure 3: Networked remote sites SES home PSTN SIP Apps servers Main business location SIP IVR private WA N SES edge Central Optional components SIP TDM SIP T Manager Communication Manager Branch l ocations PSTN Feature Ser ver SIP Enablement Services Local Manager CTI and T API applica tions Secure [...]
-
Page 26
Avaya Application Solutions 26 Avaya Application Solutions IP Telephony Deployment Guide Distributed Office benefit s The benefit s of Avaya Distributed Of fice include advanced functionality such as: ● Platform fea tures - Feature server including both PBX and Key-Syste m features - SIP Enablement Ser vices -V o i c e M a i l - Announcement s - [...]
-
Page 27
Avaya Distributed Office Issue 6 January 2008 27 An i40 might provide an adequate number of lines and trunks for the current business requirements bu t not for increased requirements in t wo years based on growth assumptions. Or , an i40 might provide eno ugh lines and trunks for the next several years but ano ther parameter , such as the number of[...]
-
Page 28
Avaya Application Solutions 28 Avaya Application Solutions IP Telephony Deployment Guide i120 construct s Each i120 construct cont ains the following port s: ● One analog trunk port ● T wo analog line port s ● One Contact Closure Adjunct (CCA) por t ● One Ethernet W AN port (not used with Distributed Of fice) ● One Ethernet LAN PoE port ?[...]
-
Page 29
Avaya Distributed Office Issue 6 January 2008 29 Distributed Office application module and media modules A vaya AM1 10 Application Module The Ava ya AM1 10 Application Module is the h eart of the Replace variable w/ short product name system. The AM1 10 Application Module prov ides the telephony feature s, voice mail, automated attendant, SES, and [...]
-
Page 30
Avaya Application Solutions 30 Avaya Application Solutions IP Telephony Deployment Guide T elephony media modules The ten constructs for Distributed Office i1 20 contain one or more media mod ules. Ta b l e 3 shows the available media modules, and the slot or slots in which each module can be inserted. S treamlined Deployment A major goal of the Di[...]
-
Page 31
Avaya Distributed Office Issue 6 January 2008 31 ● Custom — The profile is not a S tandard profile and needs to be cre ated. ● None (Default)— The default profile associat ed with the hard ware construct will be shipped and the provisioning dat a will be entered when the system is installed. The deployment of a Distributed Of fice system is[...]
-
Page 32
Avaya Application Solutions 32 Avaya Application Solutions IP Telephony Deployment Guide Partially configured systems For a partially con figured system, a S tandard profile is selected o r a Custom profile is created that conta ins some of the provisioning data. The profile contains a section for dynamic data , which is either missing and needs to[...]
-
Page 33
Issue 6 January 2008 33 A vaya Application Solutions plat forms Overview The A vaya Communication Manager portfolio covers small, medium, and large enterprises with advanced communications needs between 2 and 48,00 0 ports per system. Th is chapter provides an overvie w of the Avaya Communi cation Manager platforms architectu re that supports A vay[...]
-
Page 34
Avaya Application Solutions platforms 34 Avaya Application Solutions IP Telephony Deployment Guide T able 4: A vaya Application Solutions comp arison matrix — component s, performance, and cap acities 1 A vaya S8300 Server Avaya S8400 Server A vaya S8500 Server Avaya S8700-series Server Processor/ RAM/ disk drive Intel Celeron class server 512 MB[...]
-
Page 35
Overview Issue 6 January 2008 35 Maximum IP Endpoint s (IP T elephones + IP T runks) S8300: 900 T otal S8300/G700: 900 T otal 450 T runks 450 T elephones S8300/G450: 900 T otal 450 T runks 450 T elephones S8300/G350: 55 T otal 15 T runks 40 T elephones S8300/G250: 20 T otal 10 T runks 10 T elephones 1,300 T otal 400 T runks 900 T elephones (450 can[...]
-
Page 36
Avaya Application Solutions platforms 36 Avaya Application Solutions IP Telephony Deployment Guide T erminology The terms IP-PNC and fiber -PNC are used in this chapter to distinguish between the two types of port network connectivi ty (PNC). Synonyms are IP-connected and Fiber -connected , respectively . Fiber-connected port networks (fibe r-PNC) [...]
-
Page 37
Small to mid-siz e enterprise Issue 6 January 2008 37 Small to mid-size enterprise A vaya S8300 Server and A vaya G700, G450, G350, or G250 Media Gateway The S8300 Server and G700 Media Gatewa y solution ( Figure 5: Avaya G700 Media Gateway with the S8300 Server on p age 37) seamlessly delivers voic e, fax, and messaging cap abilities over an IP ne[...]
-
Page 38
Avaya Application Solutions platforms 38 Avaya Application Solutions IP Telephony Deployment Guide Multiple G700 Media Gateways can be connected to each other through an Octap lane 8-Gbps stacking fabric, and A vaya P330 Ex pansion Modules, which allows adding additional Ethernet ports, fiber inte rfaces, A TM access or W AN access modules without [...]
-
Page 39
Small to mid-siz e enterprise Issue 6 January 2008 39 These processing element s are controlled by Communication Manager , thus of fering the complete set of Communica tion Manager call featur es to both IP users and tra ditional telephony users. From a hardware perspective, the G700 Media Gatewa y is an enclosure with a n internal power supply and[...]
-
Page 40
Avaya Application Solutions platforms 40 Avaya Application Solutions IP Telephony Deployment Guide The G700 motherboard hard ware design involves three major b locks: ● A DSP engine and associated pa cket processor complex. This complex performs IP/UDP/ RTP processing, echo cancella tion, G .71 1 A/µ, G .729 (with or without silence suppression)[...]
-
Page 41
Small to mid-siz e enterprise Issue 6 January 2008 41 ● Recorded announcement playback (15 pl ayback cha nnels, 1 record channel) ● T one detection and generation (15 port s of tone detection) ● System clock generation and synchronization to an external network timing reference ● Download agent for the media modu les ● Licens e/trans lati[...]
-
Page 42
Avaya Application Solutions platforms 42 Avaya Application Solutions IP Telephony Deployment Guide ● V oice quality is impacte d when played over IP . However , quality is acceptable even with 2 hops and 10-msec delay . ● The use of G700 V AL sourced an nouncements imp a cts that g ateway’s overall occup ancy , and IP T elephony resources (fo[...]
-
Page 43
Small to mid-siz e enterprise Issue 6 January 2008 43 S8300 as an LSP The S8300 Server installe d in a G700, G450, G350, or G250 Media Gateway can be configu red as a Local Survivable Processor (LSP). The L SP provides survivabili ty when the primary controller , either an S8300 ICC or an S8700-ser ies External Communications Controller (ECC), is i[...]
-
Page 44
Avaya Application Solutions platforms 44 Avaya Application Solutions IP Telephony Deployment Guide The G450 can support up to 450 users when deployed as a branch gateway in a mid to large branch of fice of a large enterprise or a call ce nter , and can serve up to 24 00 users when deployed as a campus gateway . Both configur ations require A vaya C[...]
-
Page 45
Small to mid-siz e enterprise Issue 6 January 2008 45 - Supported CODECs: G . 71 1A/µLaw , G .729a, G .726 - DHCP and TFTP server to support IP phones images and configuration - Announcements and Music on Hold (MoH) su pport ● Survivability features for continuous voice services: - Local Survivable Processor (LSP , wi th S8300) — failove r to [...]
-
Page 46
Avaya Application Solutions platforms 46 Avaya Application Solutions IP Telephony Deployment Guide ● Management features: - Avaya G450 Device Manager - Embedded Web Manager - RADIUS Authentication support - SNMPv1 traps and SNMPv3 notifications - T elnet and SSHv2 support - SCP , TFTP and FTP support -S y s l o g - Modem access for remote adminis[...]
-
Page 47
Small to mid-siz e enterprise Issue 6 January 2008 47 G450 physical descript ion Figure 8: The A vaya G450 Media Gateway Chassis The Ava ya G450 Media Gateway is a versatile device with powerful capabilities. T o implement the various services that are supported, a va riety o f swappable internal co mponents called media modules are available. Supp[...]
-
Page 48
Avaya Application Solutions platforms 48 Avaya Application Solutions IP Telephony Deployment Guide ! CAUTION: CAUTION: The MM340 and MM342 are not supp orted by the Ava ya G700 Media Gateway . Do not insert an MM340 or MM342 medi a module into an A vaya G700 Media Gateway . V oice over IP (V oIP) The G450 provides V oIP services over the LAN and W [...]
-
Page 49
Small to mid-siz e enterprise Issue 6 January 2008 49 Emergency T ransfer Relay (ETR) The Emergency T ransfer Relay (ETR) feature provi des basic telephone service s in the event of a power outage or a failed connection to A vaya Communication Manager . The ETR support s the connection of two external 808A ETR p anels. Each 808A Emergency T ransfer[...]
-
Page 50
Avaya Application Solutions platforms 50 Avaya Application Solutions IP Telephony Deployment Guide Rapid Sp anning T r ee Protocol (RSTP) The IEEE 802.1D (STP) and IEEE 802.1w (RST P) S panning T ree Protocols are supported on the ETH LAN port s. Port mirroring The G450 supports network traf fic monitoring by po rt mirroring. Y ou can configure por[...]
-
Page 51
Small to mid-siz e enterprise Issue 6 January 2008 51 Media modules necessary for each W AN line The table b elow lists wh ich media modules to in stall to connect each type of out side WAN line. Management access security features The G450 features the followin g management security mechanisms: ● A basic authentication mechan ism in which users [...]
-
Page 52
Avaya Application Solutions platforms 52 Avaya Application Solutions IP Telephony Deployment Guide - SYN cookies, which protect against a well-known TCP/IP att ack in which a malicious attacker t argets a vulnerable device and ef fectively prevents it from est ablishing new TCP connections. Alarms and troubl eshooting features The G450 has extensiv[...]
-
Page 53
Small to mid-siz e enterprise Issue 6 January 2008 53 The G350 is designed for use in a 16- to 24-user environment, but can support sites with up to 40 statio ns. The G250 media gateway is designed for smaller branch offices with two to eight users. T elephone services on a G250/G350 are controlle d by a Media Gateway Controller (MGC). Y ou can use[...]
-
Page 54
Avaya Application Solutions platforms 54 Avaya Application Solutions IP Telephony Deployment Guide ● Fax and modem over IP ● Frame-Relay ● GRE tunneling ● Inter-Gateway Alternate Routing (IGAR) ● MGC automatic switchover , migration, and survivability features ● Modem access for remote administration ● Modem backup connection to the M[...]
-
Page 55
Small to mid-siz e enterprise Issue 6 January 2008 55 ● Distributed Av aya Enterprise Connect. In this mode, the G250/G35 0 is controlled by an external MGC. This may be a st andalone server , such as the S8500, S8700-series, or a separate media gatewa y in a standalon e configuration. In systems with Enhanced Local Survivability (ELS), the G250/[...]
-
Page 56
Avaya Application Solutions platforms 56 Avaya Application Solutions IP Telephony Deployment Guide G350 Specifications The G350 chassis feature s six media module slots (V1 to V6) a nd various fixed ports and buttons. V1 to V5 are G700 form factor media module slots cap able of housing existing G700 media modules. V6 is a high-density media module [...]
-
Page 57
Small to mid-siz e enterprise Issue 6 January 2008 57 T able 8: Buttons on the G350 front p anel Button Description RST Reset button. Resets chassis co nfiguration. ASB Alternate Softwa re Bank button. Reboots the G350 with the software image in th e non-default bank. T able 9: Supported media modules for G350 Media module Description MM312 (HDMM) [...]
-
Page 58
Avaya Application Solutions platforms 58 Avaya Application Solutions IP Telephony Deployment Guide The MM710, MM71 1, MM712, and MM720 are existing G700 med ia modules. T able 10: Additional G350 functions and cap acities Function Cap acity V oIP DSP engine 32 G .71 1 or 16 G .729 channels T ouch T one Recognition (TTR) 15 channels Announcement 6 p[...]
-
Page 59
Small to mid-siz e enterprise Issue 6 January 2008 59 G250 Configurations Figure 10 shows the G250 Med ia Gateway chassis. Figure 1 1 shows the G250-BRI Media Gateway chassis. Figure 10: The A vaya G250 analog Media Gateway Chassis, Figure 1 1: The A vaya G250 BRI Media Gateway Chassis, Figure notes: 1. V1 — ICC/LSP Slot 2. V2 — W AN Media Modu[...]
-
Page 60
Avaya Application Solutions platforms 60 Avaya Application Solutions IP Telephony Deployment Guide T able 1 1: Fixed ports and buttons on the G250 front p anel describes the functions of the fixed ports and buttons on t he G250 front panel. T able 1 1: Fixed port s and buttons on the G250 front p anel Port Description TRUNK Four analog trunk ports [...]
-
Page 61
Small to mid-siz e enterprise Issue 6 January 2008 61 G250 DCP and G250 DS1 Media Gateways Release 3.1 of Communication Manager introdu ces two new versions of the G250 Media Gateway . The G250 DS1, supporting the T1/E1/PRI market, includes: ● One T1/E1/PRI trunk with fr actio nal trunks allowed. ● One analog trunk with loop st art only (no sup[...]
-
Page 62
Avaya Application Solutions platforms 62 Avaya Application Solutions IP Telephony Deployment Guide turning the SOHO branch into a seamless p art of the enterprise’ s network. For information on the G150 Media Gateway , see Hardware Description a nd Reference for A vaya Communication Manager , 555-245-207. IG550 Integrated Gateway The IG550 Integr[...]
-
Page 63
Small to mid-siz e enterprise Issue 6 January 2008 63 Figure 12: Sample config uration of the IG550 in a Communic ation Manager network Figure notes: Sample configuration of the IG550 in a Co mmunication Manager network 1. Media Gateway 8. Public Switched T elephone Network (PSTN) 2. Legacy telephones 9. WA N 3. S8700-series Server 10. J-series rou[...]
-
Page 64
Avaya Application Solutions platforms 64 Avaya Application Solutions IP Telephony Deployment Guide The IG550 is designed for use in a 20 -to-100 user environment, with optimal performance at branch of fices with 20 to 80 telephones. The IG550 features S tandard Local Survivability (SLS). SLS provides p artial backup media gateway controller (MGC) f[...]
-
Page 65
Small to mid-siz e enterprise Issue 6 January 2008 65 - Simple Network Management Protocol (SNM P) trap s and informs (v1 and v2 only) sent to the primary controller - SNMP v3 for remote management access, trap s and informs - Secure Shell (SSH) Authentication support - Secrets encryption of configur ation data ● Provisioning - Avaya Communicatio[...]
-
Page 66
Avaya Application Solutions platforms 66 Avaya Application Solutions IP Telephony Deployment Guide ● Border Gateway Protocol (BGP) - PPP over Ethernet (PPPoE) - Policy-based routing - Dynamic Host Configuration Protocol ( DHCP) client, server , and relay functions - Generic Routing Encapsulation (GRE) tunneling - Dynamic IP addressing - Class of [...]
-
Page 67
Small to mid-siz e enterprise Issue 6 January 2008 67 IG550 and J4350 Services Ro uter physical descript ion Figure 13: Example of th e IG550 Integrated Gateway in a J4350 Services Router Slot locations on J4350 Services Router - The slots on the J4350 Service s Router are identified as follows: Figure 14: Slot numbers on the Juniper J4350 Services[...]
-
Page 68
Avaya Application Solutions platforms 68 Avaya Application Solutions IP Telephony Deployment Guide IG550 and J6350 Services Ro uter physical descript ion Figure 15: The IG5 50 Integrated Gateway in a J 6350 Services Router Slot locations on J635 0 Services Router The slots on the J6 350 Services Router are identified as follows: Figure 16: Slot num[...]
-
Page 69
Small to mid-siz e enterprise Issue 6 January 2008 69 The J-series router chassis has six slo ts. The TGM550 can be housed in any of the six router slots. The TIMs can also be housed in any slot. Gigabit Ethernet and Fast Ethernet PIMs can be housed only in slot s 2, 3, 5, or 6. Other optional PIMs can be housed in any slots. TGM550 physical descri[...]
-
Page 70
Avaya Application Solutions platforms 70 Avaya Application Solutions IP Telephony Deployment Guide TIM521 4 ISDN BRI trunk ports providing up to 8 bearer ch annels J-series Router Physical Interface Modules Dual-Port Serial PIM 2 Fast Ethernet ports and two serial ports Dual-Port T1 or E1 PIM 2 Fast Ethernet ports and two E1/T1 ports, each providin[...]
-
Page 71
Small to mid-siz e enterprise Issue 6 January 2008 71 T able 13 shows capacities of the supported interface modules. ! CAUTION: CAUTION: Some capacities may cha nge. For the most up-to-date list, see System Capacities T able for Avaya Communication Manager on Av aya Servers , 03-30051 1. Summary of services The IG550 of fers various services, a few[...]
-
Page 72
Avaya Application Solutions platforms 72 Avaya Application Solutions IP Telephony Deployment Guide V oice over IP (V oIP) The IG550 features a V oIP engine that provides voice services over I P data networks. The IG550 allows you to use many types of telephones and trunks that do not directly support V oIP . The media gateway translates voice and s[...]
-
Page 73
Small to mid-siz e enterprise Issue 6 January 2008 73 ● Y ou can configure the dialer interface to connect to the media gatew ay’s primary MGC via a modem connected to the J-series router in the event that the connection between the media gateway and the MGC is lost. ● Y ou can configure the A vaya Communication Manager to support the a uto f[...]
-
Page 74
Avaya Application Solutions platforms 74 Avaya Application Solutions IP Telephony Deployment Guide IG550 maximum media gateway cap acities T able 14: IG550 media gateway cap acities Description Cap acity Comments Busy Hour Call rate (BHCC) 800 Maximum number of TGM550s controlled by an S8500 or S8700-series Server 250 This number also applies if a [...]
-
Page 75
Small to mid-siz e enterprise Issue 6 January 2008 75 ! CAUTION: CAUTION: Some capacities may cha nge. For the most up-to-date list, see System Capacities T able for Avaya Communication Manager on Av aya Servers , 03-30051 1. For more information on the IG550 Integrate d Gateway , see Overview for the A vaya IG550 Integrated Gateway , 03-60158. A v[...]
-
Page 76
Avaya Application Solutions platforms 76 Avaya Application Solutions IP Telephony Deployment Guide Figure 18: TN8400AP circuit p ack (S8400 Server) The S8400 Server can replace the follo wing platforms: ● DEFINITY CSI ● DEFINITY One/S8100 ● IP600/S8100 For new installa tions, the PNs use the G650 M edia Gateways. For migrations of current ins[...]
-
Page 77
Small to mid-siz e enterprise Issue 6 January 2008 77 The TN799DP Control-LAN (C-LAN) circuit pack pr ovides f irmware download functionality while the TN2501 V oice Announcement over LAN (V AL) circuit pack provides annou ncement functionality . The S8400 Server provides a V oice over Internet Protocol (V oIP) based integrated messaging capability[...]
-
Page 78
Avaya Application Solutions platforms 78 Avaya Application Solutions IP Telephony Deployment Guide - emergency transfer ● An optional TN2302AP IP Media Processor if you run the optional embedded messaging (IA770) or run IP telephones. When running IP te lephones, the TN2302AP interfaces between the T ime Division Multiplex (TDM) bus and the IP ne[...]
-
Page 79
Mid-market to large enterprise Issue 6 January 2008 79 Mid-market to large enterprise S8500 Server The Ava ya S8500 Server Platform is a simplex L inux-based server running Av aya Communication Manager sof tware that replaces the DEFINITY SI and R processing plat forms for small sites and for customers who do not requ ire a duplicated server comple[...]
-
Page 80
Avaya Application Solutions platforms 80 Avaya Application Solutions IP Telephony Deployment Guide Because the inter port network TDM traffic flow is supported by a Center S tage Switch (CSS) or an Asynchronous T ransfer Mode (A TM) switch us ing fiber-optic cables, this configuration is called fiber -PNC . The call control traffic between the serv[...]
-
Page 81
Mid-market to large enterprise Issue 6 January 2008 81 S8700-series ext ernal features ● Six 10/100 Ethernet NICs per server , which are used as follows: - Dual control network connectio ns - A memory duplication link to the du plicated server - Administrative access from the corporate network - T echnician access - One unused ● A PCMCIA Flash [...]
-
Page 82
Avaya Application Solutions platforms 82 Avaya Application Solutions IP Telephony Deployment Guide USB modem - Each S8700-series Server sup ports a Universal Se rial Bus (USB) modem. For customers with an A vaya service contract, the modem is used to sen d alarms to the A vaya Services organization, and to facilit ate maintenance by A vaya Services[...]
-
Page 83
Mid-market to large enterprise Issue 6 January 2008 83 Figure 21: A vaya S8700/MCC1 fiber-PNC major comp onent s Control network through an A vaya Ethernet switch When designing S8700-series fibe r-PNC systems, a control network connects the servers to the IPSIs through a 10/100 BaseT Ethernet. It consist s of two sep arate Ethernet networks using [...]
-
Page 84
Avaya Application Solutions platforms 84 Avaya Application Solutions IP Telephony Deployment Guide Circuit p acks that support IP signaling an d media traffic Figure 23: S8700-series / MCC1 sign aling p ath Figure 24: S8700-series fiber-PNC — a basic phone call cynds117 KLC 121003 IP IP PN1 PN2 H.323 endpoint or H.248 Gatew ay C L A N I P S I B C[...]
-
Page 85
Mid-market to large enterprise Issue 6 January 2008 85 IP Server Interface (TN2312BP) - The IP Server In terface (I PSI) is the communication interface between the server and the Media Gatewa ys (port networks). The IPSI is re sponsible for gateway control, and for tunneling call control messages back to the S8700. One IPSI circuit pack is requ ire[...]
-
Page 86
Avaya Application Solutions platforms 86 Avaya Application Solutions IP Telephony Deployment Guide The C-LAN circuit p ack is used for all IP call si gnaling for both IP trunks and st ations. This circuit pack also provides T CP/IP connectivity to su ch adjuncts a nd synchronous applications as Call Management System (CMS) and INTUITY AUDIX. This c[...]
-
Page 87
Mid-market to large enterprise Issue 6 January 2008 87 Figure 25: TN2302AP Media Processor operation T o do the job, a media processing circuit p ack has a set of DSP resources. These resources are deployed dynamically and flexibly to any o f a number of tasks, in cluding: ● Originating and terminating IP-bas ed p acket-switched audio streams ●[...]
-
Page 88
Avaya Application Solutions platforms 88 Avaya Application Solutions IP Telephony Deployment Guide Since H.323 allows any of se veral different c odecs to be used for encoding an audio stream on the IP network, the Media Processor board is able to use any of th e following codecs: ● G. 7 1 1 ● G .723.1 ● G .726 (on the TN2602AP circuit pack o[...]
-
Page 89
Mid-market to large enterprise Issue 6 January 2008 89 Figure 26: MCC1 Media Gateway Single-Carrier Cabinet (SCC1 ) Media Gateway - The SCC1 Media Gateway consist s of a single carrier . Up to four SCC1 Media Gateways can be connected together in one locatio n to form one port network. There are tw o typ es of SCC1 Media Gateways: ● An Expansion [...]
-
Page 90
Avaya Application Solutions platforms 90 Avaya Application Solutions IP Telephony Deployment Guide Figure 27: SCC1 Media Gateway Non-IPSI connected Media Gateway - T ypically , one of every five Port Networks (PNs) contains one or two IPSI circu it packs. The remaining PNs are referred to as non-IPSI connected . Non-IPSI connected PNs get th eir co[...]
-
Page 91
Mid-market to large enterprise Issue 6 January 2008 91 Remote G700, G450, G350, G250, or G150 Media Gateway - The S8700-series Server can provide the call processing features for a re mote G700, G450, G350, or G250 media gateway over an H.248 link, and G150 gateway using H. 323. In this configuration, the S8700 can support up to 250 G700, G450, 350[...]
-
Page 92
Avaya Application Solutions platforms 92 Avaya Application Solutions IP Telephony Deployment Guide S8700-series fiber-PNC configur ation for higher availability When used with the MCC1 and SCC1 Media Gateways, t he S8700-series Server has the following reliability options: ● S tandard reliability configuration ● High reliability configuration ?[...]
-
Page 93
Mid-market to large enterprise Issue 6 January 2008 93 Figure 28: S8700-series fiber-PNC in a st andard reliability configuration Figure notes: 1. The Adm inistration PC accesses the S8700-series Server over the corporate data network. 2. Corporate IP network. 3. Corporate IP network interface. The Ethernet 4 link from the S8700 to th e dat a netwo[...]
-
Page 94
Avaya Application Solutions platforms 94 Avaya Application Solutions IP Telephony Deployment Guide High reliability configuration The high reliability configuration option build s on the standa rd reliability option. The high reliability option duplicates component s, so that no single point of failure exists in th e control network. The high relia[...]
-
Page 95
Mid-market to large enterprise Issue 6 January 2008 95 Figure 29: S8700-series fiber-PNC in a high reliability configuration Figure notes: 1. The Adm inistration PC is used to access the S8700-series Server over the corporate data network. 2. Corporate IP network. 3. Corporate IP network interface. The Ethernet 4 link from the S8700-series Server t[...]
-
Page 96
Avaya Application Solutions platforms 96 Avaya Application Solutions IP Telephony Deployment Guide Critical reliability configuration The critical reliability configuratio n option is built upon the high reliability configura tion. In the critical reliability configuration, the bearer network has duplica ted components so tha t there is no single p[...]
-
Page 97
Mid-market to large enterprise Issue 6 January 2008 97 Figure 30: A vaya S8700-series Server with remote G650 / G700 / G350 Media Gateways cynds125 LAO 101104 S8700 system with remote G650/G700 sites and IP TIE T runk links to other Av ay a PBXs ALM TST ACT ALM TST ACT 1 2 3 4 5 6 8 7 ALM TST ACT ALM TST ACT 1 2 3 4 5 6 8 7 REMOVE ALM TST ACT OKTO [...]
-
Page 98
Avaya Application Solutions platforms 98 Avaya Application Solutions IP Telephony Deployment Guide Figure 31: S8700-series Server I P-PNC — a basic phone ca ll on page 98 shows a call through an S8700 IP-PNC system. Figure 31: S8700-series Server IP-PNC — a basic phone cal l Main component s The S8700-series Server IP-PNC consis t s of the foll[...]
-
Page 99
Mid-market to large enterprise Issue 6 January 2008 99 ● At least one TN2302AP IP Media Processor or TN2602AP IP Me dia Resource 320 to support inter-PN and intra-PN connectivity ● The G650 Media Gateway ● Avaya Communication Manager Figure 32: S8700-series Server I P-PNC m ajor component s on page 99 shows the main S8700 IP-PNC components mo[...]
-
Page 100
Avaya Application Solutions platforms 100 Avaya Application Solutions IP Te lephony Deployment Guid e The left da ta rack cont ains a stack of five G650 Media Gateways that are labeled A through E. The right dat a rack contains the following (fro m top to bottom): ● T wo USB-compliant modems ● T wo S8700-series Servers ● One Avaya Ethernet sw[...]
-
Page 101
Mid-market to large enterprise Issue 6 January 2008 101 S8700 IP-PNC configuration Figure 33: S8700 IP-PNC st andard configuration Figure notes: 1. T wo S8700-series Servers. One server is in a active mode, and the other server is on st andby . 2. Duplication Interface. The Ethernet connection betwee n the two S8700-series Ser vers. 3. A dedicated [...]
-
Page 102
Avaya Application Solutions platforms 102 Avaya Application Solutions IP Te lephony Deployment Guid e Combined IP and fiber Port Network Connectivity Communication Manager Release 3.0 enables th e S8700-series and S8500 Servers to support configurations that combine IP-connected port networks (I P-PNC) with fiber-connected port networks (fiber-PNC)[...]
-
Page 103
Mid-market to large enterprise Issue 6 January 2008 103 The G650, SCC1, and MCC1 Media Gateways can connect to a combined IP-PNC and fiber-PNC system using either IP or fiber connections. The CMC1 Med ia Gateway can be IP-connected only and cannot be fibe r-connected in any of the combin ed IP-PNC and fiber-PNC configurations. The following t able [...]
-
Page 104
Avaya Application Solutions platforms 104 Avaya Application Solutions IP Te lephony Deployment Guid e Cap acity limit for media gateways A combined IP-PNC and fiber-PNC system can support up to 250 Media Gateways including the G150, G250, G350, G450, and G700. Configuration rules Combined IP-PNC and fiber-PNC require s CM3.0 or later softwa re but [...]
-
Page 105
Mid-market to large enterprise Issue 6 January 2008 105 MCC1 Media Gateway with one or more IP- an d fiber-connected PNs In a combined IP-PNC and fiber-PNC configuration, an MCC1 Media Gateway may contain ● up to 5 fiber-connected PNs. ● up to 5 IP-connected PNs. ● both IP-connected and fiber-conn ected PN s (this only applies for migration a[...]
-
Page 106
Avaya Application Solutions platforms 106 Avaya Application Solutions IP Te lephony Deployment Guid e Mixed reliability options The reliability options separate ly available for each PNC method still apply except th at fiber-connected PNs (fiber-PNC) with single control networks cannot be mixed with IP-connected PNs (IP-PNC) with duplicated contro [...]
-
Page 107
Processor Et hernet Issue 6 January 2008 107 Networking option of S8700-series Serv er p air for duplicated and single control networks For an S8700-series Server p a ir with direct/CSS/A TM PNC and duplicated control networks, control network A and control network B interf aces are administered as dedicated control networks and connecte d to dupli[...]
-
Page 108
Avaya Application Solutions platforms 108 Avaya Application Solutions IP Te lephony Deployment Guid e The following tab le describes the usage of Processor Ethernet as of release 3.1 : A vaya IP Office Avaya IP Office is anoth er standalone A vaya plat form that support s IP T elephony for the small to mid-size market. Avaya IP Of fice is an IP PBX[...]
-
Page 109
Issue 6 January 2008 109 Greenfield deployment This chapter explains how to implement A v aya Application Solutions components in a Greenfield site. A Greenfield site is a busines s or an organization that does not have an existing communication system. Most Greenfield syst ems are dep loyed into new businesses and organizations, and these systems [...]
-
Page 110
Greenfield deployment 110 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 34: A Greenfield I P T elephony deployment Servers (H.323 Gatekeeper) The servers are responsible for running A v aya Communication Mana ger and controlling the Media Gateways and end points. The servers control the dial plan translatio ns and call routing,[...]
-
Page 111
Components needed for Gr eenfield deployment Issue 6 January 2008 111 A vaya Communication Manager Communication Manager IP cap abilities and applicat ions support voice over an IP network, and ensure that remote workers have access to co mmunication system featur es from their PCs. Communication Manager also provides st andar ds-based control betw[...]
-
Page 112
Greenfield deployment 112 Avaya Application Solutions IP Te lephony Deployment Guid e Greenfield configurations S8300 st andalone solution (small-to-midsize enterprise) An S8300 Server with a G700, G250, or G350 gateway is designed for a small to mid-size office. The S8300 fits in to a media module slot in the G700, G350, or G25 0 Media Gateway . S[...]
-
Page 113
Greenfield configurations Issue 6 January 2008 113 Medium-to-large enterprise solutions Note: Note: The description of the duplicate d S8700-series Server configuration in this section, except for capacities, also ap plies to an S8500 simplex configuration. S8700-series / G650 IP-PNC The S8700-series IP-PNC system ( Figure 36: S8700 -series IP-PNC [...]
-
Page 114
Greenfield deployment 114 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 36: S8700-series IP-PNC system S8700-series IP-PNC with remote G700s or G350s The IP-PNC solution can be exp anded to suppor t a remote office with G700 or G350 Media Gateways in addition to G650 Gateways ( Figure 37: S8700 -series IP-PNC w ith remote G700 [...]
-
Page 115
Greenfield configurations Issue 6 January 2008 115 Figure 37: S8700-series IP-PNC with remote G700 or G350s Note: Note: A typical remote of fice is configured with a single gateway . Several gateways are shown in the remote of fice in Figure 37 to illustrate additional possible configurations. S8700-series with G150 /G250: large number of remote br[...]
-
Page 116
Greenfield deployment 116 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 38: S8700-series with G150 /G250 -- large number of remote branches Required circuit p acks for S8700-series configuration The circuit packs tha t are required for IP T elephony in a Communication Man ager system include: ● TN2312BP IP Server Interface (I[...]
-
Page 117
Greenfield configurations Issue 6 January 2008 117 As shown in Figure 39: Signaling path (S870 0 / G650 configuration) on page 1 17, an IP T elephone sends all IP T elephony signaling traf fic to the C-LAN. The C-LAN multiplexes IP T elephone signaling messages, and sends them to th e S8700-series Server through the IPSI. The connectivity between t[...]
-
Page 118
Greenfield deployment 118 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 40: Media flow p ath (S8700 IP-PNC configuration) Figure 41: Signaling flow[...]
-
Page 119
Issue 6 January 2008 119 Evolution from circuit-switched to IP Overview The Ava ya DEFINITY® Enterprise Communications Server G3r has been the flagship product in the DEFINITY family of commun ications se rvers. As technology changed, A vaya was able to leverage the rapid advances in microprocessor technology to increase the ca pacity and processi[...]
-
Page 120
Evolution from circ uit-switched to IP 120 Avaya Application Solutions IP Te lephony Deployment Guid e With the S8700 fiber-PNC solution, A vaya is delivering a high-capacity server and a migration path from DEFINITY . The S8700-series Server uses an industry-st andard Linux operating system on an industry-standard server , which enables all endpoi[...]
-
Page 121
Migration from DEFINITY Server R to S8700 f iber-PNC Issue 6 January 2008 121 The full migration from a G3r to an S8700-series Server fiber-PNC system, with tra ditional or A TM center stage, invo lves the following simplified steps: 1. Decide which EPNs are to be IPSI connected, and replace processor complexes with IPSIs. 2. Install servers. 3. In[...]
-
Page 122
Evolution from circ uit-switched to IP 122 Avaya Application Solutions IP Te lephony Deployment Guid e Phase 2: IP-enable the Port Networks to support IP end point s Port Networks, with the addition of IP enablin g circuit p acks, are abl e to serve as Media Gateways, representing the integration of IP and T DM telephony . IP-enabling the existing [...]
-
Page 123
Migration from DEFINITY Server R to S8700 f iber-PNC Issue 6 January 2008 123 At this stage, th e media flow between two IP endpoint s can be “shuffled.” That is, the media flow proceeds directly between both end points without requiring Media Pro cessor resources. Shuffling may be used across multiple sites or multiple Avaya switches . Likewis[...]
-
Page 124
Evolution from circ uit-switched to IP 124 Avaya Application Solutions IP Te lephony Deployment Guid e Consolidating remote site servers into an S8700 system requires a G700 or G350 Media Gateway with the option of Local Survivable Processors (LSP) ( Figure 46: S8700 / G700 / G350 system with Local S urvivable Processors ). The LSP can be an S8300 [...]
-
Page 125
Issue 6 January 2008 125 Call processing This chapter explains the features, th e str engths, and the architecture of Communicat ion Manager call processing.This chapter emph asizes the call processing component s of Communication Manager and it s architecture, and br iefly discusses IP-re la ted applications in the areas of telephony , convergence[...]
-
Page 126
Call processi ng 126 Avaya Application Solutions IP Te lephony Deployment Guid e IP Port Network / Media Gateway connectivity IP PNC allows S8700-series Servers and G650 Media Gateways to be connected over IP networks. A vaya Communication Manager uses a propriet ary method to p ackage signaling messages over IP . This method allows deplo ym ent of[...]
-
Page 127
Call Processing Issue 6 January 2008 127 Call Processing Communication Manager gatekeepers A gatekeeper is an H.323 entity o n the network that provides address tran slation and controls access to the network for H.323 end point s. For Communication Manager plat forms, these are the Ava ya S8300, S8400, S8500, and S8700-series Servers. H.323 RAS (R[...]
-
Page 128
Call processi ng 128 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 47: Discovery and reg istration process to the gatekeeper Call signaling Communication Manager implement s the gatek eeper routed call model of H.32 3. The registration process that is de scribed above allows the end point and the Communication Manager gatekeepe[...]
-
Page 129
Call Processing Issue 6 January 2008 129 Media stream handling Media processor circuit p acks (V oIP resources) The basic functions of the TN2302AP IP Medi a Processo r and TN2602AP IP Media Resource 320 circuit packs, an d V oIP on the G700/G350 Media Gateways, include: ● T aking media streams off the IP network, te rminat ing RTP/ UDP (adjustin[...]
-
Page 130
Call processi ng 130 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 48: Media Processor board s upport of a three-p arty audio conference on page 130 provides an example to show how the Med ia Processor board is configured for a three-p arty H.323 audio conference using G .729. This conference is conventional in that it u ses TD[...]
-
Page 131
Call Processing Issue 6 January 2008 131 Multi-location Communication Manager release 2.2 or later a llows a Linux-based server located in one country to control gateways located across national borders and provide appropriate country-specific tones and features. S pecifically , these features include the following: ● A-law & Mu-law Comp andi[...]
-
Page 132
Call processi ng 132 Avaya Application Solutions IP Te lephony Deployment Guid e Avaya 's TTY oIP support works by identifying TTY Baudot tones at the near-end Media Processor , removing them from the voice p ath, and transporting them across the network in RFC 2833 messages. The far-end Media Processor receives the RFC 2833 messages and regen[...]
-
Page 133
IP-based trunks Issue 6 January 2008 133 IP-based trunks In circuit switched networks, trunks provide the means to in terconnect PBXs with each other and to the PSTN. Connection to the public network allows PBX sta tion users to call and be called by terminals that are no t p art of the PBX private networ k. An analogous arrangement exists in p ack[...]
-
Page 134
Call processi ng 134 Avaya Application Solutions IP Te lephony Deployment Guid e IP tie trunks IP tie trunks are used to connect switches to one another . When an IP trunk is used to interconnect two switches, the trunk can also carry st andard (QSIG) and proprietary (DCS+) signaling for interswitch feature t ransparency . The location of each othe[...]
-
Page 135
SIP Issue 6 January 2008 135 RFC 3261, and so interoperates with any SIP-ena bled endpoint/st ation that also complies with the standa rd. T able 17 shows the maximum number of SIP trunks supported out of th e total number of IP trunks supported. Avaya Communication Manager support s SIP endpoint s, including the A vaya 4602 SIP T elephone and Avay[...]
-
Page 136
Call processi ng 136 Avaya Application Solutions IP Te lephony Deployment Guid e name. As of SES 4.0, there is no integration between AES and SES, and the Converged Communications Server port folio is a marketing name. Overview SES is sold as a communicati ons appliance similar to Av aya Communication Manager , and is deployed on the X305 (3.0, 3.1[...]
-
Page 137
SIP Issue 6 January 2008 137 The high level architecture is a shared d ata approach, where most component s do not interact directly with each other , but rather all shar e and use data in the dat abase. The master admin system populates that dat a from a single web interface, and run-time co mponents read and modify that data. In some cases, there[...]
-
Page 138
Call processi ng 138 Avaya Application Solutions IP Te lephony Deployment Guid e feature using Feature Name URIs, and retrieving st ate through event packages. Advanced SIP users must be provisioned both on SES as a SIP user and as an OP TIM station on Communication Manager . There must be a SIP trunk configured on Communication Man ager , and a co[...]
-
Page 139
SIP Issue 6 January 2008 139 SIP deployment s cenarios SIP and DNS In all SIP configurations it is highly reco mmended to use both Dynamic Name System (DNS) and Dynamic Host Configuration Protocol (DHCP ). The customer must have DNS running in the enterprise for external lookup s. Proper DNS configuration allows for prope r server resolution, inclu[...]
-
Page 140
Call processi ng 140 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 49: T ypical home/edge configuration Multi-home multi-Commun ication Manager system The multi-home system is a distribu ted version of the home/edge system where the edge is a separate host from th e home servers, which ar e de ployed for the user base . The hom[...]
-
Page 141
SIP Issue 6 January 2008 141 Figure 50: Multi-home multi-Communicatio n Manager configuration Figure 51: Message flow for multi-home multi-Communication Manager configuration on page 142 shows t he message flow , where the arrows in numerical order represent the path of the initial INVITE message starting from the caller . Messages starting from th[...]
-
Page 142
Call processi ng 142 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 51: Message flow for multi-home multi -Communication Manager configuration Multi-home single Comm unication Manager system One possible configuration is to only have a si ngle Communication Manager system in the SIP deployment. The reason for do ing this is to s[...]
-
Page 143
SIP Issue 6 January 2008 143 Figure 52: Multi-home single Co mmunication Manager configuration Figure 53: Multi-home single Co mmunication Manager configuration - message flow[...]
-
Page 144
Call processi ng 144 Avaya Application Solutions IP Te lephony Deployment Guid e Multi-home multi-Communication Ma nager with QSIG (TIE trunk) connection An alternative to the sin gle Communication Manager configuration is to have o ne logical Communication Manager system, but have tw o Communication Manage r servers connected with QSIG or standard[...]
-
Page 145
SIP Issue 6 January 2008 145 Figure 55: Multi-home multi-Communication Manager configuratio n with QSIG connection - message flow A vaya-T oshiba Solution Avaya and T oshiba have collaborated to provide a combined A vaya AST solution (Communication Manager and SES) with T oshiba SIP terminals for the Japan ese general office market. Development and[...]
-
Page 146
Call processi ng 146 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 56: A vaya-T oshiba Solution[...]
-
Page 147
Avaya G860 Media Gateway Issue 6 January 2008 147 A vaya G860 Media Gateway The Ava ya G860 media gateway is a DS3-capabl e , high channel density st andards-compliant, V oIP media gateway system. It provides a robust, scalable, and modular solution designed f or a large campus or call center with high availability and reliability . T o support hig[...]
-
Page 148
Call processi ng 148 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 57: G860 Front view Figure 58: G860 Back view Figure notes: 1. T runk Processing Module (TPM) board s 2. Blank and baf fled panels 3. ESD connectors on the attachment br ackets 4. Fan T ray Module (FTM) with alarm LEDs 5. ES 6600 Ethernet switch boards 6. System[...]
-
Page 149
Avaya G860 Media Gateway Issue 6 January 2008 149 G860 Component s The G860 media gateway hardware consists of the chassis, T P6310 (media gateway board), Ethernet Switch, System Controller , and the corresponding Rear T ransition Modules (RTM). T able 19 lists the G860 Media Gateway comp onents and red undancy configuration. System Controller Boar[...]
-
Page 150
Call processi ng 150 Avaya Application Solutions IP Te lephony Deployment Guid e contains an on-board hard disk, which stores the SC sof tware and the configuration and performance dat abase. The SC board incorporates a 6 50 Mhz UltraS parc processor with 512 MB memory and uses the robust Solaris operating system environment enhanced for advanced h[...]
-
Page 151
Avaya G860 Media Gateway Issue 6 January 2008 151 Example configuration for call center The A vaya G860 Media Gateway allows call cent er customers to consolidate facilities and reduce communications cost s. The media gatewa y concentrates incoming PSTN tra ffic over several DS3 lines while supporting V oIP telephony in the call center it self. The[...]
-
Page 152
Call processi ng 152 Avaya Application Solutions IP Te lephony Deployment Guid e Mobility IP T elephones or IP Softphones IP T elephones allow access to the features of Communication Manage r without having to be tied to one location. One of the major benefit s of IP T elephones is that you can move the telephones around on an IP network just by un[...]
-
Page 153
Communication applications Issue 6 January 2008 153 ● A vaya Ca ll Management System (CMS) ● Conferencing systems ● Meet-me conferencing ● Avaya Meeting Exchange Solutions ● Video T elephony Solutions ● C omputer T elephony Integration (CTI) ● Application Programming Interfaces (APIs) ● Best Services Routing (BSR) polling For more i[...]
-
Page 154
Call processi ng 154 Avaya Application Solutions IP Te lephony Deployment Guid e ● Avaya Call Management System Su pervisor ● Avaya Basic Call Management System ● Avaya Business Advocate ● Call Center - Avaya Call Center Basic - Avaya Call Center Deluxe - Avaya Call Center Elite ● Call Recording ● CALLMASTER® series digital t elephones[...]
-
Page 155
Communication applications Issue 6 January 2008 155 Unified Communication Center Unified Communication Center let s mobile, remo te and of fice workers easily access important communications tools and information via any telephone using simple an d intuitive speech commands. A vaya Call Management System (CMS) The A vaya Call Management System coll[...]
-
Page 156
Call processi ng 156 Avaya Application Solutions IP Te lephony Deployment Guid e special hardware. Meet-me conferencing uses a sof tware approach that is based on V ector Directory Number (VDN) vectors and ann ouncements. An announcemen t source is necessary to use meet-me conferencing. S upported an nouncement sources include: ● V oice Announcem[...]
-
Page 157
Communication applications Issue 6 January 2008 157 V alue-added Features - These capabilities, includ ing reporting, recording and billing , enable enterprises to precisely manage use of their conferencing service by generating cu stomized conference report s and enabling internal bill back systems. Integrated W eb Conferencing - Provides comprehe[...]
-
Page 158
Call processi ng 158 Avaya Application Solutions IP Te lephony Deployment Guid e Meeting Exchange W eb Conferencing T arget Market: Mid-market, Service Providers Integrated Solution Features: ● PowerPoint push and document annot ation, white boarding, chat, polling ● Desktop or application sharing ● Workho rse application for 4-8 person, ever[...]
-
Page 159
Communication applications Issue 6 January 2008 159 Hardware and Software re quirements include: ● Meeting Exchange audio conferencing bridg e ● Off-the-she lf server , plus Web Conferen cing software (license based capacity) ● Additional servers required for recordin g and playback (optional) Meeting Exchange Express Edition Meeting Exchange[...]
-
Page 160
Call processi ng 160 Avaya Application Solutions IP Te lephony Deployment Guid e other H.323 end points. With the A vaya Video T elephony Solution, you can provide video for desktop and group commun ications. The Ava ya Video T elephony Solution support s the following features and product s: ● Ad-hoc video conferencing ● Avaya IP Softphone Re [...]
-
Page 161
Communication applications Issue 6 January 2008 161 Best Services Routing (BSR) polling Best Service Routing (BSR) polling over QSIG Call Inde pendent Signaling Connections (CISCs) and T emporary Signaling Connections (T SCs) provides the ability to do BSR polling between multiple sites over H.323 IP trunks without requ iring an ISDN PRI B-channel.[...]
-
Page 162
Call processi ng 162 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 163
Issue 6 January 2008 163 LAN switching product s This chapter discusses how Av aya LAN switc hes and other LAN switching products add valu e to an IP T elephony deployment. A vaya C360 converged st ackable switches The Ava ya C360 converged st ackable switch series is a line of stackab le, multilayer switches that provide high availability , qualit[...]
-
Page 164
LAN switching products 164 Avaya Application Solutions IP Te lephony Deployment Guid e ● C363T -PWR converged stackable switch This switch has 24 10/100 Mbp s ports with Power over Ethernet (PoE) a nd two GBIC SFP ports. Figure 61: C363T -PWR Converged St ackable switch ● C364T converged st ackable switch This switch has 48 10/100 Mbp s ports a[...]
-
Page 165
Avaya C360 converged st ackable switches Issue 6 January 2008 165 S t acking ● Up to 10 switches can be st acked together . ● Features such as S panning T ree, redundancy , VLANs, and SMON are common to the stack. ● The Octaplan e stacking system provide s 8 Gbps sta cking bandwidth to all switches in t he stack. ● C360 stacks continue to f[...]
-
Page 166
LAN switching products 166 Avaya Application Solutions IP Te lephony Deployment Guid e ● RMON/SMON port statistics provide real-tim e top-down a nalysis of network traffic. ● IP multicast filtering (snooping) filters multica st traffic to optimize network bandwidth. ● Classification of port s as regular or valuable is supported so that if a l[...]
-
Page 167
Avaya C360 converged st ackable switches Issue 6 January 2008 167 ● Simple network time protocol (SNTP) or TIME protoco ls are available to provide a consistent timestamp to a ll switches from an external source. ● Radius authentication enables centralized user management. ● Y ou can use all appropriate tools of the A vaya Integrated Manageme[...]
-
Page 168
LAN switching products 168 Avaya Application Solutions IP Te lephony Deployment Guid e - BlackDiamond 8806 - a 6-slot non-blocking switch for access or core - BlackDiamond 8810 - a 10-slot non-bl ocking switch for access or core For information on Extreme Networks switches, see http://www .extremenetworks.com A vaya Power over Ethernet (PoE) switch[...]
-
Page 169
Midspan Power Units Issue 6 January 2008 169 Power priority mechanism The priority mechanism is implemented in order to handle cases where the power requeste d by the PDs exceeds the switch PoE cap acity . This priority mechanism determines the order in which ports will b e powered on after boot, and powere d off if the powe r resources of the modu[...]
-
Page 170
LAN switching products 170 Avaya Application Solutions IP Te lephony Deployment Guid e The 1 152A1 can be collocated with the dat a equipment or closer to the end points. In all cases, IEEE 802.3af capable IP devices must connect di rectly to this PDU. The PDU cannot power any device if a hub or a switch is b etween itself and the end point because[...]
-
Page 171
Midspan Power Units Issue 6 January 2008 171 1 1 52B Power Distribution Unit s The A vaya 1 152B Mid-S pan Po wer Distribution Un its a re Ethernet power supplies that provide power to up to 48 46xx-series o r 96xx IP telepho nes or wireless LAN (WLAN) access points. The 1 152B PDUs are designed to deliver power in addition to dat a communication o[...]
-
Page 172
LAN switching products 172 Avaya Application Solutions IP Te lephony Deployment Guid e Designed usage The 1 152B PDUs are used to power the 46xx series an d 96xx series of IP telephones in addition to providing 10/100 meg abits per se cond Ethernet connection. Generation 1 A vaya IP telephones can receive p ower from the 1 152B using an in-line ada[...]
-
Page 173
VPN Client Issue 6 January 2008 173 VPNremote Client is a comp atible with Micr osoft Win dows software, and provides secure, authenticated access to enterprise network r eso urces and applications over the Internet. T his application leverages the benefit s of global access and cost-effective pub lic network features to support a remote or a mobil[...]
-
Page 174
LAN switching products 174 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 175
Issue 6 January 2008 175 Section 2: Deploying IP T elephony[...]
-
Page 176
176 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 177
Issue 6 January 2008 177 T raffic engineering This chapter provides an introduction to traf fic eng ineering. S pecifically , this chapter discusses various traf fic models, algorithms, and resource sizing. This section includes the following top ics: ● Introduction ● Design inputs - T opology - Endpoint specifications - Endpoint traf fic usage[...]
-
Page 178
Traffic engineer ing 178 Avaya Application Solutions IP Te lephony Deployment Guid e This discussion of the configura tion, engineerin g, and deployment pro cesses is intended as an overview that is suitable for a fairly genera l aud ience. One example that is designed to exercise all aspects of these p rocesses continues throughout the chapter to [...]
-
Page 179
Design inputs Issue 6 January 2008 179 A Communication Manager system can operate as an independent entity , or can be networked together with other Communication Manager systems. For networked systems, the various Communication Manager systems in the network ar e generally interconnected by IP tie trunks. If the two members of a given p a ir of Co[...]
-
Page 180
Traffic engineer ing 180 Avaya Application Solutions IP Te lephony Deployment Guid e End point specifications Normally , a customer who submits a Re quest fo r Proposal (RFP) specifies the number of each type of statio n to place in each site, in each Commun ication Manager system in the n etwork. Certain customers might want to specify statio n pl[...]
-
Page 181
Design inputs Issue 6 January 2008 181 The most commonly used default value for a genera l business system is 0.1 1 Erlangs per station. The most common way to de termine trunk usage rates is to divide the to tal traf fic 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[...]
-
Page 182
Traffic engineer ing 182 Avaya Application Solutions IP Te lephony Deployment Guid e Additional design criteria ● Each site is to have a suit able number of PSTN trunks (which terminate on PNs in Atlant a and Boston, and on the G35 0 Media Gateways in Cleveland). ● This is a general business application (for ex a mple, no Call Center agents), w[...]
-
Page 183
Call usage rates Issue 6 January 2008 183 Call usage rates In the previous section, st at ion usages and overall end point usages, including both stations a nd trunks, were discussed. The overall end point usa ge is sometimes referred to as port usag e rate (PUR). The term station usage rate (SUR) applies when referring only to the st ations. In ge[...]
-
Page 184
Traffic engineer ing 184 Avaya Application Solutions IP Te lephony Deployment Guid e One of the first steps in the p rocess is to distinguish between inte rcom call usage, inbound PSTN call usage, and outboun d PSTN call usage. Inbound and outbound tie trunk usa ge must also be considered when working with mu ltiple Communication Manage r systems t[...]
-
Page 185
Call usage rates Issue 6 January 2008 185 Alternatively , 100 Erlangs of total st ation usa ge could also hypothetically corre spond to 35 Erlangs of intercom call usage, 10 Erlang s of inbound PSTN usage, and 20 Erlangs of outboun d PSTN usage. Using the procedure from t he preceding example to verify th is: ● Intercom st ation usage = 70 Erlang[...]
-
Page 186
Traffic engineer ing 186 Avaya Application Solutions IP Te lephony Deployment Guid e Example 2: Uniform Distribution model In the case of a stan d-alone Avaya system, the Uniform Distribution model works on the assumption that when a given st ation places an intercom call, the call is equally likely to terminate at any of the other st ations in the[...]
-
Page 187
Call usage rates Issue 6 January 2008 187 Communication Manager uses a first-site -preference algorithm for outbound trunk calls. This algorithm specifies that all outbo und calls first at tempt 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. F[...]
-
Page 188
Traffic engineer ing 188 Avaya Application Solutions IP Te lephony Deployment Guid e Again, T able 26 and Ta b l e 2 7 are constructed withou t considering overflow traf fic.These tables imply that the Site 1 PSTN trunks carry 98 Erla ngs (4 9 inbound and 49 outbound) of traf fic, the Site 2 trunks carry 36 Erlangs, and the Site 3 trunks carry 16 E[...]
-
Page 189
Call usage rates Issue 6 January 2008 189 It is assumed that half of each individual st ation’ s usage is associated with calls that the station generates, and the other half is associated with calls that the st ation receives. Therefore, half of the 97 Erlangs of st ation usage (that is, 49 Erlangs) in the Atlanta site co rresponds to intercom c[...]
-
Page 190
Traffic engineer ing 190 Avaya Application Solutions IP Te lephony Deployment Guid e The general formulas used to populate th e COI matrix entries in T able 26 , T able 27 , and T able 28 , respectively , for the Uniform Distribution model are: Additional comment s regarding Example 2: Uniform Distribution model In the Uniform Distribution mod el i[...]
-
Page 191
Call usage rates Issue 6 January 2008 191 T able 27 , and Ta b l e 2 8 , respectively , for the Uniform Distribution model based on relative SUR are: Example 3: Empirical appr oach for existing systems Another possible means of populating the COI matr ices exist s for established systems. In su ch cases, the necessary information can be read from t[...]
-
Page 192
Traffic engineer ing 192 Avaya Application Solutions IP Te lephony Deployment Guid e Consider the COI matrix for a three-site, st and-alone Communication Manager system, as presented in T able 25 . A suitable exp ansion of that matrix might take the form of the matrix in T able 29: Expanded COI matrix for a th ree-site system on page 19 2 in which [...]
-
Page 193
Call usage rates Issue 6 January 2008 193 First consider the 32 Erl angs of intercom CUR between Site 1 stations ( T able 28 ). Site 1 (Atlanta) has a tot al of 1755 stations, 1 107 of which are IP stations, and 6 48 of which are circuit-switched st ations. So, 63% of the st ations in Site 1 are IP , and 37% are circuit switched. Therefore, 63% of [...]
-
Page 194
Traffic engineer ing 194 Avaya Application Solutions IP Te lephony Deployment Guid e In addition, 37% of intercom calls that a re generat ed in Site 1 are generated by circuit-switched stations, and 69% of those calls are terminated by IP stations. Since 69% of 37% is 25.5%, 25.5% of Site 1 to Site 2 inter com calls are circuit-switched st ation to[...]
-
Page 195
Call usage rates Issue 6 January 2008 195 The general formula that is used t o determine the exp anded intercom CUR entries in T able 31 is: where: ● “T ype t ” refers to IP or circuit-switched ● ● Now that the intercom CURs have been dete rmined, CURs that invo lve trunks will be addressed. First, because Communication Manager systems ar[...]
-
Page 196
Traffic engineer ing 196 Avaya Application Solutions IP Te lephony Deployment Guid e The general formula that is used t o determine the exp anded inbound and outbound CUR entries in T able 32 is: where: ● “T ype t ” refers to IP or circuit-switched ● ● T able 32: Completed COI matrix for Example 4: Exp anded COI matrices T o end point s i[...]
-
Page 197
Call usage rates Issue 6 January 2008 197 In general, one may choose to expand a COI matrix in any of several diffe rent possible ways, depending upon the needs of the problem. In the preceding example, sep arating the endpoint s into IP , circuit-switched, and PSTN makes sense for the upcoming resource -sizing calculations, as will be seen later i[...]
-
Page 198
Traffic engineer ing 198 Avaya Application Solutions IP Te lephony Deployment Guid e A seven-site COI matrix analogous to the three-site matrix in T able 25: 3-site st andalone community of interest (COI) matrix on p age 184 can be constructed for the network shown in Figure 64 . A corresponding seven-site, expanded COI matrix, similar to the o ne [...]
-
Page 199
Resource sizing Issue 6 January 2008 199 Signaling resources The TN799DP C-LAN and the TN2312BP (IPSI) circuit packs are the primary signaling traf fic bearing component s residing within a port network. Both have finit e internal resources such as sockets and dat a-link connection identifiers (DLCIs) for assignment to and use b y endpoint s. In ad[...]
-
Page 200
Traffic engineer ing 200 Avaya Application Solutions IP Te lephony Deployment Guid e the message traf fic through C-LANs and IPSIs. Optimal configurations allocate enough of both to maintain traf fic levels at or below known st able thresholds. A v aya configuration software to ols perform the requisite analysis and r esulting resource sizing, as n[...]
-
Page 201
Resource sizing Issue 6 January 2008 201 Although we st ated that calls between two circuit- switched endpo ints on dif ferent port networks use an IP connection, the use of a circuit-swit ched center stage betwe en the two PNs is also supported. However , using circuit-switched faciliti es is not viable for interconn ecting multiple Media Gateways[...]
-
Page 202
Traffic engineer ing 202 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 66: Connectivity m odes between two IP end points At this point, we can quantify the TDM and media processing re quirements for various call types. Throughout this discussion, ca lls between tw o IP stations are assu med to use shuf fling. That being the cas[...]
-
Page 203
Resource sizing Issue 6 January 2008 203 connectivity is being used (as opposed to a ce nter stage), each interport network call requires two TDM resources and two media p rocessing res ources. One of each of these resources is supplied by each of the PNs that is involved in the call. In t he preceding discussion, everything that applies to a PN al[...]
-
Page 204
Traffic engineer ing 204 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 68: Inter-s ite TDM and Media Processing resource requirement s In Figure 68 , the usages are presente d on an end point-by-end point basis. For example, according to Figure 68 , an in tersite call between an IP endpoint in Site 1 and a circuit-switched endp[...]
-
Page 205
Resource sizing Issue 6 January 2008 205 Example 5: TDM and me dia processi ng usage Consider the COI matrix in T able 32: Completed COI matrix for Example 4: Expanded COI matrices on page 196 in Example 4: Exp anded COI matrices . A set of nine cells corresponds to calls originated in Site 1 and termin ated in Site 1 (that is, the upper lef t grou[...]
-
Page 206
Traffic engineer ing 206 Avaya Application Solutions IP Te lephony Deployment Guid e T able 33 provides a summary of call usage rates, which can be mapped to a t able of TDM usage rates and media processing usage rates by using the information in Figure 67 and Figure 68 . We assume that there is only one PN in Site 1, one in Site 2, and two G350 Me[...]
-
Page 207
Resource sizing Issue 6 January 2008 207 T able 34: TDM and Media Processing usag es (Erlangs) for Example 5: TDM an d media processing usage End point s Site 1 (Atlant a) Site 2 (Boston) Site 3 (Cleveland) Intrasite: I, I TDM: 0 Media: 0 TDM: 0 Media: 0 TDM: 0 Media: 0 Intrasite: I, C or P TDM: 76.8 Media: 76.8 TDM: 26.7 Media: 26.7 TDM: 14.4 Medi[...]
-
Page 208
Traffic engineer ing 208 Avaya Application Solutions IP Te lephony Deployment Guid e The TDM usage rates of 130.0 Erlangs for Site 1 and 46.7 Erlangs for Sit e 2 can both be easily handled by the TDM facilities o f a single PN, whic h is capab le of carrying up to 200 Erlangs o f TDM traffic at a P001 GOS. Therefore, th e assump tion that all calls[...]
-
Page 209
Resource sizing Issue 6 January 2008 209 processing loads in Sites 2 a nd 3 are 43. 9 Erlangs and 17.6 Erlangs , respectively . Those numbers are also based on the assumptio n that media encryption was not used. T able 35: Number of TN2302AP IP Media Pro cessors or G700 Media Gateway V oIP Modules required for a given carried load Carried load (Erl[...]
-
Page 210
Traffic engineer ing 210 Avaya Application Solutions IP Te lephony Deployment Guid e T able 35 implies that three TN2302AP IP Media Proc essor circuit p acks should be used in Site 1 (Atlanta), and two should be used in Site 2 (Boston). Ta b l e 3 6 implies that the media processing resources on the two G350 Media Gateways in Site 3 (Cleveland) are[...]
-
Page 211
Resource sizing Issue 6 January 2008 211 S tarting with release 3.1 of Communicatio n Manager , the TN2602AP IP Media Resource 320 can be duplicated to provide critical bearer re liability for IP-connected port networks. If more than one PN had been required in a particular site, intrasite calls b etween circuit-switched end points in that site wou[...]
-
Page 212
Traffic engineer ing 212 Avaya Application Solutions IP Te lephony Deployment Guid e occupancy is allocated on an as-n eeded basis, such as for periodic maintenance functions. However , if the overall server occup ancy exceeds a particular threshold, SM operations are postponed until a quie ter traffic perio d. Usually , the relationship betwe en t[...]
-
Page 213
Resource sizing Issue 6 January 2008 213 Therefore, for the given configuration, the sp ecific linear model for the relationship between the sum of static and CP occupancy , as a function of BHCC, has been derived. Using the anticipated BHCC rate in that model yields the expected combined st atic and CP occupancy . If that value exceeds the preset [...]
-
Page 214
Traffic engineer ing 214 Avaya Application Solutions IP Te lephony Deployment Guid e usual. Direct media shuff ling between SIP st atio ns and IP trunks is not supported. Therefore, SIP calling between Communication Manager syst ems connected by IP TIE trunks always require allocation of V oIP media resources. C-LAN allocation and SIP trunks The Co[...]
-
Page 215
Resource sizing Issue 6 January 2008 215 3. Allocate enough trun k members to each C-LAN to achieve desired grade of service, based on the known or assumed call traf fic. 4. Check SIP message throughput based o n the call traffic. 5. If SIP message traf fic exceeds desirable threshold for any C-LAN, either add more C-LANs or re-distribute users, if[...]
-
Page 216
Traffic engineer ing 216 Avaya Application Solutions IP Te lephony Deployment Guid e Communication Manager and SES server processor occup ancy SIP incurs Communication Manager server proces sing time (as discussed in a previous section), just like any other type of Communica tion Manager call. S pecial care should go into accounting for the SIP fea[...]
-
Page 217
Resource sizing Issue 6 January 2008 217 Figure 70: Required number of bidirectiona l IP media streams for intra-site calls Figure 71: Required number of bidirectiona l IP media streams for inter-site calls 1 P C COI Matrix P er- C a ll I n t er - Si te R esource U sage (IP media streams within each part icipating site’s LAN, as well as between t[...]
-
Page 218
Traffic engineer ing 218 Avaya Application Solutions IP Te lephony Deployment Guid e Example 6: IP bandwid th considerations The information in Figure 70 and Figure 71 along with the information in T able 33 produces the following tables of b andwidth usages th at are associated with the configuration in Example 4: Expanded COI mat rices . T able 3[...]
-
Page 219
Resource sizing Issue 6 January 2008 219 T able 39 and Ta b l e 4 0 express bandwidth usages in Erlangs, because e ach such usage actually represents the average number of simu lt aneous bidirectional media streams through the IP network in question. T o convert those usages into bandwid th requirements in unit s of kilobits pe r second (kbps), one[...]
-
Page 220
Traffic engineer ing 220 Avaya Application Solutions IP Te lephony Deployment Guid e T able 41: Payload size per p acket on page 220 is populated using this formula, and pr ovides the paylo ad size per packet (expresse d in bits) as a function of p acket “size” (that is, ms per packet) and codec. Note that the number of bit s of paylo ad per pa[...]
-
Page 221
Resource sizing Issue 6 January 2008 221 Example 7: LAN bandwid th In Example 6 : IP bandwidth consideratio ns , the total IP LAN bandwidth usage for each site was calculated, and expressed in Erlangs at t he bottom of Ta b l e 3 9 . S pecifically , the total LAN bandwidth usage in Site 1 is 123.5 Erlangs, in Site 2 is 56.6 Erlangs, and in Site 3 i[...]
-
Page 222
Traffic engineer ing 222 Avaya Application Solutions IP Te lephony Deployment Guid e table of W AN bandwidths, T able 44: IP W AN bandwidth requirement s for media streams on page 222, which a ssumes the use of cR TP: This table can be u sed in the W AN bandwidth calculation for the system in Example 6: IP bandwidth considerat ions . Example 8: W A[...]
-
Page 223
Resource sizing Issue 6 January 2008 223 In T able 45 , the number of simultaneous media streams for “P001” rep resents the 9 9.9th percentile for the numbe r of simultaneou s streams, as determined by applying the st andard infinite-server queueing model. T o this point, all the discussion regarding band widt h relates only to bearer traf fic [...]
-
Page 224
Traffic engineer ing 224 Avaya Application Solutions IP Te lephony Deployment Guid e Physical resource placement As a default, resources shou ld be balanced as uniformly as possible. For example, if 1 1 Media Processors are required in a Network Region that has three PNs, two of the PNs should house four Media Processors each, and the oth er PN sho[...]
-
Page 225
Avaya Distributed Office Issue 6 January 2008 225 A vaya Distributed Office Distributed Office is a communications system consisting of a number of geograph ically dispersed nodes or branches. Each bran ch contains a Distributed Of fice branch solution running both a SIP proxy se rver and a SIP feature server for local end points. The single-locati[...]
-
Page 226
Traffic engineer ing 226 Avaya Application Solutions IP Te lephony Deployment Guid e Of the flow component s listed above, the first three, rela ted to call traf fic, should be the most commonly considered loads. Call traf fic patterns and profiles heavily d epend on the specific type of business conducted at the branches, such as retail, support, [...]
-
Page 227
Issue 6 January 2008 227 Security This chapter discusses the security design and feat ures for Avaya Co mmunication Manager , and how to operate A vaya systems securely . Note: Note: Because this information is valuable both to those who want to protect the system and to those who seek to “hack” into those systems, the information in this secti[...]
-
Page 228
Security 228 Avaya Application Solutions IP Te lephony Deployment Guid e What are you trying to protect? The security policy usually attempt s to protect information, whethe r the information is in the form of data (files) o r conversations (digitiz ed voice packet s). Customers should assess the value of those assets that require protection, and c[...]
-
Page 229
Avaya Communication Manager and Ser vers Issue 6 January 2008 229 A vaya Communication Manager and Servers This section discusses A vaya’s security d esigns: ● Built-in Linux security features ● One-time passwords ● Shell access ● Root access ● Remote access ● Secure access ● Monitoring and alarming ● Data encryption Built-in Linu[...]
-
Page 230
Security 230 Avaya Application Solutions IP Te lephony Deployment Guid e A vaya capit alizes on Li nux’ security advant age The Ava ya servers run under the Linux operating system that has two import ant security features: ● Built-in protection against cert ain types of De nial of Service (DOS) attack, such as SYN floods, ping floods, malformed[...]
-
Page 231
Avaya Communication Manager and Ser vers Issue 6 January 2008 231 Root access On a Linux system, the highest admi nistrative-access level is called root . Dire ct logins to root-level account s are not permitted on Avaya se rvers. Administrative acce ss, which requires root-level permissions, is handl ed through “p roxy” programs that grant spe[...]
-
Page 232
Security 232 Avaya Application Solutions IP Te lephony Deployment Guid e Secure access T ypical server access methods include telnet, W eb browser (HTTP), and FTP for file transfers. Each of these mechanisms can support login aut hentication, but suff er a common weakness. The passwo rd that you type during login is sent in clear text, which allows[...]
-
Page 233
Avaya Communication Manager and Ser vers Issue 6 January 2008 233 Dat a encryption Attacks against a system are not limited to attempts to find holes in the access structure . Avaya servers store backup copies of critical confi guration information , including authentication and account information, on external sy stems. If this information is stor[...]
-
Page 234
Security 234 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 72: A vaya S8700-series Server with an A vaya MCC1 or an SCC1 Media Gateway T o provide the most secure environment that is possible for the system, network access shou ld be divided into sep arate zones of control. These zones are sometimes referred to as DMZs . ● On[...]
-
Page 235
Avaya Communication Manager and Ser vers Issue 6 January 2008 235 Figure 73: Isolated LANs (A vaya S8700-series Server with an MCC1 or an SCC1 Media Gateway) Figure 73: Isolated LANs (Avaya S8700-series Server w ith an MCC1 or an SCC1 Media Gateway) on page 235 shows h ow Communication Manager can be configured to a llow only certain types of acces[...]
-
Page 236
Security 236 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 74: Isolated LANs (A vaya S8700-series Server with a G650 Media Gate way) V irus and worm protection Viruse s and worms are most ofte n targeted at Microsof t Windows operating systems or such commonly used applications as IIS, Exchange, Outlo ok, or Word. Becau se the [...]
-
Page 237
Avaya Communication Manager and Ser vers Issue 6 January 2008 237 Te s t i n g During the development of the S8300, S850 0, and S8700-series Servers, or in pro duction of upgrades to its sof tware, A vaya subjects the system to a variety of co mmon “attack tools” to find any overlooked or accident ally created security holes. The exact set of t[...]
-
Page 238
Security 238 Avaya Application Solutions IP Te lephony Deployment Guid e IP T elephony circuit p ack security Avaya circuit packs such as those in the G650 Media Gateways have a variety of securit y measures that combine both voice and data security stra tegies in to a secure package. The G650 use three dif ferent Ethernet interfaces to help isolat[...]
-
Page 239
IP Telephony circuit pack security Issue 6 January 2008 239 FTP An FTP service exist s , but is disabled by def ault. Commun ication Manager must enable the FTP service, and only does so for firmware downloads. On ce the FTP service is started, Communication Manager initiates the client-side of the FTP protocol, and then transfers a new firmware fi[...]
-
Page 240
Security 240 Avaya Application Solutions IP Te lephony Deployment Guid e TN799DP Control LAN (C-LAN) The C-LAN circuit p ack interface not only support s signaling for IP T elephony applications, but also supports asynchronous links to INTUITY AUDIX, Call Management System (CMS), and other adjuncts. This interface ● Is independent of the Media Ga[...]
-
Page 241
Toll fraud Issue 6 January 2008 241 A vaya’ s security design T elecommunications systems fa ce significant and growing problems of thef t of customer services. T oll fraud, the unauthorized use of a syst em and its facilit ies by a third party , can result in substantial ad ditional charges for telecommunicat ions services. Avaya makes every eff[...]
-
Page 242
Security 242 Avaya Application Solutions IP Te lephony Deployment Guid e Y our toll fraud responsibilities No telecommunications system can be entirely free f rom risk of unauthorized use. But diligent attention to system management and security can reduce that risk considerably . Often a trade-off is required between reduced risk and f lexibility [...]
-
Page 243
Toll fraud Issue 6 January 2008 243 Security Audit Service The Ava ya Security Audit Service is a fee-based, consultation service tha t provides a security evaluation of a customer's telecommunications system. The Security Audit is conducted b y a Avaya team of experts and in cludes: 1. Preliminary telephone interview 2. On-site or remote secu[...]
-
Page 244
Security 244 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 245
Issue 6 January 2008 245 V o ice quality network requirement s In addition to the influence of the telephony terminals at either end of a connection, there are several network p arameters that can af fect voice quality . This chapter lists some o f the more important ones. The concept of voice quality has dif ferent aspects that need to be properly[...]
-
Page 246
Voice quality network re quirements 246 Avaya Application Solutions IP Te lephony Deployment Guid e Some of the issues that must be conside red when designing a network for V oIP are: ● One-way delays in excess of 250 ms can caus e the well-known prob lem of "talk-over ." This occurs when both parties t alk at the same time because the [...]
-
Page 247
Jitter Issue 6 January 2008 247 Jitter Jitter is thought of as the sta tistical average variance of the arrival time b etween packet s received from the IP network. T o compensate for jit ter , a de-jitter buffer is implemented in V oIP endpoint s. The purpose of the jitter buf fer is to hold incoming packets for a specified per iod of time such th[...]
-
Page 248
Voice quality network re quirements 248 Avaya Application Solutions IP Te lephony Deployment Guid e The effe cts of p acket loss on V oIP service are multifold: ● Problems caused by occasional p acket loss ar e dif ficult to detect because each codec has its own p acket loss concealment method (PLC). Therefore, it is possible that voice quality w[...]
-
Page 249
Echo Issue 6 January 2008 249 Packet loss concealment (PLC) Some packet loss can be dea lt with by attempting to co nceal the loss by generating voice samples to take the place of the missing samples. ITU st andards G .71 1 Annex I and the G .729 standard define methods by which p acket loss concealment can be provi ded. Excessive packet loss canno[...]
-
Page 250
Voice quality network re quirements 250 Avaya Application Solutions IP Te lephony Deployment Guid e Resource 320, the A vaya IP SoftPho ne, and the A vaya 4600 Series IP T elephone all incorporate echo cancellation designed fo r IP T elephony to improve voice quality . Signal levels In order to provide more natural-sounding conversa tions, voice co[...]
-
Page 251
Codecs Issue 6 January 2008 251 Echo and Signal Levels As mentioned before, in circuit-switch ed telepho ny , echo may be caused by acoustic reflection in the remote pa rty's environment, or by electric al reflection from 2-to-4 wire a nalog hybrid impedance mismatches. Impedan ce mismatch can occur in analog telephones and analog lin e/ trunk[...]
-
Page 252
Voice quality network re quirements 252 Avaya Application Solutions IP Te lephony Deployment Guid e T able 46 provides a comparison of voice quality con siderations associa ted with some of the codecs supported by Avaya pro ducts. T oll-quality voice must achieve a MOS (Mean Opin ion Score) of 4 or above. The MOS scoring is a long-standing, su bjec[...]
-
Page 253
Silence suppress ion/VAD Issue 6 January 2008 253 ● 320 channels of V .32 SPRT The above channel counts are the same if AES encryption and SHA-1 authentication are enabled. The One-X Deskphones (96xx) support the G .722 codec with 64 kbp s and with 20 ms packets Generally , G .71 1 is used on LANs because bandwidth is abundant and inexp ensive wh[...]
-
Page 254
Voice quality network re quirements 254 Avaya Application Solutions IP Te lephony Deployment Guid e ● Avaya 4600 series IP T elephone ● Av aya IP SoftPh one ● Avaya Media Gate ways For procedures to administer QoS p arameters, refer to Administration for Network Conne ctivity for Avaya Communication Manag er (555-233-504). T ranscoding/t ande[...]
-
Page 255
Translatin g low level statistics t o an Applic ation Performance rat ing Issue 6 January 2008 255 T ranslating low level st atistics to an Application Performance rating The CNA assessment of application performanc e is based on application models, which convert the raw delay , jitter , and loss measurem ents into an application performance rating[...]
-
Page 256
Voice quality network re quirements 256 Avaya Application Solutions IP Te lephony Deployment Guid e A vailable application models Vo i c e The voice model convert s low level st atistics (network delay , latency , and loss) into an APR score that take s into account voice requirement s. Given the sensitivity of voice to jitter , the voice model is [...]
-
Page 257
Issue 6 January 2008 257 A vaya Integrated Management This chapter outlines Ava ya’s system, net work, and device management and monitoring products , and some common third-p arty tools. It also discusses the distributed a nd centralized management models, and d escribes how Avaya ma nagement product s fit into those models. Integrated Management[...]
-
Page 258
Avaya Integrated Manageme nt 258 Avaya Application Solutions IP Te lephony Deployment Guid e Administration T ools Offer Administration T ools is a Microsoft Windows solution for A vaya Integrated Management. It is designed for small-to-med ium size networks t hat run Microsof t Windows platforms. The Avaya Integrated Management applications p rovi[...]
-
Page 259
Avaya Integr ated Management offers Issue 6 January 2008 259 Enterprise Network Management Offer Enterprise Network Management is a Microsof t Windows solution for Avaya Integrated Management. It is designed for V oIP networks of any size that run Microsof t Windows platforms. It provides a complete converged solution th at helps you ma nage your n[...]
-
Page 260
Avaya Integrated Manageme nt 260 Avaya Application Solutions IP Te lephony Deployment Guid e voice and data network from a ce ntral location; and manage the A vaya network server and IP endp oints. Note: Note: The most current release of the System Manageme nt offer is Relea se 3.2. System Management Release 3.2 applications are co mpatible with th[...]
-
Page 261
Network management mode ls Issue 6 January 2008 261 ● Monitors any SNMP variable that yo u choose. Y ou can even use an external prog ram to gather the dat a that MRTG sh ould monitor , for example: - System load - Login sessions - Modem availability For more MR TG information, see: ● http://www .mrtg.org for the main MRTG W eb site. Their pr o[...]
-
Page 262
Avaya Integrated Manageme nt 262 Avaya Application Solutions IP Te lephony Deployment Guid e Distributed (component) Distributed network management is the default management mo del for network equipment. As Figure 76 shows, each device is managed sep arately , and can have its own management interface. There is no commonality between t hese interfa[...]
-
Page 263
Network management mode ls Issue 6 January 2008 263 Figure 77: Centralized management mode l Additional management tools, such as A v aya Network Management Console with V oIP SystemView , attach to the framework ( Figu re 77 ). They can be launched directly from the underlying application, and can share data with it. This allows a networ k adminis[...]
-
Page 264
Avaya Integrated Manageme nt 264 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 265
Issue 6 January 2008 265 Reliability and Recovery The purpose of this chapter is to provi de the reader an overview of the subject of communication-system “availability ,” specif ic to Avaya Communi cation Manage r and Avaya servers and gateways. The discussion th at follows demonstrates A vaya’s long-stand ing commitment to high availability[...]
-
Page 266
Reliability and Recovery 266 Avaya Application Solutions IP Te lephony Deployment Guid e Reliability Customers need the full reliability of their tradi tional voice networks, including feature richness and robustness, and they want the opt ion of using converged voice and dat a infrastructures. With the convergence of voice and da ta applications t[...]
-
Page 267
Survivability solutions Issue 6 January 2008 267 Use the indicated links to access these do cuments on the A vaya Support web site. Survivability solutions Avaya Communication Manger release 3.0 introduces new features in support of enh ancing high availability and surv ivability . These features are in su pport of business continuity through unsch[...]
-
Page 268
Reliability and Recovery 268 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 78: Release 3.0 system example S8700-series Server Sep aration S8700-series server sep aration allows the two servers in an S8700-series Server p air to be geographically sep arated up to a maximum dist ance of 10 kilometers over a fiber-optic link. Sepa[...]
-
Page 269
Survivability solutions Issue 6 January 2008 269 Enterprise survivable servers (ESS) Note: Note: See Using the A vaya Enterprise Survivable Servers (ESS) , 03-300 428, for additional information about ESS. The Enterprise Survivable Server (ESS) is a su rvivability o ption for S8700-series and S8500/ S8500(B) systems and is avail able with the Commu[...]
-
Page 270
Reliability and Recovery 270 Avaya Application Solutions IP Te lephony Deployment Guid e ESS System Cap acities ESS can be administered as “local only” or as an “enterprise-wide” survivable server(s). When administered as “Local only”, which ind icates it will act as the survivabl e server for a community or a subset of port networks, u[...]
-
Page 271
Survivability solutions Issue 6 January 2008 271 Connection preserving upgrades for duplex servers This feature is designed for preserving st able bearer connections for TDM end poin ts and IP stations during an upgrad e of S8700/S8710 duplex servers. TDM and IP connection of H.248 Media Gateways, with the S8700/ S8710 being the ma in call controll[...]
-
Page 272
Reliability and Recovery 272 Avaya Application Solutions IP Te lephony Deployment Guid e IGAR relies on Call Admission Control. When a ll V oIP RTP resources have been used the next attempt to get a V oIP RTP resource result s in denial of the V oIP connection. Communication Manager 3.0 will attempt to use existing applic ations and fea tures to re[...]
-
Page 273
Survivability for branch office media gateways Issue 6 January 2008 273 In the event of a W AN failure, any IP telephone or media g ateway that cannot reach the primary controlling server can register with an LSP co n troller in survivable mode. In the S8 700/G700/ G350 configuration, up to 50 LS Ps are available and ready for the fail-over process[...]
-
Page 274
Reliability and Recovery 274 Avaya Application Solutions IP Te lephony Deployment Guid e The auto fallback process While LSP is the acting call controller , the Media Gateway attempts to register with the prima ry server every 30 seconds or whenever there are no active calls (this signaling also acts as keep-alive messages to the primary serve r). [...]
-
Page 275
IP endpoint recovery Issue 6 January 2008 275 The link recovery process fo llows these steps: 1. While SLS is e nabled and processing, the me dia gateway continues to seek an alternative media gateway controller . 2. If A vaya Communication Manager accept s the registration then the active IP to IP calls that shuffle are prese rved. 3. The SLS appl[...]
-
Page 276
Reliability and Recovery 276 Avaya Application Solutions IP Te lephony Deployment Guid e A C-LAN provides two basic reliability functions: ● A C-LAN hides server interchanges from the IP endpoint s. The signaling channels of the endpoint s remain intact during server interchanges, and do not have to be reestablished with the new active server . ?[...]
-
Page 277
IP endpoint recovery Issue 6 January 2008 277 While the LSP is not call preserving, the fa il-over from primary gatekeeper to LSP is an automatic process, and doe s not require human interven tion. The fail-back from LSP to primary gatekeeper , however , is not currently automatic, and requires a system reset on the LSP . During the fail-back to th[...]
-
Page 278
Reliability and Recovery 278 Avaya Application Solutions IP Te lephony Deployment Guid e If re-registration is not required, only the re-est ablishment of the TCP socket is needed, which is also done in an on-demand fashion. Currently , in a call center environment, the agents mu st always log-in again whenever the end point becomes un-registered. [...]
-
Page 279
IP endpoint recovery Issue 6 January 2008 279 This path optimization fe ature can be used to protect both the vo ice bearer traf fic and the voice signaling traf fic. S tudies have shown that enabl ing CNA p ath optimization can yield more than an order of magnitude improvemen t in application availability . See Section 3: Getting the IP network re[...]
-
Page 280
Reliability and Recovery 280 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 281
Issue 6 January 2008 281 Section 3: Getting the IP network ready for telephony[...]
-
Page 282
282 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 283
Issue 6 January 2008 283 IP T elephony network engineering overview In the early days of local area networking, ne twork designers used hubs to att ach servers and workstations, an d routers to segment the netwo rk into manageable pieces . Because of the high cost of router interfaces and the inherent limitatio ns of shared-media hubs, network desi[...]
-
Page 284
IP Telephony network engineerin g overview 284 Avaya Application Solutions IP Te lephony Deployment Guid e In general, these concerns dict ate a hierarchical net work that consists of at most three layers ( T able 48: Layers in a hierarchical network on p age 284): ● Core ● Distribution ● Access Some smaller networks can collap se the functio[...]
-
Page 285
Voice quali ty Issue 6 January 2008 285 The following W AN technologies are commonly used with IP T elephony: ● MPLS (Multiprotocol Label Switching) ● A TM (Asynchronous T ransfer Mode) ● Frame Relay ● Point-to-point (PPP) circuits ● Internet VPNs The first four technologies all have g ood throughput, low latency , and low jitter . MPLS a[...]
-
Page 286
IP Telephony network engineerin g overview 286 Avaya Application Solutions IP Te lephony Deployment Guid e trunk that links the west coast of the United S tates to India could add a f ixed delay of 150 milliseconds (ms) into the overall dela y budget. Perfectly acceptable voice quality is attainable, bu t will not be “toll” quality . Therefore,[...]
-
Page 287
Best prac tices Issue 6 January 2008 287 The Converged Network Analyzer (CNA) can he lp you measu re and report on network delay , jitter , and packet loss. CNA can a lso provide you with a rating of voice quality using the 0-5 APR score (see C NA Application Performance Ratin g on p age 254). With the optional Path Optimiza tion feature, CNA can a[...]
-
Page 288
IP Telephony network engineerin g overview 288 Avaya Application Solutions IP Te lephony Deployment Guid e Common issues Some common negative practices that can seve rely impact network performance, especially when using IP T elephony , include: ● A flat, non-hierarchical network , for example, cascading small workgroup switches together . This t[...]
-
Page 289
Issue 6 January 2008 289 Network design This section discusses the network de sign process for IP T elephony . This section focuses on: ● LAN issues ● WA N ● VPN ● NA T LAN issues This section covers Local Area Network (LAN) is sues, including speed and duplex, inline power , hubs versus switches, and so on: General guidelines Because of th[...]
-
Page 290
Network design 290 Avaya Application Solutions IP Te lephony Deployment Guid e Ethernet switches The following recommendations apply to Ethe rnet switches to optimize operation with A vaya endpoint s. Theses recommendations are meant to provide the simplest co nfiguration by removing unnecessary features. ● Enable spannin g tree fast start featur[...]
-
Page 291
LAN issues Issue 6 January 2008 291 VLANs Virtual Loca l Area Networks (VLANs) are an of ten-misunderstood concept. This section begins by defining VLANs, and then addresses configu rations that require the A vaya IP T elephone to connect to an Ethernet switch p ort that is confi gured for multiple VLANs. The IP T elephone is on one VLAN, and a per[...]
-
Page 292
Network design 292 Avaya Application Solutions IP Te lephony Deployment Guid e T runk configuration A trunk port on an Ethernet switch is one that is capable of forwarding Ethernet frames on multiple VLANs through the mechanism of VLAN t agging. IEEE 802.1Q specifies the st andard method for VLAN taggin g. Cisco also uses a propriet ary method call[...]
-
Page 293
WAN Issue 6 January 2008 293 e. Apply the configured VLANs to the port, and permit only those VLANs (bind-to-all permits all VLANs and not just the configured) by typing set port vlan-binding-mode <mod/ port> bind-to-configured 3. For simplicity , Avaya recommends using the st atic option for IP T elephony . If the port is connected to a rout[...]
-
Page 294
Network design 294 Avaya Application Solutions IP Te lephony Deployment Guid e Overview QoS In particular , Quality of Servic e (QoS) becomes more important in a W AN environment than in a LAN. In many cases, transitioning from the LAN to the W AN reduces bandwidth by approximately 99%. Because of this severe bandwidth crunch , strong queuing, buf [...]
-
Page 295
WAN Issue 6 January 2008 295 T o conserve even more bandwidth, R TP header compression (cRTP) can be use d on point-to-point links. cRTP reduces the IP/UDP/RTP overhead from 40 b ytes to 4 bytes. With 20-ms packe ts, this transla tes to a savings of 14.4 Kbps, ma king the tota l bandwidth required for G .729 approximately 9.6 Kbps. The tra de-off f[...]
-
Page 296
Network design 296 Avaya Application Solutions IP Te lephony Deployment Guid e Multip ath routing Many routing protocols, such as OSPF , install multiple routes fo r a particular destination into a routing tab le. Many routers attempt to load-balance across the two p aths. There are two methods for load balancing across multiple paths. The first me[...]
-
Page 297
WAN Issue 6 January 2008 297 Figure 79: Dat a-link connection identifiers over an interexchange carrier Frame Rel ay network This hypothetical implement ation shows the Dallas corporate of fice connected to three branch offices in a common st ar topology (or hub and spoke). Each of fice connects to a LE C CO over a fractional T1 circuit, which term[...]
-
Page 298
Network design 298 Avaya Application Solutions IP Te lephony Deployment Guid e As Figure 80: Committed information rate (burst range) shows, traf fic up to the CIR is guaranteed, whereas traf fic beyond the CIR usually is not. This is how Frame Relay is in tended to work. CIR is a committed and reliab le rate, whereas burst is a bonus wh en network[...]
-
Page 299
VPN Issue 6 January 2008 299 VPN Many definitions exist for Virtual Private Networ ks (VPNs). VPNs refer to encrypted tunnels that carry packetize d data betwe en remote sites. VPNs can use private lines, or use the Internet through one or more Internet Service Providers (ISPs). VPNs a re implemented in both dedicated hardware and sof tware, but ca[...]
-
Page 300
Network design 300 Avaya Application Solutions IP Te lephony Deployment Guid e Managing IP T elephony VPN issues This section provides information on communica tions security , firewall technologies, and network management as re lated to VPN issues. Communication security The public nature of the Internet , its reach, and its shared infrastructure [...]
-
Page 301
VPN Issue 6 January 2008 301 Firewall technologies T o reduce security risks, appropriate network acce ss policies should be defined as p art of business strategy . Firewalls can be used to enfor ce such policies. A firewall is a network interconnection element that polices traf fic the flows between internal (protected) networks and external (publ[...]
-
Page 302
Network design 302 Avaya Application Solutions IP Te lephony Deployment Guid e Conclusion Moving to a multipurpose p acket-based VPN that transports both voice and data with high quality poses a number of significant m anagement challenges. Managers must de termine whether to operate the netwo rk using an enterprise-based model, an out sourced or c[...]
-
Page 303
NAT Issue 6 January 2008 303 Solutions based on futu re standards ICE and STUN are expected to be supported in some NA T traversal scenarios where applicable. Figure 81: IP T elephony without NA T[...]
-
Page 304
Network design 304 Avaya Application Solutions IP Te lephony Deployment Guid e Converged network design Converged networks require the application of good management and control practices to support and sustain the d eployment of IP tel ephony . The first step in implementing an IP telephony system is making the commitment to provid e a network cap[...]
-
Page 305
Converged network des ign Issue 6 January 2008 305 train. A conscious choice to favor simplicity in design may be the single biggest factor in improving uptime due to its casca ding effect on process, document ation and verification. Design for Manageability S tudies of operator errors have identified several classes of errors typical o f network s[...]
-
Page 306
Network design 306 Avaya Application Solutions IP Te lephony Deployment Guid e T opologies The network topology most commonly recommended c onsist s of a redundant core with building blocks of layered routers and switches as shown in the figure be low . This is the defacto standard for network design suppo rting both modularity and reuse. Figure 82[...]
-
Page 307
Converged network des ign Issue 6 January 2008 307 Figure 83: Layered Server Cluster T opology Assume that each G650 is equipped with redu ndant TN2602AP Media Resource 320 circuit packs optio nally configured for load balancing or I P bearer duplication. Each G650 is also assumed to contain duplicated TN23 12BP IP Serv er Interfaces (IPSI). The nu[...]
-
Page 308
Network design 308 Avaya Application Solutions IP Te lephony Deployment Guid e configuration complexity with little benefit in term s of availability unless th e subnets termin ate on different route rs, which in turn implies sep a rate modular clusters. An argume nt can be made that separa te subnets simplify diagnostic activiti es, but this bene [...]
-
Page 309
Converged network des ign Issue 6 January 2008 309 Figure 85: Redundant conn ections It is good practice to have the red undant boards of each PN connected to redundant Layer 2 switches as shown to protect each PN from failu re of the Layer 2 switch itself. If asymmetric redundancy is configured through IP bearer duplicati on, it is essential for p[...]
-
Page 310
Network design 310 Avaya Application Solutions IP Te lephony Deployment Guid e Layer 2 Layer 2 configuration o f the switches supporting the cluster sh ould use IEEE 802.1w Rapid S panning T ree Protocol (RSTP) to prevent loop s and for selection between redundant links. Most modern switches implement this protocol. Se lecting a device for Laye r 2[...]
-
Page 311
Converged network des ign Issue 6 January 2008 311 Figure 86: Sample sp anning tree If the primary router fails, the secondary rou ter becomes both the active router and the ro ot bridge, and traf fic from the switches flows on the reconfigured sp anning tree along links C & D. If bridge priorities are not managed, traf fic from one switch may [...]
-
Page 312
Network design 312 Avaya Application Solutions IP Te lephony Deployment Guid e Layer 3 The symmetric or asymmetric question is link ed to the configu ration of redundancy for the routers serving this cluster . If the single subnet model is used, the router configuration in the direction of the cluster will also follow th e asymmetric model. V irtua[...]
-
Page 313
Converged network des ign Issue 6 January 2008 313 References for Converged network design on p age 304 1. Infonetics 2/1 1/2004. 2. Network W orld 10/26/2004. 3. DMreview 2/18/2004. 4. Medium businesses lose $867,0 00 a year to network downtime 3/09/2006. 5. Gartner Research 7/03/2001. 6. Underst anding and Dealing with Operator Mi stakes in Inter[...]
-
Page 314
Network design 314 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 315
Issue 6 January 2008 315 Quality of Service guidelines This chapter contains guidelines for deploying Quality of Service (QoS) for a n IP T elephony network. This chapter begins with an overvi ew of Class of Service (CoS) versus QoS. Class of Service refers to mechan isms that tags traf fic in such a way that the traf fic can be differentiat ed and[...]
-
Page 316
Quality of Service guidelines 316 Avaya Application Solutions IP Te lephony Deployment Guid e Note that the 802.1Q t ag changes the size and the forma t of the Ethernet frames. Because of this, many switches must be explicitly co nfigured to accept 802.1Q t agged frames. Otherwise, these switches might reject the t agged frames. The two fields to b[...]
-
Page 317
Layer 2 QoS Issue 6 January 2008 317 Layer 2 QoS On Avaya and Cisco switches, IP T elephony traf fic can be assigned to higher priority queues. The number and the sizes of queues an d how the queues function are device depend ent, and beyond the scope of this document. However , in general, a fixed number of queues exist, and the queues a re usuall[...]
-
Page 318
Quality of Service guidelines 318 Avaya Application Solutions IP Te lephony Deployment Guid e serialization delay for a variety of p acket sizes and line speeds. The formula for determinin g serialization delay is: Because of all these configuration variables, proper ly implementing QoS on a router is no trivial task. However , QoS is needed most o[...]
-
Page 319
Layer 3 QoS Issue 6 January 2008 319 There is one caution to keep in mind about QoS with regard to the processor loa d on network devices. Simple routing and switching technologies have been around for many years and have advanced significantly . Packet forwarding at Layer 2 and Layer 3 is commonly done in hardware (Cisco calls this fast switching,[...]
-
Page 320
Quality of Service guidelines 320 Avaya Application Solutions IP Te lephony Deployment Guid e IEEE 802.1 p/Q Figure 89: 802.1Q t ag The IEEE 802.1Q st andard is a Layer 2 t agging method that adds 4 bytes to the Layer 2 Ethernet header . IEEE 802.1Q def ines the open standard for VLAN t agging. T wo bytes house 12 bits that are used to t ag each fr[...]
-
Page 321
DiffServ Issue 6 January 2008 321 Recommendations for end-to-end QoS When end-to-end QoS is desire d, Avaya recommen ds using DiffServ , a L ayer 3 CoS method. Modern routers can map DiffServ Code Point s (DSC P) to 802.1p priority values, so 802.1p t ags can be recreated on each Etherne t link. This functionality is supp orted in Avaya Laye r 3 sw[...]
-
Page 322
Quality of Service guidelines 322 Avaya Application Solutions IP Te lephony Deployment Guid e Figure 90: Differentiated Services (DiffServ) T OS byte A DiffServ Cod e Point (DSCP) of 46 (101 1 10), referred to as expedited forwarding (EF), is suggested for the proper treatment of voice p ackets. Sign aling packe ts can also be marked with DSCP 46 i[...]
-
Page 323
RSVP Issue 6 January 2008 323 policy . The TOS byte is an OSI model Layer 3 solution, and works on IP p ackets on th e LAN and possibly the W AN, depending upon the service provider . RSVP Resource Reservation Protoco l (RSVP) is a protocol that host s can use to request specific QoS parameters through the network for a particular applicatio n data[...]
-
Page 324
Quality of Service guidelines 324 Avaya Application Solutions IP Te lephony Deployment Guid e to the better-than-best-effor t (BBE) DSCP that is defined on the network region form. By default, this value is 43. If RSVP is enabled on a network region, it is very import ant that it also be enabled on associated routers. If not, all RSVP reservations [...]
-
Page 325
Queuing methods Issue 6 January 2008 325 Round-robin queuing is not p articularly suited to IP T elephony . It does not ensure strict enough priority to voice pa ckets, so they may still wait behind other traf fic flows in other queues. Latency and jitter can be at unaccept able levels. CB-WFQ / LLQ / CBQ Class-Based W eighted Fair Queuing (CB-WFQ)[...]
-
Page 326
Quality of Service guidelines 326 Avaya Application Solutions IP Te lephony Deployment Guid e T raffic shaping and policing T raffic shaping is a mechanism to reduce the rate at which dat a is transmitted over an interface. When people discuss traf fic shaping, they are usually referring to the related technology of traffic policing. Policing works[...]
-
Page 327
Fragmentation Issue 6 January 2008 327 Thus, the complete configuratio n for Frame Relay traffic shapin g 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 Fragment ation One la[...]
-
Page 328
Quality of Service guidelines 328 Avaya Application Solutions IP Te lephony Deployment Guid e *0.01 second (10 ms)/8 bits /byte = 480 bytes. As the circuit size diminishes, however , care should be taken to never reduce the MTU belo w 200 bytes. Below that size, telephony signaling and bearer (voice) p ackets can also be fra gmented, which reduces [...]
-
Page 329
RTP Issue 6 January 2008 329 It is important to un derstand that a ll 20-ms G .729 audio packets, regard less of the vendor , are constructed like this. Not only is the structure of the p acket the same, but the method of encoding and decoding the audio itself is also the same. This sameness is what allows an Avaya IP T elephone to communicate dire[...]
-
Page 330
Quality of Service guidelines 330 Avaya Application Solutions IP Te lephony Deployment Guid e RTP header compression test This section details the result s of a simple RTP header compression test that was con ducted in a laboratory environment. Although t his test wa s conducted using Cisco rout ers, the expected behavior is the same for any router[...]
-
Page 331
RTP Issue 6 January 2008 331 For each codec, there was an attempt to verify that the audio p ackets were received intact. This was done by spot checking the audio p acket s before and afte r compression, using two Snif fer protocol analyzers. For every codec except G .71 1, the RTP h eader and payload we re identical before and af ter compression. [...]
-
Page 332
Quality of Service guidelines 332 Avaya Application Solutions IP Te lephony Deployment Guid e See the Cisco document ation for more specific configurations o n other types of W AN links (that is, Frame Relay and A TM). Configuration for the X 330W AN router is very similar to Cisco, and is well documented in the X330W AN User Guides. For this docum[...]
-
Page 333
Examples of QoS implementation Issue 6 January 2008 333 Figure 92: High-quality se rvice across a congested W AN link CB-WFQ/LLQ is a priority-aware queuing strat egy that has a strict prio rity queue for voice packet s, and does round-robin queuing for other ty pes of traf fic. Non-prio ritized traf fic is still forwarded, however , so this should[...]
-
Page 334
Quality of Service guidelines 334 Avaya Application Solutions IP Te lephony Deployment Guid e Administration comm ands for Example 1 T able 58: Administration commands for Example 1 Command Meaning 1.class-map match-any VoIP Create a class map called “V oIP .” 2.match ip dscp 46 Any packet with DSCP 46 is in the class “V oIP .” 3.policy-map[...]
-
Page 335
Examples of QoS implementation Issue 6 January 2008 335 Example 2: C-LANS cannot t ag their traffic Assumptions for Example 2 ● The C-LANs 192.168.1.10 and.1 1 cannot tag their traf fic (TN-799C or earlier). ● The configuration command s in Ta b l e 5 9 are applied only to the left router . Administration comm ands for Example 2 T able 59: Admi[...]
-
Page 336
Quality of Service guidelines 336 Avaya Application Solutions IP Te lephony Deployment Guid e Example 3: More restrictions on the traffic Assumptions for Example 3 ● DSCP 46 is used throughout to simplify the a ccess list. ● A somewhat matching set of configuratio ns is applied to both routers. Administration comm ands for Example 3 T able 60: [...]
-
Page 337
Examples of QoS implementation Issue 6 January 2008 337 If any of the end points are incapable of t agging, the “dscp 46” can be removed from access list 101. Then any traffic between the two IP T elephony s ubnetworks, regardless of the tag, is in the class “V oIP .” Converged infrastructure LAN switches X330 W AN Module The new X330W AN v[...]
-
Page 338
Quality of Service guidelines 338 Avaya Application Solutions IP Te lephony Deployment Guid e 5.ip access-list-dscp trust 100 trust-cos-dscp T rust packet tagging. 6.interface FabricFastEthernet 1 Activate the above mapping o n ingress traffic to the Fabric Fast Ethernet interface 7.ip access-group 100 in Apply the ACL to traf fic that is arriving [...]
-
Page 339
Issue 6 January 2008 339 Network recovery Conventional wisdom holds that ne twork reliability is typically 3-9s (99.9%) on a LAN, and 2-9s (99%) on a W AN. The leading causes of network failure are a W AN link failure, administrator error , cable failure, issues that involve co nnecting new device s or services, and malicious activity , including D[...]
-
Page 340
Network recovery 340 Avaya Application Solutions IP Te lephony Deployment Guid e Layer 2 mechanisms to increase reliability S p anning tree IEEE 802.1D spanning tree is an Ethernet loop avoidance protocol. It al lows network managers to connect redundant network links within their networks. Prior to the advent of spanning tree, loops within a switc[...]
-
Page 341
Layer 3 availability mechanisms Issue 6 January 2008 341 Layer 3 availability mechanisms Routing protocols Routing protocols allow ro uters to dynamically learn the topology of the network. Should the topology of the netwo rk change, routing protocols update th eir internal topology table, wh ich allows them to route around failure. There are two t[...]
-
Page 342
Network recovery 342 Avaya Application Solutions IP Te lephony Deployment Guid e Multip ath routing Modern routers and Layer 3 switches allow mu ltip le routes for a particula r destination to be installed in the routing table. Depending on the implementation, this can b e as high as six routes. Some implement ations require that all rout es that a[...]
-
Page 343
Convergence t imes Issue 6 January 2008 343 Convergence times Convergence is the time that it takes from t he in stan t a failure occurs in the network u ntil 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 co mplexity and size of a network. T able 62: Sample[...]
-
Page 344
Network recovery 344 Avaya Application Solutions IP Te lephony Deployment Guid e The Converged Network Analyzer The Converged Network Analyzer (CNA) is an of fer from the Avaya Ap plication Assurance Networking (AAN) line of product s. It provides two princip al value propositions: ● visibility ● path optimization . Visibility is a chieved thro[...]
-
Page 345
The Converged Network Analyze r Issue 6 January 2008 345 such as Extreme Networks ( http:// www .extremenetworks.com/ homepage.a sp ). T est agents are also available in low cost devices that can be deployed standalone. T est agents help complement server measurement s in two ways: they allow end to end mea surement to be performed between specific[...]
-
Page 346
Network recovery 346 Avaya Application Solutions IP Te lephony Deployment Guid e (Routers R1a, R1b, R1c), and on the branch side (R2a, R2b, and R2c); these rou ters would then have been able move the traf fic to Path B or Path C. In practice, howeve r , some dynamic routing protocols such as Border Gateway Protocols (BGP) are slow to prop agate rou[...]
-
Page 347
The Converged Network Analyze r Issue 6 January 2008 347 Sites A and B will move away from the out age in less than a second, preventing un intelligibility in the audio bearer , or outages in the voice signaling. Simult aneous monitoring of all paths The ability for CNA to me asure all path s simult ane ously is achieved by configuring Policy Based[...]
-
Page 348
Network recovery 348 Avaya Application Solutions IP Te lephony Deployment Guid e Controlling edge routers CNA maintains a BGP peerin g with every edge device it needs to con trol. It is configured as a route reflector to the edge devices, which allows it to (1) receive state of the routing table from the edge devices, and (2) send BGP control messa[...]
-
Page 349
Issue 6 January 2008 349 Network assessment offer Avaya Communication Solutions and Integration (CSI) support s a portfolio of consulting and engineering of fers to help plan and design: ● IP T elephony ● Data Networking Services ● Network Security Services. How to contact the CSI ● On the Web — CSI ● E-Mail: bcsius@avaya.com ● Phone:[...]
-
Page 350
Network assessmen t offer 350 Avaya Application Solutions IP Te lephony Deployment Guid e Note: Note: The Basic Network Readiness Assessment Service is available in th e U.S. and Canada through direct and indirect channels. ● Detail ed network readiness a ssessment service is typically the seco nd phase in the Network Assessment for IP T elephony[...]
-
Page 351
Avaya network readines s assessment services Issue 6 January 2008 351 Site Configuration Survey The ECLIPS Site Configuration Surve y (SCS) is an detailed customer-view of the their network. This survey is required as p art of the Customer Infrastructure Readiness Survey proce ss. The ECLIPS SCS questionnaire must be filled out as completely as pos[...]
-
Page 352
Network assessmen t offer 352 Avaya Application Solutions IP Te lephony Deployment Guid e V it a l Agent analysis Vit al Agent is a high-level analysis tool that pa ssively monitors and report s throughput and performance st atistics and errors and reports any proble ms that the host computer encounters. The customer must inst all and run the V ita[...]
-
Page 353
Avaya network readines s assessment services Issue 6 January 2008 353 Use these links for more informatio n about the Detaile d network readiness assessment service components: ● The Detailed network readi ness assessment process ● Customer responsibilitie s ● Discovery ● Element monitoring ● Synthetic IP T elephony measurements ● Remot[...]
-
Page 354
Network assessmen t offer 354 Avaya Application Solutions IP Te lephony Deployment Guid e T able 64: Det ailed network readiness assessment servic e component s Component Who does this? What does this do? What are the result s? What happens with the result s? Network T opo logy Report Customer (may already be part of Basic service) Describes your n[...]
-
Page 355
Avaya network readines s assessment services Issue 6 January 2008 355 Customer responsibilities In order to successfully complete a Deta iled network readiness assessment the customer must: ● Provide technical resource personnel who are we ll-versed in the network in frastructure. ● Provide complete access to the network. ● Provide passwords [...]
-
Page 356
Network assessmen t offer 356 Avaya Application Solutions IP Te lephony Deployment Guid e Synthetic IP T elephony measurement s ● Inject busy hour IP T elephony call traffic simulation into live network segments ● Random CODECs and injection point s between pre-defined end point s /host s ● Injections initially within single f acilities , rep[...]
-
Page 357
Avaya network readines s assessment services Issue 6 January 2008 357 Customer deliverables ● Avaya networking experts perform disco very of the customer ’s network an d document findings in a Detailed Network Readiness Asse ssment Report delivered to the customer . ● Accurate network topology ● Measurements of actual usability performanc e[...]
-
Page 358
Network assessmen t offer 358 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 359
Issue 6 January 2008 359 Appendix A: CNA configuration and deployment This section provides det ailed CNA configurat ion procedures for the scenario shown in Figure 95 . For the purpose of gene rality , we assume two routers and three pa ths. Figure 95: Det ailed configuration scenario[...]
-
Page 360
CNA configuration and de ployment 360 Avaya Application Solutions IP Te lephony Deployment Guid e Configuring CNA Basic configuration Configuring V irtual Module Interfaces Avaya CNA Ethernet interfaces need to be associated with an Ethernet in terface and a physical connection to the network. Once the system has boot ed and all of its necessary po[...]
-
Page 361
Configuring CNA Issue 6 January 2008 361 Service Provider Access Links Each service provider that is to be manage d or monitored by Avaya CNA nee ds a link object defined. From config mode, enter en gine configuration mode: module engine T o associate a service provider with a link name, create the links using the link command. link provider_1 prov[...]
-
Page 362
CNA configuration and de ployment 362 Avaya Application Solutions IP Te lephony Deployment Guid e Assigning UST A T s to Providers module usta t command s now need to be defined for each W AN link: module ustat provider_1 link provider_1 vip 172.25.5.1 The ustat module specifies the association of th e UST A T module to a specific WAN link and the [...]
-
Page 363
Configuring CNA Issue 6 January 2008 363 Prefix bearer_1/32 Prefix bearer_2/32 end module engine active-measurement group AM_sig naling_targets type icmp rate 5 per-second timeout 200 target group bearer_targets end active-measurement group AM_bea rer_targets type icmp rate 5 per-second timeout 200 target group bearer_targets end end Decision makin[...]
-
Page 364
CNA configuration and de ployment 364 Avaya Application Solutions IP Te lephony Deployment Guid e route-assert-filter force decision-policy DP_signaling_targets set-application-model enterprise damped-mode disable end decision-policy DP_bearer_targets set-application-model voice damped-mode disable end set-decision-policy DM_signalin g_targets acti[...]
-
Page 365
Configuring the Routers Issue 6 January 2008 365 These are the IOS commands needed to set up the GRE tunnel interface on Ra (see Figure 95 ): interface Tunnel1 description GRE to provider_1 ip address 172.25.5.129 255.255.2 55.252 ip policy route-map provider_1 tunnel source 172.16.6.1 tunnel destination 172.16.6.4 S pecifically , here’s what the[...]
-
Page 366
CNA configuration and de ployment 366 Avaya Application Solutions IP Te lephony Deployment Guid e These commands will have to be repeated for each UST A T module/ISP pair; at which point the configuration would model th e network shown in Figure 95 . Routing Configuration Here, the routing to the UST A T VIPS are configured; the IBGP peering betwee[...]
-
Page 367
Configuring the Routers Issue 6 January 2008 367 Route Reflection The CNA system must be a route reflector client to all of the edge routers that will operate within the CNA system’ s sphere of influence. When multiple edge routers are being configured for route reflection, a BGP cluster ID is required. The number can be eith er a 32 bit integer [...]
-
Page 368
CNA configuration and de ployment 368 Avaya Application Solutions IP Te lephony Deployment Guid e Command summary All of the CNA and router configura tion commands described in this d ocument are listed in this section. For more information, please refer to the CNA administrat ive guide. CNA commands interface fastethernet 0/0 ip address 176.16.6.4[...]
-
Page 369
Command summary Issue 6 January 2008 369 route-assert-filter force link provider_1 provider-as 10 172.30.100.33 winner-set-priority prefer end link provider_2 provider-as 20 172.29.100.33 end link provider_3 provider-as 30 172.28.100.1 end bgp 65002 neighbor 172.16.6.1 link provider_1 neighbor 172.16.6.1 remote-as 65002 neighbor 172.16.6.2 link pro[...]
-
Page 370
CNA configuration and de ployment 370 Avaya Application Solutions IP Te lephony Deployment Guid e vip 172.25.5.1 ip route 10.6.0.1 255.255.255.2 55 172.16.6.1 ip route 0.0.0.0 0.0.0.0 tunnel 1 end module ustat provider_2 link provider_2 vip 172.25.5.2 ip route 10.6.0.2 255.255.255.2 55 172.16.6.2 ip route 0.0.0.0 0.0.0.0 tunnel 2 end module ustat p[...]
-
Page 371
Command summary Issue 6 January 2008 371 neighbor 172.16.6.4 route-refle ctor-client neighbor 172.16.6.4 soft-reconf iguration inbound neighbor 172.16.6.4 weight 200 Router Rb commands interface Tunnel2 description GRE to provider_2 ip address 172.25.5.133 255.255 .255.252 ip policy route-map provider_2 tunnel source 172.16.6.2 tunnel destination 1[...]
-
Page 372
CNA configuration and de ployment 372 Avaya Application Solutions IP Te lephony Deployment Guid e[...]
-
Page 373
Issue 6 January 2008 373 Index Index Numerical 1152A1 Power Unit . . . . . . . . . . . . . . . . 169 A ACM, see Avaya Communication Manager Alarms and troubleshoo ting . . . . . . . . . . . . . 52 API . . . . . . . . . . . . . . . . . . . . . . . . 160 ASB button G250 . . . . . . . . . . . . . . . . . . . . . 60 Asynchronous Transfer Mode . . . . .[...]
-
Page 374
374 Avaya Application Solutions IP Telephony Deplo yment Guide Index selecting . . . . . . . . . . . . . . . . . . . . 26 Contact Closure . . . . . . . . . . . . . . . . . . 49 Continuous telephon e services . . . . . . . . . . . 72 Control LA N . . . . . . . . . . . . . . . . . . . . 85 CoS . . . . . . . . . . . . . . . . . . . . . . . . 315 CSS .[...]
-
Page 375
Issue 6 January 2008 375 Index J J4350 router physical description . . . . . . . . . . . . . . . 67 slot locations . . . . . . . . . . . . . . . . . . 67 J6350 router physical description . . . . . . . . . . . . . . . 68 slot locations . . . . . . . . . . . . . . . . . . 68 L LAN ETH LAN POE ports (G250) . . . . . . . . . . . 60 LAN ports fixed . .[...]
-
Page 376
376 Avaya Application Solutions IP Telephony Deplo yment Guide Index hub-based network . . . . . . . . . . . . . 288 multiple subnets on VLAN . . . . . . . . . . 288 network address translation (NAT) . . . . . . 288 non-hierarchical netwo rk . . . . . . . . . . . 288 virtual private network (VPN) . . . . . . . . . 288 hierarchy . . . . . . . . . . [...]
-
Page 377
Issue 6 January 2008 377 Index S S8300 primary controller architecture . . . . . . . . 42 S8300 Server . . . . . . . . . . . . . . . . . . . 37 as LSP . . . . . . . . . . . . . . . . . . . . . 44 supported . . . . . . . . . . . . . . . . . . . 44 S8300 server in standalone deployment . . . . . . . . . . . . 44 S8400 Server . . . . . . . . . . . . .[...]
-
Page 378
378 Avaya Application Solutions IP Telephony Deplo yment Guide Index Voice Announcement over the LAN . . . . . . . . . 41 Voice over IP (VoIP) services . . . . . . . . . . . 48 , 72 voice quality . . . . . . . . . . . . . . . . . . . . 245 codecs . . . . . . . . . . . . . . . . . . . . . 251 delay . . . . . . . . . . . . . . . . . . . . . . 245 ech[...]