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

Transcription

1 This topic provides an overview of the call loads that were tested with various site models during Cisco Unified Communications Release 7.0(1) testing for IP telephony. It includes information for made within various site models (intracluster) and for made between site models (intercluster). During call load testing, the busy hour call attempt () rates described in this topic were sustained for five consecutive days. Note The information in this topic represents tested call rates, not the maximum call rate capabilities of the system. Also, call load testing was performed with all components configured with detailed trace levels. This topic includes the following sections: Very Large Campus with Clustering over the WAN () Load Testing Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) Load Testing Large SIP Site () Load Testing Cisco Communications Manager 7.0(1) Interoperability Site () Load Testing Cisco CallManager 4.2(3) Interoperability Site () Load Testing Small Campus SIP Unified Communications Manager Express Site () Load Testing Small Campus H.323 Unified Communications Manager Express Site () Load Testing Medium Business with Remote Locations (AZO) Load Testing Very Large Campus with Clustering over the WAN () Load Testing This section describes call load testing for 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 grand total tested for the cluster was 79,650 busy hour call attempts. Table 1 shows the for various call types and call scenarios between different endpoints. In addition to the call scenarios shown, the Cisco Unified Presence Server in the cluster maintained 1,000 active logins from Cisco IP Phone Messenger clients and monitored 1,000 user presence states. 1

2 Very Large Campus with Clustering over the WAN () Load Testing Call Load Testing Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. Table 1 Very Large Campus with Clustering over the WAN Site Model () Load Testing 1 SFO-ORD Intracluster SJC to SJC Cisco Unified Contact Center Express 2,800 SJC to SJC Cisco Unified MeetingPlace 4,095 SJC to SJC Cisco Unity 4,725 SJC to SJC 756 SJC to SJC (blind transfer) 945 SJC to SJC (consult transfer) 945 SJC to SJC (hold) 1,344 SJC to SJC (conference) 890 SJC encrypted to SJC encrypted 1,260 SJC encrypted to SJC encrypted (blind transfer) 315 SJC encrypted to SJC encrypted (consult transfer) 441 SJC encrypted to SJC encrypted (hold) 840 SJC encrypted to SJC encrypted (conference) 840 SJC video to SJC video 1,995 SJC video to SJC video (blind transfer) 441 SJC video to SJC video (consult transfer) 272 SJC video to SJC video (hold) 1,260 SJC video to SJC video (conference) 504 SJC CUPC to SJC CUPC 1,029 SJC to SJC PSTN 2 to SJC PSTN to 32,928 SJC to SJC PSTN (blind transfer) to SJC PSTN to 2,352 2

3 Very Large Campus with Clustering over the WAN () Load Testing Table 1 Very Large Campus with Clustering over the WAN Site Model () Load Testing (continued) 1 SFO-ORD SJC to SJC PSTN (consult transfer) to SJC PSTN to 1932 SJC to SJC PSTN (hold) to SJC PSTN to 126 SJC to SJC PSTN (conference) to SJC PSTN to 3,150 SJC to SJC analog (6624) 1,344 SJC to SJC analog (Cisco VG224/ Cisco VG248) 2,352 SJC to SJC encrypted PSTN to SJC PSTN to 756 SJC to SJC encrypted PSTN (blind transfer) to SJC PSTN to 504 SJC to SJC encrypted PSTN (consult transfer) to SJC PSTN to 504 SJC to SJC encrypted PSTN (conference) to SJC PSTN to 378 Intracluster Subtotal 72,023 Intercluster SJC/RFD to ICT to SFO ICT to SJC/RFD to ICT (blind transfer) to SFO ICT to SJC/RFD to ICT (consult transfer) to SFO ICT to SJC to ICT (hold) to SFO ICT to SJC/RFD to ICT (conference) to SFO ICT to SJC to ICT to ORD ICT to SJC/RFD to ICT (blind transfer) to ORD ICT to SJC/RFD to ICT (consult transfer) to ORD ICT to SJC to ICT (hold) to ORD ICT to SJC/RFD to ICT (conference) to ORD ICT to SJC to ICT 3 to ICT to SJC to ICT (blind transfer) to ICT to

4 Very Large Campus with Clustering over the WAN () Load Testing Call Load Testing Table 1 Very Large Campus with Clustering over the WAN Site Model () Load Testing (continued) SJC/RFD to ICT (consult transfer) to ICT to SJC to ICT (hold) to ICT to SJC to ICT (conference) to ICT to SJC/RFD to ICT to ICT to IP SJC/RFD to ICT (blind transfer) to ICT to SJC/RFD to ICT (consult transfer) to ICT to SJC/RFD to ICT (hold) to ICT to SJC/RFD to ICT (conference) to ICT to SJC/RFD to ICT to ICT to SJC/RFD to ICT (blind transfer) to ICT to SJC/RFD to ICT (consult transfer) to ICT to SJC/RFD to ICT (hold) to ICT to SJC/RFD to ICT (conference) to ICT to SJC/RFD to ICT to ICT to IP SJC/RFD to ICT to ICT to IP SJC/RFD to ICT (blind transfer) to ICT to SJC/RFD to ICT (consult transfer) to ICT to SJC/RFD to ICT (hold) to ICT to SJC/RFD to ICT (conference) to ICT to SFO/ORD to ICT to SJC ICT to SFO-ORD 4

5 Very Large Campus with Clustering over the WAN () Load Testing Table 1 Very Large Campus with Clustering over the WAN Site Model () Load Testing (continued) SFO/ORD to ICT (blind transfer) to SJC ICT to SFO/ORD to ICT (consult transfer) to RFD ICT to SFO/ORD to ICT (hold) to RFD ICT to SFO/ORD to ICT (conference) to SJC ICT to SFO/ORD to ICT to RFD ICT to IP SFO/ORD to ICT (blind transfer) to RFD ICT to SFO/ORD to ICT (consult transfer) to RFD ICT to SFO/ORD to ICT (hold) to RFD ICT to SFO/ORD to ICT (conference) to RFD ICT to to ICT to SJC ICT to to ICT (blind transfer) to RFD ICT to to ICT (consult transfer) to RFD ICT to to ICT (hold) to RFD ICT to to ICT (conference) to RFD ICT to to ICT to RFD ICT to to ICT to RFD ICT to to ICT to SJC ICT to to ICT to RFD ICT to Intercluster Subtotals 7,627 2,313 1, , Grand Total for Sites 79, = busy hour call attempts. 2. PSTN = public switched tele network. 3. ICT = intercluster trunk. 1 SFO-ORD 5

6 Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) Load Testing Call Load Testing Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) Load Testing This section describes call load testing for originating or terminating in the Unified SRST sites in the Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) site model. The grand total tested for the SFO-ORD cluster was 32,849 busy hour call attempts. Table 2 shows the number of that were made from and to various sites and endpoints. This table shows for various call types and call scenarios. Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. Table 2 Load Testing for Multisite Centralized, Clustering over the WAN with Unified SRST Site Model SJC/RFD 1 SFO/ORD Intracluster SFO to SFO 2,520 SFO to SFO (blind transfer) 252 SFO to SFO (consult transfer) 252 SFO to SFO (hold) 210 SFO to SFO (conference) 672 SFO to SFO PSTN 2 to SFO PSTN to 16,674 SFO to SFO PSTN (blind transfer) to SFO PSTN to 560 SFO to SFO PSTN (consult transfer) to SFO PSTN to 560 SFO to SFO PSTN (hold) to SFO PSTN to 588 SFO to SFO PSTN (conference) to SFO PSTN to 1,120 SFO to SFO Unity Connection 1,125 Intracluster Subtotal 24,533 Intercluster SJC to ICT to SFO ICT to SJC/RFD to ICT (blind transfer) to SFO ICT to SJC/RFD to ICT (consult transfer) to SFO ICT to

7 Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) Load Testing Table 2 Load Testing for Multisite Centralized, Clustering over the WAN with Unified SRST Site Model (continued) SJC/RFD 1 SFO/ORD SJC/RFD to ICT (hold) to SFO ICT to SJC/RFD to ICT (conference) to SFO ICT to SJC/RFD I to ICT to ORD ICT to SJC/RFD to ICT (blind transfer) to ORD ICT to SJC/RFD to ICT (consult transfer) to ORD ICT to SJC/RFD I to ICT (hold) to ORD ICT to SJC/RFD to ICT (conference) to ORD ICT to SFO/ORD to ICT to SJC ICT to SFO/ORD to ICT (blind transfer) to SJC ICT to SFO/ORD to ICT (consult transfer) to SJC ICT to SFO/ORD to ICT (hold) to SJC ICT to SFO/ORD to ICT (conference) to SJC ICT to SFO/ORD to ICT to RFD ICT to IP SFO/ORD to ICT (blind transfer) to RFD ICT to SFO/ORD to ICT (consult transfer) to RFD ICT to SFO/ORD to ICT (hold) to RFD ICT to SFO/ORD to ICT (conference) to RFD ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to

8 Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) Load Testing Call Load Testing Table 2 Load Testing for Multisite Centralized, Clustering over the WAN with Unified SRST Site Model (continued) SJC/RFD 1 SFO/ORD SFO/ORD to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to SFO/ORD to ICT to ICT to IP SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO/ORD to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO/ORD to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO/ORD to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to to ICT to SFO ICT to to ICT (blind transfer) to SFO ICT to

9 Multisite Centralized, Clustering over the WAN with Unified SRST (SFO-ORD) Load Testing Table 2 Load Testing for Multisite Centralized, Clustering over the WAN with Unified SRST Site Model (continued) to ICT (consult transfer) to SFO ICT to to ICT (hold) to SFO ICT to to ICT (conference) to SFO ICT to to ICT to ORD ICT to to ICT (blind transfer) to ORD ICT to to ICT (consult transfer) to ORD ICT to to ICT (hold) to ORD ICT to to ICT (conference) to ORD 0 0 ICT to to ICT to SFO ICT to IP to ICT to ORD ICT to IP to ICT to SFO ICT to to ICT to ORD ICT to to ICT to ORD ICT to to ICT to SFO ICT to Intercluster Subtotals ,316 2,247 1,169 1, Grand Total for SFO-ORD Sites 32, = busy hour call attempts. 2. PSTN = public switched tele network. SJC/RFD 1 SFO/ORD 9

10 Large SIP Site () Load Testing Call Load Testing Large SIP Site () Load Testing This section describes call load testing for originating or terminating in the Dallas () site in the Large SIP Site model. The grand total tested for the cluster was 29,193 busy hour call attempts. Table 3 shows the for various call types and call scenarios between different endpoints. Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. Table 3 Large SIP Site Model () Load Testing 1 SFO/ORD AZO Intracluster to 3,150 to (blind transfer) 1,008 to (consult transfer) 1,008 to (hold) 1,050 to (conference) 1,260 to PSTN 2 to PSTN to 9,555 to PSTN (blind transfer) to PSTN to 532 to PSTN (consult transfer) to PSTN to 532 to PSTN (hold) to PSTN to 1,260 to PSTN (conference) to PSTN to 1,260 to Unity 3,000 Intracluster Subtotal 23,615 Intercluster SJC/RFD to ICT to ICT to SJC/RFD to ICT (blind transfer) to ICT to SJC/RFD to ICT (consult transfer) to ICT to

11 Large SIP Site () Load Testing Table 3 Large SIP Site Model () Load Testing (continued) 1 SFO/ORD AZO SJC/RFD to ICT (hold) to ICT to SJC/RFD to ICT (conference) to ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to IP to ICT to RFD ICT to to ICT (blind transfer) to RFD ICT to to ICT (consult transfer) to RFD ICT to to ICT (hold) to RFD ICT to to ICT (conference) to RFD ICT to to ICT to SFO ICT to to ICT (blind transfer) to SFO ICT to to ICT (consult transfer) to SFO ICT to to ICT (hold) to SFO ICT to to ICT (conference) to SFO ICT to to ICT to ORD ICT to to ICT (blind transfer) to ORD ICT to

12 Cisco Communications Manager 7.0(1) Interoperability Site () Load Testing Call Load Testing Table 3 Large SIP Site Model () Load Testing (continued) 1 SFO/ORD AZO to ICT (consult transfer) to ORD ICT to to ICT (hold) to ORD ICT to to ICT (conference) to ORD ICT to 0 0 to ICT to ICT to to ICT (conference) to ICT to to ICT to ICT to to ICT (conference) to ICT to to ICT to ICT to to ICT to ICT to Intercluster Subtotals 3,068 1,530 5, Grand Total for Site 29, = busy hour call attempts. 2. PSTN = public switched tele network. Cisco Communications Manager 7.0(1) Interoperability Site () Load Testing This section describes call load testing for originating or terminating in the Raleigh () site in the Cisco Communications Manager 7.0(1) Interoperability Site model. The grand total tested for the cluster was 2,713 busy hour call attempts. Table 5 shows the for intercluster between different endpoints for various call scenarios. Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. 12

13 Cisco Communications Manager 7.0(1) Interoperability Site () Load Testing Table 4 Cisco Communications Manager 6.1(1) Interoperability Site Model () Load Testing 1 SFO-ORD AZO Intercluster SJC/RFD to ICT 2 to ICT to SJC/RFD to ICT (blind transfer) to ICT to SJC/RFD to ICT (consult transfer) to ICT to SJC/RFD to ICT (hold) to ICT to SJC/RFD to ICT (conference) to ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO/ORD to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to IP to ICT to ICT to 281 to ICT (conference) to ICT to IP to ICT to RFD ICT to to ICT to SFO ICT to to ICT to ORD ICT to to ICT to ICT to Intercluster Subtotals 1,185 1, ,713 Grand Total for Site 2, = busy hour call attempts. 2. ICT = intercluster trunk. 13

