 |
|
|
|
|
Case Study (Corporate Headquarters)
CallManager Design
| The CallManager IP Telephony solution consists of a
single CallManager Cluster with eight (8) CallManager
Servers.
There is one (1) Publisher, one (1) TFTP server and six
(6) Subscriber machines. The Publisher is a Microsoft SQL 7.0
database that replicates its database to the 6
Subscriber machines. The database publisher is used to make
all configuration changes and also to produce call
detail records. The TFTP server facilitates the
downloading of configuration files, device loads
(operating code), and ring types. A dedicated database
publisher and a dedicated TFTP server are recommended
for large systems. Two (2) of the six (6) subscriber
machines are used to backup. The CallManager Solution
operates as a single cluster with 4 CallManager
Redundancy Groups. By provisioning a cluster of CallManager
Servers into redundancy groups to provide resilient call
control, other servers can pick up the load if any
device within the group fails. The CallManager Cluster consists of the following
servers: Server A is a dedicated database publisher. USNYHQVOIPPB01 (10.2.40.42/27) ·
Extension Mobility API for Agilquest Server B is a dedicated TFTP server. USNYHQVOIPTF01 (10.2.40.107/27) Server C is the primary Cisco CallManager for the following: USNYHQVOIPCM01 (10.2.40.10/27)
|
|
Server C |
|
|
|
|
Device |
Ports |
Weight |
Total |
|
IP Phone (79xx) |
1000 |
1 |
1000 |
|
Voicemail
(VG248) |
288 |
1 |
288 |
|
Conference Ports
(6608) |
96 |
3 |
288 |
|
PRI Gateway (6608) |
17 |
72 |
1224 |
|
FXO Gateway (3662) |
24 |
3 |
72 |
|
|
|
Total |
2872 |
Server D is the primary Cisco CallManager for the following:
USNYHQVOIPCM02 (10.2.40.43/27)
|
Server D |
|
|
|
|
Device |
Ports |
Weight |
Total |
|
IP Phone (79xx) |
1000 |
1 |
1000 |
|
fax/mdm (VG248) |
384 |
1 |
384 |
|
Conference Ports
(6608) |
96 |
3 |
288 |
|
PRI Gateway (6608) |
16 |
72 |
1152 |
|
FXO Gateway (3662) |
24 |
3 |
72 |
|
|
|
Total |
2896 |
Server E is the backup Cisco CallManager for Server C and Server D
USNYHQVOIPCB02
(10.2.40.74/27)
Server F is the primary Cisco CallManager for the following:
USNYHQVOIPCM03 (10.2.40.75/27)
|
Server F |
|
|
|
|
Device |
Ports |
Weight |
Total |
|
IP Phone (79xx) |
1000 |
1 |
1000 |
|
fax/mdm (VG248) |
384 |
1 |
384 |
|
Conference Ports
(6608) |
96 |
3 |
288 |
|
PRI Gateway (6608) |
16 |
72 |
1152 |
|
FXO Gateway (3662)- 1211 6th
Ave |
10 |
3 |
30 |
|
Call Center
Agents |
22 |
6 |
132 |
|
CTI Route
Points |
3 |
2 |
6 |
|
CTI Client
Port |
22 |
12 |
264 |
|
IP/IVR |
24 |
2 |
48 |
|
|
|
Total |
3304 |
USNYHQVOIPCM04 (10.2.40.106/27)
|
Server G |
|
|
|
|
Device |
Ports |
Weight |
Total |
|
IP Phone (79xx) |
1000 |
1 |
1000 |
|
fax/mdm (VG248) |
288 |
1 |
288 |
|
fax/mdm (VG248) - 1211 6th
Ave |
48 |
1 |
48 |
|
Conference Ports
(6608) |
96 |
3 |
288 |
|
PRI Gateway (6608) |
16 |
72 |
1152 |
|
|
|
Total |
2776 |
|
Server H is the backup Cisco CallManager for Server F and Server G. USNYHQVOIPCB02 (10.2.40.11/27) In the above configuration, four Cisco CallManager redundancy groups are required for servers CE, DE, FH and GH. Server E will act as a backup server to either server C or D in the event of a server failure, or a switch failure providing access to the server. Note that in this design that servers E, C, and D are connected to different core switches to avoid a single switch failure from impacting more than a single CallManager, which will help to maintain high availability. Server H will act as a backup server to either servers, F or G, in the event of a server failure, or a switch failure providing access to the server. Note that in this design that servers H, F, and G are connected to different core switches to avoid a single switch failure from impacting more than a single CallManager, which will help to maintain high availability. |
