Call Load Testing

Table Of Contents

Call Load Testing

Very Large Campus with Clustering over the WAN (SJC-RFD) Load Testing

Large SIP Site (DFW) Load Testing

Small-Campus SIP Site (ATL) Load Testing

Small-Campus H.323 Site (YYZ) Load Testing

North America Cisco Unified CallManager Interoperability Site (NYC) Load Testing

Call Load Testing

---

This chapter provides an overview of the call loads that were tested with various site models during Cisco Unified Communications Release 5.0(2) testing for IP telephony. It includes information for calls made within various site models (intracluster) and for calls made between site models (intercluster). During call load testing, the busy hour call attempt (BHCA) rates described in this chapter were sustained for five consecutive days.

---

Note The information in this chapter represents tested call rates, not the maximum call rate capabilities of the system. Also, call load testing was performed with all components configured with default trace/debug levels.

---

This chapter includes the following sections:

•Very Large Campus with Clustering over the WAN (SJC-RFD) Load Testing

•Large SIP Site (DFW) Load Testing

•Small-Campus SIP Site (ATL) Load Testing

•Small-Campus H.323 Site (YYZ) Load Testing

•North America Cisco Unified CallManager Interoperability Site (NYC) Load Testing

Very Large Campus with Clustering over the WAN (SJC-RFD) Load Testing

This section describes call load testing for calls originating or terminating in the San Jose (SJC) site or the Rockford (RFD) site in the Very Large Campus with Clustering over the WAN site model. The BHCA grand total tested for the SJC-RFD cluster was 76,659 busy hour call attempts. Table 22-1 shows the BHCA for various call types and call scenarios between different endpoints.

---

Note Some intercluster calls show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary services was performed at the originating cluster, which resulted in additional call processing at the originating cluster.

---

In addition to the call scenarios shown, the Cisco Unified Presence Server in the SJC-RFD cluster maintained 1,000 active logins from Cisco IP Phone Messenger clients and monitored 1,000 user presence states.

Table 22-1 Very Large Campus with Clustering over the WAN Site Model (SJC-RFD) Load Testing 

Call Type	Call Scenario	SJC-RFD BHCA 1	DFW BHCA	NYC BHCA	ATL BHCA	YYZ BHCA
Intracluster calls	SJC IP phone to SJC Cisco Unified Contact Center Express	3,000
	SJC IP phone to SJC Cisco Unified MeetingPlace	2,678
	SJC IP phone to SJC Cisco Unity	4,725
	SJC IP phone to SJC IP phone	5,400
	SJC IP phone to SJC IP phone (blind transfer)	1,013
	SJC IP phone to SJC IP phone (consult transfer)	1,013
	SJC IP phone to SJC IP phone (hold)	1,350
	SJC IP phone to SJC IP phone (conference)	900
	SJC encrypted IP phone to SJC encrypted IP phone	1,800
	SJC encrypted IP phone to SJC encrypted IP phone (blind transfer)	338
	SJC encrypted IP phone to SJC encrypted IP phone (consult transfer)	473
	SJC encrypted IP phone to SJC encrypted IP phone (hold)	900
	SJC encrypted IP phone to SJC encrypted IP phone (conference)	900
	SJC video IP phone to SJC video IP phone	2,138
	SJC video IP phone to SJC video IP phone (blind transfer)	473
	SJC video IP phone to SJC video IP phone (consult transfer)	297
	SJC video IP phone to SJC video IP phone (hold)	1,013
	SJC video IP phone to SJC video IP phone (conference)	540
	SJC IP phone to SJC PSTN2 to SJC PSTN to IP phone	35,280
	SJC IP phone to SJC PSTN (blind transfer) to SJC PSTN to IP phone	2,520
	SJC IP phone to SJC PSTN (consult transfer) to SJC PSTN to IP phone	2,520
	SJC IP phone to SJC PSTN (conference) to SJC PSTN to IP phone	3,375
	SJC IP phone to SJC analog (6624)	720
	SJC IP phone to SJC analog (Cisco VG224/ Cisco VG248)	1,260
	Intracluster BHCA Subtotal	74,626
Intercluster calls	SJC IP phone to ICT3 to DFW ICT to IP phone	599	599
	SJC IP phone to ICT (blind transfer) to DFW ICT to IP phone	338	113
	SJC IP phone to ICT (consult transfer) to DFW ICT to IP phone	338	113
	SJC IP phone to ICT (hold) to DFW ICT to IP phone	342	171
	SJC IP phone to ICT (conference) to DFW ICT to IP phone	342	114
	SJC IP phone to ICT to NYC ICT to IP phone	450		450
	SJC IP phone to ICT (blind transfer) to NYC ICT to IP phone	108		36
	SJC IP phone to ICT (consult transfer) to NYC ICT to IP phone	108		36
	SJC IP phone to ICT (hold) to NYC ICT to IP phone	118		59
	SJC IP phone to ICT (conference) to NYC ICT to IP phone	108		36
	SJC IP phone to ICT to ATL ICT to IP phone	68			68
	SJC IP phone to ICT to YYZ ICT to IP phone	36				36
	SJC IP phone to ICT (blind transfer) to YYZ ICT to IP phone	13				4
	SJC IP phone to ICT (consult transfer) to YYZ ICT to IP phone	13				4
	SJC IP phone to ICT (hold) to YYZ ICT to IP phone	10				5
	SJC IP phone to ICT (conference) to YYZ ICT to IP phone	18				6
	DFW IP phone to ICT to SJC ICT to IP phone	302	302
	DFW IP phone to ICT (blind transfer) to RFD ICT to IP phone	50	149
	DFW IP phone to ICT (consult transfer) to RFD ICT to IP phone	50	149
	DFW IP phone to ICT (hold) to RFD ICT to IP phone	76	153
	DFW IP phone to ICT (conference) to RFD ICT to IP phone	48	144
	NYC IP phone to ICT to RFD ICT to IP phone	599		599
	YYZ IP phone to ICT to RFD ICT to IP phone	36				36
	ATL IP phone to ICT to SJC ICT to IP phone	36			36
	Intercluster BHCA Subtotals	4,206	2,007	1,216	104	91
BHCA Grand Total for SJC-RFD Site		78,832

1 BHCA = busy hour call attempts. 2 PSTN = public switched telephone network. 3 ICT = intercluster trunk.

Large SIP Site (DFW) Load Testing

This section describes call load testing for calls originating or terminating in the Dallas (DFW) site in the Large SIP Site model. The BHCA grand total tested for the DFW cluster was 27,671 busy hour call attempts. Table 22-2 shows the BHCA for various call types and call scenarios between different endpoints.

---

Note Some intercluster calls show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary services was performed at the originating cluster, which resulted in additional call processing at the originating cluster.

---

Table 22-2 Large SIP Site Model (DFW) Load Testing 

Call Type	Call Scenario	SJC-RFD BHCA 1	DFW BHCA	NYC BHCA	ATL BHCA	YYZ BHCA
Intracluster calls	DFW IP phone to DFW IP phone		3,375
	DFW IP phone to DFW IP phone (blind transfer)		1,080
	DFW IP phone to DFW IP phone (consult transfer)		1,080
	DFW IP phone to DFW IP phone (hold)		1,125
	DFW IP phone to DFW IP phone (conference)		1,350
	DFW IP phone to DFW PSTN2 to DFW PSTN to IP phone		10,238
	DFW IP phone to DFW PSTN (blind transfer) to DFW PSTN to IP phone		570
	DFW IP phone to DFW PSTN (consult transfer) to DFW PSTN to IP phone		570
	DFW IP phone to DFW PSTN (hold) to DFW PSTN to IP phone		1,350
	DFW IP phone to DFW PSTN (conference) to DFW PSTN to IP phone		1,350
	DFW IP phone to DFW Unity		3,000
	Intracluster BHCA Subtotal	25,088
Intercluster calls	SJC IP phone to ICT to DFW ICT to IP phone	599	599
	SJC IP phone to ICT (blind transfer) to DFW ICT to IP phone	338	113
	SJC IP phone to ICT (consult transfer) to DFW ICT to IP phone	338	113
	SJC IP phone to ICT (hold) to DFW ICT to IP phone	342	171
	SJC IP phone to ICT (conference) to DFW ICT to IP phone	342	114
	DFW IP phone to ICT to SJC ICT to IP phone	302	302
	DFW IP phone to ICT (blind transfer) to RFD ICT to IP phone	50	149
	DFW IP phone to ICT (consult transfer) to RFD ICT to IP phone	50	149
	DFW IP phone to ICT (hold) to RFD ICT to IP phone	76	153
	DFW IP phone to ICT (conference) to RFD ICT to IP phone	48	144
	DFW IP phone to ICT to NYC ICT to IP phone		302	302
	NYC IP phone to ICT to DFW ICT to IP phone		302	302
	Intercluster BHCA Subtotals	2,485	2,611	604
BHCA Grand Total for DFW Site		27,699

1 BHCA = busy hour call attempts. 2 PSTN = public switched telephone network.

Small-Campus SIP Site (ATL) Load Testing

This section describes call load testing for calls originating or terminating in the Atlanta (ATL) site in the Small-Campus SIP Site model. The BHCA grand total tested for the ATL cluster was 104 busy hour call attempts. Table 22-3 shows the BHCA for intercluster calls between different endpoints in this site and other sites.

Table 22-3 Small-Campus SIP Site Model (ATL) Load Testing 

Call Type	Call Scenario	SJC-RFD BHCA 1	DFW BHCA	NYC BHCA	ATL BHCA	YYZ BHCA
Intercluster calls	SJC IP phone to ICT2 to ATL ICT to IP phone	68			68
	ATL IP phone to ICT to SJC ICT to IP phone	36			36
	Intercluster BHCA Subtotals	104			104
BHCA Grand Total for ATL Site		104

1 BHCA = busy hour call attempts. 2 ICT = intercluster trunk.

Small-Campus H.323 Site (YYZ) Load Testing

This section describes call load testing for calls originating or terminating in the Toronto (YYZ) site in the Small-Campus H.323 Site model. The BHCA grand total tested for the YYZ cluster was 92 busy hour call attempts. Table 22-4 shows the BHCA for intercluster calls between different endpoints for various call scenarios.

---

Note Some calls show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary services was performed at the originating cluster, which resulted in additional call processing at the originating cluster.

---

Table 22-4 Small-Campus H.323 Site Model (YYZ) Load Testing 

Call Type	Call Path	SJC-RFD BHCA 1	DFW BHCA	NYC BHCA	ATL BHCA	YYZ BHCA
Intercluster calls	SJC IP phone to ICT2 to YYZ ICT to IP phone	36				36
	SJC IP phone to ICT (blind transfer) to YYZ ICT to IP phone	13				4
	SJC IP phone to ICT (consult transfer) to YYZ ICT to IP phone	13				4
	SJC IP phone to ICT (hold) to YYZ ICT to IP phone	10				5
	SJC IP phone to ICT (conference) to YYZ ICT to IP phone	18				6
	YYZ IP phone to ICT to RFD ICT to IP phone	36				36
	Intercluster BHCA Subtotals	104				92
BHCA Grand Total for YYZ Site		92

1 BHCA = busy hour call attempts. 2 ICT = intercluster trunk.

North America Cisco Unified CallManager Interoperability Site (NYC) Load Testing

This section describes call load testing for calls originating or terminating in the New York City (NYC) site in the North America Cisco Unified CallManager Interoperability Site model. The BHCA grand total tested for the NYC cluster was 1,811 busy hour call attempts. Table 22-5 shows the BHCA for intercluster calls between different endpoints for various call scenarios.

---

Note Some calls show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary services was performed at the originating cluster, which resulted in additional call processing at the originating cluster.

---

Table 22-5 North America Cisco Unified CallManager Interoperability Site Model (NYC) Load Testing 

Call Type	Call Scenario	SJC-RFD BHCA 1	DFW BHCA	NYC BHCA	ATL BHCA	YYZ BHCA
Intercluster calls	SJC IP phone to ICT2 to NYC ICT to IP phone	450		450
	SJC IP phone to ICT (blind transfer) to NYC ICT to IP phone	108		36
	SJC IP phone to ICT (consult transfer) to NYC ICT to IP phone	108		36
	SJC IP phone to ICT (hold) to NYC ICT to IP phone	118		59
	SJC IP phone to ICT (conference) to NYC ICT to IP phone	108		36
	DFW IP phone to ICT to NYC ICT to IP phone		302	302
	NYC IP phone to ICT to RFD ICT to IP phone	599		599
	NYC IP phone to ICT to DFW ICT to IP phone		302	302
	Intercluster BHCA Subtotals	1,491	604	1,820
BHCA Grand Total for NYC Site		1,820

1 BHCA = busy hour call attempts. 2 ICT = intercluster trunk.