14 Cisco CallManager 4.2(3) Interoperability Site () Load Testing Call Load Testing Cisco CallManager 4.2(3) Interoperability Site () Load Testing Bhairav, is this section required??? This section describes call load testing for originating or terminating in the New York City () site in the Cisco CallManager 4.2(3) Interoperability Site model. The grand total tested for the cluster was 2,944 busy hour call attempts. Table 5 shows the for intercluster between different endpoints for various call scenarios. Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. Table 5 Cisco CallManager 4.2(3) Interoperability Site Model () Load Testing 1 SFO-ORD AZO Intercluster SJC/RFD to ICT 2 to ICT to SJC/RFD to ICT (blind transfer) to ICT to SJC/RFD to ICT (consult transfer) to ICT to SJC/RFD to ICT (hold) to ICT to SJC/RFD to ICT (conference) to ICT to SFO/ORD to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO/ORD to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to to ICT to ICT to to ICT (conference) to ICT to to ICT to SJC ICT to

15 Small Campus SIP Unified Communications Manager Express Site () Load Testing Table 5 Cisco CallManager 4.2(3) Interoperability Site Model () Load Testing (continued) 1 SFO-ORD AZO to ICT to SFO ICT to to ICT to ORD ICT to to ICT to ICT to Intercluster Subtotals 1,395 1, ,944 Grand Total for Site 2, = busy hour call attempts. 2. ICT = intercluster trunk. Small Campus SIP Unified Communications Manager Express Site () Load Testing This section describes call load testing for originating or terminating in the Atlanta () site in the Small Campus SIP Unified Communications Manager Express Site model. The grand total tested for the cluster was 322 busy hour call attempts. Table 6 shows the for intercluster between different endpoints in this site and other sites. Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. Table 6 Small Campus SIP Unified Communications Manager Express Site Model () Load Testing Intercluster 1. = busy hour call attempts. 2. ICT = intercluster trunk. 1 SFO-ORD SJC to ICT 2 to ICT to SFO to ICT to ICT to to ICT to SJC ICT to to ICT to ORD ICT to Intercluster Subtotals Grand Total for Site 322 AZO 15

16 Small Campus H.323 Unified Communications Manager Express Site () Load Testing Call Load Testing Small Campus H.323 Unified Communications Manager Express Site () Load Testing This section describes call load testing for originating or terminating in the Toronto () site in the Small Campus H.323 Unified Communications Manager Express Site model. The grand total tested for the cluster was 680 busy hour call attempts. Table 7 shows the for intercluster between different endpoints for various call scenarios. Note Some 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 7 Small Campus H.323 Unified Communications Manager Express Site Model () Load Testing Intercluster Call Path 1 SFO-ORD SJC to ICT 2 to ICT to SJC to ICT (blind transfer) 13 4 to ICT to SJC to ICT (consult 13 4 transfer) to ICT to SJC to ICT (hold) to 8 4 ICT to SJC to ICT (conference) to 21 7 ICT to SFO to ICT to ICT to SFO/ORD to ICT (blind transfer) to ICT to SFO/ORD to ICT (consult transfer) to ICT to SFO to ICT (hold) to ICT to SFO/ORD to ICT (conference) to ICT to to ICT to RFD ICT to to ICT to SFO ICT to Intercluster Subtotals Grand Total for Site 242 AZO 1. = busy hour call attempts. 2. ICT = intercluster trunk. 16

17 Medium Business with Remote Locations (AZO) Load Testing Medium Business with Remote Locations (AZO) Load Testing This section describes call load testing for originating or terminating in the Kalamazoo (AZO) site in the Medium Business with Remote Locations Site model. The grand total tested for the AZO cluster was 3896 busy hour call attempts. Table 8 shows the for intercluster between different endpoints in this site. Note Some intercluster show different values for the two clusters involved in the call. This situation occurs because a conference, hold, or transfer supplementary service is initiated at one of these clusters resulting in additional call processing (higher value) in that cluster. Table 8 Medium Business with Remote Locations (AZO) Load Testing Intercluster 1. = busy hour call attempts. 1 SFO-OR D AZO AZO to AZO Cisco 172 Unified MeetingPlace Express AZO to AZO Unity 840 Connection AZO to AZO 308 AZO to AZO 105 (blind transfer) AZO to AZO 105 (consult transfer) AZO to AZO 140 (hold) AZO to AZO 112 (conference) AZO to AZO PSTN to 1,568 AZO PSTN to AZO to AZO PSTN 140 (blind transfer) to AZO PSTN to AZO to AZO PSTN (consult transfer) to AZO PSTN to AZO to AZO PSTN (hold) to AZO PSTN to AZO to AZO PSTN (conference) to AZO PSTN to IP Intercluster Subtotals 3,896 Grand Total for AZO Site 3,

18 Medium Business with Remote Locations (AZO) Load Testing Call Load Testing 18

19 Medium Business with Remote Locations (AZO) Load Testing 19