Reliability and Recovery
262 Avaya Application Solutions IP Telephony Deployment Guide
In this section, use the configuration recommended in Example 1 of
Traffic engineering
. Based
on the configuration data
Table 19: Example 1 configuration data
on page 145, and the
estimated traffic load, the following configuration was recommended.
As shown in
Figure 75: Case Study I: Configuration of the Three Sites
on page 263, this S8700
IP-Connect System has a pair of S8700 media servers residing at the headquarters office in
Atlanta, one port network (two G650 media gateways) at headquarters, one port network (one
or two G650 media gateways) in the Boston branch office, and two G700 Media Gateways in
the Cleveland branch office. The link between servers and IPSIs residing on a port network
(PN) at the headquarters site traverses the LAN. The links between the media servers and the
two remote sites cross the WAN.
For the purpose of assessing full system availability, the percentage of traffic generated at each
site serves as the prorating factor for the downtime expected as a result of a failure at that site.
The percentage of traffic generated at each site is calculated from the Communities of Interest
(COI) Matrix presented in
Traffic engineering
.
Case Study 1: The Standard reliability configuration:
●
The call processing link from the S8700 media servers to the G650 media gateways in the
headquarters is supported by a single LAN connection.
●
The call processing link from the servers to each of the branch offices is over a single
WAN link.
●
The quantity of C-LAN and Media Processor circuit packs or media modules follow the
recommendations in Section 2.1 for supporting the calculated traffic load, and have not
been engineered with N+1 reliability.
Table 55: Percentage of Traffic Generated by Each Site is
Calculated Based on Traffic COI Matrices. Total Traffic Generated
by All Sites is 226 Erlangs.
Inbound &
outbound
Site
Atlanta
Site
Boston
Site
Clevelan
d
Site Atlanta
98E =>
43.3%
32E =>
14.2%
12E =>
5.2%
5E =>
2.2%
Site Boston
36E =>
16%
12E =>
5.2%
4E => 2%
2E=>
0.9%
Site
Cleveland
16E => 7%
6E => 2.7%
2E =>
0.9%
1E =>
0.4%
Summary of Contents for Application Solutions
Page 1: ...Avaya Application Solutions IP Telephony Deployment Guide 555 245 600 Issue 3 4 1 June 2005 ...
Page 20: ...About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 21: ...Issue 3 4 1 June 2005 21 Section 1 Avaya Application Solutions product guide ...
Page 22: ...22 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 106: ...Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 124: ...Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 139: ...Issue 3 4 1 June 2005 139 Section 2 Deploying IP Telephony ...
Page 140: ...140 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 186: ...Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 204: ...Security 204 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 228: ...Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 274: ...Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 275: ...Issue 3 4 1 June 2005 275 Section 3 Getting the IP network ready for telephony ...
Page 276: ...276 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 356: ...Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 366: ...Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 367: ...Issue 3 4 1 June 2005 367 Appendixes ...
Page 368: ...Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 394: ...Access list 394 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 414: ...DHCP TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide ...